W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2007

[Bug 4535] [UPD] Section 2.4.4 Rename: make it optional

From: <bugzilla@wiggum.w3.org>
Date: Tue, 29 May 2007 16:02:08 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1Ht49A-0008Vr-Pz@wiggum.w3.org>

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





------- Comment #6 from jonathan.robie@redhat.com  2007-05-29 16:02 -------
I agree with Don and with Michael Kay here. XQuery is defined in terms of
operations on XML, not in terms of the infinite number of possible underlying
stores, and basic functionality like renaming a node is pretty much expected.

When I was at DataDirect, we carefully documented the (relatively few!) places
where we were unable to conform to the specification due to limitations caused
by the underlying relational databases. We never had a customer complain,
because we were able to explain these limitations pretty easily, and they were
few. I'm no longer at DataDirect, but in this case I would simply introduce an
error saying that you can't do a rename of a node that corresponds to a table,
row, or column name in an XML view. I would, however, allow renames in XML
documents if it were possible in my implementation.

To me, this allows us to keep the XQuery specification clean, providing the
functionality needed for XML, while still making it easy for vendors to be
clear why they can't always be 100% spec compliant.
Received on Tuesday, 29 May 2007 16:02:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:18 UTC