QT4CG Minutes 048 (XSLT-focused), 3 October 2023

Hello,

Here are the minutes from yesterday’s call. My thanks to MSM for chairing
and JL for scribing! I’m on the mend and expect to be back to normal for
next week. 

  https://qt4cg.org/meeting/minutes/2023/10-03.html

QT4 CG Meeting 048 Minutes 2023-10-03

Table of Contents

     * [1]Draft Minutes
     * [2]Summary of new and continuing actions [0/12]
          + [3]Agenda: Approved
          + [4]Last minutes: Approved
          + [5]Next meeting: 10 October 2023
          + [6]Regrets: JL (and 17th)
          + [7]Roll call
          + [8]1.5. Review of open action items
          + [9]1.6. Review of open pull requests and issues related to
            XSLT
               o [10]1.6.1. Blocked
               o [11]1.6.2. XSLT-related issues
          + [12]Issue #233: Declare the result type of a mode, via @as
          + [13]Issue #172: Record Tests Feature
     * [14]Adjourned at 1659

   [15]Agenda index / [16]QT4CG.org / [17]Dashboard / [18]GH Issues /
   [19]GH Pull Requests

Draft Minutes

   (Lightly edited by NW to simplify publication.)

Summary of new and continuing actions [0/12]

     * [ ] QT4CG-029-07: NW to open the next discussion of #397 with a
       demo from DN
          + See PR [20]#449. Discussion planned for meeting 049, 10
            October 2023.
     * [ ] QT4CG-045-02: RD to address comments on HTML namespaces in
       another PR
     * [ ] QT4CG-046-01: MK to continue the work on #129 for the other
       specs (we accepted #703)
     * [ ] QT4CG-046-02: RD to draft the specification changes to allow
       record(*)
     * [ ] QT4CG-046-03: MK to roll back the changes related to default
       namespaces for elments and types (issue #372)
     * [ ] QT4CG-046-04: CG to flesh out changes related to annotations in
       other parts of the specs
     * [ ] QT4CG-046-05: NW to updated parse-uri to use decode-from-uri
       (issue #566)
     * [ ] QT4CG-047-01: MK to make a PR that renames break-when to
       split-when
     * [ ] QT4CG-048-01: MK - to identify what happens with the mode
       default rule behaviours.
     * [ ] QT4CG-048-02: MK to clean up the proposal for adding @as to
       xsl:sequence and elsewhere
     * [ ] QT4CG-048-03: MK 5.4. - the section on type patterns - replace
       3rd paragraph - belongs with predicate patterns. Fix cut-and-paste
       issues.
     * [ ] QT4CG-048-04: MK to use xs: prefix

Agenda: Approved

Last minutes: Approved

Next meeting: 10 October 2023

Regrets: JL (and 17th)

Roll call

   Regrets NW.
     * [X] Reece Dunn (RD)
     * [X] Sasha Firsov (SF)
     * [ ] Christian Gr¸n (CG)
     * [X] Joel Kalvesmaki (JK)
     * [X] Michael Kay (MK)
     * [X] John Lumley (JL) Scribe.
     * [X] Dimitre Novatchev (DN)
     * [X] Wendell Piez (WP)
     * [X] Ed Porter (EP)
     * [X] C. M. Sperberg-McQueen (MSM). Chair
     * [ ] Norm Tovey-Walsh (NW).

1.5. Review of open action items

     * [ ] QT4CG-029-07: NW to open the next discussion of #397 with a
       demo from DN

   See PR #449. Discussion planned for meeting 048, 3 October 2023.
     * [ ] QT4CG-045-02: RD to address comments on HTML namespaces in
       another PR Still working on it
     * [ ] QT4CG-046-01: MK to continue the work on #129 for the other
       specs (we accepted #703) Pending
     * [ ] QT4CG-046-02: RD to draft the specification changes to allow
       record(*) Still working on it. MK thought he'd raised a PR on this
       one.
     * [ ] QT4CG-046-03: MK to roll back the changes related to default
       namespaces for elments and types (issue #372) PR raised on this one
       - pending
     * [ ] QT4CG-046-04: CG to flesh out changes related to annotations in
       other parts of the specs
     * [ ] QT4CG-046-05: NW to updated parse-uri to use decode-from-uri
       (issue #566)
     * [ ] QT4CG-047-01: MK to make a PR that renames break-when to
       split-when Pending

1.6. Review of open pull requests and issues related to XSLT

1.6.1. Blocked

   The following PRs are open but have merge conflicts or comments which
   suggest they aren't ready for action.
     * PR #650: 649: fix an xsl:fallback problem
     * PR #470: 369 add fixed-prefixes attribute in XSLT
     * PR #412: 409, QT4CG-027-01: xsl:next-match

   MK: lots problems with GIT useage to solve the blocking. Maybe
   associated with authentication. Talk to NW when he's well.

1.6.2. XSLT-related issues

   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 #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

   MK: These are in the spec but not realy discussion, so need to decide
   their fate. Has tackled a few by raising PRs. Others on the agenda

Issue #233: Declare the result type of a mode, via @as

     * MK: This is required more as a mode in 3.0+ introduces the distinct
       possibility that templates in a mode might be returning
       functions,maps, arrays, etc. This can be declared as a default for
       the templates within a mode,
     * JL: It this a default or a constraint on consistency of the return
       type from anything in the mode.
     * MK: Both
     * DN: Should this be mandatory? Perhaps a bit restrictive - what
       about internal templates (not accessed from outside)?
     * MSM: The subtyping rule for the @as. In some cases the mode might
       produce T1 and others T2. Use different modes, or a union type
     * MK: Or don't use the feature. You might find yourself using more
       modes than normal.
     * DN: I would find it too restrictive.
     * MK: The driving use case was a schema-validator written in XSLT
       that use maps (records) VERY heavily. Every template rule in a mode
       had the same @as.
     * JK: Note that the question I posed has now been resolved. Add a
       note suggesting feature designed for homogenous modes.
     * JL: Very much in favour, especially with enclosed modes.
     * WP: May be difficult if you're working with multiple mode
       templates.
     * MSM: Homegeneity - useful if the mapping is of type T to type T,
       but perhaps less so for types X,Y,Z to type T, but with homogeneous
       cases it very much increases type checking.
     * MK: Result type of a mode DOES invoked coercion, so e.g.
       @as="string" would invoke stringification (if permitted) or
       results.
     * JL: Built-in actions (e.g. shallow-copy) - does it affect them.

   ACTION QT4CG-048-01: MK - to identify what happens with the mode
   default rule behaviours.
     * MK: It can also add compile-time checking of xsl:apply-templates.
     * MSM: Add @as to apply-templates?
     * MK: There is a proposal to add @as to xsl:sequence and others.
       Needs some more mulling other

   Implicit general approval for letting this be status quo.

   ACTION QT4CG-048-02: MK to clean up the proposal for adding @as to
   xsl:sequence and elsewhere

Issue #172: Record Tests Feature

     * MK: Given record type is accepted, but we need to look in some more
       detail. It is not just relevant to XSLT.
     * RD: I don't think we've discussed record matching in XSMLT match
       patterns.
     * JK: Record constructors in XSLT?
     * MK: No proposals at present.
     * MSM: Given not just XSLT - I would like to bring this back in a
       future meeting.
     * MK: It should be in the XSLT spec section on patterns. In type
       patterns particular.

   ACTION QT4CG-048-03: MK 5.4. - the section on type patterns - replace
   3rd paragraph - belongs with predicate patterns. Fix cut-and-paste
   issues.
     * MSM: Can we use ComplexItemType in these patterns
     * MK: No - they are not an ItemType.

   Some discussion on the WrappedItemType (type(....)) and short forms.

   ACTION QT4CG-048-04: MK to use xs: prefix

   Agreed it should be accepted for XSLT.

Adjourned at 1659

References

   1. https://qt4cg.org/meeting/minutes/2023/10-03.html#minutes
   2. https://qt4cg.org/meeting/minutes/2023/10-03.html#new-actions
   3. https://qt4cg.org/meeting/minutes/2023/10-03.html#h-670FE983-0B70-4E61-912F-640F6F9830CD
   4. https://qt4cg.org/meeting/minutes/2023/10-03.html#h-3D2855AE-D0B5-470C-B650-EFB72A83FB1E
   5. https://qt4cg.org/meeting/minutes/2023/10-03.html#h-6CF9B8F6-70C2-42E8-8418-1EC0251213CD
   6. https://qt4cg.org/meeting/minutes/2023/10-03.html#h-39B170D3-7C85-4C88-A847-A30410985E7C
   7. https://qt4cg.org/meeting/minutes/2023/10-03.html#h-121CF876-BD2D-4D62-820F-7B933315BDCF
   8. https://qt4cg.org/meeting/minutes/2023/10-03.html#h-550A2EB4-306A-482C-9F88-68B6D0498D29
   9. https://qt4cg.org/meeting/minutes/2023/10-03.html#h-87C4C4BD-D307-4203-928B-8B74B58B0574
  10. https://qt4cg.org/meeting/minutes/2023/10-03.html#h-1B6E9807-A2EF-4832-B996-F110FFB6818F
  11. https://qt4cg.org/meeting/minutes/2023/10-03.html#h-3707E401-2FAB-4041-AD8E-57D638ECEEDF
  12. https://qt4cg.org/meeting/minutes/2023/10-03.html#h-2476E3A4-7AB9-474C-8122-04FA7CDC9551
  13. https://qt4cg.org/meeting/minutes/2023/10-03.html#h-2A975F7E-9A4C-469B-9102-16E450DC8B88
  14. https://qt4cg.org/meeting/minutes/2023/10-03.html#adjourned
  15. https://qt4cg.org/meeting/minutes/
  16. https://qt4cg.org/
  17. https://qt4cg.org/dashboard
  18. https://github.com/qt4cg/qtspecs/issues
  19. https://github.com/qt4cg/qtspecs/pulls
  20. https://qt4cg.org/dashboard/#pr-449

                                        Be seeing you,
                                          norm

--
Norm Tovey-Walsh
Saxonica

Received on Wednesday, 4 October 2023 16:13:07 UTC