QT4CG meeting 116 draft agenda, 8 April 2025

Hi folks,

Here’s the proposed agenda for tomorrow’s meeting:

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

QT4 CG Meeting 116 Agenda 2025-04-08

   [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 (25 March; there was no meeting on 1
   April).

1.4. Next meeting

   This meeting is planned for 8 April 2025. The following meeting is
   scheduled for 15 April 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 NW to come to agreement on the
       fn:ranks proposal
     * [ ] QT4CG-107-05: JLO and DN to consider a proposal for system
       defined records.
     * [ ] QT4CG-112-01: JLO to propose a concrete example that uses "."
       in a ~%method~s.
     * [ ] QT4CG-113-02: NW to investigate a way to show extra attributes
       in the syntax summary.
     * [ ] QT4CG-115-01: MK to give an example of params passed
       automatically through next-match using a 3.0 version control
     * [ ] QT4CG-115-02: JWL to write a few tests for xsl:record

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]#1888: 366 xsl:package-location
     * PR [11]#1283: 77b Update expressions
     * PR [12]#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 [13]#1913: 1911 Clarifications for regular expressions
     * PR [14]#1904: 1832 Operator Associativity
     * PR [15]#1898: 1624b Expand rules for document node subtyping

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 [16]#1900: Records: instance checks
     * Issue [17]#1846: %method functions, dynamic function calls
     * Issue [18]#982: scan-left, scan-right: position argument, array
       functions
     * Issue [19]#564: Sorted maps

1.6.4. Substantive PRs

   The following substantive PRs were open when this agenda was prepared.
     * PR [20]#1915: 1902b bin:unpack out of range error
     * PR [21]#1914: 501 Error handling: try/finally
     * PR [22]#1910: 1021 (part 1) Add $options arg to doc() and
       doc-available()
     * PR [23]#1908: 1520 Allow forwards references to named item types
     * PR [24]#1906: 1797 elements-to-maps-conversion-plan function
     * PR [25]#1901: 1363 fallback becomes a value not a function
     * PR [26]#1897: 1876 In fn:replace(), merge the $replacement and
       $action parameters
     * PR [27]#1895: 1881 Function identity for maps and arrays
     * PR [28]#1894: Additional examples to fn:chain - in a new branch
     * PR [29]#1883: 882 Replace fn:chain by fn:compose
     * PR [30]#1819: 451 Multiple schemas in XSLT
     * PR [31]#1587: 557 Add fn:binary-resource

1.6.5. Required for V4.0

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

1.6.6. To be triaged

   The following issues need to be triaged.
     * Issue [50]#1912: Error handling: `fn:throw`
     * Issue [51]#1911: Remarks on recent changes to regular expression
       handling
     * Issue [52]#1907: Method lookup: wildcards
     * Issue [53]#1905: Editorial edits
     * Issue [54]#1903: `fn:scan-left`, `fn:scan-right`: missing steps
     * Issue [55]#1896: Drop "parameter names" as a property of a function
       item
     * Issue [56]#1891: `fn:parse-html`: `html-version`
     * Issue [57]#1889: HTML serialization: `html-version` and `version`
       parameters; allowed values
     * Issue [58]#1885: Use the spcification grammar markup to define the
       regular expression grammar in F&O
     * Issue [59]#1871: Arrays and maps: consistency
     * Issue [60]#1868: array:members() to include index position
     * Issue [61]#1859: Question on `fn:chain` and `err:FOAP0001`
     * Issue [62]#1852: fn:values-except: Return atomic values that occur
       in A but not in B
     * Issue [63]#1846: %method functions, dynamic function calls
     * Issue [64]#1844: Drop mapping arrow operator
     * Issue [65]#1799: "well-formed HTML document"?
     * Issue [66]#1795: XSLT templates: Matching values in a map by key
     * Issue [67]#1787: Sorted maps revisited
     * Issue [68]#1775: Navigation in JSON trees
     * Issue [69]#1774: Nomenclature: relabelling
     * Issue [70]#1754: Inverse functions to bin:hex, bin:bin, and
       bin:octal
     * Issue [71]#1736: Add option retain-order=false when constructing
       maps
     * Issue [72]#1718: Ordered Maps: positions in callback functions
     * Issue [73]#1704: Ignore the byte order mark more
       completely/globally
     * Issue [74]#1697: Add documentary names to callback function
       signatures
     * Issue [75]#1661: QName arguments: also allow strings
     * Issue [76]#1644: fn:elements-to-maps: Mixed Content
     * Issue [77]#1618: Adaptive serialization: doubles
     * Issue [78]#1591: Implausible filter expressions
     * Issue [79]#1583: JSON: Parsing and serializing numbers, often
       undesired E notation
     * Issue [80]#1568: Define a Unicode case-insensitive collation
     * 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]#1416: Key-value pairs: built-in record type `pair`
     * Issue [86]#1310: add fn:match-groups() function
     * Issue [87]#1307: For symmetry, add functions array:scan-left and
       array:scan-right
     * Issue [88]#1271: Schema validation in XPath
     * Issue [89]#1175: XPath: Optional parameters in the definition of an
       inline function
     * Issue [90]#850: fn:parse-html: Finalization
     * Issue [91]#760: Serialize functions: consistency
     * Issue [92]#641: Serialization fallback.
     * Issue [93]#119: Allow a map's key value to be any sequence

2. Technical agenda

   We do need to get back to issue triage, but in the interest of
   "catching up", let's plan to focus on PRs this week. I've tried to
   order them with the "easy" ones first, but suggestions for reordering a
   perfectly in order. (No pun intended.)

   I don't actually think we'll get through all of these, but let's try to
   prioritize finishing the small ones over discussing the big ones where
   practical.

2.1. Review of pull requests

2.1.1. PR #1915: 1902b bin:unpack out of range error

   See PR [94]#1915

2.1.2. PR #1914: 501 Error handling: try/finally

   See PR [95]#1914

2.1.3. PR #1910: 1021 (part 1) Add $options arg to doc() and doc-available()

   See PR [96]#1910

2.1.4. PR #1908: 1520 Allow forwards references to named item types

   See PR [97]#1908

2.1.5. PR #1897: 1876 In fn:replace(), merge the $replacement and $action
parameters

   See PR [98]#1897

2.1.6. PR #1895: 1881 Function identity for maps and arrays

   See PR [99]#1895

2.1.7. PR #1901: 1363 fallback becomes a value not a function

   See PR [100]#1901

2.1.8. PR #1819: 451 Multiple schemas in XSLT

   See PR [101]#1819

2.1.9. PR #1587: 557 Add fn:binary-resource

   See PR [102]#1587

2.1.10. PR #1906: 1797 elements-to-maps-conversion-plan function

   See PR [103]#1906

2.1.11. PR #1894: Additional examples to fn:chain - in a new branch

   See PR [104]#1894

2.1.12. PR #1883: 882 Replace fn:chain by fn:compose

   See PR [105]#1883

2.2. Issue triage

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

   See issue [106]#1832

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

   See issue [107]#1799

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

   See issue [108]#1797

2.2.4. Issue #760: Serialize functions: consistency

   See issue [109]#760

2.2.5. Issue #641: Serialization fallback.

   See issue [110]#641

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

   See issue [111]#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/03-25.html
   9. https://qt4cg.org/meeting/agenda/2025/04-08.html#technical-agenda
  10. https://qt4cg.org/dashboard/#pr-1888
  11. https://qt4cg.org/dashboard/#pr-1283
  12. https://qt4cg.org/dashboard/#pr-1062
  13. https://qt4cg.org/dashboard/#pr-1913
  14. https://qt4cg.org/dashboard/#pr-1904
  15. https://qt4cg.org/dashboard/#pr-1898
  16. https://github.com/qt4cg/qtspecs/issues/1900
  17. https://github.com/qt4cg/qtspecs/issues/1846
  18. https://github.com/qt4cg/qtspecs/issues/982
  19. https://github.com/qt4cg/qtspecs/issues/564
  20. https://qt4cg.org/dashboard/#pr-1915
  21. https://qt4cg.org/dashboard/#pr-1914
  22. https://qt4cg.org/dashboard/#pr-1910
  23. https://qt4cg.org/dashboard/#pr-1908
  24. https://qt4cg.org/dashboard/#pr-1906
  25. https://qt4cg.org/dashboard/#pr-1901
  26. https://qt4cg.org/dashboard/#pr-1897
  27. https://qt4cg.org/dashboard/#pr-1895
  28. https://qt4cg.org/dashboard/#pr-1894
  29. https://qt4cg.org/dashboard/#pr-1883
  30. https://qt4cg.org/dashboard/#pr-1819
  31. https://qt4cg.org/dashboard/#pr-1587
  32. https://github.com/qt4cg/qtspecs/issues/1777
  33. https://github.com/qt4cg/qtspecs/issues/1742
  34. https://github.com/qt4cg/qtspecs/issues/1584
  35. https://github.com/qt4cg/qtspecs/issues/1240
  36. https://github.com/qt4cg/qtspecs/issues/1127
  37. https://github.com/qt4cg/qtspecs/issues/1045
  38. https://github.com/qt4cg/qtspecs/issues/1021
  39. https://github.com/qt4cg/qtspecs/issues/1011
  40. https://github.com/qt4cg/qtspecs/issues/986
  41. https://github.com/qt4cg/qtspecs/issues/967
  42. https://github.com/qt4cg/qtspecs/issues/826
  43. https://github.com/qt4cg/qtspecs/issues/748
  44. https://github.com/qt4cg/qtspecs/issues/714
  45. https://github.com/qt4cg/qtspecs/issues/675
  46. https://github.com/qt4cg/qtspecs/issues/501
  47. https://github.com/qt4cg/qtspecs/issues/407
  48. https://github.com/qt4cg/qtspecs/issues/366
  49. https://github.com/qt4cg/qtspecs/issues/272
  50. https://github.com/qt4cg/qtspecs/issues/1912
  51. https://github.com/qt4cg/qtspecs/issues/1911
  52. https://github.com/qt4cg/qtspecs/issues/1907
  53. https://github.com/qt4cg/qtspecs/issues/1905
  54. https://github.com/qt4cg/qtspecs/issues/1903
  55. https://github.com/qt4cg/qtspecs/issues/1896
  56. https://github.com/qt4cg/qtspecs/issues/1891
  57. https://github.com/qt4cg/qtspecs/issues/1889
  58. https://github.com/qt4cg/qtspecs/issues/1885
  59. https://github.com/qt4cg/qtspecs/issues/1871
  60. https://github.com/qt4cg/qtspecs/issues/1868
  61. https://github.com/qt4cg/qtspecs/issues/1859
  62. https://github.com/qt4cg/qtspecs/issues/1852
  63. https://github.com/qt4cg/qtspecs/issues/1846
  64. https://github.com/qt4cg/qtspecs/issues/1844
  65. https://github.com/qt4cg/qtspecs/issues/1799
  66. https://github.com/qt4cg/qtspecs/issues/1795
  67. https://github.com/qt4cg/qtspecs/issues/1787
  68. https://github.com/qt4cg/qtspecs/issues/1775
  69. https://github.com/qt4cg/qtspecs/issues/1774
  70. https://github.com/qt4cg/qtspecs/issues/1754
  71. https://github.com/qt4cg/qtspecs/issues/1736
  72. https://github.com/qt4cg/qtspecs/issues/1718
  73. https://github.com/qt4cg/qtspecs/issues/1704
  74. https://github.com/qt4cg/qtspecs/issues/1697
  75. https://github.com/qt4cg/qtspecs/issues/1661
  76. https://github.com/qt4cg/qtspecs/issues/1644
  77. https://github.com/qt4cg/qtspecs/issues/1618
  78. https://github.com/qt4cg/qtspecs/issues/1591
  79. https://github.com/qt4cg/qtspecs/issues/1583
  80. https://github.com/qt4cg/qtspecs/issues/1568
  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/1416
  86. https://github.com/qt4cg/qtspecs/issues/1310
  87. https://github.com/qt4cg/qtspecs/issues/1307
  88. https://github.com/qt4cg/qtspecs/issues/1271
  89. https://github.com/qt4cg/qtspecs/issues/1175
  90. https://github.com/qt4cg/qtspecs/issues/850
  91. https://github.com/qt4cg/qtspecs/issues/760
  92. https://github.com/qt4cg/qtspecs/issues/641
  93. https://github.com/qt4cg/qtspecs/issues/119
  94. https://qt4cg.org/dashboard/#pr-1915
  95. https://qt4cg.org/dashboard/#pr-1914
  96. https://qt4cg.org/dashboard/#pr-1910
  97. https://qt4cg.org/dashboard/#pr-1908
  98. https://qt4cg.org/dashboard/#pr-1897
  99. https://qt4cg.org/dashboard/#pr-1895
 100. https://qt4cg.org/dashboard/#pr-1901
 101. https://qt4cg.org/dashboard/#pr-1819
 102. https://qt4cg.org/dashboard/#pr-1587
 103. https://qt4cg.org/dashboard/#pr-1906
 104. https://qt4cg.org/dashboard/#pr-1894
 105. https://qt4cg.org/dashboard/#pr-1883
 106. https://github.com/qt4cg/qtspecs/issues/1832
 107. https://github.com/qt4cg/qtspecs/issues/1799
 108. https://github.com/qt4cg/qtspecs/issues/1797
 109. https://github.com/qt4cg/qtspecs/issues/760
 110. https://github.com/qt4cg/qtspecs/issues/641
 111. https://github.com/qt4cg/qtspecs/issues/119

                                        Be seeing you,
                                          norm

--
Norm Tovey-Walsh
Saxonica

Received on Monday, 7 April 2025 10:09:19 UTC