[OASIS Issue Tracker] Updated: (EBXMLMSG-21) @mpc attribute on UserMessage needs editorial fix and clarification

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

     [ http://tools.oasis-open.org/issues/browse/EBXMLMSG-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dale Moberg updated EBXMLMSG-21:
--------------------------------

    Proposal: 
Edit or replace the core language to say something like:
"Unless the UserMessage is in response to a Pull request, the @mpc attribute need not be used. When the UserMessage is in response to a PullRequest and the @mpc attribute is absent, then the message reflects the use of the default MPC.

But when the PullRequest signal used a specific value for the MPC, then the UserMessage MUST have an @mpc attribute, and the value of that attribute must equal 
the MPC URI value that was requested in the PullRequest signal. [Jacques Durand changes here.]

  was:
Edit or replace the core language to say something like:
"Unless the UserMessage is in response to a Pull request, the @mpc attribute is not used. When the UserMessage is in response
to a PullRequest and the @mpc attribute is absent, then the message reflects the use of the default MPC. But when the PullRequest
signal used a specific value for the MPC, then the UserMessage MUST have an @mpc attribute, and the value of that attribute must equal 
the MPC URI value that was requested in the PullRequest signal. 


> @mpc attribute on UserMessage  needs editorial fix and clarification
> --------------------------------------------------------------------
>
>                 Key: EBXMLMSG-21
>                 URL: http://tools.oasis-open.org/issues/browse/EBXMLMSG-21
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Bug
>          Components: AS4 Profile, Core Spec
>            Reporter: Dale Moberg
>            Priority: Minor
>
> ebMS 3 Core Spec section 5.2.2 has a section on the @mpc attribute of eb:Messaging/eb:UserMessage. 
> eb:Messaging/eb:UserMessage/@mpc: This OPTIONAL attribute contains a URI that
> identifies the Message Partition Channel to which the message is assigned. The absence of this
> element indicates the use of the default MPC. When the message is pulled, the value of this
> attribute MUST indicate the MPC requested in the PullRequest message.
> What is meant is conjectured to be that:
> Unless the UserMessage is in response to a Pull request, the attribute is not used. When the UserMessage is in response
> to a PullRequest and the @mpc attribute is absent, then the message reflects the use of the default MPC. But when the PullRequest
> signal used a specific value for the MPC, then the UserMessage must have the @mpc attribute, and the value of that attribute must equal 
> the MPC URI value that was requested in the PullRequest signal. 
> The remark about "OPTIONAL" should be deleted as it is only a schema technicality, and is partly responsible for some confusion. 
> The confusion is interpreting that the @mpc attribute can be omitted when the PullRequest has used a specific value in its @mpc attribute.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira