- From: Doug Davis <dug@us.ibm.com>
- Date: Tue, 11 Dec 2001 06:48:25 -0500
- To: "Andrew Layman" <mail@strongbrains.com>
- Cc: xml-dist-app@w3.org
I never read it to mean that you couldn't do other things with the xml - but if you want to deserialize it then yes you must use those encoding rules - but of course we can't control what people 'really' do, can we. :-) -Dug "Andrew Layman" <andrew@strongbrains.com>@w3.org on 12/10/2001 10:55:01 PM Please respond to "Andrew Layman" <mail@strongbrains.com> Sent by: xmlp-comments-request@w3.org To: xmlp-comments@w3.org cc: Subject: Re: issue #159 resolution addendum Perhaps I am reading this out of context, but the quote sounds peculiar to me. The soap-enc:encodingStyle attribute says that the writer asserts that IF you follow the rules you will end up a certain graph; but that is not the same as forbidding all readers to use other processes and end up with something else. Does this resolution say that it is improper to apply XSL to elements within the scope of a soap-enc:encodingStyle attribute? To render the characters in an emacs display without ever deserializing? etc. Andrew Layman http://strongbrains.com -- Resources for Self-Education ----- Original Message ----- From: "Jacek Kopecky" <jacek@systinet.com> To: "XMLP Comments" <xmlp-comments@w3.org> Cc: <dug@us.ibm.com> Sent: Monday, December 10, 2001 11:09 AM Subject: issue #159 resolution addendum Hello all. 8-) I apologize but only after rereading the minutes of the f2f meeting (not public yet, but soon) I've realized that resolution to #159 contains the following, too: "Change 'can' to 'MUST' in section 4.1.1 of part 1 of the spec: the >>serialization rules that can be used to deserialize the SOAP message<< should be changed to >>serialization rules that MUST be used to deserialize the SOAP message<<." Best regards, Jacek Kopecky Senior Architect, Systinet (formerly Idoox) http://www.systinet.com/
Received on Tuesday, 11 December 2001 06:48:33 UTC