- From: Max Froumentin <mf@w3.org>
- Date: Tue, 03 Dec 2002 12:04:58 +0100
- To: www-ws@w3.org
Hugo Haas <hugo@w3.org> writes: > Note that one way to see the problem is that a SOAP processor could do > an HTTP request indicating that it wants an application/soap+xml > reply, whereas a browser could make a similar request indicating that > it wants an application/xhtml+xml reply, using content negotiation, in > which case the problem vanishes. I think that this is better than the stylesheet PI. Allowing that particular PI in SOAP would make it possible to use any PI, which is clearly not what the WG wants. We're going back to the original point: the stylesheet PI is not a particularly good way to associate style with content (although it is convenient), and I don't think we should mandate SOAP to allow it just for the particular case of displaying messages in a browser, especially if it can be achieved by another mechanism, such as the one you describe. Now if people think that allowing PIs in SOAP is acceptable, then it is a different story. Cheers, Max.
Received on Tuesday, 3 December 2002 06:05:29 UTC