- From: Hugo Haas <hugo@w3.org>
- Date: Mon, 10 Sep 2001 14:49:55 -0700
- To: xmlp-comments@w3.org
Here are a few very minor things that I noted:
Section 2.5[1]:
2. Process SOAP blocks targeted at the SOAP node, generating SOAP
faults (see 4.4 SOAP Fault if necessary. A SOAP node MUST process
^^
missing parenthesis
Section 2[2]:
SOAP messages are fundamentally one-way transmissions from a SOAP
sender to a SOAP receiver, but as illustrated above, SOAP messages are
often combined to implement patterns such as request/response.
"as illustrated above": there is no request/response above anymore.
Section 4.1.1[3]:
The serialization rules defined by SOAP (see [1]SOAP Encoding are
identified by the URI "http://www.w3.org/2001/06/soap-encoding". SOAP
^^
missing parenthesis
Section 6.1[4] and also section 8.1 of part 2[5]:
6.1 Normative References
[..]
2
XML Protocol Comments Archive (See
http://lists.w3.org/Archives/Public/xmlp-comments/.)
3
XML Protocol Discussion Archive (See
http://lists.w3.org/Archives/Public/xml-dist-app/.)
4
XML Protocol Charter (See
http://www.w3.org/2000/09/XML-Protocol-Charter.)
I wonder if such references (particularly 2 and 3) can be normative.
We can't expect people to read all the mailing list archives. I
think that those should be move to the non-normative section. I
think that it is the same for the charter.
I was also wondering why the reference to the XML Information Set
specification was really an informative reference[6].
1. http://www.w3.org/2000/xp/Group/1/08/29/soap12-part1.html#procsoapmsgs
2. http://www.w3.org/2000/xp/Group/1/08/29/soap12-part1.html#msgexchngmdl
3. http://www.w3.org/2000/xp/Group/1/08/29/soap12-part1.html#soapencattr
4. http://www.w3.org/2000/xp/Group/1/08/29/soap12-part1.html#N9F3
5. http://www.w3.org/2000/xp/Group/1/08/29/soap12-part2.html#N931
6. http://www.w3.org/2000/xp/Group/1/08/29/soap12-part1.html#NA68
--
Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/ - tel:+1-617-452-2092
Received on Monday, 10 September 2001 17:49:57 UTC