Message Construction Guideline


Project Details

Project Identifier
Bureau Decision #
#1903058, #2003094; #2006001
Project Proposal Status


Project Page

Message Construction Guideline Project

Supporting VC
Project Lead
HoD Support
Submitted date
Draft Development Completion
Publication Date

Project Purpose

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. Further more,  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).

Project Scope

The guidelines introduce the method to design a XML user message using MA, MBIE and QDT under the rules of CCTS, CCBDA and NDR.

Project Deliverables

The project deliverables are: • Deliverable 1: XML Message design guidelines for CCBDA • Deliverable 2: Publication guidelines for MA, MBIE, QDT • Deliverable 3: RSM guidelines for the message using MBIE and QDT • Deliverable 4: Requirements for amendment to related technical specifications, if any

Exit Criteria

The exit criteria will be: • Exit Criteria for Deliv. 1: The guidelines for XML message implementation based CCBDA approved by the Bureau. • Exit Criteria for Deliv. 2: Publication guidelines for MA, MBIE, QDT approved by the Bureau • Exit Criteria for Deliv. 3: RSM guidelines for the message using MBIE and QDT approved by the Bureau • Exit Criteria for Deliv. 4: List of project proposal(s) to amend related technical specifications recognized by the Bureau, if applicable

Project Team Membership and Required Functional Expertise

Membership is open to UN/CEFACT experts with broad knowledge in the area of: XML message design and related activities In addition, Heads of Delegations may invite technical experts from their constituency to participate in the work. Experts are expected to contribute to the work based solely on their expertise and to comply with the UN/CEFACT Code of Conduct and Ethics and the policy on Intellectual Property Rights.

Geographical Focus

The geographical focus of the project is global.

Initial Contributions

• Core Components Technical Specification – Part 8 of the ebXML Framework, Version 2.01 • Core Components Business Document Assembly Technical Specification, CCBDA, version 1.0 • UN/CEFACT XML Naming and Design Rules for CCTS 2.01 Version 2.1 dated 27 May 2014 • Requirements Specification Mapping (RSM) Documentation Template Guidelines Version 2.0

Resource Requirements

Establishing the necessary CUE pages for the project

Project Proposal Files