QT4 CG Meeting 108 Agenda 2025-02-04

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)

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 4 February 2025. The following meeting is scheduled for 11 February 2025.

1.5. Review of open action items [3/11]

(Items marked [X] are believed to have been closed via email before this agenda was posted.)

  • [ ] QT4CG-082-02: DN to work with MK to come to agreement on the fn:ranks proposal
  • [X] QT4CG-088-04: [Someone] needs to update the processing model diagram needs vis-a-vis the static typing feature
  • [ ] QT4CG-097-02: MK to make the XSD schema component references into links to XSD
  • [ ] QT4CG-103-01: MK to add an example of showing all the properties for an untyped node.
  • [X] QT4CG-106-01: NW to remove the dead wood from the XSLT build (SVG diagrams)
  • [ ] QT4CG-107-01: MK to amend PR 1722 so the expansion of focus functions includes the return type item()*
  • [ ] QT4CG-107-02: MK to propose adding the "duplicates" option (from map:merge) to map:build and map:of-pairs
  • [ ] QT4CG-107-03: MK to propose amending all the functions that return ordered maps so that when duplicates are found, the key of the combined entry is taken from the first of the duplicates.
  • [ ] QT4CG-107-04: MK to review CG’s comment to align fn:map-merge by removing the reference to random number generator and fixing a typo.
  • [ ] QT4CG-107-05: JLO and DN to consider a proposal for system defined records.
  • [X] QT4CG-107-06: NW to integrate DN’s expandable ToC into the build.

1.6. Review of open pull requests and issues

1.6.1. Blocked

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

  • 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

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 #1760: Remove hand-generated diffs from the builds
  • PR #1759: Fix validation issues in the EXPath module function catalogs
  • PR #1743: 1738 Formatting of Notes in F&O
  • PR #1741: 1739 drop references to ordering mode in the static context
  • PR #1734: 1682 Type promotion and operator mapping

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 #1699: XPath function to calculate edit distance between two strings
  • Issue #1571: Discussion: On the implementability of the specs and helping implementors

1.6.4. Substantive PRs

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

  • PR #1753: 1750 Overhaul of EXPath binary spec
  • PR #1746: Replace processing model diagrams

1.6.5. Required for V4.0

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

  • Issue #1240: $sequence-of-maps ? info()
  • Issue #1238: XSLT on-no-match="shallow-copy-all" - revised rules
  • 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 #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 #272: Setting parameter values in xsl:use-package

1.6.6. To be triaged

The following issues need to be triaged.

  • Issue #1754: Inverse functions to bin:hex, bin:bin, and bin:octal
  • Issue #1753: 1750 Overhaul of EXPath binary spec
  • Issue #1752: Return type of fn:partition()
  • Issue #1751: bin:encode-string - should the result have a BOM?
  • Issue #1750: EXPath Binary : copy-edits and minor enhancements
  • Issue #1746: Replace processing model diagrams
  • Issue #1742: Maps constructed using streamed xsl:fork instruction should not be ordered
  • Issue #1741: 1739 drop references to ordering mode in the static context
  • Issue #1740: 1725b Further elaboration of duplicates handling in maps
  • Issue #1737: Grammar problems introduced by #1732
  • Issue #1736: Add option retain-order=false when constructing maps
  • Issue #1735: 1341 Drop $position callback from many functions
  • Issue #1734: 1682 Type promotion and operator mapping
  • Issue #1729: Grammar problems introduced by #1721
  • Issue #1724: Allow @copy-namespaces on <xsl:mode>?
  • Issue #1718: Ordered Maps: positions in callback functions
  • Issue #1716: Variable lookahead needed for `ArrowTarget`
  • Issue #1715: Array Lookups: partial removal of out-of-bounds checks
  • Issue #1704: Ignore the byte order mark more completely/globally
  • Issue #1702: Node Updates: Functions
  • Issue #1698: Allow select attribute for xsl:call-template instruction
  • 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 #1631: xsl:apply-templates (without select) should allow inline 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 #1587: 557 Add fn:binary-resource
  • Issue #1584: Review the XML Schema and RELAX NG schemas for XSLT 4.0 for compatibility
  • 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 #1537: XSLT: local functions within an enclosing xsl:mode
  • 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 #1456: Filtering by type in lookup expressions
  • 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 #1296: 982 Rewrite of scan-left and scan-right
  • Issue #1283: 77b Update expressions
  • Issue #1271: Schema validation in XPath
  • Issue #1227: 150 PR resubmission for fn ranks
  • Issue #1175: XPath: Optional parameters in the definition of an inline function
  • Issue #1062: 150bis revised proposal for fn:ranks
  • Issue #850: fn:parse-html: Finalization
  • Issue #760: Serialize functions: consistency
  • Issue #755: with expression; chaining and concatenation
  • Issue #641: Serialization fallback.
  • Issue #583: (array|map):replace → *:substitute or *:change
  • Issue #576: JSON serialization: INF/NaN, function items
  • Issue #322: Map construction in XSLT: xsl:record instruction
  • Issue #285: Stability of collections
  • Issue #158: Support optional parameters on dynamic functions
  • Issue #75: Support processing HTML 5 template element content

2. Technical agenda

2.1. PR #1753: 1750 Overhaul of EXPath binary spec

See PR #1753.

2.2. PR #1746: Replace processing model diagrams

See PR #1746.

2.3. Issue triage

Using the PRG-* tags seems like it would be inviting confusion. New tags proposal:

  • Reviewed-required, this is a required feature; we can’t progress without it.
  • Reviewed-optional, this is an optional feature we’re still hoping to finish.
  • Reviewed-close, this is an optional feature that we’d like to have, but we’re going to abandon it if no one provides a detailed change proposal. (This category implies “close without further action” at the next meeting.)
  • Reviewed-easy, Reviewed-hard, optional tags indicating the consensus intuition about how difficult it would be to address the issue.

There are 70 untriaged issues. We can start at the top, or the bottom, or with nominations for “easy to categorize” issues.

3. Any other business