W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2013

[Bug 22747] Visibility and overriding accumulated attribute-sets

From: <bugzilla@jessica.w3.org>
Date: Mon, 22 Jul 2013 08:58:28 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-22747-523-27rFLU5mcJ@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22747

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
I would propose to tackle this as follows.

First, refine the terminology, as we currently do with xsl:key,
xsl:decimal-format, and xsl:output. We say for example

[Definition: A key is defined as a set of xsl:key declarations in the same
package that share the same name.]

and we should similarly say that an attribute set is a defined as a set of
xsl:attribute-set declarations in the same package that share the same name.

Then (again by analogy with xsl:key and collation) require that all the
declarations making up an attribute set have the same value for the visibility
attribute.

Then make it clear that the attribute set "component" is an attribute set, not
an xsl:attribute-set declaration, and that constructs like xsl:accept and
xsl:override apply to the attribute set as a whole.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 22 July 2013 08:58:29 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:53 UTC