W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2016

[Bug 29709] New: [XSLT30]Some xsl:merge examples use variables not defined in the samples, probably as earlier versions bound merge groups or keys to variables

From: <bugzilla@jessica.w3.org>
Date: Mon, 27 Jun 2016 17:22:02 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29709-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29709

            Bug ID: 29709
           Summary: [XSLT30]Some xsl:merge examples use variables not
                    defined in the samples, probably as earlier versions
                    bound merge groups or keys to variables
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: martin.honnen@gmx.de
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

Section https://www.w3.org/TR/xslt-30/#merge-examples has an example with code

  <record ID="{$merge-key}">

although that variable is not defined in the example. I suppose the example has
not been (completely) corrected since earlier versions of the spec where merge
groups and keys were accessible as variables.

In the current spec I think 

  <record ID="{$merge-key}">

should be

  <record ID="{current-merge-key()}">


And in https://www.w3.org/TR/xslt-30/#merge-action there is an example using an
undefined variable 

  <xsl:copy-of select="$master"/>

which should be

  <xsl:copy-of select="current-merge-group('master')"/>

to use the proper way to access a merge group by name in line with the current
spec.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 27 June 2016 17:22:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:01 UTC