[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: OASIS ebXML Messaging Services Version 3.0: Part 1, Core Features Submitted for OASIS Standard
OASIS Members: The OASIS ebXML Messaging Services Technical Committee has submitted the following specification set, which is an approved Committee Specification, to be considered as an OASIS Standard: OASIS ebXML Messaging Services Version 3.0: Part 1, Core Features The text of the TC submission is appended. You now have until 15 August to familiarize yourself with the submission and provide input to your organization's voting representative. In addition, the TC is providing another document to facilitate familiarization (this document is not part of the official package and is not up for consideration for OASIS Standard vote): OASIS ebXML Messaging Services 3.0 Conformance Profiles http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/prof/cd02/ebms-3.0-confprofiles-cd-02.pdf http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/prof/cd02/ebms-3.0-confprofiles-cd-02.html http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/prof/cd02/ebms-3.0-confprofiles-cd-02.odt On 16 August, a Call For Vote will be issued to all Voting Representatives of OASIS member organizations. They will have until the last day of August, inclusive, to cast their ballots on whether this Committee Specification should be approved as an OASIS Standard or not. Members who wish to discuss this ballot may do so through member-discuss@lists.oasis-open.org. In accordance with the OASIS Technical Committee Process, this Committee Specification has already completed the necessary 60-day public review period as noted in the submission below. The normative TC Process for approval of Committee Specifications as OASIS Standards is found at http://www.oasis-open.org/committees/process.php#3.4 Any statements related to the IPR of this specification are posted at: http://www.oasis-open.org/committees/ebxml-msg/ipr.php Your participation in the review and balloting process is greatly appreciated. Mary Mary P McRae Manager of TC Administration, OASIS email: mary.mcrae@oasis-open.org phone: 603.232.9090 ----------------------- On behalf of the Chair and Members of the ebXML Messaging Services TC, I present the submission package for OASIS ebXML Messaging Services Version 3.0: Part 1, Core Features, for approval as an OASIS Standard. A record of the decision to approve the submission of this specification may be found at http://www.oasis-open.org/committees/ballot.php?id=1335 a. Links to the approved Committee Specification: Specification text: PDF: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/core/cs02/ebms_core-3.0-spec-cs-02.pdf HTML: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/core/cs02/ebms_core-3.0-spec-cs-02.html Schema: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/core/cs02/ebms-header-3_0-200704.xsd b. Editable version of the specification: Open Document Format: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/core/cs02/ebms_core-3.0-spec-cs-02.odt c. Certification by the TC that schema and XML instances are well formed, and expressions are valid: See Resolution recorded in 11 July 2007 TC Meeting Minutes: http://www.oasis-open.org/committees/download.php/24646/MessagingTC071107.htm d. A clear English-language summary of the specification (from the specification's Abstract): This specification defines a communications-protocol neutral method for exchanging electronic business messages. It defines specific Web Services-based enveloping constructs supporting reliable, secure delivery of business information. Furthermore, the specification defines a flexible enveloping technique, permitting messages to contain payloads of any format type. This versatility ensures legacy electronic business systems employing traditional syntaxes (i.e. UN/EDIFACT, ASC X12, or HL7) can leverage the advantages of the ebXML infrastructure along with users of emerging technologies. e. A statement regarding the relationship of this specification to similar work of other OASIS TCs or other standards developing organizations: This specification is the first major revision of ebXML Message Services since the OASIS ebMS 2.0 (April 2002). It continues the use of relevant Web Services specifications, including SOAP 1.1 and SOAP with Attachments; and also encourages the use of and converge with various Web Services standards that have emerged since the publication of ebMS 2.0, including SOAP 1.2, Web Services Security: SOAP Message Security 1.0 & 1.1, WS-Reliability 1.1, WS- ReliableMessaging 1.1. It is designed to be used either with or without any of the other ebXML components, including ebXML Business Process Specification Schema (BPSS) 2.0.4 and a forthcoming version of ebXML Collaboration Protocol Profile and Agreement (CPP/A). f. Statements of Use have been provided by three OASIS member companies: Fujitsu Computer Systems http://www.oasis-open.org/archives/ebxml-msg/200706/msg00001.html Axway Inc http://www.oasis-open.org/archives/ebxml-msg/200706/msg00003.html NEC Corporation http://www.oasis-open.org/archives/ebxml-msg/200706/msg00004.html g. Two Public Reviews have been held: 12 May 2006 through 11 June 2006 http://lists.oasis-open.org/archives/tc-announce/200605/msg00002.html 02 May 2007 through 17 May 2007 http://lists.oasis-open.org/archives/tc-announce/200705/msg00002.html A record of all issues logged against this specification, along with the disposition of each, can be found here: http://www.oasis-open.org/committees/download.php/24495/ebms-3.0-issues-wd-20.pdf [Note that no substantive changes have been made to the specification since the last Public Review; see Resolution to this effect recorded in 11 July 2007 TC Meeting Minutes noted above.] h. The 2nd Committee Specification ballot concluded on 12 July 2007, and the result was unanimous approval. Results may be found at http://www.oasis-open.org/committees/ballot.php?id=1328 i. This is the first attempt to standardize ebMS version 3.0. j. The Technical Committee's publicly visible comments archive may be found at http://www.oasis-open.org/archives/ebxml-msg-comment/ k. As the CS ballot was unanimous, no Minority Reports have been submitted.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]