- From: Norm Tovey-Walsh <ndw@nwalsh.com>
- Date: Mon, 03 Feb 2025 11:25:19 +0000
- To: "public-xslt-40@w3.org" <public-xslt-40@w3.org>
Hello,
Here is the agenda for tomorrow’s QT4CG meeting:
https://qt4cg.org/meeting/agenda/2025/02-04.html
QT4 CG Meeting 108 Agenda 2025-02-04
[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 4 February 2025. The following meeting is
scheduled for 11 February 2025.
1.5. Review of open action items [3/11]
(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
* [X] QT4CG-088-04: [Someone] needs to update the processing model
diagram needs vis-a-vis the static typing feature
* [ ] QT4CG-097-02: MK to make the XSD schema component references
into links to XSD
* [ ] QT4CG-103-01: MK to add an example of showing all the
properties for an untyped node.
* [X] QT4CG-106-01: NW to remove the dead wood from the XSLT build
(SVG diagrams)
* [ ] QT4CG-107-01: MK to amend PR 1722 so the expansion of focus
functions includes the return type item()*
* [ ] QT4CG-107-02: MK to propose adding the "duplicates" option
(from map:merge) to map:build and map:of-pairs
* [ ] QT4CG-107-03: MK to propose amending all the functions that
return ordered maps so that when duplicates are found, the key of
the combined entry is taken from the first of the duplicates.
* [ ] QT4CG-107-04: MK to review CG's comment to align fn:map-merge
by removing the reference to random number generator and fixing a
typo.
* [ ] QT4CG-107-05: JLO and DN to consider a proposal for system
defined records.
* [X] QT4CG-107-06: NW to integrate DN's expandable ToC into the
build.
1.6. Review of open pull requests and issues
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]#1587: 557 Add fn:binary-resource
* PR [10]#1296: 982 Rewrite of scan-left and scan-right
* PR [11]#1283: 77b Update expressions
* PR [12]#1062: 150bis revised proposal for fn:ranks
* PR [13]#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 [14]#1760: Remove hand-generated diffs from the builds
* PR [15]#1759: Fix validation issues in the EXPath module function
catalogs
* PR [16]#1743: 1738 Formatting of Notes in F&O
* PR [17]#1741: 1739 drop references to ordering mode in the static
context
* PR [18]#1734: 1682 Type promotion and operator mapping
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 [19]#1699: XPath function to calculate edit distance between
two strings
* Issue [20]#1571: Discussion: On the implementability of the specs
and helping implementors
1.6.4. Substantive PRs
The following substantive PRs were open when this agenda was prepared.
* PR [21]#1753: 1750 Overhaul of EXPath binary spec
* PR [22]#1746: Replace processing model diagrams
* PR [23]#1740: 1725b Further elaboration of duplicates handling in
maps
* PR [24]#1735: 1341 Drop $position callback from many functions
* PR [25]#1227: 150 PR resubmission for fn ranks
1.6.5. Required for V4.0
The following issues are labeled "required for V4.0".
* Issue [26]#1240: $sequence-of-maps ? info()
* Issue [27]#1238: XSLT on-no-match="shallow-copy-all" - revised
rules
* Issue [28]#1127: Binary resources
* Issue [29]#1045: Functions to manage namespace usage
* Issue [30]#1021: Extend `fn:doc`, `fn:collection` and
`fn:uri-collection` with options maps
* Issue [31]#1011: fn:transform() improvements
* Issue [32]#986: Numeric Comparisons
* Issue [33]#967: XPath Appendix I: Comparisons
* Issue [34]#826: Arrays: Representation of single members of an
array
* Issue [35]#748: Parse functions: consistency
* 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]#272: Setting parameter values in xsl:use-package
1.6.6. To be triaged
The following issues need to be triaged.
* Issue [40]#1754: Inverse functions to bin:hex, bin:bin, and
bin:octal
* Issue [41]#1753: 1750 Overhaul of EXPath binary spec
* Issue [42]#1752: Return type of fn:partition()
* Issue [43]#1751: bin:encode-string - should the result have a BOM?
* Issue [44]#1750: EXPath Binary : copy-edits and minor enhancements
* Issue [45]#1746: Replace processing model diagrams
* Issue [46]#1742: Maps constructed using streamed xsl:fork
instruction should not be ordered
* Issue [47]#1741: 1739 drop references to ordering mode in the
static context
* Issue [48]#1740: 1725b Further elaboration of duplicates handling
in maps
* Issue [49]#1737: Grammar problems introduced by #1732
* Issue [50]#1736: Add option retain-order=false when constructing
maps
* Issue [51]#1735: 1341 Drop $position callback from many functions
* Issue [52]#1734: 1682 Type promotion and operator mapping
* Issue [53]#1729: Grammar problems introduced by #1721
* Issue [54]#1724: Allow @copy-namespaces on <xsl:mode>?
* Issue [55]#1718: Ordered Maps: positions in callback functions
* Issue [56]#1716: Variable lookahead needed for `ArrowTarget`
* Issue [57]#1715: Array Lookups: partial removal of out-of-bounds
checks
* Issue [58]#1704: Ignore the byte order mark more
completely/globally
* Issue [59]#1702: Node Updates: Functions
* Issue [60]#1698: Allow select attribute for xsl:call-template
instruction
* Issue [61]#1697: Add documentary names to callback function
signatures
* Issue [62]#1661: QName arguments: also allow strings
* Issue [63]#1660: Further suggestions for fn:path
* Issue [64]#1658: fn:elements-to-maps: `empty`, normalize space ?
* Issue [65]#1656: Ordered Maps: Updates
* Issue [66]#1648: fn:elements-to-maps: Types
* Issue [67]#1647: fn:elements-to-maps: Explicit Layouts
* Issue [68]#1646: fn:elements-to-maps: Robustness
* Issue [69]#1645: fn:elements-to-maps: Debugging
* Issue [70]#1644: fn:elements-to-maps: Mixed Content
* Issue [71]#1631: xsl:apply-templates (without select) should allow
inline 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]#1587: 557 Add fn:binary-resource
* Issue [76]#1584: Review the XML Schema and RELAX NG schemas for
XSLT 4.0 for compatibility
* Issue [77]#1583: JSON: Parsing and serializing numbers, often
undesired E notation
* Issue [78]#1568: Define a Unicode case-insensitive collation
* Issue [79]#1566: EXPath Modules: Future
* Issue [80]#1537: XSLT: local functions within an enclosing xsl:mode
* Issue [81]#1528: Computed node constructors: observations
* Issue [82]#1520: Type declarations of cyclically dependent modules
* Issue [83]#1514: Editorial: optional position argument in function
signature for for-each and other HOF
* 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]#1456: Filtering by type in lookup expressions
* Issue [88]#1416: Key-value pairs: built-in record type `pair`
* Issue [89]#1363: map:get and array:get
* Issue [90]#1340: Namespace nodes and the namespace axis
* Issue [91]#1338: Arrays and maps: Members, entries, values,
contents, pairs, ...
* Issue [92]#1319: Specification Documents: Editors and Contributors
* Issue [93]#1310: add fn:match-groups() function
* Issue [94]#1307: For symmetry, add functions array:scan-left and
array:scan-right
* Issue [95]#1296: 982 Rewrite of scan-left and scan-right
* Issue [96]#1283: 77b Update expressions
* Issue [97]#1271: Schema validation in XPath
* Issue [98]#1227: 150 PR resubmission for fn ranks
* Issue [99]#1175: XPath: Optional parameters in the definition of an
inline function
* Issue [100]#1062: 150bis revised proposal for fn:ranks
* Issue [101]#850: fn:parse-html: Finalization
* Issue [102]#760: Serialize functions: consistency
* Issue [103]#755: with expression; chaining and concatenation
* Issue [104]#641: Serialization fallback.
* Issue [105]#583: (array|map):replace -> *:substitute or *:change
* Issue [106]#576: JSON serialization: INF/NaN, function items
* Issue [107]#322: Map construction in XSLT: xsl:record instruction
* Issue [108]#285: Stability of collections
* Issue [109]#158: Support optional parameters on dynamic functions
* Issue [110]#75: Support processing HTML 5 template element content
2. Technical agenda
2.1. PR #1753: 1750 Overhaul of EXPath binary spec
See PR [111]#1753.
2.2. PR #1746: Replace processing model diagrams
See PR [112]#1746.
2.3. Issue triage
Using the PRG-* tags seems like it would be inviting confusion. New
tags proposal:
* Reviewed-required, this is a required feature; we can't progress
without it.
* Reviewed-optional, this is an optional feature we're still hoping
to finish.
* Reviewed-close, this is an optional feature that we'd like to have,
but we're going to abandon it if no one provides a detailed change
proposal. (This category implies "close without further action" at
the next meeting.)
* Reviewed-easy, Reviewed-hard, optional tags indicating the
consensus intuition about how difficult it would be to address the
issue.
There are 70 untriaged issues. We can start at the top, or the bottom,
or with nominations for "easy to categorize" issues.
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/01-28.html
9. https://qt4cg.org/dashboard/#pr-1587
10. https://qt4cg.org/dashboard/#pr-1296
11. https://qt4cg.org/dashboard/#pr-1283
12. https://qt4cg.org/dashboard/#pr-1062
13. https://qt4cg.org/dashboard/#pr-1227
14. https://qt4cg.org/dashboard/#pr-1760
15. https://qt4cg.org/dashboard/#pr-1759
16. https://qt4cg.org/dashboard/#pr-1743
17. https://qt4cg.org/dashboard/#pr-1741
18. https://qt4cg.org/dashboard/#pr-1734
19. https://github.com/qt4cg/qtspecs/issues/1699
20. https://github.com/qt4cg/qtspecs/issues/1571
21. https://qt4cg.org/dashboard/#pr-1753
22. https://qt4cg.org/dashboard/#pr-1746
23. https://qt4cg.org/dashboard/#pr-1740
24. https://qt4cg.org/dashboard/#pr-1735
25. https://qt4cg.org/dashboard/#pr-1227
26. https://github.com/qt4cg/qtspecs/issues/1240
27. https://github.com/qt4cg/qtspecs/issues/1238
28. https://github.com/qt4cg/qtspecs/issues/1127
29. https://github.com/qt4cg/qtspecs/issues/1045
30. https://github.com/qt4cg/qtspecs/issues/1021
31. https://github.com/qt4cg/qtspecs/issues/1011
32. https://github.com/qt4cg/qtspecs/issues/986
33. https://github.com/qt4cg/qtspecs/issues/967
34. https://github.com/qt4cg/qtspecs/issues/826
35. https://github.com/qt4cg/qtspecs/issues/748
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/272
40. https://github.com/qt4cg/qtspecs/issues/1754
41. https://github.com/qt4cg/qtspecs/issues/1753
42. https://github.com/qt4cg/qtspecs/issues/1752
43. https://github.com/qt4cg/qtspecs/issues/1751
44. https://github.com/qt4cg/qtspecs/issues/1750
45. https://github.com/qt4cg/qtspecs/issues/1746
46. https://github.com/qt4cg/qtspecs/issues/1742
47. https://github.com/qt4cg/qtspecs/issues/1741
48. https://github.com/qt4cg/qtspecs/issues/1740
49. https://github.com/qt4cg/qtspecs/issues/1737
50. https://github.com/qt4cg/qtspecs/issues/1736
51. https://github.com/qt4cg/qtspecs/issues/1735
52. https://github.com/qt4cg/qtspecs/issues/1734
53. https://github.com/qt4cg/qtspecs/issues/1729
54. https://github.com/qt4cg/qtspecs/issues/1724
55. https://github.com/qt4cg/qtspecs/issues/1718
56. https://github.com/qt4cg/qtspecs/issues/1716
57. https://github.com/qt4cg/qtspecs/issues/1715
58. https://github.com/qt4cg/qtspecs/issues/1704
59. https://github.com/qt4cg/qtspecs/issues/1702
60. https://github.com/qt4cg/qtspecs/issues/1698
61. https://github.com/qt4cg/qtspecs/issues/1697
62. https://github.com/qt4cg/qtspecs/issues/1661
63. https://github.com/qt4cg/qtspecs/issues/1660
64. https://github.com/qt4cg/qtspecs/issues/1658
65. https://github.com/qt4cg/qtspecs/issues/1656
66. https://github.com/qt4cg/qtspecs/issues/1648
67. https://github.com/qt4cg/qtspecs/issues/1647
68. https://github.com/qt4cg/qtspecs/issues/1646
69. https://github.com/qt4cg/qtspecs/issues/1645
70. https://github.com/qt4cg/qtspecs/issues/1644
71. https://github.com/qt4cg/qtspecs/issues/1631
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/1587
76. https://github.com/qt4cg/qtspecs/issues/1584
77. https://github.com/qt4cg/qtspecs/issues/1583
78. https://github.com/qt4cg/qtspecs/issues/1568
79. https://github.com/qt4cg/qtspecs/issues/1566
80. https://github.com/qt4cg/qtspecs/issues/1537
81. https://github.com/qt4cg/qtspecs/issues/1528
82. https://github.com/qt4cg/qtspecs/issues/1520
83. https://github.com/qt4cg/qtspecs/issues/1514
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/1456
88. https://github.com/qt4cg/qtspecs/issues/1416
89. https://github.com/qt4cg/qtspecs/issues/1363
90. https://github.com/qt4cg/qtspecs/issues/1340
91. https://github.com/qt4cg/qtspecs/issues/1338
92. https://github.com/qt4cg/qtspecs/issues/1319
93. https://github.com/qt4cg/qtspecs/issues/1310
94. https://github.com/qt4cg/qtspecs/issues/1307
95. https://github.com/qt4cg/qtspecs/issues/1296
96. https://github.com/qt4cg/qtspecs/issues/1283
97. https://github.com/qt4cg/qtspecs/issues/1271
98. https://github.com/qt4cg/qtspecs/issues/1227
99. https://github.com/qt4cg/qtspecs/issues/1175
100. https://github.com/qt4cg/qtspecs/issues/1062
101. https://github.com/qt4cg/qtspecs/issues/850
102. https://github.com/qt4cg/qtspecs/issues/760
103. https://github.com/qt4cg/qtspecs/issues/755
104. https://github.com/qt4cg/qtspecs/issues/641
105. https://github.com/qt4cg/qtspecs/issues/583
106. https://github.com/qt4cg/qtspecs/issues/576
107. https://github.com/qt4cg/qtspecs/issues/322
108. https://github.com/qt4cg/qtspecs/issues/285
109. https://github.com/qt4cg/qtspecs/issues/158
110. https://github.com/qt4cg/qtspecs/issues/75
111. https://qt4cg.org/dashboard/#pr-1753
112. https://qt4cg.org/dashboard/#pr-1746
Be seeing you,
norm
--
Norm Tovey-Walsh <ndw@nwalsh.com>
https://norm.tovey-walsh.com/
> It's all fun and games until someone loses an eye. Then it's just fun
> with a pirate.
Received on Monday, 3 February 2025 11:25:27 UTC