(@mgh128 and @CraigRe I submitted a CommunityReview issue 30 min ago, but we cannot edit them to provide any extra info, so I'm posting a github issue as well).
@domguinard: At the Nov 9 call we discussed what should eg REST /bizSteps or /bizSteps/receiving return: a list of HATEOAS links.
Dom, could you evaluate if we should use this RFC spec?
Note: H. Van de Sompel is the creator of OAI PMH and Memento, so he knows about linking resources
GS1_Global_Office_Resolver.pdf gives an example of what these links could look like for the purpose of DigitalLinks, eg
(@mgh128 and @CraigRe I submitted a CommunityReview issue 30 min ago, but we cannot edit them to provide any extra info, so I'm posting a github issue as well).
@domguinard: At the Nov 9 call we discussed what should eg REST /bizSteps or /bizSteps/receiving return: a list of HATEOAS links.
https://www.gs1.org/docs/Digital-Link/GS1_Global_Office_Resolver.pdf refers to https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-linkset-05. That RFC describes a format for returning links, either in JSON payload (with appropriate media type) or using Link header(s).
Dom, could you evaluate if we should use this RFC spec? Note: H. Van de Sompel is the creator of OAI PMH and Memento, so he knows about linking resources
GS1_Global_Office_Resolver.pdf gives an example of what these links could look like for the purpose of DigitalLinks, eg
@domguinard if you think that
... then just reject this issue.