Added by Kamola Khusnutdinova, last edited by Kamola Khusnutdinova on Jun 28, 2012  (view change) show comment

Labels

 

Table of Content

1. Project purpose

The project's purpose is to define a consistent and timely way to address and resolve issues of gaps, overlaps, and counterproductive standardization efforts through: • Description of a coordinated framework, fostering an integrated work program to meet stakeholder needs in administration, commerce and trade • Description of a collaboration process, involving business processes and supporting data that facilitate the open electronic interchange of structured data

Version: 1.0

2. Project scope

The Project scope is the following:

a. The identification of technical specifications and standards that are being
maintained, developed or given consideration in work programmes and strategies
that respond to stakeholder requirements for the open interchange of structured
data in support of administration, commerce and trade. This may include work
from Standards Development Organizations (SDO) other than ISO and UNECE.
b. Identifying relationships and dependencies between the above specifications and
standards.
c. The identification and definition of what is missing under “a” in order to provide a
complete technical framework.
d. Recommendations concerning ways forward, such as the division of labor to avoid
duplication of work and to foster coherence in work programmes and strategies.

3. Project deliverables

The project deliverables are:

"Open Data Interchange" Framework Technical Report – A technical report that outlines a
coordinated framework of global standards involving business processes and supporting
data to facilitate the open electronic interchange of structured data in the areas of
administration, commerce, and trade

4. Exit criteria

The Technical Report has completed its stated ODP stages and been approved by the
Project Team for consideration by UN/CEFACT and ISO (and, if appropriate, by UNECE
management and/or its Executive Committee).

5. Project Team membership and required functional expertise

Membership is open to experts with broad knowledge in the area of methodologies and
technologies for the open electronic interchange of structured data.

6. HoD support(required for technical standards, business standards and UNECE recommendations

List at least three Country heads of delegation who support this project, and include their written expression of support using the template in annex IV...

  Country HoD
1    
2    
3    

7. Geographical Focus

The geographical focus is global.

8. Initial contributions

The following contributions are submitted as part of this proposal. It is understood that
these contributions are only for consideration by the Project Team and that other
participants may submit additional contributions in order to ensure that as much
information as possible is obtained from those with expertise and a material interest in the
project. It is also understood that the Project Team may choose to adopt one or more of
these contributions “as is”.

UN/CEFACT strategic documents
• United Nations Centre for Trade Facilitation and Electronic Business
(UN/CEFACT) programme of work 2012 – 2013
• UN/CEFACT Product Strategy (A description of the technical specifications of
UN/CEFACT and how they work together to provide the outputs of
UN/CEFACT)(December 2011)
• UN/CEFACT Technical Framework Supporting eBusiness Standards (August
2010)
• UN/CEFACT eBGT Gap Analyses Report (August 2010)
• UN/CEFACT Standards Development Advisory Team (CSDAT) Findings and
Recommendations (August 2010)
• UN/CEFACT Technical Frameworks Some Strategic Technical Topics and
Alternative Ways Forward (August 2010)

International Standards jointly developed by UN/CEFACT and ISO/TC154
• ISO 6422-1:2010 - Layout key for trade documents — Part 1: Paper-based
documents
• ISO 7372:2005 - Trade data interchange — Trade data elements directory
• ISO 8439:1990 - Forms design — Basic layout
• ISO 8440:1986 - Location of codes in trade documents
• ISO 8601:2004 - Data elements and interchange format — Information
interchange — Representation of dates and times
• ISO 9735:1988 - Electronic data interchange for administration, commerce and
transport (UN/EDIFACT) — Application level syntax rules
• ISO 9735-1:2002 - Electronic data interchange for administration, commerce and
transport (UN/EDIFACT) — Application level syntax rules (Syntax version
number: 4, Syntax release number: 1) — Part 1: Syntax rules common to all parts
• ISO 9735-2:2002 - Electronic data interchange for administration, commerce and
transport (UN/EDIFACT) — Application level syntax rules (Syntax version
number: 4, Syntax release number: 1) — Part 2: Syntax rules specific to batch EDI
• ISO 9735-3:2002 - Electronic data interchange for administration, commerce and
transport (UN/EDIFACT) — Application level syntax rules (Syntax version
number: 4, Syntax release number: 1) — Part 3: Syntax rules specific to
interactive EDI
• ISO 9735-4:2002 - Electronic data interchange for administration, commerce and
transport (UN/EDIFACT) — Application level syntax rules (Syntax version
number: 4, Syntax release number: 1) — Part 4: Syntax and service report
message for batch EDI (message type — CONTRL)
• ISO 9735-5:2002 - Electronic data interchange for administration, commerce and
transport (UN/EDIFACT) — Application level syntax rules (Syntax version
number: 4, Syntax release number: 1) — Part 5: Security rules for batch EDI
(authenticity, integrity and non-repudiation of origin)
• ISO 9735-6:2002 - Electronic data interchange for administration, commerce and
transport (UN/EDIFACT) — Application level syntax rules (Syntax version
number: 4, Syntax release number: 1) — Part 6: Secure authentication and
acknowledgement message (message type – AUTACK)
• ISO 9735-7:2002 - Electronic data interchange for administration, commerce and
transport (UN/EDIFACT) — Application level syntax rules (Syntax version
number: 4, Syntax release number: 1) — Part 7: Security rules for batch EDI
(confidentiality)
• ISO 9735-8:2002 - Electronic data interchange for administration, commerce and
transport (UN/EDIFACT) — Application level syntax rules (Syntax version
number: 4, Syntax release number: 1) — Part 8: Associated data in EDI
• ISO 9735-9:2002 - Electronic data interchange for administration, commerce and
transport (UN/EDIFACT) - Application level syntax rules (Syntax version
number: 4, Syntax release number: 1) — Part 9: Security key and certificate
management message (message type-KEYMAN)
• ISO 9735-10:2002 - Electronic data interchange for administration, commerce and
transport (UN/EDIFACT) — Application level syntax rules (Syntax version
number: 4, Syntax release number: 1) — Part 10: Syntax service directories

Technical Specifications jointly developed by OASIS and ISO/TC 154:
• ISO/TS 15000-1:2004 - Electronic business eXtensible Markup Language
(ebXML) — Part 1: Collaboration protocol profile and agreement specification
(ebCPP)
• ISO/TS 15000-2:2004 - Electronic business eXtensible Markup Language
(ebXML) — Part 2: Message service specification (ebMS)
• ISO/TS 15000-3:2004 - Electronic business eXtensible Markup Language
(ebXML) — Part 3: Registry information model specification (ebRIM)
• ISO/TS 15000-4:2004 - Electronic business eXtensible Markup Language
(ebXML) — Part 4: Registry services specification (ebRS)
Technical Specifications jointly developed by UN/CEFACT and ISO/TC 154:
• ISO/TS 15000-5:2005 - Electronic Business Extensible Markup Language
(ebXML) — Part 5: ebXML Core Components Technical Specification, Version
2.01 (ebCCTS)

Other ISO/TC 154 Technical Specifications:
• ISO/TS 17369:2005 - Statistical data and metadata exchange (SDMX)
• ISO/TS 20625:2002 - Electronic data interchange for administration, commerce
and transport (UN/EDIFACT) — Rules for generation of XML scheme files
(XSD) on the basis of UN/EDI(FACT) implementation guidelines …

9. Resource Requirements

No additional resources are required.

10. Project Leadership

Proposed Project Leader: Tim McGrath - Australia, Klaus-Dieter Naujok - ISO/TC 154
Proposed Editors: Tim McGrath – Australia, Klaus-Dieter Naujok (ISO/TC 154)

[Note to user: Each UN/CEFACT project proposal must specify the name and email address of at least one proposed Project Convener and at least one proposed Editor.]

11. Milestones (repeat per deliverable)

Yes/No ODP Stage Expected Completion Date (YYYY-MM-DD)
Yes Inception 16.04.2012
  Requirements gathering 20.04.2012
  Draft development 01.07.2012
  Public Draft Review (required for Standards and Recommendations) 01.09.2012
Yes Project Exit 01.11.2012
Yes Publication  
  Maintenance