QT4 CG Meeting 115 Agenda 2025-03-25

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

• PR #1283: 77b Update expressions
• PR #1062: 150bis revised proposal for fn:ranks

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

• PR #1890: More examples added to fn:chain
• PR #1888: 366 xsl:package-location
• PR #1887: 1870 rename $zero keyword of fold functions
• PR #1886: 1660 Additional options for fn:path
• PR #1883: 882 Replace fn:chain by fn:compose
• PR #1875: 1861 Params passed automatically through next-match
• PR #1874: 1862 Coercing to a record type changes map order
• PR #1858: Initial xsl:record
• PR #1819: 451 Multiple schemas in XSLT
• PR #1766: 1715 Drop array bound checking
• PR #1587: 557 Add fn:binary-resource

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

• Issue #1777: Shallow copy in XSLT with maps and arrays
• Issue #1742: Maps constructed using streamed xsl:fork instruction should not be ordered
• 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 #826: Arrays: Representation of single members of an array
• Issue #748: Parse functions: consistency
• Issue #714: Function annotations in XSLT
• Issue #675: XSLT streaming rules for new constructs
• Issue #501: Error handling: Rethrow errors; finally block
• 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

The following issues need to be triaged.

• 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 #1881: fn:function-identity for maps and arrays
• Issue #1876: `fn:replace`: Combine $replacement and $action parameters
• Issue #1871: Arrays and maps: consistency
• Issue #1870: Rename $zero keyword of fold-left and fold-right
• 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 #1846: %method functions, dynamic function calls
• Issue #1844: Drop mapping arrow operator
• Issue #1832: Associativity of Operators, especially "||" (Appendix A.5)
• Issue #1799: "well-formed HTML document"?
• Issue #1797: elements-to-maps: separate function to construct a plan
• 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 #1754: Inverse functions to bin:hex, bin:bin, and bin:octal
• 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 #1660: Further suggestions for fn:path
• Issue #1658: fn:elements-to-maps: `empty`, normalize space ?
• Issue #1648: fn:elements-to-maps: Types
• Issue #1647: fn:elements-to-maps: Explicit Layouts
• Issue #1646: fn:elements-to-maps: Robustness
• Issue #1645: fn:elements-to-maps: Debugging
• Issue #1644: fn:elements-to-maps: Mixed Content
• Issue #1624: document-node(a|b) is the same type as document-node(a)|document-node(b)
• 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 #1520: Type declarations of cyclically dependent modules
• 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 #1363: map:get and array:get
• Issue #1310: add fn:match-groups() function
• Issue #1307: For symmetry, add functions array:scan-left and array:scan-right
• Issue #1271: Schema validation in XPath
• Issue #1175: XPath: Optional parameters in the definition of an inline function
• Issue #850: fn:parse-html: Finalization
• Issue #760: Serialize functions: consistency
• Issue #641: Serialization fallback.
• Issue #119: Allow a map's key value to be any sequence

See PR #1883, see also PR #1890: More examples added to fn:chain

We discussed this last week; let’s time box this to 15 minutes and if we haven’t reached a resolution, try to switch to working out what next steps would help us reach a resolution.

See PR #1875

See PR #1874

See PR #1888

See PR #1887

See PR #1858

See PR #1886

See issue #1832

See issue #1799

See issue #1797

See issue #760

See issue #641

See issue #119