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

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

Apologies for the delay in publishing these minutes. Entirely my fault, MSM sent them to me shortly after the meeting. (Thank you, Michael, for chairing and scribing.)

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

QT4 CG Meeting 076 Minutes 2024-05-07

Table of Contents

     * [1]1. Administrivia
          + [2]1.1. Roll call
          + [3]1.2. Approve the agenda
          + [4]1.3. Approve minutes of previous meeting
          + [5]1.4. Next meeting
          + [6]1.5. Review of open action items [1/7]
          + [7]1.6. Review of open pull requests and issues
               o [8]1.6.1. XSLT focused
               o [9]1.6.2. Substantive PRs
     * [10]2. Technical Agenda
          + [11]2.1. PR #1186: 1170 Editorial: fn:index-where
          + [12]2.2. PR #1185: 1179 array:values, map:values -> contents
          + [13]2.3. PR #1184: 1165-Use Unicode-style character references
          + [14]2.4. PR #1182: 1171 Change predicate
          + [15]2.5. PR #1148: 1143 Coercion rules:
     * [16]3. Any other business

1. Administrivia

1.1. Roll call

   Regrets from NW, JLY. MSM to chair. [7/12]
     * [ ] Reece Dunn (RD). Regrets.
     * [ ] Sasha Firsov (SF)
     * [X] Christian Gr¸n (CG)
     * [X] Joel Kalvesmaki (JK)
     * [X] Michael Kay (MK)
     * [ ] Juri Leino (JLO)
     * [ ] John Lumley (JLY). Regrets.
     * [X] Dimitre Novatchev (DN)
     * [X] Wendell Piez (WP)
     * [X] Ed Porter (EP)
     * [X] C. M. Sperberg-McQueen (MSM). Scribe. Chair.
     * [ ] Norm Tovey-Walsh (NW). Regrets.

1.2. Approve the agenda

   Proposal: Accept [17]the agenda as posted.

   MK says that PR #1181 belongs in the general list, not XSLT-focused, as
   it affects all specs.

   CG: can we prioritize 1068?

   Accepted as modified.

1.3. Approve minutes of previous meeting

   MSM urged the group to look carefully at the status visualizations at
   the beginning of each week's minutes. The number of open bugs is
   improving, but (a) the overall trend line is still ascending and (b)
   the number of issues is still well into triple digits.

   Proposal: Accept [18]minutes of the previous meeting.

   Accepted.

1.4. Next meeting

   The next meeting is scheduled for [19]14 May. The following meeting is
   scheduled for 21 May.

   MSM noted that he and NW have a conflicting meeting, but having just
   harangued the group on the subject of improving the burn-down rate, he
   felt incapable of proposing that we skip the meeting. So: we will meet
   on 14 May, and NW and MSM will have to sneak out of their other
   meeting.

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
     * [X] QT4CG-075-03: CG to make changes to map:values analagous to
       MK's changes to array:values

   MK reports he's done half of 075-01.

   CG has made a PR satisfying 075-03.

1.6. Review of open pull requests and issues

1.6.1. XSLT focused

   The following PRs appear to be candidates for a future XSLT-focused
   meeting.
     * PR [20]#1015: 1013 [XSLT] Clarify

   effect of accumulator capture on non-element nodes
     * PR [21]#921: 920 Allow xsl:break and

   xsl:next-iteration within branch of xsl:switch
     * PR [22]#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 [23]#168: XSLT Extension

   Instructions invoking Named Templates

   We removed PR [24]#1181 from this list and moved it to the next
   section.

1.6.2. Substantive PRs

   The following substantive PRs were open when this agenda was prepared.
     * PR [25]#1186: 1170 Editorial: fn:index-where
     * PR [26]#1185: 1179 array:values, map:values -> contents
     * PR [27]#1184: 1165-Use Unicode-style character references
     * PR [28]#1182: 1171 Change predicate

   callbacks to allow empty return value
     * PR [29]#1148: 1143 Coercion rules:

   handle choice types before atomization
     * PR [30]#1117: 1116 Add options param to unparsed-text
     * PR [31]#1108: 566-partial Describe a

   less aggressive %-encoding for fn:build-uri
     * PR [32]#1098: 566-partial Editorial improvements for parse-uri
     * PR [33]#1068: 73 fn:graphemes
     * PR [34]#1062: 150bis - revised proposal for fn:ranks
     * PR [35]#1027: 150 fn:ranks

   We added:
     * PR [36]#1181: 296 Allow default-namespace=##any

2. Technical Agenda

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

   See PR [38]#1186.

   Accept and close.

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

   See PR [40]#1185.

   MK: the problem is that 'contains' looks at keys, and 'contents' looks
   at key-values.

   MSM: 'value' is overloaded; that's part of theproblem, right?

   CG maybe item?

   DN: sequence concatenation in undefined order? Yow!

   These functions lose the structure! This isn't a great way to get at
   the parts of an array or map.

   MK: Yes. But so many arrays have singleton values that the requirement
   to move from array to sequence is a very common one.

   JK: what's the intended difference between array:content() and
   array:flatten()? CG: contents() is much simpler.

   CG: the motivation for these is to allow functional equivalents for a
   widely used wildcard syntax.

   Various people: would 'flatten' be a better name?

   CN: or flattened-value()?

   CN: loss of information is the issue. array:squashed(),
   maps:squashed().

   Further consideration needed. Take it offline.

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

   See PR [42]#1184.

   MK: purely editorial.

   Accepted.

2.4. PR [43]#1182: 1171 Change predicate

   callbacks to allow empty return value

   See PR [44]#1182.

   Accepted.

2.5. PR [45]#1148: 1143 Coercion rules:

   handle choice types before atomization

   See PR [46]#1148

   DN asks for more examples. Text nodes?

   ACTION: MK to draft an editorial proposal to add more examples.

3. Any other business

   None.

References

   1. https://qt4cg.org/meeting/minutes/2024/05-07.html#h-5FD58640-0C4C-47AD-9DD2-CE42E3859295
   2. https://qt4cg.org/meeting/minutes/2024/05-07.html#h-F610AA71-DC40-4E3E-A05D-568CABACE015
   3. https://qt4cg.org/meeting/minutes/2024/05-07.html#h-B1C3720D-A852-416F-8CA8-F796F8B4928E
   4. https://qt4cg.org/meeting/minutes/2024/05-07.html#h-AD4E2248-E237-42B4-987B-745B7073F0BD
   5. https://qt4cg.org/meeting/minutes/2024/05-07.html#h-6E415DD8-5C33-4E06-A5CA-DB9AC4955455
   6. https://qt4cg.org/meeting/minutes/2024/05-07.html#h-1C7F6C83-ADC6-4CE8-9C43-C68FC17DFCF3
   7. https://qt4cg.org/meeting/minutes/2024/05-07.html#h-B9D86C17-B569-479B-9148-AA10721BBA6C
   8. https://qt4cg.org/meeting/minutes/2024/05-07.html#h-2E27F717-E026-4E76-8867-3D13A65059E3
   9. https://qt4cg.org/meeting/minutes/2024/05-07.html#h-777CB2A2-C144-480C-859C-1A2E43163364
  10. https://qt4cg.org/meeting/minutes/2024/05-07.html#h-92D0ACD0-9BC3-4389-9479-CBEBFC2419E2
  11. https://qt4cg.org/meeting/minutes/2024/05-07.html#h-C7830527-6C52-4E7B-AFCF-A826F4B1F550
  12. https://qt4cg.org/meeting/minutes/2024/05-07.html#h-0B28CDC3-EB80-49BD-8171-A9E7BC2E019F
  13. https://qt4cg.org/meeting/minutes/2024/05-07.html#h-D8882D53-D962-4A76-8AF6-68CCA1B84C9A
  14. https://qt4cg.org/meeting/minutes/2024/05-07.html#h-55CEF04C-9E1E-48A3-A445-20A06CD23939
  15. https://qt4cg.org/meeting/minutes/2024/05-07.html#h-706A7B88-ABA8-4A39-A41C-D3FAF396F7E0
  16. https://qt4cg.org/meeting/minutes/2024/05-07.html#h-BE122C76-CD86-48A2-9360-6E61E3C3BC85
  17. https://qt4cg.org/meeting/agenda/2024/05-07.html
  18. https://qt4cg.org/meeting/minutes/2024/04-30.html
  19. https://qt4cg.org/meeting/agenda/2024/05-14.html
  20. https://qt4cg.org/dashboard/#pr-1015
  21. https://qt4cg.org/dashboard/#pr-921
  22. https://qt4cg.org/dashboard/#pr-871
  23. https://github.com/qt4cg/qtspecs/issues/168
  24. https://qt4cg.org/dashboard/#pr-1181
  25. https://qt4cg.org/dashboard/#pr-1186
  26. https://qt4cg.org/dashboard/#pr-1185
  27. https://qt4cg.org/dashboard/#pr-1184
  28. https://qt4cg.org/dashboard/#pr-1182
  29. https://qt4cg.org/dashboard/#pr-1148
  30. https://qt4cg.org/dashboard/#pr-1117
  31. https://qt4cg.org/dashboard/#pr-1108
  32. https://qt4cg.org/dashboard/#pr-1098
  33. https://qt4cg.org/dashboard/#pr-1068
  34. https://qt4cg.org/dashboard/#pr-1062
  35. https://qt4cg.org/dashboard/#pr-1027
  36. https://qt4cg.org/dashboard/#pr-1181
  37. https://qt4cg.org/dashboard/#pr-1186
  38. https://qt4cg.org/dashboard/#pr-1186
  39. https://qt4cg.org/dashboard/#pr-1185
  40. https://qt4cg.org/dashboard/#pr-1185
  41. https://qt4cg.org/dashboard/#pr-1184
  42. https://qt4cg.org/dashboard/#pr-1184
  43. https://qt4cg.org/dashboard/#pr-1182
  44. https://qt4cg.org/dashboard/#pr-1182
  45. https://qt4cg.org/dashboard/#pr-1148
  46. https://qt4cg.org/dashboard/#pr-1148


                                        Be seeing you,
                                          norm

--
Norm Tovey-Walsh
Saxonica
Received on Monday, 13 May 2024 12:12:45 UTC