QT4 CG Meeting 029 Agenda 2023-04-04


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

See the meeting logistics page for 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 4 April, the following meeting is scheduled for 11 April.

Any regrets for the following meeting?

1.5. Review of open action items [1/9]

(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
  • [ ] QT4CG-016-08: RD to clarify how namespace comparisons are performed.
  • [ ] QT4CG-023-01: NW to review the stylesheets for functions across XPath and XSLT
  • [ ] QT4CG-025-03: MK to revise and expand technical detail in PR #375
  • [ ] QT4CG-026-01: MK to write a summary paper that outlines the decisions we need to make on “value sequences”
  • [ ] QT4CG-027-01: MK to update the text for next-match wrt type() matching
  • [ ] QT4CG-028-01: MK to summarize the options available wrt deep equal and errors

2. Technical Agenda

In response to feedback from last week, this agenda includes more issues and fewer PRs. MSM and I reviewed the issues list and selected a group of issues that (a) looked like they would benefit from discussion and (b) were not marked Feature or Enhancement. (We obviously need to discuss enhancements and features too, but focusing on bugs and errors seemed like a good initial strategy.)

I propose an initial 15 minute time box on each issue. If, after 10 minutes, if we aren’t closing in on a resolution, let’s work out what we need to do to improve our chances of being able to resolve it next time.

2.1. PR #411: Remove the note from the parse-html unparsed-entity sections

2.2. Issue #399: Using Multilevel Hierarchy and Abstraction…deep-equal

2.3. Issue #280: Why is resolve-uri forbidden … a fragment identifier?

See issue 280.

2.4. Issue #293: Error in fn:doc-available specification

See issue 293.

2.5. Issue #315: fn:transform inconsistency: initial-mode

See issue 315.

2.6. Issue #367: Focus for RHS of thin arrow expressions

See issue 367.

2.7. Issue #397: Type names

See issue 397.

2.8. Issue #334: Transient properties: a new approach to deep selection…

See issue 334.

3. Any other business