Creation of Memento resources
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
The Solid Ecosystem document mentions Memento as an optional dimension for content negotiation.
Memento, itself, defines a mechanism whereby a client can discover and retrieve previous states of a resource. Memento does not define how these previous states (Mementos) are created or otherwise managed. Is this an implementation decision or will the Solid specification take a stance on issues such as:
- Will it be possible to delete a Memento? If so, what are the ACL implications?
- How and under what conditions are Mementos created? Is a new Memento created every time a resource is modified?
- When a resource is deleted, are all associated Mementos also removed?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked Solid Ecosystem document and RFC 7089, then review the issue's questions about Memento deletion, creation conditions, and resource deletion. Done means the specification clearly states its position on Memento lifecycle and ACL implications, or identifies these as implementation decisions.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100