QT4 CG Meeting 135 Agenda 2025-09-23

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).

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 23 September 2025.

The next meeting is planned for 30 September 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-116-01: Add a specific error code for unsupported options on doc and doc-available
  • [ ] QT4CG-118-01: MK to make an incorrect type raise an error in #1906
  • [ ] QT4CG-127-01: NW to diagram the JTree representing arbitrary XDM content.
  • [ ] QT4CG-128-03: NW to compare the file: module against the equivalent XProc 3.1 steps
  • [ ] QT4CG-131-01: MK to add a non-schema aware result.
  • [ ] QT4CG-131-02: MK to expand on the $E := <e A="p q r"… example
  • [ ] QT4CG-131-03: MK to change “invert” to “transpose” in the matrix example.
  • [ ] QT4CG-133-01: MK to correct the use of “Expr” in examples for get()
  • [ ] QT4CG-134-01: MK to open an issue about the error code for =?>

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 #2124: 573 Functions to Construct Trees
  • PR #2120: 2007 Revised design for xsl:array
  • PR #2019: 1776: XSLT template rules for maps and array

1.6.2. Substantive PRs

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

  • PR #2202: New rules for schema-attribute and schema-element subtyping
  • PR #2200: 657 Allow user-defined functions in no namespace
  • PR #2176: 2130 encore: precedes-or-is, follows-or-is
  • PR #2175: 2093 Rearrange the order and grouping of functions
  • PR #2160: 2073 data model changes for JNodes and Sequences
  • PR #2071: 77c deep update
  • PR #2155: 2150 Define patterns for JNodes
  • PR #2123: 2051: XSLT group by cluster
  • PR #2120: 2007 Revised design for xsl:array
  • PR #2019: 1776: XSLT template rules for maps and array

1.6.3. 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 #1011: fn:transform() improvements
  • Issue #986: Numeric Comparisons
  • Issue #675: XSLT streaming rules for new constructs
  • 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 #2202: New rules for schema-attribute and schema-element subtyping

See PR #2202.

2.2. PR #2200: 657 Allow user-defined functions in no namespace

See PR #2200.

2.3. PR #2176: 2130 encore: precedes-or-is, follows-or-is

See PR #2176.

2.4. PR #2175: 2093 Rearrange the order and grouping of functions

See PR #2175.

2.5. PR #2160: 2073 data model changes for JNodes and Sequences

See PR #2160.

2.6. PR #2071: 77c deep update

See PR #2071.

2.7. PR #2155: 2150 Define patterns for JNodes

See PR #2155.

2.8. PR #2123: 2051: XSLT group by cluster

See PR #2123.

2.9. PR #2120: 2007 Revised design for xsl:array

See PR #2120.

2.10. PR #2019: 1776: XSLT template rules for maps and array

See PR #2019.

3. Any other business

3.1. FYI: the path to standardization…

The W3C held a meeting about Community Groups recently. One observation from that meeting is that the W3C does not consider Community Groups to be an appropriate place to do standards work. They’re envisioned as incubators that lead to the formation of regular Working Groups or migration of the work to another standards development organization.

I pointed out that there is no W3C Activity for XML-related standardization. One place to discuss this would be at the Technical Plenary but that’s in Kobe, Japan this year and I don’t think anyone in this CG is planning to go. (It will be in Dublin, Ireland next year and I will plan to go.)

More discussion, with an eye towards forming a Working Group is expected in the following months. I have no prediction about how that will proceed.