Fw: Minutes: XML Query/XSL WG Joint Teleconference #628 2016-01-05

Forwarded to public mailing list...

"Robie, Jonathan" <jonathan.robie@emc.com> wrote on 11/01/2016 13:42:06:

> From: "Robie, Jonathan" <jonathan.robie@emc.com>
> To: "w3c-xsl-query@w3.org" <w3c-xsl-query@w3.org>
> Date: 11/01/2016 13:54
> Subject: Minutes: XML Query/XSL WG Joint Teleconference #628 2016-01-05
> 
> > 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.
> 
> 
> Action A-628-01: Liam to discuss the status of XML Update 3.0 at XML 
Prague.
> 
> Action A-628-01: Jonathan to enter the following modification to
> MDyck's proposal, into the Bug 29277 and ask Abel / Mike whether this
> resolves the bug:
> 
>    1. The processor "makes the information available" as opposed to
>       invoking using SC and DC
>    2. The Note (which is non-normative). 
> 
>    Replace the note with following normative text:
> 
>      An API used to invoke external functions must state whether the
>      static and dynamic contexts are available to a function that is
>      invoked. The F&O specification states how the static and dynamic
>      contexts are available to a function that is invoked. A host
>      language must state whether and how the static and dynamic
>      contexts are available to a function that is invoked.
> 
> Action A-628-02: Andy to invite Abel to join the next telcon to
> discuss Bug 29346 and Bug 29277.
> 
> Action A-628-03: O'Neil will add the order by clause to fix Bug 29337,
> as proposed in the bug.
> 
> Action A-628-04:  O'Neil to close Bug 29354 as "works for me" witht 
> he following rationale:
> 
>    The key rationale is to decouple our spec from Unicode: using an
>    unassigned character may be (perhaps is) a violation of the
>    agreement between data source and data sink, if they have agreed to
>    use a particular version of Unicode.  But it is not (and should not
>    be) a violation of our specs.  Unicode may assign the character
>    next month or next year, and it should be possible to use the
>    character then, in a conforming implementation.  That means it must
>    be possible *now* to use it in a conforming implementation.
> 
> > ===================================================
> > 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. Jonathan 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
> > Jonathan Robie      - 2015-10-29, 2015-05-12, 2015-01-13
> > 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
> > 
> > 
> > 
> > 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 #627 (Norm)
> > 
https://lists.w3.org/Archives/Public/public-xsl-query/2015Dec/0026.html

> 
> Accepted.
> 
> > 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

> > 
> > 
> > Status: Pending; ETA not specified.
> 
> Still open. Due 12 January. 
> 
> > ACTION A-627-01: Michael Kay to publish a new F&O with the approved
> > revised definition of fn:transform
> > 
> > Status: Pending; ETA not specified.
> 
> Still open. Due 12 January. 
> 
> Action A-628-01:  Liam to discuss the status of XML Update 3.0 at XML 
Prague, 
> 
> > J1.5.2 Completed action items
> > 
> > 
> > ACTION A-579-18: Jonathan to write change proposal to support update 
of
> > maps and arrays.  (See agenda item Q2.1.1)
> > 
> > Status: Closed; Insufficient WG interest to pursue XQUF31
> > 
> > 
> > ACTION A-585-04: Jonathan to write a concrete proposal for XQuery 
Update
> > 3.1 that makes preservation of node identity implementation defined at
> > the persistence layer.
> > See 
https://lists.w3.org/Archives/Member/w3c-xsl-query/2014Nov/0012.html

> > 
> > 
> > Status: Closed; Insufficient WG interest to pursue XQUF31
> > 
> > 
> > ACTION A-622-02: Josh Spiegel to propose changes to XQueryX to support
> > new grammar for empty expressions in braces and return to group with a
> > proposal.
> > 
> > Status: Closed; See
> > 
https://lists.w3.org/Archives/Public/public-xsl-query/2015Dec/0018.html

> > 
> > 
> > 
> > ACTION A-623-01 Andy to do what's needed to republish the XQuery CR.
> > 
> > Status: Closed; See
> > 
https://lists.w3.org/Archives/Public/public-xsl-query/2015Dec/0036.html

> > 
> > 
> > 
> > ACTION A-624-05 on Andy to request publication of Serialization 3.1
> > as revised CR.
> > 
> > Status: Closed; See
> > 
https://lists.w3.org/Archives/Public/public-xsl-query/2015Dec/0036.html

> > 
> > 
> > 
> > ACTION A-624-06 on Andy to request publication of XPath 3.1
> > as revised CR.
> > 
> > Status: Closed; See
> > 
https://lists.w3.org/Archives/Public/public-xsl-query/2015Dec/0036.html

> > 
> > 
> > 
> > ACTION A-625-06 on O’Neil to fix bug 29258 by splitting the tests into 

> > multiple versions.
> > 
> > Status: Closed; See
> > 
https://lists.w3.org/Archives/Public/public-xsl-query/2015Dec/0024.html

> > 
> > 
> > 
> > ACTION A-625-08 on Jonathan to propose a solution for bug 29246.
> > 
> > Status: Closed; See
> > 
https://lists.w3.org/Archives/Public/public-xsl-query/2015Dec/0025.html

> > 
> > 
> > 
> > ACTION A-626-01: Mike to fix F&O example to use correct XPath.
> > Bug 29310 - [FO31] Invalid and ambiguous XPath expression in normative 

> > part of section 5.4.3 fn:substring. 
> > https://www.w3.org/Bugs/Public/show_bug.cgi?id=29310

> > 
> > 
> > Status: Closed; See
> > https://www.w3.org/Bugs/Public/show_bug.cgi?id=29246#c7

> > 
> > 
> > 
> > ACTION A-626-02: JRobie to make a proposal by defining  1. external 
> > functions, 2. host language functions.  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: Closed; See
> > 
https://lists.w3.org/Archives/Public/public-xsl-query/2015Dec/0023.html

> > 
> > 
> > 
> > ACTION A-626-04: JRobie to add 'switch' to the list of expressions in 
> > section 2.3.4 Errors and Optimization which must not raise a dynamic 
> > error in respect of subexpressions occurring in a branch that is not 
> > selected, and must not return the value delivered by a branch unless 
> > that branch is selected.  ALSO add a note to clarify that in "if 
> > (condition) then 'z' else error()" z cannot be returned without 
> > evaluating the condition.  Bug 29320 - [XQ31] Switch expressions 
> > should have same error semantics as typeswitch. 
> > https://www.w3.org/Bugs/Public/show_bug.cgi?id=29320

> > 
> > 
> > Status: Closed; See
> > 
https://lists.w3.org/Archives/Public/public-xsl-query/2015Dec/0022.html

> > 
> > 
> > 
> > ACTION A-627-02: Michael Dyck to review bug #29277 and clarify what
> > the text means. ETA 2016-01.
> > 
> > Status: Closed; See
> > 
https://lists.w3.org/Archives/Public/public-xsl-query/2016Jan/0005.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)
> 
> New Facets proposal:
> http://expath.org/spec/facet/editor 
> 
> > 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

> > 
> > 
> > 
> > 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

> > 
> > 
> > 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

> > 
> > 
> > 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

> > 
> > 
> > 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-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 29333 - Higher-order functions and updates
> > https://www.w3.org/Bugs/Public/show_bug.cgi?id=29333

> 
> We agree with https://www.w3.org/Bugs/Public/show_bug.cgi?id=29333#c1,

> and will close with WORKSFORME.
> 
> > 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
> > 
> > Status: Ready to discuss; Please review MDyck's analysis:
> > 
https://lists.w3.org/Archives/Public/public-xsl-query/2016Jan/0005.html

> 
> Differences in #2 wrt the current spec:
> 
> 1. The processor "makes the information available" as opposed to 
> invoking using SC and DC
> 2. The Note (which is non-normative). 
> 
> Replace the note with following normative text:
> 
> An API used to invoke external functions must state whether the static
> and dynamic contexts are available to a function that is invoked. The
> F&O specification states how the static and dynamic contexts are
> available to a function that is invoked. A host language must state
> whether and how the static and dynamic contexts are available to a
> function that is invoked.
> 
> Action A-628-01: Jonathan to enter the following modification to
> MDyck's proposal, into the Bug 29277 and ask Abel / Mike whether this
> resolves the bug:
> 
>    1. The processor "makes the information available" as opposed to
>       invoking using SC and DC
>    2. The Note (which is non-normative). 
> 
>    Replace the note with following normative text:
> 
>      An API used to invoke external functions must state whether the
>      static and dynamic contexts are available to a function that is
>      invoked. The F&O specification states how the static and dynamic
>      contexts are available to a function that is invoked. A host
>      language must state whether and how the static and dynamic
>      contexts are available to a function that is invoked.
> 
> 
> > 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

> 
> Mike Kay believes that this proposal is correct:
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29346#c3

> 
> Abel has pushed back on it.  We should invite him to the next call.
> 
> This same issue was previously discussed in this thread:
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Sep/0017.html

> 
> Action A-628-02: Andy to invite Abel to join the next telcon to
> discuss Bug 29346 and Bug 29277.
> 
> > 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)
> 
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29337

> 
> Decision: We agree to the proposed fix for Bug 29337.
> 
> Action A-628-03: O'Neil will add the order by clause to fix Bug 29337,
> as proposed in the bug.
> 
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29354

> 
> Action A-628-04: O'Neil to close Bug 29354 as "works for me" witht he
> following rationale:
> 
>    The key rationale is to decouple our spec from Unicode: using an
>    unassigned character may be (perhaps is) a violation of the
>    agreement between data source and data sink, if they have agreed to
>    use a particular version of Unicode.  But it is not (and should not
>    be) a violation of our specs.  Unicode may assign the character
>    next month or next year, and it should be possible to use the
>    character then, in a conforming implementation.  That means it must
>    be possible *now* to use it in a conforming implementation.
> 
> > 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-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 Monday, 4 January 2016 10:54:06 UTC
> > 
> >     This message: [ Message body ]
> >     Previous message: Michael Dyck: "Re: completed A-627-02: 
> "clarify what the text means""
> > 
> >     Mail actions: [ respond to this message ] [ mail a new topic ]
> >     Contemporary messages sorted: [ by date ] [ by thread ] [ by 
> subject ] [ by author ]
> >     Help: [ How to use the archives ] [ Search in the archives ] 
> > 
> > This archive was generated by hypermail 2.3.1 : Monday, 4 January 
> 2016 10:54:07 UTC
> >