Procedure for CCTS 2.01 & CCBDA 1.0 & NDR 2.1 Artefacts Publication Project

 

Domain

Project Identifier
p1032
Bureau Decision # 
Project Proposal

Project Proposal: Procedure for CCTS 2.01 & CCBDA 1.0 & NDR 2.1 Artefacts Publication Project 

Supporting VC 
Project Lead
HoD SupportN/A
Status

Draft Development
Exit Date


1. CHOOSE A "PAGE TITLE" FOR YOUR ODP PROJECT AND FILL THE FIRST ROW.

2 SUBSTITUTE THE ABOVE "NEW ODP PROJECT" WITH YOUR TITLE.

3 CLICK ON THE SAVE BUTTON AT THE RIGHT BOTTOM.

 

Project Identifier (PID)
Update Of
Project Proposal
Project Status
p1032
Procedure for CCTS 3 & NDR 3 artefacts publication (p0107)Project Proposal: Procedure for CCTS 2.01 & CCBDA 1.0 & NDR 2.1 Artefacts Publication Project

 

  • Initiated
  • In development
  • Completed

back to

Interested in this project

 

 


Project Deliverables 

 

Search in this project

Project Leadership

Role

Member

 

  • Project Chair
  • Project Lead
  • Co-Project Lead
  • Lead Editor
  • Co-Lead Editor
  • Editor
Rolf,r.wessel
  • Project Chair
  • Project Lead
  • Co-Project Lead
  • Lead Editor
  • Co-Lead Editor
  • Editor
gerhard.heemskerk@kpnmail.nl

Heads of Delegation

N/A
N/A
N/A

Projects Activities

Project Updates


Executive Summary

Project purpose

The purpose of the project is to define the procedures for the creation and publication of CCTS 2.01, CCBDA 1.0 and NDR 2.1 Business Standards.
Reason for version 2: http://www.unece.org/cefact/codesfortrade/ccts_index.html

Project scope

The ODP process of developing a Business Standard from inception to publication for CCTS 2 and NDR 2 artefacts includes but is not limited to:

 - Harmonization of core components
 - Verification of libraries and other artefacts
 - Definition of the publication bundle
 - Publication schedules

The project will define all new procedures and artefacts required to develop a Business Standard using the CCL Library and the CCTS 2.01, CCBDA 1.0 and NDR 2.1 Technical Specifications.

The project will be conducted by undertaking a proof of concept Business Standard development. The CII semantic content in the CCL will be reused by defining CCBDA Message Assembly restrictions. A public review version of the resultant proof of concept Cross Industry Invoice (CII) will be published. The proof of concept example used will therefore be semantically equal to published CII D15B which will increase the usefulness of the project results for comparison purposes.


Project Overview