- From: O'Neil Delpratt <oneil@saxonica.com>
- Date: Wed, 20 Apr 2016 11:23:39 +0100
- To: Public Joint XSLT XQuery XPath <public-xsl-query@w3.org>
- Message-Id: <E6A8E8C0-41D8-42CA-A806-2AEB380646AF@saxonica.com>
Minutes from XML Query/XSL WG Joint Teleconference #640, 2016-04-19
Andy chaired the meeting
Added the following items:
J4.6.3 Out-of-range date values
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29546 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29546>
J4.6.4
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29573 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29573>
format-dateTime-en151, format-dateTime-en152, format-time-en151, format-time-en152
Q2.3.2 https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0020.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0020.html>
>
>
>
> This week, I'd like us to work on the following items:
> J4.2 (F&O)
> J4.4 (XPath)
We did not get to the items below:
> J4.6 (Test Suite)
> Q2.3 (XQuery)
> Q2.4 (XQueryX)
>
>
>
>
>
>
> SUMMARY OF DECISIONS
> ====================
>
DECISION: Bug 29501 (Colon is not in the list of non-terminal symbols). Voted in favour of option 2b. From email message https://lists.w3.org/Archives/Public/public-xsl-query/2016Mar/0035.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Mar/0035.html>
DECISION: J4.4.2. 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.
DECISION: J4.4.2. The WG reviewed https://www.w3.org/Bugs/Public/show_bug.cgi?id=29277#c20 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29277#c20> and agrees with points 2 and 5 which needs to be fixed.
DECISION: J4.4.4. The WG agreed that the example expression in March email message #37 are valid. Although the spec will remain unchanged.
>
>
> NEW ACTION ITEMS
> ================
>
ACTION A-640-01: Mike Kay to resolve Bug 29570 as described in comment #0
ACTION A-640-02: Mdyck to implemented proposal in the appendix A of the XPath and XQuery specs as described in 2b. Also to make change in the applet and ensure tests cases are updated in the test suite.
Primary one is map-constructor. See: https://lists.w3.org/Archives/Public/public-xsl-query/2016Mar/0035.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Mar/0035.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.
ACTION A-640-04: Jonathan Robie to resolve Bug #29277 by making the changes from comment #20 items 2 and 5.
>
>
>
> ===================================================
> Joint XML Query Working Group and XSL Working Group
> ===================================================
>
>
> J1. Administrative Items
>
> J1.1 Selection of secretary(s)
>
>
O’Neil Delpratt
>
>
> 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-01-12, 2015-07-16, 2015-06-02
> Liam Quin - 2016-01-19, 2015-10-06, 2015-06-16
> Adam Retter - 2016-01-26, 2015-10-20, 2015-04-21
>
> Michael Sprbrg-McQn - 2016-02-09, 2015-10-03, 2015-06-09
> Mike Kay - 2016-03-01, 2015-11-10, 2015-07-15
> Michael Dyck - 2016-03-08, 2015-11-17, 2015-09-01
> Josh Spiegel - 2016-03-15, 2015-12-01, 2015-09-08
> Tim Mills - 2016-03-22, 2015-12-08, 2015-09-15
> 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
>
>
>
> 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 <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 <http://www.w3.org/2000/09/dbwg/details?group=19552&order=org>
Tim Mills
Jonathan Robie
O’Neil Delpratt
Mike Kay
Michael Dyck
Michael Sperberg-McQueen
Josh Spiegel
Abel Braaksma
Andrew Coleman
Norm Walsh
>
>
> Regrets:
Liam Quin
John Snelson
Adam Retter
>
>
>
>
> 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 #639 (Jonathan)
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0012.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0012.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-637-02: JRobie to include the note in Comment #8 of Bug 29419.
>
> Status: Pending; ETA 2016-04-19
Not Done. ETA 2016-04-26
>
>
>
> ACTION A-639-01: Mike to resolve Bug 29534 and modify the tests as
> stated in https://www.w3.org/Bugs/Public/show_bug.cgi?id=29534#c1 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29534#c1>
>
> Status: Pending; ETA not specified.
Closed. https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0024.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0024.html>
>
>
> ACTION A-639-02: Mike to evaluate his proposal in
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29555#c1 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29555#c1> in light of
> Tim's response wrt fractional seconds in #c2.
>
> Status: Pending; ETA not specified.
Closed. https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0024.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0024.html>
>
>
> ACTION A-639-04: O'Neil to remove tests that are not XQuery 3.1
> features from the XQuery 3.1 test suite
>
> Status: Pending; ETA not specified.
Closed. https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0009.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0009.html>
>
>
> ACTION A-639-05: O'Neil to report on tests that do not yet have
> sufficient implementations
>
> Status: Pending; ETA not specified.
Closed. https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0009.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0009.html>
>
>
> Action A-639-06: Mike to implement the resolution of bug 29408 in the F&O text and the tests.
>
> Status: Pending; ETA not specified.
Closed https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0019.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0019.html>
>
>
>
>
> J1.5.2 Completed action items
>
>
> ACTION A-634-04 (bug 29498) Jonathan to ensure that all terms that use RFC rendition (e.g. "required", "recommended") are listed in the terminology section.
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0007.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0007.html>
>
>
> ACTION A-635-04: JRobie to editorially fix Bug 29487 (Section 3.11.3.1 Unary
> Lookup wrongly compares array?* to array:flatten)
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0008.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0008.html>
>
>
> ACTION A-635-05: O'Neil to go through the bugs in the defunct Bugzilla
> component "XML Query Test Suite", closing or moving each as appropriate.
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0009.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0009.html>
>
>
> ACTION A-636-06: Jonathan to ensure that the classification of functions implemented by an XQuery expression covers the case where the function body is empty.
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0010.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0010.html>
>
>
> ACTION A-636-08: Jonathan to adopt the proposal in comment 0 of bug 29526.
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0015.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0015.html>
>
>
> ACTION A-637-01. MKay to respond to Bug 29534 - format-number.
>
> Status: Closed; See Bug report
>
>
> ACTION A-639-03: Jonathan to send email saying he believes that
> Bug29277 is now fixed, including functions with out an explicit
> content expression, and encourage people to read the text with an eye
> to adopting it next week.
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0013.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0013.html>
>
>
>
> J1.6 Update on related activities
>
> J1.6.1 Update on XSLT WG activities (Sharon, MikeK)
>
>
Nothing to report
>
> J1.6.2 Update on EXPath/EXQuery CG activities (Mike)
Nothing to report
>
>
>
> 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 <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)
>
>
> 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)
J3.2 Please add an agenda item for "deprecate Test Suite 1.0":
https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0011.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0011.html>
>
>
>
> 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.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/html/Overview-diff.html>
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-datamodel-31/src/changes.txt <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.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/html/Overview-diff.html>
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/src/changes.txt <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 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29555>
Mike reviewed the bug.
Tim Mills: What happens about repeating groups?
Mike Kay: The is a lack of clarity if the width includes grouping separators or not. It should as his examples shows. Comment 3 focus on the fractional seconds case.
Josh: Would like another week to review his proposal.
Mike Kay will add clarification of the minimum and maximum separators includes grouping separators
>
> Status: Pending completion of A-639-02
>
>
> J4.2.2 Bug 29570 - [FO31] 19.3.6 Casting to list types
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29570 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29570>
>
> Status: Ready to discuss
Tim Mills: Thinks this is an editorial error
ACTION A-640-01: Mike Kay to resolve Bug 29570 as described in comment #0
>
>
>
> 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.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/html/Overview-diff.html>
> http://www.w3.org/XML/Group/qtspecs/specifications/xslt-xquery-serialization-31/src/changes.txt <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.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/html/xpath-31-diff.html>
> http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/src/changes.txt <http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/src/changes.txt>
>
>
> J4.4.1 Bug 29501 - [xp31] Colon is not in the list of non-terminal symbols
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29501 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29501>
See email message: https://lists.w3.org/Archives/Public/public-xsl-query/2016Mar/0035.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Mar/0035.html>
Possibilities:
mdyck: (0) status quo
mdyck: (1) all still legal, but * ones are parsed differently
mdyck: (2) all illegal (user needs to insert a space to get something legal)
Mike Kay: In favours of 2.
Josh: In favour of 1a. Low risk and low changes to the spec. More human readable in the query
Robie: In favour of 2.
Norm in favour of 2.
Andy asked Josh if he would live with option 2.
Josh said yes he could.
DECISION: Bug 29501. Voted in favour of option 2b from email message https://lists.w3.org/Archives/Public/public-xsl-query/2016Mar/0035.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Mar/0035.html>
mdyck: People would be more inclined to write a colon after the NCName
ACTION A-640-02: Mdyck to implemented proposal in the appendix A of the XPath and XQuery specs as described in 2b. Also to make change in the applet and ensure tests cases are updated in the test suite.
Primary one is map-constructor. See: https://lists.w3.org/Archives/Public/public-xsl-query/2016Mar/0035.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Mar/0035.html>
>
> Status: Ready to discuss; see MDyck's proposal:
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Mar/0035.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Mar/0035.html>
>
>
> J4.4.2 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 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29277>
>
> Status: Ready to discuss
Mdyck summarised the bug and the email message: https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0021.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0021.html>jrobie: Issues:
robie: 1. FunctionBody vs. host language expression
2. What happens if we do partial function application on a map or an array
Function body is confusing in two ways
FunctionBody := { Expr? }
Does not want to change the data model
I don't want have to explain the diffence between { avg($a) } and avg($a)
Prefers the later thinks that this is the content expression
Thinks this is editorial
Mdyck: The data model uses the word expression.
Robie: Changing our data model is a big deal at this stage.
Mdyck: Not feeling particularly constrained to the wording used in the data model. It is just being too specific than it has to be.
Mdyck: I think i said something like: The distinction between a FunctionBody and an expression within a FunctionBody is worth recognising.
Mdyck: Agrees that it is editorial, but thinks that a change may be needed to the data model. Another way to resolve it is to leave the data model alone as Jonathan would refer
Mdyck, Robie and Norm to discuss in a telcon how to resolve this bug.
Other point:
Mdyck: Not clear on partial function application to a map or an array. Is that function a map or an array? You will get a type error
Robie Agrees with Mdyck.
Mdyck: Partial function has to supply a question mark as an argument.
Abel: Alternatively, a more orthogonal solution may be to let the lookup operators allow to operate on function items as context item, but this would require to remove the "If the context item is not a map or an array, a type error is raised" from 3.11.3.1, and possibly modifying the rules here.
MikeK. Suggestion: a function call in which all arguments are represented by "?" becomes an error, e.g. f(?, ?)
Robie likes the suggestion
MikeK but it is not backwards compatible with 3.0.
mdyck: let $m := map {"Su": "Sunday"} return ($m(?)) ? "Su"
Abel: and now: let $f := $m(?)
Abel: $m#1
Abel: is disallowed already, right?
MikeK: An array must have some run-time property which says it is an error. The question is should partial function app have some run-time property. Thinks that it should not.
MikeK: Proposal is that when $F is an array or map, $F(?) is legal, and the result is a function that is not a map nor an array.
Robie: Thinks we would have to add some new information to section 2.8.1 Functions DM31.
jrobie: Note: if F is a map or an array, ....
MikeK: Just add: "the result of partial function application is never a map or an array"
jrobie: even if F is.
Abel: @MKay: so, if $F is a map, then $F instance of map(*) succeeds, $F(?) instance of map(*) fails? But is it still cartable?
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.
ACTION A-640-03: Jonathan Robie 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.
Abel added notes in https://www.w3.org/Bugs/Public/show_bug.cgi?id=29277#c20 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29277#c20> discussed each point.
jrobie: If F's implementation is not an XQuery 3.1 expression (e.g., F is a built-in function or an external function or a partial application of such a function)
Points 3) and 4) from Abel’s comment should be crossed out.
Abel: "Errors raised by external functions are implementation-defined (see 2.2.4 Consistency Constraints). “
robie suggests : An API used to invoke external functions must state how the static and dynamic contexts are provided to a function that is invoked.
jrobie: #=> XQuery only:
jrobie: Errors raised by external functions are implementation-defined (see 2.2.4 Consistency Constraints).
DECISION: The WG reviewed https://www.w3.org/Bugs/Public/show_bug.cgi?id=29277#c20 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29277#c20> and agrees with points 2 and 5 which needs to be fixed.
ACTION A-640-04: Jonathan Robie to resolve Bug #29277 by making the changes from comment #20 items 2 and 5.
>
>
>
> J4.4.3 Bug 29509 - Functions: External, Implementation-Defined, Host Language
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29509 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29509>
>
> Status: Pending resolution of bug 29277
>
>
> J4.4.4 Necessary whitespace?
> See: https://lists.w3.org/Archives/Public/public-xsl-query/2016Mar/0037.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Mar/0037.html>
>
> Status: Ready to discuss
Example queries in question:
12!(12 div.)
12 div-3
3!(12 div-.)
Mdyck: Do people agree that the spec says they are valid. Is that ok or do we want to change that.
Josh’s implementation passes the examples.
MikeK: Saxon is not parsing these examples.
MikeK: Syntax error on line 1 at column 8 in {12!(12 div.)}
MikeK: XPST0003: expected ")", found name "div.”
MikeK: Says he would not be happy to apply them. There would be a need to communicate between the tokeniser and the parser.
It depends on the interpretation of the tokenisation rules.
Abel: FWIW: Just tried all three in Exselt, they fail all three as an invalid XPath expression.
Examples match the grammar given that you are generating the grammar.
MikeK: There are two exceptions to this, that of "." and "-", which do require a symbol separator if they follow a QName or NCName.
DECISION: The WG agreed that the example expression in March email message #37 are valid. Although the spec will remain unchanged.
>
>
>
> 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 <http://www.w3.org/Bugs/Public/show_bug.cgi?id=13796>
>
> Status: Pending
>
>
>
> J4.6 QT3 test suite (O'Neil)
>
> J4.6.1 Status report on test suite, harness, tools
>
>
> J4.6.2 Status of 3.1 tests results
>
> Status: Currently three implementers submitted results
>
>
J4.6.3 Out-of-range date values
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29546 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29546>
J4.6.4
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29573 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29573>
format-dateTime-en151, format-dateTime-en152, format-time-en151, format-time-en152
>
> 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.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/html/Overview-diff.html>
> http://www.w3.org/XML/Group/qtspecs/specifications/xquery-update-30/src/changes.txt <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 <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.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/html/xquery-31-diff.html>
> http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/src/changes.txt <http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/src/changes.txt>
>
>
> Q2.3.1 Bug 29571 - [XQ31] [FO31] 3.18.3 Cast
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29571 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29571>
>
> 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.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/html/Overview-diff.html>
> http://www.w3.org/XML/Group/qtspecs/specifications/xqueryx-31/src/changes.txt <http://www.w3.org/XML/Group/qtspecs/specifications/xqueryx-31/src/changes.txt>
>
>
> Q2.4.1 Bug 29568 - [XQX3.1] Incorrect XQueryX conversion of "\u005c"
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29568 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29568>
>
> Status: Ready to discuss
>
>
>
> Q3. Test Suite Development
>
> Q3.1 Update Facility 3.0 Test Suite (????)
>
> * Need test suite developer/manager
>
> * Need tests
Q2.3.2 https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0020.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0020.html>
>
>
>
> Q4. Any other business
>
>
>
> Q5. Adjourn
>
>
>
-------------------------------
O'Neil Delpratt
Software Developer, Saxonica Limited
Email: oneil@saxonica.com <mailto:oneil@saxonica.com>
Twitter: https://twitter.com/ond1 <https://twitter.com/ond1>
Tel: +44 118 946 5894
Web: http://www.saxonica.com <http://www.saxonica.com/>
Saxonica Community site: http://dev.saxonica.com <http://dev.saxonica.com/>
Bug tracking site: https://saxonica.plan.io/ <https://saxonica.plan.io/>
Received on Wednesday, 20 April 2016 10:24:22 UTC