Re: QT4CG Agenda 050, 17 October 2023

I will be late to tomorrow's meeting (per usual), so wanted to remark that
at 1.6.2 in the agenda, #749 merits discussion, even if perfunctory,
because the change is IMO not trivial, and both on the website and in
github it is difficult to quickly identify the material differences.

Best wishes,

jk

On Mon, Oct 16, 2023 at 9:17 AM Norm Tovey-Walsh <norm@saxonica.com> wrote:

> Hello,
>
> Here’s a draft agenda for tomorrow’s meeting
>
>    https://qt4cg.org/meeting/agenda/2023/10-17.html
>
> QT4 CG Meeting 050 Agenda 2023-10-17
>
>    [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 17 October, the following meeting is
>    scheduled for 24 October.
>
>    Any regrets for the following meeting?
>
> 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-045-02: RD to address comments on HTML namespaces in
>        another PR
>      * [ ] QT4CG-046-01: MK to continue the work on #129 for the other
>        specs (we accepted #703)
>      * [ ] QT4CG-046-04: CG to flesh out changes related to annotations in
>        other parts of the specs
>      * [ ] QT4CG-046-05: NW to updated parse-uri to use decode-from-uri
>        (issue #566)
>      * [ ] QT4CG-048-01: MK - to identify what happens with the mode
>        default rule behaviours.
>      * [ ] QT4CG-048-02: MK to clean up the proposal for adding @as to
>        xsl:sequence and elsewhere
>      * [ ] QT4CG-049-01: MK to make sure CastTarget is defined locally
>      * [ ] QT4CG-049-02: NW to sort out what has made the dashboard so
>        unwieldy
>
> 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]#538: 480: Attempt to allow xs:string to be 'promoted to'
>        xs:anyURI
>
> 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.
>      * [9]#752 Fix "for member" grammar problems
>      * [10]#751 See ACTION QT4CG-048-01: xsl:mode/@as with built-in
>        templates
>      * [11]#744 XQFO Examples: minor fixes, formatting
>      * [12]#741 Fix copy and paste errors in describing type patterns
>      * [13]#740 Rename break-when to split-when, plus minor editorial
>        cleanup
>      * [14]#739 Apply review comment changes to the HTML DOM XDM mapping.
>
>    NW has reservations about E and L (and Q for that matter) but won't
>    object if he's alone.
>      * [15]#749 Add string literals E".." and L".." to control entity
>        expansion
>
> 1.6.3. Close without action
>
>    It has been proposed that the following issues be [16]closed without
>    action. If you think discussion is necessary, please say so.
>
>    None this week.
>
> 1.6.4. XSLT focused
>
>    The following PRs appear to be candidates for a future XSLT-focussed
>    meeting.
>      * [17]#470: 369 add fixed-prefixes attribute in XSLT
>      * [18]#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 [19]#742: xsl:function-library: keep, drop, or refine?
>      * Issue [20]#169: Handling of duplicate keys in xsl:map Enhancement
>      * Issue [21]#168: XSLT Extension Instructions invoking Named
>        Templates
>
> 1.6.5. Substantive PRs
>
>    The following substantive PRs were open when this agenda was prepared.
>      * PR [22]#737: 295 Boost the capability of recursive record types
>      * PR [23]#736: 730: Clarify (and correct) rules for maps as instances
>        of function types
>      * PR [24]#734: 517: fn:chain
>      * PR [25]#719: 413: Spec for CSV-related functions
>      * PR [26]#659: 647: schema location hints
>      * PR [27]#635: 451: Schema compatibility
>      * PR [28]#529: 528: revision of json(), and renaming to
>        elements-to-maps()
>
> 1.6.6. Proposed for V4.0
>
>    The following issues are labled "proposed for V4.0".
>      * Issue [29]#716: Generators in XPath
>      * Issue [30]#479: fn:deep-equal: Input order
>      * Issue [31]#340: fn:format-number: Specifying decimal format
>      * Issue [32]#260: array:index-of
>      * Issue [33]#238: Support Invisible XML
>      * Issue [34]#130: New super/union type xs:binary?
>
> 2. Technical Agenda
>
> 2.1. PR #719: 413: Spec for CSV-related functions
>
>    See [35]PR #719.
>
>    Status update with MP. Short discussion of recent comments about
>    functions.
>
> 2.2. PR #659: 647: schema location hints
>
>    See PR [36]#659.
>
> 2.3. PR #635: 451: Schema compatibility
>
>    See PR [37]#635.
>
> 2.4. PR #529: 528: revision of json(), and renaming to elements-to-maps()
>
>    See PR [38]#529.
>
> 2.5. PR #734: 517: fn:chain
>
>    See [39]#734.
>
> 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/10-10.html
>    8. https://qt4cg.org/dashboard/#pr-538
>    9. https://qt4cg.org/dashboard/#pr-752
>   10. https://qt4cg.org/dashboard/#pr-751
>   11. https://qt4cg.org/dashboard/#pr-744
>   12. https://qt4cg.org/dashboard/#pr-741
>   13. https://qt4cg.org/dashboard/#pr-740
>   14. https://qt4cg.org/dashboard/#pr-739
>   15. https://qt4cg.org/dashboard/#pr-749
>   16.
> https://github.com/qt4cg/qtspecs/labels/Propose%20Closing%20with%20No%20Action
>   17. https://qt4cg.org/dashboard/#pr-470
>   18. https://qt4cg.org/dashboard/#pr-412
>   19. https://github.com/qt4cg/qtspecs/issues/742
>   20. https://github.com/qt4cg/qtspecs/issues/169
>   21. https://github.com/qt4cg/qtspecs/issues/168
>   22. https://qt4cg.org/dashboard/#pr-737
>   23. https://qt4cg.org/dashboard/#pr-736
>   24. https://qt4cg.org/dashboard/#pr-734
>   25. https://qt4cg.org/dashboard/#pr-719
>   26. https://qt4cg.org/dashboard/#pr-659
>   27. https://qt4cg.org/dashboard/#pr-635
>   28. https://qt4cg.org/dashboard/#pr-529
>   29. https://github.com/qt4cg/qtspecs/issues/716
>   30. https://github.com/qt4cg/qtspecs/issues/479
>   31. https://github.com/qt4cg/qtspecs/issues/340
>   32. https://github.com/qt4cg/qtspecs/issues/260
>   33. https://github.com/qt4cg/qtspecs/issues/238
>   34. https://github.com/qt4cg/qtspecs/issues/130
>   35. https://qt4cg.org/dashboard/#pr-719
>   36. https://qt4cg.org/dashboard/#pr-659
>   37. https://qt4cg.org/dashboard/#pr-635
>   38. https://qt4cg.org/dashboard/#pr-529
>   39. https://qt4cg.org/dashboard/#pr-734
>
>                                         Be seeing you,
>                                           norm
>
> --
> Norm Tovey-Walsh
> Saxonica
>


-- 
Joel Kalvesmaki
kalvesmaki.com

Received on Tuesday, 17 October 2023 03:08:44 UTC