Unsufficient restriction over user supplied containment triples
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
Currently following requirement is the only one that restricts user supplied containment triples.
Servers MUST NOT allow HTTP PUT or PATCH on a container to update its containment triples; if the server receives such a request, it MUST respond with a 409 status code. [Source]
But that allows including containment triples in representation of to be created container, when container is created through POST on parent container.
It may not be the intention.
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
Read the existing PUT/PATCH requirement and its cited Solid specification issue comment first. Then determine whether POST-created container representations may carry containment triples; done requires an agreed normative requirement for that case to be recorded in the specification.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100