Hi Folks, I wanted to draw our collective attention to this specification because it is, while directed to business rather than government, a competitor to the DE. I don't feel that it is likely to be used for emergency communications, but it may well marginalize the DE for only emergency communications. We might want to ask ourselves if we would like to see the DE used for wider communications. I'm sorry I don't have the time to get into this in more depth, but we're pursuing our own work. See ya, metaphorically, in tomorrow's TC meeting. Cheers, Rex -------- Forwarded Message -------- Subject: [members] Correction: Invitation to comment on Exchange Header Envelope (XHE) V1.0 - ends May 29th Date: Mon, 30 Apr 2018 12:15:17 -0400 From: Chet Ensign <
chet.ensign@oasis-open.org> To:
tc-announce@lists.oasis-open.org ,
members@lists.oasis-open.org ,
bdxr@lists.oasis-open.org ,
bdxr-comment@lists.oasis-open.org My apologies. Friday's email announcement of the comment period for Exchange Header Envelop (XHE) V1.0 had incorrect links to the HTML and PDF versions of the specification documents. The correct links are: HTML:
http://docs.oasis-open.org/bdxr/xhe/v1.0/csprd01/xhe-v1.0-csprd01-oasis.html and
http://docs.oasis-open.org/bdxr/xhe/v1.0/csprd01/xhe-v1.0-csprd01-oasis.pdf Best regards, /chet On Fri, Apr 27, 2018 at 4:50 PM, Chet Ensign <
chet.ensign@oasis-open.org > wrote: OASIS members and other interested parties, OASIS and the OASIS Business Document Exchange (BDXR) TC [1] are pleased to announce that Exchange Header Envelope (XHE) Version 1.0 is now available for public review and comment. The Exchange Header Envelope (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. XHE, a specification developed jointly by UN/CEFACT and OASIS, is 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 [BDE]. The documents and related files are available here: Exchange Header Envelope (XHE) Version 1.0 Committee Specification Public Review Draft 01 23 April 2018 Editable source (Authoritative):
http://docs.oasis-open.org/ bdxr/xhe/v1.0/csprd01/xhe-v1. 0-csprd01.xml HTML:
http://docs.oasis-open.org/ bdxr/xhe/v1.0/csprd01/xhe-v1. 0-csprd01.html PDF:
http://docs.oasis-open.org/ bdxr/xhe/v1.0/csprd01/xhe-v1. 0-csprd01.pdf Document models of information bundles:
http://docs.oasis-open.org/ bdxr/xhe/v1.0/csprd01/mod Annotated XSD schemas:
http://docs.oasis-open.org/ bdxr/xhe/v1.0/csprd01/xsd Runtime XSD schemas:
http://docs.oasis-open.org/ bdxr/xhe/v1.0/csprd01/xsdr For your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files. You can download the ZIP file at:
http://docs.oasis-open.org/ bdxr/xhe/v1.0/csprd01/xhe-v1. 0-csprd01.zip How to Provide Feedback OASIS and the BDXR TC value your feedback. We solicit input from developers, users and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work. The public review starts 30 April 2018 at 00:00 UTC and ends 29 May 2018 at 23:59 UTC. Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC's Send A Comment page (
https://www.oasis-open.org/ committees/comments/index.php? wg_abbrev=bhxr ). Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
https://lists.oasis-open.org/ archives/bhxr-comment/ All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review, we call your attention to the OASIS IPR Policy [2] applicable especially [3] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member's patent, copyright, trademark and license rights that read on an approved OASIS specification. OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC's work. Additional information about the specification and the <tc shortname> TC can be found at the TC's public home page:
https://www.oasis-open.org/ committees/ <tc abbr>/ ========== Additional references: [1] OASIS Business Document Exchange (BDXR) TC
https://www.oasis-open.org/ committees/bdxr/ [2]
http://www.oasis-open.org/who/ intellectualproperty.php [3]
http://www.oasis-open.org/ committees/bdxr/ipr.php
https://www.oasis-open.org/ policies-guidelines/ipr#Non- Assertion-Mode Non-Assertion Mode -- /chet ---------------- Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society
http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 -- /chet ---------------- Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society
http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 Virus-free.
www.avast.com