Upon request Document Routing SHOULD be able to provide to the sender the proof of delivery from the receiver.
Upon request Document Routing SHOULD be able to provide to the sender the acknowledgment of the e-Document information by the receiver.
The sender MAY associate routing information with the e-Document so that the delivery system may route the documents to the right destination.
The routing envelope MAY contain sender/receiver's contact information.
The routing envelope MAY contain information about the document: version, type,etc.
The SBDH SHOULD include the optional Manifest group for non-XML payload because e-Document Container is a non-XML file.
Include routing information
Add the information needed for routing the document
Routing information is added
|Embed the Container||Embed the eDocument container into the business envelope||Container is embeded|
|Include additional metadata||Include metadata that will be used for document processing||Metadata included|
Figure 1 Routing envelope application view
Figure 2 Routing envelope information view
ICI – National Institute for Research and Development in Informatics
Klaus Vilstrup Pedersen
Routing Envelope ABB is included.
Burçin Bozkurt GÜNAY
Added List of Tables, List of figures, Glossary, Function, Use case, Profiling Document Routing, SBDH integration with e-Delivery, SBDH example, AS4 Header and SBDH Comparison, Interoperability level, Requirements, Functional Requirements, Application View, Technology View, Specification, Implementation Guidelines.
Review and update Document Routing
|0.5||10.03.2015||Update ABB name, SBDH example, SBDH data elements, SBDH use with MIME part issue.||Carmen Rotună|
|0.6||04.05.2015||Updated Generic requirements, Related ABBs section and ABB Capability Realization||Carmen Rotună|