- From: Paul Grosso <paul@paulgrosso.name>
- Date: Mon, 30 Sep 2013 11:42:09 -0500
- To: core <public-xml-core-wg@w3.org>
Here is was I propose sending to the IETF for our WG comment on 3023bis. Comments welcome from all and REQUIRED from Henry. I plan to send in our comment at the end of this week's telcon. Henry, please remind me of the mechanics for submitting our comment. paul --------------------------------- Dear ???, The W3C XML Core Working Group is pleased to see the recent progress made toward a replacement for RFC 3023. We have reviewed the 2013 July 8 draft at https://datatracker.ietf.org/doc/draft-ietf-appsawg-xml-mediatypes/ and would like to support its transition to RFC [is that the right thing???] Below we make several fairly minor technical suggestions; see also http://lists.w3.org/Archives/Public/public-xml-core-wg/2013Sep/0010 and http://lists.w3.org/Archives/Public/public-xml-core-wg/2013Sep/0019 for a fuller list of editorial comments. 1. 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. 2. 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)". 3. 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." 4. 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." Paul Grosso, co-chair for the W3C XML Core Working Group
Received on Monday, 30 September 2013 16:42:37 UTC