- From: Susan Lesch <lesch@w3.org>
- Date: Sun, 4 Feb 2001 01:21:01 -0800
- To: www-xml-infoset-comments@w3.org
These are just minor comments for your Last Call Working Draft [1]. Globally, I would capitalize Infoset, or not if you prefer. See the mismatch for example in list items 3 and 4 in section 3. Also globally, "white space" in prose is two words. (See http://www.w3.org/TR/REC-xml#sec-white-space.) Until the reader gets to section 2, the square brackets around [namespace name] and [base URI] are unexplained; (they looked like missing links to references). Could par. 1 in section 2 which explains this be moved up to the Introduction? The two notes at the end of Synthetic Infosets could be in the same place, maybe all three paragraphs under one heading. Is there any precedent for marking up properties [thus]? Some XML specifications use square brackets around or before definitions. Have you tried monospace for contrast instead, like <code><strong>thus</strong></code> or <code><em>thus</em></code>? In 1. par. 5, "favour" -> "favor" In 1. last par., "Nodes" -> "nodes" In 1. Namespaces, "[Namespaces]" needs an anchor. In Appendix A, for W3C publications, I would add "World Wide Web Consortium" or "W3C." (That would be everything except ISO/IEC 10646 and RFC 2119.) In Appendix C, list item 6, is http://www.message.net/ a typo for http://www.message.example/? Also regarding Appendix C, W3C recommends using example.com, example.org, and example.net which IANA reserves. See RFC 2606 section 3 at http://www.ietf.org/rfc/rfc2606.txt. Though I don't think they are needed here, if you want evocative domain names, you might try machine names like doc.example.org and message.example.org. In Appendix E, third comment, "XML Infoset Specification" -> "XML Infoset specification" [1] http://www.w3.org/TR/2001/WD-xml-infoset-20010202/ Best wishes for your project, -- Susan Lesch - mailto:lesch@w3.org tel:+1.858.483.4819 World Wide Web Consortium (W3C) - http://www.w3.org/
Received on Sunday, 4 February 2001 04:21:13 UTC