QT4 CG Meeting 011 Agenda 2022-11-15

Regrets for the next meeting?

Minutes of the previous meeting.

(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
  • See issue #236.
• [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
  • https://lists.w3.org/Archives/Public/public-xslt-40/2022Nov/0013.html

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.

• See pull request #197 (you’ll find links to formatted versions of the specs at https://qt4cg.org/).
• See also the nexus of issues #162, #161, #160, #159, #158, #157, and #155.
• See the discussion from meeting 006, meeting 007, and meeting 008.

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

We hope to resolve this PR this week.

• See pull request #210 and the minutes of two weeks ago.

We hope to resolve this PR this week.

See pull request #202

Waiting for update from MK.

See pull request #207

Waiting for action QT4CG-008-04 on MK.

See pull request #215

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

See pull request #222

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

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.

See pull request #230 and related issue #71.

Approved by CG.

See pull request #232 and related issue #225.

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

MK proposes that this issue may be ready to be decided

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