Thanks Pete,
Receipt acknowledged. I'll check all the links, etc. to make sure everything is in order in the next few days - as
long as there are no major defects, and any minor defects are fixed prior to the end of the month you'll be all set.
Regards,
Mary
> -----Original Message-----
> From: Pete Wenzel [mailto:]
> Sent: Friday, July 13, 2007 8:33 PM
> To:
> Cc: Ian Jones; ; Mary McRae
> Subject: OASIS Standard Submission Package for ebXML
> Messaging Services v3.0: Part 1, Core Features
>
> 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/apps/org/workgroup/ebxml-msg/ballot.
> php?id=1335
>
> a. Links to the approved Committee Specification:
> Specification text:
>
> http://www.oasis-open.org/committees/download.php/24618/ebms_c
> ore-3.0-spec-cs-02.pdf
>
> http://www.oasis-open.org/committees/download.php/24617/ebms_c
> ore-3.0-spec-cs-02_html.zip
> Schema:
>
> http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/core/ebms-heade
> r-3_0-200704.xsd
>
> b. Editable version of the specification:
>
> http://www.oasis-open.org/committees/download.php/24616/ebms_c
> ore-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 (to be
> provided by Chair when available).
>
> 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:
> http://www.oasis-open.org/archives/ebxml-msg/200706/msg00001.html
> http://www.oasis-open.org/archives/ebxml-msg/200706/msg00003.html
> 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
> 02 May 2007 through 17 May 2007
> 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 (to be provided
> by Chair when available).]
>
> 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/apps/org/workgroup/ebxml-msg/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.
>
> --Pete
> Pete Wenzel <>
> Join the Open ESB Community <http://open-esb.org/>
