- From: Martin Gudgin <marting@develop.com>
- Date: Fri, 17 Aug 2001 09:29:14 +0100
- To: "Henrik Frystyk Nielsen" <henrikn@microsoft.com>, <xml-dist-app@w3.org>
----- Original Message ----- From: "Henrik Frystyk Nielsen" <henrikn@microsoft.com> To: "Martin Gudgin" <marting@develop.com>; <xml-dist-app@w3.org> Sent: Friday, August 17, 2001 1:16 AM Subject: RE: Proposed replacement text for final paragraph in Section 3 > Great - maybe clarify "specification" as in > > "elements and attributes defined in this specification" > > with > > "element and attribute information items defined in this > specification with a namespace identifier of > 'http://www.w3.org/2001/06/soap-envelope', 'http://...' > etc." OK, I can see that, it's more explicit. > > Given the restriction to these parts, it might be good to have a note > saying that SOAP has nothing to say about data not defined by SOAP: > > "Note that it is outside the scope of this specification > whether information items not defined by SOAP does or > does not require schema processing." Yeah, I wondered about that as I was writing up the text. I can see adding such a clause, again, it's more explicit. What do other people think? > > Btw, only "REQUIRED" and not "REQUIRES" in upper-case in listed as a > reserved term in section 1.2 [1]. Therefore it might be better to say: > "It is REQUIRED that..." >>A SOAP message MUST NOT impose any XML schema processing >>(assessment and >>validation) requirement on the part of any receiving SOAP node >>with respect to the elements and attributes defined in this >>specification. Therefore, SOAP REQUIRES that all attribute >>information items defined in this specification be carried in >>the serialized SOAP envelope or that the defaults defined by >>this specification apply. OK, I'll fix that. Cheers Gudge
Received on Friday, 17 August 2001 04:29:27 UTC