QT4 CG Meeting 039 Agenda 2023-06-20

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


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 20 June, the following meeting is scheduled for 27 June.

Any regrets for the following meeting?

The CG will take a vacation for four weeks in August. We will not meet on 1, 8, 15, or 22 August.

1.5. Review of open action items [1/8]

(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-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-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 See PR #449
  • [ ] QT4CG-035-01: CG to make a few more (slightly more complex) map:keys examples.
  • [ ] QT4CG-035-02: CG to fix the type signature and examples in map:filter.
  • [X] QT4CG-038-01: NW to attempt to craft some sort of proposal for dealing with stale issues.

1.6. Review of open pull requests and issues

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

  • PR #538: Attempt to allow xs:string to be 'promoted to' xs:anyURI
  • PR #491: Fix more examples in the FO 4.0 spec
  • PR #368: 129: Context item generalized to context value

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

  • PR #533: 413: Spec for CSV parsing with fn:parse-csv()
  • PR #529: 528: revision of json(), and renaming to xdm-to-json()
  • PR #547: Action QT4CG-036-02: Further elaboration of the rules for function identity
  • PR #546: Attempt to implement expanding the allowed character repertoire
  • PR #555: Revised narrative of normalization steps for serialization

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

  • PR #549: 526 load xquery module
  • PR #552: Editorial: Updates to back matter and status section of F+O spec
  • PR #551: Drop the fn:differences function
  • PR #550: 548: require parens around lambda arguments

Added by amendment:

  • PR #558 Added fn:items-X cross-references
  • PR #559 Minor editorial edits

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

  • Iss #425: Structural proposal (ThinLayer™️) : Add a layer of thin spec between XPath and the XPath Derived Language
  • Iss #399: fn:deep-equal: Using Multilevel Hierarchy and Abstraction when designing and specifying complex functions
  • Iss #376: add documentation prefix attribute to xsl:stylesheet
  • Iss #331: Extend fn:path to support arrays and maps.
  • Iss #112: Abbreviate map:function($someMap) to $someMap?function()
  • Iss #82: Should the mode attribute for apply-templates in templates of enclosed modes default to #current?
  • Iss #52: Allow record(*) based RecordTests

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

  • PR #470: 369 add fixed-prefixes attribute in XSLT
  • PR #412: 409, QT4CG-027-01: xsl:next-match

2. Technical Agenda

This week’s focus is on two large PRs related to CSV and JSON. We expect Matt Patterson to join us for the CSV discussions.

2.1. PR #533: 413: Spec for CSV parsing with fn:parse-csv()

See PR #533

2.2. PR #529: 528: revision of json(), and renaming to xdm-to-json()

See PR #529

3. Any other business