- From: Norm Tovey-Walsh <norm@saxonica.com>
- Date: Mon, 11 Sep 2023 12:15:43 +0100
- To: public-xslt-40@w3.org
- Message-ID: <m24jk12c15.fsf@saxonica.com>
Hello,
The proposed agenda for tomorrow’s QT4 CG meeting is available:
https://qt4cg.org/meeting/agenda/2023/09-12.html
It’s a little long and complicated. Attempting to implement what we
discussed last week, after reviewing what’s open, there are a few PRs to
discuss and then a few issues.
Here’s a text copy:
QT4 CG Meeting 045 Agenda 2023-09-12
[1]Agenda index / [2]QT4CG.org / [3]Dashboard / [4]GH Issues / [5]GH
Pull Requests
Agenda
This meeting will be hosted on Zoom at 16:00BST (17:00CEST, 11:00EDT,
08:00PDT).
See the [6]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 [7]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 [8]#449
* [ ] QT4CG-039-01: NW to schedule discussion of issue [9]#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 [10]#635: 451: Schema compatibility
* PR [11]#538: Attempt to allow xs:string to be 'promoted to'
xs:anyURI
* PR [12]#529: 528: revision of json(), and renaming to xdm-to-json()
* PR [13]#470: 369 add fixed-prefixes attribute in XSLT
* PR [14]#412: 409, QT4CG-027-01: xsl:next-match
* PR [15]#368: 129: Context item generalized to context value
1.6.2. Merge without discussion
The following PRs were discussed [16]last week and identified as "merge
next week" if there have been no comments to the contrary.
* PR [17]#631: 600: fn:decode-from-uri
* PR [18]#623: 93: sort descending
* PR [19]#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 [20]#682: 637: allow true() and false() as function annotation
values
* PR [21]#681: 665: Fix typos in fn:items-XX functions
* PR [22]#679: 669 - fix typo "appearing appearing"
* PR [23]#678: 671 switch sans operand
* PR [24]#672: XFO minor edits, chap. 1
1.6.3. Close without action
It has been proposed that the following issues be [25]closed without
action. If you think discussion is necessary, please say so.
* Issue [26]#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 [27]#674: 663: Describe how calls to xsl:original with keywords
work
* PR [28]#650: 649: fix an xsl:fallback problem
(And also [29]#470 and [30]#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 [31]#571: XSLT: xsl:for-each-group/@break-when
* Issue [32]#233: Declare the result type of a mode, via @as
* Issue [33]#172: Record Tests Feature
* Issue [34]#169: Handling of duplicate keys in xsl:map Enhancement
* Issue [35]#168: XSLT Extension Instructions invoking Named
Templates
1.6.5. Substantive PRs
The following substantive PRs were open when this agenda was prepared.
* PR [36]#691: 688 Semantics of local union types, enumeration types,
etc
* PR [37]#690: 687 Clarify constructor functions for user-defined
types
* PR [38]#680: 668 define case insensitive collation normatively
* PR [39]#673: HTML namespace changes
* PR [40]#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 [41]#372: Separate default namespace for elements from the
default namespace for types
* Issue [42]#283: Enumeration types
1.6.7. Proposed for V4.0
The following issues are labled "proposed for V4.0".
* Issue [43]#479: fn:deep-equal: Input order
* Issue [44]#359: fn:void: Absorb result of evaluated argument
* Issue [45]#340: fn:format-number: Specifying decimal format
* Issue [46]#260: array:index-of
* Issue [47]#238: Support Invisible XML
* Issue [48]#130: New super/union type xs:binary?
* Issue [49]#129: Context item -> Context value?
* Issue [50]#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
References
1. https://qt4cg.org/meeting/agenda/
2. https://qt4cg.org/
3. https://qt4cg.org/dashboard
4. https://github.com/qt4cg/qtspecs/issues
5. https://github.com/qt4cg/qtspecs/pulls
6. https://qt4cg.org/meeting/logistics.html
7. https://qt4cg.org/meeting/minutes/2023/09-05.html
8. https://qt4cg.org/dashboard/#pr-449
9. https://github.com/qt4cg/qtspecs/issues/52
10. https://github.com/qt4cg/qtspecs/pull/635
11. https://github.com/qt4cg/qtspecs/pull/538
12. https://github.com/qt4cg/qtspecs/pull/529
13. https://github.com/qt4cg/qtspecs/pull/470
14. https://github.com/qt4cg/qtspecs/pull/412
15. https://github.com/qt4cg/qtspecs/pull/368
16. https://qt4cg.org/meeting/minutes/2023/09-05.html#open-prs
17. https://github.com/qt4cg/qtspecs/pull/631
18. https://github.com/qt4cg/qtspecs/pull/623
19. https://qt4cg.org/dashboard/#pr-599
20. https://github.com/qt4cg/qtspecs/pull/682
21. https://github.com/qt4cg/qtspecs/pull/681
22. https://github.com/qt4cg/qtspecs/pull/679
23. https://github.com/qt4cg/qtspecs/pull/678
24. https://github.com/qt4cg/qtspecs/pull/672
25. https://github.com/qt4cg/qtspecs/labels/Propose%20Closing%20with%20No%20Action
26. https://github.com/qt4cg/qtspecs/issues/160
27. https://github.com/qt4cg/qtspecs/pull/674
28. https://github.com/qt4cg/qtspecs/pull/650
29. https://github.com/qt4cg/qtspecs/pull/470
30. https://github.com/qt4cg/qtspecs/pull/412
31. https://github.com/qt4cg/qtspecs/issues/571
32. https://github.com/qt4cg/qtspecs/issues/233
33. https://github.com/qt4cg/qtspecs/issues/172
34. https://github.com/qt4cg/qtspecs/issues/169
35. https://github.com/qt4cg/qtspecs/issues/168
36. https://qt4cg.org/dashboard/#pr-691
37. https://qt4cg.org/dashboard/#pr-690
38. https://qt4cg.org/dashboard/#pr-680
39. https://qt4cg.org/dashboard/#pr-673
40. https://qt4cg.org/dashboard/#pr-659
41. https://github.com/qt4cg/qtspecs/issues/372
42. https://github.com/qt4cg/qtspecs/issues/283
43. https://github.com/qt4cg/qtspecs/issues/479
44. https://github.com/qt4cg/qtspecs/issues/359
45. https://github.com/qt4cg/qtspecs/issues/340
46. https://github.com/qt4cg/qtspecs/issues/260
47. https://github.com/qt4cg/qtspecs/issues/238
48. https://github.com/qt4cg/qtspecs/issues/130
49. https://github.com/qt4cg/qtspecs/issues/129
50. https://github.com/qt4cg/qtspecs/issues/36
Be seeing you,
norm
--
Norm Tovey-Walsh
Saxonica
Received on Monday, 11 September 2023 11:18:58 UTC