- From: Norm Tovey-Walsh <norm@saxonica.com>
- Date: Sun, 25 May 2025 16:04:39 +0100
- To: public-xslt-40@w3.org
Hello folks,
Here’s the agenda for Tuesday’s meeting:
https://qt4cg.org/meeting/agenda/2025/05-27.html
QT4 CG Meeting 123 Agenda 2025-05-27
[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.
1.4. Next meeting
This meeting is planned for 27 May 2025. The following meeting is
scheduled for 10 June 2025. The CG will not meet on 3 June.
1.5. Review of open action items [0/6]
(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-112-01: JLO to propose a concrete example that uses "."
in a ~%method~s.
* [ ] QT4CG-116-01: Add a specific error code for unsupported options
on doc and doc-available
* [ ] QT4CG-118-01: MK to make an incorrect type raise an error in
#1906
* [ ] QT4CG-119-02: MK to add a note about how schema composition is
done for multiple options
* [ ] QT4CG-021-01: MK to raise a new issue which may propose a
subset of the QNameLiteral which doesn't permit a namespace.
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]#2019: 1776: XSLT template rules for maps and array
* PR [11]#1883: 882 Replace fn:chain by fn:compose
* PR [12]#1283: 77b Update expressions
* PR [13]#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 [14]#2024: Add rules for $V?$X
1.6.3. Substantive PRs
The following substantive PRs were open when this agenda was prepared.
* PR [15]#1984: 882 Drop fn:chain
* PR [16]#1894: Additional examples to fn:chain - in a new branch
* PR [17]#2013: 748 Parse functions: consistency
* PR [18]#1959: 1953 (part) XSLT Worked example using methods to
implement atomic sets
* PR [19]#2011: 675(part): Add XSLT static typing rules for new kinds
of XPath expression
* PR [20]#1942: 37 Support sequence, array, and map destructuring
declarations
* PR [21]#1888: 366 xsl:package-location
* PR [22]#2019: 1776: XSLT template rules for maps and array
* PR [23]#2015: 2009 Avoid constructing document node when it makes
no sense
* PR [24]#2014: QT4CG-122-01 Add notes, examples, and rationale for
xsl:select
1.6.4. Required for V4.0
The following issues are labeled "required for V4.0".
* Issue [25]#1777: Shallow copy in XSLT with maps and arrays
* Issue [26]#1584: Review the XML Schema and RELAX NG schemas for
XSLT 4.0 for compatibility
* 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]#748: Parse functions: consistency
* Issue [34]#714: Function annotations in XSLT
* Issue [35]#675: XSLT streaming rules for new constructs
* Issue [36]#407: XSLT-specific context properties used in function
items
* Issue [37]#366: Support xsl:use-package with xsl:package-location
* Issue [38]#272: Setting parameter values in xsl:use-package
1.6.5. To be triaged
The following issues need to be triaged.
* Issue [39]#2025: Combine the concepts of pins/labels and modified
lookups
* Issue [40]#2022: Simplify optional XQuery conformance features
* Issue [41]#2021: XSLT: Move "Patterns" section into "Template
Rules"
* Issue [42]#2018: Type-checking the result of xsl:apply-templates
* Issue [43]#2017: `fn:sort-by`: Observations
* Issue [44]#2016: File Module: Incorporate changes
* Issue [45]#2012: Add array:sort-with
* Issue [46]#2010: XSLT patterns: generalize union, intersect, and
except
* Issue [47]#2007: Creating arrays in XSLT
* Issue [48]#2003: Conditional entries in map constructors
* Issue [49]#2002: Adaptive serialization: QNames
* Issue [50]#2000: element-to-map() - type signature of plan
* Issue [51]#1996: Lookups, KeySpecifier: add NumericLiteral and
ContextValueRef?
* Issue [52]#1995: Consistency: array lookups
* Issue [53]#1980: HTML serialization: the rules for adding a meta
element need to be aligned with HTML5
* Issue [54]#1979: Records: Type Safety
* Issue [55]#1970: Editorial notes
* Issue [56]#1955: fn:doc, fn:parse-xml: entity expansion
* Issue [57]#1949: fn:element-to-map: Updated Feedback
* Issue [58]#1948: fn:element-to-map: Tests
* Issue [59]#1946: We need examples of a record with an entry that is
a %method and invoking this method with the result it must produce
* Issue [60]#1944: Try/Catch/Finally - order of evaluation
* Issue [61]#1938: Invoking coerced methods
* Issue [62]#1935: doc-available() with invalid options
* Issue [63]#1934: Supporting RELAX NG validation
* Issue [64]#1920: Parse functions: determinism
* Issue [65]#1912: Error handling: `fn:throw`
* Issue [66]#1903: `fn:scan-left`, `fn:scan-right`: missing steps
* Issue [67]#1885: Use the spcification grammar markup to define the
regular expression grammar in F&O
* Issue [68]#1871: Arrays and maps: consistency
* Issue [69]#1868: array:members() to include index position
* Issue [70]#1859: Question on `fn:chain` and `err:FOAP0001`
* Issue [71]#1852: fn:values-except: Return atomic values that occur
in A but not in B
* Issue [72]#1787: Sorted maps revisited
* Issue [73]#1775: Navigation in JSON trees
* Issue [74]#1774: Nomenclature: relabelling
* Issue [75]#1736: Add option retain-order=false when constructing
maps
* Issue [76]#1718: Ordered Maps: positions in callback functions
* Issue [77]#1697: Add documentary names to callback function
signatures
* 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]#1528: Computed node constructors: observations
* Issue [82]#1484: Functions that expect a record type should make it
extensible
* Issue [83]#1479: Default element namespace in XQuery: interaction
of 'fixed' and '##any'
* Issue [84]#1459: Function properties and arities (editorial)
* Issue [85]#1310: add fn:match-groups() function
* Issue [86]#1307: For symmetry, add functions array:scan-left and
array:scan-right
* Issue [87]#1175: XPath: Optional parameters in the definition of an
inline function
* Issue [88]#760: Serialize functions: consistency
* Issue [89]#641: Serialization fallback.
* Issue [90]#115: Lookup operator on arrays of maps
2. Technical agenda
2.1. Review of pull requests
2.2. What about fn:chain?
We had a couple of meetings discussing the proposal to replace fn:chain
with fn:compose. The PR for discussion this week simply removes
fn:chain. (In previous straw polls, no one preferred "only fn:chain";
this PR changes the status quo to reflect that.)
I don't expect there's a lot of new technical ground to cover here, so
we'll attempt to time box the discussion. Ultimately, I hope the CG can
express a clear consensus and that everyone in the minority can accept
that consensus.
See PR [91]#1984: 882 Drop fn:chain, and PR [92]#1894: Additional
examples to fn:chain
2.3. PR #1959: 1953 (part) XSLT Worked example using methods to implement
atomic sets
See PR [93]#1959
2.4. PR #2011: 675(part): Add XSLT static typing rules for new kinds of XPath
expression
See PR [94]#2011
2.5. PR #1942: 37 Support sequence, array, and map destructuring declarations
See PR [95]#1942
2.6. PR #1888: 366 xsl:package-location
See PR [96]#1888
2.7. PR #2013: 748 Parse functions: consistency
See PR [97]#2013
2.8. PR #2019: 1776: XSLT template rules for maps and array
See PR [98]#2019
2.9. PR #2015: 2009 Avoid constructing document node when it makes no sense
See PR [99]#2015
2.10. PR #2014: QT4CG-122-01 Add notes, examples, and rationale for
xsl:select
See PR [100]#2014
2.11. Issue triage
2.11.1. Issue #1832: Associativity of Operators, especially "||" (Appendix
A.5)
See issue [101]#1832
2.11.2. Issue #1799: "well-formed HTML document"?
See issue [102]#1799
2.11.3. Issue #1797: elements-to-maps: separate function to construct a plan
See issue [103]#1797
2.11.4. Issue #760: Serialize functions: consistency
See issue [104]#760
2.11.5. Issue #641: Serialization fallback.
See issue [105]#641
2.11.6. Issue #119: Allow a map's key value to be any sequence
See issue [106]#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/05-20.html
9. https://qt4cg.org/meeting/agenda/2025/05-27.html#technical-agenda
10. https://qt4cg.org/dashboard/#pr-2019
11. https://qt4cg.org/dashboard/#pr-1883
12. https://qt4cg.org/dashboard/#pr-1283
13. https://qt4cg.org/dashboard/#pr-1062
14. https://qt4cg.org/dashboard/#pr-2024
15. https://qt4cg.org/dashboard/#pr-1984
16. https://qt4cg.org/dashboard/#pr-1894
17. https://qt4cg.org/dashboard/#pr-2013
18. https://qt4cg.org/dashboard/#pr-1959
19. https://qt4cg.org/dashboard/#pr-2011
20. https://qt4cg.org/dashboard/#pr-1942
21. https://qt4cg.org/dashboard/#pr-1888
22. https://qt4cg.org/dashboard/#pr-2019
23. https://qt4cg.org/dashboard/#pr-2015
24. https://qt4cg.org/dashboard/#pr-2014
25. https://github.com/qt4cg/qtspecs/issues/1777
26. https://github.com/qt4cg/qtspecs/issues/1584
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/748
34. https://github.com/qt4cg/qtspecs/issues/714
35. https://github.com/qt4cg/qtspecs/issues/675
36. https://github.com/qt4cg/qtspecs/issues/407
37. https://github.com/qt4cg/qtspecs/issues/366
38. https://github.com/qt4cg/qtspecs/issues/272
39. https://github.com/qt4cg/qtspecs/issues/2025
40. https://github.com/qt4cg/qtspecs/issues/2022
41. https://github.com/qt4cg/qtspecs/issues/2021
42. https://github.com/qt4cg/qtspecs/issues/2018
43. https://github.com/qt4cg/qtspecs/issues/2017
44. https://github.com/qt4cg/qtspecs/issues/2016
45. https://github.com/qt4cg/qtspecs/issues/2012
46. https://github.com/qt4cg/qtspecs/issues/2010
47. https://github.com/qt4cg/qtspecs/issues/2007
48. https://github.com/qt4cg/qtspecs/issues/2003
49. https://github.com/qt4cg/qtspecs/issues/2002
50. https://github.com/qt4cg/qtspecs/issues/2000
51. https://github.com/qt4cg/qtspecs/issues/1996
52. https://github.com/qt4cg/qtspecs/issues/1995
53. https://github.com/qt4cg/qtspecs/issues/1980
54. https://github.com/qt4cg/qtspecs/issues/1979
55. https://github.com/qt4cg/qtspecs/issues/1970
56. https://github.com/qt4cg/qtspecs/issues/1955
57. https://github.com/qt4cg/qtspecs/issues/1949
58. https://github.com/qt4cg/qtspecs/issues/1948
59. https://github.com/qt4cg/qtspecs/issues/1946
60. https://github.com/qt4cg/qtspecs/issues/1944
61. https://github.com/qt4cg/qtspecs/issues/1938
62. https://github.com/qt4cg/qtspecs/issues/1935
63. https://github.com/qt4cg/qtspecs/issues/1934
64. https://github.com/qt4cg/qtspecs/issues/1920
65. https://github.com/qt4cg/qtspecs/issues/1912
66. https://github.com/qt4cg/qtspecs/issues/1903
67. https://github.com/qt4cg/qtspecs/issues/1885
68. https://github.com/qt4cg/qtspecs/issues/1871
69. https://github.com/qt4cg/qtspecs/issues/1868
70. https://github.com/qt4cg/qtspecs/issues/1859
71. https://github.com/qt4cg/qtspecs/issues/1852
72. https://github.com/qt4cg/qtspecs/issues/1787
73. https://github.com/qt4cg/qtspecs/issues/1775
74. https://github.com/qt4cg/qtspecs/issues/1774
75. https://github.com/qt4cg/qtspecs/issues/1736
76. https://github.com/qt4cg/qtspecs/issues/1718
77. https://github.com/qt4cg/qtspecs/issues/1697
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/1528
82. https://github.com/qt4cg/qtspecs/issues/1484
83. https://github.com/qt4cg/qtspecs/issues/1479
84. https://github.com/qt4cg/qtspecs/issues/1459
85. https://github.com/qt4cg/qtspecs/issues/1310
86. https://github.com/qt4cg/qtspecs/issues/1307
87. https://github.com/qt4cg/qtspecs/issues/1175
88. https://github.com/qt4cg/qtspecs/issues/760
89. https://github.com/qt4cg/qtspecs/issues/641
90. https://github.com/qt4cg/qtspecs/issues/115
91. https://qt4cg.org/dashboard/#pr-1984
92. https://qt4cg.org/dashboard/#pr-1894
93. https://qt4cg.org/dashboard/#pr-1959
94. https://qt4cg.org/dashboard/#pr-2011
95. https://qt4cg.org/dashboard/#pr-1942
96. https://qt4cg.org/dashboard/#pr-1888
97. https://qt4cg.org/dashboard/#pr-2013
98. https://qt4cg.org/dashboard/#pr-2019
99. https://qt4cg.org/dashboard/#pr-2015
100. https://qt4cg.org/dashboard/#pr-2014
101. https://github.com/qt4cg/qtspecs/issues/1832
102. https://github.com/qt4cg/qtspecs/issues/1799
103. https://github.com/qt4cg/qtspecs/issues/1797
104. https://github.com/qt4cg/qtspecs/issues/760
105. https://github.com/qt4cg/qtspecs/issues/641
106. https://github.com/qt4cg/qtspecs/issues/119
Be seeing you,
norm
--
Norm Tovey-Walsh
Saxonica
Received on Sunday, 25 May 2025 15:04:57 UTC