- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 03 May 2007 06:24:18 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4523 ------- Comment #1 from mike@saxonica.com 2007-05-03 06:24 ------- I agree that there's a usability problem here. Sometimes you do need to generate output in a default namespace, for example because there's a DTD that requires this for validity, or because there's some other bit of software at the receiving end that isn't 100% namespace-aware. I think we should put this use case on the requirements list for XQuery 1.1. Personally I think the right answer is along the lines we adopted in XSLT 2.0: allow a different default namespace for element names in path expressions and element names in constructors.
Received on Thursday, 3 May 2007 06:24:23 UTC