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

[Bug 6775] DOM-to-DOM transform with method='html' needs to convert no-namespace nodes into the HTML namespace

From: <bugzilla@wiggum.w3.org>
Date: Mon, 06 Apr 2009 09:44:18 +0000
To: public-qt-comments@w3.org
Message-Id: <E1LqlNK-0004vv-Es@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6775





--- Comment #3 from Michael Kay <mike@saxonica.com>  2009-04-06 09:44:18 ---
(personal response) It seems to me that the kind of thing you are describing is
entirely outside the scope of the XSLT and XPath specifications. These
specifications are described in terms of an abstract data model (XDM) which you
can map to concrete data structures (such as a Gecko implementation of an HTML5
DOM) in any way you choose. If you choose to map a node called
"{http://www.w3.org/xhtml}P" in the XDM to a node called "p" in your concrete
DOM, or vice versa, that's entirely up to you. Please take advantage of the
abstractions built in to the specifications, which are there precisely so that
XSLT and XPath don't need to change every time someone has this kind of
requirement.

>Gecko already needs to perform the local name lower-casing in such a DOM-to-DOM transform by observing parameters meant for serialization even though no serialization happens

If you want this to be regarded as conformant behaviour, I think it's best to
present it not as an XSLT transformation proper, but as an optimized
implementation of a pipeline that consists of XSLT transformation, HTML
serialization, and HTML parsing of the result into an HTML DOM.

Michael Kay
http://www.saxonica.com/


-- 
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, 6 April 2009 09:44:26 UTC

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