Re: [ebxml-msg] Referencing XML payload in SOAP Body

[Pim van der Eijk <pvde@sonnenglanz.net>]

The developer sends me the following comment:

Then the definition of partInfo needs to be corrected in the spec.

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

I will file a JIRA issue.


On 06/22/2015 11:38 AM, Theo Kramer wrote:

I would agree with this. 

Also according to WS-I Basic Profile 2.0 section 3.2.1 SOAP Envelope Structure rule 9981, an ENVELOPE MUST have exactly zero or one child elements of the soap12:Body element.

So allowing references to sub-nodes in the body could open interpretation up that more than one payload is permitted in the soap body. This potentially leading to interop issues.
 
On 22 Jun 2015, at 10:23 , Pim van der Eijk <pvde@sonnenglanz.net> wrote:

Hi,

The example in AS4:
http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/os/AS4-profile-v1.0-os.html#__RefHeading__58427_149522555 

Has a reference to the XML payload in the SOAP Body by referencing its wsu:Id

<eb:PayloadInfo>
                    <eb:PartInfo href=""/>
</eb:PayloadInfo>

<S12:Body wsu:Id="_f8aa8b55-b31c-4364-94d0-3615ca65aa40">
        <CrossIndustryInvoice xmlns="urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:2">
            <!-- content omitted -->
        </CrossIndustryInvoice>

An implementer asks if that attribute should not be on the business document (CrossIndustryInvoice) instead,

Now in many cases the schema does not have such an ID,  and anyway we don't want the MSH to change the XML payload.

Do we agree that a Payload reference to an ID the SOAP Body is to be interpreted as referencing the payload in the Body, rather than the sub-node, as the example suggests?

(I am aware that the "href" can be omitted and then it implicitly references the payload in the body,  but this is about situations where there is an explicit reference).

There is a similar issue https://issues.oasis-open.org/browse/EBXMLMSG-39 but it is about signing.

Kind Regards,

Pim