Make link headers canonical
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 26
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
In the current specification, the section on Link headers says that "a client MUST treat the RDF in the body of the WebID Profile as canonical."
Is there a specific reason for this decision?
I am asking because having the Link header as canonical instead would allow for an easier integration of this (non-writable) technical information with the (preferably writable) content of a Solid Profile.
Contributor guide
No contributing guide indexed for this repository
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 linked Link headers section in the Solid OIDC specification and review the stated treatment of RDF in the WebID Profile as canonical. Determine whether Link headers should instead be canonical and document the decision or resulting specification change.
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
- 25/100