- From: O'Neil Delpratt <oneil@saxonica.com>
- Date: Thu, 8 Sep 2016 11:54:13 +0100
- To: Public Joint XSLT XQuery XPath <public-xsl-query@w3.org>
- Message-Id: <F8C609EA-FCAC-41DB-82AE-5222989D48CB@saxonica.com>
> On 2 Sep 2016, at 13:58, Andrew Coleman <andrew_coleman@uk.ibm.com <mailto:andrew_coleman@uk.ibm.com>> wrote:
>
> DRAFT XML Query/XSL WG Joint Teleconference #652 Agenda 2016-09-06
>
>
Andy chaired this meeting
>
> Changes in this agenda:
Added J4.3.1 Problem with schema
https://lists.w3.org/Archives/Public/public-xsl-query/2016Aug/0000.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Aug/0000.html>
J4.4 (XPath) promoted to the first item discussed in the meeting
>
>
>
> This week, I'd like us to work on the following items:
> J4.2 (F&O)
> J4.4 (XPath)
> 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 <https://lists.w3.org/Archives/Member/w3c-xsl-query/2015Sep/0014.html>
>
>
>
> SUMMARY OF DECISIONS
> ====================
>
DECISION: Adopted MHK’s proposal on map:find in July message 29 with some extra words around order
DECISION: The WG accepted MHK proposal in comment 2 of bug 29740
DECISION: WG agreed to accept proposal in comment 4 to resolve bug 29765. If you have a single digit picture then there is no truncation.
DECISION: WG accepts resolution in comment 0 of bug 29755: For functions parse-json, xml-to-json and json-to-xml: Explicit the default is implementation-defined
DECISION: WG accepted resolution in comment 1 of bug 29800. We need test cases for processors that don’t support functions: transform and load-query-module.
Module URIs are namespace URIs therefore relative URIs are deprecated and not resolved.
>
>
> NEW ACTION ITEMS
> ================
>
ACTION A-652-01: MHK to implement his proposal on map:find in the F&O spec
ACTION A-652-02: MHK to implement the resolution in comment 1 for bug 29758
ACTION A-652-03: MHK to implement the resolution in comment 1 in bug 29760
ACTION A-652-04: MHK to write proposal to resolve bug 29761
ACTION A-652-05: MHK to implement fix mentioned in comment 2 of bug 29740
ACTION A-652-06: MHK to Implement change in comment 4 in bug 29765. If you have a single digit picture then there is no truncation.
ACTION A-652-07: MHK to propose wording that addresses Bug 29785. Issue: If you have tried validation against the schema and it has
failed because of an invalid xsi type the rule says you must carry on to do rule 2. (note this was not the intent)
ACTION A-652-08: MHK to implement the proposal in comment 0 of bug 29755
ACTION A-652-09: MHK to implement in spec the proposal in comment 1 of bug 29800
ACTION A-652-10: Tim to write test cases for transform and load-query-module for when these functions are not supported. See bug 29800
ACTION A-652-11: O'Neil to update the public website with the latest results on the full test suite. This should include the static typing test cases.
ACTION A-652-12: O’Neil to add note in the following test case description to say 'tests case is not representable in XQueryX': Axes112, K2-NameTest-21, K2-NameTest-23
ACTION A-652-13: Michael Sprbrg-McQn to address the issue raised in August message 0: https://lists.w3.org/Archives/Public/public-xsl-query/2016Aug/0000.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Aug/0000.html>
Make change: Namespaced-Name were inlined in method-type and in json-node-output-method-type
ETA one week.
>
>
>
> ===================================================
> Joint XML Query Working Group and XSL Working Group
> ===================================================
>
>
> J1. Administrative Items
>
> J1.1 Selection of secretary(s)
O’Neil took these minutes
>
>
>
> 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.
>
> 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
> Adam Retter - 2016-06-21, 2016-01-26, 2015-10-20
> 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
>
>
>
> J1.2 Call the Roll -- NOT DONE DURING TELECONFERENCE
>
>
Andy, O’Neil, Mike Kay, Michael Sprbrg-McQn, Tim Mills, Liam Quin, Josh Spiegel, Michael Dyck, Abel Braaksma
>
>
> 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 #651 (MikeK)
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Jul/0030.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Jul/0030.html>
Approved
>
>
> 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-649-04: Abel to report test results.
>
> Status: Pending; ETA 2016-08-02
Still pending. ETA 2016-09-20
>
>
> ACTION A-650-07: Action on Jonathan to resolve bug 29721 as described in comment 0. Also, query the document source to ensure that there are not inconsistencies between the error appendix and the main text.
>
> Status: Pending; ETA 2016-09-06
Done.
>
>
> ACTION A-650-08: Action on Abel to implement fn:transform
>
> Status: Pending; ETA 2016-08-02
Still pending. ETA 2016-09-20
>
>
>
>
> J1.5.2 Completed action items
>
>
> 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: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Aug/0000.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Aug/0000.html>
>
>
> ACTION A-650-09: Action on Josh to propose a new test suite feature that allows implementations to filter out tests that require more than 18 digits for xs:decimal.
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Jul/0028.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Jul/0028.html>
>
>
> ACTION A-651-01: MHK to implement the proposal for bug 29722 (fn:sort, array:sort with collations) as amended.
>
> Status: Closed; See
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29722#c6 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29722#c6>
>
>
> ACTION A-651-02: MHK to implement resolution of bug 29723 (options parameter to map:merge to control duplicates). Proposal in comment 2 accepted, as modified by comment 6, but implementation-dependent rather than implementation-defined.
>
> Status: Closed; See
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29723#c9 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29723#c9>
>
>
> ACTION A-651-03: MHK to implement the decision on bug 29749 (rounding of fractional seconds): adopt the proposal (A) in comment (1).
>
> Status: Closed; See
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29749#c4 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29749#c4>
>
>
> ACTION A-651-04 (Bug 29743: recursive maps) MHK to write a proposal for an fn:find() function. (But note, we are in no way committed to adopting this).
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Jul/0029.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Jul/0029.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
>
> [V45] Joint XML Query/XSL WG meeting schedule
> https://lists.w3.org/Archives/Member/w3c-xsl-query/2016Jul/0003.html <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.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 29758 - [FO31] What is the sort order of errors?
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29758 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29758>
>
> Status: Ready to discuss
MHK summarised bug.
MHK resolved bug in comment 1.
No objects to MHK comment.
ACTION A-652-02: MHK to implement the resolution in comment 1 for bug 29758
>
>
> J4.2.2 Bug 29760 - [FO31] 9.8.4.4 Formatting the Year Component
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29760 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29760>
>
> Status: Ready to discuss
MHK agrees with the bug that a spec change is required
MHK: It is saying if you are formatting the year in roman numerals or similar with no width modifier then it does not get truncated. We have two ifs and no otherwise. Nothing special happens
TimMills: Agrees with MHK.
Liam thinks N mod infinity is N
ACTION A-652-03: MHK to implement the resolution in comment 1 in bug 29760
>
>
> J4.2.3 Bug 29761 - [FO31] width modifier (again)
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29761 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29761>
>
> Status: Ready to discuss
Tim: Suggest looking at the example in the bug.
Do you take the minus into account or do you just count digits?
MHK: Suggests that he will come back with a proposal
ACTION A-652-04: MHK to write proposal to resolve bug 29761
>
>
> J4.2.4 Bug 29740 - [FO31] serialize-xml-139,140
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29740 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29740>
>
> Status: Ready to discuss
Tim: Summarised bug. Was a test bug but became a spec bug in comment 2.
(a) the required type is map{xs:string, xs:string}
(b) the option parameter conventions apply recursively to this map.
MHK: The two statements in comment 2 (above) are a contradiction.
MHK: Took a look at the F+O spec. Note 2 underneath the table. Proposal to delete the sentence that starts with: The option parameter convention apply recursively….
Andy asked if anyone object to MHK proposal?
Josh: Asked question What is the downside to having this because although it is a corner case. I can imagine the character mapping comes for a configuration files like an XML document where the value or the mapping can be untyped atomic value.
Why not have this? Why should that case fail
TimMills: Because would not have the right type. Spec says should be grin string to string.
Josh: Why not? Is it easier to update the spec or some other reason.
MHK: It becomes complex to allow conversion of untyped atomic to string in this context
Josh: Might be complex to describe but from a users prospective it would work as expected and not go around casting.
MHK: Thinks it would be marginal benefit for extra benefit in the spec.
Andy asked if there is any objection to MHK’s proposal
No objection
DECISION: The WG accepted MHK proposal in comment 2 of bug 29740
ACTION A-652-05: MHK to implement fix mentioned in comment 2 of bug 29740
>
>
> J4.2.5 Bug 29765 - [FO31] 9.8.4.4 Formatting the Year Component
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29765 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29765>
>
> Status: Ready to discuss
Tim: Still thinks there is a problem with (c).
MHK: We should clarify it defining a max width what we meant to say was include finite upper bound on the width. Other issue in the absence of width modifier what do we do if …. Open to suggestions
MHK: We currently have this rule for the minimum of two. We should change how this works. If the supplied picture is of length one then we don’t truncate.
Abel: Agrees with this as it is consistent
Proposal in comment 4. If you have a single digit picture then there is no truncation
TimMills: The node supplied as $input must be one of the following: [err:FOJS0006]
Abel: In FO30 we said it clearly, so I think we made the right bw-compat decision on "Y0": <quote>A format token consisting of a single digit, such as 1, does not constrain the number of digits in the output</quote>)
DECISION: WG agreed to accept proposal in comment 4 to resolve bug 29765. If you have a single digit picture then there is no truncation.
ACTION A-652-06: MHK to Implement change in comment 4 in bug 29765. If you have a single digit picture then there is no truncation.
>
>
> J4.2.6 Bug 29785 - [FO31] 17.5.4 fn:xml-to-json
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29785 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29785>
>
> Status: Ready to discuss
TimMills summarised bug.
Two test case which highlights the problem where some element was annotated xsi type xs:string. when Microsoft validating it said that was invalid.
The assertion expected to pass so we had to ignore the xsi type attribute
Tim: If you have validated it then we just go with it. If we have not valid it then we do something different
MHK: Rule 2 only applied to untyped nodes. This rule was removed because it should be accepted if be validated against a different schema so long as it validate against this one.
A more restrictive schema could have been defined from a less restrictive schema.
Test case: xml-to-json-045
Andy suggested that we think about this bug and come back to it next week
cmsmcq: Does the rule do any harm? Leans towards including the possibly redundant rule in case of doubt. But it might make people wonder.
MHK: Has a different view on the bug. If you have tried validation against the schema and it has failed because of an invalid xsi type the rule says you must carry on to do rule 2. This was not the intent.
ACTION A-652-07: MHK to propose wording that addresses Bug 29785. Issue: If you have tried validation against the schema and it has failed because of an invalid xsi type the rule says you must carry on to do rule 2.
(note this was not the intent)
>
>
> J4.2.7 Bug 29791 - [XP31] Non-deterministic with respect to ordering
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29791 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29791>
>
> Status: Ready to discuss
Abel summarised bug.
MHK: Comments are valid. Bug should be editorial.
Andy changed bug to editorial.
>
>
> J4.2.8 Bug 29755 - [FO31] Options with no specified default
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29755 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29755>
>
> Status: Ready to discuss
DECISION: WG accepts resolution in comment 0 of bug 29755
ACTION A-652-08: MHK to implement the proposal in comment 0 of bug 29755
>
>
> J4.2.9 Bug 29797 - [FO31] Latest Unicode version is 9.0, not 6.0
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29797 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29797>
>
> Status: Ready to discuss
Change bug to editorial
>
>
> J4.2.10 Bug 29800 - [FO31] fn:load-xquery-module, fn:transform
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29800 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29800>
>
> Status: Ready to discuss
Tim: Summarised bug
MHK: Clarified the meaning. You have to implemented the function but it is allowed to report an error if you cannot do with some error codes.
Tim: Have test cases if we don’t support the function.
DECISION: WG accepted resolution in comment 1 of bug 29800.
ACTION A-652-09: MHK to implement in spec the proposal in comment 1 of bug 29800
ACTION A-652-10: Tim to write test cases for transform and load-query-module for when these functions are not supported. See bug 29800
>
>
>
> 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.3.1 Problem with schema
https://lists.w3.org/Archives/Public/public-xsl-query/2016Aug/0000.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Aug/0000.html>
ACTION A-652-13: Michael Sprbrg-McQn to address the issue raised in August message 0: https://lists.w3.org/Archives/Public/public-xsl-query/2016Aug/0000.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Aug/0000.html> Namespaced-Name were inlined in method-type and in json-node-output-method-type
ETA one week.
>
>
> 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 29743 - XPath 3.1 maps recursive descent
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29743 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29743>
>
> Status: Ready to discuss; See Mike Kay's proposal for map:find:
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Jul/0029.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Jul/0029.html>
MHK summarised bug. External bug report commenting on the inability to do deep searching of josh like structures. MHK produced spec of this function. Before the meeting he thought that this
function did not need to be this complicated. Idea Look for a particular key in any map that is reachable by mays and arrays. Scanning down through sequences, maps and arrays but not in nodes.
Result is an array. One entry for each hit (work need here on spec).
Jonathan: Add one note: Reason for having it being an array is that we might have zero or more than one entry in one of the item.
Follow-up by Abel: https://lists.w3.org/Archives/Public/public-xsl-query/2016Jul/0033.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Jul/0033.html>
Abel: Suggest to add a one argument signature which is similar to what Mike proposed. Mentioned example in email: Expect result is not implementation dependent but
Mike had a questioned example in regards to Abel’s email. Extended $keys to except a sequence rather than just a single value. But this has not been explained. Correct interpretation made.
Jonathan: Agreed with Mike’s question. Thought it was somewhat too clever.
mdyck: you could still define map:find#1 without defining it as that shorthand
Josh: $map?customers?* ! map:find("line items”)
MHK asked Josh if we could use the arrow operator
Josh: $map?customers?* => map:find("lineitems") => map:find("products”)
Abel thought this could work
Josh: We would like to do some steps with the lookup operator then you would like to do a recursive descend. It would be nice to look like a path expression
MHK: Asked if we could use the arrow operator?
Andy: Asked Josh if this is still supporting Mike’s original proposal.
Andy asked Abel for the sake of simplicity if he would accept Mike’s proposal with his extension.
Abel agreed that he would accept Mike’s proposal.
Abel asked about the second half of his email regarding order of the resulting array.
MHK: Suggested that Abel proposal can be done. But the complexity of defining it might be difficult. but will try to define an order constraint on order of the result rathe
Jonathan: Mentioned about saying Order reserved or arrays and sequences but not items in an map is implementation defined and not say more than that.
MHK: Formalising Jonathan suggestion is tricky but can be done.
Tim Mills: Is it worth bringing things together so that order you visit the keys is the same order by the function used to get the keys out of the map
MHK: We don’t usually add this kind of constraint. But the result order could be defined to reflect the input order
Andy asked WG if there were any objection on accepting Mike’s proposal.
No one objected
….
DECISION: Adopted MHK’s proposal on map:find with some extra words around order
ACTION A-652-01: MHK to implement his proposal on map:find in the F+O spec
>
>
>
> 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
Results submitted by XmlPrime for 3.1 spec, including XQueryX 3.1
WG discussed preliminary version of the test suite reports.
Able to fill gap in fn:transform.
Tim: Results are better than it looks. Bug in a couple tests that should not be reported as they are XQuery 3.0 only test.
O’Neil: Possibly a bug in the stylesheet. I will investigate this further.
ACTION A-652-11: O'Neil to update the public website with the latest results on the full test suite. This should include the static typing test cases.
Tim: Mentioned that there are three tests that are not representable in XQueryX: Axes112, K2-NameTest-21, K2-NameTest-23
Maybe it should be noted on the test case that these are not representable
Jonathan are not all queries in XQuery representable in XQueryX?
Tim: Yes, but these test case when generating the XQueryX are not parse error but returns some other error. i.e. namespace error.
ACTION A-652-12: O’Neil to add note in the following test case description to say 'tests case is not representable in XQueryX': Axes112, K2-NameTest-21, K2-NameTest-23
Josh: XQueryX list of test case that are not convertible are mentioned under test-suite directory under tools. Reason is given for the failure to convert.
>
>
> J4.6.2 Status of 3.1 tests results
>
> Status: Currently three implementers submitted results
>
>
>
> 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
>
> * 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>
>
> (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.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>
>
>
> (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
>
>
>
>
> 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 Thursday, 8 September 2016 10:54:52 UTC