Minutes for Query/XSL WG Joint Teleconference #657, 2016-10-18

Minutes are between the lines, after the summaries below.

Notes from scribe:

Added to agenda were items:
J4.2.8, J4.2.9, J4.2.10 (new bugs F&O)
Section J4.7 on test bugs
J4.7.1 - J4.7.10 (test bugs)

Summary of actions (19 in total):

ACTION A-657-01: Jonathan to review XDM 3.1, ETA: 25 Oct 2016
ACTION A-657-02: Abel to finish reviewing F&O 3.1, ETA: 25 Oct 2016
ACTION A-657-03: MKay to implement changes required to allow "key" attribute in top level of json xml for fn:json-to-xml, bug 29917, comment#0
ACTION A-657-04: MKay to update text of the FOJS error codes to include map/array functions where appropriate, see bug 29928
ACTION A-657-05: MKay to adopt "use-any" for map:merge and to add a Note to clarify its meaning, see bug 29929
ACTION A-657-06: MKay to implement making errors on unspecified variables or context item a dynamic error for fn:load-xquery-module, bug 29930
ACTION A-657-07: MKay to implement the proposal on FOQM007 in bug 29935, comment#0
ACTION A-657-10: MKay to propose a response to make the parameter stylesheet-base-uri implementation defined to address the concerns raised in the bug report, see bug 29939
ACTION A-657-08: MKay to put the rules on serialization parameters in one place, see comment#0 and #1 in bug 29940
ACTION A-657-09: MKay to bring fn:transform in line with fn:serialize w.r.t. serialization parameters, see Bug 29943
ACTION A-657-11: Andy to make the text on use-character-maps to read: "The use-character-maps parameter is directly applicable to the Adaptive output method only as elsewhere specified.", see Bug 29925
ACTION A-657-12: ABr to create more tests for fn:transform, as he describes in bug 29834
ACTION A-657-13: MKay to look at the tests in bug 29883 and suggest a fix
ACTION A-657-14: O'Neil to look at bug 29931 on collations to add dependencies for these tests
ACTION A-657-15: O'Neil to fix the tests mentioned in this bug report, fn-parse-json-110, bug 29934
ACTION A-657-16: Tim to fix test fn-load-xquery-module-012 as he proposed in bug 29936
ACTION A-657-17: Tim to fix test fn-load-xquery-module-060 as he proposed in bug 29937
ACTION A-657-18: O'Neil to look at tests fn-transform-2, 26, 27 to improve them and actually test the caching, see Bug 29942
ACTION A-657-19: O'Neil to look at tests cbcl-cast-gYear-003 and cbcl-cast-gYearMonth-004 and to fix as proposed by MKay in comment #7 of bug 29547 (drop errors as allowed result)

Summary of decisions (decisions on test bugs not recorded as such):

DECISION: the WG accepts the proposal in comment#0 of bug 29917 on relaxing the rules for key attributes
DECISION: Bug 29928, the WG agrees to update the text of these FOJS error codes, but to NOT split them into more categories.
DECISION: Bug 29929, the WG adopts "use-any" instead of "unspecified" for map:merge.
DECISION: Bug 29930, the WG adopts the proposal in comment#0, making errors on unspecified variables or context item a dynamic error.
DECISION: Bug 22935, the WG accepts the proposal on FOQM0007 in comment#0
DECISION: Bug 29943, fn:serialize and fn:transform should be brought in line with one another, where fn:serialize is leading and fn:transform should point to it.
DECISION: Bug 29925, the WG accepts the textual change proposed by MSMcQ to refer to elsewhere in the spec w.r.t. use-character-maps in conjunction with the adaptive output method.

Cheers,
Abel


> 
> DRAFT XML Query/XSL WG Joint Teleconference #657 Agenda 2016-10-18
> 
> 
> 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.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.
> 
> 
> NEW ACTION ITEMS
> ================
> Note to secretary: Please insert all new action items assigned during
> this teleconference at this location in the minutes.
> 
> Action items MUST make sense even when they are viewed standalone (that
> is, not read in the context of the agenda item where they were
> assigned).  This explicitly requires that all referents (e.g., "this",
> "that") be made clear.  Action items such as "Ralph to resolve this
> problem" are DISALLOWED.  It takes a scribe only a few additional
> minutes to ensure that action items are clear, while it takes the entire
> WG considerable effort to constantly research the meaning of unclear
> action items.  The subject of the action item should *not* require
> dereferencing; it is most helpful if agenda numbers and bug numbers are
> accompanied by their titles.
> 
> 
> 
> ===================================================
> Joint XML Query Working Group and XSL Working Group
> ===================================================
> 
> 
> J1. Administrative Items
> 
> J1.1 Selection of secretary(s)
> 
> Abel 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.
> 
> Abel Braaksma       - 2016-06-28
> Jonathan Robie      - 2016-07-05, 2016-04-12, 2016-01-05
> Josh Spiegel        - 2016-07-19, 2016-03-15, 2015-12-01
> Mike Kay            - 2016-07-26, 2016-04-26, 2016-03-01
> O'Neil Delpratt     - 2016-09-06, 2016-04-19, 2016-02-02
> Liam Quin           - 2016-09-13, 2016-05-03, 2016-01-19
> Tim Mills           - 2016-09-20, 2016-05-10, 2016-03-22
> Michael Sprbrg-McQn - 2016-09-27, 2016-06-07, 2016-02-09
> Michael Dyck        - 2016-10-04, 2016-06-14, 2016-03-08
> 
> 
> 
> J1.2 Call the Roll -- NOT DONE DURING TELECONFERENCE

Present as seen in Webex:

Andy
CMSMcQ
Jonathan
Michael Dyck
Michael Kay
O'Neil
Tim Mills
Liam
Abel

Regrets from: Josh

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

Several items were added to the agenda during the meeting, see sections:
F&O new bugs:
J4.2.8
J4.2.9
J4.2.10

QT3 test bugs:
Section J4.7
J4.7.1 - J4.7.10 


> 
> 
> 
> J1.4 Review of recent minutes and administrative items
> 
> J1.4.1 Minutes of meeting #656 (Michael Dyck)
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Oct/0002.html

Approved with no additional comments

> 
> 
> 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-654-11: Jonathan, Michael Kay, Abel, Tim, Michael
> Sperberg-McQueen and Andy to review assigned specifications.

This action can be closed
Jonathan has not finished yet
Michael reviewed XP31, done
Abel is halfway with FO31
Tim reviewed SER31, done
MSMcQ started reviewing XQ31, but doesn't have time to finish
Andy reviewed XQX31, done

Andy asks for a volunteer, will ask Josh

ACTION A-657-01: Jonathan to review XDM 3.1, ETA: 25 Oct 2016
ACTION A-657-02: Abel to finish reviewing F&O 3.1, ETA: 25 Oct 2016

Andy mentions that there is no editor for XDM anymore, he will take on the status section himself

> 
> Status: Pending; ETA 2016-10-11
> 
> 
> ACTION A-655-05: Jonathan Robie to make a proposal to resolve bug 29858
> "Named
> Function References - context information".
> 
> Status: Pending; ETA 2016-10-11

Not done, new ETA 25 Oct 2016

> 
> 
> ACTION A-655-06: Jonathan Robie to review the use of the verb "denote" in
> the
> XPath and XQuery specs.
> 
> Status: Pending; ETA 2016-10-11

Not done, new ETA 25 Oct 2016

> 
> 
> ACTION A-656-01: MKay to make the change summarized in comment 11 of
> Bug 28812
> (JSON options 'unescape' and 'liberal' prevent use of off-the-shelf JSON
> parsers)
> 
> Status: Pending; ETA not specified.

Done, action can be closed, bug is updated.

> 
> 
> ACTION A-656-03: Abel to modify tests in fn/transform.xml to use XPath
> syntax.
> 
> Status: Pending; ETA not specified.

Done, discussed last meeting, action can be closed.

> 
> 
> ACTION A-656-04: O'Neil to run the test suite catalog checks.
> 
> Status: Pending; ETA not specified.

MKay looked at the catalog, mentions it passes all the tests currently.
He mentions it needs "continuous vigilance"

Action completed, can be closed.

> 
> 
> ACTION A-656-05: Josh to implement the fix in comment 1 of bug 29868
> (XQueryX
> stylesheet does not always convert arrowExpr to XQuery correctly).
> 
> Status: Pending; ETA not specified.

Josh is absent today.

> 
> 
> 
> J1.5.2 Completed action items
> 
> 
> ACTION A-654-01:  Abel to commit changes to CVS for fn:transform tests.
> 
> Status: Closed; See
> See https://lists.w3.org/Archives/Public/public-xsl-query/2016Oct/0001.html
> 
> 
> ACTION A-654-09: Tim to fix test suite bug 29833.
> 
> Status: Closed; Reported in last meeting. See
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29833#c1
> 
> 
> ACTION A-656-02: Andy to carry out the decision re Bug 29890 ([SER31] Arrays
> in sequence normalization).
> 
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Oct/0019.html
> 
> 
> 
> J1.6 Update on related activities
> 
> J1.6.1 Update on XSLT WG activities (Sharon, MikeK)

ABr mentions that invocation options are considered for simplification, to make them more orthogonal.
This MAY have impact on fn:transform

Discussion skipped forward to J4.2.1, bug 29917 below

> 
> 
> 
> J1.6.2 Update on EXPath/EXQuery CG activities (Mike)
> 
> 
> 
> 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/2016Jul/0003.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 29917 - [FO31] xml-to-json - processing a subtree
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29917
> 
> Status: Ready to discuss

MKay proposes to remove the rule that it is invalid to supply a top level element that has a key attribute.

Tim asks whether this involves changing the schema
MKay answers: no, no influence, just relaxing the rules

DECISION: the WG accepts the proposal in comment#0
ACTION-657-03: MKay to implement changes required to allow "key" attribute in top level of json xml for fn:json-to-xml, bug 29917, comment#0

> 
> 
> J4.2.2 Bug 29918 - [FO31] map:find ordering constraint prevents streaming
> evaluation
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29918
> 
> Status: Ready to discuss

This bug was raised by Josh, but he is absent, MKay walks us through
The WG tried to discuss it, but didn't understand the streaming-requirement mentioned here.

Leaving the bug open, to be discussed when Josh is present.

> 
> 
> J4.2.3 Bug 29928 - map:merge, error codes
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29928
> 
> Status: Ready to discuss

MKay walks us through the bug, raised by Christian Gruen

DECISION: The WG agrees to update the text of these FOJS error codes, but to NOT split them into more categories.

ACTION-657-04: MKay to update text of the FOJS error codes to include map/array functions where appropriate, see bug 29928

> 
> 
> J4.2.4 Bug 29929 - map:merge: duplicates=unspecified
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29929
> 
> 
> Status: Ready to discuss

MKay briefly walks us through this bug

DECISION: the WG adopts "use-any" instead of "unspecified".
ACTION-657-05: MKay to adopt "use-any" for map:merge and to add a Note to clarify its meaning, see bug 29929

> 
> 
> J4.2.5 Bug 29930 - [FO31] 16.3.1 fn:load-xquery-module
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29930
> 
> Status: Ready to discuss

Tim walks us through. Bottom line: in XQuery, context items and external variables cannot be made REQUIRED by code, so this text should be updated to reflect that status.

DECISION: the WG adopts the proposal in comment#0 of bug 29930 on making errors on unspecified variables or context item a dynamic error.
ACTION-657-06: MKay to implement making errors on unspecified variables or context item a dynamic error for fn:load-xquery-module, bug 29930

> 
> 
> J4.2.6 Bug 29935 - [FO31] 16.3.1 fn:load-xquery-module (FOQM0007)
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29935
> 
> Status: Ready to discuss

DECISION: the WG accepts the proposal in bug 29935 on FOQM0007
ACTION-657-07: MKay to implement the proposal on FOQM007 in bug 29935, comment#0

> 
> 
> J4.2.7 Function annotations, See
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Oct/0011.html

MKay explains that annotations with the same name could not be interrogated by the API of Saxon and it turned out that the spec says little about it.

No further action needed.

ADDED TO AGENDA:

J4.2.8: Bug 29939 - [FO31] fn:transform stylesheet-base-uri options

Tim walks us through the bug report.

He suggests that in 3.0 the stylesheet can be precompiled, *and* be given a "dynamic static base uri", which can henceforth be overridden. However in XSLT 1.0 to 2.0 does not have this ability (unless allowed by a processor as extension).

ACTION-657-10: MKay to propose a response to make the parameter stylesheet-base-uri implementation defined to address the concerns raised in the bug report, see bug 29939

J4.2.9: Bug 29940 - [FO31] fn:transform serialization parameters

MKay suggests that improvement is possible, but since this is already spread over the spec, there's a danger of introducing inconsistencies.

The WG agrees improvement is a good thing in this area

ACTION-657-08: MKay to put the rules on serialization parameters in one place, see comment#0 and #1 in bug 29940


J4.2.10: Bug 29943 - [FO31] fn:transform serialization parameters

The WG agrees that there is an inconsistency
ABr suggests to bring it into line with the serialization parameter schema as well, MKay says they are different things and in the schema the keys are not typed and booleans can have values yes/no, true/false, whereas in the map these are proper booleans. In other words, they cannot be brought in line.

DECISION: fn:serialize and fn:transform should be brought in line with one another, where fn:serialize is leading and fn:transform should point to it.

ACTION-657-09: MKay to bring fn:transform in line with fn:serialize w.r.t. serialization parameters


> 
> Status: Ready to discuss
> 
> 
> 
> 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 29925 - use-character-maps and the adaptive method
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29925
> 
> Status: Ready to discuss

The WG discussed the bug
MSMcQ suggests that there is no conflict

>From IRC, from MSMcQ:
Proposal:  for "The use-character-maps parameter is not directly applicable to the Adaptive output method."
read "The use-character-maps parameter is directly applicable to the Adaptive output method only for the serialization of strings enclosed in quotation marks (e.g. for values of type string or anyURI)."

MKay says it is not quite precise enough. I.e., what about variables of type date for instance?

New proposal from MSMcQ:
read "The use-character-maps parameter is directly applicable to the Adaptive output method only as elsewhere specified."

He proposes using less specific language to describe this, to prevent conflicts as raised in this bug report and by MKay

DECISION: the WG accepts the textual change proposed by MSMcQ to refer to elsewhere in the spec w.r.t. use-character-maps in conjunction with the adaptive output method.
ACTION-657-11: Andy to make the text on use-character-maps to read: "The use-character-maps parameter is directly applicable to the Adaptive output method only as elsewhere specified."

> 
> 
> 
> 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 29858 - [XP31] Named Function References - context information
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29858
> 
> Status: Pending completion of A-655-05
> 
> 
> 
> 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

ADDED TO AGENDA:

Section J4.7 on QT31 test suite bugs

O'Neil walked us through some of the test suite bugs. Of relevance were:

J4.7.1 Bug 29834: O'Neil agrees that some more tests need to be created in the area of fn:transform (some options are not covered)

ACTION-657-12: ABr to create more tests for fn:transform, as he describes in bug 29834

J4.7.2 Bug 29883: [Qt3Ts] fo-test-d3e4625, fo-test-d3e4630

The WG discussed this at some length. 
O'Neil shared the following result:
https://www.wolframalpha.com/input/?i=tan(pi%2F+2)
which is infinity

ACTION-657-13: MKay to look at the tests in bug 29883 and suggest a fix

J4.7.2 Bug 29884: [QT3TS] fo-test-d3e25667

MKay says they will take a look at it (no action)

J4.7.3: Bug 29931 - collation tests allow fallback behavior but the expected results do not

Tim says that there will be a bunch of tests that no-one will pass

Some people on the call considered it a problem, others not to have tests that nobody can pass.

MKay would like to keep the bug open and to add a dependency

ACTION-657-14: O'Neil to look at bug 29931 on collations to add dependencies for these tests

J4.7.4: Bug 29934 - fn-parse-json-110 expects wrong result

ACTION-657-15: O'Neil to fix the tests mentioned in this bug report, fn-parse-json-110, bug 29934

J4.7.5: Bug 29936 - [QT3TS] fn-load-xquery-module-012

The WG agrees to the proposal in this bug report (29936)

ACTION-657-16: Tim to fix test fn-load-xquery-module-012 as he proposed in bug 29936

J4.7.6: Bug 29937 - [QT3TS] fn-load-xquery-module-060

The WG agrees to the proposal in this bug report (29937)

ACTION-657-17: Tim to fix test fn-load-xquery-module-060 as he proposed in bug 29937

J4.7.7: Bug 29942 - [QT3TS] fn-transform-2, 26, 27

MKay says that these assertion were probably meant as placeholders during creation of the tests and agrees that they can be made better.
The WG agrees there is room for improvement with these tests, that were intended to test caching

ACTION-657-18: O'Neil to look at tests fn-transform-2, 26, 27 to improve them and actually test the caching

J4.7.8: Bug 29547 - Castable tests assume no year zero

ACTION-657-19: O'Neil to look at tests cbcl-cast-gYear-003 and cbcl-cast-gYearMonth-004 and to fix as proposed by MKay in comment #7 (drop errors as allowed result)

J4.7.9: Bug 29788 - Incorrect result for millisecs-018

Bug can be closed, overtaken by events and tests succeed now.
Bug to be closed by O'Neil, no action

J4.7.10: Bug 29915 - qt3ts] fn-function-lookup-766a

Bug can be closed, overtaken by events and tests succeed now.
Bug to be closed by O'Neil, 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
> 
> * Potential coordination of dates with XSLT 3.0
> 
> 
> J5.1.2 Dependencies inhibiting progression
> 
> * Sufficient implementation experience and reports thereof
> 
> * Detailed review of specifications by WG
> 
> Participant assigned to each document for detailed review
>   - XDM 3.1           - Jonathan
>   - XPath 3.1         - Mike Kay
>   - F&O 3.1           - Abel
>   - Serialization 3.1 - Tim
>   - XQuery 3.1        - Michael Sperberg-McQueen
>   - XQueryX 3.1       - Andy
> 
> 
> * 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
> 
> (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

Meeting was adjourned at 7PM CEST

> 
> 
> 
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
> 3AU

Received on Tuesday, 18 October 2016 21:29:03 UTC