search

uncefact / spec-jsonld

Exposing the UN/CEFACT vocabulary as web semantics
https://service.unece.org/trade/uncefact/vocabulary/uncefact/
13 stars 5 forks source link

Update unece @context file with term definitions from code lists #136

Closed nissimsan closed 1 year ago

nissimsan commented 1 year ago
image

These RDF classes are to be defined too:

image
jmcanterafonseca-iota commented 1 year ago

@nissimsan the code lists can be huge ... and the size of the LD Context can increase a lot ...

could they be hosted in their own LD Context and then imported only if they are really used. In EPCIS we have only one LD Context that also contains the CBV Code Lists (enumerations in schema.org jargon) , but in EPCIS CBV code lists are not so long ... in any case we generate a single LD Context from multiple sources, see https://github.com/gs1/EPCIS/tree/master/JSON-LD-Context

nissimsan commented 1 year ago

@jmcanterafonseca-iota , are you suggesting that we combine the contexts into a single file? They are huge already.

Context granularity is a trade off, there's no right and wrong. I sort of think that we've landed it in a pretty good middle ground with the two (pretty big) contexts.

nissimsan commented 1 year ago

We should probably just close this. What I am suggesting sounds like a bad idea.

nissimsan commented 1 year ago

We did this: https://vocabulary.uncefact.org/unlocode-vocab-context.jsonld