W3C home > Mailing lists > Public > public-qt-comments@w3.org > October 2005

[Bug 2420] xsl:message treats a colision of select attribute and sequence-constructor in contentare different from other elements

From: <bugzilla@wiggum.w3.org>
Date: Wed, 26 Oct 2005 20:13:33 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1EUreP-0001NB-2G@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2420

           Summary: xsl:message treats a colision of select attribute and
                    sequence-constructor in contentare different from other
                    elements
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: PC
               URL: http://www.w3.org/TR/xslt20/#element-perform-sort
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P3
         Component: XSLT 2.0
        AssignedTo: mike@saxonica.com
        ReportedBy: sdubinets@hotmail.com
         QAContact: public-qt-comments@w3.org


In XSLT 2.0 many instructions allow two alternatives in specifying content:
1. with optional select attribute.
2. with sequence-constructor as content.
In most of them attribute select and sequence-constructor are "mutually
exclusive"  (with more or less consisting wording of this fact).
xsl:variable, xsl:param, xsl:with-param, xsl:attribute, xsl:manespace,
xsl:comment, xsl:processing-instruction, xsl:value-of, xsl:sort, xsl:perform-sort.

xsl:message handles this collision differently: it allows both of them.

This looks like a bug in a spec.
Received on Wednesday, 26 October 2005 20:13:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:09 UTC