QT4 CG Meeting 004 Agenda 2022-09-27

Agenda

This meeting will be hosted on Zoom at 16:00BST (15:00GMT, 17:00CEST, 11:00EDT).

See the meeting logistics page for details.

1. Administrivia

1.1. Roll call

1.2. Approve minutes of previous meeting

Minutes of the previous meeting: https://qt4cg.org/meeting/minutes/2022/09-20.html.

As amended on 20 September 2022 by MK.

1.3. Review of open action items `[4/6]`

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

[ ] QT4CG-002-01: NW to incorporate email feedback and produce new versions of the process documents.
[X] QT4CG-003-01: MK to find a way to specify fn:characters() more formally
- https://lists.w3.org/Archives/Public/public-xslt-40/2022Sep/0044.html
[X] QT4CG-003-02: MK to propose a reformulation of fn:index-of() in terms of fn:index-where()
- https://lists.w3.org/Archives/Public/public-xslt-40/2022Sep/0045.html
[ ] QT4CG-003-03: NW to tweak the CSS for function signatures to avoid line breaks on - characters.
[X] QT4CG-003-04: MK to rename fn:uniform() and fn:unique() to fn:all-equal() and fn:all-different(), respectively
- https://github.com/qt4cg/qtspecs/commit/f4b331869f0d75a5a706c01cc0655625fe065fa0 (see below)
[X] QT4CG-003-05: MK to consider how fn:array-filter() could be generalized to handle array predicates on the index as well as the value.
- https://lists.w3.org/Archives/Public/public-xslt-40/2022Sep/0046.html

2. Technical Agenda

2.1. Approve proposed changes to fn:all and fn:some

Mike completed his action. I’ve republished the PR so that it builds against the updated infrastructure.

2.2. Approve changes in `changes-agreed-2022-09-20` branch

Mike created a branch which renames fn:uniform() and fn:unique() per his action QT4CG-003-04 and adds a few other editorial improvements.

2.3. XPath 4.0 functions

See https://github.com/qt4cg/qtspecs/blob/master/editorial/functions-checklist.pdf

The items that follow are taken from the PDF in roughly the order presented in the PDF. The agenda does not intend to assert that they must or should be discussed in precisely this order.

2.3.1. Variadic functions

Dimitre proposes that we should discuss variadic functions sooner rather than later:

“WRT our dependency sorting, can we discuss with high priority and approve the XPath 4.0 variadic functions, so that immediately after that we could typically describe not N overloads of a proposed function, but just a single signature containing keyword arguments with defaults?”

2.3.2. Move `fn:deep-equal` higher up the list?

Dimitre observes “some of the functions to be discussed that are included in the current list/checklist, depend on using a compare() function / strategy. This makes all of them dependent on having first discussed and approved fn:deep-equal(options). Therefore, could we move fn:deep-equal(options) considerably higher in the list, so that it precedes all such functions that are dependent on a compare() function/strategy?”