Canonical Model
other
| Submitted date | Last Update Date | Version | Project Proposal Status | Project Page |
|---|---|---|---|---|
Draft
|
Project Purpose
The project’s purpose is to address the now globally recognised importance of the role of canonical process and data models in facilitating trade. Given UN/CEFACT’s current global recognition as a proven and effective standards developer, the development of such a canonical mode is considered to be UN/CEFACT’s number one opportunity. The project will draw on UN/CEFACT’s sound foundations and current progress to date in the development of such a canonical model and proceed to develop guidelines to assist all working groups engaged in the development of UN/CEFACT standards and recommendations to contribute effectively to the delivery of the required canonical model. What does “canonical” mean? (adj.) Authoritative or standard: conforming to an accepted rule or procedure. When referring to programming, canonical means conforming to well-established patterns or rules. The term is typically used to describe whether or not a programming interface follows the already established standard. The opportunity & the driving forces UN/CEFACT is poised to significantly contribute to: • Blockchain enabled “Trust” applied to the supply chain • Internet enabled “Collaboration” applied to the supply chain “Data Pipeline” • The uptake of process driven as distinct to document driven supply chains as required to gain benefit from blockchain and IoT technologies, and in support of “Event Driven Architectures” based services • Deployment of UN/CEFACT’s Reference Data Model approach To deliver UN/CEFACT must now focus on processes and choreography moving beyond primarily focussing only on message definition.Project Scope
Project Deliverables
Exit Criteria
Project Team Membership and Required Functional Expertise
Head of Delegation Support
Geographical Focus
Initial Contributions
Resource Requirements
Project Leadership
Milestones
DELIVERABLE NAME | Project Inception | Expected Completion Date | Requirements Gathering | Expected Completion Date | Draft Development | Expected Completion Date | Public Review | Expected Completion Date | Project Exit | Expected Completion Date | Publication | Expected Completion Date | Maintenance | Expected Completion Date |
YES | YES | YES | YES | YES | YES | YES | ||||||||
YES | YES | YES | YES | YES | YES | YES | ||||||||
YES | YES | YES | YES | YES | YES | YES |
Project Proposal Files