[OASIS Issue Tracker] (EBXMLMSG-62) D.3.3 PMode[1].BusinessInfo.PayloadProfile[]

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

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

Sander Fieten commented on EBXMLMSG-62:
---------------------------------------

A more general problem with this parameter is how a MSH can determine to which specific payload the profile applies. This will require that the identifier is given on submission and is also transferred within the message. To ensure interoperability the way to identify a payload, e.g. by adding a specific "PartProperty", should be specified. 

I however doubt if this should be done in the specification itself. This seems something that can be done in usage profiles. This however makes it impossible to define general requirements for a MSH to validate the payloads against the profile. At the moment these requirements do not exist, so this would be no less than currently defined.

Therefor my proposal would be to remove this parameter completely.

> D.3.3 PMode[1].BusinessInfo.PayloadProfile[] 
> ---------------------------------------------
>
>                 Key: EBXMLMSG-62
>                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-62
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Bug
>          Components: Core Spec
>            Reporter: Pim van der Eijk
>
> "A payload part is a data structure that consists of five properties: name (or Content-ID) that is the part identifier"
> Content-ID is set per message,  it cannot be set for a PMode that covers a class of messages.



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