QT4CG meeting 119 draft agenda, 29 April 2025

Hi folks,

Here’s the proposed agenda for tomorrow:

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

QT4 CG Meeting 119 Agenda 2025-04-29

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

1.5. Review of open action items [4/10]

   (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.
     * [X] QT4CG-113-02: NW to investigate a way to show extra attributes
       in the syntax summary.
     * [ ] QT4CG-115-02: JWL to write a few tests for xsl:record
     * [ ] QT4CG-116-01: Add a specific error code for unsupported options
       on doc and doc-available
     * [X] QT4CG-116-03: NW to review the star/plus/delta symbols in the
       ToC. (See [9]1838)
     * [ ] QT4CG-118-01: MK to make an incorrect type raise an error in
       #1906
     * [X] QT4CG-118-02: DN to open an issue about methods in records
     * [X] QT4CG-118-03: NW to make sure compose/chain and binary are on
       the agenda for next week

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 [10]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 [11]#1942: 37 Support sequence, array, and map destructuring
       declarations
     * 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]#1950: 1704 Add rules/notes for BOM and related topics
     * PR [15]#1945: 1568 unicode case blind collation
     * PR [16]#1906: 1797 elements-to-maps-conversion-plan function

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 [17]#1844: Drop mapping arrow operator
     * Issue [18]#1416: Key-value pairs: built-in record type `pair`
     * Issue [19]#1319: Specification Documents: Editors and Contributors

1.6.4. Substantive PRs

   The following substantive PRs were open when this agenda was prepared.
     * PR [20]#1961: Attempt to show that xsl:record allows extra
       attributes
     * PR [21]#1959: 1953 (part) XSLT Worked example using methods to
       implement atomic sets
     * PR [22]#1956: 1954 (part) Private variables and functions don't
       need to be in the module namespace
     * PR [23]#1933: 1271 fn:xsd-validator() function
     * PR [24]#1894: Additional examples to fn:chain - in a new branch
     * PR [25]#1888: 366 xsl:package-location
     * PR [26]#1883: 882 Replace fn:chain by fn:compose
     * PR [27]#1587: 557 Add fn:unparsed-binary function

1.6.5. 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.6. To be triaged

   The following issues need to be triaged.
     * Issue [43]#1958: Typo in map:build
     * Issue [44]#1957: Schema for XSLT incorrectly allows mixed content
       for xsl:output
     * Issue [45]#1955: fn:doc, fn:parse-xml: entity expansion
     * Issue [46]#1954: Private fields in records
     * Issue [47]#1952: Change option name from xsi-schema-location to
       use-xsi-schema-location
     * Issue [48]#1951: Some nits regarding the method attribute
     * Issue [49]#1949: fn:element-to-map: Updated Feedback
     * Issue [50]#1948: fn:element-to-map: Tests
     * Issue [51]#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 [52]#1944: Try/Catch/Finally - order of evaluation
     * Issue [53]#1938: Invoking coerced methods
     * Issue [54]#1935: doc-available() with invalid options
     * Issue [55]#1934: Supporting RELAX NG validation
     * Issue [56]#1920: Parse functions: determinism
     * Issue [57]#1912: Error handling: `fn:throw`
     * Issue [58]#1903: `fn:scan-left`, `fn:scan-right`: missing steps
     * Issue [59]#1889: HTML serialization: `html-version` and `version`
       parameters; allowed values
     * Issue [60]#1885: Use the spcification grammar markup to define the
       regular expression grammar in F&O
     * Issue [61]#1871: Arrays and maps: consistency
     * Issue [62]#1868: array:members() to include index position
     * Issue [63]#1859: Question on `fn:chain` and `err:FOAP0001`
     * Issue [64]#1852: fn:values-except: Return atomic values that occur
       in A but not in B
     * Issue [65]#1844: Drop mapping arrow operator
     * 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]#1736: Add option retain-order=false when constructing
       maps
     * Issue [71]#1718: Ordered Maps: positions in callback functions
     * Issue [72]#1697: Add documentary names to callback function
       signatures
     * Issue [73]#1661: QName arguments: also allow strings
     * 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]#1416: Key-value pairs: built-in record type `pair`
     * Issue [82]#1310: add fn:match-groups() function
     * Issue [83]#1307: For symmetry, add functions array:scan-left and
       array:scan-right
     * Issue [84]#1175: XPath: Optional parameters in the definition of an
       inline function
     * Issue [85]#760: Serialize functions: consistency
     * Issue [86]#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 [87]#1883: 882 Replace fn:chain by fn:compose
     * PR [88]#1894: Additional examples to fn:chain - in a new branch

2.3. PR #1587: 557 Add fn:unparsed-binary function

   See PR [89]#1587

2.4. PR #1961: Attempt to show that xsl:record allows extra attributes

   See PR [90]#1961

2.5. PR #1933: 1271 fn:xsd-validator() function

   See PR [91]#1933

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

   See PR [92]#1959

2.7. PR #1956: 1954 (part) Private variables and functions don't need to be
in the module namespace

   See PR [93]#1956

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

   See PR [94]#1888

2.9. Issue triage

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

   See issue [95]#1832

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

   See issue [96]#1799

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

   See issue [97]#1797

2.9.4. Issue #760: Serialize functions: consistency

   See issue [98]#760

2.9.5. Issue #641: Serialization fallback.

   See issue [99]#641

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

   See issue [100]#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-22.html
   9. https://github.com/qt4cg/qtspecs/pull/1838#issuecomment-2682372207
  10. https://qt4cg.org/meeting/agenda/2025/04-29.html#technical-agenda
  11. https://qt4cg.org/dashboard/#pr-1942
  12. https://qt4cg.org/dashboard/#pr-1283
  13. https://qt4cg.org/dashboard/#pr-1062
  14. https://qt4cg.org/dashboard/#pr-1950
  15. https://qt4cg.org/dashboard/#pr-1945
  16. https://qt4cg.org/dashboard/#pr-1906
  17. https://github.com/qt4cg/qtspecs/issues/1844
  18. https://github.com/qt4cg/qtspecs/issues/1416
  19. https://github.com/qt4cg/qtspecs/issues/1319
  20. https://qt4cg.org/dashboard/#pr-1961
  21. https://qt4cg.org/dashboard/#pr-1959
  22. https://qt4cg.org/dashboard/#pr-1956
  23. https://qt4cg.org/dashboard/#pr-1933
  24. https://qt4cg.org/dashboard/#pr-1894
  25. https://qt4cg.org/dashboard/#pr-1888
  26. https://qt4cg.org/dashboard/#pr-1883
  27. https://qt4cg.org/dashboard/#pr-1587
  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/1958
  44. https://github.com/qt4cg/qtspecs/issues/1957
  45. https://github.com/qt4cg/qtspecs/issues/1955
  46. https://github.com/qt4cg/qtspecs/issues/1954
  47. https://github.com/qt4cg/qtspecs/issues/1952
  48. https://github.com/qt4cg/qtspecs/issues/1951
  49. https://github.com/qt4cg/qtspecs/issues/1949
  50. https://github.com/qt4cg/qtspecs/issues/1948
  51. https://github.com/qt4cg/qtspecs/issues/1946
  52. https://github.com/qt4cg/qtspecs/issues/1944
  53. https://github.com/qt4cg/qtspecs/issues/1938
  54. https://github.com/qt4cg/qtspecs/issues/1935
  55. https://github.com/qt4cg/qtspecs/issues/1934
  56. https://github.com/qt4cg/qtspecs/issues/1920
  57. https://github.com/qt4cg/qtspecs/issues/1912
  58. https://github.com/qt4cg/qtspecs/issues/1903
  59. https://github.com/qt4cg/qtspecs/issues/1889
  60. https://github.com/qt4cg/qtspecs/issues/1885
  61. https://github.com/qt4cg/qtspecs/issues/1871
  62. https://github.com/qt4cg/qtspecs/issues/1868
  63. https://github.com/qt4cg/qtspecs/issues/1859
  64. https://github.com/qt4cg/qtspecs/issues/1852
  65. https://github.com/qt4cg/qtspecs/issues/1844
  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/1736
  71. https://github.com/qt4cg/qtspecs/issues/1718
  72. https://github.com/qt4cg/qtspecs/issues/1697
  73. https://github.com/qt4cg/qtspecs/issues/1661
  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/1416
  82. https://github.com/qt4cg/qtspecs/issues/1310
  83. https://github.com/qt4cg/qtspecs/issues/1307
  84. https://github.com/qt4cg/qtspecs/issues/1175
  85. https://github.com/qt4cg/qtspecs/issues/760
  86. https://github.com/qt4cg/qtspecs/issues/641
  87. https://qt4cg.org/dashboard/#pr-1883
  88. https://qt4cg.org/dashboard/#pr-1894
  89. https://qt4cg.org/dashboard/#pr-1587
  90. https://qt4cg.org/dashboard/#pr-1961
  91. https://qt4cg.org/dashboard/#pr-1933
  92. https://qt4cg.org/dashboard/#pr-1959
  93. https://qt4cg.org/dashboard/#pr-1956
  94. https://qt4cg.org/dashboard/#pr-1888
  95. https://github.com/qt4cg/qtspecs/issues/1832
  96. https://github.com/qt4cg/qtspecs/issues/1799
  97. https://github.com/qt4cg/qtspecs/issues/1797
  98. https://github.com/qt4cg/qtspecs/issues/760
  99. https://github.com/qt4cg/qtspecs/issues/641
 100. https://github.com/qt4cg/qtspecs/issues/119

                                        Be seeing you,
                                          norm

--
Norm Tovey-Walsh
Saxonica

Received on Monday, 28 April 2025 09:10:36 UTC