[OASIS Issue Tracker] (EBXMLMSG-83) Referencing XML documents in SOAP body

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

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

Sander Fieten commented on EBXMLMSG-83:
---------------------------------------

I prefer a solution where no reference is used at all to indicate that the content of the SOAP Body is the payload. Because the payload XML document should of course be a well formed document it requires that the SOAP Body has just one child element. 

My proposal is therefore to replace the sentence in 5.2.2.13 starting with "The absence..." with the following text:
"If no href attribute is included in the eb:PartInfo element the SOAP Body of the message MUST contain a single child element and this element MUST be considered as the payload referenced by this eb:PartInfo element."  

> Referencing XML documents in SOAP body
> --------------------------------------
>
>                 Key: EBXMLMSG-83
>                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-83
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Bug
>          Components: Core Spec
>            Reporter: Pim van der Eijk
>
> “The PartInfo element is used to reference a MIME attachment, an XML element within the SOAP Body, or another resource which may be obtained
> by resolving a URL, according to the value of the href attribute”
> This suggests referencing to substructures in the SOAP body, whereas we only want to reference the complete document in the SOAP body.
> As that body may not have an ID (and its schema may not even allow one), the document is to be referenced using an ID on the Body element.



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