QT4 CG Meeting 045 Agenda 2023-09-12

Agenda index / QT4CG.org / Dashboard / GH Issues / GH Pull Requests

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 12 September, the following meeting is scheduled for 19 September.

Any regrets for the following meeting?

Proposal: the meeting of 26 September will focus on XSLT issues.

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

(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-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.
  • [ ] QT4CG-029-07: NW to open the next discussion of #397 with a demo from DN See PR #449
  • [ ] QT4CG-039-01: NW to schedule discussion of issue #52, Allow record(*) based RecordTests
  • [ ] QT4CG-042-01: NW to use sequences instead of arrays in parse-uri output.
  • [ ] QT4CG-042-02: NW to make the query into a simple map with repeated values.
  • [ ] QT4CG-042-03: NW to consider revisions to query parses.

1.6. Review of open pull requests and issues

1.6.1. Blocked

The following PRs are open but have merge conflicts or comments which suggest they aren’t ready for action.

  • PR #635: 451: Schema compatibility
  • PR #538: Attempt to allow xs:string to be 'promoted to' xs:anyURI
  • PR #529: 528: revision of json(), and renaming to xdm-to-json()
  • PR #470: 369 add fixed-prefixes attribute in XSLT
  • PR #412: 409, QT4CG-027-01: xsl:next-match
  • PR #368: 129: Context item generalized to context value

1.6.2. Merge without discussion

The following PRs were discussed last week and identified as “merge next week” if there have been no comments to the contrary.

  • PR #631: 600: fn:decode-from-uri
  • PR #623: 93: sort descending
  • PR #599: 90: Simplified stylesheets with no xsl:version

The following editorial or otherwise minor PRs were open when this agenda was prepared. The chairs propose that these can be merged without discussion. If you think discussion is necessary, please say so.

  • PR #682: 637: allow true() and false() as function annotation values
  • PR #681: 665: Fix typos in fn:items-XX functions
  • PR #679: 669 - fix typo "appearing appearing"
  • PR #678: 671 switch sans operand
  • PR #672: XFO minor edits, chap. 1

1.6.3. Close without action

It has been proposed that the following issues be closed without action. If you think discussion is necessary, please say so.

  • Issue #160: Support named arguments on dynamic function calls

1.6.4. XSLT focused

The following PRs appear to be candidates for a future XSLT-focussed meeting.

  • PR #674: 663: Describe how calls to xsl:original with keywords work
  • PR #650: 649: fix an xsl:fallback problem

(And also #470 and #412 from the “blocked” list above.)

These issues identify the XSLT-focused changes that have been made to the specifications but which have not been established by the community group as the status quo.

  • Issue #571: XSLT: xsl:for-each-group/@break-when
  • Issue #233: Declare the result type of a mode, via @as
  • Issue #172: Record Tests Feature
  • Issue #169: Handling of duplicate keys in xsl:map Enhancement
  • Issue #168: XSLT Extension Instructions invoking Named Templates

1.6.5. Substantive PRs

The following substantive PRs were open when this agenda was prepared.

  • PR #691: 688 Semantics of local union types, enumeration types, etc
  • PR #690: 687 Clarify constructor functions for user-defined types
  • PR #680: 668 define case insensitive collation normatively
  • PR #673: HTML namespace changes
  • PR #659: 647: schema location hints

1.6.6. Requires confirmation

These issues identify changes that have been made to the specifications but which have not been established by the community group as the status quo.

  • Issue #372: Separate default namespace for elements from the default namespace for types
  • Issue #283: Enumeration types

1.6.7. Proposed for V4.0

The following issues are labled “proposed for V4.0”.

  • Issue #479: fn:deep-equal: Input order
  • Issue #359: fn:void: Absorb result of evaluated argument
  • Issue #340: fn:format-number: Specifying decimal format
  • Issue #260: array:index-of
  • Issue #238: Support Invisible XML
  • Issue #130: New super/union type xs:binary?
  • Issue #129: Context item → Context value?
  • Issue #36: Allow support for user-defined annotations.

2. Technical Agenda

2.1. PRs

Try to resolve as many of these PRs as we can, leaving 20 minutes to discuss issues.

2.1.1. PR #691: 688 Semantics of local union types, enumeration types, etc

2.1.2. PR #690: 687 Clarify constructor functions for user-defined types

2.1.3. PR #673: HTML namespace changes

2.1.4. PR #680: 668 define case insensitive collation normatively

2.1.5. PR #659: 647: schema location hints

2.2. Issues

CG offered to update us on issue #129. Then review of issues that “require confirmation”.

2.2.1. Issue #129: Context item → Context value?

2.2.2. Issue #372: Separate default namespace for elements from the default namespace for types

2.2.3. Issue #283: Enumeration types

3. Any other business