QT4 CG Meeting 030 Agenda 2023-04-11
Agenda
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 11 April, the following meeting is scheduled for 18 April.
Any regrets for the following meeting?
1.5. Review of open action items [6/14]
(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.[X]
QT4CG-023-01: NW to review the stylesheets for functions across XPath and XSLT- Withdrawn: it’s unclear what the issue was
[ ]
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[ ]
QT4CG-029-01: RD+DN to draft spec prose for the “divide and conquer” approach outlined in issue #399[X]
QT4CG-029-02: NW to check how Java and JavaScript behave when resolving a relative URI against a base URI that has a fragment identifier.[X]
QT4CG-029-03: NW to draft a PR that resolves issue #280[X]
QT4CG-029-04: CG to draft a PR that resolves issue #293[X]
QT4CG-029-05: NW to draft a PR that resolves issue #315[X]
QT4CG-029-06: NW to put a review of the thin arrow operator on the agenda (with links to the relevant issues)[ ]
QT4CG-029-07: NW to open the next discussion of #397 with a demo from DN
2. Technical Agenda
2.1. Review of the thin arrow operator
2.2. PR #415: Revise parse/build URI functions for UNC names
See PR #415
2.3. PR #420: Issue 357 Map composition and decomposition
See PR #420
2.4. Issue #410: Converting doubles to decimals, fractional digits
See Issue #410
2.5. Issue #369: Namespaces for Functions
See Issue #369
2.6. Issue #359: fn:void: Absorb result of evaluated argument
See Issue #359
2.7. Issue #340: fn:format-number: Specifying decimal format
See Issue #340
2.8. Issue #296: Default namespace for elements; especially in the context of HTML
See Issue #296