Re: PI's and HTTP GET binding

Just my opinion, but the Get binding is not to make SOAP easier to use 
with browsers and other user agents that might benefit from the PI.  The 
binding is specifically there to cause SOAP processing of the response. 
SOAP processing is entirely driven by the element structure of the SOAP 
envelope, and PI's really don't fit with that.  If a PI appears 
immediately before a header entry, should it be taken to modify that 
entry?  Should it be removed from the message along with that entry after 
processing?  etc.  PI's just don't fit into the element/attribute model 
well, and they would be very hard to introduce into the SOAP processing 
model in an organized manner.   It's too bad that PI is the only widely 
deployed mechanism for naming a stylesheet in an instance. Interestingly, 
and its clear why no existing software supports this, it would be 
absolutely coherent to define a SOAP header to indicate the stylesheet. 
You could even put mustUnderstand="false" on it to make sure it didn't 
bother anyone.

------------------------------------------------------------------
Noah Mendelsohn                              Voice: 1-617-693-4036
IBM Corporation                                Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
------------------------------------------------------------------







Simon Fell <simon@zaks.demon.co.uk>
Sent by: xmlp-comments-request@w3.org
07/17/2002 11:35 PM

 
        To:     xmlp-comments@w3.org
        cc:     (bcc: Noah Mendelsohn/Cambridge/IBM)
        Subject:        PI's and HTTP GET binding



Hi,

Now that there's a HTTP GET binding for SOAP, I think it would make
sense to allow PI's, so that the xml-stylesheet PI can be used.

Thanks
Simon
www.pocketsoap.com

Received on Wednesday, 24 July 2002 21:00:04 UTC