QT4 CG Meeting 006 Agenda 2022-10-11
Agenda
This meeting will be hosted on Zoom at 16:00BST (15:00GMT, 17:00CEST, 11:00EDT).
See the meeting logistics page for details.
- Ammended with proposals from MK on 7 October 2022.
1. Administrivia
1.1. Roll call
1.2. Approve minutes of previous meeting
Minutes of the previous meeting.
1.3. Review of open action items [5/7]
(Items marked [X] are believed to have been closed via email before this agenda was posted.)
[X]QT4CG-002-01: NW to incorporate email feedback and produce new versions of the process documents.[X]QT4CG-003-03: NW to tweak the CSS for function signatures to avoid line breaks on-characters.[ ]QT4CG-002-10: BTW to coordinate some ideas about improving diversity in the group[X]QT4CG-005-01: NW to update the W3C CG page to reflect the current chairs[X]QT4CG-005-02: NW to investigate how the function dropdown works and if it’s buggy[ ]QT4CG-005-03: RD to review the variadic functions proposal in #166[X]QT4CG-005-04: MK to draft a concrete proposal for the range-related functions- See pull request #177, also below.
1.4. Scheduling XSLT work
- MK writes:
I'd also like to talk about how we tackle XSLT issues - would anyone prefer if some meetings were dedicated to that spec?
2. Technical Agenda
2.1. Review pull request #197 (was 166; variadic functions)
- See pull request #197 (you’ll find links to formatted versions of the specs at https://qt4cg.org/).
- See also the nexus of issues #162, #161, #160, #159, #158, #157, and #155.
2.2. Review pull request #198 (was 173; fn:op)
2.3. Review pull request #199 (was 177; items before, etc.)
2.4. Review pull request #200 (was 185; drop xsl:match instruction)
2.5. Review pull request #201 (was 188; editorial)
2.6. Review pull request #202 (was 196; subtyping)
2.7. fn:while (previously fn:until)
2.8. HOF sequence functions and positional arguments
- See #181
CG says “I haven’t drafted a full proposal yet, as I’d first like to hear what everyone thinks about it.”
2.9. Issue #170, XPath “otherwise” operator
MK proposes that this issue may be ready to be decided.
2.10. Issue #165, keyword arguments, “:=” or “:”
MK proposes that this issue may be ready to be decided.
2.11. Issue #151, map:build() functions
MK proposes that this issue may be ready to be decided.
2.12. Issue #114, array:index-where
MK proposes that this issue may be ready to be decided
2.13. Issue #107, allow self::(a|b|c)
MK proposes that this issue may be ready to be decided.
2.14. Issue #96, starting/ending sequence functions
MK proposes that this issue may be ready to be decided.
2.15. XPath 4.0 functions
2.15.1. fn:duplicate-values
- See #123
- See also discussion from last meeting
2.15.2. fn:replace (action)
2.15.3. fn:format-number (minor fixes)
2.15.4. fn:json
2.15.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.15.6. fn:stack-trace
2.15.7. map:group-by
2.15.8. map:replace
2.15.9. map:substitute
2.15.11. array:replace
2.15.12. array:slice
2.15.13. array:partition
2.15.14. fn:parts
- See ???
2.15.15. fn:op
- See #83
2.15.16. fn:init, fn:foot, etc
- See #97
2.15.18. fn:convert-to/from-EQName
- See #1
2.15.19. fn:parse-html
- See #74
2.15.20. fn:split-by-graphemes
- See #73
2.15.21. fn:until
- See #80
2.15.22. fn:nl, fn:cr, fn:tab
- See #121
2.15.23. fn:deep-normalize-space
- See #79
2.15.24. fn:parcel, fn:unparcel, array:from-members/of, array:members/parcels
- See #113
2.15.25. array:values, map:values
- See #29