Should CoO structured model be based on UN or WCO models or both?

[onthebreeze]

This ticket is to facilitate an open discussion on the question of whether the data element needs of a Certificate of Origin should be met using a structured schema based on the WCO data model or the UN/CEFACT Reference Data Models - or both.

[arpentnoir]

Not sure if you were getting at overall structure or semantics of individual elements, but I'll comment on semantics.

Assuming that CoO is a JSON-LD document with context referencing some vocabulary, and framing this question as "which vocabulary do we use, UN or WCO?" then it's easy enough to create a JSON-LD context which references multiple vocabularies, this is an example: https://json-ld.org/contexts/person
but that is just binding each element to a single definition, so in that respect it might be a case of picking the most relevant vocabulary to bind to for each element.

if both UN and WCO have vocabularies which contain definitions of the same concept, then sounds like we need the idea of a synonym - this thing defined by UN is the same as this thing defined by WCO...

[monkeypants]

If we have a json-ld document that covers is harmonised against both vocabularies, then the next question is should we send two messages about the same object:

• ({coo_id}, 'UNCEFACT.Trade.CertificateOfOrigin.created', {document_id})
• ({coo_id}, 'WTO.CertificateOfOrigin.created', {document_id})