- From: Michael Dyck <jmdyck@ibiblio.org>
- Date: Tue, 14 Jun 2016 15:23:47 -0400
- To: public-xsl-query@w3.org
On 16-06-10 11:45 AM, Andrew Coleman wrote:
> DRAFT XML Query/XSL WG Joint Teleconference #646 Agenda 2016-06-14
>
> Andy will chair this meeting.
>
> PLEASE SEND CORRECTIONS AND ADDITIONS AS SOON AS POSSIBLE SO A REVISED
> AGENDA CAN BE PREPARED IN A TIMELY MANNER!
>
> Changes in this agenda:
>
>
>
> This week, I'd like us to work on the following items:
> J4.2 (F&O)
> J4.3 (Serialization)
> J4.4 (XPath)
> J4.6 (Test Suite)
> 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.
DECISION re bug 29684 ([FO31] options arguments): close with no action.
DECISION re bug 29683 ([XP31] Map lookup through function-call syntax does
not explain what happens if the key does not exist): resolve this as
outlined in comments 2 and 3 of the bug.
DECISION re bug 29419 ([XP31] edge case with negative integer literals
(UnaryExpr) and limits for -9223372036854775808, which cannot be parsed):
add CMSMcQ's Note (see below) to the XPath spec.
DECISION re bug 29678 ([QT3TS] same-key-006): accept the solution in
comment 2 of the bug.
DECISION re bug 29679 ([XQ3Ts] same-key-008): close bug with no action.
DECISION re bug 29622 ([XP31] Atomization in Postfix Lookup, Unary Lookup):
accept Tim's proposal in comment 0.
DECISION re bug 29615 (roman and max-width year): this bug will be resolved
by A-643-01.
> 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-646-01: MKay to propose a solution for Bug 29080
([FO31] array:members).
ACTION A-646-02: JRobie to make the changes outlined in bug 29683
comments 2 and 3 (re map lookup).
ACTION A-646-03: JRobie to add CMSMcQ's Note from the 646 minutes
to the XPath spec.
ACTION A-646-04: Tim to implement the solution in comment 2 of bug 29678.
ACTION A-646-05: Tim to clarify the changes he's proposing for bug 29586
(subtype-itemtype).
ACTION A-646-06: Jonathan to add comment 0 of bug 29622 to the XPath spec.
> ===================================================
> Joint XML Query Working Group and XSL Working Group
> ===================================================
>
>
> J1. Administrative Items
>
> J1.1 Selection of secretary(s)
>
> Michael Dyck has been asked to take the minutes. Josh has been asked to
> stand by.
Michael Dyck scribed.
> 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.
>
> Adam Retter - 2016-01-26, 2015-10-20, 2015-04-21
> 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
> Michael Dyck - 2016-06-14, 2016-03-08, 2015-11-17
>
>
>
> 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.
Abel Braaksma
Andy Coleman
C. M. Sperberg-McQueen
Jonathan Robie
Josh Spiegel
Michael Dyck
Michael Kay
O'Neil Delpratt
Tim Mills
> 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
> J1.3 Approval of agenda
>
> J1.3.1 Additions, deletions, or corrections?
None.
(But J4.4.2 was added on the fly.)
> J1.4 Review of recent minutes and administrative items
>
> J1.4.1 Minutes of meeting #645 (Michael Sperberg-McQueen)
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0014.html
No changes.
> 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-06-14
Jrobie suggested a differemt resolution and checked it in:
https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0024.html
> 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-06-14
Done:
https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0026.html
> 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-06-14
Still open. ETA 2016-06-21
> 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-06-14
Done. (No email yet.)
> ACTION A-641-04 (bug 29277) Jonathan to make the editorial changes needed.
>
> Status: Pending; ETA 2016-06-14
Still open. ETA 2016-06-21
> 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: Progressing; ETA not specified.
Ongoing.
> 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-06-14
Done.
https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0028.html
> 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-04
Done:
https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0022.html
> ACTION A-642-03 Mike Kay to make editorial change in 29593 (search
> terms)
>
> Status: Pending; ETA 2016-06-04
Done:
https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0022.html
> ACTION A-643-01: MikeK to update proposal on Bug 29555.
>
> Status: Pending; ETA 2016-06-04
MKay: Hoping to work on this today. ETA 2016-06-21
> 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.
Andy: I've done the easy bit, still need to talk to Liam about the redirect.
ETA 2016-06-21
> 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.
>
> Status: Pending; ETA not specified.
Done:
https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0022.html
> 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).
>
> Status: Pending; ETA not specified.
Done:
https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0021.html
> 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.
>
> Status: Pending; ETA not specified.
Done:
https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0020.html
> ACTION A-645-04: MK to make the change proposed in bug 29685 and make
> test cases.
>
> Status: Pending; ETA not specified.
Done:
https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0022.html
> ACTION A-645-05: Serialization editors (AC, MSM) to discuss bug 29664
> offline and come back with a proposal.
>
> Status: Pending; ETA 2016-06-14
ETA 2016-06-21
> ACTION A-645-06: Serialization editors (AC, MSM) to come back with a
> proposal for bug 29665.
>
> Status: Pending; ETA not specified.
ETA 2016-06-21
> ACTION A-645-07: MSM to prepare a schema with a workaround for the
> issue reported in bug 29658 and post it.
>
> Status: Pending; ETA not specified.
Not done. ETA 2016-06-21
> 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.)
>
> Status: Pending; ETA not specified.
Waiting on 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.)
>
> Status: Pending; ETA not specified.
Waiting on 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.)
>
> Status: Pending; ETA not specified.
Waiting on A-645-07
> ACTION A-645-11: JR to integrate the changes proposed in comments 4-6
> of bug 29509 into the spec.
>
> Status: Pending; ETA not specified.
Done:
https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0025.html
> J1.5.2 Completed action items
>
>
> ACTION A-641-05 (bug 29509) Jonathan to make a proposal to resolve this bug.
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0009.html
>
>
> 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: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0010.html
>
>
> ACTION A-643-02: MikeK to fix definition of array:join so that joining
> zero arrays returns an empty array.
>
> Status: Closed; Reported in meeting
>
>
> 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: Closed; See
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29608#c6
>
>
> ACTION A-644-02 Michael Kay to implement the change proposed in bug 29660.
>
> Status: Closed; See
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29660#c2
>
>
>
> J1.6 Update on related activities
>
> J1.6.1 Update on XSLT WG activities (Sharon, MikeK)
MKay: We should probably start co-ordinating on release dates.
> J1.6.2 Update on EXPath/EXQuery CG activities (Mike)
Nothing.
> 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 Bug 29684 - [FO31] options arguments
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29684
>
> Status: Ready to discuss
Tim recaps comment 1.
MKay: no technical objection, but preference for no change at this stage.
Andy: What's the risk level?
Tim: fairly low, but I can live without the change.
DECISION: close with no action.
> J4.2.3 Bug 29080 - array:members
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29080
>
> Status: Ready to discuss
MKay reviews bug.
MKay: I don't think we can specify these functions without inviting debate.
JRobie: yes, risk of debate.
Abel: if you do this for arrays, then you may find you want to do it for maps.
JRobie: mildly in favour.
Abel: also mildly in favour.
Andy: How long could this potentially delay us?
MKay: I think I could come up with a fairly simple spec.
ACTION A-646-01: MKay to propose a solution.
> 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: Pending completion of A-645-05
>
>
> J4.3.2 Bug 29665 - [SER31] JSON escaping
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29665
>
> Status: Pending completion of A-645-06
>
>
>
> 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 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: Redy to discuss
JRobie: I suggest that we implement this using comments 2 and 3.
DECISION: resolve this as outlined in comments 2 and 3.
ACTION A-646-02: JRobie to make the changes.
NEW AGENDA ITEM:
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
JRobie: reopened this while suggesting a different resolution for A-637-02.
(See comment 13.)
JRobie: I don't think it's good to have conformance language in a Note.
There should be a general statement about limits in the Conformance section.
CMSMcQ: Here is a version of the note in comment 8 without RECOMMENDED and
SHOULD:
The effect of the above rule is that in the case of an integer or
decimal literal, a dynamic error FOAR0002 will generally be raised if
the literal is outside the range of values supported by the
implementation (other options are available: see [F+O section 4.2] for
details.)
The XSD specification allows implementations to impose a limit (which
must not be less than 18 digits) on the size of integer and decimal
values. The full range of values of built-in subtypes of xs:integer,
such as xs:long and xs:unsignedLong, can be supported only if the
limit is 20 digits or higher. Negative numbers such as the minimum
value of xs:long (-9223372036854775808) are technically unary
expressions rather than literals, but implementations may prefer to
ensure that they are expressible.
DECISION: add CMSMcQ's Note to the XPath spec.
ACTION A-646-03: JRobie to do so.
No objections to Jonathan's wording in comment 13.
> 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
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29678
>
> Status: Ready to discuss
DECISION: accept the solution in comment 2
ACTION A-646-04: Tim to implement the solution.
> J4.6.4 Bug 29679 - [XQ3Ts] same-key-008
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29679
>
> Status: Ready to discuss
DECISION: close bug with no action.
> 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
Andy: is this editorial?
Tim: The original problem was substantive.
Andy: but it seems to be settled except for editorial disagreement.
ACTION A-646-05: Tim to clarify the changes.
> 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
Abel: This bug was raised against XQuery, but it's actually an XPath bug.
DECISION: accept Tim's proposal in comment 0
ACTION A-646-06: Jonathan to add to XPath spec
> Q2.3.3 Bug 29634 - [XQ31] ExtensionExpr
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29634
>
> Status: Ready to discuss
JRobie: It's editorial, and I've already fixed it.
> Q2.3.4 Bug 29615 - roman and max-width year
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29615
>
> Status: Ready to discuss
MKay: I have reclassified this bug as F+O.
My existing work on Bug 29555 should be extended to take this into account.
DECISION: this bug is covered by A-643-01.
> 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 Tuesday, 14 June 2016 19:25:20 UTC