- From: <bugzilla@jessica.w3.org>
- Date: Fri, 13 Feb 2015 21:36:38 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28018 Bug ID: 28018 Summary: Normative vs. Non-Normative Text (Examples) Product: XPath / XQuery / XSLT Version: Candidate Recommendation Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: Data Model 3.1 Assignee: ndw@nwalsh.com Reporter: patrick@durusau.net QA Contact: public-qt-comments@w3.org See Bug 6374, which has the language of the current draft: **** In this document, examples and material labeled as "Note" are provided for explanatory purposes and are not normative. **** But note that "exammple" occurs 100 times in this document, often as "for example" and isn't contained in a note. So the draft violates its own terms for presentation to the reader. For example: 2.3 Node Identity "No two distinct integers, for example, have the same value ; every instance of the value “5” as an integer is identical to every other instance of the value “5” as an integer.)" 2.6 Namespace Names "Namespace names, whatever form they take, are treated as character strings and compared for equality using codepoint-by-codepoint comparison, subject only to whitespace normalization if they appear in a context (for example, within an attribute value) where this is appropriate." (inside a definition) Still under 2.6 " For example, the namespace part of an expanded QName is defined to be a value of type xs:anyURI." (normative or non-normative?) I won't bore you with citing all the other "for example" cases. Examples should be separated and numbered (including sub-numbering if it has parts). How else are implementers going to refer to examples in the text? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 13 February 2015 21:36:40 UTC