OASIS ebXML Messaging Services TC

 View Only

  • 1.  Groups - ebms_core-3.0-spec-wd-18.pdf (ebms_core-3.0-spec-wd-18.pdf) uploaded

    Posted 03-20-2007 22:08 
    The document revision named ebms_core-3.0-spec-wd-18.pdf
(ebms_core-3.0-spec-wd-18.pdf) has been submitted by Pete Wenzel to the
OASIS ebXML Messaging Services TC document repository.  This document is
revision #16 of ebms-3.0-spec-wd-04.pdf.

Document Description:
This is Working Draft 18 of OASIS ebXML Messaging Services
Version 3.0: Part 1, Core Features.

Changes from WD 17:
* 03/13/2007 Edits from Jacques, Sections 5.2.3.3, 2.2.2, I.
* CORE-95, Updated Figure 15.
* CORE-102, Section F.2.6.
* 03/14/2007 Edits from Jacques, Appendix E.
* CORE-105, Updated reference to WSRM CD7.
* CORE-106, Signed Receipt Example, Section 7.9.3.
* CORE-107, Updated schema and schemaLocation URIs.

A "diff" marked version can also be found in the TC's document repository.

View Document Details:
http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/document.php?document_id=23050

Download Document:  
http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/download.php/23050/ebms_core-3.0-spec-wd-18.pdf

Revision:
This document is revision #16 of ebms-3.0-spec-wd-04.pdf.  The document
details page referenced above will show the complete revision history.


PLEASE NOTE:  If the above links do not work for you, your email application
may be breaking the link into two pieces.  You may be able to copy and paste
the entire link address into the address field of your web browser.

-OASIS Open Administration


  • 2.  WD 18 and 2 New Issues

    Posted 03-20-2007 23:21 
    This draft should be a good candidate for the next (hopefully final)
Public Review.  Please review the changes with that in mind, and plan
to vote on CD+PR approval at tomorrow's meeting.

An important note, regarding new issue CORE-107:

The namespace URI we had been using was arbitrarily chosen, and was
not a location (if resolved) that we have access to on the OASIS web
server.  While the namespace need not be resolvable, of course, the
schemaLocation hint should be.  And current best practice dictates
that the namespace URI also be resolvable to a RDDL-annotated index
document, which in turn refers to all relevant specifications and
schemas that describe that namespace.

See


Related Content