FW: Minutes of XSLT WG Telcon Agenda 01 October 2015

Following is a public abstract of the minutes of the XSLWG meeting of Oct 1, 2015.


> 
> 6 XSLT Draft
> 
> W3C Internal Working Draft 14 September 2015
> 
> https://www.w3.org/XML/Group/qtspecs/specifications/xslt-
> 30/html/Overview-diff.html
> 
> Last public draft:
> W3C Last Call Working Draft 2 October 2014
> 
> http://www.w3.org/TR/2014/WD-xslt-30-20141002/
> 
> 6.1 Arrays in the built-in template rules
>     https://lists.w3.org/Archives/Public/public-xsl-wg/2015Sep/0004.html- MK
>     
> https://lists.w3.org/Archives/Public/public-xsl-wg/2015Sep/0010.html- 
> Abr

There was some discussion on the way shallow-copy could be made workable by recursively going over the members of maps or arrays. It was then decided that it'd be sufficient to support copy of the atomic item and *not* also go over the members of the array (it it is an array) or map (if it is a map).

DECISION:
The WG discussed at some depth the mentioned mail and in the end accepted the recommendation as written in message 0004 in the Sept 2015 archive.

> 
> 6.2 "Available" variables
>    https://lists.w3.org/Archives/Member/w3c-xsl-wg/2015Sep/0010.html
>    https://lists.w3.org/Archives/Member/w3c-xsl-wg/2015Sep/0012.html
> 
>    See https://www.w3.org/Bugs/Public/show_bug.cgi?id=29113
>    Changes as outlined applied in spec.  Need WG review.
> 
> 6.3 Parentless Attribute Nodes
> 
>     Parentless attribute nodes and namespaces, text says it is...
>     https://lists.w3.org/Archives/Public/public-xsl-wg/2015Sep/0011.html- ABr
>     https://lists.w3.org/Archives/Public/public-xsl-wg/2015Sep/0012.html- FG
>     https://lists.w3.org/Archives/Public/public-xsl-wg/2015Sep/0013.html- ABr
>     https://lists.w3.org/Archives/Public/public-xsl-wg/2015Sep/0014.html- FG
>     https://lists.w3.org/Archives/Public/public-xsl-wg/2015Sep/0015.html- MK
>     
> https://lists.w3.org/Archives/Public/public-xsl-wg/2015Sep/0016.html- 
> FG

The WG discussed this briefly and ABr concluded that the confusion came from the word "content" as in the content of an attribute node. The prose talks about the value of an attribute, which does not include the namespace information inside the attribute name, which itself is a triplet of namespace, prefix and local name.

DECISION: no action

> 
> 6.4 XSLT's Relationship to XPath 3.1
>    Continue discussion of XPath 3.0 and 3.1 in relation to XSLT 3.0
> 
>   6.4.1 XSLT 3.0, XPath 3.1, including arrays
>     See bug 29079

MK walks us through comment#1. Since this is mainly a placeholder for an existing action item, the discussion was brief and the WG accepted the proposal as written.

DECISION: The WG accepts the resolution in comment#1 of bug 29079 as written.

The WG skipped the next item on the agenda and continued with 6.4.3.

> 
>   6.4.2 ACTION 2015-06-18-002: Abel will look at the XPath 3.1 and 3.0 bug
>    lists and report back the bugs applicable to XPath 3.0..
>    https://lists.w3.org/Archives/Member/w3c-xsl-wg/2015Sep/0005.html
> 
>    This agenda item is a placeholder.
> 
>   *6.4.3. Streamability and XPath 3.1
>       
> https://lists.w3.org/Archives/Public/public-xsl-wg/2015Sep/0006.html

The proposal as written was accepted, will be turned into a bug entry and a more detailed proposal to be included in the spec

> 
> 6.6 Default mode through xsl:default-mode, if it is not declared - Abel
>     https://lists.w3.org/Archives/Member/w3c-xsl-wg/2015Sep/0015.html
>     See bug list 29122. Changes applied to the spec.  WG to review.

DECISION: bug as implemented is accepted and approved as written

At this moment, we moved to item 7.2.3 of the agenda.

> 
> 6.7 Review Updated Appendix F
> 
>     6.7.1 "compare" MKay and ABraaksma's implementations
>

Received on Wednesday, 7 October 2015 09:11:36 UTC