add(considered): the "dpp" link relation is resolver-side, not page-side - #148
Draft
jdevalk wants to merge 1 commit into
Draft
add(considered): the "dpp" link relation is resolver-side, not page-side#148jdevalk wants to merge 1 commit into
jdevalk wants to merge 1 commit into
Conversation
IANA registered rel="dpp" for Digital Product Passports on the UN Transparency Protocol's authority, and schema.org 30.0 added EU DPP examples. But UNTP carries the relation in an RFC 9264 linkset returned by a GS1 Digital Link resolver, not on the product's own page — so there is no website behaviour to spec yet. Recorded with what would reverse it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
0211d5c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f4653e7f.specification-website.pages.dev |
| Branch Preview URL: | https://add-considered-dpp-link-rela.specification-website.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
One new entry in
src/content/considered/—dpp-link-relation.md, reasontoo-early. No spec page.Why now
Daily standards scan, 2026-08-01. Three signals landed close together and looked, at first pass, like a topic arriving:
dppin the Link Relation Types registry — "a link from a context URI that identifies a product to its digital product passport" — on the authority of the UN Transparency Protocol.Why it did not earn a page
The relation is real and in use — but not on websites. UNTP carries
dppinside an RFC 9264 linkset returned by an identity resolver that extends the GS1 Digital Link resolver schema. The context URI is a GS1 product identifier, the client is a scanner following a QR code on physical packaging, and the passport comes back as a verifiable credential (application/vc+jwt). A page here would have to tell readers to putLink: <…>; rel="dpp"on their product pages, and nothing asks them to.That is a scope miss rather than the usual "finished RFC, no implementations" miss, so the entry says so — and names what would flip it: a product page advertising its own passport, which ESPR delegated acts could produce quickly.
Sources
Status
Not applicable — no spec page, so no status and no changelog entry (the changelog covers spec pages, not the register).
npm run buildpasses.🤖 Generated with Claude Code