@reiver

Today "ActivityStreams: Where do you want to go to today?" might be a slogan we borrowed from Microsoft.

The question is whether #ActivityStreams should be used - besides all the things it is already being used for - to also map to file systems.

The #LinkedData nature of #ActivityPub is generally shunned in favor of plain #JSON. That in itself is fine, as long as:

a) information still represents valid #JSONLD.

b) information models still follow data modeling best practices.

c) information models are designed with #interoperability in mind.

Not saying your approach is good or bad, just observing that everyone mapping and overloading their own app-specific semantics to the poor AS vocab looks to me a worst-practice. We can get away with it, as we made post-facto interop the poor man's accepted practice, lacking more rigorous extension process and guidance.

There are likely existing standardized ontologies.

@gugurumbe

Yes, thank you. It is a bit of everything. Where I worked in Print production at the time we used all the XML standards to max extent and got great benefit from doing so. It all crumbled down very quickly with the take-off of Web where #JSON mapped way better to JS than #XML did, esp. when also honoring the intricate web of (de-facto) standards that had emerged, and how the XML ecosystem got captured by corporations peddling expensive products, such Enterprise service buses and the like.

It would have been great if #XHTML had stuck around. In hindsight the shift to HTML5 may be seen as a move by the WHATWG to establish their dominance over the #browser market.

As for #JSONLD it must see to rewin hearts and minds, must inspire and convince people to take the bet of adopting it.

@strypey @FinchHaven @naturzukunft2026

For the sake of further clarity I should point to your starting post and this text:

> we need domain-specific applications that leverage ActivityPub’s full semantic potential

And remark that in my opinion and by observation, tapping the sign "Reminder: #ActivityPub is #JSONLD, folks!" isn't enough. Much more is needed than pointing to the #OpenStandards to win back developers minds to adopt #LinkedData. There is a high reluctance and resistance to adoption that must be overcome.

Referring again to that adoption chart I drafted the other day - which is about #SolidProject, but this is where LD is strong(est?) today - "build open standards, and they will come" isn't going so well. I hope that changes, as I have always been a fan of the *notion* of the semantic web. Yet in role of a technology decision maker, not ready to bet on it for a social networking environment.