Next in thread → Next in month →

[OASIS Issue Tracker] (EBXMLMSG-64) D.3.3 PMode[1].BusinessInfo.PayloadProfile[], schema name

From
OASIS Issues Tracker <>
Date
2014-12-02T22:26:41+00:00
ID
Thread
[OASIS Issue Tracker] (EBXMLMSG-64) D.3.3 PMode[1].BusinessInfo.PayloadProfile[], schema name
[ https://issues.oasis-open.org/browse/EBXMLMSG-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52576#comment-52576 ] 

Sander Fieten commented on EBXMLMSG-64:
---------------------------------------

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[], schema name
> ---------------------------------------------------------
>
>                 Key: EBXMLMSG-64
>                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-64
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Improvement
>          Components: Core Spec
>            Reporter: Pim van der Eijk
>            Priority: Minor
>
> "name of the applicable XML Schema file"
> Instead of "name", should this be URI or namespace?
> Or some combination of namespaces and root element?



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
Next in thread → Next in month →