QT4 CG Meeting 093 Agenda 2024-10-08

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 8 October 2024. The following meeting is scheduled for 15 October.

Note: The QT4CG operates on European civil time. In Europe and the United Kingdom, summer time ends on 27 October. In the United States, summer time ends on 3 November. That means the meeting of 29 October will be one hour later in the United States.

1.5. Review of open action items [0/6]

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

  • [ ] QT4CG-080-07: NW to update the build instructions in the README
  • [ ] QT4CG-082-02: DN to work with MK to come to agreement on the fn:ranks proposal
  • [ ] QT4CG-088-01: NW to consider how best to add a dedication to MSM.
  • [ ] QT4CG-088-04: [Someone] needs to update the processing model diagram needs vis-a-vis the static typing feature
  • [ ] QT4CG-089-01: CG to draft a PR that attempts to resolve the operators described in #755 to a smaller number of orthogonal choices.
  • [ ] QT4CG-091-01: MK to make sure there’s an editorial note about parameter renaming.

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 #1296: 982 Rewrite of scan-left and scan-right
  • PR #1283: 77b Update expressions
  • PR #1062: 150bis revised proposal for fn:ranks
  • PR #529: 528 fn:elements-to-maps

1.6.2. 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 #1305: Almost all functions in FO that must process multiple string items, can have as a parameter only a single collation

1.6.3. Substantive PRs

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

  • PR #1482: 1468 Revise the xsl:array instruction
  • PR #1481: 1448 Component extraction on gregorian types
  • PR #1480: 1450 Disallow reserved names in element/attribute constructors
  • PR #1477: 1475 Stylesheet change to mark optional fields with '?'
  • PR #1476: 1474 xml-to-json: ensure numbers are JSON conformant
  • PR #1472: 1471 JSON Serialization: Sequences on Top Level
  • PR #1470: 689 fn:stack-trace: replace with $err:stack-trace
  • PR #1467: Modest editorial corrections to XSLT specs through 2.7
  • PR #1454: 1449 Relax rules on multiple xsl:includes
  • PR #1442: 1394 Add new default priority rules
  • PR #1378: 1375 bugs in pattern syntax
  • PR #1355: 1351 Add "declare record" in XQuery
  • PR #1227: 150 PR resubmission for fn ranks

1.6.4. Required for V4.0

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

  • Issue #1252: Add a new function `fn:html-doc`
  • Issue #1240: $sequence-of-maps ? info()
  • Issue #1238: XSLT on-no-match="shallow-copy-all" - revised rules
  • Issue #1169: Maps & Arrays: Consistency & Terminology
  • 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 #868: fn:intersperse → fn:join, array:join($arrays, $separator)
  • Issue #826: Arrays: Representation of single members of an array
  • Issue #767: parse-html(): case of SVG element names
  • Issue #748: Parse functions: consistency
  • Issue #689: fn:stack-trace: replace with $err:stack-trace
  • Issue #675: XSLT streaming rules for new constructs
  • Issue #501: Error handling: Rethrow errors; finally block
  • Issue #490: Control over schema validation in parse-xml(), doc(), etc.
  • Issue #407: XSLT-specific context properties used in function items
  • Issue #272: Setting parameter values in xsl:use-package
  • Issue #69: fn:document, fn:function-available: default arguments

2. Technical agenda

2.1. PR #1355: 1351 Add "declare record" in XQuery

See #1355

2.2. PR #1481: 1448 Component extraction on gregorian types

See #1481

2.3. PR #1480: 1450 Disallow reserved names in element/attribute constructors

See #1480

2.4. PR #1477: 1475 Stylesheet change to mark optional fields with '?'

See #1477

2.5. PR #1476: 1474 xml-to-json: ensure numbers are JSON conformant

See #1476

2.6. PR #1472: 1471 JSON Serialization: Sequences on Top Level

See #1472

2.7. PR #1482: 1468 Revise the xsl:array instruction

See #1482

2.8. PR #1470: 689 fn:stack-trace: replace with $err:stack-trace

See #1470

2.9. PR #1467: Modest editorial corrections to XSLT specs through 2.7

See #1467

2.10. PR #1454: 1449 Relax rules on multiple xsl:includes

See #1454

2.11. PR #1442: 1394 Add new default priority rules

See #1442

2.12. PR #1378: 1375 bugs in pattern syntax

See #1378

3. Any other business