QT4 CG Meeting 021 Agenda 2023-02-07


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. Approve the agenda

1.3. Approve minutes of previous meeting

Minutes of the previous meeting.

1.4. Next meeting

This meeting is planned for 7 February, the following meeting is scheduled for 14 February.

Regrets for the following meeting?

1.5. Review of open action items [0/12]

(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-02: NW to add an ed-note indicating when it was approved.
  • [ ] QT4CG-016-06: RD to reword the introduction to mapping to clarify who’s doing the mapping
  • [ ] QT4CG-016-07: NW to make an issue about the problems of document-uri uniqueness
  • [ ] QT4CG-016-08: RD to clarify how namespace comparisons are performed.
  • [ ] QT4CG-016-09: RD to add a note stating that the local name should always be lowercase
  • [ ] QT4CG-016-10: RD to consider how to clarify parsed entity parsing.
  • [ ] QT4CG-019-01: MK to fix the type of $pattern in fn:tokenize()
  • [ ] QT4CG-020-01: MK to check if the default for type-variety is correct.
  • [ ] QT4CG-020-02: MK to review the description of the equal-strings function
  • [ ] QT4CG-020-03: MK to add examples using options.
  • [ ] QT4CG-020-03: MK to add an option to return false instead of raising an error

2. Technical Agenda

2.1. Issue #307, parsing and building URIs comments and queries

2.2. PR #320: Issue 98 - add options parameter to fn:deep-equal

See pull request #320. We reviewed this last week with an eye towards getting approval this week.

2.3. PR #289: Proposal to add fallback behaviour to map:get and array:get

2.4. PR #330: Update fn:parse-html to apply review feedback.

2.5. Issue #299 (formerly #281)

We had some discussion of #281 previously, but no resolution. Awaiting more feedback from the CG in the issue.

2.6. XPath 4.0 functions

2.6.1. fn:duplicate-values

2.6.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.6.10. map:entries

2.6.14. fn:split-by-graphemes

2.6.15. fn:deep-normalize-space

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

2.6.17. array:values, map:values

3. Any other business