- From: <bugzilla@jessica.w3.org>
- Date: Fri, 28 Mar 2014 12:06:03 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24619
--- Comment #4 from Michael Kay <mike@saxonica.com> ---
I like the idea of static AVTs but it's not easy to find a good solution to the
compatiblity problem. I propose:
for any element in the XSLT namespace,
for any permitted attribute A of that element that is in no-namespace
there is another permitted attribute _A (the same attribute name, prefixed with
an underscore), whose value is a static AVT for computing the value of A.
If both A and _A are present, A is ignored.
A static AVT is evaluated in the same way as an ordinary AVT, but using the
rules for static expressions.
For example
<xsl:include _href="library_v{$version}.xsl"/>
The result of evaluating a static AVT may be a dynamic AVT, but we won't go out
of our way to make this easy.
We allow the mechanism even for attributes with static significance, such as
static="yes|no" and use-when.
We won't include the extra attributes in the schema for XSLT 3.0 (we already
ignore the implications of xsl:use-when processing).
We won't allow the mechanism for xsl: prefixed attributes on literal result
elements.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 28 March 2014 12:06:05 UTC