For semantic interoperability in the field of Trade Facilitation and eBusiness, UN/CEFACT Technical Specifications and Dictionaries should be used more widely in the world.
There are several standard messages published in the UN/CEFACT library (Web site) which are designed to be used widely including general purpose business information entities and code lists.
The other hand, a user’s application used within a trading partner’s needs and can handle a part of information of the standard message. This causes frustration among users especially SMEs, such as;
(1) It needs a large size standard message for the small set of information used in user’s application.
(2) Each user application has to handle a bunch of information defined in the standard message.
(3) A user cannot predict the usable set of information in the standard message received.
Fortunately, we have the technical specification Core Component Business Document Assembly (CCBDA) which enables defining a subset of the standard message particularly through a Reference-Data Model approach. This CCBDA specification has the capability to solve the above issues.
However, there seems to be some difficulties to apply CCBDA specification for implementing restricted messages while keeping interoperability, as follows.
No ful rules for restrictions of MBIE.
No rules for identifier of MA, MBIE.
No construction rules for internal schema used for MBIEs.
No rules for restricting code lists.
No publication rules for MA.
Considering an updated RSM template describing MBIEs;
Considering an updated namespace for MBIEs;
Considering an updated relation with XHE (Exchange Header Envelope) specification;
It is desirable to take careful guidance for message implementations based on CCBDA specification to keep interoperability among EDI users.
This project introduces the guidelines how to define a Message Assembly (MA) constructed with Message Business Information Entities (MBIE) and Qualified Data Type (QDT).