- From: <bugzilla@jessica.w3.org>
- Date: Tue, 25 Mar 2014 22:30:48 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25149 Bug ID: 25149 Summary: Normative references to unstable documents must be removed before publication Product: XPath / XQuery / XSLT Version: Proposed Recommendation Hardware: PC OS: Linux Status: NEW Severity: blocker Priority: P2 Component: Serialization 3.0 Assignee: cmsmcq@blackmesatech.com Reporter: liam@w3.org QA Contact: public-qt-comments@w3.org The Serialization 3.0 PR contains normative references to HTML 5 POLYGLOT XSLT 3 In order to be published as a Rec we mustn't be in a situation where a change to an unstable spec like POLYGLOT (likely to have a 2nd last call soon) would break XQuery or XPath implementations. I don't think we are actually in such a situation, but some editorial work is needed. I suggest (1) for POLYGLOT, this should become a non-normative reference; the one place where it's used in normative text seems to be about namespaces, and copying the appropriate paragraph out of the polyglot draft would cure that. (2) for HTML 5, we refer to things like the list of void elements, which is now out of date (there are new ones). However, the new ones can have end tags, so we're *probably* OK on HTML 5; referring to specific sections of that huge spec might help. See http://www.w3.org/html/wg/tests-cr-exit/index.html - the items with green check marks are considered stable. (3) XSLT 3 references can probably say "XSLT 2 or later"?? In cases where an XQuery alternative is given, the XSLT 3 reference could be non-normative. The document (and hence XQuery 3, XQueryX 3, XPath 3 etc which refer nomatively to this spec) can't advance to Recommendation until this is resolved. It probably also applies to the 3.1 spec. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 25 March 2014 22:30:50 UTC