QT4 CG Meeting 118 Agenda 2025-04-22
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 22 April 2025. The following meeting is scheduled for 29 April 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-082-02: DN to work with NW to come to agreement on the fn:ranks proposal[ ]
QT4CG-107-05: JLO and DN to consider a proposal for system defined records.[ ]
QT4CG-112-01: JLO to propose a concrete example that uses “.” in a ~%method~s.[ ]
QT4CG-113-02: NW to investigate a way to show extra attributes in the syntax summary.[ ]
QT4CG-115-02: JWL to write a few tests for xsl:record[ ]
QT4CG-116-01: Add a specific error code for unsupported options on doc and doc-available[ ]
QT4CG-116-03: NW to review the star/plus/delta symbols in the ToC. (See 1838)[ ]
QT4CG-117-01: MK to add errors for invalid plans.[ ]
QT4CG-117-02: MK to rename ‘fallback’ to ‘default’, then merge the 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.
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 #910: Introduce a Kollection object with functions that operate on all types of items that can be containers of unlimited number of "members"
1.6.4. Substantive PRs
The following substantive PRs were open when this agenda was prepared.
- PR #1937: 1936 Mark attribute declarations as form=qualified
- PR #1933: 1271 fn:validate() function
- PR #1929: 1725 xsl:mode/@copy-namespaces
- PR #1928: 1844b Arrow Expressions
- PR #1926: 1907 method lookup (disallow wildcard selection)
- PR #1922: 1921 Expand definition of version ranges in XSLT
- PR #1906: 1797 elements-to-maps-conversion-plan function
- PR #1894: Additional examples to fn:chain - in a new branch
- PR #1883: 882 Replace fn:chain by fn:compose
- PR #1587: 557 Add fn:binary-resource
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 #1240: $sequence-of-maps ? info()
- 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 #748: Parse functions: consistency
- Issue #714: Function annotations in XSLT
- Issue #675: XSLT streaming rules for new constructs
- Issue #407: XSLT-specific context properties used in function items
- Issue #366: Support xsl:use-package with xsl:package-location
- Issue #272: Setting parameter values in xsl:use-package
1.6.6. To be triaged
The following issues need to be triaged.
- Issue #1938: Invoking coerced methods
- Issue #1935: doc-available() with invalid options
- Issue #1934: Supporting RELAX NG validation
- Issue #1920: Parse functions: determinism
- Issue #1912: Error handling: `fn:throw`
- Issue #1903: `fn:scan-left`, `fn:scan-right`: missing steps
- Issue #1889: HTML serialization: `html-version` and `version` parameters; allowed values
- Issue #1885: Use the spcification grammar markup to define the regular expression grammar in F&O
- Issue #1871: Arrays and maps: consistency
- Issue #1868: array:members() to include index position
- Issue #1859: Question on `fn:chain` and `err:FOAP0001`
- Issue #1852: fn:values-except: Return atomic values that occur in A but not in B
- Issue #1844: Drop mapping arrow operator
- Issue #1795: XSLT templates: Matching values in a map by key
- Issue #1787: Sorted maps revisited
- Issue #1775: Navigation in JSON trees
- Issue #1774: Nomenclature: relabelling
- Issue #1736: Add option retain-order=false when constructing maps
- Issue #1718: Ordered Maps: positions in callback functions
- Issue #1704: Ignore the byte order mark more completely/globally
- Issue #1697: Add documentary names to callback function signatures
- Issue #1661: QName arguments: also allow strings
- Issue #1644: fn:elements-to-maps: Mixed Content
- Issue #1618: Adaptive serialization: doubles
- Issue #1591: Implausible filter expressions
- Issue #1583: JSON: Parsing and serializing numbers, often undesired E notation
- Issue #1568: Define a Unicode case-insensitive collation
- Issue #1528: Computed node constructors: observations
- Issue #1484: Functions that expect a record type should make it extensible
- Issue #1479: Default element namespace in XQuery: interaction of 'fixed' and '##any'
- Issue #1459: Function properties and arities (editorial)
- Issue #1416: Key-value pairs: built-in record type `pair`
- Issue #1310: add fn:match-groups() function
- Issue #1307: For symmetry, add functions array:scan-left and array:scan-right
- Issue #1175: XPath: Optional parameters in the definition of an inline function
- Issue #760: Serialize functions: consistency
- Issue #641: Serialization fallback.
2. Technical agenda
2.1. Review of pull requests
I’ve put 1906 back on the top of the agenda because we seem to be making good progress. I propose once again to time box this so we don’t spend the whole meeting discussing it.
2.1.1. PR #1906: 1797 elements-to-maps-conversion-plan function
See PR #1906
2.1.2. PR #1937: 1936 Mark attribute declarations as form=qualified
See PR #1937
2.1.3. PR #1933: 1271 fn:validate() function
See PR #1933
2.1.4. PR #1929: 1725 xsl:mode/@copy-namespaces
See PR #1929
2.1.5. PR #1928: 1844b Arrow Expressions
See PR #1928
2.1.6. PR #1926: 1907 method lookup (disallow wildcard selection)
See PR #1926
2.1.7. PR #1922: 1921 Expand definition of version ranges in XSLT
See PR #1922
2.2. Issue triage
2.2.1. Issue #1832: Associativity of Operators, especially "||" (Appendix A.5)
See issue #1832
2.2.2. Issue #1799: "well-formed HTML document"?
See issue #1799
2.2.3. Issue #1797: elements-to-maps: separate function to construct a plan
See issue #1797
2.2.4. Issue #760: Serialize functions: consistency
See issue #760
2.2.5. Issue #641: Serialization fallback.
See issue #641
2.2.6. Issue #119: Allow a map's key value to be any sequence
See issue #119