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 13360 - [XSLT 3.0] Comments on the serializability analysis
Summary: [XSLT 3.0] Comments on the serializability analysis
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Working drafts
Hardware: PC Windows NT
: P2 normal
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: 2011-07-25 22:30 UTC by Michael Kay
Modified: 2012-05-16 20:47 UTC (History)
0 users

See Also:


Attachments

Description Michael Kay 2011-07-25 22:30:17 UTC
The following comments were received from Hans-Juergen Rennau:

in part 18.4.1 "Building an Expression Tree" I tiny text omissions (?) in the 
text - perhaps of interest to you. It is purely editorial.

handling xsl:sort
============
In the table, row "xsl:apply-templates instruction" there is:
"...; in addition, it has as children the select expression of the xsl:sort 
element, plus any expressions ..." [singular!]

I suspect this should be:
"...; in addition, it has as children the select expressions and/or contained 
sequence constructors of the xsl:sort elements, plus any expressions ..."

Similarly, in the row "xsl:perform-sort" it reads:
"The select expression or contained sequence constructor, together with any 
expressions that appear in attribute value templates ..."

but should perhaps be:
"The select expression or contained sequence constructor, together with the 
select expressions and/or contained sequence constructors of the xsl:sort 
elements, plus any expressions that appear in attribute value templates ..."

and in the row "xsl:for-each-group" it reads:
"...; in addition, it has as children any expression that appear in attribute 
value templates among the attribues of the xsl:sort elements..."

but should perhaps be the same text as in row "xsl:apply-templates", that is:
"...; in addition, it has as children the select expressions and/or contained 
sequence constructors of the xsl:sort elements, plus any expressions that appear 
in attribute value templates among the attributes of the xsl:sort elements..."

xsl:param, xsl:with-param: slight "inconsistencies" (correct, but may a little 
confuse)
=============================================================
Row "Template": ...; the xsl:param elements used to bind default values ..."
Row "xsl:iterate-instrcution": ...; the select expressions of all contained 
xsl:param elements

And the second variant is inferior, as it omits the possibility of a sequence 
constructor (in contrast to the first one, referring to "xsl:param", a row where 
we find "...the select attribute, or the contained sequence constructor".

---

Row "xsl:apply-templates": "... plus variable binding elements representing the 
xsl:with-param children"
Row "xsl:evaluate instruction": "... ; any child xsl:with-param elements"

Dealing with pattern
==============
Probably this is intentional and has a reason, but it strikes me that in 
"Template" the pattern is represented by a child e-node, whereas in 
"xsl:for-each-group instruction" the pattern is analyzed and then either not 
represented or represented by "preceding::*".

Kind regards,
-- Hans
Comment 1 Michael Kay 2012-05-16 20:47:23 UTC
These comments have been overtaken by events: the serializability analysis has been completely rewritten in the latest draft. Therefore closing as RESOLVED.