QT4CG meeting 120 draft agenda, 6 May 2025

Hello,

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

   https://qt4cg.org/meeting/agenda/2025/05-06.html

QT4 CG Meeting 120 Agenda 2025-05-06

   [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 6 May 2025. The following meeting is
   scheduled for 13 May 2025.

1.5. Review of open action items [1/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-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
     * [X] QT4CG-119-01: NW will add a bit of prose about * and then merge
       the PR 1961
     * [ ] QT4CG-119-02: MK to add a note about how schema composition is
       done for multiple options

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]#1942: 37 Support sequence, array, and map destructuring
       declarations
     * 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]#1974: 1973 Cross-reference from type analysis to definition
       of disjointedness
     * PR [14]#1971: 1951 Clarifications on serialization parameters
     * PR [15]#1969: 1952 Change option name xsi-schema-location
     * PR [16]#1968: 1967 r/binary-resource/unparsed-binary/
     * PR [17]#1964: 1957 xsl output allows mixed content
     * PR [18]#1963: 1958 Fix simple typo in map:build

1.6.3. Substantive PRs

   The following substantive PRs were open when this agenda was prepared.
     * PR [19]#1977: 1889 Tidy up handling of HTML serialization version,
       default to HTML5
     * PR [20]#1976: 1661 Introduce QName literals
     * PR [21]#1975: 1240 Allow operand of dynamic function call to be a
       sequence
     * PR [22]#1971: 1951 Clarifications on serialization parameters
     * PR [23]#1964: 1957 xsl output allows mixed content
     * PR [24]#1959: 1953 (part) XSLT Worked example using methods to
       implement atomic sets
     * PR [25]#1894: Additional examples to fn:chain - in a new branch
     * PR [26]#1888: 366 xsl:package-location
     * PR [27]#1883: 882 Replace fn:chain by fn:compose

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]#1584: Review the XML Schema and RELAX NG schemas for
       XSLT 4.0 for compatibility
     * Issue [30]#1240: $sequence-of-maps ? info()
     * Issue [31]#1127: Binary resources
     * Issue [32]#1045: Functions to manage namespace usage
     * Issue [33]#1021: Extend `fn:doc`, `fn:collection` and
       `fn:uri-collection` with options maps
     * Issue [34]#1011: fn:transform() improvements
     * Issue [35]#986: Numeric Comparisons
     * Issue [36]#967: XPath Appendix I: Comparisons
     * Issue [37]#748: Parse functions: consistency
     * Issue [38]#714: Function annotations in XSLT
     * Issue [39]#675: XSLT streaming rules for new constructs
     * Issue [40]#407: XSLT-specific context properties used in function
       items
     * Issue [41]#366: Support xsl:use-package with xsl:package-location
     * Issue [42]#272: Setting parameter values in xsl:use-package

1.6.5. To be triaged

   The following issues need to be triaged.
     * Issue [43]#1979: Records: Type Safety
     * Issue [44]#1970: Editorial notes
     * Issue [45]#1955: fn:doc, fn:parse-xml: entity expansion
     * Issue [46]#1949: fn:element-to-map: Updated Feedback
     * Issue [47]#1948: fn:element-to-map: Tests
     * Issue [48]#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 [49]#1944: Try/Catch/Finally - order of evaluation
     * Issue [50]#1938: Invoking coerced methods
     * Issue [51]#1935: doc-available() with invalid options
     * Issue [52]#1934: Supporting RELAX NG validation
     * Issue [53]#1920: Parse functions: determinism
     * Issue [54]#1912: Error handling: `fn:throw`
     * Issue [55]#1903: `fn:scan-left`, `fn:scan-right`: missing steps
     * Issue [56]#1885: Use the spcification grammar markup to define the
       regular expression grammar in F&O
     * Issue [57]#1871: Arrays and maps: consistency
     * Issue [58]#1868: array:members() to include index position
     * Issue [59]#1859: Question on `fn:chain` and `err:FOAP0001`
     * Issue [60]#1852: fn:values-except: Return atomic values that occur
       in A but not in B
     * Issue [61]#1795: XSLT templates: Matching values in a map by key
     * Issue [62]#1787: Sorted maps revisited
     * Issue [63]#1775: Navigation in JSON trees
     * Issue [64]#1774: Nomenclature: relabelling
     * Issue [65]#1736: Add option retain-order=false when constructing
       maps
     * Issue [66]#1718: Ordered Maps: positions in callback functions
     * Issue [67]#1697: Add documentary names to callback function
       signatures
     * Issue [68]#1661: QName arguments: also allow strings
     * Issue [69]#1618: Adaptive serialization: doubles
     * Issue [70]#1591: Implausible filter expressions
     * Issue [71]#1583: JSON: Parsing and serializing numbers, often
       undesired E notation
     * Issue [72]#1528: Computed node constructors: observations
     * Issue [73]#1484: Functions that expect a record type should make it
       extensible
     * Issue [74]#1479: Default element namespace in XQuery: interaction
       of 'fixed' and '##any'
     * Issue [75]#1459: Function properties and arities (editorial)
     * Issue [76]#1310: add fn:match-groups() function
     * Issue [77]#1307: For symmetry, add functions array:scan-left and
       array:scan-right
     * Issue [78]#1175: XPath: Optional parameters in the definition of an
       inline function
     * Issue [79]#760: Serialize functions: consistency
     * Issue [80]#641: Serialization fallback.

2. Technical agenda

2.1. Review of pull requests

2.2. PR #1883/1894: fn:chain and fn:compose

   Related PRs:
     * PR [81]#1883: 882 Replace fn:chain by fn:compose
     * PR [82]#1894: Additional examples to fn:chain - in a new branch

   We need to come to some resolution on this issue. Recall that in last
   week's straw poll, there were only two options that got any votes at
   all: fn:compose (only) got 6 votes, both got 3 votes.

   I'm going to time box this discussion to 10 minutes. If, after that
   time, there is still a substantial majority in favor of fn:compose
   only, I'm going to ask the minority to accept that the consensus does
   not favor keeping fn:chain as well.

2.3. PR #1976: 1661 Introduce QName literals

   See PR [83]#1976

2.4. PR #1975: 1240 Allow operand of dynamic function call to be a sequence

   See PR [84]#1975

2.5. PR #1977: 1889 Tidy up handling of HTML serialization version, default
to HTML5

   See PR [85]#1977

2.6. PR #1971: 1951 Clarifications on serialization parameters

   See PR [86]#1971

2.7. PR #1959: 1953 (part) XSLT Worked example using methods to implement
atomic sets

   See PR [87]#1959

2.8. PR #1888: 366 xsl:package-location

   See PR [88]#1888

2.9. PR #1964: 1957 xsl output allows mixed content

   See PR [89]#1964

2.10. Issue triage

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

   See issue [90]#1832

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

   See issue [91]#1799

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

   See issue [92]#1797

2.10.4. Issue #760: Serialize functions: consistency

   See issue [93]#760

2.10.5. Issue #641: Serialization fallback.

   See issue [94]#641

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

   See issue [95]#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/04-29.html
   9. https://qt4cg.org/meeting/agenda/2025/05-06.html#technical-agenda
  10. https://qt4cg.org/dashboard/#pr-1942
  11. https://qt4cg.org/dashboard/#pr-1283
  12. https://qt4cg.org/dashboard/#pr-1062
  13. https://qt4cg.org/dashboard/#pr-1974
  14. https://qt4cg.org/dashboard/#pr-1971
  15. https://qt4cg.org/dashboard/#pr-1969
  16. https://qt4cg.org/dashboard/#pr-1968
  17. https://qt4cg.org/dashboard/#pr-1964
  18. https://qt4cg.org/dashboard/#pr-1963
  19. https://qt4cg.org/dashboard/#pr-1977
  20. https://qt4cg.org/dashboard/#pr-1976
  21. https://qt4cg.org/dashboard/#pr-1975
  22. https://qt4cg.org/dashboard/#pr-1971
  23. https://qt4cg.org/dashboard/#pr-1964
  24. https://qt4cg.org/dashboard/#pr-1959
  25. https://qt4cg.org/dashboard/#pr-1894
  26. https://qt4cg.org/dashboard/#pr-1888
  27. https://qt4cg.org/dashboard/#pr-1883
  28. https://github.com/qt4cg/qtspecs/issues/1777
  29. https://github.com/qt4cg/qtspecs/issues/1584
  30. https://github.com/qt4cg/qtspecs/issues/1240
  31. https://github.com/qt4cg/qtspecs/issues/1127
  32. https://github.com/qt4cg/qtspecs/issues/1045
  33. https://github.com/qt4cg/qtspecs/issues/1021
  34. https://github.com/qt4cg/qtspecs/issues/1011
  35. https://github.com/qt4cg/qtspecs/issues/986
  36. https://github.com/qt4cg/qtspecs/issues/967
  37. https://github.com/qt4cg/qtspecs/issues/748
  38. https://github.com/qt4cg/qtspecs/issues/714
  39. https://github.com/qt4cg/qtspecs/issues/675
  40. https://github.com/qt4cg/qtspecs/issues/407
  41. https://github.com/qt4cg/qtspecs/issues/366
  42. https://github.com/qt4cg/qtspecs/issues/272
  43. https://github.com/qt4cg/qtspecs/issues/1979
  44. https://github.com/qt4cg/qtspecs/issues/1970
  45. https://github.com/qt4cg/qtspecs/issues/1955
  46. https://github.com/qt4cg/qtspecs/issues/1949
  47. https://github.com/qt4cg/qtspecs/issues/1948
  48. https://github.com/qt4cg/qtspecs/issues/1946
  49. https://github.com/qt4cg/qtspecs/issues/1944
  50. https://github.com/qt4cg/qtspecs/issues/1938
  51. https://github.com/qt4cg/qtspecs/issues/1935
  52. https://github.com/qt4cg/qtspecs/issues/1934
  53. https://github.com/qt4cg/qtspecs/issues/1920
  54. https://github.com/qt4cg/qtspecs/issues/1912
  55. https://github.com/qt4cg/qtspecs/issues/1903
  56. https://github.com/qt4cg/qtspecs/issues/1885
  57. https://github.com/qt4cg/qtspecs/issues/1871
  58. https://github.com/qt4cg/qtspecs/issues/1868
  59. https://github.com/qt4cg/qtspecs/issues/1859
  60. https://github.com/qt4cg/qtspecs/issues/1852
  61. https://github.com/qt4cg/qtspecs/issues/1795
  62. https://github.com/qt4cg/qtspecs/issues/1787
  63. https://github.com/qt4cg/qtspecs/issues/1775
  64. https://github.com/qt4cg/qtspecs/issues/1774
  65. https://github.com/qt4cg/qtspecs/issues/1736
  66. https://github.com/qt4cg/qtspecs/issues/1718
  67. https://github.com/qt4cg/qtspecs/issues/1697
  68. https://github.com/qt4cg/qtspecs/issues/1661
  69. https://github.com/qt4cg/qtspecs/issues/1618
  70. https://github.com/qt4cg/qtspecs/issues/1591
  71. https://github.com/qt4cg/qtspecs/issues/1583
  72. https://github.com/qt4cg/qtspecs/issues/1528
  73. https://github.com/qt4cg/qtspecs/issues/1484
  74. https://github.com/qt4cg/qtspecs/issues/1479
  75. https://github.com/qt4cg/qtspecs/issues/1459
  76. https://github.com/qt4cg/qtspecs/issues/1310
  77. https://github.com/qt4cg/qtspecs/issues/1307
  78. https://github.com/qt4cg/qtspecs/issues/1175
  79. https://github.com/qt4cg/qtspecs/issues/760
  80. https://github.com/qt4cg/qtspecs/issues/641
  81. https://qt4cg.org/dashboard/#pr-1883
  82. https://qt4cg.org/dashboard/#pr-1894
  83. https://qt4cg.org/dashboard/#pr-1976
  84. https://qt4cg.org/dashboard/#pr-1975
  85. https://qt4cg.org/dashboard/#pr-1977
  86. https://qt4cg.org/dashboard/#pr-1971
  87. https://qt4cg.org/dashboard/#pr-1959
  88. https://qt4cg.org/dashboard/#pr-1888
  89. https://qt4cg.org/dashboard/#pr-1964
  90. https://github.com/qt4cg/qtspecs/issues/1832
  91. https://github.com/qt4cg/qtspecs/issues/1799
  92. https://github.com/qt4cg/qtspecs/issues/1797
  93. https://github.com/qt4cg/qtspecs/issues/760
  94. https://github.com/qt4cg/qtspecs/issues/641
  95. https://github.com/qt4cg/qtspecs/issues/119

                                        Be seeing you,
                                          norm

--
Norm Tovey-Walsh
Saxonica

Received on Monday, 5 May 2025 10:46:09 UTC