- From: Michael Kay <mike@saxonica.com>
- Date: Tue, 26 Apr 2016 22:28:45 +0100
- To: Public Joint XSLT XQuery XPath <public-xsl-query@w3.org>
MINUTES of XML Query/XSL WG Joint Teleconference #641 2016-04-26
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:
J3.2
J4.2 (F&O)
J4.4 (XPath)
Q2.3 (XQuery)
Q2.4 (XQueryX)
Key:
J = Joint Query/XSLT meeting;
Q = Query-only meeting
Teleconference connection details
---------------------------------
(Member only)
https://lists.w3.org/Archives/Member/w3c-xsl-query/2015Sep/0014.html
SUMMARY OF DECISIONS
====================
Note to secretary: Please insert a summary of all decisions made during
this teleconference at this location in the minutes.
Decisions MUST be clear as to their complete intent. The subject of the
decision should *not* require dereferencing; it is most helpful if
agenda numbers and bug numbers are accompanied by their titles. If a
decision is recorded about the resolution of a bug, the decision must
state exactly what the resolution is (e.g., "Accept the solution in
comment #5", or "Replace the production for XXX with this: <new
production>", or the like. It should be possible to read a decision
months later and be certain what it meant and whether or not it was
properly applied.
DECISION (concerning parsing of colons in map constructor expressions) the WG approved the action that was taken by Michael Dyck on action A-640-02a, reported in https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0030.html, and resolved that no further action was needed on this.
NEW ACTION ITEMS
================
Note to secretary: Please insert all new action items assigned during
this teleconference at this location in the minutes.
Action items MUST make sense even when they are viewed standalone (that
is, not read in the context of the agenda item where they were
assigned). This explicitly requires that all referents (e.g., "this",
"that") be made clear. Action items such as "Ralph to resolve this
problem" are DISALLOWED. It takes a scribe only a few additional
minutes to ensure that action items are clear, while it takes the entire
WG considerable effort to constantly research the meaning of unclear
action items. The subject of the action item should *not* require
dereferencing; it is most helpful if agenda numbers and bug numbers are
accompanied by their titles.
ACTION A-641-01 on Liam to make the front page of the old test suite documentation (https://dev.w3.org/2006/xquery-test-suite/PublicPagesStagingArea/) essentially say that the 1.0 test suite is superseded by the 3.0 test suite (which identifies those tests that are suitable for running under 1.0). Also to update the links (or their annotation) appearing on https://www.w3.org/XML/Query/#hardcore.
ACTION A-641-02 (bug 29555) MK to propose a precise algorithm for computing min and max width of a format-date component; also define an error when min>max.
ACTION A-641-03 (bug 29583) Jonathan to add xs:anySimpleType to the list of types for which there is no constructor function.
ACTION A-641-04 (bug 29277) Jonathan to make the editorial changes needed.
ACTION A-641-05 (bug 29509) Jonathan to make a proposal to resolve this bug.
ACTION A-641-06 (bug 29546) OND to implement the agreed resolution: tests that require construction of dates with negative years should have an alternative result of error FODT0001.
ACTION A-641-07 (bug 29573) (fallback language and calendar) OND to implement the resolution: make the test assertion more liberal, ie. do not require anything that the spec doesn't require. (Done by MK after the meeting)
ACTION A-641-08 (bug 29590) (Circularities) OND to implement the resolution: change the test so there is no possibility of infinite function-call recursion
ACTION A-641-09 (bug 29547) (year zero) OND to apply the resolution: make these tests (a) dependent on support for XSD 1.1, and (b) allow an FODT0001 result for implementations whose minimum year is 0001.
ACTION A-641-10 (bug 29589) (multiple module imports) MK to apply documentation changes to explain the expectations of the test suite <module> element. (DONE after the meeting).
ACTION A-641-11 (bug 29592) (array and map prefixes). Action on Tim to resolve the issue in the way suggested in the bug report.
ACTION A-641-12 (bug 29572) (an integer is acceptable where decimal is required) MK to change the expected test results so that an integer is acceptable where the specification mandates a decimal.
ACTION A-641-13 (bug 29571) on Jonathan and Tim to agree a Note to add to the spec to make it clear to readers that when T is a list type, T(x) cast as T will typically fail.
ACTION A-641-14 on Jonathan and Michael Dyck to agree revised wording to resolve the potential ambiguity in the resolution of action A-636-08 as described in https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0020.html.
ACTION A-641-15 (bug 29576) (date/time limits) on Jonathan to apply the proposed text in comment #1 of the bug report.
ACTION A-641-16 (bug 29568) (applet problem with \uHHHH) on MDyck to see if we can find a way forward on this bug.
===================================================
Joint XML Query Working Group and XSL Working Group
===================================================
J1. Administrative Items
J1.1 Selection of secretary(s)
John has been asked to take the minutes. Liam has been asked to stand by.
§§ Neither was available at the start of the call so Michael Kay did the honours.
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
Andy, Jonathan, MK, MD, Josh, O'Neil, MSp-McQ, Liam, Norm (part-time).
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:
§§ None recorded.
J1.3 Approval of agenda
J1.3.1 Additions, deletions, or corrections?
§§ Agenda Approved.
J1.4 Review of recent minutes and administrative items
J1.4.1 Minutes of meeting #640 (O'Neil)
https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0027.html
§§ MDyck amendments in message 0029 noted.
§§ Minutes accepted as amended by the corrections in message 2016Apr/0029.html
J1.5 Review of action items
NOTE: Please be prepared to respond quickly on your action items!
J1.5.1 Outstanding action items
ACTION A-637-02: JRobie to include the note in Comment #8 of Bug 29419. Note also comment #11.
Status: Pending; ETA 2016-04-26
§§ deferred to 17 May.
ACTION A-640-01: Mike Kay to resolve Bug 29570 as described in comment #0
Status: Pending; ETA not specified.
§§ DONE (no action needed, bug was a duplicate)
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
Status: Pending; ETA not specified.
§§ MDyck has split the action into parts (a), (b), (c). Still outstanding.
§§ (a) ETA next week. (b) and (c) ETA TBA.
ACTION A-640-03: Jonathan to document the decision: Partial function application never returns a map or an array. if $F is a map or an array then $F(?) is legal, it returns a function and the function is not a map or an array.
Status: Pending; ETA not specified.
§§ deferred to 17 May.
ACTION A-640-04: Jonathan Robie to resolve Bug #29277 by making the changes from comment #20 items 2 and 5.
Status: Pending; ETA not specified.
§§ deferred to 17 May.
J1.5.2 Completed action items
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
Status: Closed; See
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 in light of
Tim's response wrt fractional seconds in #c2.
Status: Closed; See
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: Closed; See
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: Closed; See
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: Closed; See
https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0019.html
J1.6 Update on related activities
J1.6.1 Update on XSLT WG activities (Sharon, MikeK)
§§ No XSLT meeting last week.
J1.6.2 Update on EXPath/EXQuery CG activities (Mike)
§§ No reported activity.
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/2016Apr/0000.html
§§ Correction: should be [v45]. Takes us to end July.
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 Deprecation of Test Suite 1.0. See
https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0011.html
Status: Ready to discuss
§§ Should we make some change to documentation? Should put a big red flag on
https://dev.w3.org/2006/xquery-test-suite/PublicPagesStagingArea/
ACTION A-641-01 on Liam to make the front page of the old test suite documentation (https://dev.w3.org/2006/xquery-test-suite/PublicPagesStagingArea/) essentially say that the 1.0 test suite is superseded by the 3.0 test suite (which identifies those tests that are suitable for running under 1.0). Also to update the links (or their annotation) appearing on https://www.w3.org/XML/Query/#hardcore.
J4. Active Specification Development
** Note: Full Text 3.1 has been removed from the WG agenda.
If, in the future, there is sufficient interest (i.e. at least two
independent participants to develop the spec and implementations),
then this can be brought back on the agenda.
J4.1 Data Model 3.1 (Norm)
J4.1.0 Internal working draft
http://www.w3.org/XML/Group/qtspecs/specifications/xpath-datamodel-31/html/Overview.html
http://www.w3.org/XML/Group/qtspecs/specifications/xpath-datamodel-31/html/Overview-diff.html
http://www.w3.org/XML/Group/qtspecs/specifications/xpath-datamodel-31/src/changes.txt
(none)
J4.2 Functions and Operators 3.1 (Mike Kay)
J4.2.0 Internal working draft
http://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/html/Overview.html
http://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/html/Overview-diff.html
http://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/src/changes.txt
J4.2.1 Bug 29555 - [FO31] 9.8.4.2 The Width Modifier
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29555
Status: Ready to discuss
§§ Discussed. Should we add an error for min>max? General feeling, yes, we should.
§§ Josh: Some criticism of the way the optional digit signs are being used. MK says that it's consistent with the fractional part of format-number. Tim: do we make the algorithm for computing min and max width? MK. Words need to be written to implement the intent of comment #4. Josh: question about spaces in the picture: MK: I think spaces are just a grouping separator. NO: apparently the text says that whitespace in format-date component specifiers is ignored. We can't change this for back-compat reasons.
ACTION A-641-02 (bug 29555) MK to propose a precise algorithm for computing min and max width of a format-date component; also define an error when min>max.
Leave bug open for now.
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
(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-diff.html
http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/src/changes.txt
J4.4.1 Bug 29583 - [XP31] No constructor for xs:anySimpleType
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29583
Status: Ready to discuss
§§ Agreed to add xs:anySimpleType to the list of types for which there is no constructor function.
§§ ACTION A-641-03 (bug 29583) Jonathan to add xs:anySimpleType to the list of types for which there is no constructor function.
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
Status: Pending outcome of discussion between editors
§§ Last week we left this for the editors to consult among themselves.
§§ Jonathan: currently we have a couple of possible solutions, one of them involves republishing XDM and the other doesn't.
§§ Resolve the bug.
§§ ACTION A-641-04 (bug 29277) Jonathan to make the editorial changes needed.
J4.4.3 Bug 29509 - Functions: External, Implementation-Defined, Host Language
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29509
Status: Pending resolution of bug 29277
§§ ACTION A-641-05 (bug 29509 Jonathan to make a proposal to resolve this bug.
J4.4.4 Discuss MDyck action (on colons in map constructors)
Outcome of action A-640-02a
https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0030.html
MK: did we decide the change to Wildcard to make ":*" and "*:" a single token rather than two?
MD: this was one of the options for dealing with this problem. We chose a different route. If we can come up with an example where it still makes a difference then we could consider doing this as well, but for the moment we aren't changing it.
DECISION to approve the action that was taken, no further action needed on this.
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
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 29546 - Out-of-range date values
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29546
Status: Ready to discuss
§§ MK presented the problem.
§§ Proposed resolution: mark the tests as allowed to raise FODT0001.
§§ ACTION A-641-06 (bug 29546) OND to implement the agreed resolution: tests that require construction of dates with negative years should have an alternative result of error FODT0001.
J4.6.4 Bug 29573 - format-dateTime-en151, format-dateTime-en152, format-time-en151, format-time-en152
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29573
Status: Ready to discuss
§§ MK: I think CG's criticism of the test is reasonable, the language of the spec is less prescriptive than XSLT 2.0 was. It's not clear how best to deal with it.
§§ MK: proposal is to make the test assertion more liberal, ie. not require anything that the spec doesn't require.
§§ ACTION A-641-07 (bug 29573) (fallback language and calendar) OND to implement the resolution: make the test assertion more liberal, ie. do not require anything that the spec doesn't require. (Done by MK after the meeting)
§§ Bug 29590: circularity.
§§ Proposal is to change the test K2-InternalVariablesWithout-1a so that there is no possibility of infinite function-call recursion.
§§ ACTION A-641-08 (bug 29590) (Circularities) OND to implement the resolution: change the test so there is no possibility of infinite function-call recursion
§§ Bug 29547
§§ MK noted that an implementation might reject year zero either because it implements XSD 1.0, or because it supports XSD 1.1 but has an implementation-defined range of zero to 9999.
§§ ACTION A-641-09 (bug 29547) (year zero) OND to apply the resolution: make these tests (a) dependent on support for XSD 1.1, and (b) allow an FODT0001 result for implementations whose minimum year is 0001.
§§ Bug 29589
§§ MK: do we require all implementations to allow multiple modules with the same URI? (And if so, how would we phrase this requirement?) The current wording in the spec about importing an implementation-defined subset of modules permits implementations to have a restriction of one module per namespace.
§§ Perhaps we should make it clear that implementations are allowed to disallow multiple modules with the same URI, but that we encourage them to allow it?
§§ MK: perhaps the test suite documentation should simply say "This is how we expect modules to work for the purpose of the test suite; it's conceivable you have an implementation that is conformant but can't be made to work this way; if so, don't run these tests". So any test that uses modules has an implicit dependency on being able to configure the product to do modules in the way the test driver expects.
§§ ACTION A-641-10 (bug 29589) (multiple module imports) MK to apply documentation changes to explain the expectations of the test suite <module> element. (DONE after the meeting).
§§ ACTION A-641-11 (bug 29592) (array and map prefixes). Action on Tim to resolve the issue in the way suggested in the bug report.
§§ Bug 29572. Agreed that the expected results of these tests are over-prescriptive: op(decimal, decimal) is allowed to return an integer if the result happens to be an integer.
§§ ACTION A-641-12 (bug 29572) (an integer is acceptable where decimal is required) MK to change the expected test results so that an integer is acceptable where the specification mandates a decimal.
J5. Progression of Work
J5.1 XSLT 3.0, XQuery 3.1, XQueryX 3.1, XPath 3.1, XDM 3.1, F&O 3.1,
Serialization 3.1
J5.1.1 Current status
* In Candidate Recommendation; awaiting implementation reports
J5.1.2 Dependencies inhibiting progression
* Completion of test suite minimum-required-to-declare-victory
* Sufficient implementation experience and reports thereof
* Formal response to all comments, responses accepted by commenters
* PR Transition Request and authorization, PR pub request
* REC Transition Request and authorization, REC pub request
J5.2 Update 3.0
J5.2.1 Current Status
* In Last Call Working Draft
At XML Prague, Liam talked to a few people about XQuery Update but found no great enthusiasm for doing the work. We cannot progress without plans for a test suite and potential implementers. The WG needs to decide what to do with this spec.
Status: Ready to discuss
J5.2.2 Require owner of XQUF 3.0 Test Suite
J5.2.3 Dependencies inhibiting progression
* CR Transition Request and authorization, CR pub request
* Completion of test suite minimum-required-to-declare-victory
* Sufficient implementation experience and reports thereof
* Formal response to all comments, responses accepted by commenters
* PR Transition Request and authorization, PR pub request
* REC Transition Request and authorization, REC pub request
J6. Any other business
J6.1 Consideration of future work
J6.1.1 QT 3.2
The WGs decided that we will finish the 3.1 documents presently under way,
but undertake no new work. Maintenance work should be planned upon for a
period of time after finishing the specifications.
J6.1.2 FT 3.1
Currently inadequate interest and resources
J6.1.3 Update 3.1
Currently inadequate interest and resources
J7. Adjourn
=======================
XML Query Working Group
=======================
Q1. The XML Query WG does not intend to maintains specs earlier than the
3.0 suite of documents; when the 3.1 suite reaches Recommendation,
maintenance of the 3.0 documents will be terminated.
Q1.0 This agenda item is reserved for reporting errors and other
problems reported against the 3.0 (later, 3.1) XML Query WG suite of
specifications.
Q1.1 Bugzilla Bugs filed against the 3.0 suite of XML Query WG documents
(none)
Q2. Active Specification Development
Q2.1 XQuery Update Facility 3.0 (John)
Q2.1.0 Internal working draft
http://www.w3.org/XML/Group/qtspecs/specifications/xquery-update-30/html/Overview.html
http://www.w3.org/XML/Group/qtspecs/specifications/xquery-update-30/html/Overview-diff.html
http://www.w3.org/XML/Group/qtspecs/specifications/xquery-update-30/src/changes.txt
* The WG needs to obtain implementation experience with this document.
Q2.2 XQuery Update Facility 3.0 Requirements and Use Cases (Andy)
See
http://www.w3.org/XML/Group/qtspecs/requirements/xquery-update-30/html/Overview.html
* The WGs need to be certain that this document is completed
(red/yellow/green bullets on requirements, all the use cases intended to
be published) and a decision made to advance it to WG Note.
Q2.3 XQuery 3.1 (Jonathan)
Q2.3.0 Internal working draft
http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/html/xquery-31.html
http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/html/xquery-31-diff.html
http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/src/changes.txt
Q2.3.1 Bug 29571 - [XQ31] [FO31] 3.18.3 Cast
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29571
Status: Ready to discuss
§§ Tim presented the problem. Consensus that although we weren't happy that
xs:NMTOKENS("a b c") cast as NMTOKENS
should fail, we weren't prepared to fix this at this stage. But we should add a note to make the behaviour clear.
§§ ACTION A-641-13 (bug 29571) on Jonathan and Tim to agree a Note to add to the spec to make it clear to readers that when T is a list type, T(x) cast as T will typically fail.
Q2.3.2 Discuss Action A-636-08
See https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0020.html
Status: Ready to discuss
§§ (This was an action on Jonathan which Michael Dyck has pushed back on; he thinks the phrasing of the resolution could be ambiguous.)
§§ ACTION A-641-14 on Jonathan and Michael Dyck to agree revised wording to resolve the potential ambiguity in the resolution of action A-636-08 as described in https://lists.w3.org/Archives/Public/public-xsl-query/2016Apr/0020.html.
Q2.3.3 Bug 29576 - Range of dateTime value missing minimum year details
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29576
Status: Ready to discuss
§§ DECIDED to adopt comment #1
§§ ACTION A-641-15 (bug 29576) (date/time limits) on Jonathan to apply the proposed text in comment #1 of the bug report.
Q2.3.4 Bug 29586 - [XQ31] 2.5.6.2 The judgement subtype-itemtype(Ai, Bi)
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29586
Status: Ready to discuss
§§ MK believes this has been extensively discussed and there is logic behind the way the spec is written. John Snelson is the expert on this!
§§ ACTION on John Snelson to respond to this bug (and on Andy to tell him he has an action...)
§§ Discussion postponed.
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
Q2.4.1 Bug 29568 - [XQX3.1] Incorrect XQueryX conversion of "\u005c"
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29568
Status: Ready to discuss
§§ This is a bug in the XQueryX applets (caused by a bug in JavaCC) that results in the XQueryX conversion of some tests being incorrect.
§§ It could be that there's a subsequent release of JavaCC that fixes it. Or it's open source so we could potentially fix it ourselves.
§§ ACTION A-641-16 (bug 29568) (applet problem with \uHHHH) on MDyck to see if we can find a way forward on this bug.
§§ One possibility is to circumvent the bug by writing the relevant tests a different way, e.g. construct the string containing "\uXXXX" dynamically.
Q3. Test Suite Development
Q3.1 Update Facility 3.0 Test Suite (????)
* Need test suite developer/manager
* Need tests
Q4. Any other business
Q5. Adjourn
Received on Tuesday, 26 April 2016 21:29:21 UTC