- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 30 Mar 2006 13:32:34 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3061 Summary: inconsistent treatment of the absence of declarations in Section 4 of the XQuery Rec. Product: XPath / XQuery / XSLT Version: Candidate Recommendation Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: XQuery AssignedTo: chamberl@almaden.ibm.com ReportedBy: pichler@dbai.tuwien.ac.at QAContact: public-qt-comments@w3.org CC: pichler@dbai.tuwien.ac.at In my eyes, the preferred formulation for the behavior in case of the absence of some kind of declaration is the one given e.g. in Section 4.3 (Boundary Space Declaration). Here it says: "A boundary-space declaration sets... overriding any implementation-defined default". In Sections 4.5 (Base URI Declaration) and 4.8 (Empty Order Declaration), it is not specified what happens if no such declaration is given. I would expect an analogous sentence as the one in Section 4.3, i.e. "A ... declaration sets... overriding any implementation-defined default". In Section 4.13 (Default Namespace Declaration) it is not specified what happens if no default element/type namespace declaration is given. Again, I would expect an analogous sentence as the one in Section 4.3, i.e. "A ... declaration sets... overriding any implementation-defined default". In Section 4.9 (Copy-Namespaces Declaration) it says "A ... declaration sets... overwriting any implementation-defined default". Changing "overwriting" to "overriding" would be preferable. In Section 4.13 (Default Namespace Declaration) the behavior in case of the absence of a default function namespace declaration is specified as follows: "If no default function namespace declaration is present, the default function namespace is the namespace of XPath/XQuery functions, http://www.w3.org/2005/xpath-functions (however, this default may be overridden by an implementation.)" This formulation is confusing. If the implementation may override this default, then the default function namespace is simply "implementation-defined". Again, the analogous formulation as in Section 4.3 is preferable.
Received on Thursday, 30 March 2006 13:32:43 UTC