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

[Bug 10976] New: Problems in various streamability examples

From: <bugzilla@jessica.w3.org>
Date: Mon, 04 Oct 2010 15:38:50 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-10976-523@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10976

           Summary: Problems in various streamability examples
           Product: XPath / XQuery / XSLT
           Version: Member-only Editors Drafts
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P2
         Component: XSLT 2.1
        AssignedTo: mike@saxonica.com
        ReportedBy: nick@cbcl.co.uk
         QAContact: public-qt-comments@w3.org
             Group: XSLXQuery_WG


In 18.4.4.4 the diagram for "Example: Non-streamable sorting" contains
attribute::empNr as a child of the xsl:for-each expression, it should be a
child of the sort expression according to the e-node representation directly
above it.

In 18.4.4.6 "Example: A streamable recursive template" the function names
div-depth and nesting-depth are used interchangeably for the same function in
both the code and diagram.

In 18.4.4.3 it could appear that that dataflow is connected via the
xsl:template, so the diagram "Example: A streamable loop" could easily be
interpreted as:

<a> => xsl:for-each => xsl:template => child::employee => child::salary =>
descendant-of-self::text() => path

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 4 October 2010 15:38:52 UTC

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