QT4CG meeting 065 draft agenda, 13 February 2024

Hello,

Here’s the agenda for tomorrow, a continuation of last week’s agenda as agreed.

   https://qt4cg.org/meeting/agenda/2024/02-13.html

QT4 CG Meeting 065 Agenda 2024-02-13

   [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 13 February. The following meeting is
   scheduled for 20 February.

   Any regrets for 20 February 2024?

1.5. Review of open action items [3/18]

   (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
     * [X] QT4CG-062-03: JK to revise the fn:hash function along the lines
       discussed at the meeting
     * [ ] 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.
     * [X] QT4CG-063-03: DN to address the editorial remarks from meeting
       063 in a new PR.
     * [ ] 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
     * [X] QT4CG-064-01: MK to remove "#..." and "#x..." arguments from
       fn:char
     * [ ] QT4CG-064-02: CG to update the fallback function to use the new
       char argument.
     * [ ] QT4CG-064-03: CG to add examples to show how JSON parsing
       changes are useful.
     * [ ] QT4CG-064-04: CG to change the return type of fallback to
       xs:untypedAtomic?
     * [ ] QT4CG-064-05: CG to amend the names in the keys-where example
       to be more inclusive
     * [ ] QT4CG-064-06: Add a keys-where example that uses the value in a
       more interesting way.
     * [ ] QT4CG-064-07: CG to add an array:index-of example that uses a
       collation
     * [ ] QT4CG-064-08: NW to open an issue to try to resolve $search to
       $target consistently.

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]#1010: 1009 Examples, Return type of parse-json:fallback

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 [11]#994: Invoking maps & arrays: allow sequences?
     * Issue [12]#989: character sequence constructor 'a' to 'z'
     * Issue [13]#79: fn:deep-normalize-space($e as node())
     * Issue [14]#55: Provide an XML version of the stack trace
     * Issue [15]#42: Relax type incompatibility in order by clause (impl.
       dep. instead of XPST0004)

1.6.4. XSLT focused

   The following PRs appear to be candidates for a future XSLT-focused
   meeting.
     * 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]#1015: 1013 [XSLT] Clarify effect of accumulator capture on
       non-element nodes
     * PR [20]#1008: 1002 Add fn:take-while function (replacing
       subsequence-before)
     * PR [21]#1003: 919 Use EBV in boolean callbacks
     * PR [22]#988: 960 Pinned and labeled values
     * PR [23]#985: 720 Add lookup arrow expressions (method invocations)
     * PR [24]#978: 948 Reflected the comments of the CG on the
       specification of scan-left and scan-right
     * PR [25]#972: 949 Partial Function Applications: Allow return of
       function name
     * PR [26]#953: 617 Define record constructors
     * PR [27]#916: 720 Allow methods in maps with access to $this
     * PR [28]#832: 77 Add map:deep-update and array:deep-update
     * PR [29]#795: 655 fn:sort-with

1.6.6. Proposed for V4.0

   The following issues are labled "proposed for V4.0".
     * Issue [30]#938: Canonical serialization
     * 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 still too vague
     * Issue [33]#882: fn:chain or fn:compose
     * Issue [34]#850: fn:parse-html: Finalization
     * Issue [35]#829: fn:boolean: EBV support for more item types
     * Issue [36]#716: Generators in XPath
     * Issue [37]#689: fn:stack-trace: keep, drop, replace with
       $err:stack-trace ?
     * Issue [38]#583: array:replace(), etc
     * Issue [39]#557: fn:unparsed-binary: accessing and manipulating
       binary types
     * Issue [40]#340: fn:format-number: Specifying decimal format
     * Issue [41]#283: Enumeration types
     * Issue [42]#236: map:build: sequence of keys
     * Issue [43]#33: JSON Parsing & Serialization: Numbers
     * Issue [44]#31: Extend FLWOR expressions to maps

2. Technical Agenda

   As agreed, we continue with the items left over from last week.

2.1. PR #795: 655 fn:sort-with

   See PR [45]#795

   T.B.D. Was there progress over the week or is more discussion required?

2.2. PR #972: 949 Partial Function Applications: Allow return of function
name

   See PR [46]#972

2.3. PR #988: 960 Pinned and labeled values

   See PR [47]#988

2.4. PR #985: 720 Add lookup arrow expressions (method invocations)

   See PR [48]#985

2.5. PR #978: 948 Reflected the comments of the CG on the specification of
scan-left and scan-right

   See PR [49]#978

2.6. PR #953: 617 Define record constructors

   See PR [50]#953

2.7. PR #916: 720 Allow methods in maps with access to $this

   See PR [51]#916

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

   See PR [52]#832

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-06.html
   8. https://qt4cg.org/dashboard/#pr-956
   9. https://qt4cg.org/dashboard/#pr-529
  10. https://qt4cg.org/dashboard/#pr-1010
  11. https://github.com/qt4cg/qtspecs/issues/994
  12. https://github.com/qt4cg/qtspecs/issues/989
  13. https://github.com/qt4cg/qtspecs/issues/79
  14. https://github.com/qt4cg/qtspecs/issues/55
  15. https://github.com/qt4cg/qtspecs/issues/42
  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-1015
  20. https://qt4cg.org/dashboard/#pr-1008
  21. https://qt4cg.org/dashboard/#pr-1003
  22. https://qt4cg.org/dashboard/#pr-988
  23. https://qt4cg.org/dashboard/#pr-985
  24. https://qt4cg.org/dashboard/#pr-978
  25. https://qt4cg.org/dashboard/#pr-972
  26. https://qt4cg.org/dashboard/#pr-953
  27. https://qt4cg.org/dashboard/#pr-916
  28. https://qt4cg.org/dashboard/#pr-832
  29. https://qt4cg.org/dashboard/#pr-795
  30. https://github.com/qt4cg/qtspecs/issues/938
  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/829
  36. https://github.com/qt4cg/qtspecs/issues/716
  37. https://github.com/qt4cg/qtspecs/issues/689
  38. https://github.com/qt4cg/qtspecs/issues/583
  39. https://github.com/qt4cg/qtspecs/issues/557
  40. https://github.com/qt4cg/qtspecs/issues/340
  41. https://github.com/qt4cg/qtspecs/issues/283
  42. https://github.com/qt4cg/qtspecs/issues/236
  43. https://github.com/qt4cg/qtspecs/issues/33
  44. https://github.com/qt4cg/qtspecs/issues/31
  45. https://qt4cg.org/dashboard/#pr-795
  46. https://qt4cg.org/dashboard/#pr-972
  47. https://qt4cg.org/dashboard/#pr-988
  48. https://qt4cg.org/dashboard/#pr-985
  49. https://qt4cg.org/dashboard/#pr-978
  50. https://qt4cg.org/dashboard/#pr-953
  51. https://qt4cg.org/dashboard/#pr-916
  52. https://qt4cg.org/dashboard/#pr-832

                                        Be seeing you,
                                          norm

--
Norm Tovey-Walsh
Saxonica