W3C home > Mailing lists > Public > public-qt-comments@w3.org > August 2009

[Bug 7239] [XQTS] New test for typed value of potentially namespace sensitive XDM nodes when copied with different in scope namespaces..

From: <bugzilla@wiggum.w3.org>
Date: Mon, 10 Aug 2009 09:40:55 +0000
To: public-qt-comments@w3.org
Message-Id: <E1MaRN9-0008Nm-Kf@wiggum.w3.org>

--- Comment #2 from Oliver Hallam <oliver@cbcl.co.uk>  2009-08-10 09:40:54 ---
I did indeed mean XQTY0086.

You are indeed right in saying that the error is raised in this case.

I also meant to have the following copy-namespaces declaration in the example

declare copy-namespaces preserve,inherit;

Since copy-namespaces mode is preserve, and I am copying an element, the
XQTY0086 error is not raised according to the rules defined in XQ.E1, and my
description above is as it stands.

If the example is changed to copy an element with type "union" whose value is
"bar:test" then this example becomes even more problematic.  The type of the
value of the node in the source document is myString, and so is certainly not
namespace sensitive.  However in the context of the result document its value
is a QName if only the schema type is preserved.  XQTY0086 as it is currently
defined certainly does not apply to namespace-insensitive values.

I can not see a simple way to rewrite the conditions for XQTY0086, without
being too restrictive (only allowing copy-namespaces mode preserve no-inherit,
for nodes with schema types which can contain values that are
namespace-sensitive when using construction mode preserve)

Should this bug be raised against the spec instead, or does this example
indicate a flaw in this document representation?

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 10 August 2009 09:41:04 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:40 UTC