- From: C. M. Sperberg-McQueen <cmsmcq@acm.org>
- Date: Tue, 07 Jun 2016 21:20:39 +0000
- To: Public Joint XSLT XQuery XPath <public-xsl-query@w3.org>
- Cc: "C. M. Sperberg-McQueen" <cmsmcq@acm.org>
The XML Query and XSLT Working Groups held a joint teleconference (#645) on 2016-06-07. Agenda: https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0007.html Andy Coleman chaired this meeting. > This week, I'd like us to work on the following items: > J4.2 (F&O) > J4.3 (Serialization) > J4.4 (XPath) > Q2.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 > 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. RESOLVED: to adopt the proposal in bug 29671 to make random-number-generator#1 accept an empty sequence as argument, with the behavior being the same as for random-number-generator#0. RESOLVED: to close bug 29685 by adopting the proposal made there. RESOLVED: to address bug 29509 by adopting the proposal in comments 4-6. > 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-645-01: MK to make the change necessary to implement the proposal in bug 29671 to make random-number-generator#1 accept an empty sequence as argument, with the behavior being the same as for random-number-generator#1. ACTION A-645-02: TM to produce tests for the case of random-number-generator#1 being called with the empty sequence (proposal in bug 29671). ACTION A-645-03: TM to make a list of functions for which the change proposed in bug 29684 (allow the empty sequence as a possible value for the options argument) would in his view make sense, and add those functions to the entry for bug 29684. ACTION A-645-04: MK to make the change proposed in bug 29685 and make test cases. ACTION A-645-05: Serialization editors (AC, MSM) to discuss bug 29664 offline and come back with a proposal. ETA 2016-06-14. ACTION A-645-06: Serialization editors (AC, MSM) to come back with a proposal for bug 29665. ACTION A-645-07: MSM to prepare a schema with a workaround for the issue reported in bug 29658 and post it. ACTION A-645-08: TM to test the schema prepared by MSM to address the issue raised in bug 29658. (Depends on action A-645-07.) ACTION A-645-09: JS to test the schema prepared by MSM to address the issue raised in bug 29658. (Depends on action A-645-07.) ACTION A-645-10: OND to test the schema prepared by MSM to address the issue raised in bug 29658. (Depends on action A-645-07.) ACTION A-645-11: JR to integrate the changes proposed in comments 4-6 of bug 29509 into the spec. > =================================================== > Joint XML Query Working Group and XSL Working Group > =================================================== > J1. Administrative Items > J1.1 Selection of secretary(s) MSM took these minutes. > 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. > Adam Retter - 2016-01-26, 2015-10-20, 2015-04-21 > Michael Dyck - 2016-03-08, 2015-11-17, 2015-09-01 > Josh Spiegel - 2016-03-15, 2015-12-01, 2015-09-08 > Abel Braaksma - > Norm Walsh - 2016-04-05, 2015-12-15, 2015-09-22 > Jonathan Robie - 2016-04-12, 2016-01-05, 2015-09-29 > O'Neil Delpratt - 2016-04-19, 2016-02-02, 2015-10-27 > Mike Kay - 2016-04-26, 2016-03-01, 2015-11-10 > 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 > 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. Present: Andrew Coleman (IBM Corporation) O'Neil Delpratt (W3C Invited Experts) Michael Dyck (W3C Invited Experts) Michael Kay (W3C Invited Experts) Tim Mills (Clinical and Biomedical Computing Ltd) Jonathan Robie (EMC Corporation) C. M. Sperberg-McQueen (W3C Invited Experts) Josh Spiegel (Oracle Corporation) > 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: Liam Quin (W3C Staff) Norman Walsh (MarkLogic) > J1.3 Approval of agenda > J1.3.1 Additions, deletions, or corrections? O'Neil has asked to add some test suite bugs to the agenda; we added agenda item J4.6.3. > J1.4 Review of recent minutes and administrative items > J1.4.1 Minutes of meeting #644 (John) > https://lists.w3.org/Archives/Public/public-xsl-query/2016May/0038.html Accepted as a true record. > 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-637-02: JRobie to include the note in Comment #8 of Bug 29419. > Note also comment #11. > Status: Pending; ETA 2016-05-17 JR reported that he has a large backlog of editorial work, so this is still pending. New ETA 2016-06-14. > ACTION A-640-03: Jonathan to document the decision: Partial function > application never returns a map or an array. if $F is a map or an array > then $F(?) is legal, it returns a function and the function is not a map > or an array. > Status: Pending; ETA 2016-05-17 New ETA 2016-06-14. > ACTION A-640-04: Jonathan Robie to resolve Bug #29277 by making the > changes from comment #20 items 2 and 5. > Status: Pending; ETA 2016-05-17 New ETA 2016-06-14. > ACTION A-641-03 (bug 29583) Jonathan to add xs:anySimpleType to the list > of types for which there is no constructor function. > Status: Pending; ETA 2016-05-17 New ETA 2016-06-14. > ACTION A-641-04 (bug 29277) Jonathan to make the editorial changes needed. > Status: Pending; ETA 2016-05-17 New ETA 2016-06-14. > ACTION A-641-05 (bug 29509) Jonathan to make a proposal to resolve this > bug. > Status: Pending; ETA 2016-05-17 Done: https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0009.html > ACTION A-641-11 (bug 29592) (array and map prefixes). Action on Tim to > resolve the issue in the way suggested in the bug report. > Status: Pending; ETA not specified. Ongoing; TM continues to fix test items that have the problem, as he finds them. > ACTION A-641-14 on Jonathan and Michael Dyck to agree revised wording to > resolve the potential ambiguity in the resolution of action A-636-08 as > described in > https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0020.html. > Status: Pending; ETA not specified. Done; close the action item. https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0010.html > ACTION A-641-15 (bug 29576) (date/time limits) on Jonathan to apply the > proposed text in comment #1 of the bug report. > Status: Pending; ETA 2016-05-17 New ETA 2016-06-14. > ACTION A-642-02 Mike Kay to implement the change he suggested in bug > 29588 > to make the prose normative for duplicate keys > > Status: Pending; ETA 2016-06-07 New ETA 2016-06-14. > ACTION A-642-03 Mike Kay to make editorial change in 29593 (search > terms) > > Status: Pending; ETA 2016-06-07 New ETA 2016-06-14. > ACTION A-643-01: MikeK to update proposal on Bug 29555. > > Status: Pending; ETA 2016-06-07 New ETA 2016-06-14. > ACTION A-643-02: MikeK to fix definition of array:join so that joining > zero arrays returns an empty array. > > Status: Pending; ETA 2016-06-07 Done, but the Bugzilla entry has not been updated; MK will do this as soon as he can find the Bugzilla entry. > ACTION A-643-03: MikeK to address Bug 29608 - Fragment identifiers in > fn:doc etc. Adopted Plan A. normative text remains as is (inconsistent > funcitons), add health warning on doc() > > Status: Pending; ETA 2016-06-07 Done; MK has put a note in the Bugzilla entry. > ACTION A-643-05: Andy to investigate how to solve Q2.3.2 Bug 29610 - > Differing namespace definitions for xqt-errors. > > Status: Pending; ETA not specified. Not done; MK has found the place where the build scripts are going wrong. Perhaps we should work with the Webmaster to provide a redirect. New ETA 2016-06-14. > ACTION A-644-02 Michael Kay to implement the change proposed in bug 29660. > > Status: Pending; ETA not specified. This was making map:remove() and array:remove() support multiple items. Done. MK has added some tests. > J1.5.2 Completed action items > ACTION A-644-01 O'Neil - look into tests tests FODC0004 and FODC0005-1 in > misc-CombinedErrorCodes as per bug 29404 > > Status: Closed; See > https://lists.w3.org/Archives/Public/public-xsl-query/2016May/0039.html > ACTION A-644-03 Tim to revise his proposal in bug 29586 "The judgement > subtype-itemtype(Ai, Bi)" with changes from today's discussion > > Status: Closed; See > https://lists.w3.org/Archives/Public/public-xsl-query/2016May/0040.html > J1.6 Update on related activities > J1.6.1 Update on XSLT WG activities (Sharon, MikeK) MK reported that the XSLT WG continues to work through its issues; nothing has come up relevant to inter-WG coordination. Mike Kay and Abel Braaksma gave a workshop about packages at XML London last week; found a few bugs. > J1.6.2 Update on EXPath/EXQuery CG activities (Mike) Nothing to report. From here we went to J4.2. > 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/2016Apr/0000.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 29555 - [FO31] 9.8.4.2 The Width Modifier > https://www.w3.org/Bugs/Public/show_bug.cgi?id=29555 > Status: Pending completion of A-643-01 > J4.2.2 Discussion of op:same-key > https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0000.html > Status: Ready to discuss Tim Mills described the background. We discussed the relative costs of computing the keys in the cases mentioned in TM's mail and the relative likelihood of user surprise and uncovering hidden bugs in implementators' code. There was sympathy for TM's points, but not a great deal of support for making the change proposed. TM asked whether conversion to string values (with a possible upper limit of 17 characters) would preserve transitivity. AC suggested that further discussion would be in order on the mailing list, but we now have no consensus for a change. > J4.2.3 Bug 29663 - map:for-each > https://www.w3.org/Bugs/Public/show_bug.cgi?id=29663 > Status: Ready to discuss MK decided this was editorial and has fixed it. > J4.2.4 Bug 29671 - [Fo31] fn:random-number-generator > https://www.w3.org/Bugs/Public/show_bug.cgi?id=29671 > Status: Ready to discuss We discussed; the proposal appears to many to be a mild improvement to functionality and to have a modest implementation cost. RESOLVED: to adopt the proposal in bug 29671 to make random-number-generator#1 accept an empty sequence as argument, with the behavior being the same as for random-number-generator#0. ACTION A-645-01: MK to make the change necessary to implement the proposal in bug 29671 to make random-number-generator#1 accept an empty sequence as argument, with the behavior being the same as for random-number-generator#1. ACTION A-645-02: TM to produce tests for the case of random-number-generator#1 being called with the empty sequence (proposal in bug 29671). We looked at the F and O bug list and added two new bugs to the agenda. J4.2.5 Bug 29684 [FO31] options arguments The arguments are similar to those for the bug just discussed. MK expressed reservation on the grounds that there are a great many functions in the library that do NOT adhere to this convention. TM suggested it is a convention that would make sense. ACTION A-645-03: TM to make a list of functions for which the change proposed in bug 29684 (allow the empty sequence as a possible value for the options argument) would in his view make sense, and add those functions to the entry for bug 29684. Bug left open for now. J4.2.6 Bug 29685 [FO31] array:put() There was general embarrassment that such an obvious function as array:put() had been omitted. RESOLVED: to close bug 29685 by adopting the proposal made there. ACTION A-645-04: MK to make the change proposed in bug 29685 and make test cases. > 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 29664 - [SER31] 9.1.17 JSON Output Method: the > json-node-output-method Parameter > https://www.w3.org/Bugs/Public/show_bug.cgi?id=29664 > Status: Ready to discuss We discussed the bug at some length. There was some uncertainty about whether serialization of nodes using the HTML, XML, or other serialization methods (as specified by the json-node-output-method option) uses the serialization parameters specified overall, or uses default values. Some implementations do one, some the other. Some WG members thought the spec could be interpreted in either way and needed clarification; others thought only one reading was plausible (some on each side). Empirically, then, the spec is not now sufficiently clear. Concretely: if we specify indent=yes, and then serialize a map as JSON with json-node-output-method set to HTML, are HTML nodes indented or not? If serialization are passed down to the called method, then yes the HTML will be indented, and there seems to be no way to get JSON indented but HTML non-indented. If the parameters are not passed down, then the HTML will or won't be indented, depending on how we define the defaults, and there is not way to control it. There was some sentiment for making the spec more explicit. AC noted that the adaptive input method explicitly says that parameters are passed down. There was some sentiment that that might be the right thing to do in the JSON case, too, for the sake of uniformity. TM observed that three options have meaning both for JSON and for other methods: byte-order-mark, use-character-maps, indent. We want to avoid double application of character maps. Looking closely at the rules at the beginning of section 9 (paragraph beginning "Whenever a value is serialized to a JSON string, ..."), however, we saw that it seems to suggest that if character maps are supplied as serialization options, and applied by the XML method, then they will be applied again by JSON on the string returned by the XML method. Josh proposed as an alternative that we specify that serialization options NOT be passed down, and that the default values on the serialization function be used. MK noted that making json-node-output-method accept a set of serialization parameters would solve the problem; this was felt to be a suitable proposal for a time in a WG is defining new functionality, but perhaps not for now. There was some discussion of which approach to the problem would place fewer barriers in the way of some future WG (but it did not seem conclusive). MSM asked for time to think. ACTION A-645-05: Serialization editors (AC, MSM) to discuss bug 29664 offline and come back with a proposal. ETA 2016-06-14. > J4.3.2 Bug 29665 - [SER31] JSON escaping > https://www.w3.org/Bugs/Public/show_bug.cgi?id=29665 > Status: Ready to discuss We discussed. ACTION A-645-06: Serialization editors (AC, MSM) to come back with a proposal for bug 29665. MK suggested they might consult the documentation for xml-to-json() for consistency. > J4.3.3 Bug 29658 - [SER31] Problem with schema > https://www.w3.org/Bugs/Public/show_bug.cgi?id=29658 > Status: Ready to discuss The schema does not work out of the box with Microsoft tools. We discussed. ACTION A-645-07: MSM to prepare a schema with a workaround for the issue reported in bug 29658 and post it. ACTION A-645-08: TM to test the schema prepared by MSM to address the issue raised in bug 29658. (Depends on action A-645-07.) ACTION A-645-09: JS to test the schema prepared by MSM to address the issue raised in bug 29658. (Depends on action A-645-07.) ACTION A-645-10: OND to test the schema prepared by MSM to address the issue raised in bug 29658. (Depends on action A-645-07.) > 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 29509 - Functions: External, Implementation-Defined, Host > Language > https://www.w3.org/Bugs/Public/show_bug.cgi?id=29509 > > Status: Pending completion of A-641-05 JR reviewed his proposal in comments 4-6. We discussed. RESOLVED: to address bug 29509 by adopting the proposal in comments 4-6. ACTION A-645-11: JR to integrate the changes proposed in comments 4-6 of bug 29509 into the spec. At this point, the usual time had elapsed, and we adjourned. > J4.4.2 Bug 29683 - [XP31] Map lookup through function-call syntax does not > explain what happens if the key does not exist > https://www.w3.org/Bugs/Public/show_bug.cgi?id=29683 > Status: Ready to discuss > 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 J4.6.3 Bug 29678 [QT3TS] same-key-006 J4.6.4 Bug 29679 [XQ3Ts] same-key-008 > 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 > 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 > Q2.3.1 Bug 29586 - [XQ31] 2.5.6.2 The judgement subtype-itemtype(Ai, Bi) > https://www.w3.org/Bugs/Public/show_bug.cgi?id=29586 > Status: Ready to discuss; See revised proposal: > https://lists.w3.org/Archives/Public/public-xsl-query/2016May/0040.html > Q2.3.2 Bug 29622 - [XQ31] Atomization in Postfix Lookup, Unary Lookup > https://www.w3.org/Bugs/Public/show_bug.cgi?id=29622 > Status: Ready to discuss > Q2.3.3 Bug 29634 - [XQ31] ExtensionExpr > https://www.w3.org/Bugs/Public/show_bug.cgi?id=29634 > 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-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, 8 June 2016 06:45:52 UTC