Skip to content
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

linkType=linkset, not all #273

Closed
philarcher opened this issue Feb 2, 2025 · 2 comments
Closed

linkType=linkset, not all #273

philarcher opened this issue Feb 2, 2025 · 2 comments
Assignees
Labels
Identity Resolver Issues related to Identifiers and resolvers

Comments

@philarcher
Copy link
Contributor

In the IDR spec and anywhere else that talks about requesting the linkset for a given item, please note that ISO/IEC 18975 (and GS1 Conformant resolver) use linkType=linkset. At GS1, the original linkType=all construct has been deprecated.

Also, note that RFC 9264, the linkset spec, says that if you set the HTTP Accept header to application/linkset+json the service should return the linkset and not redirect. The ISO/IEC spec just says "follow RFC 9264". The GS1 Conformant resolver spec explictly calls this out.

@philarcher philarcher added the Identity Resolver Issues related to Identifiers and resolvers label Feb 2, 2025
@onthebreeze
Copy link
Contributor

onthebreeze commented Feb 3, 2025

OK thanks for the pickup - I see that your PR has already changes ?linktype=all to ?linktype=linkset.

Regarding the HTTP accept header if the desired behaviour is redirect to default target, I suppose that means it can be pretty much anything except application/linkset+json - eg text/html?

@onthebreeze
Copy link
Contributor

ok to close?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Identity Resolver Issues related to Identifiers and resolvers
Projects
None yet
Development

No branches or pull requests

2 participants