What does a delete operation imply?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
[Question was raised in https://github.com/solid/specification/pull/157#discussion_r405219429 .]
The read, write and append operations ( #149 #126 #118 ) are aligned with WAC access modes. Write covers delete in both access mode and definition. Given that context, would it be useful to introduce the notion of delete as a separate operation?
"A delete operation entails that information can be removed."
Without discussing atomicity or recursion in the definition, I'm not sure how useful it'll be, but it may support the phrase "delete operation". Tautology.
It may help to revisit this after existing requirements involving write and delete are drafted and accepted. Ditto "update" and possibly other operations that could be argued to be distinct but I don't think we want to go over board or worse redefine CRUD or something.
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 with the discussion linked from pull request #157 and review the related issues #149, #126, and #118. Revisit the question after the existing requirements for write and delete are drafted and accepted; done would require a decision on whether delete should be a separate operation and corresponding specification changes.
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
- 20/100