QT4 CG Meeting 051 Agenda 2023-10-24
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.
ATTENTION: Europe and the United Kingdom switch from daylight saving time to standard time on Sunday, October 29, 2023. The meeting on Tuesday, 31 October 2023, will occur one hour earlier in The United States.
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 24 October, the following meeting is scheduled for 31 October.
Any regrets for the following meeting?
1.5. Review of open action items [2/7]
(Items marked [X] are believed to have been closed via email before this agenda was posted.)
[ ]
QT4CG-046-01: MK to continue the work on #129 for the other specs (we accepted #703)[X]
QT4CG-046-04: CG to flesh out changes related to annotations in other parts of the specs[X]
QT4CG-046-05: NW to updated parse-uri to use decode-from-uri (issue #566)[ ]
QT4CG-048-02: MK to clean up the proposal for adding @as to xsl:sequence and elsewhere[ ]
QT4CG-050-02: MP to attempt to summarize this discussion and identify specific issues[ ]
QT4CG-050-01: MK to revise #749 to retain only the editorial parts.[ ]
QT4CG-050-03: MK to make the proposed editorial improvements to PR #659
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 #538: 480: Attempt to allow xs:string to be 'promoted to' xs:anyURI
1.6.2. Merge without discussion
The following PRs are editorial, small, or otherwise appeared to be uncontroversial when the agenda was prepared. The chairs propose that these can be merged without discussion. If you think discussion is necessary, please say so.
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 #383: fn:deep-equal: Order of child elements (unordered-elements)
1.6.4. XSLT focused
The following PRs appear to be candidates for a future XSLT-focussed meeting.
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.
1.6.5. Substantive PRs
The following substantive PRs were open when this agenda was prepared.
- PR #761: 554/754 Simplify the new transitive-closure function
- PR #753: 65: Allow xmlns="xxx" to NOT change the default namespace for NameTests
- PR #737: 295: Boost the capability of recursive record types
- PR #736: 730: Clarify (and correct) rules for maps as instances of function types
- PR #734: 517: fn:chain
- PR #719: 413: Spec for CSV-related functions
- PR #635: 451: Schema compatibility
- PR #529: 528: revision of json(), and renaming to elements-to-maps()
1.6.6. Proposed for V4.0
The following issues are labled “proposed for V4.0”.
- Issue #716: Generators in XPath
- Issue #479: fn:deep-equal: Input order
- 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 #31: Extend FLWOR expressions to maps
2. Technical Agenda
2.1. Issue 129: Context item → Context value?
See issue #129: does this need to remain open? Can we create actions for the unresolved edits instead?
2.2. Issue 238: Support Invisible XML
See issue #238: time boxed discussion to see if the group wants to do this.
2.3. PR #635: 451: Schema compatibility
See PR #635.
2.4. PR #734: 517: fn:chain
See #734.
2.5. PR #761: 554/754 Simplify the new transitive-closure function
See #761.
2.6. PR #753: 65: Allow xmlns="xxx" to NOT change the default namespace for NameTests
See #753.
2.7. PR #737: 295: Boost the capability of recursive record types
See #737.
2.8. PR #736: 730: Clarify (and correct) rules for maps as instances
See #736.