Fix incorrect metadata member name in Section 8.2.1
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 160
- Forks
- 40
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 23
Description
Section 8.2.1 (Paginated Requests) says:
Furthermore, the PDP MUST declare support for the corresponding capability URN in its
supported_capabilitiesmetadata (Section 9.1.2).
There is no supported_capabilities metadata member. Section 9.1.2, which this sentence itself cross-references, defines the member as capabilities, and that is the name registered in the PDP Metadata Registry (Section 12.3). supported_capabilities appears nowhere else in the document, and it is also present in the published version.
Should be fixed as: capabilities.
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
Open the AuthZEN specification and locate Section 8.2.1, then compare its metadata member name with the definition in Section 9.1.2 and the PDP Metadata Registry in Section 12.3. Replace the incorrect supported_capabilities reference with capabilities and verify that no incorrect occurrence remains in the document.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 92/100