QT4 CG Meeting 105 Agenda 2025-01-14
Agenda index / QT4CG.org / Dashboard / GH Issues / GH Pull Requests
Agenda
This meeting will be hosted on Zoom at 16:00GMT (17:00CET, 11:00EST)
The Zoom meeting ID is 831 9996 6275; the passcode is 707664.
See the meeting logistics page for more 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 14 January 2025. The following meeting is scheduled for 21 January 2025.
1.5. Review of open action items [0/9]
(Items marked [X] are believed to have been closed via email before this agenda was posted.)
[ ]
QT4CG-080-07: NW to update the build instructions in the README[ ]
QT4CG-082-02: DN to work with MK to come to agreement on the fn:ranks proposal[ ]
QT4CG-088-01: NW to consider how best to add a dedication to MSM.[ ]
QT4CG-088-04: [Someone] needs to update the processing model diagram needs vis-a-vis the static typing feature[ ]
QT4CG-089-01: CG to draft a PR that attempts to resolve the operators described in #755 to a smaller number of orthogonal choices.[ ]
QT4CG-097-03: DN to proposal an axis for accessing the siblings of a node.[ ]
QT4CG-103-01: MK to add an example of showing all the properties for an untyped node.[ ]
QT4CG-104-01: MK to improve the wording aroundtrim-whitespace
wrt spaces outside the quoted string[ ]
QT4CG-103-02: MK to research alternative names fordivide-decimals
.
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.
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.
1.6.4. Substantive PRs
The following substantive PRs were open when this agenda was prepared.
- PR #1609: 1651 Ordered Maps
- PR #1677: 1675 Fixes for CSV parsing
- PR #1686: 1685 Pipeline Operator
- PR #1687: 1672 array:values, map:values: Alternatives
- PR #1689: 1684 Composite merge keys; current-merge-key-array function
- PR #1692: 1680 Fix switch syntax ambiguity
- PR #1694: 1632 Add xsl:map/@select
- PR #1696: 1136 Optional names in typed function types
1.6.5. Required for V4.0
The following issues are labeled “required for V4.0”.
- Issue #1252: Add a new function `fn:html-doc`
- Issue #1240: $sequence-of-maps ? info()
- Issue #1238: XSLT on-no-match="shallow-copy-all" - revised rules
- Issue #1127: Binary resources
- Issue #1045: Functions to manage namespace usage
- Issue #1021: Extend `fn:doc`, `fn:collection` and `fn:uri-collection` with options maps
- Issue #1011: fn:transform() improvements
- Issue #986: Numeric Comparisons
- Issue #967: XPath Appendix I: Comparisons
- Issue #826: Arrays: Representation of single members of an array
- Issue #748: Parse functions: consistency
- Issue #675: XSLT streaming rules for new constructs
- Issue #501: Error handling: Rethrow errors; finally block
- Issue #490: Control over schema validation in parse-xml(), doc(), etc.
- Issue #407: XSLT-specific context properties used in function items
- Issue #272: Setting parameter values in xsl:use-package
2. Technical agenda
2.1. PR #1686: 1685 Pipeline Operator
See PR #1686
2.2. PR #1677: 1675 Fixes for CSV parsing
See PR #1677
2.3. PR #1687: 1672 array:values, map:values: Alternatives
See PR #1687
2.4. PR #1692: 1680 Fix switch syntax ambiguity
See PR #1692
2.5. PR #1696: 1136 Optional names in typed function types
See PR #1696
2.6. PR #1609: 1651 Ordered Maps
See PR #1609
2.7. PR #1689: 1684 Composite merge keys; current-merge-key-array function
See PR #1689
2.8. PR #1694: 1632 Add xsl:map/@select
See PR #1694