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 11:32:07 +0000
To: public-qt-comments@w3.org
Message-Id: <E1Lqn3f-0001UB-WC@wiggum.w3.org>

--- Comment #4 from Henri Sivonen <hsivonen@iki.fi>  2009-04-06 11:32:07 ---
(In reply to comment #3)
> (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.

As I pointed out in bug 6777, defining an XDM mapping for HTML5 that differed
from the HTML5 -> DOM -> Infoset -> XDM mapping would defeat the point of
harmonizing HTML5 and XHTML5 DOMs in the first place. In practical terms, Gecko
uses the same DOM to XDM mapping for all kinds of DOMs, except XDM to result
DOM when the output method is 'html'. I suppose we could spec-wise define a
special XDM to DOM mapping when the output method is 'html'. In any case, this
needs to be triggered on the output method even though it is a DOM-to-DOM

I observe that browsers implement XSLT 1.0 rather than XSLT 2.0. Where do you
propose this output mapping be specified?

> >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.

The results are not equivalent to the pipeline you describe. It is a DOM-to-DOM
transform with special munging for local names currently and for namespace in
the near future.

My interest here isn't getting the behavior regarded as conforming. I'm
interested in having the behavior specified to avoid a situation where creating
a new independent implementation of the Web the platform involved discovering
unspecified information.

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 11:32:17 UTC

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