Re: DRAFT XML Query/XSL WG Joint Teleconference #629 Agenda 2016-01-12

Andy,

Please add bugs 29364 and 29365 to the agenda.  These bugs identify a couple of minor problems with the XQueryX stylesheet.

Thanks,
Josh

> On Jan 10, 2016, at 8:32 AM, Andrew Coleman <andrew_coleman@uk.ibm.com> wrote:
> 
> DRAFT XML Query/XSL WG Joint Teleconference #629 Agenda 2016-01-12 
> 
> 
> 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: 
> 
> ** Please note, the minutes from last week's meeting had not been posted 
> at the time this agenda was prepared.  Consequently, the current status of 
> action items might be inaccurate and any new action items raised at last 
> week's meeting will not be listed. 
> 
> 
> This week, I'd like us to work on the following items: 
> J4.4 (XPath) 
> J4.6 (Test Suite) 
> J2.3 (XQuery) 
> 
> 
> 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 <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) 
> 
> John has been asked to take the minutes. Liam 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. 
> 
> John Snelson        - 2015-07-16, 2015-06-02, 2015-02-11 
> Liam Quin           - 2015-10-06, 2015-06-16, 2015-03-10 
> Adam Retter         - 2015-10-20, 2015-04-21, 2015-01-20 
> O'Neil Delpratt     - 2015-10-27, 2015-06-23, 2015-03-17 
> Michael Sprbrg-McQn - 2015-10-03, 2015-06-09, 2015-03-03 
> Mike Kay            - 2015-11-10, 2015-07-15, 2015-04-14 
> Michael Dyck        - 2015-11-17, 2015-09-01, 2015-03-31 
> Josh Spiegel        - 2015-12-01, 2015-09-08, 2015-03-24 
> Tim Mills           - 2015-12-08, 2015-09-15, 2015-04-21 
> Norm Walsh          - 2015-12-15, 2015-09-22, 2015-05-05 
> Jonathan Robie      - 2016-01-05, 2015-10-29, 2015-05-12 
> 
> 
> 
> 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 <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 <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 #628 (Jonathan) 
> ** NOT YET POSTED ** 
> 
> 
> 
> 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-626-03: MKay to fix bug 27908 by modifying the test case to use 
> an invalid URI.  Bug 27908 - K2-SeqDocFunc-12 
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=27908 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=27908> 
> 
> Status: Pending; ETA 2016-01-12 
> 
> 
> ACTION A-627-01: Michael Kay to publish a new F&O with the approved 
> revised definition of fn:transform 
> 
> Status: Pending; ETA 2016-01-12 
> 
> 
> 
> J1.5.2 Completed action items 
> 
> 
> 
> 
> 
> 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 
> 
> [V44] Joint XML Query/XSL WG meeting schedule 
> https://lists.w3.org/Archives/Member/w3c-xsl-query/2015Dec/0000.html <https://lists.w3.org/Archives/Member/w3c-xsl-query/2015Dec/0000.html> 
> 
> 
> J1.7.2 Future F2F Meetings 
> 
> J1.7.2.1 Other future F2F meetings 
> 
> None scheduled. 
> 
> 
> 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 
> 
> J3.1.1 Bugzilla Bug 24568, Is the type system really a lattice? Or just 
> a partially ordered set? 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=24568 <http://www.w3.org/Bugs/Public/show_bug.cgi?id=24568> 
> 
> Status: Fixed in Data Model 3.1; not expected to be addressed in Data 
> Model 3.0 
> 
> 
> J3.1.2 Bugzilla Bug 25231, [F+O 3.0 ONLY], ISO 8601, and XSD 1.1 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=25231 <http://www.w3.org/Bugs/Public/show_bug.cgi?id=25231> 
> 
> Status: Fixed in F&O 3.1; not expected to be addressed in F&O 3.0 
> 
> 
> J3.1.3 Bugzilla Bug 26788, [XPath30] XQuery-only errors in XPath 3.0 
> specification, like XQST0134" 
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=26788 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=26788> 
> 
> Status: Fixed in XPath 3.1; not expected to be addressed in XPath 3.0 
> 
> 
> 
> 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.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/html/Overview-diff.html> 
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-datamodel-31/src/changes.txt <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.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/html/Overview-diff.html> 
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/src/changes.txt <http://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/src/changes.txt> 
> 
> (none) 
> 
> 
> 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.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/html/Overview-diff.html> 
> http://www.w3.org/XML/Group/qtspecs/specifications/xslt-xquery-serialization-31/src/changes.txt <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.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/html/xpath-31-diff.html> 
> http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/src/changes.txt <http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/src/changes.txt> 
> 
> 
> J4.4.1 Bug 29277 - [XP31] Evaluating function calls does not mention evaluation of dynamic or static function calls that have no FunctionBody 
> 
> Status: Ready to discuss; Please review MDyck's analysis: 
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Jan/0005.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Jan/0005.html> 
> 
> 
> J4.4.2 Bug 29346 - [XP31] XPath-style currying, or the arrow operator, may require a bit more specification 
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29346 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29346> 
> 
> Status: Ready to discuss 
> 
> 
> 
> J4.5 Grammar Test Applets (Michael Dyck) 
> 
> J4.5.1 Bugzilla Bug 13796, [Applet30] \u escaped characters in grammar 
> applets 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=13796 <http://www.w3.org/Bugs/Public/show_bug.cgi?id=13796> 
> 
> Status: Pending 
> 
> 
> 
> 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 
> 
> Status: Coverage is almost complete. 
> 
> 
> J4.6.3 Publication of test suite. 
> 
> Status: Ready to discuss 
> 
> 
> 
> 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 
> 
> 
> 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 
> 
> 
> 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. 
> 
> Status: Pending completion of ACTION A-592-02. 
> 
> 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.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/html/Overview-diff.html> 
> http://www.w3.org/XML/Group/qtspecs/specifications/xquery-update-30/src/changes.txt <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 <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.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/html/xquery-31-diff.html> 
> http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/src/changes.txt <http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/src/changes.txt> 
> 
> 
> Q2.3.1 Bug 29362 - [XQ31] Definition of "same-key" is out of date 
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29362 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29362> 
> 
> Status: Ready to discuss 
> 
> 
> 
> 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.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/html/Overview-diff.html> 
> http://www.w3.org/XML/Group/qtspecs/specifications/xqueryx-31/src/changes.txt <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 
> 
> 
>