- From: Michael Kay <mike@saxonica.com>
- Date: Tue, 24 Oct 2023 08:03:22 +0100
- To: Norm Tovey-Walsh <norm@saxonica.com>
- Cc: public-xslt-40@w3.org
You have put PR #529: 528: revision of json(), and renaming to elements-to-maps() but I think there have been comments that I would like to respond to before bringing it back to the meeting. I think the following PRs all have a reasonable chance of going through quickly • PR #761: 554/754 Simplify the new transitive-closure function • PR #753: 65: Allow xmlns="xxx" to NOT change the default namespace for NameTests • PR #737: 295: Boost the capability of recursive record types • PR #736: 730: Clarify (and correct) rules for maps as instances of function types though one thing I have learnt is that you never can tell! It always helps, of course, if people read the PR and raise any comments (or simply indicate approval) in advance. Michael Kay > On 23 Oct 2023, at 11:25, Norm Tovey-Walsh <norm@saxonica.com> wrote: > > Hello, > > Here’s the agenda for tomorrow’s CG meeting. It’s mostly a continuation > of last week’s agenda. > > https://qt4cg.org/meeting/agenda/2023/10-24.html > > QT4 CG Meeting 051 Agenda 2023-10-24 > > [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. > > ATTENTION: Europe and the United Kingdom switch from daylight saving > time to standard time on Sunday, October 29, 2023. The meeting on > Tuesday, 31 October 2023, will occur one hour earlier in The United > States. > > 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 24 October, the following meeting is > scheduled for 31 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-046-01: MK to continue the work on #129 for the other > specs (we accepted #703) > * [X] 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-02: MK to clean up the proposal for adding @as to > xsl:sequence and elsewhere > * [ ] QT4CG-050-02: MP to attempt to summarize this discussion and > identify specific issues > * [ ] QT4CG-050-01: MK to revise #749 to retain only the editorial > parts. > * [ ] QT4CG-050-03: MK to make the proposed editorial improvements to > PR #659 > > 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. > * PR [9]#766: 765 Update version references etc to 4.0 status > * PR [10]#763: 686: XQFO diagnostic function documentation > * PR [11]#762: 758: XQFO minor edits 3 > * PR [12]#749: 653: Add string literals E".." and L".." to control > entity expansion > * PR [13]#659: 647: schema location hints > > 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 [14]#383: fn:deep-equal: Order of child elements > (unordered-elements) > > 1.6.4. XSLT focused > > The following PRs appear to be candidates for a future XSLT-focussed > meeting. > * PR [15]#470: 369: add fixed-prefixes attribute in XSLT > * PR [16]#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 [17]#742: xsl:function-library: keep, drop, or refine? > * Issue [18]#169: Handling of duplicate keys in xsl:map > * Issue [19]#168: XSLT Extension Instructions invoking Named > Templates > > 1.6.5. Substantive PRs > > The following substantive PRs were open when this agenda was prepared. > * PR [20]#761: 554/754 Simplify the new transitive-closure function > * PR [21]#753: 65: Allow xmlns="xxx" to NOT change the default > namespace for NameTests > * 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]#635: 451: Schema compatibility > * PR [27]#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 [28]#716: Generators in XPath > * Issue [29]#479: fn:deep-equal: Input order > * Issue [30]#340: fn:format-number: Specifying decimal format > * Issue [31]#260: array:index-of > * Issue [32]#238: Support Invisible XML > * Issue [33]#130: New super/union type xs:binary? > * Issue [34]#129: Context item -> Context value? > * Issue [35]#31: Extend FLWOR expressions to maps > > 2. Technical Agenda > > 2.1. Issue 129: Context item -> Context value? > > See issue [36]#129: does this need to remain open? Can we create > actions for the unresolved edits instead? > > 2.2. Issue 238: Support Invisible XML > > See issue [37]#238: time boxed discussion to see if the group wants to > do this. > > 2.3. PR #635: 451: Schema compatibility > > See PR [38]#635. > > 2.4. PR #529: 528: revision of json(), and renaming to elements-to-maps() > > See PR [39]#529. > > 2.5. PR #734: 517: fn:chain > > See [40]#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-17.html > 8. https://qt4cg.org/dashboard/#pr-538 > 9. https://qt4cg.org/dashboard/#pr-766 > 10. https://qt4cg.org/dashboard/#pr-763 > 11. https://qt4cg.org/dashboard/#pr-762 > 12. https://qt4cg.org/dashboard/#pr-749 > 13. https://qt4cg.org/dashboard/#pr-659 > 14. https://github.com/qt4cg/qtspecs/issues/383 > 15. https://qt4cg.org/dashboard/#pr-470 > 16. https://qt4cg.org/dashboard/#pr-412 > 17. https://github.com/qt4cg/qtspecs/issues/742 > 18. https://github.com/qt4cg/qtspecs/issues/169 > 19. https://github.com/qt4cg/qtspecs/issues/168 > 20. https://qt4cg.org/dashboard/#pr-761 > 21. https://qt4cg.org/dashboard/#pr-753 > 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-635 > 27. https://qt4cg.org/dashboard/#pr-529 > 28. https://github.com/qt4cg/qtspecs/issues/716 > 29. https://github.com/qt4cg/qtspecs/issues/479 > 30. https://github.com/qt4cg/qtspecs/issues/340 > 31. https://github.com/qt4cg/qtspecs/issues/260 > 32. https://github.com/qt4cg/qtspecs/issues/238 > 33. https://github.com/qt4cg/qtspecs/issues/130 > 34. https://github.com/qt4cg/qtspecs/issues/129 > 35. https://github.com/qt4cg/qtspecs/issues/31 > 36. https://github.com/qt4cg/qtspecs/issues/129 > 37. https://github.com/qt4cg/qtspecs/issues/238 > 38. https://qt4cg.org/dashboard/#pr-635 > 39. https://qt4cg.org/dashboard/#pr-529 > 40. https://qt4cg.org/dashboard/#pr-734 > > Be seeing you, > norm > > -- > Norm Tovey-Walsh > Saxonica
Received on Tuesday, 24 October 2023 07:03:43 UTC