QT4CG meeting 076 draft agenda, 7 May 2024 from Norm Tovey-Walsh on 2024-05-06 (public-xslt-40@w3.org from May 2024)

From: Norm Tovey-Walsh <norm@saxonica.com>
Date: Mon, 06 May 2024 10:07:34 +0100
To: "public-xslt-40@w3.org" <public-xslt-40@w3.org>
Message-ID: <m2a5l3e26c.fsf@saxonica.com>
Hello,

Here is the agenda for tomorrow’s QT4CG meeting. Apologies that it was somewhat hastily constructed from a remote outpost in the wilds of Norfolk[*] on a bank holiday weekend.

   https://qt4cg.org/meeting/agenda/2024/05-07.html

QT4 CG Meeting 076 Agenda 2024-05-07

   [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)

   See the [6]meeting logistics page for details.

1. Administrivia

1.1. Roll call

   NW gives regrets, MSM to chair.

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 7 May. The following meeting is scheduled
   for 14 May.

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-063-06: MK to consider refactoring the declare item type
       syntax to something like declare record
     * [ ] QT4CG-071-06: NW to clarify the cases that are distinguished by
       the leading empty string in path segments
     * [ ] QT4CG-072-03: NW to clarify the round-tripping of URIs
     * [ ] QT4CG-073-01: NW to proceed with the records/options proposal
       and make a PR.
     * [ ] QT4CG-075-01: MK to drop the deterministic option and raise it
       as a separate issue.
     * [ ] QT4CG-075-02: MK to define sequence-concatenation more formally
       with links where appropriate
     * [ ] QT4CG-075-03: CG to make changes to map:values analagous to
       MK's changes to array:values

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]#956: 850-partial Editorial improvements to parse-html()
     * PR [9]#832: 77 Add map:deep-update and array:deep-update
     * PR [10]#529: 528 fn:elements-to-maps

1.6.2. XSLT focused

   The following PRs appear to be candidates for a future XSLT-focused
   meeting.
     * PR [11]#1181: 296 Allow default-namespace=##any
     * PR [12]#1015: 1013 [XSLT] Clarify effect of accumulator capture on
       non-element nodes
     * PR [13]#921: 920 Allow xsl:break and xsl:next-iteration within
       branch of xsl:switch
     * PR [14]#871: Action qt4 cg 027 01 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 [15]#168: XSLT Extension Instructions invoking Named
       Templates

1.6.3. Substantive PRs

   The following substantive PRs were open when this agenda was prepared.
     * PR [16]#1186: 1170 Editorial: fn:index-where
     * PR [17]#1185: 1179 array:values, map:values -> contents
     * PR [18]#1184: 1165-Use Unicode-style character references
     * PR [19]#1182: 1171 Change predicate callbacks to allow empty return
       value
     * PR [20]#1148: 1143 Coercion rules: handle choice types before
       atomization
     * PR [21]#1117: 1116 Add options param to unparsed-text
     * PR [22]#1108: 566-partial Describe a less aggressive %-encoding for
       fn:build-uri
     * PR [23]#1098: 566-partial Editorial improvements for parse-uri
     * PR [24]#1068: 73 fn:graphemes
     * PR [25]#1062: 150bis - revised proposal for fn:ranks
     * PR [26]#1027: 150 fn:ranks

1.6.4. Proposed for V4.0

   The following issues are labled "proposed for V4.0".
     * Issue [27]#1069: fn:ucd
     * Issue [28]#982: Add position argument to scan-left and scan-right
     * Issue [29]#938: Canonical serialization
     * Issue [30]#934: String comparison in deep-equal
     * Issue [31]#910: Introduce a Kollection object with functions that
       operate on all types of items that can be containers of unlimited
       number of "members"
     * Issue [32]#908: Function identity: documentation, nondeterminism
     * Issue [33]#882: fn:chain or fn:compose
     * Issue [34]#850: fn:parse-html: Finalization
     * Issue [35]#716: Generators in XPath
     * Issue [36]#689: fn:stack-trace: keep, drop, replace with
       $err:stack-trace ?
     * Issue [37]#657: User-defined functions in main modules without
       `local` prefix
     * Issue [38]#557: fn:unparsed-binary: accessing and manipulating
       binary types
     * Issue [39]#150: fn:ranks: Produce all ranks in applying a function
       on the items of a sequence
     * Issue [40]#31: Extend FLWOR expressions to maps

2. Technical Agenda

2.1. PR #1186: 1170 Editorial: fn:index-where

   See [41]PR #1186.

2.2. PR #1185: 1179 array:values, map:values -> contents

   See [42]PR #1185.

2.3. PR #1184: 1165-Use Unicode-style character references

   See [43]PR #1184.

2.4. PR #1182: 1171 Change predicate callbacks to allow empty return value

   See [44]PR #1182.

2.5. PR #1148: 1143 Coercion rules: handle choice types before atomization

   See PR [45]#1148

2.6. PR #1117: 1116 Add options param to unparsed-text

   See PR [46]#1117

2.7. PR #1068: 73 fn:graphemes

   See PR [47]#1068

2.8. PR #1062/#1027: fn:ranks

   See PR [48]#1062 See PR [49]#1027

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/2024/04-30.html
   8. https://qt4cg.org/dashboard/#pr-956
   9. https://qt4cg.org/dashboard/#pr-832
  10. https://qt4cg.org/dashboard/#pr-529
  11. https://qt4cg.org/dashboard/#pr-1181
  12. https://qt4cg.org/dashboard/#pr-1015
  13. https://qt4cg.org/dashboard/#pr-921
  14. https://qt4cg.org/dashboard/#pr-871
  15. https://github.com/qt4cg/qtspecs/issues/168
  16. https://qt4cg.org/dashboard/#pr-1186
  17. https://qt4cg.org/dashboard/#pr-1185
  18. https://qt4cg.org/dashboard/#pr-1184
  19. https://qt4cg.org/dashboard/#pr-1182
  20. https://qt4cg.org/dashboard/#pr-1148
  21. https://qt4cg.org/dashboard/#pr-1117
  22. https://qt4cg.org/dashboard/#pr-1108
  23. https://qt4cg.org/dashboard/#pr-1098
  24. https://qt4cg.org/dashboard/#pr-1068
  25. https://qt4cg.org/dashboard/#pr-1062
  26. https://qt4cg.org/dashboard/#pr-1027
  27. https://github.com/qt4cg/qtspecs/issues/1069
  28. https://github.com/qt4cg/qtspecs/issues/982
  29. https://github.com/qt4cg/qtspecs/issues/938
  30. https://github.com/qt4cg/qtspecs/issues/934
  31. https://github.com/qt4cg/qtspecs/issues/910
  32. https://github.com/qt4cg/qtspecs/issues/908
  33. https://github.com/qt4cg/qtspecs/issues/882
  34. https://github.com/qt4cg/qtspecs/issues/850
  35. https://github.com/qt4cg/qtspecs/issues/716
  36. https://github.com/qt4cg/qtspecs/issues/689
  37. https://github.com/qt4cg/qtspecs/issues/657
  38. https://github.com/qt4cg/qtspecs/issues/557
  39. https://github.com/qt4cg/qtspecs/issues/150
  40. https://github.com/qt4cg/qtspecs/issues/31
  41. https://qt4cg.org/dashboard/#pr-1186
  42. https://qt4cg.org/dashboard/#pr-1185
  43. https://qt4cg.org/dashboard/#pr-1184
  44. https://qt4cg.org/dashboard/#pr-1182
  45. https://qt4cg.org/dashboard/#pr-1148
  46. https://qt4cg.org/dashboard/#pr-1117
  47. https://qt4cg.org/dashboard/#pr-1068
  48. https://qt4cg.org/dashboard/#pr-1062
  49. https://qt4cg.org/dashboard/#pr-1027

                                        Be seeing you,
                                          norm

[*] Okay, to be fair, the exurbs of Norwich aren’t an especially remote outpost, nor especially wild, but a man can dream.

--
Norm Tovey-Walsh
Saxonica
Received on Monday, 6 May 2024 09:10:27 UTC