UN/CEFACT Public Information

Space shortcuts

Page tree

Versions Compared

Old Version 19

changes.mady.by.user Lance Thompson

Saved on

compared with

New Version 20

changes.mady.by.user Lance Thompson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Head/Envelope Document Exchange Project

other

Linktoparent

Submitted dateLast Update DateVersionProject Proposal StatusProject Page
Date Picker
defaultClick to set the submissions date
idsubmitted_date
requiredtrue
 
Date Picker
defaultClick to set the latest update date
idlatest_updated_date
 
Text Field
defaultClick to set the version number
idversion_number
requiredtrue
 
SP Page Status
hidetrue
width25%

Comment

Insert here a link to the project page using the brackets [   ]

 

 

Project Purpose

Text Area
default<click here to edit>
idproject_purpose
The Standard Business Document Header, SBDH, was developed by UN/CEFACT in 2004 to facilitate internal routing and management of EDI and other business document files, primarily in applications where documents are being exchanged directly between two systems.
The Business Document Envelope, BDE, was developed by OASIS in 2015 to facilitate routing of business document files across networks with multiple gateways (also known as 4-cornered architectures).
Business document headers and envelopes provide a standardized semantic layer enabling business applications and document exchange gateways to determine logical routing and addressing information for processing the exchange of business documents between multiple parties.
A document header works by adding additional standardized document headers to an existing document, whereas a document envelope separates the semantic information from the document and carries the document within it as a payload.
Some of the principal functional differences between an envelope and a header are that the envelope may carry in it more than one payload at a time, and it can maintain its content confidential while being transported over a network with multiple gateways.
The two specifications, although using different technical approaches, address to a large extent the same application area. This risks increasing the cost in global document exchange by forcing users to apply different software for different business partners.

Project Scope

Text Area
default<click here to edit>
idproject_scope
The project will explore if a joint technical specification can be developed that will outline:
     •	a single Header/Envelope Technical Specification
     •	where a header technology and where envelope technology would be applied
     •	the relationship with CCL and CCTS [spell out]
     •	how it could be used with, and how it would be agnostic to transport protocols, including AS2, ebMS and web services (including AS4)
     •	how it would be agnostic to payload content
     •	the implications on the current user base including migration guidance, if applicable

A proof of concept based on a draft of the deliverables outlined in chapter 3 should be carried out by a minimum of three independent implementations, demonstrating interoperability.
Out of Scope: The project will not include the use of newer exchange technologies and environments, such as cloud computing, APIs and mobile devices, except to prove being agnostic to transport technologies in general. If required, this will be set up as a separate project.

Project Deliverables

Text Area
default<click here to edit>
idproject_deliverables
Option 1: Upon assessing that a joint technical specification can be developed, deliverables from this project would include:
     •	A technical specification based on the current version of SBDH and BDE 
     •	Proof of concept reports / Statements of Use
     •	Migration guidelines
Option 2: Upon assessing that a joint technical specification cannot or does not need to be developed, the deliverable would be a technical report.

Exit Criteria

Text Area
default<click here to edit>
idexit_criteria
Option 1: Upon assessing that a joint technical specification can be developed, deliverables from this project would include:
     •	A technical specification based on the current version of SBDH and BDE 
     •	Proof of concept reports / Statements of Use
     •	Migration guidelines
Option 2: Upon assessing that a joint technical specification cannot or does not need to be developed, the deliverable would be a technical report.

Project Team Membership and Required Functional Expertise

Text Area
default<click here to edit>
idproject_membership
Membership is open to UN/CEFACT Experts  and OASIS BDXR Members with broad knowledge in the area of standardised electronic document exchange.
The project will follow the UN/CEFACT Open Development Process, ODP , and include at least one public review as required by OASIS (https://www.oasis-open.org/policies-guidelines/tc-process).

Head of Delegation Support

Text Area
default<click here to edit>
idhead_of_delegation
Denmark
Japan
Netherlands

Geographical Focus

Text Area
default<click here to edit>
idgeographical_focus
The geographical focus is global.

Initial Contributions

Text Area
default<click here to edit>
idinitial_contributions
The contributions submitted with this proposal include:
     •	UN/CEFACT Standard Business Document Header version 1.3
     •	OASIS Business Document Envelope version 1.1
     •	AS2, ebMS and AS4 Technical Specifications
     •	Core Components Technical Specification version 2.01
     •	Core Components Business Document Assembly version 1.0
     •	OASIS Business Document Naming and Design Rules version 1.0
     •	UN/CEFACT XML Naming and Design Rules, version 2.1

Resource Requirements

Text Area
default<click here to edit>
idresource_requirements
 

Project Leadership

Text Area
default<click here to edit>
idproject_leadership
Project Leader: Anders Grangard
Project Leader: Kenneth Bengtsson

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

Text Field
default<click here to edit>
iddeliverable_name1
Tech.Spec., Report, Migration Guideline
Select2
defaultSELECT
idyesno_odp1
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp1
2016-11-01
Select2
defaultSELECT
idyesno_odp2
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp2
2017-02-01
Select2
defaultSELECT
idyesno_odp3
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp3
2017-05-01
Select2
defaultSELECT
idyesno_odp4
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp4
2017-07-01
Select2
defaultSELECT
idyesno_odp5
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp5
2017-09-15
Select2
defaultSELECT
idyesno_odp6
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp6
2017-10-01
Select2
defaultSELECT
idyesno_odp7
selectedNO
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp7
 
Text Field
default<click here to edit>
iddeliverable_name2
Proof of Concept and Statement Use
Select2
defaultSELECT
idyesno_odp11
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp11
 2016-11-01
Select2
defaultSELECT
idyesno_odp22
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp22
 
Select2
defaultSELECT
idyesno_odp33
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp33
 
Select2
defaultSELECT
idyesno_odp44
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp44
 
Select2
defaultSELECT
idyesno_odp55
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp55
 
Select2
defaultSELECT
idyesno_odp66
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp66
 
Select2
defaultSELECT
idyesno_odp77
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp77
 
Text Field
default<click here to edit>
iddeliverable_name3
 
Select2
defaultSELECT
idyesno_odp111
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp111
 
Select2
defaultSELECT
idyesno_odp222
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp222
 
Select2
defaultSELECT
idyesno_odp333
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp333
 
Select2
defaultSELECT
idyesno_odp444
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp444
 
Select2
defaultSELECT
idyesno_odp555
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp555
 
Select2
defaultSELECT
idyesno_odp666
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp666
 
Select2
defaultSELECT
idyesno_odp777
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp777
 

Project Proposal Files

Attachments
oldfalse

© United Nations Economic Commission for Europe | Trade Division | UN/CEFACT

 

UNECE Staff members are authorized to login with their network credentials (i.e. login/pwd to access their Desktop computer)


Access to this system is restricted to members of UN/CEFACT Community only : UNECE Staff, UN/CEFACT Bureau, Heads of Delegations, Domain Coordinators and UN/CEFACT Experts. All information contained in or obtained from this system is to be used exclusively for UN/CEFACT official purposes. In proceeding, the user agrees to comply with all UN/CEFACT Policies, Procedures and Terms of Reference and with the UN/CEFACT Code of Conduct.