- From: Andrew Coleman <andrew_coleman@uk.ibm.com>
- Date: Fri, 20 Apr 2018 13:15:16 +0100
- To: public-xsl-query@w3.org
- Message-Id: <OFB2FD4942.BB13828F-ON80258275.00433BE6-80258275.004350EE@notes.na.collabserv.c>
DRAFT XML Query/XSL WG Joint Teleconference #672 Agenda 2018-04-24
** THIS IS THE LAST SCHEDULED MEETING OF THE WG BEFORE CLOSURE **
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)
J6.2 Relocation of qtspecs to GitHub
J6.3 Bug tracking to move to GitHub
Key:
J = Joint Query/XSLT meeting;
Q = Query-only meeting
Teleconference connection details
---------------------------------
*** PLEASE NOTE NEW CONNECTION DETAILS ***
(Member only)
TO BE CONFIRMED - check members only mailing list and IRC prior to
meeting.
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. Josh 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 - 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
O'Neil Delpratt - 2017-08-29, 2016-11-29, 2016-09-06
Michael Dyck - 2017-12-19, 2017-01-10, 2016-10-04
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 #671 (Michael Dyck)
https://lists.w3.org/Archives/Public/public-xsl-query/2017Dec/0002.html
J1.5 Review of action items
NOTE: Please be prepared to respond quickly on your action items!
J1.5.1 Outstanding action items
(None)
J1.5.2 Completed action items
ACTION A-668-04 Josh to fix the expected result of test case
Serialization-html-19c as suggested in bug 30120.
Status: Done. See
https://www.w3.org/Bugs/Public/show_bug.cgi?id=30120#c2
ACTION A-670-03: - Mike Kay to create an errata entry for the bug 30151 -
Write properties section for fn:boolean and to provide text for what the
default is for operators without a properties section.
Status: Closed. Erratum FO31.E2 addresses this
ACTION A-671-01 on Liam:
to copy F+O errata document to its public location.
Status: Done. See:
https://www.w3.org/XML/2017/qt-errata/xpath-functions-31-errata.html
ACTION A-671-02 on Andy:
to work out which namespace docs need republishing (and maybe
re-dating).
Status: Done. All republished with fixed links
ACTION A-671-03 on Michael Kay:
to check in source XML for XPath/XQuery errata docs.
Status: Done. See https://github.com/w3c/qtspecs/tree/master/errata/build
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
[V49] Joint XML Query/XSL WG meeting schedule
https://lists.w3.org/Archives/Member/w3c-xsl-query/2017Sep/0000.html
* This WG is scheduled to close on 2018-04-30. No further meetings are
planned.
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. Maintenance of 3.1 Specifications
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
* There are 2 editorial bugs currently open against F&O (30217 & 30237)
- Please can we get these into the errata document?
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 five implementers submitted results
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
For a future Working Group
J6.1.2 FT 3.1
Currently inadequate interest and resources
J6.1.3 Update 3.1
Currently inadequate interest and resources
J6.2 Relocation of qtspecs to GitHub
The CVS qtspecs repository has been put on ice. GitHub is now the single
source of truth:
https://github.com/w3c/qtspecs
* Editors to read and action the instructions on accessing github:
https://lists.w3.org/Archives/Member/w3c-xsl-query/2017Oct/0009.html
J6.3 Bug tracking to move to GitHub
The process is now in place to close the Working Groups and still to be
able to update specs if needed.
The idea is
* flag github issues (on the qtspecs specs) as errata;
* at any time, anyone can ask W3C to republish a Rec with errata folded
in:
1. an in-place update (e.g. for fixing links)
https://www.w3.org/2003/01/republishing/
or, for purely editorial changes
2. https://www.w3.org/Guide/transitions?profile=REC&rec=editorial
(no CR or PR needed, just a new Rec)
or, if there are substantive errata,
3. https://www.w3.org/Guide/transitions?profile=CR&cr=rec-amended
which needs test results.
A whole new version needs a Working Group again.
A W3C Community Group is free to join and could be used as a space for
people to track errata.
We can also update the specs in place on /TR to tell people to use
github instead of bugzilla.
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 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
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, 20 April 2018 12:15:48 UTC