I looked through the GS1-based examples and made a few minor changes that I hope are OK.
The underlying complication is that id.gs1.org is not a typical website as such but a resolver as defined by the GS1 Digital Link standard so its behavior may not be as expected. Specifically, the linkType=all parameter that shows up in a couple of places is what prevents the resolver redirecting you to one of the links in the linkset. The other way to avoid being redirected is to set the Accept header to application/linkset+json :-)
I am just editing the XML, I can't see the rendered version and I am new to editing RFCs so it's more than likely I've messed up. But I hope this is at least helpful. Happy, of course, to discuss further as required.
Almost as an aside, we are committed to making our implementation fully conformant to linkset, but recognize we're not quite there yet. We will include the profile parameter (please don't hold me to a deadline!!)
I looked through the GS1-based examples and made a few minor changes that I hope are OK.
The underlying complication is that id.gs1.org is not a typical website as such but a resolver as defined by the GS1 Digital Link standard so its behavior may not be as expected. Specifically, the linkType=all parameter that shows up in a couple of places is what prevents the resolver redirecting you to one of the links in the linkset. The other way to avoid being redirected is to set the Accept header to application/linkset+json :-)
I am just editing the XML, I can't see the rendered version and I am new to editing RFCs so it's more than likely I've messed up. But I hope this is at least helpful. Happy, of course, to discuss further as required.
Almost as an aside, we are committed to making our implementation fully conformant to linkset, but recognize we're not quite there yet. We will include the profile parameter (please don't hold me to a deadline!!)