-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linkset errors #272
Comments
The same problem applies to the section about creating new links. The linkset is mal-formed. |
And the secure targets section. |
From what I can see here - https://datatracker.ietf.org/doc/rfc9264/ the thing below {
"linkset": [
{
"anchor": "https://resolver.sample-register.example/products/ABCD9876",
"untp:dpp": [
{
"href": "https://sample-credential-store.example/credentials/dpp/90664869327.json",
"title": "Digital Product Passport",
"hreflang":["en"],
"type": "application/vc+jwt"
},
{
"href": "https://sample-credential-store.example/credentials/dpp/90664869111.json",
"rel":["predecessor-version"],
"title": "Digital Product Passport",
"hreflang":["en"],
"type": "application/vc+jwt"
}
]
}
]
} |
OK to close this? noting separate discussion on link type registration. |
The Versioned Targets section of the IDR spec has important errors in the example linksets.
Below the
anchor
, the next level down is the link relation. This is either an IANA-registered link relation or a URI. It is not an array.The confusion arises because in an HTML hyperlink you can indeed provide a white space separated list of relations, but not in a linkset.
To support the concepts of version targets we might want to introduce link types for 'latest version' and 'immutable version'? Eiher way, that section needs thinking about
The text was updated successfully, but these errors were encountered: