- From: Michael Kay <mike@saxonica.com>
- Date: Wed, 2 Mar 2016 14:19:43 +0000
- To: Michael Kay <mike@saxonica.com>
- Cc: Public Joint XSLT XQuery XPath <public-xsl-query@w3.org>
Sorry, I omitted the list of attendees:
According to webex:
Abel Braaksma
Andy Coleman
C. M. Sperberg-McQueen
John Snelson
Jonathan Robie
Josh
Liam Quin
Michael Dyck
Michael Kay
O'Neil Delpratt
Tim Mills
Michael Kay
> On 2 Mar 2016, at 14:14, Michael Kay <mike@saxonica.com> wrote:
>
> XML Query/XSL WG Joint Teleconference #634 Minutes 2016-03-01
>
>
> Andy did 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.4 (XPath)
> 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.
>
> DECISION to close bug 29427 (map:get suggestions) with no action. (Andy will close it).
>
> DECISION to fix the text for regular expression backreferences as suggested in the latest comment of bug 29415, and close the bug.
>
> DECISION: close bug 29430 (numeric result types) with no action. (Abel will do)
>
> DECISION: (bug 29496) accepted one technical change, allowing the hours value to be single digit, plus editorial clarifications as suggested in points (3) and (5).
>
> DECISION: (bug 29498): only action to be taken is to add definitions of RECOMMENDED/REQUIRED to specs if they are actually used: check XPath/XQuery
>
>
> 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-634-01 (bug 29415) Mike K to fix regex text as proposed in bug 29415 (and close the bug)
>
> ACTION A-634-02 (bug 29404) Mike to propose harmonization of the way that doc, collection, unparsed-text etc treat invalid URI arguments.
>
> ACTION A-634-03: (bug 29496) MikeK to implement the minuted decision on bug 29496 and close the bug.
>
> ACTION A-634-04 (bug 29498) Jonathan to ensure that all terms that use RFC rendition (e.g. "required", "recommended") are listed in the terminology section.
>
> ACTION A-634-05 (bug 29227) on MDyck to draft alternative wording for this section that addresses
>
> ACTION A-634-06 (bug 29419) on Abel to either close bug 29419, or propose spec changes that address the problem.
>
> ===================================================
> Joint XML Query Working Group and XSL Working Group
> ===================================================
>
>
> J1. Administrative Items
>
> J1.1 Selection of secretary(s)
>
> Mike Kay has been asked to take the minutes. Michael Dyck 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.
>
> 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-09-29, 2015-05-12
> John Snelson - 2015-01-12, 2015-07-16, 2015-06-02
> Liam Quin - 2016-01-19, 2015-10-06, 2015-06-16
> Adam Retter - 2015-01-26, 2015-10-20, 2015-04-21
> O'Neil Delpratt - 2016-02-02, 2015-10-27, 2015-06-23
> Michael Sprbrg-McQn - 2016-02-09, 2015-10-03, 2015-06-09
>
>
>
> 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 #632 (O'Neil)
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Feb/0001.html
>
> §§ Link needs updating, should be Feb/0029.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-628-01: Liam to discuss the status of XQuery Update 3.0 at XML Prague.
>
> Status: Pending; ETA 2016-02-13
>
> §§ Liam talked to a few people about XQuery Update but found no great enthusiasm for doing the work.
>
> §§ Note we have already abandoned 3.1, we're talking now about whether to take XQuery Update 3.0 to completion. JS: the spec is essentially complete, but if we're not going to have implementations and test suites, perhaps we should publish it as a Note and leave it there.
>
> §§ We're at LCWD, we can't progress beyond that without plans for a test suite.
>
> §§ Jonathan thinks there are implementations, but we're not sure how many. Adam says Exist doesn't; Christian apparently has plans/intents but no product.
>
> §§ Moved to agenda item 5.2.
>
> §§ ACTION CLOSED.
>
>
> ACTION A-629-02: Jonathan Robie to apply the clarification from the comment 12 of bug 29346 to the spec.
>
> Status: Pending; ETA 2016-03-01
>
> §§ DONE: See March message 0001.
>
>
> ACTION A-629-03: Abel to write test cases for the resolution to bug 29346.
>
> Status: Pending; ETA 2016-02-02; Awaiting completion of A-629-02
>
> §§ PENDING (A-629-02 is now complete so this is no longer blocked). New ETA 8 March.
>
>
> ACTION A-629-04: Jonathan Robie to fix bug 29362 by referring to the definition of op:same-key in F&O
>
> Status: Pending; ETA 2016-03-01
>
> §§ PENDING. ETA 2016-03-08.
>
>
> ACTION A-630-01: Mike Kay to propose a resolution on 29373 Missing error code
> when fn:serialize receives a QName method in no namespace
>
> Status: Pending; ETA 2016-03-01
>
> §§ PENDING ETA 2016-03-08
>
>
> ACTION A-630-02: O'Neil to remove reporting of the features that aren't in 3.1
> (static typing, namespace axis) and tests that are not for 3.1
> (e.g. 3.0 or XPath)
>
> Status: Pending; ETA 2016-03-01
>
> §§ PENDING. O'Neil has been working on it but needed to investigate the requirements more carefully.
>
>
> ACTION A-630-06: jonathan to check the wording to make validate {} an error [bug 29370]g
>
> Status: Pending; ETA 2016-03-01
>
> §§ PENDING ETA 2016-03-08
>
>
> ACTION A-631-02: Jonathan Robie to make the changes in XPath 3.1 as suggested by Michael Dyck in Bug 29382
>
> Status: Pending; ETA 2016-03-01
>
> §§ PENDING ETA 2016-03-08
>
>
> ACTION A-632-03: Mike to add a clarification text and example to bug 29415
>
> Status: Pending; ETA not specified.
>
> §§ PENDING ETA 2016-03-08
>
>
> ACTION A-633-01: Andy Coleman to discuss the possible obsoleting of the
> 3.0 specs with Liam Quin (once 3.1 is a REC).
>
> Status: Pending; ETA not specified.
>
> §§ PENDING ETA 2016-03-08
>
> §§ CLOSED for now because we can't do anything until 3.1 is a REC.
>
>
> ACTION A-633-02: Andy Coleman to change the serialization spec to say
> that in the JSON serialization method, "Implementations MAY serialize
> the value of a number using any lexical representation of the
> xs:double value" or words to that effect. This should resolve bug
> 29435 (JSON Serialization of numerics).
>
> Status: Pending; ETA not specified.
>
> §§ DONE. March message 0000.
>
>
> ACTION A-633-03: Jonathan Robie to open a new bug on the
> classification of functions and terminology for that classification.
>
> Status: Pending; ETA not specified.
>
> §§ DONE. Bug 29509.
>
>
> ACTION A-633-04: Jonathan Robie to reword section 3.1.5.1 Evaluating
> Static and Dynamic Function Calls of XQuery (and the corresponding
> function of XPath) to address Abel Braaksma's observations that (a)
> 5.b.iv is ill-worded since not every nonlocal variable binding will
> necessarily be supplied as an actual parameter, and (b) the parameter
> bindings supplied by the partial application should not be commingled
> forever with the nonlocal variable bindings.
>
> Status: Pending; ETA not specified.
>
> §§ There has been a proposal and subsequent email discussion. See March message 0001.
>
> J1.5.2 Completed action items
>
>
> ACTION A-632-02: Mike to make the change of adding cross reference to section 5.3.5 in relation to bug 29406
>
> Status: Closed; See
> http://lists.w3.org/Archives/Public/public-xsl-query/2016Feb/0015.html
>
>
> ACTION A-632-04: Jonathan to refine wording in section 3.1.5.1Evaluating Static and Dynamic Function Calls. Based on the following points: 1. provide formal definitions for "host language function", "implementation-defined function", link to "external function”. 2. make sure that inline functions and declared functions are well defined as "functions that have bodies”. 3. Change ...F's implementation is a... to ..F is a…
> 3a. typo: s/an/a in "is an partially applied function,”
>
> Status: Closed; See
> http://lists.w3.org/Archives/Public/public-xsl-query/2016Feb/0008.html
>
>
> ACTION A-632-05: Jonathan to propose a solution to bug 29414
>
> Status: Closed; See
> http://lists.w3.org/Archives/Public/public-xsl-query/2016Feb/0009.html
>
>
> ACTION A-632-06: O’Neil to make dependency on XSD 1.0 on the test cases. Update the bug issue 29404
>
> Status: Closed; See
> http://lists.w3.org/Archives/Public/public-xsl-query/2016Feb/0007.html
>
>
>
> J1.6 Update on related activities
>
> J1.6.1 Update on XSLT WG activities (Sharon, MikeK)
>
> §§ MikeK reported on the F2F and on the XML Prague interoperability workshop.
>
> §§ Abel: on usability, there was some critique from the audience on syntax for streaming, static expressions, text value templates, etc.
>
> J1.6.2 Update on EXPath/EXQuery CG activities (Mike)
>
> §§ MikeK reported there has been a fair bit of email traffic on XSpec (unit testing framework).
>
> J1.7 Future Meetings
>
> §§ No plans for a future F2F, no one saying it is needed.
>
> 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
>
>
>
> 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
>
> (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 29373 - Missing error code when fn:serialize receives a QName method in no namespace
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29373
>
> Status: Pending completion of A-630-01
>
>
> J4.2.2 Bug 29427 - [FO31] map:get
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29427
>
> Status: Ready to discuss
>
> §§ Most of these comments are simply too late. The typo has already been fixed.
>
> §§ DECISION to close bug 29427 (map:get suggestions) with no action. (Andy will close it).
>
>
> J4.2.3 Bug 29415 - [FO31] Regex: capturing parentheses inside non-capturing parentheses
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29415
>
> Status: REOPENED - Ready to discuss
>
> §§ Abel Reopened. Mike accepts the need to fix the text as suggested.
>
> §§ DECISION Editor to fix the text for regular expression backreferences as suggested in the latest comment of bug 29415.
>
> §§ ACTION A-634-01 Mike to fix regex text as proposed in bug 29415 (and close the bug)
>
>
> J4.2.4 Bug 29404 - [QT3] anyURI in fn:collection
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29404
>
> Status: Ready to discuss
>
> §§ Mike: fn:doc() says an error "may" be raised in the case of an invalid URI; fn:doc-available(), fn:collection(), fn:uri-collection() say it "is raised". Also need to consider the unparsed-text() family. A complication is that errors may occur resolving a relative URI ref if it is invalid.
>
> ACTION A-634-02 (Bug 29404) Mike to propose harmonization of the way that doc, collection, unparsed-text etc treat invalid URI arguments.
>
>
> J4.2.5 Bug 29430 - [FO31] Resulting type of numeric functions
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29430
>
> Status: Ready to discuss
>
> §§ Mike: Abel's last sentence is "let's close with no action".
>
> §§ DECISION: close bug 29430 with no action. (Abel will do)
>
>
> J4.2.6 Bug 29496 - [FO31] parse-ietf-date with military timezones and leniency towards single-digit numbers
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29496
>
> Status: Ready to discuss
>
> §§ Military timezones: Liam says these have been deprecated in later RFCs and believes they are not in use in the wild. Suspects even the military no longer use them. At least not in the principal use cases for this function. Mike: to add functionality in CR you need a very strong use case.
>
> §§ (2) is about named timezones. Liam: most people are using one of a small number of libraries to generate these dates. I don't think other timezones are widely encountered. Mike: if we defined the meanings of additional timezones, it would involve cultural bias. If we left them impl-def, we would lose interoperability. So I'm opposed to this change. Jonathan: it's too late to be doing this.
>
> §§ (3) we should say that the default for fractional seconds is zero. Leave this one to the editor.
>
> §§ (4) leading zero optional. This is only the case for day number, not for hours. Liam this might be related to dropping support for 12-hr clock. Thinks the note may have been intended to allow H:mm (but not H:M?). Thinks it might make sense to change hours to (digit digit?)
>
> §§ (5) We should clarify that the Note about liberalism is explaining why the rules are as they are, not encouraging people to relax the specification further.
>
> §§ Further, it would be useful to explain any deviations from the RFC (e.g. military timezones): Liam – we accept everything in 2616, which itself is derived from the others, obsoleting some aspects.
>
> §§ DECISION: (bug 29496) accepted one technical change, allowing the hours value to be single digit, plus editorial clarifications as suggested in points (3) and (5).
>
> §§ ACTION A-634-03: MikeK to implement the minuted decision on bug 29496 and close the bug.
>
>
> J4.2.7 Bug 29498 - [FO31] Some normative RFC 2119 MAY/SHOULD etc appear in non-normative Notes, RFC itself is not mentioned in conformance section
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29498
>
> Status: Ready to discuss
>
> §§ Mike: we made the decision to use our own definitions of the terms rather than refer to the RFC definitions. Also, where SHOULD and MAY appear in a note, this is deliberate: they are sometimes paraphrasing normative statements, they are sometimes giving additional advice consistent with the definition of SHOULD and MAY.
>
> §§ DECISION: Bug 29498: only action to be taken is to add definitions of RECOMMENDED/REQUIRED to specs if they are actually used: check XPath/XQuery
>
> §§ ACTION A-634-04: (Bug 29498) Jonathan to ensure that all terms that use RFC rendition (e.g. "required", "recommended") are listed in the terminology section.
>
>
> 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
>
>
> J4.4.1 Bug 29277 - [XP31] Evaluating function calls does not mention evaluation of dynamic or static function calls that have no FunctionBody
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29277
>
> Status: Pending completion of A-633-04
>
> §§ We discussed the status. Jonathan has checked in changes, and there has been email discussion questioning it.
>
> §§ There was a lot of discussion/criticism which I haven't tried to capture partly because I was talking too much. Part of the criticism is that the classification of functions here doesn't relate in any obvious way to the properties of functions as values in the data model.
>
> §§ ACTION A-634-05 (bug 29227) on MDyck to draft alternative wording for this section that addresses
>
>
> J4.4.2 Bug 29419 - [XP31] edge case with negative integer literals (UnaryExpr) and limits for -9223372036854775808, which cannot be parsed
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29419
>
> Status: Ready to discuss
>
> §§ Discussed. Accepted that the rules for limits on integer ranges aren't very satisfactory, but everyone else seems to be able to live with them. Abel is free to come up with a proposed way forward if he wishes but at the moment there is no proposal to discuss.
>
> §§ No Decision on the bug for now, leave open for Abel to come up with a proposal.
>
> §§ ACTION A-634-06 (bug 29419) on Abel to either close bug 29419, or propose spec changes that address the problem.
>
>
> J4.4.3 Bug 29501 - [xp31] Colon is not in the list of non-terminal symbols
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29501
>
> Status: Ready to discuss
>
>
> J4.4.4 Bug 29487 - [XPath31] Section 3.11.3.1 Unary Lookup wrongly compares array?* to array:flatten
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29487
>
> Status: Ready to discuss
>
>
> J4.4.5 The longest token rule
> See https://lists.w3.org/Archives/Public/public-xsl-query/2016Feb/0043.html
>
> 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
>
> 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 results
>
> Status: Currently three implementers submitted results
>
>
> J4.6.3 - 13 ignored open bugs in defunct category "XML Query Test Suite", should these be moved / closed?
> See https://lists.w3.org/Archives/Public/public-xsl-query/2016Jan/0037.html
>
> 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.
>
>
> 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
>
Received on Wednesday, 2 March 2016 14:20:29 UTC