9509 2010-04-13 20:23:51 +0000 [XQ31ReqUC] Default element namespace applies to both input and output. 2014-05-20 16:56:18 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Requirements for Future Versions Working drafts PC Windows NT NEW P2 normal --- 1 dlee jim.melton jim.melton jonathan.robie mike public-qt-comments oldest_to_newest 34959 0 dlee 2010-04-13 20:23:51 +0000 Default element namespaces (4.14 "Default Namespace Declaration") apply to both input (XPath) namespaces and output (generated elements). A very common use case for XQuery is to generate XML documents to a different namespace then the input. For example, converting an XML document to an XHTML document. The use of namespace prefixes in XPath expressions and element generation is a very difficult task for beginning and often even experienced users to correctly use. To aid in the common case of reading from one namespace and outputting to another, this difficulty should be addressed in order to encourage wider use of XQuery. It is unnecessarily tedious to require namespace prefixes to perform this common operation. Namespaces are difficult enough that XQuery 1.1 should assist in this common case. XSLT 2.0 solves this problem with the introduction of the "xsl:xpath-default-namespace". XQuery 1.1 should provide a similar feature where the input (xpath) default namespace can differ from the output (generated element) namespaces. 47109 1 jim.melton 2011-04-04 01:12:31 +0000 David, although there is interest in the XML Query WG to address this opportunity, we have concluded that we do not have the resources to add this feature in the XQuery 3.0 timeframe. We will reconsider this opportunity during development of the mythical next generation of XQuery following 3.0. Consequently, I am marking this bug as a possible requirement for a possible future version of the language. Thanks for making the suggestion! 47111 2 mike 2011-04-04 08:18:38 +0000 While I'm disappointed that the WG decided not to fix this well known usability problem, it might help to point out that there's a bit of a workaround available in XQuery 3.0 - you can use the expression "":local to refer to elements in no namespace, regardless of the namespace context. 106465 3 jonathan.robie 2014-05-20 16:47:56 +0000 Assigning to future requirements per Working Group decision (https://lists.w3.org/Archives/Member/w3c-xsl-query/2012Oct/0087.html). 106469 4 jonathan.robie 2014-05-20 16:50:26 +0000 Assigning to future requirements per Working Group decision (https://lists.w3.org/Archives/Member/w3c-xsl-query/2012Oct/0087.html). 106478 5 jonathan.robie 2014-05-20 16:56:18 +0000 Assigning to future requirements per Working Group decision (https://lists.w3.org/Archives/Member/w3c-xsl-query/2012Oct/0087.html).