29207 2015-10-16 11:48:03 +0000 [XQ31] reserved namespaces needs updating 2015-10-20 16:22:31 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3.1 Candidate Recommendation PC Windows NT RESOLVED WONTFIX P2 normal --- 1 abel.braaksma jonathan.robie public-qt-comments oldest_to_newest 123738 0 abel.braaksma 2015-10-16 11:48:03 +0000 The XQ31 spec defines a list of reserved namespaces. This list is repeated in several places: * http://www.w3.org/XML/1998/namespace * http://www.w3.org/2001/XMLSchema * http://www.w3.org/2001/XMLSchema-instance * http://www.w3.org/2005/xpath-functions * http://www.w3.org/2005/xpath-functions/math * http://www.w3.org/2012/xquery Sometimes they are called "reserved" (in para 2.5.5.7 and 4.15), sometimes not (in 4.18 Function Declarations they are not called "reserved", nor in the error description for XQST0045). I think the following are candidates to be included in this list: * http://www.w3.org/2005/xpath-functions/map * http://www.w3.org/2005/xpath-functions/array * http://www.w3.org/2005/xqt-errors * http://www.w3.org/2000/xmlns/ * http://www.w3.org/2010/xslt-xquery-serialization And possibly, with the introduction of fn:transform() in F&O 3.1, we should consider adding the XSLT namespace as well: * http://www.w3.org/1999/XSL/Transform In addition, if it is not too late considering the current CR status, to group these together and use a TERMDEF, to prevent the repetition? 123747 1 jonathan.robie 2015-10-16 21:00:05 +0000 This was fixed in passing when I addressed the same comment in Bug 29170. 123750 2 abel.braaksma 2015-10-17 13:55:57 +0000 Can you elaborate a little bit? The referred to bug seems to be about the text of the error. Was a decision made on all these namespaces, or did you (or the WG) decide to include a part of them? Was the XSL namespace added for reasons of interaction with fn:transform, or was it left unreserved? 123751 3 abel.braaksma 2015-10-17 14:46:45 +0000 (disregard my prev. comment, I think I have now seen the internal draft update, which reorganizes this a bit). I see that the list has been upgraded to the following: * http://www.w3.org/XML/1998/namespace * http://www.w3.org/2001/XMLSchema * http://www.w3.org/2001/XMLSchema-instance * http://www.w3.org/2005/xpath-functions * http://www.w3.org/2005/xpath-functions/math * http://www.w3.org/2012/xquery * http://www.w3.org/2005/xpath-functions/array * http://www.w3.org/2005/xpath-functions/map That leaves: * http://www.w3.org/2005/xqt-errors * http://www.w3.org/2000/xmlns/ * http://www.w3.org/2010/xslt-xquery-serialization * http://www.w3.org/1999/XSL/Transform Perhaps the xmlns namespace does not fit in this list because it is already covered by other errors, or it could be included for completion. I am not sure if all the others deserve a "reserved" status. If I compare it with XSLT, the Errors namespace is reserved there (and of course the XSLT namespace). The Serialization namespace is up for debate. I see no harm in either including or excluding them, but we should make an informed decision. If the policy has been to reserve namespaces that have special meaning in (aspects of) the specs, then I think all of them should be included. 123809 4 jonathan.robie 2015-10-20 16:22:31 +0000 (In reply to Abel Braaksma from comment #3) > That leaves: > > * http://www.w3.org/2005/xqt-errors > * http://www.w3.org/2000/xmlns/ > * http://www.w3.org/2010/xslt-xquery-serialization > * http://www.w3.org/1999/XSL/Transform This would introduce an incompatibility with XQuery 3.0, and we don't want to do that.