OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: about Receipts

Taking into account last week comments, this mail supersedes my previous one (2/21):
- in the XML sample in 5.2: incorrect structure:
the element eb:MessageInfo should be under eb:UserMessage
- in 5.2.1: update the "bundling " section as follows:

When the eb:Messaging element contains several children elements, i.e. several message units (either User message units or Signal message units) this is called message unit bundling. The bundling patterns supported by this specification are governed by the following rules:

·        The eb:Messaging element contains no more than one eb:UserMessage element.

·        The eb:Messaging element with or without an eb:UserMessage child element may contain more than one eb:SignalMessage element, but not two signal messages of the same type (e.g. two eb:SignalMessage elements containing each an eb:PullRequest element may not be present).

This is a non-exhaustive list of valid bundling cases:

<keep same list, possibly replace in (d) the error signal message with a receipt signal message, for illustration>

<the "note" could be removed>

- in 5.2.2:
after "TheOPTIONAL element is named after  a Signal message." add:
"Three types of Signal messages are specified in this document: Pull signal (eb:PullRequest), Error signal (eb:Error) and Receipt signal (eb:Receipt)."
- In 5.2.4:
second bullet: replace comment with: "This REQUIRED element defines the nature of the ebMS signal. There is only one eb:[SignalName] child element when SignalName=PullRequest or SignalName=Receipt. There may be several children elements when SignalName=Error."
- create and add description of:


- in 7.12.2: replace Acknowledgment Message with Receipt signal, update appropriately.
- in PMode Appendix:
PMode[1].Security.SendReceipt: the Boolean value of this parameter indicates whether a receipt (Receipt ebMS signal) containing a signed digest of the message must be sent back.
PMode[1].Security.SendReceipt.ReplyPattern: this parameter indicates whether the Receipt signal is to be sent as a callback (value “callback”), or synchronously in the back-channel response (value “response”). If not present, any pattern can be used.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]