- From: Norm Tovey-Walsh <norm@saxonica.com>
- Date: Mon, 24 Mar 2025 10:59:43 +0000
- To: "public-xslt-40@w3.org" <public-xslt-40@w3.org>
Hi folks,
Here’s the agenda for tomorrow’s meeting:
https://qt4cg.org/meeting/agenda/2025/03-25.html
QT4 CG Meeting 115 Agenda 2025-03-25
[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
meeting of 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 25 March 2025. The following meeting is
scheduled for 1 April 2025.
Note: The QT4CG meeting is scheduled on UK/European civil time. The
United States switched to daylight saving time on 9 March 2025 and the
UK/Europe switches on 30 March 2025. Consequently, the 1 April meeting
will be back to the "usual" time in North America (no fooling!).
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-02: NW to investigate a way to show extra attributes
in the syntax summary.
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. Substantive PRs
The following substantive PRs were open when this agenda was prepared.
* PR [12]#1890: More examples added to fn:chain
* PR [13]#1888: 366 xsl:package-location
* PR [14]#1887: 1870 rename $zero keyword of fold functions
* PR [15]#1886: 1660 Additional options for fn:path
* PR [16]#1883: 882 Replace fn:chain by fn:compose
* PR [17]#1875: 1861 Params passed automatically through next-match
* PR [18]#1874: 1862 Coercing to a record type changes map order
* PR [19]#1858: Initial xsl:record
* PR [20]#1819: 451 Multiple schemas in XSLT
* PR [21]#1766: 1715 Drop array bound checking
* PR [22]#1587: 557 Add fn:binary-resource
1.6.3. Required for V4.0
The following issues are labeled "required for V4.0".
* Issue [23]#1777: Shallow copy in XSLT with maps and arrays
* Issue [24]#1742: Maps constructed using streamed xsl:fork
instruction should not be ordered
* Issue [25]#1584: Review the XML Schema and RELAX NG schemas for
XSLT 4.0 for compatibility
* Issue [26]#1240: $sequence-of-maps ? info()
* Issue [27]#1127: Binary resources
* Issue [28]#1045: Functions to manage namespace usage
* Issue [29]#1021: Extend `fn:doc`, `fn:collection` and
`fn:uri-collection` with options maps
* Issue [30]#1011: fn:transform() improvements
* Issue [31]#986: Numeric Comparisons
* Issue [32]#967: XPath Appendix I: Comparisons
* Issue [33]#826: Arrays: Representation of single members of an
array
* Issue [34]#748: Parse functions: consistency
* Issue [35]#714: Function annotations in XSLT
* Issue [36]#675: XSLT streaming rules for new constructs
* Issue [37]#501: Error handling: Rethrow errors; finally block
* Issue [38]#407: XSLT-specific context properties used in function
items
* Issue [39]#366: Support xsl:use-package with xsl:package-location
* Issue [40]#272: Setting parameter values in xsl:use-package
1.6.4. To be triaged
The following issues need to be triaged.
* Issue [41]#1889: HTML serialization: `html-version` and `version`
parameters; allowed values
* Issue [42]#1885: Use the spcification grammar markup to define the
regular expression grammar in F&O
* Issue [43]#1881: fn:function-identity for maps and arrays
* Issue [44]#1876: `fn:replace`: Combine $replacement and $action
parameters
* Issue [45]#1871: Arrays and maps: consistency
* Issue [46]#1870: Rename $zero keyword of fold-left and fold-right
* Issue [47]#1868: array:members() to include index position
* Issue [48]#1859: Question on `fn:chain` and `err:FOAP0001`
* Issue [49]#1852: fn:values-except: Return atomic values that occur
in A but not in B
* Issue [50]#1846: %method functions, dynamic function calls
* Issue [51]#1844: Drop mapping arrow operator
* Issue [52]#1832: Associativity of Operators, especially "||"
(Appendix A.5)
* Issue [53]#1799: "well-formed HTML document"?
* Issue [54]#1797: elements-to-maps: separate function to construct a
plan
* Issue [55]#1795: XSLT templates: Matching values in a map by key
* Issue [56]#1787: Sorted maps revisited
* Issue [57]#1775: Navigation in JSON trees
* Issue [58]#1774: Nomenclature: relabelling
* Issue [59]#1754: Inverse functions to bin:hex, bin:bin, and
bin:octal
* Issue [60]#1736: Add option retain-order=false when constructing
maps
* Issue [61]#1718: Ordered Maps: positions in callback functions
* Issue [62]#1704: Ignore the byte order mark more
completely/globally
* Issue [63]#1697: Add documentary names to callback function
signatures
* Issue [64]#1661: QName arguments: also allow strings
* Issue [65]#1660: Further suggestions for fn:path
* Issue [66]#1658: fn:elements-to-maps: `empty`, normalize space ?
* Issue [67]#1648: fn:elements-to-maps: Types
* Issue [68]#1647: fn:elements-to-maps: Explicit Layouts
* Issue [69]#1646: fn:elements-to-maps: Robustness
* Issue [70]#1645: fn:elements-to-maps: Debugging
* Issue [71]#1644: fn:elements-to-maps: Mixed Content
* Issue [72]#1624: document-node(a|b) is the same type as
document-node(a)|document-node(b)
* Issue [73]#1618: Adaptive serialization: doubles
* Issue [74]#1591: Implausible filter expressions
* Issue [75]#1583: JSON: Parsing and serializing numbers, often
undesired E notation
* Issue [76]#1568: Define a Unicode case-insensitive collation
* Issue [77]#1528: Computed node constructors: observations
* Issue [78]#1520: Type declarations of cyclically dependent modules
* Issue [79]#1484: Functions that expect a record type should make it
extensible
* Issue [80]#1479: Default element namespace in XQuery: interaction
of 'fixed' and '##any'
* Issue [81]#1459: Function properties and arities (editorial)
* Issue [82]#1416: Key-value pairs: built-in record type `pair`
* Issue [83]#1363: map:get and array:get
* Issue [84]#1310: add fn:match-groups() function
* Issue [85]#1307: For symmetry, add functions array:scan-left and
array:scan-right
* Issue [86]#1271: Schema validation in XPath
* Issue [87]#1175: XPath: Optional parameters in the definition of an
inline function
* Issue [88]#850: fn:parse-html: Finalization
* Issue [89]#760: Serialize functions: consistency
* Issue [90]#641: Serialization fallback.
* Issue [91]#119: Allow a map's key value to be any sequence
2. Technical agenda
2.1. Review of pull requests
2.1.1. PR #1883: 882 Replace fn:chain by fn:compose
See PR [92]#1883, see also PR [93]#1890: More examples added to
fn:chain
We discussed this last week; let's time box this to 15 minutes and if
we haven't reached a resolution, try to switch to working out what next
steps would help us reach a resolution.
2.1.2. PR #1875: 1861 Params passed automatically through next-match
See PR [94]#1875
2.1.3. PR #1874: 1862 Coercing to a record type changes map order
See PR [95]#1874
2.1.4. PR #1888: 366 xsl:package-location
See PR [96]#1888
2.1.5. PR #1887: 1870 rename $zero keyword of fold functions
See PR [97]#1887
2.1.6. PR #1858: Initial xsl:record
See PR [98]#1858
2.1.7. PR #1886: 1660 Additional options for fn:path
See PR [99]#1886
2.2. Issue triage
2.2.1. Issue #1832: Associativity of Operators, especially "||" (Appendix
A.5)
See issue [100]#1832
2.2.2. Issue #1799: "well-formed HTML document"?
See issue [101]#1799
2.2.3. Issue #1797: elements-to-maps: separate function to construct a plan
See issue [102]#1797
2.2.4. Issue #760: Serialize functions: consistency
See issue [103]#760
2.2.5. Issue #641: Serialization fallback.
See issue [104]#641
2.2.6. Issue #119: Allow a map's key value to be any sequence
See issue [105]#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-18.html
9. https://qt4cg.org/meeting/agenda/2025/03-25.html#technical-agenda
10. https://qt4cg.org/dashboard/#pr-1283
11. https://qt4cg.org/dashboard/#pr-1062
12. https://qt4cg.org/dashboard/#pr-1890
13. https://qt4cg.org/dashboard/#pr-1888
14. https://qt4cg.org/dashboard/#pr-1887
15. https://qt4cg.org/dashboard/#pr-1886
16. https://qt4cg.org/dashboard/#pr-1883
17. https://qt4cg.org/dashboard/#pr-1875
18. https://qt4cg.org/dashboard/#pr-1874
19. https://qt4cg.org/dashboard/#pr-1858
20. https://qt4cg.org/dashboard/#pr-1819
21. https://qt4cg.org/dashboard/#pr-1766
22. https://qt4cg.org/dashboard/#pr-1587
23. https://github.com/qt4cg/qtspecs/issues/1777
24. https://github.com/qt4cg/qtspecs/issues/1742
25. https://github.com/qt4cg/qtspecs/issues/1584
26. https://github.com/qt4cg/qtspecs/issues/1240
27. https://github.com/qt4cg/qtspecs/issues/1127
28. https://github.com/qt4cg/qtspecs/issues/1045
29. https://github.com/qt4cg/qtspecs/issues/1021
30. https://github.com/qt4cg/qtspecs/issues/1011
31. https://github.com/qt4cg/qtspecs/issues/986
32. https://github.com/qt4cg/qtspecs/issues/967
33. https://github.com/qt4cg/qtspecs/issues/826
34. https://github.com/qt4cg/qtspecs/issues/748
35. https://github.com/qt4cg/qtspecs/issues/714
36. https://github.com/qt4cg/qtspecs/issues/675
37. https://github.com/qt4cg/qtspecs/issues/501
38. https://github.com/qt4cg/qtspecs/issues/407
39. https://github.com/qt4cg/qtspecs/issues/366
40. https://github.com/qt4cg/qtspecs/issues/272
41. https://github.com/qt4cg/qtspecs/issues/1889
42. https://github.com/qt4cg/qtspecs/issues/1885
43. https://github.com/qt4cg/qtspecs/issues/1881
44. https://github.com/qt4cg/qtspecs/issues/1876
45. https://github.com/qt4cg/qtspecs/issues/1871
46. https://github.com/qt4cg/qtspecs/issues/1870
47. https://github.com/qt4cg/qtspecs/issues/1868
48. https://github.com/qt4cg/qtspecs/issues/1859
49. https://github.com/qt4cg/qtspecs/issues/1852
50. https://github.com/qt4cg/qtspecs/issues/1846
51. https://github.com/qt4cg/qtspecs/issues/1844
52. https://github.com/qt4cg/qtspecs/issues/1832
53. https://github.com/qt4cg/qtspecs/issues/1799
54. https://github.com/qt4cg/qtspecs/issues/1797
55. https://github.com/qt4cg/qtspecs/issues/1795
56. https://github.com/qt4cg/qtspecs/issues/1787
57. https://github.com/qt4cg/qtspecs/issues/1775
58. https://github.com/qt4cg/qtspecs/issues/1774
59. https://github.com/qt4cg/qtspecs/issues/1754
60. https://github.com/qt4cg/qtspecs/issues/1736
61. https://github.com/qt4cg/qtspecs/issues/1718
62. https://github.com/qt4cg/qtspecs/issues/1704
63. https://github.com/qt4cg/qtspecs/issues/1697
64. https://github.com/qt4cg/qtspecs/issues/1661
65. https://github.com/qt4cg/qtspecs/issues/1660
66. https://github.com/qt4cg/qtspecs/issues/1658
67. https://github.com/qt4cg/qtspecs/issues/1648
68. https://github.com/qt4cg/qtspecs/issues/1647
69. https://github.com/qt4cg/qtspecs/issues/1646
70. https://github.com/qt4cg/qtspecs/issues/1645
71. https://github.com/qt4cg/qtspecs/issues/1644
72. https://github.com/qt4cg/qtspecs/issues/1624
73. https://github.com/qt4cg/qtspecs/issues/1618
74. https://github.com/qt4cg/qtspecs/issues/1591
75. https://github.com/qt4cg/qtspecs/issues/1583
76. https://github.com/qt4cg/qtspecs/issues/1568
77. https://github.com/qt4cg/qtspecs/issues/1528
78. https://github.com/qt4cg/qtspecs/issues/1520
79. https://github.com/qt4cg/qtspecs/issues/1484
80. https://github.com/qt4cg/qtspecs/issues/1479
81. https://github.com/qt4cg/qtspecs/issues/1459
82. https://github.com/qt4cg/qtspecs/issues/1416
83. https://github.com/qt4cg/qtspecs/issues/1363
84. https://github.com/qt4cg/qtspecs/issues/1310
85. https://github.com/qt4cg/qtspecs/issues/1307
86. https://github.com/qt4cg/qtspecs/issues/1271
87. https://github.com/qt4cg/qtspecs/issues/1175
88. https://github.com/qt4cg/qtspecs/issues/850
89. https://github.com/qt4cg/qtspecs/issues/760
90. https://github.com/qt4cg/qtspecs/issues/641
91. https://github.com/qt4cg/qtspecs/issues/119
92. https://qt4cg.org/dashboard/#pr-1883
93. https://qt4cg.org/dashboard/#pr-1890
94. https://qt4cg.org/dashboard/#pr-1875
95. https://qt4cg.org/dashboard/#pr-1874
96. https://qt4cg.org/dashboard/#pr-1888
97. https://qt4cg.org/dashboard/#pr-1887
98. https://qt4cg.org/dashboard/#pr-1858
99. https://qt4cg.org/dashboard/#pr-1886
100. https://github.com/qt4cg/qtspecs/issues/1832
101. https://github.com/qt4cg/qtspecs/issues/1799
102. https://github.com/qt4cg/qtspecs/issues/1797
103. https://github.com/qt4cg/qtspecs/issues/760
104. https://github.com/qt4cg/qtspecs/issues/641
105. https://github.com/qt4cg/qtspecs/issues/119
Be seeing you,
norm
--
Norm Tovey-Walsh
Saxonica
Received on Monday, 24 March 2025 10:59:51 UTC