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

[Bug 22747] New: Visibility and overriding accumulated attribute-sets

From: <bugzilla@jessica.w3.org>
Date: Sun, 21 Jul 2013 22:23:04 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-22747-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22747

            Bug ID: 22747
           Summary: Visibility and overriding accumulated attribute-sets
    Classification: Unclassified
           Product: XPath / XQuery / XSLT
           Version: Member-only Editors Drafts
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org

This bug was first sent to the XSL WG mailing list [1], a copy of the message
follows:

Different from other declarations, an attribute set declaration with the
same name doesn't override the previous attribute set, but augments
it.We went through the specification on the (I think) relevant sections,
but wecouldn't find a definitive rule how to deal with conflicting
situations, like when visibility is not equal. Example:

Inside a package:

<xsl:attribute-set name="foo" visibility="private">
    <xsl:attribute name="a" />
</xsl:attribute-set>   

<xsl:attribute-set name="foo" visibility="public">
    <xsl:attribute name="b" />
</xsl:attribute-set>   

<xsl:attribute-set name="foo" visibility="final">
    <xsl:attribute name="c" />
</xsl:attribute-set>  

I think we need rules for the following scenario's:

1) Which attribute-set(s) is/are overriden when you override
attribute-set"foo"?
2) Which attribute-set(s) is/are referenced when xsl:override is used
within an overriding attribute-set of "foo"?
3) What attributes are included when nothing is overriden for "foo"?
4) What would cause an error to be raised for trying to override a
finalattribute-set "foo"?

My preference would go to the following: disallow different visibility
on an attribute-set with the same name and the same import precedence.
That way, we don't have to deal with potentially complex rules and,
possibly worse, hard-to-understand behavior of stylesheets that
accidentally forget the visibility attribute (it defaults to private).

[1] https://lists.w3.org/Archives/Member/w3c-xsl-wg/2013Jul/0046.html

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 21 July 2013 22:23:06 UTC

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