- From: Susan Lesch <lesch@w3.org>
- Date: Fri, 18 Jan 2002 01:03:27 -0500 (EST)
- To: www-xml-linking-comments@w3.org
Hello, Belated congratulations on your XPointer Candidate Recommendation [1]. > We expect that sufficient feedback to determine its future will have > been received by 4 March 2002. Here are a few minor editorial suggestions to use as you see fit. The questions "Who does this specification address?" and "How do I create an XPointer?" could be answered. For the first question, one or two sentences: This specification is written for software developers who wish to implement XPointer in authoring tools [or whatever]. People who wish to author XPointers by hand will find the grammar in section 4.2 and examples throughout the text. For the second question, I would make 4.2 into section 5.1 (moving everything in 5 up to 6) named "Structure of an XPointer" (if not "How to Create an XPointer" :-). Follow that with the three forms in 5.2, 5.3, 5.4. Under 5 say that what is coming up in 5.1 is "how to author an XPointer." The sentence, "The internal structure of an XPointer is as follows," could be a little more elaborate, possibly a paragraph explaining to an author that by understanding and following the grammar, they can create an XPointer. (Please pardon if I misunderstand.) There are about 10 external links to XPath. I think you have to find a way to let the reader know these aren't local links. There is a pretty well developed example here: http://www.w3.org/2001/06/manual/#linking-within. For XML, you might just say in prose that the EBNF links to the XML 1.0 Recommendation. About 16 of the 82 "</b>"s need to be closed up. They each follow a line break which puts a space character between link text and punctuation. The punctuation ought to immediately follow the link. A few typos: Internet Draft Internet-Draft designatation designation quotatation quotation locatino location WIthin Within In References, http://www.ietf.org/rfc/rfc3023.txt needs ".txt" (the link is 404 not found without it). In References, titles should be links, not the URIs. The last bullet in 9.5 here explains: http://www.w3.org/2001/06/manual/#References. For example: <dt class="label"><a name="rfc2119"></a>IETF RFC 2119</dt><dd><cite>RFC 2119: Key words for use in RFCs to Indicate Requirement Levels</cite>. Internet Engineering Task Force, 1997. (See <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>.)</dd> becomes: <dt class="label"><a name="rfc2119"></a>IETF RFC 2119</dt><dd><cite><a href="http://www.ietf.org/rfc/rfc2119.txt">RFC 2119: Key words for use in RFCs to Indicate Requirement Levels</a></cite>. Internet Engineering Task Force, 1997. This RFC is on-line at http://www.ietf.org/rfc/rfc2119.txt.</dd> [1] http://www.w3.org/TR/2001/CR-xptr-20010911/ 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 Monday, 21 January 2002 12:53:02 UTC