QT4 CG Meeting 153 Agenda 2026-02-17

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 17 February 2026.

The next meeting is planned for 24 February 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
  • [X] QT4CG-150-03: NW to setup an agenda item to review open issues
  • [ ] 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

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

The following PRs are open but have merge conflicts or comments which suggest they aren’t ready for action.

  • 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 #2266: 540 system-property equivalent for XQuery
  • PR #2247: 716 Deferred Evaluation in XPath - the f:generator record
  • PR #2160: 2073 data model changes for JNodes and Sequences
  • PR #2071: 77c deep update
  • PR #2019: 1776: XSLT template rules for maps and array

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 #2446: 2427 Add computed node constructors to XPath

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 #2234: Replace `a/get(XX)` with `a/?(XX)`

1.6.4. Substantive PRs

The following substantive PRs were open when this agenda was prepared.

  • PR #2457: Improved use of fos:result
  • PR #2456: Stylesheet handling of fos:result/@narrative

1.6.5. Required for V4.0

The following issues are labeled “required for V4.0”.

  • Issue #1777: Shallow copy in XSLT with maps and arrays
  • Issue #1584: Review the XML Schema and RELAX NG schemas for XSLT 4.0 for compatibility
  • Issue #1045: Functions to manage namespace usage
  • Issue #675: XSLT streaming rules for new constructs
  • Issue #272: Setting parameter values in xsl:use-package

1.6.6. To be triaged

The following issues need to be triaged.

  • Issue #2465: Error description of FODC0006 should be more generic
  • Issue #2464: add method to use path()
  • Issue #2463: Add map:apply() or third argument to fn:apply() as a map of names to parameter values.
  • Issue #2462: Revert dynamic function calls on sequences
  • Issue #2461: Unparsed entities
  • Issue #2460: read-text and invalid XML characters
  • Issue #2459: What are "invalid XML characters" in the XPath file read functions?
  • Issue #2458: NodeTests: Unify jnode(X) and get(X)
  • Issue #2455: `copy`: creating targets
  • Issue #2454: Grammar: literals & constants, negative numbers
  • Issue #2448: Change title of XPath specification
  • Issue #2433: `fn:jtree`: Identity
  • Issue #2408: Editorial notes (incremental)
  • Issue #2390: methods and inheritance
  • Issue #2389: Adaptive Serialization: more freedom?
  • Issue #2388: Adaptive Serialization: function items
  • Issue #2381: Add facility to serialize binary values as url-safe base64 encoded strings
  • Issue #2380: Use Case for Generators: News Feeds Aggregation Using Generators
  • Issue #2338: Nomenclature: node(), gnode(), jnode(), xnode()
  • Issue #2321: Make `fn:trace` non-deterministic
  • Issue #2314: `fn:error`: return type `xs:error` ?
  • Issue #2300: `fn:doc`: determinism rules
  • Issue #2298: XQFO rules: definition of default values
  • Issue #2284: fn:csv-doc, fn:json-doc: Equivalent code, unifications
  • Issue #2275: Change record constructor, to simplify updates
  • Issue #2263: Named record types: TODOs
  • Issue #2257: Record declarations without namespace
  • Issue #2252: Dynamic XPath Evaluation the functional way
  • Issue #2245: Action QT4CG-116-01: Add a specific error code for unsupported options on doc and doc-available
  • Issue #2234: Replace `a/get(XX)` with `a/?(XX)`
  • Issue #2219: Generalize method calls to sequences
  • Issue #2215: XQFO xref from xml-to-json() to element-to-map()
  • Issue #2198: Serialization parameter: `conditional-cdata`
  • Issue #2169: Longest-token rule incorrectly produces `StringInterpolation` delimiter
  • Issue #2128: JNodes and XSLT Streaming
  • Issue #2052: fn:collation-available: $usage
  • Issue #2039: Generalize context item to context value in XSLT
  • Issue #2018: Type-checking the result of xsl:apply-templates
  • Issue #2000: element-to-map() - type signature of plan
  • Issue #1979: Records: Type Safety
  • Issue #1949: fn:element-to-map: Updated Feedback
  • Issue #1948: fn:element-to-map: Tests
  • Issue #1920: Parse functions: determinism
  • Issue #1697: Add documentary names to callback function signatures
  • Issue #1528: Computed node constructors: observations
  • Issue #1479: Default element namespace in XQuery: interaction of 'fixed' and '##any'
  • Issue #1459: Function properties and arities
  • Issue #1310: add fn:match-groups() function
  • Issue #641: Serialization fallback

2. Technical agenda

2.1. Improvements to FOS

See PR #2457 Improved use of fos:result, and PR #2456: Stylesheet handling of fos:result/@narrative

2.2. Issue #2460: read-text and invalid XML characters

See issue #2460: read-text and invalid XML characters

Perhaps we can decide what needs to be done here.

2.3. Other issue triage

Proposals for how to proceed most humbly solicited. In the absense of any such proposal, I think a good first step would be to look over the 78 open issues and divide them into “required for 4.0” and “nice to have” and perhaps even “close with no further action.” Any we can’t decide on, we can just leave for another day.

3. Any other business