[ebxml-cppa] Issue 224

[Tony Weida <rweida@hotmail.com>]

Issue 224 was raised by Hima as "Why not multiple PartyIds for each PartyInfo?" [under the CPA element].  Indeed, the XSD allows multiple PartyId elements.

 

At the F2F, Dale entered the note: "Messaging allows multiple partyIds, so we will follow them ..."

 

Therefore, I've revised the relevant paragraph as follows.

 

BEFORE: "In the CPA, there SHALL be one PartyId element under each PartyInfo element. The value of this element is the same as the value of the PartyId element in the ebXML Message Service specification[ebMS] or similar messaging service specification. One PartyId element SHALL be used within a To or From Header element of an ebXML Message."

 

AFTER: "In the CPA, there SHALL be one or more PartyId elements under each PartyInfo element. The values of these elements are the same as the values of the PartyId elements in the ebXML Message Service specification[ebMS] or similar messaging service specification. These PartyId elements SHALL be used within a To or From Header element of an ebXML Message."

 

This interpretation takes the position that in case multiple party IDs have been enumerated in the CPA, the parties intended for all of them to be used in the message.  Comments?

 

Tony