QT4 CG Meeting 111 Agenda 2025-02-25

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

• PR #1766: 1715 Drop array bound checking
• PR #1587: 557 Add fn:binary-resource
• PR #1296: 982 Rewrite of scan-left and scan-right
• PR #1283: 77b Update expressions
• PR #1062: 150bis revised proposal for fn:ranks
• PR #1227: 150 PR resubmission for fn ranks

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 #1826: Fix grammar bug #1818
• PR #1824: 1823 Revise top-level headings in F+O spec
• PR #1814: 1813 Reorganise the XDM spec at top level
• PR #1812: 1811 Add note regarding non-XML chars in xsl:output-character

It has been proposed that the following issues be closed without action. If you think discussion is necessary, please say so.

• Issue #119: Allow a map's key value to be any sequence

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

• PR #1833: 583 Drop map:replace and array:replace
• PR #1830: 1829 Reintroduce restrictions on RHS of `=>`
• PR #1828: 1815 Add more detail on annotations of function items
• PR #1825: 1816 New function fn:partial-apply
• PR #1817: 1800 Methods
• PR #1801: 1798 Function fn:function-identity
• PR #1735: 1341 Drop $position callback from many functions
• PR #1740: 1725b Further elaboration of duplicates handling in maps
• PR #1778: 1456 Lookup expressions filtered by type
• PR #1819: 451 Multiple schemas in XSLT

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 #1836: unparsed-text-lines() - line endings
• 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 #1796: Allow fn:invisible-xml to return a function that returns an item()
• Issue #1795: Matching values in a map by key
• Issue #1794: Lookup: select all except
• Issue #1787: Sorted maps revisited
• Issue #1786: A case study for XSLT transformation of JSON: the transpiler
• Issue #1780: xsl:for-each optional variable introduction
• Issue #1775: Navigation in JSON trees
• Issue #1774: Nomenclature: relabelling
• Issue #1771: fn:deep-equal: map order
• 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 #1702: Node Updates: Functions
• 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 #1656: Ordered Maps: Updates
• 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 #1566: EXPath Modules: Future
• Issue #1528: Computed node constructors: observations
• Issue #1520: Type declarations of cyclically dependent modules
• Issue #1514: Editorial: optional position argument in function signature for for-each and other HOF
• 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 #1340: Namespace nodes and the namespace axis
• Issue #1338: Arrays and maps: Members, entries, values, contents, pairs, …
• Issue #1319: Specification Documents: Editors and Contributors
• 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 #1837

See PR #1833

See PR #1830

See PR #1828

See PR #1825

See PR #1817

See PR #1801

See PR #1735

See PR #1740

See PR #1778

See PR #1819

See issue #1836

See issue #1832

See issue #1799

See issue #1797

See issue #760

See issue #641

See issue #119