AW: QT4CG meeting 068 draft agenda, 3 March 2024

What about having a look at the features that have already been added to the spec, and the handling of test cases?

https://lists.w3.org/Archives/Public/public-xslt-40/2024Feb/0016.html
________________________________________

Von: Michael Kay <mike@saxonica.com>
Gesendet: Montag, 4. März 2024 14:04
An: Norm Tovey-Walsh
Cc: public-xslt-40@w3.org
Betreff: Re: QT4CG meeting 068 draft agenda, 3 March 2024

We're going to have some difficulty reviewing PRs unless the issue with non-availability of formatted documents can be fixed.

Mike

> On 4 Mar 2024, at 12:57, Norm Tovey-Walsh <norm@saxonica.com> wrote:
>
> Hi folks,
>
> Please find the agenda for this week below. There seems to be some problem with GitHub actions so it hasn’t been published to the website yet. I assume it’s a transient issue so I’ll keep retrying periodically.
>
> QT4 CG Meeting 068 Agenda 2024-03-05
>
>   [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:00EST,
>   08:00PST).
>
>   See the [6]meeting logistics page for details.
>
> 1. Administrivia
>
> 1.1. Roll call
>
>   Regrets DN.
>
> 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 5 March. The following meeting is scheduled
>   for 12 March.
>
>   Any regrets for 12 March 2024?
>
> 1.5. Review of open action items [1/12]
>
>   (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-056-04: MK to write a proposal for adding a select
>       attribute to xsl:text
>     * [ ] QT4CG-058-02: MK to consider providing more advice about the
>       pitfalls of mixing decimal and double when sorting
>     * [ ] QT4CG-063-01: MK to revise #956 especially with respect to the
>       options parameter
>     * [ ] QT4CG-063-02: JK to consider whether the roman numeral example
>       is appropriate for the spec.
>     * [ ] QT4CG-063-04: NW to try to add test review to the editorial
>       meeting.
>     * [ ] QT4CG-063-05: MK to revise PR #953 to take account of CG's
>       comments
>     * [ ] QT4CG-063-06: MK to consider refactoring the declare item type
>       syntax to something like declare record
>     * [ ] QT4CG-064-08: NW to open an issue to try to resolve $search to
>       $target consistently.
>     * [ ] QT4CG-066-01: MK to add a note that the grammar rules for
>       regular expressions apply after comments are removed
>     * [X] QT4CG-067-01: NW to ask the XML Prague organizers for hosting
>     * [ ] QT4CG-067-02: MK to revert the changes to the test suite for
>       EBV (PR 1003)
>
> 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]#529: 528 fn: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]#1051: 1043 Clarification of CSV edge cases
>     * PR [11]#1046: 1038 take-while predicate no longer uses EBV
>
> 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 [12]#1017: Change csv-to-xml() to produce an XHTML table
>     * Issue [13]#825: array:members-at
>     * Issue [14]#413: New function: parse-csv()
>
> 1.6.4. XSLT focused
>
>   The following PRs appear to be candidates for a future XSLT-focused
>   meeting.
>     * PR [15]#1015: 1013 [XSLT] Clarify effect of accumulator capture on
>       non-element nodes
>     * PR [16]#921: 920 Allow xsl:break and xsl:next-iteration within
>       branch of xsl:switch
>     * PR [17]#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 [18]#168: XSLT Extension Instructions invoking Named
>       Templates
>
> 1.6.5. Substantive PRs
>
>   The following substantive PRs were open when this agenda was prepared.
>     * PR [19]#1053: 1047 Default predicate for some#1 and every#1
>     * PR [20]#1049: 340-partial fn:format-number: Specifying decimal
>       format
>     * PR [21]#832: 77 Add map:deep-update and array:deep-update
>     * PR [22]#1027: 150 fn:ranks
>
> 1.6.6. Proposed for V4.0
>
>   The following issues are labled "proposed for V4.0".
>     * Issue [23]#938: Canonical serialization
>     * Issue [24]#910: Introduce a Kollection object with functions that
>       operate on all types of items that can be containers of unlimited
>       number of "members"
>     * Issue [25]#908: Function identity: documentation still too vague
>     * Issue [26]#882: fn:chain or fn:compose
>     * Issue [27]#850: fn:parse-html: Finalization
>     * Issue [28]#829: fn:boolean: EBV support for more item types
>     * Issue [29]#716: Generators in XPath
>     * Issue [30]#689: fn:stack-trace: keep, drop, replace with
>       $err:stack-trace ?
>     * Issue [31]#583: array:replace(), etc
>     * Issue [32]#557: fn:unparsed-binary: accessing and manipulating
>       binary types
>     * Issue [33]#340: fn:format-number: Specifying decimal format
>     * Issue [34]#283: Enumeration types
>     * Issue [35]#150: fn:ranks: Produce all ranks in applying a function
>       on the items of a sequence
>     * Issue [36]#33: JSON Parsing & Serialization: Numbers
>     * Issue [37]#31: Extend FLWOR expressions to maps
>
> 2. Technical Agenda
>
> 2.1. Review of blocked PRs
>
>   What's the status on these?
>     * PR [38]#956: 850-partial Editorial improvements to parse-html()
>     * PR [39]#529: 528 fn:elements-to-maps
>
> 2.2. PR #1053: 1047 Default predicate for some#1 and every#1
>
>   See PR [40]#1053
>
> 2.3. PR #1049: 340-partial fn:format-number: Specifying decimal format
>
>   See PR [41]#1049
>
> 2.4. PR #1027: 150 fn:ranks
>
>   See PR [42]#1027
>
> 2.5. PR #832: 77 Add map:deep-update and array:deep-update
>
>   See PR [43]#832
>
> 2.6. Issue #938: Canonical serialization
>
>   See issue [44]#938
>
> 2.7. Issue #908: Function identity: documentation still too vague
>
>   See issue [45]#908
>
> 2.8. Issue #850: fn:parse-html: Finalization
>
>   See issue [46]#850
>
> 2.9. Issue #829: fn:boolean: EBV support for more item types
>
>   See issue [47]#829
>
> 2.10. Issue #689: fn:stack-trace: keep, drop, replace with $err:stack-trace ?
>
>   See issue [48]#689
>
> 2.11. Issue #583: array:replace(), etc
>
>   See issue [49]#583
>
> 2.12. Issue #557: fn:unparsed-binary: accessing and manipulating binary types
>
>   See issue [50]#557
>
> 2.13. Issue #340: fn:format-number: Specifying decimal format
>
>   See issue [51]#340
>
> 2.14. Issue #283: Enumeration types
>
>   See issue [52]#283
>
> 2.15. Issue #150: fn:ranks: Produce all ranks in applying a function on the
> items of a sequence
>
>   See issue [53]#150
>
> 2.16. Issue #33: JSON Parsing & Serialization: Numbers
>
>   See issue [54]#33
>
> 2.17. Issue #31: Extend FLWOR expressions to maps
>
>   See issue [55]#31
>
> 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/02-27.html
>   8. https://qt4cg.org/dashboard/#pr-956
>   9. https://qt4cg.org/dashboard/#pr-529
>  10. https://qt4cg.org/dashboard/#pr-1051
>  11. https://qt4cg.org/dashboard/#pr-1046
>  12. https://github.com/qt4cg/qtspecs/issues/1017
>  13. https://github.com/qt4cg/qtspecs/issues/825
>  14. https://github.com/qt4cg/qtspecs/issues/413
>  15. https://qt4cg.org/dashboard/#pr-1015
>  16. https://qt4cg.org/dashboard/#pr-921
>  17. https://qt4cg.org/dashboard/#pr-871
>  18. https://github.com/qt4cg/qtspecs/issues/168
>  19. https://qt4cg.org/dashboard/#pr-1053
>  20. https://qt4cg.org/dashboard/#pr-1049
>  21. https://qt4cg.org/dashboard/#pr-832
>  22. https://qt4cg.org/dashboard/#pr-1027
>  23. https://github.com/qt4cg/qtspecs/issues/938
>  24. https://github.com/qt4cg/qtspecs/issues/910
>  25. https://github.com/qt4cg/qtspecs/issues/908
>  26. https://github.com/qt4cg/qtspecs/issues/882
>  27. https://github.com/qt4cg/qtspecs/issues/850
>  28. https://github.com/qt4cg/qtspecs/issues/829
>  29. https://github.com/qt4cg/qtspecs/issues/716
>  30. https://github.com/qt4cg/qtspecs/issues/689
>  31. https://github.com/qt4cg/qtspecs/issues/583
>  32. https://github.com/qt4cg/qtspecs/issues/557
>  33. https://github.com/qt4cg/qtspecs/issues/340
>  34. https://github.com/qt4cg/qtspecs/issues/283
>  35. https://github.com/qt4cg/qtspecs/issues/150
>  36. https://github.com/qt4cg/qtspecs/issues/33
>  37. https://github.com/qt4cg/qtspecs/issues/31
>  38. https://qt4cg.org/dashboard/#pr-956
>  39. https://qt4cg.org/dashboard/#pr-529
>  40. https://qt4cg.org/dashboard/#pr-1053
>  41. https://qt4cg.org/dashboard/#pr-1049
>  42. https://qt4cg.org/dashboard/#pr-1027
>  43. https://qt4cg.org/dashboard/#pr-832
>  44. https://github.com/qt4cg/qtspecs/issues/938
>  45. https://github.com/qt4cg/qtspecs/issues/908
>  46. https://github.com/qt4cg/qtspecs/issues/850
>  47. https://github.com/qt4cg/qtspecs/issues/829
>  48. https://github.com/qt4cg/qtspecs/issues/689
>  49. https://github.com/qt4cg/qtspecs/issues/583
>  50. https://github.com/qt4cg/qtspecs/issues/557
>  51. https://github.com/qt4cg/qtspecs/issues/340
>  52. https://github.com/qt4cg/qtspecs/issues/283
>  53. https://github.com/qt4cg/qtspecs/issues/150
>  54. https://github.com/qt4cg/qtspecs/issues/33
>  55. https://github.com/qt4cg/qtspecs/issues/31
>
>
>
>
>                                        Be seeing you,
>                                          norm
>
> --
> Norm Tovey-Walsh
> Saxonica

Received on Monday, 4 March 2024 13:43:05 UTC