[OASIS Issue Tracker] (EBXMLMSG-63) D.3.3 PMode[1].BusinessInfo.PayloadProfile[], part cardinality

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

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

Sander Fieten commented on EBXMLMSG-63:
---------------------------------------

This assumes the MSH can correctly identify the payload to apply the profile to. See my comment on issue #62: https://issues.oasis-open.org/browse/EBXMLMSG-62?focusedCommentId=52574&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-52574

> D.3.3 PMode[1].BusinessInfo.PayloadProfile[],  part cardinality
> ---------------------------------------------------------------
>
>                 Key: EBXMLMSG-63
>                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-63
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Improvement
>          Components: Core Spec
>            Reporter: Pim van der Eijk
>
> "A payload part is a data structure that consists of five properties [..] and a Boolean value indicating whether the part is expected or optional, within the User message."
> This supports optional parts,  but not parts occurring more than once.



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