@silverpill @mariusor

I don't think you can say that. AS has more uses than with AP. I know of at least:

- Linked Data Event Streams
- DCAT-AP and DCAT-AP Feeds
- Linked Data Event Notifications

And as for #ActivityStreams relation to #ActivityPub I'd say - and it is the argument I make in the GH issue - that we have a vocabulary without good grammar and language rules. The AS social primitives are loose words, and you can construct any gibberish with them and try to make it popular slang.

@smallcircles @silverpill @mariusor DSNP uses a subset of AS2 with some extensions.

https://dsnp.org/

@smallcircles @silverpill @mariusor also, I disagree about the vocab. We took on a few of the important use cases in the ActivityPub spec (CRUD, collections, social graph).

Now, extensions like Geosocial https://github.com/swicg/geosocial and groups https://github.com/swicg/groups are defining how to use more of the vocabulary on the wire. I think if we take on events, too, we can cover the whole vocabulary, more or less.

@smallcircles @silverpill @mariusor I have sections on each of the use cases in my book. They were made to work the way you'd expect. I think there are some gaps in some parts, though!

@evan @silverpill @mariusor

Sounds like a very good direction, and perhaps a ️ → direction there.

Every vote is a very opinionated one anyway, I guess, and depends on the expectations one has wrt to the protocol stack and the future of fediverse and social networking, and how it fulfills current (app) needs.

@smallcircles @silverpill @mariusor I think the vocabulary becomes much more important in a world of the ActivityPub API. Supporting those main use cases, ofc, but also making extensions that work purely at the edge.

@smallcircles @silverpill @mariusor I think it was a good decision to keep AP focused on the essentials for bootstrapping a network. But if I could go back in time, though, I wish we had fleshed out the rest of the vocabulary in extensions docs much sooner after AP was published.

@evan @silverpill @mariusor

Yea, those are things that can be said in hindsight. Maybe there was also the implicit expectation that the standardization process would continue in similar fashion as with other W3C recommendations. Not accounting for the organic growth in the grassroots developer ecosystem with its very particular social dynamics and how that would severely complicate things over time by accidental complexity popping up all over the place.

@evan @silverpill @mariusor

I mean AS/AP are quite unique in this regard, in the way things came together from the bottom upwards when it comes to formal open standards formation. Unique evolutionary process needed too.

@smallcircles @silverpill @mariusor Maybe. I think the CG should have followed through on the full vocabulary, and done at least one other extension to figure out how it's done. We can't go back in time, though!