Thank you Philip, and my apologies for not having responded to your other comments yet. Iâve made a note to put your comments on the agenda for our meeting next week. We very much appreciate your contributions!!
From: <email@example.com> on behalf of Philip Helger <firstname.lastname@example.org>
Date: Tuesday, May 28, 2019 at 9:11 AM
To: "email@example.com" <firstname.lastname@example.org>
Subject: Re: [bdxr-comment] Exchange Header Envelope (XHE) Version 1.0 from BDXR TC approved as a Committee Specification
just wanted to let you know, that I stumbled upon a few things while checking the document, and of course I will let you know:
* Chapter 1.1.3, 5th row: should be "... an XHE..." ('n' was missing)
* Chapter 2.1, Figure 1: the image seems to be outdated, as it is not in line with the XSD
* * Envelope / PayloadIncludedIndicator (not in XSD)
* * Header / TestIndicator (not in XSD)
* * Payload / EncryptionHashValue (called InstanceHashValue in XSD)
* * Payload / InstanceEncryptionMethodText (not in XSD)
* Chapter 2.5: as an extension proposal for the next version, I suggest to add an optional "Party name" - I assume this would greatly simplify debugging
* Chapter 2.9.2: also as an extension proposal, I suggest to make the hashing algorithm customizable, in case SHA-256 will be deemed insecure in the future
* Chapter 2.10, 2nd paragraph, 2nd row: the comma before the dot is imho unnecessary.
Am 13.05.2019 um 16:23 schrieb Paul Knight:
OASIS Members and other interested parties,
OASIS is pleased to announce that Exchange Header Envelope (XHE) Version 1.0 from the OASIS Business Document Exchange (BDXR) TC  has been approved as an OASIS Committee Specification.
The Exchange Header Envelope (XHE) has been developed jointly by UN/CEFACT and OASIS as the successor to the UN/CEFACT Standard Business Document Header (SBDH) version 1.3 [SBDH] and the OASIS Business Document Envelope (BDE) Version 1.1
XHE defines a business-oriented artefact either referencing (as a header) or containing (as an envelope) a payload of one or more business documents or other artefacts with supplemental semantic information about the collection of payloads
as a whole. An exchange header envelope describes contextual information important to the sender and receiver about the payloads, without having to modify the payloads in any fashion. This vocabulary is modeled using the UN/CEFACT Core Component Technical
Specification Version 2.01.
This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.
The prose specifications and related files are available here:
Exchange Header Envelope (XHE) Version 1.0
Committee Specification 01
Editable source (Authoritative):
For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:
Members of the BDXR TC  approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process . The vote to approve as a Committee Specification passed , and the
document is now available online in the OASIS Library as referenced above.
Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.
========== Additional references:
 OASIS Business Document Exchange (BDXR) TC
* 30-day public review, 27 April 2018:
- Comment resolution log:
OASIS - Advancing open standards for the information society