search

gs1 / EPCIS

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

Appropriate guidance/examples for URN/Web URI notations #120

Closed RalphTro closed 3 years ago

RalphTro commented 3 years ago

Hi @CraigRe , There are quite a number of occurrences in the EPCIS Guide in which we explicitly specify the usage of URNs, be it for object IDs, locations, parties, source/destination IDs, etc. As we have now TWO ways to express these values (i.e. as we introduced Web URIs/GS1 Digital Link URIs) in a standardised manner, I think we need to discuss how we could best address this. E.g., we could go for a neutral description instead of providing the URI value (e.g. 'Shipping (CBV)'), always provide both options, or sth. else. I think we need to have a thorough discussion on this matter in the group. What is your take on this? Kind regards, @RalphTro

mgh128 commented 3 years ago

Hi @RalphTro , @CraigRe

If you're talking about a neutral way to refer to either

urn:epcglobal:cbv:bizstep:shipping or https://ns.gs1.org/cbv/BizStep-shipping
then probably the most neutral way is to use a CURIE / QName such as

bizstep:shipping
where bizstep maps to urn:epcglobal:cbv:bizstep: OR https://ns.gs1.org/cbv/BizStep-

I think we can take this approach for all CBV URNs where we're now tolerating a Linked Data Web URI alternative that has the same meaning (but also provides an online definition)

I will try to ensure that the Linked Data Web URIs show the URN equivalents. I'm working on those tools this afternoon.

RalphTro commented 3 years ago

Thanks for this suggestion, @mgh128 . I like this!

jmcanterafonseca-iota commented 3 years ago

I would like to also use just shipping and not to use the CURIE format. That could be actually possible by providing a @protected JSON-LD @context for the CBV

mgh128 commented 3 years ago

Good idea. I'll look into this. We can consider adding a context for CBV terms, with aliases and @protected.

jmcanterafonseca-iota commented 3 years ago

great, you would need then to change some of the @context definitions such as

"bizStep": {"@type":"@id"} --> "bizStep": {"@type":"@vocab"}

See https://www.w3.org/TR/json-ld11/#type-coercion