QT4 CG Meeting 075 Agenda 2024-04-30
Agenda index / QT4CG.org / Dashboard / GH Issues / GH Pull Requests
Agenda
This meeting will be hosted on Zoom at 16:00BST (15:00GMT, 17:00CEST, 11:00EDT)
See the 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 the previous meeting.
1.4. Next meeting
This meeting is planned for 30 April. The following meeting is scheduled for 7 May.
NW gives (very likely) regrets for 7 May, MSM to chair.
1.5. Review of open action items [1/7]
(Items marked [X] are believed to have been closed via email before this agenda was posted.)
[ ]
QT4CG-063-06: MK to consider refactoring the declare item type syntax to something like declare record[ ]
QT4CG-071-06: NW to clarify the cases that are distinguished by the leading empty string in path segments[ ]
QT4CG-072-03: NW to clarify the round-tripping of URIs[ ]
QT4CG-073-01: NW to proceed with the records/options proposal and make a PR.[ ]
QT4CG-074-01: MK to remove default values from variadic arguments[X]
QT4CG-074-02: DN to create an issue about allowing function arguments to have default values[ ]
QT4CG-074-03: MK to add variadic functions to the XSLT specification
1.6. Review of open pull requests and issues
1.6.1. Blocked
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.
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 #553: New function fn:substitute()
1.6.4. XSLT focused
The following PRs appear to be candidates for a future XSLT-focused meeting.
- PR #1015: 1013 [XSLT] Clarify effect of accumulator capture on non-element nodes
- PR #921: 920 Allow xsl:break and xsl:next-iteration within branch of xsl:switch
- PR #871: Action qt4 cg 027 01 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 #168: XSLT Extension Instructions invoking Named Templates
1.6.5. Substantive PRs
The following substantive PRs were open when this agenda was prepared.
- PR #1177: 1162 Positional variables are xs:integer not xs:positiveInteger
- PR #1174: 1173 array:build, map:build: Positional access
- PR #1168: 1166 Clarify rule on invalid option keys
- PR #1148: 1143 Coercion rules: handle choice types before atomization
- PR #1117: 1116 Add options param to unparsed-text
- PR #1108: 566-partial Describe a less aggressive %-encoding for fn:build-uri
- PR #1098: 566-partial Editorial improvements for parse-uri
- PR #1087: 1086 Editorial changes to array:values
- PR #1068: 73 fn:graphemes
- PR #1062: 150bis - revised proposal for fn:ranks
- PR #1027: 150 fn:ranks
1.6.6. Proposed for V4.0
The following issues are labled “proposed for V4.0”.
- Issue #1069: fn:ucd
- Issue #982: Add position argument to scan-left and scan-right
- Issue #938: Canonical serialization
- Issue #934: String comparison in deep-equal
- Issue #910: Introduce a Kollection object with functions that operate on all types of items that can be containers of unlimited number of "members"
- Issue #908: Function identity: documentation, nondeterminism
- Issue #882: fn:chain or fn:compose
- Issue #850: fn:parse-html: Finalization
- Issue #716: Generators in XPath
- Issue #689: fn:stack-trace: keep, drop, replace with $err:stack-trace ?
- Issue #657: User-defined functions in main modules without `local` prefix
- Issue #557: fn:unparsed-binary: accessing and manipulating binary types
- Issue #150: fn:ranks: Produce all ranks in applying a function on the items of a sequence
- Issue #31: Extend FLWOR expressions to maps
2. Technical Agenda
2.1. PR #1177: 1162 Positional variables are xs:integer not xs:positiveInteger
See PR #1177
2.2. PR #1174: 1173 array:build, map:build: Positional access
See PR #1174
2.3. PR #1168: 1166 Clarify rule on invalid option keys
See PR #1168
2.4. PR #1148: 1143 Coercion rules: handle choice types before atomization
See PR #1148
2.5. PR #1117: 1116 Add options param to unparsed-text
See PR #1117
2.6. PR #1087: 1086 Editorial changes to array:values
See PR #1087
2.7. PR #1068: 73 fn:graphemes
See PR #1068