- From: Elliotte Rusty Harold <elharo@metalab.unc.edu>
- Date: Tue, 3 Sep 2002 22:02:11 -0400
- To: xml-dist-app@w3.org
At 6:25 PM -0400 9/3/02, noah_mendelsohn@us.ibm.com wrote: >Let's say the server responds with a SOAP message that contains a >mustUnderstand='true' header that changes the semantic of the response >(I.e. changes it relative to the meaning without the header.) For >example, maybe it specifies that all currency is in Mexican Pesos (ah, >remember that example Andrew?) If the stylesheet doesn't pick up that >essential fact, it might format numbers as French Francs or US Dollars. Yes, but the same server is providing both the stylesheet and the SOAP response. Or at the very least it's choosing the appropriate stylesheet to go with the response. In essence, it's giving the client the code it needs to display the document. Here then the onus is one the server, which is a SOAP processor, to handle this accordingly and either provide a Peso stylesheet or a stylesheet that does check which currency is in use. Will mistakes be made? Yes, just as they will be with allegedly SOAP aware clients. Experience shows the specs will not be implemented perfectly all the time, no matter how we arrange it, neither on the client side or the server side. I suppose it's probably somewhat more likely that the theoretical SOAP aware clients will handle mustUnderstand properly. However, I also think it will be easier to deploy some of this stuff if PIs are allowed. There are trade-offs either way, and no solution is perfect. > Similarly, if the response >was a SOAP fault, would we expect that to include a stylesheet PI that >would help the XForm processor to do the right thing? Yes, we would. >In short: SOAP messages are intended to be processed by SOAP-conforming >software agents. Not always. Some processes that deal with them may not be SOAP processes. For instance, in writing about SOAP, I might well choose to use an XInclude or some other that loads up a SOAP response from a server and inserts it as an example into my book or slide. Not everyone uses data in the most common or the intended way, and they're not necessarily wrong for doing so if the processes they apply are useful to them. -- +-----------------------+------------------------+-------------------+ | Elliotte Rusty Harold | elharo@metalab.unc.edu | Writer/Programmer | +-----------------------+------------------------+-------------------+ | XML in a Nutshell, 2nd Edition (O'Reilly, 2002) | | http://www.cafeconleche.org/books/xian2/ | | http://www.amazon.com/exec/obidos/ISBN%3D0596002920/cafeaulaitA/ | +----------------------------------+---------------------------------+ | Read Cafe au Lait for Java News: http://www.cafeaulait.org/ | | Read Cafe con Leche for XML News: http://www.cafeconleche.org/ | +----------------------------------+---------------------------------+
Received on Tuesday, 3 September 2002 22:10:49 UTC