- From: Norm Tovey-Walsh <norm@saxonica.com>
- Date: Mon, 14 Oct 2024 10:49:14 +0100
- To: "public-xslt-40@w3.org" <public-xslt-40@w3.org>
- Message-ID: <m2plo3dnfp.fsf@saxonica.com>
Hello,
Here’s the draft agenda for tomorrow’s meeting:
https://qt4cg.org/meeting/agenda/2024/10-15.html
QT4 CG Meeting 094 Agenda 2024-10-15
[1]Agenda index / [2]QT4CG.org / [3]Dashboard / [4]GH Issues / [5]GH
Pull Requests
Agenda
This meeting will be hosted on Zoom at 16:00BST (15:00GMT, 17:00CEST,
11:00EDT)
The [6]Zoom meeting ID is 831 9996 6275; the passcode is 707664.
See the [7]meeting logistics page for more details.
1. Administrivia
1.1. Roll call
1.2. Approve the agenda
1.3. Approve minutes of previous meeting
Minutes of [8]the previous meeting.
1.4. Next meeting
This meeting is planned for 15 October 2024. The following meeting is
scheduled for 22 October.
Note: The QT4CG operates on European civil time. In Europe and the
United Kingdom, summer time ends on 27 October. In the United States,
summer time ends on 3 November. That means the meeting of 29 October
will be one hour later in the United States.
1.5. Review of open action items [3/8]
(Items marked [X] are believed to have been closed via email before
this agenda was posted.)
* [ ] QT4CG-080-07: NW to update the build instructions in the README
* [ ] QT4CG-082-02: DN to work with MK to come to agreement on the
fn:ranks proposal
* [ ] QT4CG-088-01: NW to consider how best to add a dedication to
MSM.
* [ ] QT4CG-088-04: [Someone] needs to update the processing model
diagram needs vis-a-vis the static typing feature
* [ ] QT4CG-089-01: CG to draft a PR that attempts to resolve the
operators described in #755 to a smaller number of orthogonal
choices.
* [X] QT4CG-093-01: NW to fix the bug in the burndown charts
* [X] QT4CG-093-02: NW to resolve the F&O search box one way or the
other
* [X] QT4CG-093-03: NW to make dashboard links redirect to the
issue/PR when they're no longer on the dashboard
1.6. Review of open pull requests and issues
1.6.1. Blocked
The following PRs are open but have merge conflicts or comments which
suggest they aren't ready for action.
* PR [9]#1296: 982 Rewrite of scan-left and scan-right
* PR [10]#1283: 77b Update expressions
* PR [11]#1062: 150bis revised proposal for fn:ranks
* PR [12]#529: 528 fn:elements-to-maps
1.6.2. Merge without discussion
The following PRs are editorial, small, or otherwise appeared to be
uncontroversial when the agenda was prepared. The chairs propose that
these can be merged without discussion. If you think discussion is
necessary, please say so.
* PR [13]#1492: 1312 Add ws:explicit annotations
* PR [14]#1490: 1308 In fn:apply, Correct $array to $arguments
* PR [15]#1489: 1483 return type of fn:error
* PR [16]#1467: Modest editorial corrections to XSLT specs through
2.7
1.6.3. Close without action
It has been proposed that the following issues be closed without
action. If you think discussion is necessary, please say so.
* Issue [17]#1473: fn:identity: make it variadic
* Issue [18]#1305: Almost all functions in FO that must process
multiple string items, can have as a parameter only a single
collation
* Issue [19]#1183: transient() - a function to make functions
nondeterministic
1.6.4. Substantive PRs
The following substantive PRs were open when this agenda was prepared.
* PR [20]#1472: 1471 JSON Serialization: Sequences on Top Level
* PR [21]#1470: 689 fn:stack-trace: replace with $err:stack-trace
* PR [22]#1488: 1487 in xsl:array, drop option to construct arrays
from arrays
* PR [23]#1454: 1449 Relax rules on multiple xsl:includes
* PR [24]#1442: 1394 Add new default priority rules
* PR [25]#1378: 1375 bugs in pattern syntax
1.6.5. Required for V4.0
The following issues are labeled "required for V4.0".
* Issue [26]#1252: Add a new function `fn:html-doc`
* Issue [27]#1240: $sequence-of-maps ? info()
* Issue [28]#1238: XSLT on-no-match="shallow-copy-all" - revised
rules
* Issue [29]#1169: Maps & Arrays: Consistency & Terminology
* Issue [30]#1127: Binary resources
* Issue [31]#1045: Functions to manage namespace usage
* Issue [32]#1021: Extend `fn:doc`, `fn:collection` and
`fn:uri-collection` with options maps
* Issue [33]#1011: fn:transform() improvements
* Issue [34]#986: Numeric Comparisons
* Issue [35]#967: XPath Appendix I: Comparisons
* Issue [36]#868: fn:intersperse -> fn:join, array:join($arrays,
$separator)
* Issue [37]#826: Arrays: Representation of single members of an
array
* Issue [38]#767: parse-html(): case of SVG element names
* Issue [39]#748: Parse functions: consistency
* Issue [40]#689: fn:stack-trace: replace with $err:stack-trace
* Issue [41]#675: XSLT streaming rules for new constructs
* Issue [42]#501: Error handling: Rethrow errors; finally block
* Issue [43]#490: Control over schema validation in parse-xml(),
doc(), etc.
* Issue [44]#407: XSLT-specific context properties used in function
items
* Issue [45]#272: Setting parameter values in xsl:use-package
* Issue [46]#69: fn:document, fn:function-available: default
arguments
2. Technical agenda
2.1. PR #1472: 1471 JSON Serialization: Sequences on Top Level
See PR [47]#1472
2.2. PR #1470: 689 fn:stack-trace: replace with $err:stack-trace
See PR [48]#1470
2.3. PR #1488: 1487 in xsl:array, drop option to construct arrays from arrays
See PR [49]#1488
2.4. PR #1454: 1449 Relax rules on multiple xsl:includes
See PR [50]#1454
2.5. PR #1442: 1394 Add new default priority rules
See PR [51]#1442
2.6. PR #1378: 1375 bugs in pattern syntax
See PR [52]#1378
3. Any other business
References
1. https://qt4cg.org/meeting/agenda/
2. https://qt4cg.org/
3. https://qt4cg.org/dashboard
4. https://github.com/qt4cg/qtspecs/issues
5. https://github.com/qt4cg/qtspecs/pulls
6. https://us06web.zoom.us/j/83199966275?pwd=SmN6V0RhUGdSTHFHZkd6cjgxVEY2QT09
7. https://qt4cg.org/meeting/logistics.html
8. https://qt4cg.org/meeting/minutes/2024/10-08.html
9. https://qt4cg.org/dashboard/#pr-1296
10. https://qt4cg.org/dashboard/#pr-1283
11. https://qt4cg.org/dashboard/#pr-1062
12. https://qt4cg.org/dashboard/#pr-529
13. https://qt4cg.org/dashboard/#pr-1492
14. https://qt4cg.org/dashboard/#pr-1490
15. https://qt4cg.org/dashboard/#pr-1489
16. https://qt4cg.org/dashboard/#pr-1467
17. https://github.com/qt4cg/qtspecs/issues/1473
18. https://github.com/qt4cg/qtspecs/issues/1305
19. https://github.com/qt4cg/qtspecs/issues/1183
20. https://qt4cg.org/dashboard/#pr-1472
21. https://qt4cg.org/dashboard/#pr-1470
22. https://qt4cg.org/dashboard/#pr-1488
23. https://qt4cg.org/dashboard/#pr-1454
24. https://qt4cg.org/dashboard/#pr-1442
25. https://qt4cg.org/dashboard/#pr-1378
26. https://github.com/qt4cg/qtspecs/issues/1252
27. https://github.com/qt4cg/qtspecs/issues/1240
28. https://github.com/qt4cg/qtspecs/issues/1238
29. https://github.com/qt4cg/qtspecs/issues/1169
30. https://github.com/qt4cg/qtspecs/issues/1127
31. https://github.com/qt4cg/qtspecs/issues/1045
32. https://github.com/qt4cg/qtspecs/issues/1021
33. https://github.com/qt4cg/qtspecs/issues/1011
34. https://github.com/qt4cg/qtspecs/issues/986
35. https://github.com/qt4cg/qtspecs/issues/967
36. https://github.com/qt4cg/qtspecs/issues/868
37. https://github.com/qt4cg/qtspecs/issues/826
38. https://github.com/qt4cg/qtspecs/issues/767
39. https://github.com/qt4cg/qtspecs/issues/748
40. https://github.com/qt4cg/qtspecs/issues/689
41. https://github.com/qt4cg/qtspecs/issues/675
42. https://github.com/qt4cg/qtspecs/issues/501
43. https://github.com/qt4cg/qtspecs/issues/490
44. https://github.com/qt4cg/qtspecs/issues/407
45. https://github.com/qt4cg/qtspecs/issues/272
46. https://github.com/qt4cg/qtspecs/issues/69
47. https://qt4cg.org/dashboard/#pr-1472
48. https://qt4cg.org/dashboard/#pr-1470
49. https://qt4cg.org/dashboard/#pr-1488
50. https://qt4cg.org/dashboard/#pr-1454
51. https://qt4cg.org/dashboard/#pr-1442
52. https://qt4cg.org/dashboard/#pr-1378
Be seeing you,
norm
--
Norm Tovey-Walsh
Saxonica
Received on Monday, 14 October 2024 09:49:21 UTC