Linkage of DCSA terminology to CEFACT (or other) vocabularies

[nissimsan]

You’re creating some terms of your own, like ´cargoItems´. You’re free to do that and in many cases I would personally agree that it makes the data easier to understand. But when you post for feedback in CEFACT context, it's kinda is against the whole point.
The solution for this is JSON-LD: keep the attribute names as you have agreed, but link into https://service.unece.org/trade/uncefact/vocabulary/unece/ (or elsewhere) for concise, formal and machine interpretable definitions.
It's the perfect non-compromize - everyone's happy! Very much in the spirit of edi3.org.

[raisoman]

@nissimsan good input again.

In my opinion, we should align as much as possible to existing definitions, i.e. directly adopt the existing names rather than invent synonyms, while we can.

In the UNECE vocabulary above I have identified the following terms that we should consider adopting:

totalConsignmentValueAmount
totalItemQuantity
totalQuantity
utilizedTransportEquipment
countryName
cityName
streetName
Party Name (in our IM) should be Name (on the Party entity)
Our seal Source should be sealingPartyRoleSealingPartyRoleCode (or sealingPartyRole)

The question then is: what do we do when there is no equivalent term in the existing vocabularies?

[HenrikHL]

along the lines of cityName and streetName you can add countryName

[nissimsan]

Fantastic! I certainly won't argue against that. :) Your list changes will bring it closer to what was designed in the CEFACT "Covid IFTM**" project last year; will certainly smoothen interoperability.

When there are no equivalents, you should propose adoption into the CEFACT model (as we also done back in the IFTM project days). Curious: could you share that list too? Surely that would seed a good discussion.

[cmsdroff]

@raisoman feel free to raise those missing data elements when no equivalent with me and we can decide how to progress, this is useful input and we can influence the MMT Model with your changes, I can assist with this and we can document the process for DCSA future requirements, happy to help! drop me a message or raise a ticket and assign to me whatever fits best for you!

Agree with @nissimsan lets put them out there!