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

[Bug 1308] New: proposal: merge xsl:perform-sort and xsl:sequence

From: <bugzilla@wiggum.w3.org>
Date: Fri, 06 May 2005 14:09:35 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1DU3WJ-0001Fw-B5@wiggum.w3.org>

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

           Summary: proposal: merge xsl:perform-sort and xsl:sequence
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: PC
        OS/Version: Windows 2000
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 2.0
        AssignedTo: mike@saxonica.com
        ReportedBy: davidc@nag.co.uk
         QAContact: public-qt-comments@w3.org


As far as I can tell, an xsl:perform-sort is identical in all respects to
xsl:sequence except that in perform-sort (at least one) xsl:sort is mandatory
and in xsl:sequence xsl:sort is not allowed.

I would propose to remove xsl:perform-sort from the specification and allow
xsl:sort as a child of xsl:sequence (so that the semantics of xsl:sequence
become those currently used for xsl:perform-sort if it has an xsl:sort child)


This simplifies the specification (one less element) and makes the use of
xsl:sort more consistent. In other cases xsl:sort is optionally allowed as a
child of the containing instruction (eg xsl:for-each) with sorting occurring if
it is present, it is only in this case that there are two separate instructions,
one requiring a sort specification and the other not allowing it.

David
Received on Friday, 6 May 2005 14:09:53 UTC

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