QT4 CG Meeting 031 Agenda 2023-04-18


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 18 April, the following meeting is scheduled for 25 April.

Any regrets for the following meeting?

1.5. Review of open action items [4/10]

(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
    • Stylesheets for formatting functions in F&O and XSLT are out-of-sync
    • We’re not handling default values for parameters on the XSLT side
  • [X] 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”
    • This is related to PR #368: Issue 129 - Context item generalized to context value and subsequent discussion.
  • [X] QT4CG-027-01: MK to update the text for next-match wrt type() matching
  • [X] 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
  • [ ] QT4CG-029-07: NW to open the next discussion of #397 with a demo from DN
  • [X] QT4CG-030-01: RD to create issues that identify more clearly the various aspects of !, =>, ->, and inline function definitions.

2. Technical Agenda

This week’s agenda mostly continues where we left off last week.

2.1. Issue #53: Allow function keyword inline functions without parameters

See Issue #53

There has been a lot of discussion on this issue in the past few days. I propose that we have a time-boxed discussion for at most 15 minutes or so to see if that will help us get more quickly to a resolution.

2.2. PR #420: Issue 357 Map composition and decomposition

See PR #420

2.3. Issue #410: Converting doubles to decimals, fractional digits

See Issue #410

2.4. Issue #369: Namespaces for Functions

See Issue #369

2.5. Issue #359: fn:void: Absorb result of evaluated argument

See Issue #359

2.6. Issue #340: fn:format-number: Specifying decimal format

See Issue #340

2.7. Issue #296: Default namespace for elements; especially in the context of HTML

See Issue #296

2.8. PR #375: Context for default parameter values

See PR #375

2.9. PR #433: Allow hex and binary literals and allow underscores

See PR #433

2.10. PR #434: Functions to parse and format hex integers

See PR #434

3. Any other business