@steve

Have there been any further discussions on this? I think it’s becoming increasingly important!

https://github.com/steve-bate/activitypub-ontology/blob/main/activitystreams2.ttl

#activitystreams #activitypub #rdf

activitypub-ontology/activitystreams2.ttl at main · steve-bate/activitypub-ontology

This ontology is an unofficial version of an ActivityPub OWL ontology for experimentation and exploration purposes. It's based on an old Activity Streams ontology that was abandoned in favor of...

GitHub
@naturzukunft2026 No recent discussions. A year or two ago I tried submitting some related issues to update the W3C AP (really AS2) ontology but there was a lot of resistance to updating it for some reason that's mysterious to me.
2/2 @steve
We need to ensure that we have – or find – a compatibility layer between the two groups. My ideas are a bit more complex and I’d like to be able to document and communicate them somehow. So at the moment I’ve started working on my own ontology as an extension to yours. For now, this is just for internal use. But when you federate new types, I wouldn’t know how else to describe it.

@naturzukunft2026 @steve

For Protosocial AP extension I intend to conceptually divide the protocol layer into 2 API's. The Protosocial API provides a closed-world view of the social network as a JSON-LD-formatted but plain JSON distributed actor-based messaging architecture. While the Knowledge API exposes read-only open world information supporting full linked data.

@naturzukunft2026 @steve

As for compatibility layer, bridging these worlds, the idea is that services encapsulate their design, which can be introspected and validated against.