- From: Dimitre Novatchev <dnovatchev@gmail.com>
- Date: Mon, 30 Oct 2023 07:05:00 -0700
- To: Norm Tovey-Walsh <norm@saxonica.com>
- Cc: public-xslt-40@w3.org
- Message-ID: <CAK4KnZezWKx=YjjJZmYU2hy_2rUDVu4Pvm2UPMj_vNMcWBb-7Q@mail.gmail.com>
Action items: QT4CG-051-04, QT4CG-051-05, QT4CG-051-06 are done and the latest PR: https://github.com/qt4cg/qtspecs/pull/775 is ready to merge with the requested changes. Thanks, Dimitre On Mon, Oct 30, 2023 at 2:19 AM Norm Tovey-Walsh <norm@saxonica.com> wrote: > Hello, > > Here’s the agenda for tomorrow’s meeting. This is meeting 52, so marks > our one year anniversary. (One year of meetings spread over a little > more than one calendar year.) > > https://qt4cg.org/meeting/agenda/2023/10-31.html > > QT4 CG Meeting 052 Agenda 2023-10-31 > > [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 switched from daylight saving > time to standard time on Sunday, October 29, 2023. The meeting on > Tuesday, 31 October 2023, will occur one hour later 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 31 October, the following meeting is > scheduled for 7 November. > > DN gives possible regrets for this meeting. > > Any regrets for the following meeting? > > 1.5. Review of open action items [2/7] > > (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) > * [ ] QT4CG-050-02: MP to attempt to summarize this discussion and > identify specific issues > * [ ] QT4CG-051-01: NW to attempt to craft a new issue for the > remaining items in #129 > * [ ] QT4CG-051-02: NW to attempt to draft a proposal for > fn:invisible-xml > * [ ] QT4CG-051-03: MK to check that in our view schema components > don't indirectly reference the schema root > * [ ] QT4CG-051-04: DN to make the point that in simple, static > cases, the arrow operators may be better. > * [ ] QT4CG-051-05: DN to correct the typo in item 3 "could be > sequence" => "could > * [ ] QT4CG-051-06: MK to help DN with the markup in fn:chain > examples. > > 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 > * PR [9]#761: 554/754 Simplify the new transitive-closure function > * PR [10]#737: 295: Boost the capability of recursive record types > * PR [11]#736: 730: Clarify (and correct) rules for maps as instances > of function types > > 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 [12]#787: 783(part) - Editorial changes to Serialization spec > * PR [13]#786: 695: Added xref to fn:slice() > * PR [14]#785: 777: updated history > * PR [15]#784: fos xsd > * PR [16]#782: 469: array:of-members, map:of-pairs: Signatures, > Examples > * PR [17]#778: XQFO edits 5.4-5.6 > > 1.6.3. XSLT focused > > The following PRs appear to be candidates for a future XSLT-focussed > meeting. > * PR [18]#470: 369: add fixed-prefixes attribute in XSLT > * PR [19]#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 [20]#742: xsl:function-library: keep, drop, or refine? > * Issue [21]#169: Handling of duplicate keys in xsl:map > * Issue [22]#168: XSLT Extension Instructions invoking Named > Templates > > 1.6.4. Substantive PRs > > The following substantive PRs were open when this agenda was prepared. > * PR [23]#775: 517: Reflected Christian Gruen's remarks > * PR [24]#772: Revise the fn:parse-html rules to make them clearer to > follow. > * PR [25]#770: 566: Use fn:decode-from-uri in fn:parse-uri > * PR [26]#753: 65: Allow xmlns="xxx" to NOT change the default > namespace for NameTests > * PR [27]#719: 413: Spec for CSV-related functions > * PR [28]#529: 528: revision of json(), and renaming to > elements-to-maps() > > 1.6.5. 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]#31: Extend FLWOR expressions to maps > > 2. Technical Agenda > > 2.1. Issue #689: fn:stack-trace: keep or drop? > > See issue [35]#689. > > 2.2. Issue #130: New super/union type xs:binary? > > See issue [36]#130. > > 2.3. PR #772: Revise the fn:parse-html rules to make them clearer to > follow. > > See PR [37]#772 > > 2.4. PR #770: 566: Use fn:decode-from-uri in fn:parse-uri > > See PR [38]#770 > > 2.5. PR #753: 65: Allow xmlns="xxx" to NOT change the default namespace for > NameTests > > See PR [39]#753 > > 3. Any other business > > Plan to discuss parse-csv again next week? > > 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-24.html > 8. https://qt4cg.org/dashboard/#pr-538 > 9. https://qt4cg.org/dashboard/#pr-761 > 10. https://qt4cg.org/dashboard/#pr-737 > 11. https://qt4cg.org/dashboard/#pr-736 > 12. https://qt4cg.org/dashboard/#pr-787 > 13. https://qt4cg.org/dashboard/#pr-786 > 14. https://qt4cg.org/dashboard/#pr-785 > 15. https://qt4cg.org/dashboard/#pr-784 > 16. https://qt4cg.org/dashboard/#pr-782 > 17. https://qt4cg.org/dashboard/#pr-778 > 18. https://qt4cg.org/dashboard/#pr-470 > 19. https://qt4cg.org/dashboard/#pr-412 > 20. https://github.com/qt4cg/qtspecs/issues/742 > 21. https://github.com/qt4cg/qtspecs/issues/169 > 22. https://github.com/qt4cg/qtspecs/issues/168 > 23. https://qt4cg.org/dashboard/#pr-775 > 24. https://qt4cg.org/dashboard/#pr-772 > 25. https://qt4cg.org/dashboard/#pr-770 > 26. https://qt4cg.org/dashboard/#pr-753 > 27. https://qt4cg.org/dashboard/#pr-719 > 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/31 > 35. https://github.com/qt4cg/qtspecs/issues/689 > 36. https://github.com/qt4cg/qtspecs/issues/130 > 37. https://qt4cg.org/dashboard/#pr-772 > 38. https://qt4cg.org/dashboard/#pr-770 > 39. https://qt4cg.org/dashboard/#pr-753 > > Be seeing you, > norm > > -- > Norm Tovey-Walsh > Saxonica >
Received on Monday, 30 October 2023 14:05:19 UTC