- From: Norm Tovey-Walsh <norm@saxonica.com>
- Date: Mon, 24 Feb 2025 12:04:04 +0000
- To: "public-xslt-40@w3.org" <public-xslt-40@w3.org>
Hello,
Here’s the proposed agenda for tomorrow’s meeting:
https://qt4cg.org/meeting/agenda/2025/02-25.html
QT4 CG Meeting 111 Agenda 2025-02-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, 11:00EST)
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 25 February 2025. The following meeting is
scheduled for 4 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 MK to come to agreement on the
fn:ranks proposal
* [ ] QT4CG-097-02: MK to make the XSD schema component references
into links to XSD
* [ ] QT4CG-107-05: JLO and DN to consider a proposal for system
defined records.
* [ ] QT4CG-110-01: MK to fix the incorrect termrefs in the data
model the merge the PR.
* [ ] QT4CG-110-02: MK to review the error pointed out in one of the
examples for arrow expressions and then merge
* [ ] QT4CG-110-03: JWL to consider writing a PR for issue #322,
xsl:record instruction
* [ ] QT4CG-110-04: JK to consider a PR for #366, xsl:use-package
with xsl:package-location
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]#1766: 1715 Drop array bound checking
* PR [11]#1587: 557 Add fn:binary-resource
* PR [12]#1296: 982 Rewrite of scan-left and scan-right
* PR [13]#1283: 77b Update expressions
* PR [14]#1062: 150bis revised proposal for fn:ranks
* PR [15]#1227: 150 PR resubmission 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 [16]#1837: 1834 Additional clarification on JSON lines
* PR [17]#1826: Fix grammar bug #1818
* PR [18]#1824: 1823 Revise top-level headings in F+O spec
* PR [19]#1814: 1813 Reorganise the XDM spec at top level
* PR [20]#1812: 1811 Add note regarding non-XML chars in
xsl:output-character
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 [21]#998: regular expression addition - lookbehind assertions
and lookahead assertions
* Issue [22]#119: Allow a map's key value to be any sequence
1.6.4. Substantive PRs
The following substantive PRs were open when this agenda was prepared.
* PR [23]#1833: 583 Drop map:replace and array:replace
* PR [24]#1830: 1829 Reintroduce restrictions on RHS of `=>`
* PR [25]#1828: 1815 Add more detail on annotations of function items
* PR [26]#1825: 1816 New function fn:partial-apply
* PR [27]#1817: 1800 Methods
* PR [28]#1801: 1798 Function fn:function-identity
* PR [29]#1735: 1341 Drop $position callback from many functions
* PR [30]#1740: 1725b Further elaboration of duplicates handling in
maps
* PR [31]#1778: 1456 Lookup expressions filtered by type
* PR [32]#1819: 451 Multiple schemas in XSLT
1.6.5. Required for V4.0
The following issues are labeled "required for V4.0".
* Issue [33]#1777: Shallow copy in XSLT with maps and arrays
* Issue [34]#1742: Maps constructed using streamed xsl:fork
instruction should not be ordered
* Issue [35]#1584: Review the XML Schema and RELAX NG schemas for
XSLT 4.0 for compatibility
* Issue [36]#1240: $sequence-of-maps ? info()
* Issue [37]#1127: Binary resources
* Issue [38]#1045: Functions to manage namespace usage
* Issue [39]#1021: Extend `fn:doc`, `fn:collection` and
`fn:uri-collection` with options maps
* Issue [40]#1011: fn:transform() improvements
* Issue [41]#986: Numeric Comparisons
* Issue [42]#967: XPath Appendix I: Comparisons
* Issue [43]#826: Arrays: Representation of single members of an
array
* Issue [44]#748: Parse functions: consistency
* Issue [45]#714: Function annotations in XSLT
* Issue [46]#675: XSLT streaming rules for new constructs
* Issue [47]#501: Error handling: Rethrow errors; finally block
* Issue [48]#407: XSLT-specific context properties used in function
items
* Issue [49]#366: Support xsl:use-package with xsl:package-location
* Issue [50]#272: Setting parameter values in xsl:use-package
1.6.6. To be triaged
The following issues need to be triaged.
* Issue [51]#1836: unparsed-text-lines() - line endings
* 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]#1796: Allow fn:invisible-xml to return a function that
returns an item()
* Issue [56]#1795: Matching values in a map by key
* Issue [57]#1794: Lookup: select all except
* Issue [58]#1787: Sorted maps revisited
* Issue [59]#1786: A case study for XSLT transformation of JSON: the
transpiler
* Issue [60]#1780: xsl:for-each optional variable introduction
* Issue [61]#1775: Navigation in JSON trees
* Issue [62]#1774: Nomenclature: relabelling
* Issue [63]#1771: fn:deep-equal: map order
* 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]#1702: Node Updates: Functions
* Issue [69]#1697: Add documentary names to callback function
signatures
* Issue [70]#1661: QName arguments: also allow strings
* Issue [71]#1660: Further suggestions for fn:path
* Issue [72]#1658: fn:elements-to-maps: `empty`, normalize space ?
* Issue [73]#1656: Ordered Maps: Updates
* Issue [74]#1648: fn:elements-to-maps: Types
* Issue [75]#1647: fn:elements-to-maps: Explicit Layouts
* Issue [76]#1646: fn:elements-to-maps: Robustness
* Issue [77]#1645: fn:elements-to-maps: Debugging
* Issue [78]#1644: fn:elements-to-maps: Mixed Content
* Issue [79]#1624: document-node(a|b) is the same type as
document-node(a)|document-node(b)
* Issue [80]#1618: Adaptive serialization: doubles
* Issue [81]#1591: Implausible filter expressions
* Issue [82]#1583: JSON: Parsing and serializing numbers, often
undesired E notation
* Issue [83]#1568: Define a Unicode case-insensitive collation
* Issue [84]#1566: EXPath Modules: Future
* Issue [85]#1528: Computed node constructors: observations
* Issue [86]#1520: Type declarations of cyclically dependent modules
* Issue [87]#1514: Editorial: optional position argument in function
signature for for-each and other HOF
* Issue [88]#1484: Functions that expect a record type should make it
extensible
* Issue [89]#1479: Default element namespace in XQuery: interaction
of 'fixed' and '##any'
* Issue [90]#1459: Function properties and arities (editorial)
* Issue [91]#1416: Key-value pairs: built-in record type `pair`
* Issue [92]#1363: map:get and array:get
* Issue [93]#1340: Namespace nodes and the namespace axis
* Issue [94]#1338: Arrays and maps: Members, entries, values,
contents, pairs, ...
* Issue [95]#1319: Specification Documents: Editors and Contributors
* Issue [96]#1310: add fn:match-groups() function
* Issue [97]#1307: For symmetry, add functions array:scan-left and
array:scan-right
* Issue [98]#1271: Schema validation in XPath
* Issue [99]#1175: XPath: Optional parameters in the definition of an
inline function
* Issue [100]#850: fn:parse-html: Finalization
* Issue [101]#760: Serialize functions: consistency
* Issue [102]#641: Serialization fallback.
* Issue [103]#119: Allow a map's key value to be any sequence
2. Technical agenda
2.1. Review of pull requests
I don't actually think we'll get through all of these. Let's reserve 15
minutes at the end of the call for issue triage. See the list below.
2.1.1. PR #1833: 583 Drop map:replace and array:replace
See PR [104]#1833
2.1.2. PR #1830: 1829 Reintroduce restrictions on RHS of `=>`
See PR [105]#1830
2.1.3. PR #1828: 1815 Add more detail on annotations of function items
See PR [106]#1828
2.1.4. PR #1825: 1816 New function fn:partial-apply
See PR [107]#1825
2.1.5. PR #1817: 1800 Methods
See PR [108]#1817
2.1.6. PR #1801: 1798 Function fn:function-identity
See PR [109]#1801
2.1.7. PR #1735: 1341 Drop $position callback from many functions
See PR [110]#1735
2.1.8. PR #1740: 1725b Further elaboration of duplicates handling in maps
See PR [111]#1740
2.1.9. PR #1778: 1456 Lookup expressions filtered by type
See PR [112]#1778
2.1.10. PR #1819: 451 Multiple schemas in XSLT
See PR [113]#1819
2.2. Issue triage
2.2.1. Issue #1836: unparsed-text-lines() - line endings
See issue [114]#1836
2.2.2. Issue #1832: Associativity of Operators, especially "||" (Appendix
A.5)
See issue [115]#1832
2.2.3. Issue #1799: "well-formed HTML document"?
See issue [116]#1799
2.2.4. Issue #1797: elements-to-maps: separate function to construct a plan
See issue [117]#1797
2.2.5. Issue #760: Serialize functions: consistency
See issue [118]#760
2.2.6. Issue #641: Serialization fallback.
See issue [119]#641
2.2.7. Issue #119: Allow a map's key value to be any sequence
See issue [120]#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/02-18.html
9. https://qt4cg.org/meeting/agenda/2025/02-25.html#technical-agenda
10. https://qt4cg.org/dashboard/#pr-1766
11. https://qt4cg.org/dashboard/#pr-1587
12. https://qt4cg.org/dashboard/#pr-1296
13. https://qt4cg.org/dashboard/#pr-1283
14. https://qt4cg.org/dashboard/#pr-1062
15. https://qt4cg.org/dashboard/#pr-1227
16. https://qt4cg.org/dashboard/#pr-1837
17. https://qt4cg.org/dashboard/#pr-1826
18. https://qt4cg.org/dashboard/#pr-1824
19. https://qt4cg.org/dashboard/#pr-1814
20. https://qt4cg.org/dashboard/#pr-1812
21. https://github.com/qt4cg/qtspecs/issues/998
22. https://github.com/qt4cg/qtspecs/issues/119
23. https://qt4cg.org/dashboard/#pr-1833
24. https://qt4cg.org/dashboard/#pr-1830
25. https://qt4cg.org/dashboard/#pr-1828
26. https://qt4cg.org/dashboard/#pr-1825
27. https://qt4cg.org/dashboard/#pr-1817
28. https://qt4cg.org/dashboard/#pr-1801
29. https://qt4cg.org/dashboard/#pr-1735
30. https://qt4cg.org/dashboard/#pr-1740
31. https://qt4cg.org/dashboard/#pr-1778
32. https://qt4cg.org/dashboard/#pr-1819
33. https://github.com/qt4cg/qtspecs/issues/1777
34. https://github.com/qt4cg/qtspecs/issues/1742
35. https://github.com/qt4cg/qtspecs/issues/1584
36. https://github.com/qt4cg/qtspecs/issues/1240
37. https://github.com/qt4cg/qtspecs/issues/1127
38. https://github.com/qt4cg/qtspecs/issues/1045
39. https://github.com/qt4cg/qtspecs/issues/1021
40. https://github.com/qt4cg/qtspecs/issues/1011
41. https://github.com/qt4cg/qtspecs/issues/986
42. https://github.com/qt4cg/qtspecs/issues/967
43. https://github.com/qt4cg/qtspecs/issues/826
44. https://github.com/qt4cg/qtspecs/issues/748
45. https://github.com/qt4cg/qtspecs/issues/714
46. https://github.com/qt4cg/qtspecs/issues/675
47. https://github.com/qt4cg/qtspecs/issues/501
48. https://github.com/qt4cg/qtspecs/issues/407
49. https://github.com/qt4cg/qtspecs/issues/366
50. https://github.com/qt4cg/qtspecs/issues/272
51. https://github.com/qt4cg/qtspecs/issues/1836
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/1796
56. https://github.com/qt4cg/qtspecs/issues/1795
57. https://github.com/qt4cg/qtspecs/issues/1794
58. https://github.com/qt4cg/qtspecs/issues/1787
59. https://github.com/qt4cg/qtspecs/issues/1786
60. https://github.com/qt4cg/qtspecs/issues/1780
61. https://github.com/qt4cg/qtspecs/issues/1775
62. https://github.com/qt4cg/qtspecs/issues/1774
63. https://github.com/qt4cg/qtspecs/issues/1771
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/1702
69. https://github.com/qt4cg/qtspecs/issues/1697
70. https://github.com/qt4cg/qtspecs/issues/1661
71. https://github.com/qt4cg/qtspecs/issues/1660
72. https://github.com/qt4cg/qtspecs/issues/1658
73. https://github.com/qt4cg/qtspecs/issues/1656
74. https://github.com/qt4cg/qtspecs/issues/1648
75. https://github.com/qt4cg/qtspecs/issues/1647
76. https://github.com/qt4cg/qtspecs/issues/1646
77. https://github.com/qt4cg/qtspecs/issues/1645
78. https://github.com/qt4cg/qtspecs/issues/1644
79. https://github.com/qt4cg/qtspecs/issues/1624
80. https://github.com/qt4cg/qtspecs/issues/1618
81. https://github.com/qt4cg/qtspecs/issues/1591
82. https://github.com/qt4cg/qtspecs/issues/1583
83. https://github.com/qt4cg/qtspecs/issues/1568
84. https://github.com/qt4cg/qtspecs/issues/1566
85. https://github.com/qt4cg/qtspecs/issues/1528
86. https://github.com/qt4cg/qtspecs/issues/1520
87. https://github.com/qt4cg/qtspecs/issues/1514
88. https://github.com/qt4cg/qtspecs/issues/1484
89. https://github.com/qt4cg/qtspecs/issues/1479
90. https://github.com/qt4cg/qtspecs/issues/1459
91. https://github.com/qt4cg/qtspecs/issues/1416
92. https://github.com/qt4cg/qtspecs/issues/1363
93. https://github.com/qt4cg/qtspecs/issues/1340
94. https://github.com/qt4cg/qtspecs/issues/1338
95. https://github.com/qt4cg/qtspecs/issues/1319
96. https://github.com/qt4cg/qtspecs/issues/1310
97. https://github.com/qt4cg/qtspecs/issues/1307
98. https://github.com/qt4cg/qtspecs/issues/1271
99. https://github.com/qt4cg/qtspecs/issues/1175
100. https://github.com/qt4cg/qtspecs/issues/850
101. https://github.com/qt4cg/qtspecs/issues/760
102. https://github.com/qt4cg/qtspecs/issues/641
103. https://github.com/qt4cg/qtspecs/issues/119
104. https://qt4cg.org/dashboard/#pr-1833
105. https://qt4cg.org/dashboard/#pr-1830
106. https://qt4cg.org/dashboard/#pr-1828
107. https://qt4cg.org/dashboard/#pr-1825
108. https://qt4cg.org/dashboard/#pr-1817
109. https://qt4cg.org/dashboard/#pr-1801
110. https://qt4cg.org/dashboard/#pr-1735
111. https://qt4cg.org/dashboard/#pr-1740
112. https://qt4cg.org/dashboard/#pr-1778
113. https://qt4cg.org/dashboard/#pr-1819
114. https://github.com/qt4cg/qtspecs/issues/1836
115. https://github.com/qt4cg/qtspecs/issues/1832
116. https://github.com/qt4cg/qtspecs/issues/1799
117. https://github.com/qt4cg/qtspecs/issues/1797
118. https://github.com/qt4cg/qtspecs/issues/760
119. https://github.com/qt4cg/qtspecs/issues/641
120. https://github.com/qt4cg/qtspecs/issues/119
Be seeing you,
norm
--
Norm Tovey-Walsh
Saxonica
Received on Monday, 24 February 2025 12:04:10 UTC