QT4 CG Meeting 089 Agenda 2024-09-10

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. (As amended.)

1.4. Next meeting

This meeting is planned for 10 September 2024. The following meeting is scheduled for 17 September.

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

(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-087-01: DN to update PR #1228 to reflect MK’s compromise and update the vulnerabilities
  • [ ] QT4CG-088-01: NW to consider how best to add a dedication to MSM.
  • [ ] QT4CG-088-02: CG to add an issue about built-in, named record types.
  • [ ] QT4CG-088-03: MK to add an example of duplicate function-annotations being returned.
  • [ ] QT4CG-088-04: [Someone] needs to update the processing model diagram needs vis-a-vis the static typing feature

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 #1414: XSLT spec abstract, introduction
  • PR #1355: 1351 Add "declare record" in XQuery
  • PR #1296: 982 Rewrite of scan-left and scan-right
  • PR #1227: 150 PR resubmission for fn ranks
  • PR #1209: 1183 Add transient mode and the transient{} expression
  • PR #1185: 1179 array:values, map:values → array:get, map:get
  • PR #1062: 150bis - revised proposal for fn:ranks
  • PR #832: 77 Lookup returning path selection
  • PR #529: 528 fn:elements-to-maps

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 #1425: 1424 Fix typo
  • PR #1423: Clarify parse-uri/build-uri encoding rules, and remove options
    • Note: an alternative to/replacement for PR #1388
  • PR #1419: 1337bis Replace a few remaining occurrences of "atomic value"
  • PR #1418: 1415 Add to lists of XSLT declarations and instructions
  • PR #1417: 1408 Fix reference to "function conversion rules" in XPTY0117
  • PR #1413: Dispose of action QT4CG-080-05, add absolute to parse-uri
  • PR #1412: Fix typo in uri-structure-record
  • PR #1393: 1391 Change function-annotations to return a sequence
    • Accepted last week but not merged?

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 #1385: Quantifier expressions: optional positional argument
  • PR #1388: 1387 Clarify the encoding rules

1.6.4. XSLT focused

The following PRs appear to be candidates for a future XSLT-focused meeting.

  • PR #1418: 1415 Add to lists of XSLT declarations and instructions
  • PR #1414: XSLT spec abstract, introduction
  • PR #1378: 1375 - bugs in pattern syntax

1.6.5. Substantive PRs

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

  • PR #1429: Align type tests
  • PR #1428: 1426 Add notes on endianness of CRC-32
  • PR #1393: 1391 Change function-annotations to return a sequence
  • PR #1364: 1314 Change to type() syntax to fix ambiguity
  • PR #1360: 1348 Some grammar simplifications
  • PR #1283: 77b: Update expressions

1.6.6. 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 #1235: Function Identity: Treating function items with identical bodies
  • 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 #755: Expression for binding the Context Value
  • Issue #748: Parse functions: consistency
  • Issue #689: fn:stack-trace: keep, drop, 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. Issue #755: Expression for binding the Context Value

See issue #755.

There has been a lot of discussion in this issue and a lot of controversy. Please review the issue and be prepared to engage in productive discussion.

Remember that we are designing a language for several different constituencies: new users, casual users, experienced users, and expert users, at least. We all start as new users and rise to some level of experience with each language and to some extent each language feature.

It’s reasonable to argue that a feature has implications with respect to new users. But it’s equally reasonable to argue that a feature (or the lack of a feature) has implications for expert users.

2.2. PR #1360: 1348 Some grammar simplifications

See PR #1360

2.3. PR #1364: Change to type() syntax to fix ambiguity

See PR #1364

2.4. PR #1283: 77b: Update expressions

See PR #1283

2.5. PR #1429: Align type tests

See PR #1429

2.6. PR #1428: 1426 Add notes on endianness of CRC-32

See PR #1428

2.7. PR #1393: 1391 Change function-annotations to return a sequence

See PR #1393

3. Any other business