This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 30056 - [XSLT30]Example input and output in streamed grouping example in diff document https://www.w3.org/XML/Group/qtspecs/specifications/xslt-30/html/Overview-diff.html#stream-examples don't match
Summary: [XSLT30]Example input and output in streamed grouping example in diff documen...
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Member-only Editors Drafts
Hardware: PC Windows NT
: P2 editorial
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-28 17:52 UTC by Martin Honnen
Modified: 2017-04-03 20:57 UTC (History)
1 user (show)

See Also:


Attachments

Description Martin Honnen 2017-01-28 17:52:36 UTC
While reading https://www.w3.org/XML/Group/qtspecs/specifications/xslt-30/html/Overview-diff.html#stream-examples I noticed that for the example "Using xsl:source-document with xsl:for-each-group" the input and output don't match because the input sample has "chapter" elements with "title" child elements (e.g.

 <chapter part="1">
    <title>The first chapter of book A</title>
    ...
  </chapter>

) while the result document has "title" attributes (e.g. 

    <chapter title="The first chapter of book A" part="1">
      ...
    </chapter>

) although the XSLT does simply use 

         <xsl:for-each-group select="chapter" group-adjacent="data(@part)">
            <part number="{current-grouping-key()}">
               <xsl:copy-of select="current-group()"/>
            </part>
         </xsl:for-each-group>

so it does not modify the "chapter" elements. The document https://www.w3.org/XML/Group/qtspecs/specifications/xslt-30/html/#stream-examples does not have this problem, so somehow the example in the diff.html is different from the one in the spec document.
Comment 1 Michael Kay 2017-01-28 18:23:04 UTC
Thanks.

I think the error is present in both versions of the document.
Comment 2 Michael Kay 2017-01-30 09:02:48 UTC
I have fixed the expected output of the example.