- From: O'Neil Delpratt <oneil@saxonica.com>
- Date: Thu, 4 Feb 2016 09:50:25 +0000
- To: public-xsl-query@w3.org
- Message-Id: <0256E310-A732-4F10-8001-247F202F9AAE@saxonica.com>
IRC log of today's call: http://www.w3.org/2016/02/02-xquery-minutes.html <http://www.w3.org/2016/02/02-xquery-minutes.html>
> Changes in this agenda:
Added Agenda items:
Abel requested the addition of : https://lists.w3.org/Archives/Public/public-xsl-query/2016Feb/0000.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Feb/0000.html>
J4.4.2 The judgement subtype-itemtype(Ai, Bi) is incorrect for function(*)
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29414 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29414>
J4.2.3 no error conditions for invalid URI for fn:collation-key
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29406 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29406>
J4.2.4 fn:format-number with xs:double/float and (non-)rounding
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29409 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29409>
J4.2.5 Regex: capturing parentheses inside non-capturing parentheses
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29415 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29415>
J4.4.2 The judgement subtype-itemtype(Ai, Bi) is incorrect for function(*)
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29414 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29414>
J4.6.8 anyURI in fn:collection
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29404 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29404>
SUMMARY OF DECISIONS
====================
DECISION: In relation to bug 29406 Mike will add a cross reference to section 5.3.5
DECISION: Close bug 29409 with no action
DECISION: Resolve bug 29404 by Add dependency on XSD in the test cases mentioned in the bug
NEW ACTION ITEMS
================
ACTION A-632-01: Andy to contact Jim to make change to the hierarchy diagrams in both XDM and F+O. See bug 29403
ACTION A-632-02: Mike to make the change of adding cross reference to section 5.3.5 in relation to bug 29406
ACTION A-632-03: Mike to add a clarification text and example to bug 29415
ACTION A-632-04: Jonathan to refine wording in section 3.1.5.1Evaluating Static and Dynamic Function Calls. Based on the following points: 1. provide formal definitions for "host language function", "implementation-defined function", link to "external function”. 2. make sure that inline functions and declared functions are well defined as "functions that have bodies”. 3. Change ...F's implementation is a... to ..F is a…
3a. typo: s/an/a in "is an partially applied function,”
ACTION A-632-05: Jonathan to propose a solution to bug 29414
ACTION A-632-06: O’Neil to make dependency on XSD 1.0 on the test cases. Update the bug issue 29404
>
>
>
>
> ===================================================
> Joint XML Query Working Group and XSL Working Group
> ===================================================
>
>
> J1. Administrative Items
>
> J1.1 Selection of secretary(s)
>
> O'Neil has been asked to take the minutes. Michael Sperberg-McQueen has been asked to stand by.
Done
>
>
> 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.
>
>
> Michael Sprbrg-McQn - 2015-10-03, 2015-06-09, 2015-03-03
> Mike Kay - 2015-11-10, 2015-07-15, 2015-04-14
> Michael Dyck - 2015-11-17, 2015-09-01, 2015-03-31
> Josh Spiegel - 2015-12-01, 2015-09-08, 2015-03-24
> Tim Mills - 2015-12-08, 2015-09-15, 2015-04-21
> Norm Walsh - 2015-12-15, 2015-09-22, 2015-05-05
> Jonathan Robie - 2016-01-05, 2015-09-29, 2015-05-12
> John Snelson - 2015-01-12, 2015-07-16, 2015-06-02
> Liam Quin - 2016-01-19, 2015-10-06, 2015-06-16
> Adam Retter - 2015-01-26, 2015-10-20, 2015-04-21
O'Neil Delpratt - 2016-02-02, 2015-10-27, 2015-06-23
>
>
>
> 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>
O’Neil, Liam, Abel Andy, Michael Sperberg-McQueen, Jonathan, Michael Dyck, Michael Kay, Tim Mills, Josh
>
>
> 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 #631 (Adam)
> https://lists.w3.org/Archives/Public/public-xsl-query/2016Jan/0034.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Jan/0034.html>
>
>
Abel and the WG raised concerns that more should be captured from the minutes, including IRC notes.
>
> 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-628-01: Liam to discuss the status of XQuery Update 3.0 at XML Prague.
>
> Status: Pending; ETA 2016-02-13
Not due yet
>
>
> ACTION A-629-02: Jonathan Robie to apply the clarification from the comment 12 of bug 29346 to the spec.
>
> Status: Pending; ETA 2016-02-02
No update
>
>
> ACTION A-629-03: Abel to write test cases for the resolution to bug 29346.
>
> Status: Pending; ETA 2016-02-02
Abel would like to make this dependant on the changes on the spec.
>
>
> ACTION A-629-04: Jonathan Robie to fix bug 29362 by referring to the definition of op:same-key in F&O
>
> Status: Pending; ETA 2016-02-02
No update
>
>
> ACTION A-630-01: Mike Kay to propose a resolution on 29373 Missing error code
> when fn:serialize receives a QName method in no namespace
>
> Status: Pending; ETA not specified.
Not done yet.
ETA 16/02/16
>
>
> ACTION A-630-02: O'Neil to remove reporting of the features that aren't in 3.1
> (static typing, namespace axis) and tests that are not for 3.1
> (e.g. 3.0 or XPath)
>
> Status: Pending; ETA not specified.
ETA 16/02/16
>
>
> ACTION A-630-06: jonathan to check the wordin to make validate {} an error [bug 29370]g
>
> Status: Pending; ETA 2016-02-02
>
No update
>
> ACTION A-631-01: Jonathan Robie to propose a reformulation of XPath 3.1 section 3.1.5.1, bullet-points 2 and 5
>
> Status: Pending; ETA 2016-02-02
No update
>
>
> ACTION A-631-02: Jonathan Robie to make the changes in XPath 3.1 as suggested by Michael Dyck in Bug 29382
>
> Status: Pending; ETA not specified.
>
No update
>
>
> J1.5.2 Completed action items
>
>
> ACTION A-629-01: Jonathan Robie to propose some clarification text to resolve bug 29277.
>
> Status: Closed; Completed in editor's draft
>
>
>
> J1.6 Update on related activities
>
> J1.6.1 Update on XSLT WG activities (Sharon, MikeK)
>
No update. Last weeks meeting cancelled.
XSLT WG meeting in Prague next week.
>
>
> J1.6.2 Update on EXPath/EXQuery CG activities (Mike)
>
>
>
> J1.7 Future Meetings
XSL meeting on the 9th Feb reinstated
XSL meeting on the 16th Feb cancelled.
XSL meeting on the 23rd Feb cancelled.
>
> 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 scheduled.
>
>
> J2. Documents For Review
>
> (none)
>
>
>
> J3. Maintenance Issues
>
> J3.0 The XML Query WG and XSLT WG do not intend to maintains specs
> earlier than the 3.0 suite of documents; when the 3.1 suite reaches
> Recommendation, maintenance of the 3.0 documents will be terminated.
>
> This agenda item is reserved for reporting errors and other problems
> reported against the 3.0 (later, 3.1) suite of specifications.
>
>
> J3.0.1 Concerns raised by the XSLT working group in regards to potential
> completion delays of XSLT 3.0 if XPath 3.0 is made obsoleted by 3.1
>
> Status: Pending the outcome of Abel's review of 3.0 bugs/errata.
> Any change to the status of the 3.0 specs requires explicit XSL WG
> consultation.
>
>
> J3.1 Bugzilla Bugs filed against the 3.0 suite of joint XML Query WG and
> XSLT WG documents
>
> (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 29373 - Missing error code when fn:serialize receives a QName method in no namespace
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29373 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29373>
>
> Status: Pending completion of A-630-01
Still pending
J4.4.2 The judgement subtype-itemtype(Ai, Bi) is incorrect for function(*)
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29414 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29414>
Mike says this is trivial, but does not know how to update the diagrams
Liam mentioned that Jim Melton edited the diagram
ACTION A-632-01: Andy to contact Jim to make change to the hierarchy diagrams in both XDM and F+O. See bug 29403
J4.2.3 no error conditions for invalid URI for fn:collation-key
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29406 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29406>
Mike gave a summary of the bug issue.
Mike: The only change required might be cross reference to where the rules are described
Abel: How does that relate to the quote sentence in the original description
Mike: That is true of all functions that accepts a collationURI. It is there but hated. No intention to change it
Abel: To know something is relative it has to first be a URI. If we cannot deduct that because any string can go in a collation then you cannot determine it is a relative reference.
cmsmcq: It is defined as being a URI. The problem is many system have the donation of where the difference between legal URI and strings that are not URI.
Abel: Resolve URI is required to throw an error if it is not a valid URI
Abel: 4 error codes for resolve URI . There are three rules get it to throw. One of those is if it does not follow the RFC rules.
Mike: If the base URI is valid then relative URI would usually succeed. It is hard to come up with something that is invalid
cmsmcq: Should be able to come up with something outside of the character set. But since LEIRI is allowed
Mike: example %gg can be used to make a invalid URI
IRC ============
cmsmcq_: w.r.t. “It should be a URI but you don’t have to reject invalid URIs”, it may also be noted that many systems have no real idea what counts as a valid and what as an invalid URI
cmsmcq: resolve URI
Abel: http:\\test <smb://test>
liam: [ a LEIRI should probably also be accepted by most actual implementations]
Invalid URI:
http%gg
================
Abel: asks if we should say something in this function that resolving the the URI should not throw?
Mike propose to do nothing, but only to add a cross reference to the general rules
Mike Kay thinks URI for collation is not used in practice
Mike seen where you can pretend to resolve a URI because you can choose what URIs to recognise.
For example resolving anything ending in the word french as the collation for french regardless of what it starts with. this is within the rules.
cmsmcq: Unusual proxy
DECISION: In relation to bug 29406 Mike will add a cross reference to section 5.3.5
Abel is happy with the decision
ACTION A-632-02: Mike to make the change of adding cross reference to section 5.3.5 in relation to bug 29406
J4.2.4 fn:format-number with xs:double/float and (non-)rounding
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29409 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29409>
Mike: This area of the spec has always been vague. That is why it is a SHOULD rather than MUST.
Abel: This is something we would want to do
============
IRC:
cmsmcq_: The bug says “I fail to see how 100000000 is preferred over 100000001”
cmsmcq_: the first has one digit, not counting trailing zeros
cmsmcq_: the second has ten (or however many)
============
Abel: Section 6: What ever your doing must be convertible back to the same xs:double or xs:float. Think that we can close with no action
DECISION: Close bug 29409 with no action
Abel raised issue with QT3 tests that should accept a range of values.
Abel to raise another bug against the QT3 test suite
J4.2.5 Regex: capturing parentheses inside non-capturing parentheses
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29415 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29415>
Abel: Asks the question on applying the example of fn:replace with the arguments what would you expect: cd or d?
Mike: Will capture the c as well as the d because it is non-capturing
cmsmcq: The first pair of the parenthesis matches the c.
Abel: Issue with capturing parenthesis inside a no-capturing parenthesis
============
IRC:
liam: $ echo abcd | perl -p -e 's/a(?:b(c))/$1/'
liam: cd
liam: non-capturing *only* means that the ( isn't numbered, does not mean "discard contents”
liam: [(] indeed also doesn't count and neither does \(
liam: s/top-level/entire/
============
Abel suggests adding some explanation somewhere to make it clearer.
Mike Kay states that adding a note in the XML schema will not help because it is very informal. There is a risk of getting it wrong if we try to make it more formal.
Josh: returning cd
============
IRC:
cmsmcq_: Would an example help?
cmsmcq_: a(?:b(c))
cmsmcq_: ___1___
liam: similarly replace("abcde", "(ab(?:.)de)", "$1") => “abcde"
cmsmcq_: I think the solution here is not formality but one or two examples showing the numbering of parenthesis pairs and the text matched
cmsmcq_: perhaps s/the position of the opening parenthesis/the position of the opening non-capturing parenthesis/ ?
============
ACTION A-632-03: Mike to add a clarification text and example to bug 29415
>
>
>
> 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 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: Pending completion of A-631-01
Bug issue discussed
Jonathan: In the Spec section 3.1.5.1: Part 5 has been restructured. Did not see the need for 2 bullet points in 5a. Discussed points with the Haskell group on IRC. If it is partial function item you return a function item.They suggested partial function application and he took it. Also took ‘a fixed position is an argument/parameter’.
Jonathan: We need definition of host language
Mike Kay and Abel thinks that the restructured section is a great improvement
=================
IRC:
cmsmcq_: [JR noted that ‘implementation-defined function’ needs to be defined; perhaps 2.2 Static Context is the right place to add it? In the bullet item for statically known function signatures
cmsmcq_ doesn’t understand how AB finds 4 occurrences; i find only 3.
jrobie: cmsmcq, we need to define each of these kinds of functions. I'd like to do that in one place. Currently, the section called Functions gives the properties of a function item, I'm not sure if there is a better place.
Abel: [Definition: External functions are functions that are implemented outside the query environment.] For example, an XQuery implementation might provide a set of external functions in addition to the core function library described in [XQuery and XPath Functions and Operators 3.1]. External functions are identified by the keyword external. The purpose of a function declaration for an external
Abel: function is to declare the datatypes of the function parameters and result, for use in type checking of the query that contains or imports the function declaration.
=================
Abel: implementation-dependent - question raised in what happens in host language .External function has not been defined in XPath but is defined in XQuery. Host language function has not been explained. Needs defining.
=================
IRC:
jrobie: 1. provide formal definitions for "host language function", "implementation-defined function", link to "external function"
cmsmcq_: jrobie, you may be right; I’m agnostic. 2.2 could hold definitions of other kinds of functions. but 4.18 in XQuery would probably also work
jrobie: 2. make sure that inline functions and declared functions are well defined as "functions that have bodies”
=================
Abel: Inline function need to be well defined
Jonathan: 1) Need a section on the properties of functions. 2) Different kind of function implementation that can exist. 3) Need to define what we mean by a function that has a function body. 4)
Michael Dyck: Suggested re-wording in 5b) If F is one of these things
Abel: Suggestion: If F has an implementation of a built-in function and its name and signature match that function
Jonathan:
=================
IRC:
Jonathan: The function to be called or partially applied (call it F) is obtained as follows:
Jonathan: name: Absent.
Jonathan: parameter names: The parameter names of F, removing the parameter names at the fixed positions. (So the function's arity is the arity of F minus the number of fixed positions.)
Jonathan: signature: The signature of F, removing the parameter type at each of the fixed positions.
Jonathan: implementation: The implementation of F, associated with the same contexts as in F. If these contexts are absent in F, it is associated with SC and DC.
Jonathan: nonlocal variable bindings: The nonlocal variable bindings of F, plus, for each fixed position, a binding of the converted argument value to the corresponding parameter name.
=================
=================
IRC:
Jonathan: If F's implementation is a built-in function,
Abel: A house has a door. We have three houses. If a door is one of these houses... then
Jonathan: f.implementation
Abel: That is confusing properties with objects.
Jonathan: paf.implementation = F.implementation
Jonathan: conflating: f is a function, F.implementation is a function
Abel: I don't agree with that conflation...
Abel: we also don't say if f is a function, f.signature is a function, even though we often see a signature as the definition of a function
Jonathan states this from the working draft:
jrobie: F's implementation is invoked with the converted argument values using the contexts it is associated with in F. If these contexts are absent in F, it is associated with SC and DC.
jrobie: we invoke functions,not implementations of functions
jrobie: the function is invoked using its implementation
=================
Andy:
=================
IRC:
jrobie: If <var>F</var>'s implementation => If If <var>F</var>
Abel: 3a. typo: s/an/a in "is an partially applied function,"
mdyck: they're different numbers in XPath and XQuery
liam surprised to hear xpath doesn't have external functions, since implementations generally seem to
[jrobie: iv. If F is an partially applied function, the implementation of F is called, supplying a binding of the converted argument value to the corresponding parameter name for each fixed position.
Abel: The dynamic context for this evaluation is obtained by taking the dynamic context of the InlineFunctionExpr that contains the FunctionBody, and making the following changes:
jrobie: liam: xpath is intended to be embedded in some other language, so what does external mean?
jrobie: liam: i think it would have to be external to whatever embeds xpath
jrobie: Abels and pears?
liam: hmm ok. e.g. php lets you call php functions from xpath, so does perl, maybe python, and some C APIs.
jrobie: liam, those are all host language functions
jrobie: iv. If F is an partially applied function, the implementation of F is called, supplying a binding of the converted argument value to the corresponding parameter name for each fixed position.
jrobie: If <var>F</var> is an <termref def="dt-partially-applied-function">partially applied function</termref>, the implementation of <var>F</var> is called.
jrobie: supplying a binding of the value for each fixed position to the corresponding parameter name.
jrobie: supplying a binding of the value for each fixed position to the corresponding parameter.
Abel: "from the local variable bindings of F"
Abel: (add that, or something like it)
=================
ACTION A-632-04: Jonathan to refine wording in section 3.1.5.1Evaluating Static and Dynamic Function Calls. Based on the following points: 1. provide formal definitions for "host language function", "implementation-defined function", link to "external function”. 2. make sure that inline functions and declared functions are well defined as "functions that have bodies”. 3. Change ...F's implementation is a... to ..F is a…
3a. typo: s/an/a in "is an partially applied function,”
Michael Dyck: Partially applied function and function body are not mutually exclusive. An implementation is not a function
Jonathan: Disagrees. Suggests corresponding via email on the point Michael Dyck raised.
J4.4.2 The judgement subtype-itemtype(Ai, Bi) is incorrect for function(*)
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29414 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29414>
Jonathan: The current text is wrong. Not sure if the new text is right either.
Josh: Editorial in XPath but not in XQuery
ACTION A-632-05: Jonathan to propose a solution to bug 29414
>
>
>
> 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 Bug 29381 - [QT3] resolve-uri-28 expects error FORG0002, but seems valid according to RFC-3986
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29381 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29381>
>
> Status: Ready to discuss
>
>
> J4.6.4 Bug 29395 - [QT3] Test K2-DataFunc-6 expects validation but this is not visible in the metadata
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29395 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29395>
>
> Status: Ready to discuss
>
>
> J4.6.5 Bug 29398 - [QT3] Base uri with parse-xml in fn-parse-xml-011
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29398 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29398>
>
> Status: Ready to discuss
>
>
> J4.6.6 Bug 29400 - [QT3] fn-avgflt2args-1 result type
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29400 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29400>
>
> Status: Ready to discuss
>
>
> J4.6.7 Bug 29401 - [QT3] numeric-unary return type
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29401 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29401>
>
> Status: Ready to discuss
J4.6.8 anyURI in fn:collection
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29404 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29404>
cmsmcq: It might mean that XSD 1.0 did not define valid anyURI properly
DECISION: Add dependency on XSD in the test cases mentioned in bug 29404
ACTION A-632-06: O’Neil to make dependency on XSD 1.0 on the test cases. Update the bug issue 29404
>
>
>
> J5. Progression of Work
>
> J5.1 XSLT 3.0, XQuery 3.1, XQueryX 3.1, XPath 3.1, XDM 3.1, F&O 3.1,
> Serialization 3.1
>
> J5.1.1 Current status
>
> * In Candidate Recommendation; awaiting implementation reports
>
>
> J5.1.2 Dependencies inhibiting progression
>
> * Completion of test suite minimum-required-to-declare-victory
>
> * Sufficient implementation experience and reports thereof
>
> * Formal response to all comments, responses accepted by commenters
>
> * PR Transition Request and authorization, PR pub request
>
> * REC Transition Request and authorization, REC pub request
>
>
>
> J5.2 Update 3.0
>
> J5.2.1 Current Status
>
> * In Last Call Working Draft
>
>
> J5.2.2 Require owner of XQUF 3.0 Test Suite
>
>
> J5.2.3 Dependencies inhibiting progression
>
> * CR Transition Request and authorization, CR pub request
>
> * Completion of test suite minimum-required-to-declare-victory
>
> * Sufficient implementation experience and reports thereof
>
> * Formal response to all comments, responses accepted by commenters
>
> * PR Transition Request and authorization, PR pub request
>
> * REC Transition Request and authorization, REC pub request
>
>
>
> J6. Any other business
>
> J6.1 Consideration of future work
>
> J6.1.1 QT 3.2
>
> The WGs decided that we will finish the 3.1 documents presently under way,
> but undertake no new work. Maintenance work should be planned upon for a
> period of time after finishing the specifications.
>
>
> J6.1.2 FT 3.1
>
> Currently inadequate interest and resources
>
>
> J6.1.3 Update 3.1
>
> Currently inadequate interest and resources
>
>
>
> J7. Adjourn
>
>
>
>
> =======================
> XML Query Working Group
> =======================
>
> Q1. The XML Query WG does not intend to maintains specs earlier than the
> 3.0 suite of documents; when the 3.1 suite reaches Recommendation,
> maintenance of the 3.0 documents will be terminated.
>
> Q1.0 This agenda item is reserved for reporting errors and other
> problems reported against the 3.0 (later, 3.1) XML Query WG suite of
> specifications.
>
>
> 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
>
>
>
Received on Thursday, 4 February 2016 09:51:14 UTC