Let’s say for some contrived (but very real) reason, I want to add { "toot": "http://joinmastodon.org/ns#", "Emoji": "toot:Emoji" } to @context, but another member of @context might be { "toot": "http://joinmastodon.org/ns#", "focalPoint": ... }
Would it be acceptable if I just pushed my object to the end and assumed that JSON-LD parsers would correctly reduce it down to:
{
"toot": "http://joinmastodon.org/ns#",
"Emoji": "toot:Emoji",
"focalPoint": ...
}
… or should I be adding in logic to detect the existing member defining toot and merge the Emoji property in?
@julian depends on if your property conflicts with any other defined properties. (see the schema.org problem)
@thisismissem@hachyderm.io let’s assume no. Only common property is
toot.I just want to make sure it’s not going to make fedify or smithereen throw errors when it tries to parse my janky
@context.
