[OASIS Issue Tracker] Updated: (EBXMLMSG-24) Section 3.5 of the AS4 Profile Sub Channel Clarification

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

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

Theo Kramer updated EBXMLMSG-24:
--------------------------------

    Proposal: 
The MPC sub-channel feature for AS4 is not only intended for the multi-hop context, as it may also be used for partitioning of messages on an MPC where different pulling partners may access only the messages in the specified sub-channel. Ie. messages on an MPC may be partitioned for different pulling partners based on the sub-channel. With that I propose that the intro paragraph for 3.5 be reworded as follows

The sub-channel feature as defined in section 2 of ebMS V3 Part 2 ( [ebMS3ADV]) MAY be supported by an AS4 MSH either for partitioning messages for different pulling partners and/or for routing purposes in a multi-hop context. If used in a multi-hop context, the sub-channel feature applies to a sending AS4 MSH in the same way as it applies to the edge intermediary as described in ebMS V3 Part 2.

  was:
The MPC sub-channel feature for AS4 is not only intended for the multi-hop context, as it may also be used for partitioning of messages on an MPC where different pulling partners may access only the messages in the specified sub-channel. Ie. messages on an MPC may be partitioned for different pulling partners based on the sub-channel. With that I propose that the intro paragraph for 3.5 reads as follows

The sub-channel feature as defined in section 2 of ebMS V3 Part 2 ( [ebMS3ADV]) MAY be supported by an AS4 MSH either for partitioning messages for different pulling partners and/or for routing purposes in a multi-hop context. If used in a multi-hop context, the sub-channel feature applies to a sending AS4 MSH in the same way as it applies to the edge intermediary as described in ebMS V3 Part 2.


> Section 3.5 of the AS4 Profile Sub Channel Clarification 
> ---------------------------------------------------------
>
>                 Key: EBXMLMSG-24
>                 URL: http://tools.oasis-open.org/issues/browse/EBXMLMSG-24
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Improvement
>          Components: AS4 Profile
>            Reporter: Theo Kramer
>            Priority: Minor
>
> Section 3.5 reads as follows
> Optionally, the sub-channel feature defined in section 2 of ebMS V3 Part 2 ( [ebMS3ADV]) for intermedi-
> aries in a multi-hop context, MAY be supported by an AS4 MSH. On the Sending side of an AS4 ex-
> change, this feature will apply to a sending AS4 MSH in the same way it applies to the edge intermediary
> in ebMS V3 Part 2.

-- 
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