Head/Envelope Document Exchange Project

other

Submitted dateLast Update DateVersionProject Proposal StatusProject Page
 
 
 

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

 

 

Project 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

 

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
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 
  • YES
  • NO
 

Project Proposal Files