QT4CG meeting 112 draft agenda, 4 March 2025

Hello,

Here is the proposed agenda for tomorrow’s QT4CG call:

   https://qt4cg.org/meeting/agenda/2025/03-04.html

QT4 CG Meeting 112 Agenda 2025-03-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 March 2025. The following meeting is
   scheduled for 11 March 2025.

   Note: The QT4CG meeting is scheduled on UK/European civil time. The
   United States switches to daylight saving time on 9 March 2025, so the
   meetings of 11, 18, and 25 March will be one hour later there (12:00
   EDT, 09:00 PDT) until the UK/Europe also switches (on 30 March 2024).

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-107-05: JLO and DN to consider a proposal for system
       defined records.
     * [ ] 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
     * [X] QT4CG-111-01: MK to review the editorial comments on PR #1837
       and then merge the PR.
     * [X] QT4CG-111-02: MK to fix the typo $in as xs:double+ and 1.3. 1.4
       that middle "." should be a ","
     * [X] QT4CG-111-03: MK to add a %method example that uses the arrow
       syntax.

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]#1855: 1771 Add option for deep-equal to consider map order
     * PR [17]#1850: Actions from meeting 111
     * PR [18]#1849: Reduce the indentation in the ToC
     * PR [19]#1839: Relax the return type of the Invisible XML parsing
       function
     * PR [20]#1838: Attempt to add change markup in collapsed ToC

1.6.3. Substantive PRs

   The following substantive PRs were open when this agenda was prepared.
     * PR [21]#1853: 1845 Revised design of methods to use . rather than
       $this
     * PR [22]#1835: add zero-width assertions to regular expressions
     * PR [23]#1819: 451 Multiple schemas in XSLT
     * PR [24]#1801: 1798 Function fn:function-identity
     * PR [25]#1778: 1456 Lookup expressions filtered by type
     * PR [26]#1740: 1725b Further elaboration of duplicates handling in
       maps
     * PR [27]#1735: 1341 Drop $position callback from many functions

1.6.4. Required for V4.0

   The following issues are labeled "required for V4.0".
     * Issue [28]#1777: Shallow copy in XSLT with maps and arrays
     * Issue [29]#1742: Maps constructed using streamed xsl:fork
       instruction should not be ordered
     * Issue [30]#1584: Review the XML Schema and RELAX NG schemas for
       XSLT 4.0 for compatibility
     * Issue [31]#1240: $sequence-of-maps ? info()
     * Issue [32]#1127: Binary resources
     * Issue [33]#1045: Functions to manage namespace usage
     * Issue [34]#1021: Extend `fn:doc`, `fn:collection` and
       `fn:uri-collection` with options maps
     * Issue [35]#1011: fn:transform() improvements
     * Issue [36]#986: Numeric Comparisons
     * Issue [37]#967: XPath Appendix I: Comparisons
     * Issue [38]#826: Arrays: Representation of single members of an
       array
     * Issue [39]#748: Parse functions: consistency
     * Issue [40]#714: Function annotations in XSLT
     * Issue [41]#675: XSLT streaming rules for new constructs
     * Issue [42]#501: Error handling: Rethrow errors; finally block
     * Issue [43]#407: XSLT-specific context properties used in function
       items
     * Issue [44]#366: Support xsl:use-package with xsl:package-location
     * Issue [45]#272: Setting parameter values in xsl:use-package

1.6.5. To be triaged

   The following issues need to be triaged.
     * Issue [46]#1852: fn:values-except: Return atomic values that occur
       in A but not in B
     * Issue [47]#1851: Questions on `fn:atomic-type-annotation`
     * Issue [48]#1848: Define regular expressions using XSD 1.1 as
       baseline
     * Issue [49]#1846: %method functions, dynamic function calls
     * Issue [50]#1844: Drop mapping arrow operator
     * Issue [51]#1832: Associativity of Operators, especially "||"
       (Appendix A.5)
     * Issue [52]#1799: "well-formed HTML document"?
     * Issue [53]#1797: elements-to-maps: separate function to construct a
       plan
     * Issue [54]#1795: XSLT templates: Matching values in a map by key
     * Issue [55]#1794: Lookup: select all except
     * 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]#1338: Arrays and maps: Members, entries, values,
       contents, pairs, ...
     * Issue [85]#1310: add fn:match-groups() function
     * Issue [86]#1307: For symmetry, add functions array:scan-left and
       array:scan-right
     * Issue [87]#1271: Schema validation in XPath
     * Issue [88]#1175: XPath: Optional parameters in the definition of an
       inline function
     * Issue [89]#850: fn:parse-html: Finalization
     * Issue [90]#760: Serialize functions: consistency
     * Issue [91]#641: Serialization fallback.
     * Issue [92]#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 #1853: 1845 Revised design of methods to use . rather than $this

   See PR [93]#1853

2.1.2. PR #1801: 1798 Function fn:function-identity

   See PR [94]#1801

2.1.3. PR #1735: 1341 Drop $position callback from many functions

   See PR [95]#1735

2.1.4. PR #1740: 1725b Further elaboration of duplicates handling in maps

   See PR [96]#1740

2.1.5. PR #1778: 1456 Lookup expressions filtered by type

   See PR [97]#1778

2.1.6. PR #1819: 451 Multiple schemas in XSLT

   See PR [98]#1819

2.2. Issue triage

2.2.1. Issue #1832: Associativity of Operators, especially "||" (Appendix
A.5)

   See issue [99]#1832

2.2.2. Issue #1799: "well-formed HTML document"?

   See issue [100]#1799

2.2.3. Issue #1797: elements-to-maps: separate function to construct a plan

   See issue [101]#1797

2.2.4. Issue #760: Serialize functions: consistency

   See issue [102]#760

2.2.5. Issue #641: Serialization fallback.

   See issue [103]#641

2.2.6. Issue #119: Allow a map's key value to be any sequence

   See issue [104]#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-25.html
   9. https://qt4cg.org/meeting/agenda/2025/03-04.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-1855
  17. https://qt4cg.org/dashboard/#pr-1850
  18. https://qt4cg.org/dashboard/#pr-1849
  19. https://qt4cg.org/dashboard/#pr-1839
  20. https://qt4cg.org/dashboard/#pr-1838
  21. https://qt4cg.org/dashboard/#pr-1853
  22. https://qt4cg.org/dashboard/#pr-1835
  23. https://qt4cg.org/dashboard/#pr-1819
  24. https://qt4cg.org/dashboard/#pr-1801
  25. https://qt4cg.org/dashboard/#pr-1778
  26. https://qt4cg.org/dashboard/#pr-1740
  27. https://qt4cg.org/dashboard/#pr-1735
  28. https://github.com/qt4cg/qtspecs/issues/1777
  29. https://github.com/qt4cg/qtspecs/issues/1742
  30. https://github.com/qt4cg/qtspecs/issues/1584
  31. https://github.com/qt4cg/qtspecs/issues/1240
  32. https://github.com/qt4cg/qtspecs/issues/1127
  33. https://github.com/qt4cg/qtspecs/issues/1045
  34. https://github.com/qt4cg/qtspecs/issues/1021
  35. https://github.com/qt4cg/qtspecs/issues/1011
  36. https://github.com/qt4cg/qtspecs/issues/986
  37. https://github.com/qt4cg/qtspecs/issues/967
  38. https://github.com/qt4cg/qtspecs/issues/826
  39. https://github.com/qt4cg/qtspecs/issues/748
  40. https://github.com/qt4cg/qtspecs/issues/714
  41. https://github.com/qt4cg/qtspecs/issues/675
  42. https://github.com/qt4cg/qtspecs/issues/501
  43. https://github.com/qt4cg/qtspecs/issues/407
  44. https://github.com/qt4cg/qtspecs/issues/366
  45. https://github.com/qt4cg/qtspecs/issues/272
  46. https://github.com/qt4cg/qtspecs/issues/1852
  47. https://github.com/qt4cg/qtspecs/issues/1851
  48. https://github.com/qt4cg/qtspecs/issues/1848
  49. https://github.com/qt4cg/qtspecs/issues/1846
  50. https://github.com/qt4cg/qtspecs/issues/1844
  51. https://github.com/qt4cg/qtspecs/issues/1832
  52. https://github.com/qt4cg/qtspecs/issues/1799
  53. https://github.com/qt4cg/qtspecs/issues/1797
  54. https://github.com/qt4cg/qtspecs/issues/1795
  55. https://github.com/qt4cg/qtspecs/issues/1794
  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/1338
  85. https://github.com/qt4cg/qtspecs/issues/1310
  86. https://github.com/qt4cg/qtspecs/issues/1307
  87. https://github.com/qt4cg/qtspecs/issues/1271
  88. https://github.com/qt4cg/qtspecs/issues/1175
  89. https://github.com/qt4cg/qtspecs/issues/850
  90. https://github.com/qt4cg/qtspecs/issues/760
  91. https://github.com/qt4cg/qtspecs/issues/641
  92. https://github.com/qt4cg/qtspecs/issues/119
  93. https://qt4cg.org/dashboard/#pr-1853
  94. https://qt4cg.org/dashboard/#pr-1801
  95. https://qt4cg.org/dashboard/#pr-1735
  96. https://qt4cg.org/dashboard/#pr-1740
  97. https://qt4cg.org/dashboard/#pr-1778
  98. https://qt4cg.org/dashboard/#pr-1819
  99. https://github.com/qt4cg/qtspecs/issues/1832
 100. https://github.com/qt4cg/qtspecs/issues/1799
 101. https://github.com/qt4cg/qtspecs/issues/1797
 102. https://github.com/qt4cg/qtspecs/issues/760
 103. https://github.com/qt4cg/qtspecs/issues/641
 104. https://github.com/qt4cg/qtspecs/issues/119

                                        Be seeing you,
                                          norm

--
Norm Tovey-Walsh
Saxonica

Received on Monday, 3 March 2025 11:39:58 UTC