W3C home > Mailing lists > Public > www-tag@w3.org > January 2003

Re: On subsetting XML...

From: Jean-Jacques Moreau <jean-jacques.moreau@crf.canon.fr>
Date: Thu, 16 Jan 2003 13:48:53 +0100
Message-ID: <3E26AA35.1070607@crf.canon.fr>
To: Norman Walsh <Norman.Walsh@Sun.COM>
Cc: www-tag@w3.org

Norman,

I think the SOAP spec[1] is little stronger on receivers 
receiving processing instruction. We really want receivers to 
fault on PIs; but we don't want receivers to be required to 
examine the entire message for the presence of PIs, and fault if 
any, which is what a MUST would require. Hence the opt out clause.

Not that a well-behaved SOAP sender would not include a PI anyway.

Jean-Jacques.

[1] http://www.w3.org/2000/xp/Group/2/06/LC/soap12-part1.html#soapenv

Excerpt from SOAP 1.2, Part 1, editor draft:
"SOAP messages sent by initial SOAP senders MUST NOT contain 
processing instruction information items. SOAP intermediaries 
MUST NOT insert processing instruction information items in SOAP 
messages they relay. SOAP receivers receiving a SOAP message 
containing a processing instruction information item SHOULD 
generate a SOAP fault with the Value of Code set to "env:Sender". 
However, in the case where performance considerations make it 
impractical for an intermediary to detect processing instruction 
information items in a message to be relayed, the intermediary 
MAY leave such processing instruction information items unchanged 
in the relayed message."

Norman Walsh wrote:
> What remains are elements, attributes, namespace declarations,
> comments, processing instructions, and character data. While comments
> and processing instructions might conceivably be removed, they are
> sufficiently useful that we think they should remain. (Although the
> SOAP spec forbids senders from including processing instructions, it
> accepts that receivers might get them, so it's clear that removing
> processing instructions from the subset is not a requirement of the
> SOAP subset.)
Received on Thursday, 16 January 2003 08:15:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:15 GMT