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

[Bug 4170] W3C DOM cannot rename a PI

From: <bugzilla@wiggum.w3.org>
Date: Wed, 10 Jan 2007 12:47:46 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1H4crq-0008BP-PV@wiggum.w3.org>

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





------- Comment #5 from mike@saxonica.com  2007-01-10 12:47 -------
I'm not speaking for the WG.

But I would think that when you're doing two-way mappings rather than one-way,
a lot of systems are going to have problems if they use an underlying model
that doesn't map accurately to XDM. I don't know how you're doing your mapping,
however. In Saxon, when it runs over a DOM, there is already an indirection
between Saxon node identity and DOM node identity, for example one Saxon (XDM)
text node can map to several DOM text nodes. Frankly, there are so many
glitches you have to work around in mapping DOM to XDM that I'm surprised one
more should cause you any particular difficulties.

I would certainly rather see products saying "This feature doesn't work in this
environment because DOM can't do it" than to see the XQuery spec saying "This
feature doesn't exist in the language because implementors can't see how to
make it work when the implementation platform is a DOM". In fact, I have a
general view that arguments to restrict the language or reduce its
orthogonality because of perceived implementation difficulties are nearly
always wrong. (Certainly, when I've advanced such arguments myself I've usually
regretted it later.)
Received on Wednesday, 10 January 2007 12:47:55 UTC

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