QT4 CG Meeting 014 Agenda 2022-12-06
Agenda
This meeting will be hosted on Zoom at 16:00GMT (17:00CET, 11:00EST).
See the meeting logistics page for details.
1. Administrivia
1.1. Roll call
1.2. Approve the agenda
1.3. Next meeting
Regrets for the next meeting?
1.4. Approve minutes of previous meeting
Minutes of the previous meeting.
1.5. Review of open action items [8/9]
(Items marked [X] are believed to have been closed via email before this agenda was posted.)
[ ]QT4CG-002-10: BTW to coordinate some ideas about improving diversity in the group[ ]QT4CG-013-01: MK to refine the coercion rules with respect to enumeration types[ ]QT4CG-013-02: DN to provide a concrete example of the function case discussed with respect to coercion rules.[X]QT4CG-013-03: MK to raise a separate issue about sequence/array out-of-bounds handling
1.6. Schedule for upcoming meetings
The next few meetings scheduled after this one are:
[ ]13 December 2022[ ]20 December 2022[ ]27 December 2022[ ]3 January 2023
Do we plan to skip any of those meetings for the end-of-year holidays?
2. Technical Agenda
2.1. Issue 278, array bounds checking
Placed before PR #250 because I think it’s relevant to closing that issue.
2.2. Review pull request #250: fn:foot, etc.
See pull request #250 and the minutes of meeting 013.
2.3. Issue 274, building a module repository for QT
There’s been some discussion of this issue in the comments. I think it might benefit from some face-to-face discussion. I propose to time-box this discussion to say 20 or 30 minutes.
2.4. Review pull request #258: add array:index-where (issue #114)
2.5. Review pull request #259: parse-html (issue #74)
2.6. Review pull request #261: fn:char (issue #121)
2.7. Review pull request #268: type diagrams (issue #265)
2.8. Review pull request #271: data model changes
2.9. Review pull request #279: Rewrite XSLT §10.3.4 (function overriding) for clarity
2.10. Issue #170, XPath “otherwise” operator
MK proposes that this issue may be ready to be decided.
2.11. Issue #114, array:index-where
MK proposes that this issue may be ready to be decided
2.12. Issue #107, allow self::(a|b|c)
MK proposes that this issue may be ready to be decided.
2.13. XPath 4.0 functions
2.13.1. fn:duplicate-values
- See #123
- See also discussion from last meeting
2.13.2. fn:replace (action)
2.13.3. fn:format-number (minor fixes)
2.13.4. fn:json
2.13.5. fn:differences
Editorially, this function is not ready for approval. We should decide if we want to pursue it, and if we do, how.
2.13.6. fn:stack-trace
2.13.7. map:group-by
2.13.8. map:replace
2.13.9. map:substitute
2.13.11. array:replace
2.13.12. array:slice
2.13.13. array:partition
2.13.14. fn:parts
- See ???
2.13.15. fn:convert-to/from-EQName
- See #1
2.13.16. fn:parse-html
- See #74
2.13.17. fn:split-by-graphemes
- See #73
2.13.18. fn:until
- See #80
2.13.19. fn:nl, fn:cr, fn:tab
- See #121
2.13.20. fn:deep-normalize-space
- See #79
2.13.21. fn:parcel, fn:unparcel, array:from-members/of, array:members/parcels
- See #113
2.13.22. array:values, map:values
- See #29