w3c / activitystreams

Activity Streams 2.0
https://www.w3.org/TR/activitystreams-core/
Other
276 stars 61 forks source link

history #539

Closed trwnh closed 11 months ago

trwnh commented 1 year ago

Please Indicate One:

Please Describe the Issue:

In AS2-Core examples 18, 19, 32, we find collections representing the "history" of an object. Particularly in example 32, we see an object being Created, Updated, and Deleted.

However, there is no property dedicated to advertising such a collection.

I propose a history term be defined in the activitystreams.jsonld context document and added to the AS2-Vocab as well.

evanp commented 1 year ago

This is a very interesting and helpful idea. I think the process that we have outlined in the AS2 extensibility:

  1. Develop the structure in an external context document, perhaps using the FEP. Ideally, you should also notify the SocialCG of the ongoing.
  2. Get the extension implemented in a number of software packages, preferably >1.
  3. Once the extension is "popular", the SocialCG can vote whether or not to include its terms in the main activitystreams.jsonld context.

I would happily work on this FEP! It sounds really interesting.

trwnh commented 1 year ago

This could indeed be expressed in an FEP but there is the issue of namespacing. It would be nicer to have it be https://www.w3.org/ns/activitystreams#history instead of something like https://w3id.org/fep/xxxx/history -- although it should be possible at a later point to adopt it into the activitystreams context with an external id, similar to how inbox is actually ldp:inbox

evanp commented 1 year ago

Yes, it's entirely possible to adopt it into the context and maintain the namespace. That's the right thing to do. inbox is a good example there.

evanp commented 1 year ago

@trwnh are we going to create a FEP for this? I think the best idea would be to keep this issue open until the FEP has been started.

trwnh commented 1 year ago

https://codeberg.org/fediverse/fep/pulls/112

evanp commented 11 months ago

Since the FEP has been created, let's mark this resolved.