- From: Norm Tovey-Walsh <norm@saxonica.com>
- Date: Tue, 21 Mar 2023 17:14:13 +0000
- To: public-xslt-40@w3.org
- Message-ID: <m2bkkm9gbt.fsf@saxonica.com>
Hello,
Here are the draft minutes for meeting 027:
https://qt4cg.org/meeting/minutes/2023/03-21.html
QT4 CG Meeting 027 Minutes 2023-03-21
Table of Contents
* [1]Draft Minutes
* [2]Summary of new and continuing actions [0/7]
* [3]1. Administrivia
+ [4]1.1. Roll call [8/12]
+ [5]1.2. Accept the agenda
+ [6]1.3. Approve minutes of the previous meeting
+ [7]1.4. Next meeting
+ [8]1.5. Review of open action items [3/9]
* [9]2. Technical Agenda
+ [10]2.1. PR #391: addressed typographical errors; adjusted
Unicode character discussion...
+ [11]2.2. PR #393: Clarify explanations of functions/function
items
+ [12]2.3. PR #394: Minor correction to fn:parse-uri
+ [13]2.4. PR #395: Make the (non-)hierarchical nature of URIs
explicit
+ [14]2.5. PR #396: Deep-equal, no failure when comparing
functions
+ [15]2.6. PR #400: Issue 400: ranking of type patterns
+ [16]2.7. Issue #399: Using Multilevel Hierarchy and
Abstraction...deep-equal
* [17]3. Any other business
+ [18]3.1. Issue #360: Issue 314 array composition and
decomposition
+ [19]3.2. Local union types
* [20]4. Adjourned
Draft Minutes
Summary of new and continuing actions [0/7]
* [ ] 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
* [ ] QT4CG-025-03: MK to revise and expand technical detail in PR
#375
* [ ] QT4CG-025-04: RD to remove the note in 15.5.15 of functions and
operators.
* [ ] QT4CG-026-01: MK to write a summary paper that outlines the
decisions we need to make on "value sequences"
* [ ] QT4CG-027-01: MK to update the text for next-match wrt type()
matching
1. Administrivia
1.1. Roll call [8/12]
Regrets: BTW, MSM, DN
* [ ] Anthony (Tony) Bufort (AB)
* [X] Reece Dunn (RD)
* [X] Sasha Firsov (SF)
* [X] Christian Gr¸n (CG)
* [X] Joel Kalvesmaki (JK)
* [X] Michael Kay (MK)
* [X] John Lumley (JL)
* [ ] Dimitre Novatchev (DN)
* [X] Ed Porter (EP)
* [ ] C. M. Sperberg-McQueen (MSM)
* [ ] Bethan Tovey-Walsh (BTW)
* [X] Norm Tovey-Walsh (NW). Scribe. Chair.
1.2. Accept the agenda
Proposal: Accept [21]the agenda.
Accepted.
1.3. Approve minutes of the previous meeting
Proposal: Accept [22]the minutes of the previous meeting.
Accepted.
1.4. Next meeting
The next meeting [23]is scheduled for Tuesday, 28 March 2023.
ATTENTION: This meeting is scheduled at 16:00 local time in Europe and
the UK. The United States switched to Daylight Saving Time starting on
Sunday, 12 March 2023. Europe and the UK will switch to summer time on
26 March 2023. This meeting will return to its "usual" time, one hour
earlier than last week in the United States.
No regrets heard.
1.5. Review of open action items [3/9]
* [ ] 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
* [X] QT4CG-024-01: MK to add namespace-uri-for-prefix argument
changes to the compatibility appendix
* [X] QT4CG-024-02: DN to develop an alternative proposal for
deep-action.
* [X] QT4CG-025-02: MK to make the context function properties simple
values instead of functions
* [ ] QT4CG-025-03: MK to revise and expand technical detail in PR
#375
* [ ] QT4CG-025-04: RD to remove the note in 15.5.15 of functions and
operators.
* [ ] QT4CG-026-01: MK to write a summary paper that outlines the
decisions we need to make on "value sequences"
2. Technical Agenda
2.1. PR #391: addressed typographical errors; adjusted Unicode character
discussion...
See PR [24]pull request #391
* Some discussion of the naunces of the U+four-leading-digits
convention.
* JK may try to improve the consistency; would CSS styles for Oxygen
be useful?
* MK please make sure you don't use an editor that changes
whitespace!
Proposal: Accept this PR.
Accepted.
2.2. PR #393: Clarify explanations of functions/function items
See PR [25]pull request #393
* MK walks us through the PR; this is editorial in that it makes no
changes to grammar or implementation but does make broad changes to
the prose of the spec.
+ ... Changed data model to use "function items" instead of
"functions" because you need the distinction.
* RD: Is also consistent with map items and array items.
* MK: Changes the title of the section and explains why
+ ... Changed "implementation" to "body"
* MK: Next let's look at XQuery:
+ ... Added a discussion of categories of functions
(application, system, or external functions) and the
distinctions between them.
+ ... Context dependence is different in the three cases
* RD: This lays the groundwork for external framework bindings.
* MK: I'm not suggesting we do that, but yes, it's a start.
+ ... Rewrote the section on partial function application to
give separate sets of rules for static and dynamic calls.
Bundling it into a single set of rules had become too complex.
o ... And that's about it.
Proposal: Accept this PR.
Accepted.
2.3. PR #394: Minor correction to fn:parse-uri
See PR [26]pull request #394
* NW: This is almost too trivial for review. Basically, if you omit
the "/", the rest of the algorithm fails.
Proposal: Accept this PR.
Accepted.
2.4. PR #395: Make the (non-)hierarchical nature of URIs explicit
See PR [27]pull request #395
* NW: This one is a little more interesting. Basically, the functions
fn:parse-uri and fn:build-uri should be reversible. If the parse
function doesn't record whether or not it treated the URI as a
hierarchical URI or not, then it's not always possible for the
build function to do the right thing.
* MK: What about the question of file URIs and UNC names?
* NW: That'll be in my next PR, I wanted to clear these so I didn't
have too big a merge tangle.
* RD: The WHAT WG has notes about file URIs too.
* NW: Thanks. I'll look at that too.
Proposal: Accept this PR.
Accepted.
2.5. PR #396: Deep-equal, no failure when comparing functions
See PR [28]pull request #396
* NW: I propose we wait until DN is present.
General agreement.
2.6. PR #400: Issue 400: ranking of type patterns
See PR [29]pull request #400
* MK: This is mostly about XSLT, but I found some bugs in the pattern
grammar
+ ... Added type type() keyword to wrap a type. That was already
in the proposal.
+ ... What's new is what we do about priorities.
o ... Import precedence first
o ... Priority next
# ... All type patterns have the same priority (0)
o ... Type patterns are distinguished according to the type
hierarchy
# ... Discard supertypes (because you have a more
specific one)
# ... With special rules for predicates (predicates
win)
# ... If you're left with a single rule, that's it,
otherwise do the same thing you would for any other
case of duplicate matching templates.
* JL: I assume next-match will allow you to go to a less specific
one?
* MK: Yes, I don't think the rules don't have to change.
ACTION QT4CG-027-01: MK to update the text for next-match wrt type()
matching
Proposal: Accept this PR.
Accepted.
2.7. Issue #399: Using Multilevel Hierarchy and Abstraction...deep-equal
See [30]issue #399
* NW: I propose we wait until DN is present.
General agreement again.
3. Any other business
* NW: Apologies, I've let the agenda run a bit short this week. Shall
we pick some more items?
* RD: Could we look at local union types and some things like that?
* MK: Yes, we could do. Looking at the PRs, #368 has open actions,
but we could do #360.
Agreement to look at #360.
3.1. Issue #360: Issue 314 array composition and decomposition
See [31]issue #360
* MK: Balisage paper from last year
+ ... This is about doing navigation across arrays and maps
+ ... I started with an abstraction the "parcel", but I've moved
to a concrete representation
+ ... Let's review...
o ... Splits maps and arrays into two sections for
editorial convenience
o (Abandonning the diff version; too much text moved
around)
o ... Looking at 19 Arrays
# ... New functions available to users, array:members
and array:of
# ... A value record is a map with a single key
"value"
# ... Looking at he specification for those functions,
starting at array:members
# ... What's interesting his how it's used. Need more
use cases.
* RD: Do we have a corresponding proposal for map:members and map:of?
* MK: Not yet, but my plan is to do that next.
+ ... The problem with map is what we already have map:entries
and that's not precisely what I'd like. Would be better if it
returned a map with two keys.
* RD: With this proposal you could potentially do
array:of(map:members(...))
* MK: Yes.
Touching briefly on provenance, and agreeing to keep it separate.
* MK: The other primitives you need are how to get back. You can use
"?" and just map('value':.)
+ ... We could provide syntactic sugar, but this seems managable
* ML: What's interesting is that these new functions get used in the
description of many of the other functions, for example
array:insert-before()
* CG: Could we possibly have an atomization of the array records?
+ ... You can use them as input for arbitrary functions an you
would get them to the right type.
* MK: I think the problem is if what I've called value records were a
new data type, then we could certainly say atomization works on it.
Or that it was implicitly coerced to an array. Because I've tried
to make it a concrete reuse of maps, it's harder to give it any
special magic behavior. There's a tradeoff.
* JL: There are no implications if I chose to use a map with a value
key, that wouldn't be special would it?
* MK: No.
Proposal: Accept this PR.
Accepted.
3.2. Local union types
* RD: Local union types were added before the CG started. I was going
to suggest we look at that.
* MK: Let's look at 3.6.2.1 in XQuery
+ ... The proposal is that the semantics are based on XSD union
types. It has to be atomic types or union types.
+ ... But the grammar just says ItemType, probably so you can
put an enum in. We could restrict it to a type name so you
have to name the enumerated type.
* RD: Or we could introduce a local element union type that's an
atomic type or an enum type.
* MK: Yes, that would possibly work.
MK reviews the semantics
* MK: The subsumption rules are defined, but they're the same as XSD.
+ ... It's really just a way of saying that you can use a union
type just like it was in a scheme, but you don't have to write
a schema to do it.
4. Adjourned
References
1. https://qt4cg.org/meeting/minutes/2023/03-21.html#minutes
2. https://qt4cg.org/meeting/minutes/2023/03-21.html#new-actions
3. https://qt4cg.org/meeting/minutes/2023/03-21.html#administrivia
4. https://qt4cg.org/meeting/minutes/2023/03-21.html#roll-call
5. https://qt4cg.org/meeting/minutes/2023/03-21.html#agenda
6. https://qt4cg.org/meeting/minutes/2023/03-21.html#approve-minutes
7. https://qt4cg.org/meeting/minutes/2023/03-21.html#next-meeting
8. https://qt4cg.org/meeting/minutes/2023/03-21.html#open-actions
9. https://qt4cg.org/meeting/minutes/2023/03-21.html#technical-agenda
10. https://qt4cg.org/meeting/minutes/2023/03-21.html#pr-391
11. https://qt4cg.org/meeting/minutes/2023/03-21.html#pr-393
12. https://qt4cg.org/meeting/minutes/2023/03-21.html#pr-394
13. https://qt4cg.org/meeting/minutes/2023/03-21.html#pr-395
14. https://qt4cg.org/meeting/minutes/2023/03-21.html#pr-396
15. https://qt4cg.org/meeting/minutes/2023/03-21.html#pr-400
16. https://qt4cg.org/meeting/minutes/2023/03-21.html#iss-399
17. https://qt4cg.org/meeting/minutes/2023/03-21.html#aob
18. https://qt4cg.org/meeting/minutes/2023/03-21.html#pr-360
19. https://qt4cg.org/meeting/minutes/2023/03-21.html#h-82D9098A-13BA-48D2-86FC-76591E041F8B
20. https://qt4cg.org/meeting/minutes/2023/03-21.html#adjourned
21. https://qt4cg.org/meeting/agenda/2023/03-21.html
22. https://qt4cg.org/meeting/minutes/2023/03-14.html
23. https://qt4cg.org/meeting/agenda/2023/03-28.html
24. https://qt4cg.org/dashboard/#pr-391
25. https://qt4cg.org/dashboard/#pr-393
26. https://qt4cg.org/dashboard/#pr-394
27. https://qt4cg.org/dashboard/#pr-395
28. https://qt4cg.org/dashboard/#pr-396
29. https://qt4cg.org/dashboard/#pr-400
30. https://qt4cg.org/dashboard/#pr-399
31. https://qt4cg.org/dashboard/#pr-360
Be seeing you,
norm
--
Norm Tovey-Walsh
Saxonica
Received on Tuesday, 21 March 2023 17:15:20 UTC