QT4 CG Meeting 011 Agenda 2022-11-15


This meeting will be hosted on Zoom at 16:00GMT (17:00CET, 11:00EST).

See the meeting logistics page for details.

1. Administrivia

1.1. Roll call

1.2. Accept the agenda

1.3. Next meeting

Regrets for the next meeting?

1.4. Approve minutes of previous meeting

Minutes of the previous meeting.

1.5. Review of open action items [7/8]

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

  • [ ] QT4CG-002-10: BTW to coordinate some ideas about improving diversity in the group
  • [X] QT4CG-007-05: NW to make an issue for Martin’s proposed ammendment to map:build
  • [X] QT4CG-008-04: MK to submit a PR for fn:parseQName() to resolve PR #207
    • Mike reports the action is complete in PR #207
  • [X] QT4CG-009-01: NW to coordinate with MK on an agenda for 8 November.
  • [X] QT4CG-009-02: NW to work with MK to make sure PR #197 is updated correctly
  • [X] NW to update PR #215
    • [X] QT4CG-009-03: NW to investigate the relationship between PR #215 and resolve-uri.
    • [X] QT4CG-009-04: NW to review RFC 3896 wrt relative URIs
    • [X] QT4CG-009-05: NW to fix the return type for parse-uri; consider using a record type.
    • [X] QT4CG-009-06: NW to add error tests for parse-uri.
    • [X] QT4CG-009-07: NW to make the query segments an array of maps.
  • [X] QT4CG-010-01: DN to create an issue for proposing an optional else in XPath/XQuery
  • [X] QT4CG-010-02: MK to incorporate the suggestions made by MSM on @then/@else on xsl:if

1.6. Merging PRs that are accepted in principle

We’ve been keeping PRs open while detailed comments are worked out. I think that’s a fine model, but it has the consequence that we end up with a lot of PRs open for a long time. That increases the chances that we’ll create merge conflicts, making our life more difficult later, and means that there are many slightly different copies of each spec to review.

I propose that we agree to merge PRs as soon as the group feels that the proposal is complete enough to accept in principle. We can add a note in the history (for functions, at least) that it’s provisionally accepted until detailed comments are resolved, or words to that effect.

In the very short term, I would especially like to merge all of the PRs that are open against F&O so that the XML validity errors and the new markup for “type references” can be sorted out.

2. Technical Agenda

2.1. Review pull request #197 (was 166; variadic functions)

NW updated the PR with MK’s most recent changes.

We hope to resolve this PR this week.

2.2. Review pull request #210: Issue 80: fn:while

We hope to resolve this PR this week.

2.3. Review pull request #202 (was 196; subtyping)

See pull request #202

Waiting for update from MK.

2.4. Review pull request #207: new expanded-QName function

See pull request #207

Waiting for action QT4CG-008-04 on MK.

2.5. Review pull request #215: parse-uri/build-uri

See pull request #215

Waiting on actions QT4CG-009-0{3,4,5,6,7} on NW.

2.6. Review pull request #222: sequence comparisons

See pull request #222

Accepted at meeting 009, waiting for MK to resolve a merge conflict.

2.7. Review pull request #228: make F&O spec valid XML

See pull request #228

Approved by RD, waiting for open PRs on F&O to be accepted, then NW will resolve any merge conflicts that arise and commit it.

2.8. Review pull request #230: guarded expressions, issue #71

See pull request #230 and related issue #71.

Approved by CG.

2.9. Review pull request #232: data model clarifications, issue #225

See pull request #232 and related issue #225.

2.10. Issue #170, XPath “otherwise” operator

MK proposes that this issue may be ready to be decided.

2.11. Issue #114, array:index-where

MK proposes that this issue may be ready to be decided

2.12. Issue #107, allow self::(a|b|c)

MK proposes that this issue may be ready to be decided.

2.13. XPath 4.0 functions

2.13.1. fn:duplicate-values

2.13.5. fn:differences

Editorially, this function is not ready for approval. We should decide if we want to pursue it, and if we do, how.

2.13.10. map:entries

2.13.14. fn:parts

  • See ???

2.13.15. fn:init, fn:foot, etc

2.13.16. fn:convert-to/from-EQName

2.13.17. fn:parse-html

2.13.18. fn:split-by-graphemes

2.13.19. fn:until

2.13.20. fn:nl, fn:cr, fn:tab

2.13.21. fn:deep-normalize-space

2.13.22. fn:parcel, fn:unparcel, array:from-members/of, array:members/parcels

2.13.23. array:values, map:values

3. Any other business