[OASIS Issue Tracker] (EBXMLMSG-105) *.Initiator.* and *.Responder.* in PMode

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/EBXMLMSG-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=66991#comment-66991 ] 

Sander Fieten commented on EBXMLMSG-105:
----------------------------------------

I agree that these text are not very clear and will probably confuse readers and should therefore be changed. 

My problem is that the combined text on these parameters is incomplete rather then incorrect since it only makes a statement on the mapping of these parameters to the eb:From element for user messages **initiating** the MEP and not for the other cases. I therefore think it would be better to reformulate the text on the mapping of both parameters (this is text after the sentence starting with "Qualifies the party..." to: 
"Any user message sent by / sent to the [initiator/responder] party must have its eb:Messaging/eb:UserMessage/eb:PartyInfo/eb:From respectively its eb:Messaging/eb:UserMessage/eb:PartyInfo/eb:To element contain the same PartyId elements as the PartyId elements defined in this parameter."
This will cover all MEP bindings, both for one and two-way MEPs.

> *.Initiator.* and *.Responder.* in PMode
> ----------------------------------------
>
>                 Key: EBXMLMSG-105
>                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-105
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Bug
>          Components: Core Spec
>            Reporter: Pim van der Eijk
>
> Section D.3.1 defines the PMode.Initiator.Party and PMode.Responder.Party and references back to section 2.2.3, where "Initiator" and "Responder" are said to apply to "channel-bound MEP".   
> As explained in 2.2.5, in Push channels, it is the Sender that initiates. 
> According to 2.2.6, in Pull channels it is the Receiver that initiates.
> The definition of PMode.Iniator.Party in section D.3.1 says that "a user message initiating an MEP instance under this P-Mode must have its eb:Messaging/eb:UserMessage/eb:PartyInfo/eb:From element contain the same PartyId elements as the PartyId elements defined in this parameter." However, the "From" element identifies the Sender, so this can only be true for Push bindings.  
> Similarly, the definition of PMode.Responder.Party says that "Any user message sent to the responder must have its eb:Messaging/eb:UserMessage/eb:PartyInfo/eb:To element contain the same PartyId elements as the PartyId elements defined in this parameter." 
> However, the "To" element identifies the Receiver, so this can also only be true for Push bindings.  
> For Two Way MEPs,  it should be clear that these parameters relate to the first leg.  
>  



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)