Mintes from XML Query/XSL WG Joint Teleconference #669 on 2017-07-11

> On Jul 7, 2017, at 6:51 AM, Andrew Coleman <andrew_coleman@uk.ibm.com> wrote:
> 
> DRAFT XML Query/XSL WG Joint Teleconference #669 Agenda 2017-07-11 

Minutes from XML Query/XSL WG Joint Teleconference #669, 2017-07-11

Andy chaired this meeting.

> This week, I'd like us to work on the following items:
> J4.2 (F&O)
> J4.3 (Serialization)
> J4.6 (Test Suite)


> Key:
> J = Joint Query/XSLT meeting;
> Q = Query-only meeting


> Teleconference connection details
> ---------------------------------

> (Member only)
> https://lists.w3.org/Archives/Member/w3c-xsl-query/2015Sep/0014.html



> SUMMARY OF DECISIONS
> ====================

> Note to secretary: Please insert a summary of all decisions made
> during this teleconference at this location in the minutes.

> Decisions MUST be clear as to their complete intent. The subject of
> the decision should *not* require dereferencing; it is most helpful
> if agenda numbers and bug numbers are accompanied by their titles.
> If a decision is recorded about the resolution of a bug, the
> decision must state exactly what the resolution is (e.g., "Accept
> the solution in comment #5", or "Replace the production for XXX with
> this: <new production>", or the like. It should be possible to read
> a decision months later and be certain what it meant and whether or
> not it was properly applied.

DECIDED: to accept bug report 30133 as an error to be fixed.

DECIDED: to close bug 30128 as invalid.

DECIDED: to accept bug 30135 as as an error to be fixed.  

> NEW ACTION ITEMS
> ================
> Note to secretary: Please insert all new action items assigned
> during this teleconference at this location in the minutes.

> Action items MUST make sense even when they are viewed standalone
> (that is, not read in the context of the agenda item where they were
> assigned). This explicitly requires that all referents (e.g.,
> "this", "that") be made clear. Action items such as "Ralph to
> resolve this problem" are DISALLOWED. It takes a scribe only a few
> additional minutes to ensure that action items are clear, while it
> takes the entire WG considerable effort to constantly research the
> meaning of unclear action items. The subject of the action item
> should *not* require dereferencing; it is most helpful if agenda
> numbers and bug numbers are accompanied by their titles.

ACTION A-669-01: MK to prepare an erratum for Bug 30133, prepare new 
errata document. ETA 29 August. 

ACTION A-669-02: MK to update test so that it accepts either a 
no-error outcome or error XQST0031, to resolve bug 30135. 


> ===================================================
> Joint XML Query Working Group and XSL Working Group
> ===================================================


> J1. Administrative Items

> J1.1 Selection of secretary(s)

> Abel has been asked to take the minutes.  O'Neil has been asked to stand 
> by.

MSM took these minutes.


> NOTE: The chair will confirm the secretary prior to the start of the 
> meeting.


> Most recent secretaries (least-recent participants first):
> ----------------------------------------------------------
> (This list identifies the most recent three occasions when each 
> participant acted as Secretary for the Task Force.  The person whose 
> name is at the top of the list should plan to take the minutes at the 
> meeting identified by this agenda; if that person is unavailable, then 
> the job will fall to the next person on the list, etc.

> Abel Braaksma       - 2016-10-18, 2016-06-28
> O'Neil Delpratt     - 2016-11-29, 2016-09-06, 2016-04-19
> Michael Dyck        - 2017-01-10, 2016-10-04, 2016-06-14
> Liam Quin           - 2017-01-17, 2016-10-25, 2016-09-13
> Josh Spiegel        - 2017-01-31, 2016-11-01, 2016-07-19
> Jonathan Robie      - 2017-03-07, 2016-11-08, 2016-07-05
> Mike Kay            - 2017-06-13, 2016-11-15, 2016-07-26
> Michael Sprbrg-McQn - 2017-07-11, 2016-12-06, 2016-09-27 



> J1.2 Call the Roll -- NOT DONE DURING TELECONFERENCE

> XML Query WG membership list: 
> http://www.w3.org/2000/09/dbwg/details?group=18797&order=org

> XSL WG membership list: 
> http://www.w3.org/2000/09/dbwg/details?group=19552&order=org

Present:

Andy Coleman
Michael Dyck
Michael Kay
Josh Spiegel
Michael Sperberg-McQueen


Regrets:

O'Neil Delpratt
Liam Quin 



> J1.3 Approval of agenda

> J1.3.1 Additions, deletions, or corrections?

The agenda was published in July message 0:
https://lists.w3.org/Archives/Public/public-xsl-query/2017Jul/0000.html

No changes.


> J1.4 Review of recent minutes and administrative items

> J1.4.1 Minutes of meeting #668 (Mike)
> https://lists.w3.org/Archives/Public/public-xsl-query/2017Jun/0002.html

Mike Kay's minutes of meeting #668 were accepted as a true record.


> J1.5 Review of action items

> J1.5.1 Outstanding action items


> ACTION A-668-01 (Bug 30119 - command element in HTML5) Andy and
> MSMcQ to draft an erratum and close the bug as proposed.

> Status: Pending; ETA not specified.

DONE. AC sent out a message this morning.
https://lists.w3.org/Archives/Public/public-xsl-query/2017Jul/0001.html

> ACTION A-668-02 (Bug 30119 - command element in HTML5) Josh to fix
> the test case Serialization-html-2 referred to in the bug report.

> Status: Pending; ETA not specified.

JS says he didn't do that, but MK did. He asked for discussion later.
(We discussed it under heading J6.1.4.)

  
> ACTION A-668-03 MHK to add a new feature flag to the test suite
> indicating tests that require HTTP access, and to mark test case
> fn-unparsed-text-054 with this flag.

> Status: Pending; ETA not specified.

DONE. MK reports that he added a dependency called Remote HTTP.


> ACTION A-668-04 Josh to fix the expected result of test case 
> Serialization-html-19c as suggested in bug 30120.

> Status: Pending; ETA not specified.

PENDING. ETA 29 August (next meeting).


> ACTION A-668-06 Andy and MSMcQ to fix the bug referred to in action 
> A-668-05.

> Status: Pending; ETA not specified.

DONE.
https://lists.w3.org/Archives/Public/public-xsl-query/2017Jul/0001.html


> J1.5.2 Completed action items


> ACTION A-657-12: ABr to create more tests for fn:transform, as he 
> describes in bug 29834

> Status: Closed; Overtaken: MHK has revised the transform tests.


> ACTION A-661-04 (Bug 29997) AB to fix up the dependencies on the 
> fn:transform tests and if appropriate resubmit results.

> Status: Closed; Overtaken: MHK has revised the transform tests.


> ACTION A-662-04: MikeKay to investigate bug 29932

> Status: Closed; See
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29932#c6


> ACTION A-663-02: MK to respond to original commentor (Thomas Fischer)
> w.r.t. our decision on bug 30025 "[F+O3.1] array:join() - misleading
> name" (WORKSFORME).

> Status: Closed; action dropped


> ACTION A-663-03: MK to respond to original commentor w.r.t. our
> decision on bug 30024 "[F+O 3.1] Is map:entry superfluous?" (FIXED).

> Status: Closed; action dropped


> ACTION A-668-05 Josh to raise a bug pointing out that some namespaces in 
> the Serialization spec have been mis-edited to use "https" rather than 
> "http".

> Status: Closed; See
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=30126


> ACTION A-668-07 Andy to cause the two documents (XQuery Scripting 
> Extension 1.0 (Use Cases | Requirements)) to be republished as WG Notes.

> Status: Closed; See
> https://www.w3.org/TR/xquery-sx-10-use-cases/
> https://www.w3.org/TR/xquery-sx-10-requirements/



> J1.6 Update on related activities

> J1.6.1 Update on XSLT WG activities (Sharon, MikeK)

Very little activity; there have been one or two bug reports.


> J1.6.2 Update on EXPath/EXQuery CG activities (Mike)

No one aware of any activity there.


> J1.7 Future Meetings

> J1.7.1 QT Meeting Schedule

> [V48] Joint XML Query/XSL WG meeting schedule
> https://lists.w3.org/Archives/Member/w3c-xsl-query/2017Feb/0000.html

We have one more scheduled meeting, for 29 August.

For the time being (pending revision of the W3C process document), the
WG will not close but will remain open in maintenance mode. AC will
prepare a calendar with some dates.

From here we went to J4.2.1.


> J1.7.2 Future F2F Meetings

> J1.7.2.1 Other future F2F meetings

> (none)


> J2. Documents For Review

> (none)



> J3. Maintenance Issues

> J3.0 The XML Query WG and XSLT WG do not intend to maintains specs
> earlier than the 3.0 suite of documents; when the 3.1 suite reaches
> Recommendation, maintenance of the 3.0 documents will be terminated.

> This agenda item is reserved for reporting errors and other problems
> reported against the 3.1 suite of specifications.


> J3.1 Bugzilla Bugs filed against the 3.0 suite of joint XML Query WG
> and XSLT WG documents

> (none)



> J4. Active Specification Development


> ** Note: Full Text 3.1 has been removed from the WG agenda. If, in
> the future, there is sufficient interest (i.e. at least two
> independent participants to develop the spec and implementations),
> then this can be brought back on the agenda.



> J4.1 Data Model 3.1 (Andy)

> J4.1.0 Internal working draft
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-datamodel-31/html/Overview.html
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-datamodel-31/html/Overview-diff.html
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-datamodel-31/src/changes.txt

> (none)


> J4.2 Functions and Operators 3.1 (Mike Kay)

> J4.2.0 Internal working draft
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/html/Overview.html
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/html/Overview-diff.html
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/src/changes.txt


> J4.2.1 Bug 30133 - [FO31]Example in 
> https://www.w3.org/TR/xpath-functions-31/#func-exists is incomplete
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=30133

> Status: Ready to discuss

We examined the bug; the typo it reports seems real enough.

DECIDED: to accept bug report 30133 as an error to be fixed.

ACTION A-669-01: MK to prepare an erratum for Bug 30133, prepare new 
errata document. ETA 29 August. 


> J4.3 Serialization 3.1 (Michael Sperberg-McQueen, Andy)

> J4.3.0 Internal working draft
> http://www.w3.org/XML/Group/qtspecs/specifications/xslt-xquery-serialization-31/html/Overview.html
> http://www.w3.org/XML/Group/qtspecs/specifications/xslt-xquery-serialization-31/html/Overview-diff.html
> http://www.w3.org/XML/Group/qtspecs/specifications/xslt-xquery-serialization-31/src/changes.txt


> J4.3.1 Bug 30128 - POLYGLOT namespace declarations
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=30128

> Status: Ready to discuss

We discussed this. The key point at issue seems to be a variance of
interpretation of the statement

    ... If the value of the html-version serialization parameter is
    5.0, the serializer SHOULD output namespace declarations in a way
    that is consistent with the requirements of [POLYGLOT]. ...

The reporter (Alejandro Rojas Cepeda) appears to have interpreted it
to mean shifting unqualified elements named 'html', 'svg' (etc.) into
the appropriate namespaces.  But this violates (as MK points out in
comment 1) the requirement that serializers MUST output namespace
declarations that match the result tree.  On this second reading, the
SHOULD statement quoted above encourages serializers to supply
namespace declarations in the locations, and with the prefixes,
prescribed.

DECIDED: to close bug 30128 as invalid.  JS will do so.  (Scribe's
note:  JS has done so.)


> J4.4 XPath 3.1 (Jonathan)

> J4.4.0 Internal working draft
> http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/html/xpath-31.html
> http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/html/xpath-31-diff.html
> http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/src/changes.txt

> (none)


> J4.5 Grammar Test Applets (Michael Dyck)

> (none)


> J4.6 QT3 test suite (O'Neil)

> J4.6.1 Status report on test suite, harness, tools


> J4.6.2 Status of 3.1 tests results

> Status: Currently five implementers submitted results


> J4.6.3 Bug 30135 - [qt3ts] version_declaration-021
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=30135

> Status: Ready to discuss

We discussed.

The spec is clear that processors MAY reject a query if the major
version number is different, or if the minor number of the query is
greater than the implementation's. It does not say they MUST do so;
the test is currently expecting an error.

ACTION A-669-02: MK to update test so that it accepts either a 
no-error outcome or error XQST0031, to resolve bug 30135. 


> J5. Progression of Work

> J5.1 XQuery 3.1, XQueryX 3.1, XPath 3.1, XDM 3.1, F&O 3.1, Serialization 
> 3.1

> J5.1.1 Current status

> * Recommendation


> J5.1.2 Dependencies inhibiting progression


> J5.2 Update 3.0

> J5.2.1 Current Status

> * Working Group Note

> Insufficient resources and interest to continue development



> J6. Any other business

> J6.1 Consideration of future work

> J6.1.1 QT 3.2

> The WGs decided that we will finish the 3.1 documents presently under way,
> but undertake no new work. Maintenance work should be planned upon for a
> period of time after finishing the specifications. 


> J6.1.2 FT 3.1

> Currently inadequate interest and resources


> J6.1.3 Update 3.1

> Currently inadequate interest and resources


J6.1.4 Further discussion of bug 30119

JS reported that MK had fixed the test mentioned in bug 30119, but had
done so by changing the test input.  But the test really has nothing
to do with the erratum: the test is about escaping the URI. The test
should just be changed to expect a different result.

In discussion, we clarified that the test Serialization-html-2 is not
related to the published erratum. We agreed that Josh may change the
expected result: instead of removing the command element, he will
update the result to require serializing it correctly.

Josh's existing action A-668-02 to fix this can thus be extended.


> J7. Adjourn

Having come to the end of the agenda, we adjourned.



> =======================
> XML Query Working Group
> =======================

> Q1. The XML Query WG does not intend to maintains specs earlier than the 
> 3.0 suite of documents; when the 3.1 suite reaches Recommendation, 
> maintenance of the 3.0 documents will be terminated.

> Q1.0 This agenda item is reserved for reporting errors and other 
> problems reported against the 3.0 (later, 3.1) XML Query WG suite of 
> specifications.


> Q1.1 Bugzilla Bugs filed against the 3.0 suite of XML Query WG documents

> (none)



> Q2. Active Specification Development

> Q2.1 XQuery 3.1 (Jonathan)

> Q2.1.0 Internal working draft
> http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/html/xquery-31.html
> http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/html/xquery-31-diff.html
> http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/src/changes.txt

> (none)


> Q2.2 XQueryX 3.1 (Josh)

> Q2.2.0 Internal working draft
> http://www.w3.org/XML/Group/qtspecs/specifications/xqueryx-31/html/Overview.html
> http://www.w3.org/XML/Group/qtspecs/specifications/xqueryx-31/html/Overview-diff.html
> http://www.w3.org/XML/Group/qtspecs/specifications/xqueryx-31/src/changes.txt

> (none)


> Q3. Test Suite Development

> Q3.1 Update Facility 3.0 Test Suite (????)

> * Need test suite developer/manager

> * Need tests 



> Q4. Any other business



> Q5. Adjourn



********************************************
C. M. Sperberg-McQueen
Black Mesa Technologies LLC
cmsmcq@blackmesatech.com
http://www.blackmesatech.com
********************************************

Received on Tuesday, 11 July 2017 16:57:00 UTC