W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2005

[Bug 1272] 3.7.4 In-scope Namespaces of a Constructed Element looks buggy

From: <bugzilla@wiggum.w3.org>
Date: Tue, 26 Apr 2005 21:57:03 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1DQY3D-0007d9-9L@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1272





------- Additional Comments From mike@saxonica.com  2005-04-26 21:57 -------
I think both your examples are correct: though example 2 depends on how one
reads the serialization spec as well as the XQuery spec.

"Namespaces are way too complicated in XQuery". True. But sadly, they still
aren't complicated enough to meet all requirements. For example there is
currently no way of copying namespaces from the source document to the result
document except when making an exact copy of the containing element. So if you
want to transform a schema into an equivalent schema that drops all the
<xs:annotation>s, you're stuck. What we have may be complicated, but it's all
driven by real use cases.

Michael Kay
Received on Tuesday, 26 April 2005 21:57:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:37 GMT