deprecate wac:Control
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
In todays authorization panel (see PR) it was pointed out that the access modes were currently defined in the spec.
So @matthieubosquet argued and others seemed to agree that
It is the purpose of the Solid protocol to define which operations can be performed depending on granted access modes.
Given that I would like to point to the issue #94 deprecate acl:Control, replace with ... that I mistakenly wrote up in the WAC spec site thinking that this issue was decided there.
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 authorization-panel minutes linked in the issue and issue #94, which contains the related proposal to deprecate acl:Control. Determine the agreed replacement and scope before changing the specification; done means the decision and resulting treatment of wac:Control are reflected consistently in the relevant specification text.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100