XMLP LC Issue 392: closed

Hugo,

You raised earlier issue 392. The issue contains two parts:

[P1] You asked whether intermediaries are allowed to add/remove 
secondary parts. More generally, you wondered whether there 
should be an equivalent to our well-known processing model, but 
one that would apply to secondary parts, not header blocks.

[P2] You wondered whether some URI schemes are better adapted to 
insertion, deletion, and modification of secondary parts.

The XMLP WG considers that this issue should be addressed by the 
AF specification and has decided to incorporate the text below.

Regarding part 2, the WG considers that particular URI schemes 
should not be prescribed or rejected by the abstract AF 
specification, but by concrete attachment specifications only.

Please let us know asap if you disagree with the WG's decision.

Jean-Jacques.


[New section in AF document]

Intermediary Considerations
===========================
A SOAP message can travel through zero or more SOAP
intermediaries. This sections describes the requirements posed on
SOAP intermediaries supporting this specification.

A SOAP intermediary MUST be able to access any secondary part.

A forwarding SOAP intermediary MUST in general forward every
secondary parts contained in the incoming SOAP message, except
when the specification for a processed SOAP header block calls 
for the part to be removed or changed. An active SOAP 
intermediary MAY change or remove any secondary part even in the 
absence of such a mandate.

A SOAP intermediary MAY insert new secondary parts.

The integrity of references (i.e. URIs) to secondary parts MUST 
be maintained accross SOAP intermediaries. That is, a URI which 
resolves to a secondary part in an inbound SOAP message MUST 
continue to resolve to that part in the outbound message, unless 
that part was removed by the SOAP intermediary.

Received on Wednesday, 30 October 2002 11:09:10 UTC