local extensions to UN vocabulary

[onthebreeze]

The JSON-LD NDR will specify rules for publishing UN/CEFACT RDMs and Code Lists as JSON-LD vocabularies.

However, it is likely that there will be value in local extensions of the JSON-LD vocabulary after generation from the UN source models. Some typical examples:

• Adding sub-types that are meaningful for industry but have been abstracted out of the UN vocabulary - eg "voyage", "flight", "journey" classes as sub-types of the UN "transportMovement".
• adding attributes such as domain classifications (trade, transport, regulatory, etc) to UN classes and properties
• maybe adding candidate (draft/proposed) classes / properties that meet a user need prior to their formal implementation in the UN CCL/RDM.

Two questions arise from this:

1. should these extensions be in the same namespace? If in the UN namespace then they would need to be incorporated into the UN governance processes, which might defeat the purpose of these extensions. So perhaps edi3.org takes the UN vocabulary in the unece namespace and then adds these extensions in the edi3 namespace?
2. If we do that then what happens when an edi3 extension is used and implemented, but then the UN adopts that change and releases the same thing in the unece namespace?
3. How will we apply incremental updates from UN (each 6 months or so) to an already extended vocabulary?

[Fak3]

adding attributes such as domain classifications (trade, transport, regulatory, etc) to UN classes and properties

If we only use these attributes to render appropriately organized html docs for unece vocabulary, and those attributes are not critical for general public, then it does not matter much how and where we store them.

So perhaps edi3.org takes the UN vocabulary in the unece namespace and then adds these extensions in the edi3 namespace? If we do that then what happens when an edi3 extension is used and implemented, but then the UN adopts that change and releases the same thing in the unece namespace?

edi3 could then mark the term within edi3 anmespace as deprecated, also add a link to the new unece-namespaced term (possibly linked with owl:equivalentClass or owl:equivalentProperty)