#ActivityPub (via Activity Streams 2.0) defines "extension" as additional JSON-LD vocabulary terms: behavior is undefined. Extensions, as defined by AS2, are irrelevant since very few implementations (if any) use JSON-LD processing. And yet, the Fediverse implements many behavioral extensions. Those arise from the developer community outside the scope of ActivityPub and JSON-LD. Selling AP to new developers? Simplify it. Drop JSON-LD. Embrace the community.
@mariusor "Dropped", as in, don't mention JSON-LD if "plain old simple JSON" is sufficient.
@Steve_Bate I don't see how that would be an advantage over the current wording.
And I don't think you really mean that.
There won't be "plain old simple JSON", it will be JSON according to "this one schema" that you now have to write and maintain and be responsible for.
What you're arguing for really, is that you think one way of formalizing a data structure with JSON is superior to another. I'm not convinced yet.
Most of the time "Extension" should really be called "Expansion" .. of whack-a-mole programming and maintenance chores. 😅
Unless the extension is a community maintained open standard, that people stick to, and that defines the expected wire formats and behavior with enough detail and rigour.
@mariusor What you think I'm really arguing for is an overgeneralization of what I suggested would be beneficial *specifically for the Fediverse*. For RDF applications and related data structures, JSON-LD is clearly a better choice than plain JSON. Different context. Different tradeoffs.
@Steve_Bate no, no, I was thinking of the fediverse.
I might be wrong, but I think you underestimate just how much structure the JSON-LD part of the vocabulary provides, and that you'll need to recreate it for that simplified schema you're thinking of. And if you're planning for it to simplify the structure, then you'll be working with your own subset which won't be compatible with some of the existing applications.
Maybe for you that loss is insignificant, but to me - maintainer for some of those applications - is not.
@mariusor It would difficult to underestimate it. The AS2 JSON-LD context (and "extension" contexts) define practically *no* structure at all. The contexts primarily define terms. The AS2 spec defines simple structures in the text but that's not represented in the JSON-LD context.
I haven't said anything about schemas in this thread. Different topic. JSON-LD is not intended to be a schema language. It doesn't provide interop benefits because JSON-LD processing is optional and very rarely used.
@Steve_Bate I'm sorry if I'm not making myself understood, but the crux of what I'm saying is: to strip away the JSON-LD elements from the activity vocabulary, *AND* keep compatibility with current fediverse implementation, you will *NEED* to create a schema for future developers to work off of.
And that schema will inherently have to specify the idiosyncrasies of the JSON-LD representation of the Vocabulary.
> The AS2 spec defines simple structures in the text but that's not represented in the JSON-LD context.
I think that's not quite a correct conclusion: the JSON-LD's "RDF triples" representation informs the structure alongside the context.
> If you know what JSON-LD is, you can take advantage of the cool linked data approaches provided by JSON-LD. If you don't, don't worry, JSON-LD documents and ActivityStreams can be understood as plain old simple JSON.
@Steve_Bate how much more does it need to be "dropped" though?
From https://www.w3.org/TR/activitypub/#:~:text=If%20you%20don%27t%2C%20don%27t%20worry%2C
ActivityPub