DRAFT XML Query/XSL WG Joint Teleconference #653 Agenda 2016-09-13

DRAFT XML Query/XSL WG Joint Teleconference #653 Agenda 2016-09-13


Andy will chair this meeting.

PLEASE SEND CORRECTIONS AND ADDITIONS AS SOON AS POSSIBLE SO A REVISED 
AGENDA CAN BE PREPARED IN A TIMELY MANNER!

Changes in this agenda:



This week, I'd like us to work on the following items:
J4.2 (F&O)
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.


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.



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


J1. Administrative Items

J1.1 Selection of secretary(s)

Liam has been asked to take the minutes.  Tim has been asked to stand by.


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.

Liam Quin           - 2016-05-03, 2016-01-19, 2015-10-06
Tim Mills           - 2016-05-10, 2016-03-22, 2015-12-08
John Snelson        - 2016-05-24, 2016-01-12, 2015-07-16
Michael Sprbrg-McQn - 2016-06-07, 2016-02-09, 2015-10-03
Michael Dyck        - 2016-06-14, 2016-03-08, 2015-11-17
Adam Retter         - 2016-06-21, 2016-01-26, 2015-10-20
Abel Braaksma       - 2016-06-28
Jonathan Robie      - 2016-07-05, 2016-04-12, 2016-01-05
Josh Spiegel        - 2016-07-19, 2016-03-15, 2015-12-01
Mike Kay            - 2016-07-26, 2016-04-26, 2016-03-01
O'Neil Delpratt     - 2016-09-06, 2016-04-19, 2016-02-02



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

Note to secretary: During the meeting, take a note of the Webex 
participants, then list in the minutes those present and those who sent 
regrets.  All others will be presumed to have been absent without regrets.


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



Regrets:




J1.3 Approval of agenda

J1.3.1 Additions, deletions, or corrections?



J1.4 Review of recent minutes and administrative items

J1.4.1 Minutes of meeting #652 (O'Neil)
https://lists.w3.org/Archives/Public/public-xsl-query/2016Sep/0005.html



J1.5 Review of action items

NOTE: Please be prepared to respond quickly on your action items!

J1.5.1 Outstanding action items


ACTION A-649-04: Abel to report test results.

Status: Pending; ETA 2016-09-20


ACTION A-650-08: Action on Abel to implement fn:transform

Status: Pending; ETA 2016-09-20



J1.5.2 Completed action items


ACTION A-650-07: Action on Jonathan to resolve bug 29721 as described in 
comment 0.  Also, query the document source to ensure that there are not 
inconsistencies between the error appendix and the main text. 

Status: Closed; Reported in last meeting


ACTION A-652-01: MHK to implement his proposal on map:find in the F&O spec

Status: Closed; See
https://lists.w3.org/Archives/Public/public-xsl-query/2016Sep/0004.html



ACTION A-652-02: MHK to implement the resolution in comment 1 for bug 
29758

Status: Closed; See
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29758#c3



ACTION A-652-03: MHK to implement the resolution in comment 1 in bug 29760

Status: Closed; See
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29760#c3



ACTION A-652-04: MHK to write proposal to resolve bug 29761

Status: Closed; See
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29761#c1



ACTION A-652-05: MHK to implement fix mentioned in comment 2 of bug 29740

Status: Closed; See
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29740#c4



ACTION A-652-06: MHK to Implement change in comment 4 in bug 29765.  If 
you have a single digit picture then there is no truncation.

Status: Closed; See
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29765#c5



ACTION A-652-07: MHK to propose wording that addresses Bug 29785. Issue: 
If you have tried validation against the schema and it has 
failed because of an invalid xsi type the rule says you must carry on to 
do rule 2. (note this was not the intent)

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



ACTION A-652-08: MHK to implement the proposal in comment 0 of bug 29755

Status: Closed; See
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29755#c2



ACTION A-652-09: MHK to implement in spec the proposal in comment 1 of bug 
29800

Status: Closed; See
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29800#c2



ACTION A-652-10: Tim to write test cases for transform and 
load-query-module for when these functions are not supported. See bug 
29800

Status: Closed; See
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29800#c3



ACTION A-652-11: O'Neil to update the public website with the latest 
results on the full test suite. This should include the static typing test 
cases.

Status: Closed; See
https://lists.w3.org/Archives/Public/public-xsl-query/2016Sep/0007.html



ACTION A-652-12: O’Neil to add note in the following test case description 
to say 'tests case is not representable in XQueryX': Axes112, 
K2-NameTest-21, K2-NameTest-23

Status: Closed; See
https://lists.w3.org/Archives/Public/public-xsl-query/2016Sep/0009.html



ACTION A-652-13: Michael Sprbrg-McQn to address the issue raised in August 
message 0: 
https://lists.w3.org/Archives/Public/public-xsl-query/2016Aug/0000.html <
https://lists.w3.org/Archives/Public/public-xsl-query/2016Aug/0000.html> 
Make change: Namespaced-Name were inlined in method-type and in 
json-node-output-method-type

Status: Closed; See
https://lists.w3.org/Archives/Public/public-xsl-query/2016Sep/0002.html




J1.6 Update on related activities

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



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



J1.7 Future Meetings

J1.7.1 QT Meeting Schedule

[V45] Joint XML Query/XSL WG meeting schedule
https://lists.w3.org/Archives/Member/w3c-xsl-query/2016Jul/0003.html




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.0 (later, 3.1) suite of specifications.


J3.0.1 Concerns raised by the XSLT working group in regards to potential
completion delays of XSLT 3.0 if XPath 3.0 is made obsoleted by 3.1

Status: Pending the outcome of Abel's review of 3.0 bugs/errata.
        Any change to the status of the 3.0 specs requires explicit XSL WG
        consultation. 


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 (Norm)

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 29761 - [FO31] width modifier (again)
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29761


See Mike's comment #1
Status: Ready to discuss


J4.2.2 Bug 29765 - [FO31] 9.8.4.4 Formatting the Year Component
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29765


See Mike's proposal:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29765#c5


Status: Ready to discuss


J4.2.3 Bug 29785 - [FO31] 17.5.4 fn:xml-to-json
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29785


See Mike's proposal:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29785#c6


Status: Ready to discuss


J4.2.4 Bug 29722 - [FO31] fn:sort, array:sort
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29722


Status: REOPENED (comment #7); Ready to discuss



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


(none)


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 three implementers submitted results



J5. Progression of Work

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

J5.1.1 Current status

* In Candidate Recommendation; awaiting implementation reports

* Potential coordination of dates with XSLT 3.0


J5.1.2 Dependencies inhibiting progression

* Completion of test suite minimum-required-to-declare-victory

* Sufficient implementation experience and reports thereof

* Formal response to all comments, responses accepted by commenters

* PR Transition Request and authorization, PR pub request

* REC Transition Request and authorization, REC pub request



J5.2 Update 3.0

J5.2.1 Current Status

* In Last Call Working Draft

At XML Prague, Liam talked to a few people about XQuery Update but found 
no great enthusiasm for doing the work.  We cannot progress without plans 
for a test suite and potential implementers.  The WG needs to decide what 
to do with this spec.

Status: Ready to discuss



J5.2.2 Require owner of XQUF 3.0 Test Suite


J5.2.3 Dependencies inhibiting progression

* CR Transition Request and authorization, CR pub request

* Completion of test suite minimum-required-to-declare-victory

* Sufficient implementation experience and reports thereof

* Formal response to all comments, responses accepted by commenters

* PR Transition Request and authorization, PR pub request

* REC Transition Request and authorization, REC pub request



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



J7. Adjourn




=======================
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 Update Facility 3.0 (John)

Q2.1.0 Internal working draft
http://www.w3.org/XML/Group/qtspecs/specifications/xquery-update-30/html/Overview.html

http://www.w3.org/XML/Group/qtspecs/specifications/xquery-update-30/html/Overview-diff.html

http://www.w3.org/XML/Group/qtspecs/specifications/xquery-update-30/src/changes.txt


* The WG needs to obtain implementation experience with this document.


Q2.2 XQuery Update Facility 3.0 Requirements and Use Cases (Andy)
See 
http://www.w3.org/XML/Group/qtspecs/requirements/xquery-update-30/html/Overview.html


* The WGs need to be certain that this document is completed 
(red/yellow/green bullets on requirements, all the use cases intended to 
be published) and a decision made to advance it to WG Note.


Q2.3 XQuery 3.1 (Jonathan)

Q2.3.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.4 XQueryX 3.1 (Josh)

Q2.4.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




Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Received on Friday, 9 September 2016 13:36:24 UTC