Make `#uri-slashes-hierarchical-identifier` a `spec::Requirement` in spec rdfa
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
Currently #uri-slashes-hierarchical-identifier is not an object on any statement with predicate spec:requirement in spec rdfa.
As it seems also n requirement to be enforced, though shared between server and client, if it is linked as other requirements, we can uniformly query it. requirement subject can be both client and server.
If at all it makes sense.
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
Locate the spec RDFa statements around #uri-slashes-hierarchical-identifier and compare them with neighboring spec:requirement links. Check how requirement subjects are represented for clients and servers, then verify the RDFa query result. Done means the identifier is represented as a spec:requirement object consistently with the other requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100