- From: Jean-Jacques Moreau <moreau@crf.canon.fr>
- Date: Wed, 27 Nov 2002 09:28:35 +0100
- To: Henrik Frystyk Nielsen <henrikn@microsoft.com>
- CC: David Fallside <fallside@us.ibm.com>, Noah Mendelsohn <noah_mendelsohn@us.ibm.com>, XMLP Public <xml-dist-app@w3.org>, Herve Ruellan <ruellan@crf.canon.fr>
After reflexion, that's fine. Jean-Jacques. Henrik Frystyk Nielsen wrote: > > Jean-Jacques, > > I am generally fine with this but would it be ok to say > > A SOAP module realizes *zero* or more SOAP features > > I don't think we prevent a SOAP module to be written without calling out > any particular SOAP features (i.e. specifying them according to the > rules in the SOAP 1.2 spec)? > > Henrik Frystyk Nielsen > mailto:henrikn@microsoft.com > > >>-----Original Message----- >>From: Jean-Jacques Moreau [mailto:moreau@crf.canon.fr] >>Sent: Tuesday, November 26, 2002 02:47 >>To: Henrik Frystyk Nielsen >>Cc: David Fallside; Noah Mendelsohn; XMLP Public; Herve Ruellan >> >>Suggestions for B): >> >><revised> >>The term 'SOAP module' refers to the specification of the >>syntax and semantics of one or more SOAP header blocks. *A >>SOAP module realizes one or more SOAP features.* A module >>specification adheres to the following rules. It: >></revised> >> >>and C): >> >><revised> >>A SOAP Module is a specification that contains the combined >>syntax and semantics of SOAP header blocks specified according >>to the rules in 3.2 SOAP Modules. *A SOAP module realizes one >>or more SOAP features.* </revised> >> >>I can live with D). >> >>I am fine with your other changes. > >
Received on Wednesday, 27 November 2002 03:29:17 UTC