QT4CG Agenda 055, 21 November 2023

Here’s the agenda for tomorrow’s call:

   https://qt4cg.org/meeting/agenda/2023/11-21.html

QT4 CG Meeting 055 Agenda 2023-11-21

   [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 (17:00CEST, 11:00EDT,
   08:00PDT).

   See the [6]meeting logistics page for details.

1. Administrivia

1.1. Roll call

1.2. Approve the agenda

1.3. Approve minutes of previous meeting

   Minutes of [7]the previous meeting.

1.4. Next meeting

   This meeting is planned for 21 November, the following meeting is
   scheduled for 28 November.

   Any regrets for the following meeting?

   Shall we make 28 November an XSLT-focused meeting?

1.5. Review of open action items [1/8]

   (Items marked [X] are believed to have been closed via email before
   this agenda was posted.)
     * [ ] QT4CG-052-02: NW to consider how to schedule an "editor's
       meeting"
     * [ ] QT4CG-052-05: MK to rename the hexBinary-equal function to
       binary-equal?
     * [ ] QT4CG-052-06: MK to consider the editorial question of
       "promotion" for the symmetric relations.

1.6. Review of open pull requests and issues

1.6.1. Blocked

   The following PRs are open but have merge conflicts or comments which
   suggest they aren't ready for action.
     * PR [8]#795: 655: fn:sort-with
     * PR [9]#529: 528: revision of json(), and renaming to
       elements-to-maps()

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 [10]#846: 845 Drop mention of tuples
     * PR [11]#842: Improve stylesheet for generating keyword tests
     * PR [12]#841: 840: Typo in fn:seconds-from-duration example
     * PR [13]#833: Fix the line endings, force a single lf in text files

1.6.3. XSLT focused

   The following PRs appear to be candidates for a future XSLT-focussed
   meeting.
     * PR [14]#470: 369: add fixed-prefixes attribute in XSLT
     * PR [15]#412: 409, QT4CG-027-01: xsl:next-match

   These issues identify the XSLT-focused changes that have been made to
   the specifications but which have not been established by the community
   group as the status quo.
     * Issue [16]#742: xsl:function-library: keep, drop, or refine?
     * Issue [17]#169: Handling of duplicate keys in xsl:map
     * Issue [18]#168: XSLT Extension Instructions invoking Named
       Templates

1.6.4. Substantive PRs

   The following substantive PRs were open when this agenda was prepared.
     * PR [19]#837: 297 Deep Lookup Operator "??" and wildcard qualifier
       "::"
     * PR [20]#832: 77 Add map:deep-update and array:deep-update
     * PR [21]#798: 479: fn:deep-equal: Input order
     * PR [22]#737: 295: Boost the capability of recursive record types

1.6.5. Proposed for V4.0

   The following issues are labled "proposed for V4.0".
     * Issue [23]#716: Generators in XPath
     * Issue [24]#689: fn:stack-trace: keep or drop?
     * Issue [25]#583: array:replace(), etc
     * Issue [26]#557: fn:unparsed-binary: accessing and manipulating
       binary types
     * Issue [27]#340: fn:format-number: Specifying decimal format
     * Issue [28]#260: array:index-of
     * Issue [29]#33: json parsing number type option
     * Issue [30]#31: Extend FLWOR expressions to maps
     __________________________________________________________________

2. Technical Agenda

2.1. PR #837: 297 Deep Lookup Operator "??" and wildcard qualifier "::"

   See PR [31]#837

2.2. PR #832: 77 Add map:deep-update and array:deep-update

   See PR [32]#832

2.3. PR #798: 479: fn:deep-equal: Input order

   See PR [33]#798

2.4. PR #737: 295: Boost the capability of recursive record types

   See PR [34]#737

2.5. Issue 844: Added standard functions: Names

   See issue [35]844.

2.6. Issue 843: Standard array and map functions: equivalencies

   See issue [36]843.

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://qt4cg.org/meeting/logistics.html
   7. https://qt4cg.org/meeting/minutes/2023/11-14.html
   8. https://qt4cg.org/dashboard/#pr-795
   9. https://qt4cg.org/dashboard/#pr-529
  10. https://qt4cg.org/dashboard/#pr-846
  11. https://qt4cg.org/dashboard/#pr-842
  12. https://qt4cg.org/dashboard/#pr-841
  13. https://qt4cg.org/dashboard/#pr-833
  14. https://qt4cg.org/dashboard/#pr-470
  15. https://qt4cg.org/dashboard/#pr-412
  16. https://github.com/qt4cg/qtspecs/issues/742
  17. https://github.com/qt4cg/qtspecs/issues/169
  18. https://github.com/qt4cg/qtspecs/issues/168
  19. https://qt4cg.org/dashboard/#pr-837
  20. https://qt4cg.org/dashboard/#pr-832
  21. https://qt4cg.org/dashboard/#pr-798
  22. https://qt4cg.org/dashboard/#pr-737
  23. https://github.com/qt4cg/qtspecs/issues/716
  24. https://github.com/qt4cg/qtspecs/issues/689
  25. https://github.com/qt4cg/qtspecs/issues/583
  26. https://github.com/qt4cg/qtspecs/issues/557
  27. https://github.com/qt4cg/qtspecs/issues/340
  28. https://github.com/qt4cg/qtspecs/issues/260
  29. https://github.com/qt4cg/qtspecs/issues/33
  30. https://github.com/qt4cg/qtspecs/issues/31
  31. https://qt4cg.org/dashboard/#pr-837
  32. https://qt4cg.org/dashboard/#pr-832
  33. https://qt4cg.org/dashboard/#pr-798
  34. https://qt4cg.org/dashboard/#pr-737
  35. https://github.com/qt4cg/qtspecs/issues/844
  36. https://github.com/qt4cg/qtspecs/issues/843

                                        Be seeing you,
                                          norm

--
Norm Tovey-Walsh
Saxonica