Document:
Multihop examples v0_4.zip (Revision 3)

Draft (A preliminary unapproved sketch, outline, or version.)

Details

Submitted By Mr. Pim van der Eijk on 2009-01-12 12:49 pm UTC

Publication Type

None at this time.

Group / Folder

OASIS ebXML Messaging Services TC / Proposals

Modified by

Not modified.

Copy

This document is not a copy.

Technical Contact

None at this time.

Download Count

38

Download Agreement

None at this time.

Description

v0_4
- Fixed a remaining (wrong) reference to ReceiptAcknowledgment
- Receipt references first UserMessage by #ID reference not S12 envelope.
- Wrong "cid:" prefix in MIME part Content-id value removed
- Digests for UserMessage and MIME part should now in fact be correct values:
-- http://www.w3.org/2001/10/xml-exc-c14n#" applied to eb3:UserMessage to calculate digest
-- http://docs.oasis-open.org/wss/oasis-wss-SwAProfile-1.1#Attachment-Content-Signature-Transform" applied to business document in MIME attachment to calculate digest
- There were two issues #9 in Running Issues, renumbered ..


v0_3
- Fixed the eb:Receipt with ebBP info
- MIME payload ID should not be the same as ebMS MessageId
- @role="ebms" for PullRequest authorisation
- S12:mustUnderstand="true" added to the eb:Messaging and wsse:Security headers.
- wsa:IsReferenceParameter="true" added to ebint:RoutingInput
- Made some of the spreadsheet Pmode and routing function specifications consistent
- Company URLs now use "example.com"
- Added placeholder suggesting WS-S use (but no details on the WS-S structure)

V0_2 Update:
In scenario A, fixed some errors with the Receipt message
- SignalMessage moved to S12:Header
- Added RefToMessageId.
Added a note on ebBP signals (#12).
In scenario D, removed the @role for the WSSE header.
Added a note on reliable/non-reliable Pull (#13) as configuration parameter.

//

Set of documents/files related to the multihop draft.

Four scenarios involving various combinations of multihop functionality
(Push, Pull, Receipt signals, WS-ReliableMessaging, Push-Pull combinations, PullRequest forwarding). For each are provided the SOAP XML documents, Pmode parameter sets and "routing function".

"Sample Message Exchange.doc" pastes some of these into the OASIS spec template (for consideration as an annex to the multihop draft).

All of this is based on my reading/interpretation of various specs, so this should be reviewed carefully.

"Running notes.doc" document provides a bunch of comments, issues, potential enhancements/errata to the multihop draft and/or the ebms 3 core spec I came across while working on this.