- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 06 Apr 2009 08:40:56 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6775
Michael Kay <mike@saxonica.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
Component|XSLT 2.0 |XSLT 2.1
--- Comment #1 from Michael Kay <mike@saxonica.com> 2009-04-06 08:40:56 ---
I have reclassified this as an enhancement request, so that it gets into the
right part of the Working Group agenda.
On another related enhancement request, the WG decided that we should wait
until HTML5 has reached a more advanced stage of development before considering
in detail what XSLT support was required.
I have to say I am a little confused by this request. In a DOM-to-DOM
transformation, no serialization is taking place, therefore I would expect that
the following rule in section 2.6 applies: "When serialization is not being
performed, either because the implementation does not support the serialization
option, or because the user is executing the transformation in a way that does
not invoke serialization, then the content of the xsl:output and
xsl:character-map declarations has no effect." In particular, I would not
expect the result of DOM-to-DOM transformation to depend in any way on the fact
that xsl:output specifies method="html".
I would personally expect to handle this requirement not by a serialization
option, but by a function such as normalize-html() which converts a tree by
applying your rules (1) and (2). Whether the requirement for that function
merits including it in the standard library is something the WG will have to
debate.
--
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 08:41:07 UTC