Pim,
thanks for working on this.
Team,
please take some time to look at this as we need to discuss this -
we have deferred this on the last call to give people chance to look at
and consider these examples.
Ian
Original Message-----
From: pvde@sonnenglanz.net [mailto:pvde@sonnenglanz.net]
Sent: 20 January 2009 08:21
To: ebxml-msg@lists.oasis-open.org
Subject: [ebxml-msg] Groups - Multihop examples v0_5.zip uploaded
Fixed some small errors.
Some extra comments in running notes.
-- Mr. Pim van der Eijk
The document revision named Multihop examples v0_5.zip has been
submitted by Mr. Pim van der Eijk to the OASIS ebXML Messaging Services
TC document repository. This document is revision #4 of Multihop
examples.zip.
Document Description:
v0_5
- New comment #16 wsa:To and wsa:ReplyTo
- New comment #17 RoutingInput or RoutingInfo
- New comment #18 Text on wsa:EndpointReference
- Fixed a missing ReferencePa
rameter wrapper in the ReplyTo in the CS message in scenario B.
- Missing wsse declaration in UserMessage in B
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-Conte
nt-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.
View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=30753
Download Document:
http://www.oasis-open.org/committees/download.php/30753/Multihop%20examp
les%20v0_5.zip
Revision:
This document is revision #4 of Multihop examples.zip. 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