search

gs1 / EPCIS

Draft files being shared for EPCIS 2.0 development
Other
20 stars 7 forks source link

Conversion of Private or Industry-wide URN to URL #242

Closed shalikasingh closed 3 years ago

shalikasingh commented 3 years ago

Hi @mgh128 ,

Can you please throw some light on how the translation between EPC URN to DL will take place wrt Private or Industry-wide URN?

Have taken an example from 2021_03_29q CBV 2-0 COMMREV and translated it to the corresponding EPC URN. Please let me know if the below conversion of DL to URN is done correctly

DL : <epc>http://epcis.example.com/user/vocab/bt/12345.67890</epc> URN: <epc>urn:http://epcis.example.com/:user:vocab:bt:12345.67890</epc>

mgh128 commented 3 years ago

I don't think that's correct at all.

http is not a defined value within https://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml so it has no legitimacy as the component that follows urn:

Neither this group nor any EPCIS/CBV implementation has any authority to specify how a particular user-defined / vendor-defined Web URI should be expressed as a URN. Nor do I see any need to do this.

Note that not all Web URIs are GS1 Digital Link URIs. The GS1 Digital Link standard defined a URI syntax for expressing GS1 identifiers in a Web URI format - and the use of the .well-known mechanism to point to a resolver description file to make this intention explicit by anyone who constructs a GS1 Digital Link URI using their own domain name.

http://epcis.example.com/user/vocab/bt/12345.67890 is a Web URI. It is not a GS1 Digital Link URI. It does not need to be translated to a URN.