QT4CG meeting 121 draft agenda, 13 May 2025

Hello,

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

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

As I said last week, I’m at risk for tomorrow. In my absence, please pick a chair and a scribe. If the scribe sends me the notes, I’ll wrangle them into shape for publication.

I tried to construct a straightforward agenda, but if you run out of PRs you are ready to discuss, feel free to try doing some of that issue triage we keep talking about :-)

QT4 CG Meeting 121 Agenda 2025-05-13

   [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 13 May 2025. The following meeting is
   scheduled for 20 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
     * [ ] 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]#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]#1988: 1986 Drop obsolete notes on error reporting

1.6.3. Substantive PRs

   The following substantive PRs were open when this agenda was prepared.
     * PR [15]#1991: 835 Add built-in named record types to static context
     * PR [16]#1990: Update schema-for-xslt40.xsd
     * PR [17]#1989: 1983 QName literals in node constructors
     * PR [18]#1987: 1985 Tidy up namespace terminology
     * PR [19]#1984: 882 Drop fn:chain
     * PR [20]#1982: 1981 Ambiguity with qname literals and pragmas
     * PR [21]#1977: 1889 Tidy up handling of HTML serialization version,
       default to HTML5
     * PR [22]#1959: 1953 (part) XSLT Worked example using methods to
       implement atomic sets
     * PR [23]#1894: Additional examples to fn:chain - in a new branch
     * PR [24]#1888: 366 xsl:package-location

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

2. Technical agenda

2.1. Review of pull requests

2.1.1. PR #1989: 1983 QName literals in node constructors

   See PR [78]#1989

2.1.2. PR #1982: 1981 Ambiguity with qname literals and pragmas

   See PR [79]#1982

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

   See PR [80]#1977

2.1.4. PR #1987: 1985 Tidy up namespace terminology

   See PR [81]#1987

2.1.5. PR #1990: Update schema-for-xslt40.xsd

   See PR [82]#1990

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

   See PR [83]#1888

2.1.7. PR #1991: 835 Add built-in named record types to static context

   See PR [84]#1991

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

   See PR [85]#1959

2.2. Issue triage

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

   See issue [86]#1832

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

   See issue [87]#1799

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

   See issue [88]#1797

2.2.4. Issue #760: Serialize functions: consistency

   See issue [89]#760

2.2.5. Issue #641: Serialization fallback.

   See issue [90]#641

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

   See issue [91]#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-06.html
   9. https://qt4cg.org/meeting/agenda/2025/05-13.html#technical-agenda
  10. https://qt4cg.org/dashboard/#pr-1942
  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-1988
  15. https://qt4cg.org/dashboard/#pr-1991
  16. https://qt4cg.org/dashboard/#pr-1990
  17. https://qt4cg.org/dashboard/#pr-1989
  18. https://qt4cg.org/dashboard/#pr-1987
  19. https://qt4cg.org/dashboard/#pr-1984
  20. https://qt4cg.org/dashboard/#pr-1982
  21. https://qt4cg.org/dashboard/#pr-1977
  22. https://qt4cg.org/dashboard/#pr-1959
  23. https://qt4cg.org/dashboard/#pr-1894
  24. https://qt4cg.org/dashboard/#pr-1888
  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/1992
  40. https://github.com/qt4cg/qtspecs/issues/1980
  41. https://github.com/qt4cg/qtspecs/issues/1979
  42. https://github.com/qt4cg/qtspecs/issues/1970
  43. https://github.com/qt4cg/qtspecs/issues/1955
  44. https://github.com/qt4cg/qtspecs/issues/1949
  45. https://github.com/qt4cg/qtspecs/issues/1948
  46. https://github.com/qt4cg/qtspecs/issues/1946
  47. https://github.com/qt4cg/qtspecs/issues/1944
  48. https://github.com/qt4cg/qtspecs/issues/1938
  49. https://github.com/qt4cg/qtspecs/issues/1935
  50. https://github.com/qt4cg/qtspecs/issues/1934
  51. https://github.com/qt4cg/qtspecs/issues/1920
  52. https://github.com/qt4cg/qtspecs/issues/1912
  53. https://github.com/qt4cg/qtspecs/issues/1903
  54. https://github.com/qt4cg/qtspecs/issues/1885
  55. https://github.com/qt4cg/qtspecs/issues/1871
  56. https://github.com/qt4cg/qtspecs/issues/1868
  57. https://github.com/qt4cg/qtspecs/issues/1859
  58. https://github.com/qt4cg/qtspecs/issues/1852
  59. https://github.com/qt4cg/qtspecs/issues/1795
  60. https://github.com/qt4cg/qtspecs/issues/1787
  61. https://github.com/qt4cg/qtspecs/issues/1775
  62. https://github.com/qt4cg/qtspecs/issues/1774
  63. https://github.com/qt4cg/qtspecs/issues/1736
  64. https://github.com/qt4cg/qtspecs/issues/1718
  65. https://github.com/qt4cg/qtspecs/issues/1697
  66. https://github.com/qt4cg/qtspecs/issues/1618
  67. https://github.com/qt4cg/qtspecs/issues/1591
  68. https://github.com/qt4cg/qtspecs/issues/1583
  69. https://github.com/qt4cg/qtspecs/issues/1528
  70. https://github.com/qt4cg/qtspecs/issues/1484
  71. https://github.com/qt4cg/qtspecs/issues/1479
  72. https://github.com/qt4cg/qtspecs/issues/1459
  73. https://github.com/qt4cg/qtspecs/issues/1310
  74. https://github.com/qt4cg/qtspecs/issues/1307
  75. https://github.com/qt4cg/qtspecs/issues/1175
  76. https://github.com/qt4cg/qtspecs/issues/760
  77. https://github.com/qt4cg/qtspecs/issues/641
  78. https://qt4cg.org/dashboard/#pr-1989
  79. https://qt4cg.org/dashboard/#pr-1982
  80. https://qt4cg.org/dashboard/#pr-1977
  81. https://qt4cg.org/dashboard/#pr-1987
  82. https://qt4cg.org/dashboard/#pr-1990
  83. https://qt4cg.org/dashboard/#pr-1888
  84. https://qt4cg.org/dashboard/#pr-1991
  85. https://qt4cg.org/dashboard/#pr-1959
  86. https://github.com/qt4cg/qtspecs/issues/1832
  87. https://github.com/qt4cg/qtspecs/issues/1799
  88. https://github.com/qt4cg/qtspecs/issues/1797
  89. https://github.com/qt4cg/qtspecs/issues/760
  90. https://github.com/qt4cg/qtspecs/issues/641
  91. https://github.com/qt4cg/qtspecs/issues/119

                                        Be seeing you,
                                          norm

--
Norm Tovey-Walsh
Saxonica

Received on Monday, 12 May 2025 08:46:48 UTC