- From: Norm Tovey-Walsh <norm@saxonica.com>
- Date: Mon, 09 Sep 2024 11:27:56 +0100
- To: "public-xslt-40@w3.org" <public-xslt-40@w3.org>
- Message-ID: <m27cblazpv.fsf@saxonica.com>
Hi folks,
Here’s the agenda for tomorrow’s meeting. Please note that the first item on the technical agenda is discussion of issue #755.
https://qt4cg.org/meeting/agenda/2024/09-10.html
QT4 CG Meeting 089 Agenda 2024-09-10
[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. (As amended.)
1.4. Next meeting
This meeting is planned for 10 September 2024. The following meeting is
scheduled for 17 September.
1.5. Review of open action items [0/3]
(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-087-01: DN to update PR #1228 to reflect MK's compromise
and update the vulnerabilities
* [ ] QT4CG-088-01: NW to consider how best to add a dedication to
MSM.
* [ ] QT4CG-088-02: CG to add an issue about built-in, named record
types.
* [ ] QT4CG-088-03: MK to add an example of duplicate
function-annotations being returned.
* [ ] QT4CG-088-04: [Someone] needs to update the processing model
diagram needs vis-a-vis the static typing feature
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]#1414: XSLT spec abstract, introduction
* PR [10]#1355: 1351 Add "declare record" in XQuery
* PR [11]#1296: 982 Rewrite of scan-left and scan-right
* PR [12]#1227: 150 PR resubmission for fn ranks
* PR [13]#1209: 1183 Add transient mode and the transient{}
expression
* PR [14]#1185: 1179 array:values, map:values -> array:get, map:get
* PR [15]#1062: 150bis - revised proposal for fn:ranks
* PR [16]#832: 77 Lookup returning path selection
* PR [17]#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 [18]#1425: 1424 Fix typo
* PR [19]#1423: Clarify parse-uri/build-uri encoding rules, and
remove options
+ Note: an alternative to/replacement for PR [20]#1388
* PR [21]#1419: 1337bis Replace a few remaining occurrences of
"atomic value"
* PR [22]#1418: 1415 Add to lists of XSLT declarations and
instructions
* PR [23]#1417: 1408 Fix reference to "function conversion rules" in
XPTY0117
* PR [24]#1413: Dispose of action QT4CG-080-05, add absolute to
parse-uri
* PR [25]#1412: Fix typo in uri-structure-record
* PR [26]#1393: 1391 Change function-annotations to return a sequence
+ Accepted last week but not merged?
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 [27]#1385: Quantifier expressions: optional positional
argument
* PR [28]#1388: 1387 Clarify the encoding rules
1.6.4. XSLT focused
The following PRs appear to be candidates for a future XSLT-focused
meeting.
* PR [29]#1418: 1415 Add to lists of XSLT declarations and
instructions
* PR [30]#1414: XSLT spec abstract, introduction
* PR [31]#1378: 1375 - bugs in pattern syntax
1.6.5. Substantive PRs
The following substantive PRs were open when this agenda was prepared.
* PR [32]#1429: Align type tests
* PR [33]#1428: 1426 Add notes on endianness of CRC-32
* PR [34]#1393: 1391 Change function-annotations to return a sequence
* PR [35]#1364: 1314 Change to type() syntax to fix ambiguity
* PR [36]#1360: 1348 Some grammar simplifications
* PR [37]#1283: 77b: Update expressions
1.6.6. Required for V4.0
The following issues are labeled "required for V4.0".
* Issue [38]#1252: Add a new function `fn:html-doc`
* Issue [39]#1240: $sequence-of-maps ? info()
* Issue [40]#1238: XSLT on-no-match="shallow-copy-all" - revised
rules
* Issue [41]#1235: Function Identity: Treating function items with
identical bodies
* Issue [42]#1169: Maps & Arrays: Consistency & Terminology
* Issue [43]#1127: Binary resources
* Issue [44]#1045: Functions to manage namespace usage
* Issue [45]#1021: Extend `fn:doc`, `fn:collection` and
`fn:uri-collection` with options maps
* Issue [46]#1011: fn:transform() improvements
* Issue [47]#986: Numeric Comparisons
* Issue [48]#967: XPath Appendix I: Comparisons
* Issue [49]#868: fn:intersperse -> fn:join, array:join($arrays,
$separator)
* Issue [50]#826: Arrays: Representation of single members of an
array
* Issue [51]#767: parse-html(): case of SVG element names
* Issue [52]#755: Expression for binding the Context Value
* Issue [53]#748: Parse functions: consistency
* Issue [54]#689: fn:stack-trace: keep, drop, replace with
$err:stack-trace ?
* Issue [55]#675: XSLT streaming rules for new constructs
* Issue [56]#501: Error handling: Rethrow errors; finally block
* Issue [57]#490: Control over schema validation in parse-xml(),
doc(), etc.
* Issue [58]#407: XSLT-specific context properties used in function
items
* Issue [59]#272: Setting parameter values in xsl:use-package
* Issue [60]#69: fn:document, fn:function-available: default
arguments
2. Technical agenda
2.1. Issue #755: Expression for binding the Context Value
See issue [61]#755.
There has been a lot of discussion in this issue and a lot of
controversy. Please review the issue and be prepared to engage in
productive discussion.
Remember that we are designing a language for several different
constituencies: new users, casual users, experienced users, and expert
users, at least. We all start as new users and rise to some level of
experience with each language and to some extent each language feature.
It's reasonable to argue that a feature has implications with respect
to new users. But it's equally reasonable to argue that a feature (or
the lack of a feature) has implications for expert users.
2.2. PR #1360: 1348 Some grammar simplifications
See PR [62]#1360
2.3. PR #1364: Change to type() syntax to fix ambiguity
See PR [63]#1364
2.4. PR #1283: 77b: Update expressions
See PR [64]#1283
2.5. PR #1429: Align type tests
See PR [65]#1429
2.6. PR #1428: 1426 Add notes on endianness of CRC-32
See PR [66]#1428
2.7. PR #1393: 1391 Change function-annotations to return a sequence
See PR [67]#1393
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/09-03.html
9. https://qt4cg.org/dashboard/#pr-1414
10. https://qt4cg.org/dashboard/#pr-1355
11. https://qt4cg.org/dashboard/#pr-1296
12. https://qt4cg.org/dashboard/#pr-1227
13. https://qt4cg.org/dashboard/#pr-1209
14. https://qt4cg.org/dashboard/#pr-1185
15. https://qt4cg.org/dashboard/#pr-1062
16. https://qt4cg.org/dashboard/#pr-832
17. https://qt4cg.org/dashboard/#pr-529
18. https://qt4cg.org/dashboard/#pr-1425
19. https://qt4cg.org/dashboard/#pr-1423
20. https://qt4cg.org/dashboard/#pr-1388
21. https://qt4cg.org/dashboard/#pr-1419
22. https://qt4cg.org/dashboard/#pr-1418
23. https://qt4cg.org/dashboard/#pr-1417
24. https://qt4cg.org/dashboard/#pr-1413
25. https://qt4cg.org/dashboard/#pr-1412
26. https://qt4cg.org/dashboard/#pr-1393
27. https://github.com/qt4cg/qtspecs/issues/1385
28. https://qt4cg.org/dashboard/#pr-1388
29. https://qt4cg.org/dashboard/#pr-1418
30. https://qt4cg.org/dashboard/#pr-1414
31. https://qt4cg.org/dashboard/#pr-1378
32. https://qt4cg.org/dashboard/#pr-1429
33. https://qt4cg.org/dashboard/#pr-1428
34. https://qt4cg.org/dashboard/#pr-1393
35. https://qt4cg.org/dashboard/#pr-1364
36. https://qt4cg.org/dashboard/#pr-1360
37. https://qt4cg.org/dashboard/#pr-1283
38. https://github.com/qt4cg/qtspecs/issues/1252
39. https://github.com/qt4cg/qtspecs/issues/1240
40. https://github.com/qt4cg/qtspecs/issues/1238
41. https://github.com/qt4cg/qtspecs/issues/1235
42. https://github.com/qt4cg/qtspecs/issues/1169
43. https://github.com/qt4cg/qtspecs/issues/1127
44. https://github.com/qt4cg/qtspecs/issues/1045
45. https://github.com/qt4cg/qtspecs/issues/1021
46. https://github.com/qt4cg/qtspecs/issues/1011
47. https://github.com/qt4cg/qtspecs/issues/986
48. https://github.com/qt4cg/qtspecs/issues/967
49. https://github.com/qt4cg/qtspecs/issues/868
50. https://github.com/qt4cg/qtspecs/issues/826
51. https://github.com/qt4cg/qtspecs/issues/767
52. https://github.com/qt4cg/qtspecs/issues/755
53. https://github.com/qt4cg/qtspecs/issues/748
54. https://github.com/qt4cg/qtspecs/issues/689
55. https://github.com/qt4cg/qtspecs/issues/675
56. https://github.com/qt4cg/qtspecs/issues/501
57. https://github.com/qt4cg/qtspecs/issues/490
58. https://github.com/qt4cg/qtspecs/issues/407
59. https://github.com/qt4cg/qtspecs/issues/272
60. https://github.com/qt4cg/qtspecs/issues/69
61. https://github.com/qt4cg/qtspecs/issues/755
62. https://qt4cg.org/dashboard/#pr-1360
63. https://qt4cg.org/dashboard/#pr-1364
64. https://qt4cg.org/dashboard/#pr-1283
65. https://qt4cg.org/dashboard/#pr-1429
66. https://qt4cg.org/dashboard/#pr-1428
67. https://qt4cg.org/dashboard/#pr-1393
Be seeing you,
norm
--
Norm Tovey-Walsh
Saxonica
Received on Monday, 9 September 2024 10:28:04 UTC