- From: Michael Kay <mike@saxonica.com>
- Date: Fri, 3 Jun 2016 16:35:53 +0100
- To: Public XSLWG <public-xsl-wg@w3.org>
The XSL WG met on Thursday, 02 June 2016 for 90 minutes at the START TIME as follows: 7. XSLT Draft §§ MKay has committed a new editor's draft. The diff version is at the usual location. Published CR: http://www.w3.org/TR/2015/CR-xslt-30-20151119/ Internal version: https://www.w3.org/XML/Group/qtspecs/specifications/xslt-30/html/Overview.html dated W3C Candidate Recommendation 27 May 2016 §§ DECISION: accepted the changes made in respect of bug 29604. But note Martin Honnen has pointed out a typo – mismatched quotes around 'max". §§ DECISION: approved the changes made for bug 29574, but note that Abel found a typo and reopened 29574 (comment #16) to describe it. 8. Spec bugs 29472 [XSLT30] Optionally allow xsl:stream to process a document *without* streaming 2016-03-10 https://www.w3.org/Bugs/Public/show_bug.cgi?id=29472 §§ Discussion: §§ MK and Abel paraphrased their comments on the bug. §§ MSMcQ: makes me nervous. Starting with xsl:stream/@streamable – I think streaming is an optimization, not part of the semantics, therefore should be controlled as part of the invocation not part of the stylesheet syntax. This should be a run-time invocation option. §§ Much discussion... There seems to be agreement that we should allow execution of xsl:stream in non-streaming mode. Currently we allow a non-streaming processor to do this but not a streaming processor! The question is how to control it. §§ ACTION 2016-06-02-001 (bug 29472) on MSMcQ to put his views on this in writing, in email or in the bugzilla entry. ETA 9 June 2016. §§ No decision on this bug. 29492 [XSLT30] streamability of xsl:attribute-set may not be complete 2016-05-12 https://www.w3.org/Bugs/Public/show_bug.cgi?id=29492 §§ Accepted the proposed resolution §§ ACTION 2016-06-02-002 on MK to apply the changes outlined in bug 29492. 29513 [XSL30] Definition of "potentially consuming" in Glossary not complete 2016-03-31 https://www.w3.org/Bugs/Public/show_bug.cgi?id=29513 §§ Purely editorial. 29666 [XSLT30] Stylesheet level definition may need updating or clarification Fri 10:30 https://www.w3.org/Bugs/Public/show_bug.cgi?id=29666 §§ Note, in the new Note (comment 3) import precedence should be hyperlinked. §§ (After the meeting: the hyperlinks have been added.) §§ DECISION to mark bug 29666 as resolved with the action already taken plus some extra hyperlinking. §§ Abel felt that "includes the other" could be read as indirect inclusion. §§ MSMcQ – strictly speaking, there should be an additional case that says if something doesn't satisfy the condition, then it's not part of the stylesheet level. 29667 [XSLT30] XTSE3050 with hidden components and homonymous name conflict is ambiguous Fri 17:25 https://www.w3.org/Bugs/Public/show_bug.cgi?id=29667 §§ MSMcQ Proposal: add a note to confirm that using the same package twice is the same as using two packages with the same content. §§ Abel: but how do we prohibit cycles if there is no identity? MSMcQ: a cycle of URIs would lead to infinite regress in applying the rules. §§ DECISION to resolve with this added Note. §§ ACTION 2016-06-02-003: (bug 29667) MK to resolve this by adding a Note to the effect that using the "same" package twice is the same as using two packages with the same content.
Received on Friday, 3 June 2016 15:36:35 UTC