- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 04 Jun 2009 10:10:02 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6775
Jirka Kosek <jirka@kosek.cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jirka@kosek.cz
--- Comment #16 from Jirka Kosek <jirka@kosek.cz> 2009-06-04 10:10:02 ---
> I wonder if a serialization option to move no-namespace element nodes into a
user-specified namespace would be generally useful?
Probably xsl:namespace-alias can be extended to support this useful behaviour.
But this is only XSLT, not XQuery feature.
But more to the original problem. I think that once HTML5 is more finished
spec, serialization spec can say that if xsl:output/@method=("html", "xhtml")
and xsl:output/@version/xs:decimal(.)>5 then elements in no namespace or XHTML
namespace are serialized in the same way using syntax defined in HTML5. The
latest spec clarifications allow implementations to behave like this now.
But Henri's scenario when result of transformation is not serialized but stored
directly into DOM, which is only materialization of XDM, is IMHO out of scope
of XSLT spec (as Mike already pointed out). If I understand it correctly, this
problem is mainly when <?xml-stylesheet?> is used. Then the right place to fix
this problem is probably in the <?xml-stylesheet?> spec by adding note
explaining this normalization. I think it is good time to make this change as
XML Core WG is preparing new edition of stylesheet association spec.
Another possibility would be to define JS API for XPath and XSLT in HTML5 spec
and describe this process there.
--
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 Thursday, 4 June 2009 10:10:09 UTC