QT4 CG Agenda 029, 4 April 2023

Hi folks,

Here’s a draft agenda for next Tuesday:

  https://qt4cg.org/meeting/agenda/2023/04-04.html

QT4 CG Meeting 029 Agenda 2023-04-04

Agenda

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

   See the [1]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 [2]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

   See [3]issue #411

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

   See [4]issue #399

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

   See [5]issue 280.

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

   See [6]issue 293.

2.5. Issue #300: Ambiguity regarding Unicode normalization (editorial)

   See [7]issue 300.

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

   See [8]issue 315.

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

   See [9]issue 367.

2.8. Issue #397: Type names

   See [10]issue 397.

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

   See [11]issue 334.

3. Any other business

References

   1. https://qt4cg.org/meeting/logistics.html
   2. https://qt4cg.org/meeting/minutes/2023/03-28.html
   3. https://qt4cg.org/dashboard/#pr-411
   4. https://github.com/qt4cg/qtspecs/issues/399
   5. https://github.com/qt4cg/qtspecs/issues/280
   6. https://github.com/qt4cg/qtspecs/issues/293
   7. https://github.com/qt4cg/qtspecs/issues/300
   8. https://github.com/qt4cg/qtspecs/issues/315
   9. https://github.com/qt4cg/qtspecs/issues/367
  10. https://github.com/qt4cg/qtspecs/issues/397
  11. https://github.com/qt4cg/qtspecs/issues/334

                                        Be seeing you,
                                          norm

--
Norm Tovey-Walsh
Saxonica