Make link headers canonical

Open
#210 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

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.

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.

Dominant language
Bikeshed
Stars
26
Forks
14
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from solid/solid-oidc

All issues in solid/solid-oidc

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.