QT4 CG Meeting 154 Agenda 2026-03-03
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).
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 3 March 2026.
The next meeting is planned for 10 March 2026.
1.5. Review of open action items [1/10]
[ ]QT4CG-143-02: MK to try to recover the ability to extract formal equivalences into tests[ ]QT4CG-143-03: JK to look for C14N test suites.[ ]QT4CG-144-01: MK to consider if any now lost value comparisons should be added as examples.[ ]QT4CG-149-01: CG to draft a new PR with the common rule note.[ ]QT4CG-150-01: NW to ask Jirka for a room at XML Prague for Tuesday/Wednesday[ ]QT4CG-150-04: NW to see about a status update on PR #2345; possibly schedule discussion[ ]QT4CG-151-01: MK to fix the typo in the build-dateTime function.[ ]QT4CG-151-03: NW to investigate why records are formatted incorrectly in XSLT[ ]QT4CG-152-01: MK to add a note about the new and old syntax for names in PR #2446[ ]QT4CG-153-01: MK to investigate the indentation problem.[ ]QT4CG-153-02: MK to turn my suggestions on #1949 into a PR.
1.6. Review of open pull requests and issues
This section summarizes all of the issues and pull requests that need to be resolved before we can finish. See Technical Agenda below for the focus of this meeting.
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.
- PR #2493: 2408 Misc editorial corrections
- PR #2485: 2388 Adaptive serialization of anonymous functions
- PR #2480: 2465 Improve description of FODC0006
- PR #2479: 2472 drop the term "potential visibility"
- PR #2469: 2466 Adapt rules of format-number to new comparison rules
- PR #2468: 2448 Change title of XPath 4.0 specification
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 #2018: Type-checking the result of xsl:apply-templates
- Issue #1702: Node Updates: Functions
- Issue #1506: Type declarations: Constructor functions?
- Issue #1251: Allow sequence constructor in extension instructions that are implemented with named templates
- Issue #1225: Generalization of Deep Updates
- Issue #1045: Functions to manage namespace usage
- Issue #641: Serialization fallback
1.6.4. Substantive PRs
The following substantive PRs were open when this agenda was prepared.
- PR #2492: 2052 fn:collation-available: $usage
- PR #2491: 2484 Subtyping: abstract types vs choice types
- PR #2490: 2443 Naming: JNodes, selectors and contents
- PR #2483: 1479 XQuery: Default Namespace Clarifications
- PR #2481: 1528 ambiguities in computed node constructors
- PR #2479: 2472 drop the term "potential visibility"
- PR #2478: 2476 guaranteed streamability
- PR #2474: 272 Allow xsl:use-package to set parameters
- PR #2470: 1310 Functions fn:regex and ?matching-substrings
- PR #2467: Harmonize the fn: and file: functions that read text
- PR #2350: 708 An alternative proposal for generators
- PR #2345: 2299 Expand pipeline to allow arrow expression in path expression
- PR #2313: 2298 XQFO rules: definition of default values
- PR #2247: 716 Deferred Evaluation in XPath - the f:generator record
- PR #2019: 1776: XSLT template rules for maps and array
1.6.5. Required for V4.0
The following issues are labeled “required for V4.0”.
2. Technical agenda
2.1. PR #2467: Harmonize the fn: and file: functions that read text
See PR #2467
I think the high-order question here is, do we want to add fallback to the
text functions, or leave them alone and add it to bin:decode-string?
2.2. PR #2470: 1310 Functions fn:regex and ?matching-substrings
See PR #2470
2.3. PR #2481: 1528 ambiguities in computed node constructors
See PR #2481
2.4. PR #2483: 1479 XQuery: Default Namespace Clarifications
See PR #2483
2.5. PR #2490: 2443 Naming: JNodes, selectors and contents
See PR #2490
2.6. PR #2491: 2484 Subtyping: abstract types vs choice types
See PR #2491
2.7. PR #2492: 2052 fn:collation-available: $usage
See PR #2492
2.8. PR #2474: 272 Allow xsl:use-package to set parameters
See PR #2474
2.9. PR #2478: 2476 guaranteed streamability
See PR #2478
2.10. PR #2479: 2472 drop the term "potential visibility"
See PR #2479