- From: Henry S. Thompson <ht@inf.ed.ac.uk>
- Date: Tue, 22 Oct 2013 16:03:09 +0100
- To: John Cowan <cowan@mercury.ccil.org>
- Cc: Paul Grosso <paul@paulgrosso.name>, public-xml-core-wg@w3.org
John Cowan writes:
> Here's what I've found:
>
> 1) In Section 3, "In particular, for transports other than HTTP [RFC2616]
> or HTTPS (which uses a MIME-like mechanism). the UTF-16 family, UCS-4,
> and UTF-32 are not allowed" has a misplaced period; it should be at the
> end and the existing period should be a comma.
> "allowed".
Overtaken.
> 2) In Section 3, the sentence beginning "Thus, although all XML
> processors" says "(except for HTTP)", but should say "(except for HTTP,
> HTTPS, and other protocols if base64 transport encoding is in use)".
> This is spelled out later in the document.
Overtaken.
> 3) In Section 3, "Furthermore, such media types may allow UTF-8 or UTF-16
> only and prohibit other charsets" has a misplaced "only" which makes
> it unclear; it should read "Furthermore, such media types may forbid
> charsets other than UTF-8 (or other than UTF-8 or UTF-16)"
Reworded.
> 4) In Section 3.1, for "editting" read "editing".
Done (silently)
> 5) In Section 3.6 there is another problematic "only" and a bad comma: for
> "The charset parameter MUST only be used, when the charset is reliably
> known and agrees with the in-band XML encoding declaration" read "The
> charset parameter MUST NOT be used if the charset is not reliably known.
> If it is used, it MUST agree with the XML encoding declaration."
Overtaken -- this entire section significantly rewritten, see ...-04 to be
released shortly, please review that section again.
> 6) In Section 4, the sentence "Similarly, when converting from another
> encoding into "utf-16", the BOM MUST be added after conversion is
> complete" is incorrect; it should read, "Similarly, when converting
> from another encoding into "utf-16", either an appropriate encoding
> declaration MUST be added or modified, or a BOM MUST be added."
See my reply to Paul G. on this.
> 7) In Section 11, for "recipients of XML MIME entities may be a risk"
> read "recipients of XML MIME entities may be at risk".
Done.
> In the randomly chosen .sig below, for "report" read "RFC". :-)
Heh.
> --
> Clear? Huh! Why a four-year-old child John Cowan
> could understand this report. Run out cowan@ccil.org
> and find me a four-year-old child. I http://www.ccil.org/~cowan
> can't make head or tail out of it.
> --Rufus T. Firefly on government reports
Thanks!
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged spam]
Received on Tuesday, 22 October 2013 15:04:09 UTC