@heluecht @jaywink @Gargron @nightpool @firstname.lastname@example.org Alternatively, the cats already out of the bag, and since no one really parses JSON-LD at runtime, we'll just standardize on what's already out there, I'll change go-fed, and we'll live with the possibility of vocab collisions. Which avoids painful migrations.
@cj I'm not sure I understand the question. The PR linked doesn't look like valid JSON-LD at all. Valid JSON-LD would look something like:
"sec:publicKeyPem": "-----BEGIN PUBLIC KEY...",
@nightpool Thanks for pointing this out -- go-fed is definitely not propagating the default alias at serialization time, so that's a bug.
However my original question still stands --- if go-fed does alias the security context to "widsv" or anything else, can Mastodon et. al. (+cc @heluecht @jaywink ) handle deserializing that, or do they do non JSONLD deserializing and expect "publicKey" to never have a prefix?
I don't know JSON-LD well enough to say whether the current is a bug or not? If the security context is not an object, does the property require a prefix to be valid JSON-LD?
Please guys try to always reply to all btw, difficult to follow otherwise :P
@jaywink @cj @heluecht the way mastodon currently serializes it is also valid JSON-LD, although there ARE some subtle differences between the two. As I understand it, the array form is including the entire context while the object form is only referencing the namespace.
mastodon would not be able to process "sec:publicKey" currently, but I would prefer you federate the extension the way you prefer to and then open an issue to have us make our code compatible rather then the other way around.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!