- From: Norm Tovey-Walsh <norm@saxonica.com>
- Date: Mon, 17 Mar 2025 12:12:09 +0000
- To: "public-xslt-40@w3.org" <public-xslt-40@w3.org>
Hello,
Here’s the draft agenda for tomorrow’s meeting:
https://qt4cg.org/meeting/agenda/2025/03-18.html
QT4 CG Meeting 114 Agenda 2025-03-18
[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:00GMT (17:00CET, 12:00EDT)
The [6]Zoom meeting ID is 831 9996 6275; the passcode is 707664.
See the [7]meeting logistics page for more details.
Note: The QT4CG meeting is scheduled on UK/European civil time. The
United States switched to daylight saving time on 9 March 2025, so the
meetings of 11, 18, and 25 March will be one hour later there (12:00
EDT, 09:00 PDT) until the UK/Europe also switches (on 30 March 2025).
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 18 March 2025. The following meeting is
scheduled for 25 March 2025.
Note: The QT4CG meeting is scheduled on UK/European civil time. The
United States switched to daylight saving time on 9 March 2025, so the
meetings of 18 and 25 March will be one hour later there (12:00 EDT,
09:00 PDT) until the UK/Europe also switches (on 30 March 2025).
1.5. Review of open action items [0/7]
(Items marked [X] are believed to have been closed via email before
this agenda was posted.)
* [ ] QT4CG-082-02: DN to work with NW to come to agreement on the
fn:ranks proposal
* [ ] QT4CG-107-05: JLO and DN to consider a proposal for system
defined records.
* [ ] QT4CG-110-04: JK to consider a PR for #366, xsl:use-package
with xsl:package-location
* [ ] QT4CG-112-01: JLO to propose a concrete example that uses "."
in a ~%method~s.
* [ ] QT4CG-113-01: MK to make a PR to drop the position callback on
fold-left/fold-right
* [ ] QT4CG-113-02: NW to investigate a way to show extra attributes
in the syntax summary.
* [ ] QT4CG-113-03: JWL to consider shadow attributes and all the
other standard attributes on xsl:record.
1.6. Review of open pull requests and issues
This section summarizes all of the issues and pull requests that need
to be resolved before we can finish. See [9]Technical Agenda below for
the focus of this meeting.
1.6.1. Blocked
The following PRs are open but have merge conflicts or comments which
suggest they aren't ready for action.
* PR [10]#1283: 77b Update expressions
* PR [11]#1062: 150bis revised proposal for fn:ranks
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 [12]#1880: Editorial revision of fn:function-identity
* PR [13]#1878: 1851 Make ?variety optional; explain
namespace-sensitive
* PR [14]#1875: 1861 Params passed automatically through next-match
* PR [15]#1873: 1869 duplicate values
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 [16]#1863: add \U \u L \u \E to replace() (case conversion)
1.6.4. Substantive PRs
The following substantive PRs were open when this agenda was prepared.
(Note that the PRs to be discussed are listed in the [17]technical
agenda below.)
* PR [18]#1883: 882 Replace fn:chain by fn:compose
* PR [19]#1882: 982 Editorial rewrite of scan-left and scan-right
* PR [20]#1879: 1857, 1860: Add more options to parse-xml
* PR [21]#1877: 1866 Disambiguate TypeSpecifier syntax
* PR [22]#1874: 1862 Coercing to a record type changes map order
* PR [23]#1867: 1341 Drop position from fold callbacks
* PR [24]#1858: Initial xsl:record
* PR [25]#1856: 998 Add boundary and lookahead/behind assertions
* PR [26]#1819: 451 Multiple schemas in XSLT
* PR [27]#1766: 1715 Drop array bound checking
* PR [28]#1587: 557 Add fn:binary-resource
1.6.5. Required for V4.0
The following issues are labeled "required for V4.0".
* Issue [29]#1777: Shallow copy in XSLT with maps and arrays
* Issue [30]#1742: Maps constructed using streamed xsl:fork
instruction should not be ordered
* Issue [31]#1584: Review the XML Schema and RELAX NG schemas for
XSLT 4.0 for compatibility
* Issue [32]#1240: $sequence-of-maps ? info()
* Issue [33]#1127: Binary resources
* Issue [34]#1045: Functions to manage namespace usage
* Issue [35]#1021: Extend `fn:doc`, `fn:collection` and
`fn:uri-collection` with options maps
* Issue [36]#1011: fn:transform() improvements
* Issue [37]#986: Numeric Comparisons
* Issue [38]#967: XPath Appendix I: Comparisons
* Issue [39]#826: Arrays: Representation of single members of an
array
* Issue [40]#748: Parse functions: consistency
* Issue [41]#714: Function annotations in XSLT
* Issue [42]#675: XSLT streaming rules for new constructs
* Issue [43]#501: Error handling: Rethrow errors; finally block
* Issue [44]#407: XSLT-specific context properties used in function
items
* Issue [45]#366: Support xsl:use-package with xsl:package-location
* Issue [46]#272: Setting parameter values in xsl:use-package
1.6.6. To be triaged
The following issues need to be triaged.
* Issue [47]#1881: fn:function-identity for maps and arrays
* Issue [48]#1876: `fn:replace`: Combine $replacement and $action
parameters
* Issue [49]#1871: Arrays and maps: consistency
* Issue [50]#1870: Rename $zero keyword of fold-left and fold-right
* Issue [51]#1868: array:members() to include index position
* Issue [52]#1863: add \U \u L \u \E to replace() (case conversion)
* Issue [53]#1859: Question on `fn:chain` and `err:FOAP0001`
* Issue [54]#1852: fn:values-except: Return atomic values that occur
in A but not in B
* Issue [55]#1846: %method functions, dynamic function calls
* Issue [56]#1844: Drop mapping arrow operator
* Issue [57]#1832: Associativity of Operators, especially "||"
(Appendix A.5)
* Issue [58]#1799: "well-formed HTML document"?
* Issue [59]#1797: elements-to-maps: separate function to construct a
plan
* Issue [60]#1795: XSLT templates: Matching values in a map by key
* Issue [61]#1787: Sorted maps revisited
* Issue [62]#1775: Navigation in JSON trees
* Issue [63]#1774: Nomenclature: relabelling
* Issue [64]#1754: Inverse functions to bin:hex, bin:bin, and
bin:octal
* Issue [65]#1736: Add option retain-order=false when constructing
maps
* Issue [66]#1718: Ordered Maps: positions in callback functions
* Issue [67]#1704: Ignore the byte order mark more
completely/globally
* Issue [68]#1697: Add documentary names to callback function
signatures
* Issue [69]#1661: QName arguments: also allow strings
* Issue [70]#1660: Further suggestions for fn:path
* Issue [71]#1658: fn:elements-to-maps: `empty`, normalize space ?
* Issue [72]#1648: fn:elements-to-maps: Types
* Issue [73]#1647: fn:elements-to-maps: Explicit Layouts
* Issue [74]#1646: fn:elements-to-maps: Robustness
* Issue [75]#1645: fn:elements-to-maps: Debugging
* Issue [76]#1644: fn:elements-to-maps: Mixed Content
* Issue [77]#1624: document-node(a|b) is the same type as
document-node(a)|document-node(b)
* Issue [78]#1618: Adaptive serialization: doubles
* Issue [79]#1591: Implausible filter expressions
* Issue [80]#1583: JSON: Parsing and serializing numbers, often
undesired E notation
* Issue [81]#1568: Define a Unicode case-insensitive collation
* Issue [82]#1528: Computed node constructors: observations
* Issue [83]#1520: Type declarations of cyclically dependent modules
* Issue [84]#1484: Functions that expect a record type should make it
extensible
* Issue [85]#1479: Default element namespace in XQuery: interaction
of 'fixed' and '##any'
* Issue [86]#1459: Function properties and arities (editorial)
* Issue [87]#1416: Key-value pairs: built-in record type `pair`
* Issue [88]#1363: map:get and array:get
* Issue [89]#1310: add fn:match-groups() function
* Issue [90]#1307: For symmetry, add functions array:scan-left and
array:scan-right
* Issue [91]#1271: Schema validation in XPath
* Issue [92]#1175: XPath: Optional parameters in the definition of an
inline function
* Issue [93]#850: fn:parse-html: Finalization
* Issue [94]#760: Serialize functions: consistency
* Issue [95]#641: Serialization fallback.
* Issue [96]#119: Allow a map's key value to be any sequence
2. Technical agenda
2.1. Review of pull requests
2.1.1. PR #1877: 1866 Disambiguate TypeSpecifier syntax
See PR [97]#1877
I was tempted to mark this one merge-without-discussion, but let's see
if we all agree on the proposed syntactic change.
2.1.2. PR #1882: 982 Editorial rewrite of scan-left and scan-right
See PR [98]#1882
I was tempted to mark this one merge-without-discussion, but there's an
open comment on the PR (but not an especially substantive one, AFAICT).
2.1.3. PR #1879: 1857, 1860: Add more options to parse-xml
See PR [99]#1879
I was tempted to mark this one merge-without-discussion, but some brief
discussion of entity-expansion-limit may be in order.
2.1.4. PR #1856: 998 Add boundary and lookahead/behind assertions
See PR [100]#1856
2.1.5. PR #1867: 1341 Drop position from fold callbacks
See PR [101]#1867
2.1.6. PR #1883: 882 Replace fn:chain by fn:compose
See PR [102]#1883
2.1.7. PR #1875: 1861 Params passed automatically through next-match
See PR [103]#1875
2.1.8. PR #1874: 1862 Coercing to a record type changes map order
See PR [104]#1874
2.2. Issue triage
2.2.1. Issue #1832: Associativity of Operators, especially "||" (Appendix
A.5)
See issue [105]#1832
2.2.2. Issue #1799: "well-formed HTML document"?
See issue [106]#1799
2.2.3. Issue #1797: elements-to-maps: separate function to construct a plan
See issue [107]#1797
2.2.4. Issue #760: Serialize functions: consistency
See issue [108]#760
2.2.5. Issue #641: Serialization fallback.
See issue [109]#641
2.2.6. Issue #119: Allow a map's key value to be any sequence
See issue [110]#119
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/2025/03-11.html
9. https://qt4cg.org/meeting/agenda/2025/03-18.html#technical-agenda
10. https://qt4cg.org/dashboard/#pr-1283
11. https://qt4cg.org/dashboard/#pr-1062
12. https://qt4cg.org/dashboard/#pr-1880
13. https://qt4cg.org/dashboard/#pr-1878
14. https://qt4cg.org/dashboard/#pr-1875
15. https://qt4cg.org/dashboard/#pr-1873
16. https://github.com/qt4cg/qtspecs/issues/1863
17. https://qt4cg.org/meeting/agenda/2025/03-18.html#technical-agenda
18. https://qt4cg.org/dashboard/#pr-1883
19. https://qt4cg.org/dashboard/#pr-1882
20. https://qt4cg.org/dashboard/#pr-1879
21. https://qt4cg.org/dashboard/#pr-1877
22. https://qt4cg.org/dashboard/#pr-1874
23. https://qt4cg.org/dashboard/#pr-1867
24. https://qt4cg.org/dashboard/#pr-1858
25. https://qt4cg.org/dashboard/#pr-1856
26. https://qt4cg.org/dashboard/#pr-1819
27. https://qt4cg.org/dashboard/#pr-1766
28. https://qt4cg.org/dashboard/#pr-1587
29. https://github.com/qt4cg/qtspecs/issues/1777
30. https://github.com/qt4cg/qtspecs/issues/1742
31. https://github.com/qt4cg/qtspecs/issues/1584
32. https://github.com/qt4cg/qtspecs/issues/1240
33. https://github.com/qt4cg/qtspecs/issues/1127
34. https://github.com/qt4cg/qtspecs/issues/1045
35. https://github.com/qt4cg/qtspecs/issues/1021
36. https://github.com/qt4cg/qtspecs/issues/1011
37. https://github.com/qt4cg/qtspecs/issues/986
38. https://github.com/qt4cg/qtspecs/issues/967
39. https://github.com/qt4cg/qtspecs/issues/826
40. https://github.com/qt4cg/qtspecs/issues/748
41. https://github.com/qt4cg/qtspecs/issues/714
42. https://github.com/qt4cg/qtspecs/issues/675
43. https://github.com/qt4cg/qtspecs/issues/501
44. https://github.com/qt4cg/qtspecs/issues/407
45. https://github.com/qt4cg/qtspecs/issues/366
46. https://github.com/qt4cg/qtspecs/issues/272
47. https://github.com/qt4cg/qtspecs/issues/1881
48. https://github.com/qt4cg/qtspecs/issues/1876
49. https://github.com/qt4cg/qtspecs/issues/1871
50. https://github.com/qt4cg/qtspecs/issues/1870
51. https://github.com/qt4cg/qtspecs/issues/1868
52. https://github.com/qt4cg/qtspecs/issues/1863
53. https://github.com/qt4cg/qtspecs/issues/1859
54. https://github.com/qt4cg/qtspecs/issues/1852
55. https://github.com/qt4cg/qtspecs/issues/1846
56. https://github.com/qt4cg/qtspecs/issues/1844
57. https://github.com/qt4cg/qtspecs/issues/1832
58. https://github.com/qt4cg/qtspecs/issues/1799
59. https://github.com/qt4cg/qtspecs/issues/1797
60. https://github.com/qt4cg/qtspecs/issues/1795
61. https://github.com/qt4cg/qtspecs/issues/1787
62. https://github.com/qt4cg/qtspecs/issues/1775
63. https://github.com/qt4cg/qtspecs/issues/1774
64. https://github.com/qt4cg/qtspecs/issues/1754
65. https://github.com/qt4cg/qtspecs/issues/1736
66. https://github.com/qt4cg/qtspecs/issues/1718
67. https://github.com/qt4cg/qtspecs/issues/1704
68. https://github.com/qt4cg/qtspecs/issues/1697
69. https://github.com/qt4cg/qtspecs/issues/1661
70. https://github.com/qt4cg/qtspecs/issues/1660
71. https://github.com/qt4cg/qtspecs/issues/1658
72. https://github.com/qt4cg/qtspecs/issues/1648
73. https://github.com/qt4cg/qtspecs/issues/1647
74. https://github.com/qt4cg/qtspecs/issues/1646
75. https://github.com/qt4cg/qtspecs/issues/1645
76. https://github.com/qt4cg/qtspecs/issues/1644
77. https://github.com/qt4cg/qtspecs/issues/1624
78. https://github.com/qt4cg/qtspecs/issues/1618
79. https://github.com/qt4cg/qtspecs/issues/1591
80. https://github.com/qt4cg/qtspecs/issues/1583
81. https://github.com/qt4cg/qtspecs/issues/1568
82. https://github.com/qt4cg/qtspecs/issues/1528
83. https://github.com/qt4cg/qtspecs/issues/1520
84. https://github.com/qt4cg/qtspecs/issues/1484
85. https://github.com/qt4cg/qtspecs/issues/1479
86. https://github.com/qt4cg/qtspecs/issues/1459
87. https://github.com/qt4cg/qtspecs/issues/1416
88. https://github.com/qt4cg/qtspecs/issues/1363
89. https://github.com/qt4cg/qtspecs/issues/1310
90. https://github.com/qt4cg/qtspecs/issues/1307
91. https://github.com/qt4cg/qtspecs/issues/1271
92. https://github.com/qt4cg/qtspecs/issues/1175
93. https://github.com/qt4cg/qtspecs/issues/850
94. https://github.com/qt4cg/qtspecs/issues/760
95. https://github.com/qt4cg/qtspecs/issues/641
96. https://github.com/qt4cg/qtspecs/issues/119
97. https://qt4cg.org/dashboard/#pr-1877
98. https://qt4cg.org/dashboard/#pr-1882
99. https://qt4cg.org/dashboard/#pr-1879
100. https://qt4cg.org/dashboard/#pr-1856
101. https://qt4cg.org/dashboard/#pr-1867
102. https://qt4cg.org/dashboard/#pr-1883
103. https://qt4cg.org/dashboard/#pr-1875
104. https://qt4cg.org/dashboard/#pr-1874
105. https://github.com/qt4cg/qtspecs/issues/1832
106. https://github.com/qt4cg/qtspecs/issues/1799
107. https://github.com/qt4cg/qtspecs/issues/1797
108. https://github.com/qt4cg/qtspecs/issues/760
109. https://github.com/qt4cg/qtspecs/issues/641
110. https://github.com/qt4cg/qtspecs/issues/119
Be seeing you,
norm
--
Norm Tovey-Walsh
Saxonica
Received on Monday, 17 March 2025 12:12:16 UTC