Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

history #539

Closed
1 of 5 tasks
trwnh opened this issue May 9, 2023 · 6 comments
Closed
1 of 5 tasks

history #539

trwnh opened this issue May 9, 2023 · 6 comments
Labels
Pending Closure Resolved Unless the issue creator protests, this will be closed in a week or two

Comments

@trwnh
Copy link

trwnh commented May 9, 2023

Please Indicate One:

  • Editorial
  • Question
  • Feedback
  • Blocking Issue
  • Non-Blocking Issue

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.

@trwnh trwnh changed the title as:history history May 9, 2023
@evanp
Copy link
Collaborator

evanp commented May 24, 2023

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.

@evanp evanp added the Pending Closure Resolved Unless the issue creator protests, this will be closed in a week or two label May 24, 2023
@trwnh
Copy link
Author

trwnh commented May 24, 2023

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
Copy link
Collaborator

evanp commented May 25, 2023

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
Copy link
Collaborator

evanp commented Jun 7, 2023

@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
Copy link
Author

trwnh commented Jun 15, 2023

@evanp
Copy link
Collaborator

evanp commented Aug 16, 2023

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

@evanp evanp closed this as completed Aug 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Pending Closure Resolved Unless the issue creator protests, this will be closed in a week or two
Projects
None yet
Development

No branches or pull requests

2 participants