QT4CG meeting 122 draft agenda, 20 May 2025

Hi folks,

Here’s the agenda for tomorrow’s meeting.

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

QT4 CG Meeting 122 Agenda 2025-05-20

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

   The meeting after that is 3 June, the same week as MarkupUK. I'm
   tempted to suggest that we skip that week.

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-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
     * [ ] QT4CG-021-01: MK to raise a new issue which may propose a
       subset of the QNameLiteral which doesn't permit a namespace.
     * [ ] QT4CG-121-02: MK to fix removal of default values in the
       options for fn:serialize()

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]#1999: 1992 Correct type of constructor function in
       schema-type-record
     * PR [15]#1998: 1997 Correct nesting of item coercion rules

1.6.3. Substantive PRs

   The following substantive PRs were open when this agenda was prepared.
     * PR [16]#2001: 1085 Revert fn:sort to the 3.1 spec; introduce
       fn:sort-by
     * PR [17]#1991: 835 Add built-in named record types to static context
     * PR [18]#2008: 2004 Add xsl:xpath instruction
     * PR [19]#2006: 2005 Add fn:apply-templates function
     * PR [20]#1959: 1953 (part) XSLT Worked example using methods to
       implement atomic sets
     * PR [21]#2011: 675(part): Add XSLT static typing rules for new kinds
       of XPath expression
     * PR [22]#1942: 37 Support sequence, array, and map destructuring
       declarations
          + Is this ready for further discussion?
     * PR [23]#1888: 366 xsl:package-location
          + Is this ready for further discussion?

1.6.4. Required for V4.0

   The following issues are labeled "required for V4.0".
     * Issue [24]#1777: Shallow copy in XSLT with maps and arrays
     * Issue [25]#1584: Review the XML Schema and RELAX NG schemas for
       XSLT 4.0 for compatibility
     * Issue [26]#1127: Binary resources
     * Issue [27]#1045: Functions to manage namespace usage
     * Issue [28]#1021: Extend `fn:doc`, `fn:collection` and
       `fn:uri-collection` with options maps
     * Issue [29]#1011: fn:transform() improvements
     * Issue [30]#986: Numeric Comparisons
     * Issue [31]#967: XPath Appendix I: Comparisons
     * Issue [32]#748: Parse functions: consistency
     * Issue [33]#714: Function annotations in XSLT
     * Issue [34]#675: XSLT streaming rules for new constructs
     * Issue [35]#407: XSLT-specific context properties used in function
       items
     * Issue [36]#366: Support xsl:use-package with xsl:package-location
     * Issue [37]#272: Setting parameter values in xsl:use-package

1.6.5. To be triaged

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

2. Technical agenda

2.1. Review of pull requests

2.2. PR #2001: 1085 Revert fn:sort to the 3.1 spec; introduce fn:sort-by

   See PR [86]#2001

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

   See PR [87]#1991

2.4. PR #2008: 2004 Add xsl:xpath instruction

   See PR [88]#2008

2.5. PR #2006: 2005 Add fn:apply-templates function

   See PR [89]#2006

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

   See PR [90]#1959

2.7. PR #2011: 675(part): Add XSLT static typing rules for new kinds of XPath
expression

   See PR [91]#2011

2.8. PR #1942: 37 Support sequence, array, and map destructuring declarations

   See PR [92]#1942

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

   See PR [93]#1888

2.10. Issue triage

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

   See issue [94]#1832

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

   See issue [95]#1799

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

   See issue [96]#1797

2.10.4. Issue #760: Serialize functions: consistency

   See issue [97]#760

2.10.5. Issue #641: Serialization fallback.

   See issue [98]#641

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

   See issue [99]#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-13.html
   9. https://qt4cg.org/meeting/agenda/2025/05-20.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-1999
  15. https://qt4cg.org/dashboard/#pr-1998
  16. https://qt4cg.org/dashboard/#pr-2001
  17. https://qt4cg.org/dashboard/#pr-1991
  18. https://qt4cg.org/dashboard/#pr-2008
  19. https://qt4cg.org/dashboard/#pr-2006
  20. https://qt4cg.org/dashboard/#pr-1959
  21. https://qt4cg.org/dashboard/#pr-2011
  22. https://qt4cg.org/dashboard/#pr-1942
  23. https://qt4cg.org/dashboard/#pr-1888
  24. https://github.com/qt4cg/qtspecs/issues/1777
  25. https://github.com/qt4cg/qtspecs/issues/1584
  26. https://github.com/qt4cg/qtspecs/issues/1127
  27. https://github.com/qt4cg/qtspecs/issues/1045
  28. https://github.com/qt4cg/qtspecs/issues/1021
  29. https://github.com/qt4cg/qtspecs/issues/1011
  30. https://github.com/qt4cg/qtspecs/issues/986
  31. https://github.com/qt4cg/qtspecs/issues/967
  32. https://github.com/qt4cg/qtspecs/issues/748
  33. https://github.com/qt4cg/qtspecs/issues/714
  34. https://github.com/qt4cg/qtspecs/issues/675
  35. https://github.com/qt4cg/qtspecs/issues/407
  36. https://github.com/qt4cg/qtspecs/issues/366
  37. https://github.com/qt4cg/qtspecs/issues/272
  38. https://github.com/qt4cg/qtspecs/issues/2012
  39. https://github.com/qt4cg/qtspecs/issues/2010
  40. https://github.com/qt4cg/qtspecs/issues/2009
  41. https://github.com/qt4cg/qtspecs/issues/2007
  42. https://github.com/qt4cg/qtspecs/issues/2005
  43. https://github.com/qt4cg/qtspecs/issues/2003
  44. https://github.com/qt4cg/qtspecs/issues/2002
  45. https://github.com/qt4cg/qtspecs/issues/2000
  46. https://github.com/qt4cg/qtspecs/issues/1996
  47. https://github.com/qt4cg/qtspecs/issues/1995
  48. https://github.com/qt4cg/qtspecs/issues/1980
  49. https://github.com/qt4cg/qtspecs/issues/1979
  50. https://github.com/qt4cg/qtspecs/issues/1970
  51. https://github.com/qt4cg/qtspecs/issues/1955
  52. https://github.com/qt4cg/qtspecs/issues/1949
  53. https://github.com/qt4cg/qtspecs/issues/1948
  54. https://github.com/qt4cg/qtspecs/issues/1946
  55. https://github.com/qt4cg/qtspecs/issues/1944
  56. https://github.com/qt4cg/qtspecs/issues/1938
  57. https://github.com/qt4cg/qtspecs/issues/1935
  58. https://github.com/qt4cg/qtspecs/issues/1934
  59. https://github.com/qt4cg/qtspecs/issues/1920
  60. https://github.com/qt4cg/qtspecs/issues/1912
  61. https://github.com/qt4cg/qtspecs/issues/1903
  62. https://github.com/qt4cg/qtspecs/issues/1885
  63. https://github.com/qt4cg/qtspecs/issues/1871
  64. https://github.com/qt4cg/qtspecs/issues/1868
  65. https://github.com/qt4cg/qtspecs/issues/1859
  66. https://github.com/qt4cg/qtspecs/issues/1852
  67. https://github.com/qt4cg/qtspecs/issues/1795
  68. https://github.com/qt4cg/qtspecs/issues/1787
  69. https://github.com/qt4cg/qtspecs/issues/1775
  70. https://github.com/qt4cg/qtspecs/issues/1774
  71. https://github.com/qt4cg/qtspecs/issues/1736
  72. https://github.com/qt4cg/qtspecs/issues/1718
  73. https://github.com/qt4cg/qtspecs/issues/1697
  74. https://github.com/qt4cg/qtspecs/issues/1618
  75. https://github.com/qt4cg/qtspecs/issues/1591
  76. https://github.com/qt4cg/qtspecs/issues/1583
  77. https://github.com/qt4cg/qtspecs/issues/1528
  78. https://github.com/qt4cg/qtspecs/issues/1484
  79. https://github.com/qt4cg/qtspecs/issues/1479
  80. https://github.com/qt4cg/qtspecs/issues/1459
  81. https://github.com/qt4cg/qtspecs/issues/1310
  82. https://github.com/qt4cg/qtspecs/issues/1307
  83. https://github.com/qt4cg/qtspecs/issues/1175
  84. https://github.com/qt4cg/qtspecs/issues/760
  85. https://github.com/qt4cg/qtspecs/issues/641
  86. https://qt4cg.org/dashboard/#pr-2001
  87. https://qt4cg.org/dashboard/#pr-1991
  88. https://qt4cg.org/dashboard/#pr-2008
  89. https://qt4cg.org/dashboard/#pr-2006
  90. https://qt4cg.org/dashboard/#pr-1959
  91. https://qt4cg.org/dashboard/#pr-2011
  92. https://qt4cg.org/dashboard/#pr-1942
  93. https://qt4cg.org/dashboard/#pr-1888
  94. https://github.com/qt4cg/qtspecs/issues/1832
  95. https://github.com/qt4cg/qtspecs/issues/1799
  96. https://github.com/qt4cg/qtspecs/issues/1797
  97. https://github.com/qt4cg/qtspecs/issues/760
  98. https://github.com/qt4cg/qtspecs/issues/641
  99. https://github.com/qt4cg/qtspecs/issues/119

                                        Be seeing you,
                                          norm

--
Norm Tovey-Walsh
Saxonica

Received on Monday, 19 May 2025 10:10:59 UTC