- From: <bugzilla@jessica.w3.org>
- Date: Sat, 17 Oct 2015 14:46:45 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29207 Abel Braaksma <abel.braaksma@xs4all.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #3 from Abel Braaksma <abel.braaksma@xs4all.nl> --- (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. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Saturday, 17 October 2015 14:46:47 UTC