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

[Bug 1306] Construction mode preserve with copy-namespaces no-preserve

From: <bugzilla@wiggum.w3.org>
Date: Tue, 14 Jun 2005 13:39:51 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1DiBdv-0006rS-Kk@wiggum.w3.org>

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





------- Additional Comments From mike@saxonica.com  2005-06-14 13:39 -------
At the face-to-face meeting in May, the XQuery WG decided that disallowing the
combination of copying types without copying namespaces was too severe a
restriction, and asked XSL WG to reconsider its decision on bug 1235.

This the XSL WG did at its telcon on 9 June. The XSL WG decided they did not
want to introduce namespace fixup for this case, because of the impact on
streaming processors, but decided that rather than having a static restriction,
there should be a dynamic restriction: if copying of type annotations is
requested, and copying of namespaces is not requested, then it should be a
dynamic error (probably a type error) if the node being copied actually contains
namespace-sensitive content.

It seems to me a reasonable restriction that if you copy namespace-sensitive
content then you should also copy the namespaces. This solution appears to deal
with the XQuery WGs valid objections that the proposed restriction was too
severe, while also dealing with the XSL WG's concerns about streaming
implementations.

(There remains one difficulty: XQuery only allows the copy options to be
selected at the module level, and it's a bit onerous to have to put an
expression in a separate module just because different copy options are
required. However, that's not a new problem caused by this change, and it can be
solved quite independently of this change.)

The detailed proposal is now:

Change 3.7.1.3 1.e.ii.D.I from

If copy-namespaces mode specifies preserve, all in-scope-namespaces of the
original element are retained in the new copy. If copy-namespaces mode specifies
no-preserve, the new copy retains only those in-scope namespaces of the original
element that are used in the names of the element and its attributes, and in the
typed values of the element and its attributes if these are namespace-sensitive.
Values are namespace-sensitive if they include an item that has a dynamic type
of xs:QName or xs:NOTATION or types derived by restriction therefrom.

to

If copy-namespaces mode specifies preserve, all in-scope-namespaces of the
original element are retained in the new copy. If copy-namespaces mode specifies
no-preserve, the new copy retains only those in-scope namespaces of the original
element that are used in the names of the element and its attributes. It is a
type error [ERRxxxx] in this case if the typed value of the element or of any of
its attributes is namespace-sensitive. Values are namespace-sensitive if they
include an item that has a dynamic type of xs:QName or xs:NOTATION or types
derived by restriction therefrom.

Michael Kay
Received on Tuesday, 14 June 2005 13:39:57 GMT

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