- From: Norm Tovey-Walsh <norm@saxonica.com>
- Date: Mon, 16 Feb 2026 12:49:34 +0000
- To: public-xslt-40@w3.org
Hello,
Here’s the proposed agenda for tomorrow. Please come prepared to discuss the open issues.
https://qt4cg.org/meeting/agenda/2026/02-17.html
QT4 CG Meeting 153 Agenda 2026-02-17
[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).
See the [6]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 [7]the previous meeting.
1.4. Next meeting
This meeting is planned for 17 February 2026.
The next meeting is planned for 24 February 2026.
1.5. Review of open action items [1/10]
* [ ] QT4CG-143-02: MK to try to recover the ability to extract
formal equivalences into tests
* [ ] QT4CG-143-03: JK to look for C14N test suites.
* [ ] QT4CG-144-01: MK to consider if any now lost value comparisons
should be added as examples.
* [ ] QT4CG-149-01: CG to draft a new PR with the common rule note.
* [ ] QT4CG-150-01: NW to ask Jirka for a room at XML Prague for
Tuesday/Wednesday
* [X] QT4CG-150-03: NW to setup an agenda item to review open issues
* [ ] QT4CG-150-04: NW to see about a status update on PR #2345;
possibly schedule discussion
* [ ] QT4CG-151-01: MK to fix the typo in the build-dateTime
function.
* [ ] QT4CG-151-03: NW to investigate why records are formatted
incorrectly in XSLT
* [ ] QT4CG-152-01: MK to add a note about the new and old syntax for
names in PR #2446
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 [8]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 [9]#2350: 708 An alternative proposal for generators
* PR [10]#2345: 2299 Expand pipeline to allow arrow expression in
path expression
* PR [11]#2313: 2298 XQFO rules: definition of default values
* PR [12]#2266: 540 system-property equivalent for XQuery
* PR [13]#2247: 716 Deferred Evaluation in XPath - the f:generator
record
* PR [14]#2160: 2073 data model changes for JNodes and Sequences
* PR [15]#2071: 77c deep update
* PR [16]#2019: 1776: XSLT template rules for maps and array
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 [17]#2446: 2427 Add computed node constructors to XPath
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 [18]#2234: Replace `a/get(XX)` with `a/?(XX)`
1.6.4. Substantive PRs
The following substantive PRs were open when this agenda was prepared.
* PR [19]#2457: Improved use of fos:result
* PR [20]#2456: Stylesheet handling of fos:result/@narrative
1.6.5. Required for V4.0
The following issues are labeled "required for V4.0".
* Issue [21]#1777: Shallow copy in XSLT with maps and arrays
* Issue [22]#1584: Review the XML Schema and RELAX NG schemas for
XSLT 4.0 for compatibility
* Issue [23]#1045: Functions to manage namespace usage
* Issue [24]#675: XSLT streaming rules for new constructs
* Issue [25]#272: Setting parameter values in xsl:use-package
1.6.6. To be triaged
The following issues need to be triaged.
* Issue [26]#2465: Error description of FODC0006 should be more
generic
* Issue [27]#2464: add method to use path()
* Issue [28]#2463: Add map:apply() or third argument to fn:apply() as
a map of names to parameter values.
* Issue [29]#2462: Revert dynamic function calls on sequences
* Issue [30]#2461: Unparsed entities
* Issue [31]#2460: [32]read-text and invalid XML characters
* Issue [33]#2459: What are "invalid XML characters" in the XPath
file read functions?
* Issue [34]#2458: NodeTests: Unify jnode(X) and get(X)
* Issue [35]#2455: `[36]copy`: creating targets
* Issue [37]#2454: Grammar: literals & constants, negative numbers
* Issue [38]#2448: Change title of XPath specification
* Issue [39]#2433: `fn:jtree`: Identity
* Issue [40]#2408: Editorial notes (incremental)
* Issue [41]#2390: methods and inheritance
* Issue [42]#2389: Adaptive Serialization: more freedom?
* Issue [43]#2388: Adaptive Serialization: function items
* Issue [44]#2381: Add facility to serialize binary values as
url-safe base64 encoded strings
* Issue [45]#2380: Use Case for Generators: News Feeds Aggregation
Using Generators
* Issue [46]#2338: Nomenclature: node(), gnode(), jnode(), xnode()
* Issue [47]#2321: Make `fn:trace` non-deterministic
* Issue [48]#2314: `fn:error`: return type `xs:error` ?
* Issue [49]#2300: `fn:doc`: determinism rules
* Issue [50]#2298: XQFO rules: definition of default values
* Issue [51]#2284: fn:csv-doc, fn:json-doc: Equivalent code,
unifications
* Issue [52]#2275: Change record constructor, to simplify updates
* Issue [53]#2263: Named record types: TODOs
* Issue [54]#2257: Record declarations without namespace
* Issue [55]#2252: Dynamic XPath Evaluation the functional way
* Issue [56]#2245: Action QT4CG-116-01: Add a specific error code for
unsupported options on doc and doc-available
* Issue [57]#2234: Replace `a/get(XX)` with `a/?(XX)`
* Issue [58]#2219: Generalize method calls to sequences
* Issue [59]#2215: XQFO xref from xml-to-json() to element-to-map()
* Issue [60]#2198: Serialization parameter: `conditional-cdata`
* Issue [61]#2169: Longest-token rule incorrectly produces
`StringInterpolation` delimiter
* Issue [62]#2128: JNodes and XSLT Streaming
* Issue [63]#2052: fn:collation-available: $usage
* Issue [64]#2039: Generalize context item to context value in XSLT
* Issue [65]#2018: Type-checking the result of xsl:apply-templates
* Issue [66]#2000: element-to-map() - type signature of plan
* Issue [67]#1979: Records: Type Safety
* Issue [68]#1949: fn:element-to-map: Updated Feedback
* Issue [69]#1948: fn:element-to-map: Tests
* Issue [70]#1920: Parse functions: determinism
* Issue [71]#1697: Add documentary names to callback function
signatures
* Issue [72]#1528: Computed node constructors: observations
* Issue [73]#1479: Default element namespace in XQuery: interaction
of 'fixed' and '##any'
* Issue [74]#1459: Function properties and arities
* Issue [75]#1310: add fn:match-groups() function
* Issue [76]#641: Serialization fallback
2. Technical agenda
2.1. Improvements to FOS
See PR [77]#2457 Improved use of fos:result, and PR [78]#2456:
Stylesheet handling of fos:result/@narrative
2.2. Issue #2460: [79]read-text and invalid XML characters
See issue [80]#2460: [81]read-text and invalid XML characters
Perhaps we can decide what needs to be done here.
2.3. Other issue triage
Proposals for how to proceed most humbly solicited. In the absense of
any such proposal, I think a good first step would be to look over the
78 open issues and divide them into "required for 4.0" and "nice to
have" and perhaps even "close with no further action." Any we can't
decide on, we can just leave for another day.
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://qt4cg.org/meeting/logistics.html
7. https://qt4cg.org/meeting/minutes/2026/02-10.html
8. https://qt4cg.org/meeting/agenda/2026/02-17.html#technical-agenda
9. https://qt4cg.org/dashboard/#pr-2350
10. https://qt4cg.org/dashboard/#pr-2345
11. https://qt4cg.org/dashboard/#pr-2313
12. https://qt4cg.org/dashboard/#pr-2266
13. https://qt4cg.org/dashboard/#pr-2247
14. https://qt4cg.org/dashboard/#pr-2160
15. https://qt4cg.org/dashboard/#pr-2071
16. https://qt4cg.org/dashboard/#pr-2019
17. https://qt4cg.org/dashboard/#pr-2446
18. https://github.com/qt4cg/qtspecs/issues/2234
19. https://qt4cg.org/dashboard/#pr-2457
20. https://qt4cg.org/dashboard/#pr-2456
21. https://github.com/qt4cg/qtspecs/issues/1777
22. https://github.com/qt4cg/qtspecs/issues/1584
23. https://github.com/qt4cg/qtspecs/issues/1045
24. https://github.com/qt4cg/qtspecs/issues/675
25. https://github.com/qt4cg/qtspecs/issues/272
26. https://github.com/qt4cg/qtspecs/issues/2465
27. https://github.com/qt4cg/qtspecs/issues/2464
28. https://github.com/qt4cg/qtspecs/issues/2463
29. https://github.com/qt4cg/qtspecs/issues/2462
30. https://github.com/qt4cg/qtspecs/issues/2461
31. https://github.com/qt4cg/qtspecs/issues/2460
32. https://qt4cg.org/meeting/agenda/2026/read-text
33. https://github.com/qt4cg/qtspecs/issues/2459
34. https://github.com/qt4cg/qtspecs/issues/2458
35. https://github.com/qt4cg/qtspecs/issues/2455
36. https://qt4cg.org/meeting/agenda/2026/copy
37. https://github.com/qt4cg/qtspecs/issues/2454
38. https://github.com/qt4cg/qtspecs/issues/2448
39. https://github.com/qt4cg/qtspecs/issues/2433
40. https://github.com/qt4cg/qtspecs/issues/2408
41. https://github.com/qt4cg/qtspecs/issues/2390
42. https://github.com/qt4cg/qtspecs/issues/2389
43. https://github.com/qt4cg/qtspecs/issues/2388
44. https://github.com/qt4cg/qtspecs/issues/2381
45. https://github.com/qt4cg/qtspecs/issues/2380
46. https://github.com/qt4cg/qtspecs/issues/2338
47. https://github.com/qt4cg/qtspecs/issues/2321
48. https://github.com/qt4cg/qtspecs/issues/2314
49. https://github.com/qt4cg/qtspecs/issues/2300
50. https://github.com/qt4cg/qtspecs/issues/2298
51. https://github.com/qt4cg/qtspecs/issues/2284
52. https://github.com/qt4cg/qtspecs/issues/2275
53. https://github.com/qt4cg/qtspecs/issues/2263
54. https://github.com/qt4cg/qtspecs/issues/2257
55. https://github.com/qt4cg/qtspecs/issues/2252
56. https://github.com/qt4cg/qtspecs/issues/2245
57. https://github.com/qt4cg/qtspecs/issues/2234
58. https://github.com/qt4cg/qtspecs/issues/2219
59. https://github.com/qt4cg/qtspecs/issues/2215
60. https://github.com/qt4cg/qtspecs/issues/2198
61. https://github.com/qt4cg/qtspecs/issues/2169
62. https://github.com/qt4cg/qtspecs/issues/2128
63. https://github.com/qt4cg/qtspecs/issues/2052
64. https://github.com/qt4cg/qtspecs/issues/2039
65. https://github.com/qt4cg/qtspecs/issues/2018
66. https://github.com/qt4cg/qtspecs/issues/2000
67. https://github.com/qt4cg/qtspecs/issues/1979
68. https://github.com/qt4cg/qtspecs/issues/1949
69. https://github.com/qt4cg/qtspecs/issues/1948
70. https://github.com/qt4cg/qtspecs/issues/1920
71. https://github.com/qt4cg/qtspecs/issues/1697
72. https://github.com/qt4cg/qtspecs/issues/1528
73. https://github.com/qt4cg/qtspecs/issues/1479
74. https://github.com/qt4cg/qtspecs/issues/1459
75. https://github.com/qt4cg/qtspecs/issues/1310
76. https://github.com/qt4cg/qtspecs/issues/641
77. https://qt4cg.org/dashboard/#pr-2457
78. https://qt4cg.org/dashboard/#pr-2456
79. https://qt4cg.org/meeting/agenda/2026/read-text
80. https://github.com/qt4cg/qtspecs/issues/2460
81. https://qt4cg.org/meeting/agenda/2026/read-text
Be seeing you,
norm
--
Norm Tovey-Walsh
Saxonica
Received on Monday, 16 February 2026 12:49:40 UTC