- From: O'Neil Delpratt <oneil@saxonica.com>
- Date: Thu, 29 Oct 2015 01:41:45 +0000
- To: public-xsl-query@w3.org
- Message-Id: <47C760E8-FB59-423E-9A22-5E15E0FA2756@saxonica.com>
SUMMARY OF DECISIONS
====================
DECISION: The WG agreed upon proposal in bug 29184 that we should by default cast the first argument of string-join only but not the second.
DECISION: Resolved Bug 29027 with proposal. Any other side issue WG requested that a new bug be opened
DECISION: Q2.3.5. WG has agreed to refactor the grammar using the EnclosedExpr in the node constructors, but in the case of the element constructor we shall not use it in the first argument because it cannot be an empty sequence.
DECISION: To introduce a standard serialisation property. Called newline-representation
NEW ACTION ITEMS
================
NEW Action A-621-01: Change needed in the test case contextDecl-022. See comment 2 in bug 29027
New Action A-621-02: On Jonathan to implemented proposal of bug 29225 in the XQuery Spec.
New ACTION A-621-03: Michael Dyck to update the grammar for empty expressions in braces. ETA: 2015-11-02 (Morning)
New ACTION A-621-04: Jonathan to update the words in in Xquery for empty expressions in braces ETA: 2015-11-03
NEW ACTION A-621-05: Mike to resolve the bug 29216 to add his proposal
NEW ACTION A-621-06 Andy to make the change of Serialization of newlines in the spec.
NEW ACTION A-621-07: Mike to respond on behalf of the XSL WG to Daniel from the EXI WG in regards to October 2015 message #0 on the schema extension.
NEW ACTION A-621-08. Jonathan to make the change described in bug 29227, but limit it to context size and make it XPath only
> Andy will chair this meeting.
>
>
> ===================================================
> 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. Mike has been asked to stand by.
Minutes taken by O'Neil
>
>
> 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-06-09, 2015-03-03, 2014-11-25
> Mike Kay - 2015-07-15, 2015-04-14, 2015-01-06
> John Snelson - 2015-07-16, 2015-06-02, 2015-02-11
> Loren Cahlander - 2015-07-17, 2015-05-19, 2015-02-10
> Michael Dyck - 2015-09-01, 2015-03-31, 2014-12-16
> Josh Spiegel - 2015-09-08, 2015-03-24, 2014-12-09
> Tim Mills - 2015-09-15, 2015-04-21, 2015-02-03
> Norm Walsh - 2015-09-22, 2015-05-05, 2015-01-27
> Jonathan Robie - 2015-10-29, 2015-05-12, 2015-01-13
> Liam Quin - 2015-10-06, 2015-06-16, 2015-03-10
> Adam Retter - 2015-10-20, 2015-04-21, 2015-01-20
O'Neil Delpratt - 2015-10-27, 2015-06-23, 2015-03-17,
>
>
>
> J1.2 Call the Roll -- NOT DONE DURING TELECONFERENCE
>
>
Present:
Andy Coleman, Jonathan Robie, Michael Kay, Tim Mills, O’Neil Delpratt, Michael Dyck (attended first hour)
>
>
> Regrets:
>
>
Michael Dyck (Partial regrets)
Josh Spiegel
Norm Walsh
>
>
> J1.3 Approval of agenda
>
> J1.3.1 Additions, deletions, or corrections?
>
Added Q2.3.5 - Bug 29185: Discuss the extent of changes required for empty expressions in curly braces.
Action A-620-02 corrected in title: Bug 29184 - Modify fn:string-join to accept xs:anyAtomicType* instead of xs:string*
>
>
> J1.4 Review of recent minutes and administrative items
>
> J1.4.1 Minutes of meeting #620 (Adam)
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0055.html <https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0055.html>
Accepted as true record
>
>
>
> 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-579-18: Jonathan to write change proposal to support update of
> maps and arrays. (See agenda item Q2.1.1)
>
> Status: Pending; ETA 2015-11-24
Not due
>
>
> ACTION A-585-04: Jonathan to write a concrete proposal for XQuery Update
> 3.1 that makes preservation of node identity implementation defined at
> the persistence layer.
> See https://lists.w3.org/Archives/Member/w3c-xsl-query/2014Nov/0012.html <https://lists.w3.org/Archives/Member/w3c-xsl-query/2014Nov/0012.html>
>
> Status: Pending; ETA 2015-11-24
Not due
>
>
> ACTION A-614-01 on JRobie to work with Zed to build FT 3.1 docs before
> checking them in.
>
> Status: Pending; ETA 2015-10-27
Close. See: ttps://lists.w3.org/Archives/Member/w3c-xsl-query/2015Oct/0002.html <ttps://lists.w3.org/Archives/Member/w3c-xsl-query/2015Oct/0002.html> (although posted to the members only list)
>
>
> ACTION A-614-13 on Michael Dyck to resolve Bug 29027.
>
> Status: Pending; ETA 2015-10-27
Close. See message: https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0064.html <https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0064.html>
NEW Action A-621-01: Change needed in the test case contextDecl-022. See comment 2 in bug 29027
>
>
> ACTION A-618-01: Loren to change the schema for serialization to allow
> for EQNames.
>
> Status: Pending; ETA not specified.
Leave open
>
>
> ACTION A-619-01: Liam to add links to new mailing list onto XQuery group
> page
>
> Status: Pending; ETA not specified.
Leave open
>
>
> ACTION A-619-02: Mike to move Bug 29146 to XSLT agenda
>
> Status: Pending; ETA 2015-10-27
Close. It is now on the agenda. Concerned that there might be a timing issue to resolve the bug, but will try to prioritise it.
>
>
> ACTION A-620-01 Jonathan Robie to come up with the wording for solving Bug 4378.
>
> Status: Pending; ETA not specified.
New ETA: 2015-10-27
>
>
> ACTION A-620-02 Mike Kay to close and resolve Bug 29186 as proposed by Josh.
>
> Status: Pending; ETA not specified.
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29184 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29184>
Action corrected: Bug 29184 - Modify fn:string-join to accept xs:anyAtomicType* instead of xs:string*
>
>
> ACTION A-620-03 Jonathan Robie to propose a resolution of Bug 29192
>
> Status: Pending; ETA not specified.
Close. See: https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0067.html <https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0067.html>
>
>
>
>
> J1.5.2 Completed action items
>
>
> ACTION A-613-30: Jonathan Robie to editorially resolve bug
> 27059. Include the example of function coercion against a map item
> from comment 4 of bug 27059.
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=27059#c4 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=27059#c4>
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0056.html <https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0056.html>
>
>
> ACTION A-619-06: jrobie to adopt 29119 and close the bug, e.g. using
> [[
> xs:error is a type that has no instances; it was defined in XML Schema
> in the
> interests of making the type system complete and closed, and it is also
> available in XQuery/XPath for similar reasons. Although the practical
> uses of
> xs:error are limited, they are well-defined, and are consistent with the
> fact
> that xs:error is defined as a union type with no member types. For
> example: (X
> instance of xs:error) is always false, etc etc
> ]]
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0053.html <https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0053.html>
>
>
> ACTION A-619-07: jrobie to adopt 29170 comment 2 and close the bug,
> using
> Don't say that users can create annotations or assertions, they can't;
> annotations and assertions should behave in the same way as
> pragmas for unrecognized local names / URI; this includes its error
> behaviour
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0054.html <https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0054.html>
>
>
> ACTION A-620-04 Michael Dyck to resolve Bug 29185 by accepting the proposal.
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0057.html <https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0057.html>
>
Follow-up discussion from Mike and Tim. Tim suggested that there are other expressions that use the syntax.
Mike: There needs to be some discussion on what curly braces is allowed to be empty.
Andy requested that we added agenda item for this discussion Q2.3.5
>
>
> J1.6 Update on related activities
>
> J1.6.1 Update on XSLT WG activities (Sharon, MikeK)
Busy trying to get done the admin task to get spec to candidate recommendation. Tasks including documenting test suite.
>
>
>
> J1.6.2 Update on EXPath/EXQuery CG activities (Loren)
No update
>
>
>
> J1.7 Future Meetings
>
> J1.7.1 QT Meeting Schedule
>
> [V43] Joint XML Query/XSL WG meeting schedule
> https://lists.w3.org/Archives/Member/w3c-xsl-query/2015Jul/0038.html <https://lists.w3.org/Archives/Member/w3c-xsl-query/2015Jul/0038.html>
>
>
> J1.7.2 Future F2F Meetings
>
> J1.7.2.1 Other future F2F meetings
>
> There is interest in a possible F2F in conjunction with XML Prague in
> February 2016.
>
>
> 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
>
> J3.1.1 Bugzilla Bug 24568, Is the type system really a lattice? Or just
> a partially ordered set?
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=24568 <http://www.w3.org/Bugs/Public/show_bug.cgi?id=24568>
>
> Status: Fixed in Data Model 3.1; not expected to be addressed in Data
> Model 3.0
>
>
> J3.1.2 Bugzilla Bug 25231, [F+O 3.0 ONLY], ISO 8601, and XSD 1.1
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=25231 <http://www.w3.org/Bugs/Public/show_bug.cgi?id=25231>
>
> Status: Fixed in F&O 3.1; not expected to be addressed in F&O 3.0
>
>
> J3.1.3 Bugzilla Bug 26788, [XPath30] XQuery-only errors in XPath 3.0
> specification, like XQST0134"
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=26788 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=26788>
>
> Status: Fixed in XPath 3.1; not expected to be addressed in XPath 3.0
>
>
>
> J4. Active Specification Development
>
> J4.1 Full Text 3.0 (Jim)
>
> J4.1.0 Internal working draft
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-30/html/Overview.html <http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-30/html/Overview.html>
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-30/html/Overview-diff.html <http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-30/html/Overview-diff.html>
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-30/src/changes.txt <http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-30/src/changes.txt>
>
> (none)
>
>
> J4.2 Full Text 3.0 Requirements and Use Cases (Jim)
>
> J4.2.0 Internal working draft
> http://www.w3.org/XML/Group/qtspecs/requirements/xpath-full-text-30/html/Overview.html <http://www.w3.org/XML/Group/qtspecs/requirements/xpath-full-text-30/html/Overview.html>
>
> (none)
>
>
>
> J4.3 Full Text 3.1 (Zed Zhou)
>
> J4.1.0 Internal working draft
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-31/html/Overview.html <http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-31/html/Overview.html>
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-31/html/Overview-diff.html <http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-31/html/Overview-diff.html>
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-31/src/changes.txt <http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-31/src/changes.txt>
>
> Zed Zhou should prepare a draft of this document with at least some
> technical changes (relative to Full Text 3.0) already made so the WGs
> can consider if they like the direction.
>
>
>
> J4.4 Full Text 3.1 Requirements and Use Cases (Zed Zhou)
>
> J4.4.0 Internal working draft
> http://www.w3.org/XML/Group/qtspecs/requirements/xpath-full-text-31/html/Overview.html <http://www.w3.org/XML/Group/qtspecs/requirements/xpath-full-text-31/html/Overview.html>
>
> Zed Zhou should prepare a draft of this document with the necessary
> requirements and at least some use cases for the WGs to consider. We
> should spend significant time determining which requirements the WGs
> will accept.
>
>
>
> J4.5 XPath and XQuery 3.1 Requirements and Use Cases (Jonathan)
>
> J4.5.0 Internal working drafts
> http://www.w3.org/XML/Group/qtspecs/requirements/xquery-31/html/Overview.html <http://www.w3.org/XML/Group/qtspecs/requirements/xquery-31/html/Overview.html>
>
> (none)
>
>
> J4.6 Data Model 3.1 (Norm)
>
> J4.6.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.7 Functions and Operators 3.1 (Mike Kay)
>
> J4.7.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.7.1 Bug 29146 - [FO31] fn:transform options update
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29146 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29146>
Leave open.
>
> Status: Pending completion of A-619-02
>
>
> J4.7.2 Bug 29184 - Modify fn:string-join to accept xs:anyAtomicType* instead of xs:string*
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29184 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29184>
>
> Status: Ready to discuss
Mike summarised details of the bug.
JRobie: Likes the idea proposed
Tim: Thought that we accepted this in last week’s meeting
Amended title in A620-02 to this one
DECISION: The WG agreed upon proposal in bug 29184 that we should by default cast the first argument of string-join only but not the second.
>
>
> J2.7.3 Bug 29216 - JSON Conversion: Handling of surrogate pairs
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29216 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29216>
>
> Status: Ready to discuss
Mike: Summarised bug. Thinks that Christian Gruen is concerned only with the ill-formed surrogates pairs. Might add not that unmatched surrogate don’t cause an error.
Mike to update bug with his comment
NEW ACTION A-621-05: Mike to resolve the bug 29216 to add his proposal
>
>
>
> J4.8 Serialization 3.1 (Michael Sperberg-McQueen, Andy)
>
> J4.8.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>
>
>
> J4.8.1 Bug 29217 - Serialization of newlines
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29217 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29217>
>
> Status: Ready to discuss
Mike: Mentioned that this is a long standing issue. Mike thinks that we should not say anything different that what we currently say, but we should be more descriptive.
Mike: Thinks that this should be a vendor specific serialisation property.
Tim: Mentioned that his implementation has this vendor specific property. There is a argument to make it a standard.
Mike: Thinks that it might not be a good time.
Jonathan and Tim thinks that we should define the serialisation property.
Property naming: newline-representation set to any string. Tim: suggested newline-sequence, newline-characters
MikeK:Applies to all output methods
Andy: What about the defaults?
Mike: Defaults should be what is currently said.
MikeK: Proposal: Note: unpaired surrogates don't cause an error, but the exact treatment might depend on the parsing algorithm used
Options for name of the parameter:
newline-representation
newline-sequence
newline-characters
newline-string
Naming of the property is up to the editor
DECISION: To introduce a standard serialisation property. Called newline-representation
NEW ACTION A-621-06 Andy to make the change of Serialization of newlines in the spec.
>
>
>
> J4.9 XPath 3.1 (Jonathan)
>
> J4.9.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.9.1 Bug 29119 - [XP31] xs:error always raises a type error
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29119 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29119>
>
> Status: Ready to discuss - comment 19?
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29119#c19 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29119#c19>
No one objected. Close from agenda
>
>
> J4.9.2 EXI 'changes' to JSON schema
> See https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0000.html <https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0000.html>
>
> Status: Ready to discuss
WG discussed this message. Agreed that there are some practical difficulties.
NEW ACTION A-621-07: Mike to respond on behalf of the XSL WG to Daniel from the EXI WG in regards to October 2015 message #0 on the schema extension.
>
>
> J4.9.3 Bug 29185 - The expression inside curly braces should be optional
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29185 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29185>
>
> Status: REOPENED: Ready to discuss
Accepted. Mike wanted that semantics need to be recorded. Also to define resolution of the bug.
>
>
> J4.9.5 Bug 29227 - [XP31] Partially-defined focus
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29227 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29227>
>
> Status: Ready to discuss
MikeK: Simplest to just remove the rule.
JRobie: Concerned because this is a fundamental things that we are told is not true based on one example.
MikeK: Described a smaller change: The only flexibility is to say the context size can be absent when the context item and position are know. Only needed for a initial focus when for invoking an XPath expression. Always true in an XPath expression. Thinks we should relax an unnecessary rule.
JRobie: Agrees that we should make the smaller change
JRobie: If any component in the focus is defined, all components of the focus are defined.
JRobie: In summary we are saying path expressions cannot be used in environments where it is empty. Not sure if XQuery has this.
JRObie: Proposed that we should limit it to size and make it XPath only
DECISION: Make change as described in comment 0 of bug 29227 on Partially-defined focus. Limit it to context size and make it XPath only
NEW ACTION A-621-08. Jonathan to make the change described in bug 29227, but limit it to context size and make it XPath only
>
>
>
> J4.10 Grammar Test Applets (Michael Dyck)
>
> J4.10.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.11 QT3 test suite (O'Neil)
>
> J4.11.1 Status report on test suite, harness, tools
>
>
> J4.11.2 Status of 3.1 tests
>
> Status: Coverage is almost complete.
>
>
> J4.11.3 Publication of test suite.
>
> Status: Ready to discuss
>
>
>
> J4.12 FT 3.1 test suite (???)
>
> * Need test suite developer/manager
>
> * Need tests
>
>
>
> 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.1.3 Vote to publish XQuery 3.1 as revised Candidate Recommendation
>
> Status: Ready to discuss
>
>
> J5.1.4 Vote to publish Serialization 3.1 as revised Candidate Recommendation
>
> Status: Ready to discuss
>
>
> J5.2 Full Text 3.0
>
> J5.2.1 Current Status
>
> * Proposed Recommendation
>
>
> J5.2.2 Dependencies inhibiting progression
>
> * REC Transition Request and authorization, REC pub request
>
>
> J5.3 Update 3.0
>
> J5.3.1 Current Status
>
> * In Last Call Working Draft
>
>
> J5.3.2 Require owner of XQUF 3.0 Test Suite
>
>
> J5.3.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
>
> EMC has expressed interest and is willing to provide resources
>
>
> J6.1.3 Update 3.1
>
> Unclear whether there is adequate interest or 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.
>
> Status: Pending completion of ACTION A-592-02.
>
> 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 29027 - [qt3] contextDecl-022
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29027 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29027>
Tim: Added comment 6: Added that if you declare context item and don’t mark it as external and then give it default value then you cannot set it from outside. You can declare the context in the main module and also in the imported library module. As they don’t have to be the same declaration. What happens then? They can be both internal and external.
Mike: Thinks that Tim comment on library module has been covered and that there is no issue. Section 4.17
JRobie: Wants to take this offline.
Tim: Still thinks there is a problem here in the text. The library module has to be external. The main module says it is not. There is nothing in the text that say what to do.
JRobie: Would like time to research this.
Mike: Suggested that we open another bug. As the issue raised by Tim is somewhat widen the scope of the bug.
Andy: Requested that we close this bug.
DECISION: Resolved Bug 29027 with proposal. Any other side issue WG requested that a new bug be opened
>
> Status: Pending completion of A-614-13
>
>
> Q2.3.2 Bug 4378 - error in K2-NodeTest-21
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=4378 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=4378>
>
> Status: Pending completion of A-620-01
>
>
> Q2.3.3 Bug 29192 - [XP31] Non-normative "summary" of casting rules is inaccurate
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29192 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29192>
>
> Status: Pending completion of A-620-03
Close of the agenda
>
>
> Q2.3.4 Bug 29225 - [XQ31] Pragma in no namespace
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29225 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29225>
>
> Status: Ready to discuss
Mike summarised the bug issue.
Comments:
Mike said that he has seen use case to comment (C) in the bug comment 0.
WG accepted Mike’s proposal
DECISION: WG accepted Mike’s proposal in bug 29225.
New Action A-621-03: On JRobie to implemented proposal of bug 29225 in the XQuery Spec.
Q2.3.5 Discuss Bug 29185. Empty expressions in braces
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29185 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=29185>
Andy makes mention to https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0057.html <https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0057.html>
JRobie: Has a strong opinion on this. Any time it makes logical sense for an empty expression to occur then we should be fine. Backward compatible concerns with error conditions that we should expect. Does not want to change the error in conditions in order for us to remain consistent. Thinks that Mike’s proposal comes close to what he thinks should be done.
Andy: This agenda is about broadening out.
JRobie: https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0065.html <https://lists.w3.org/Archives/Public/public-xsl-query/2015Oct/0065.html>
What is the use of unordering an empty sequence. Also what is the use of an empty sequence in a Try expression.
Tim: From last weeks discussions when we made the decision to allow function body not to require a expression was for ease of development as you go typing, as to worry about filling in the body later. Example: TryCatch. We want a syntactic consistency. Now there is less consistency.
Tim use case: Text editor that allows someone to write empty try catch clause without the editor complaining so that he can fill-in blanks later.
Mike: We should be consistent. If function body can return empty sequence then nothing in the curly braces should mean empty sequence
JRobie: Does not want to change error conditions. Compatibly with 3.0 issue.
Mike: Does not see the problem with error conditions. Validate expression is an example. The result is an empty sequence
Tim pointed out that updating empty sequences are different
Tim: Static typing issue. If you find an expression has type of empty sequence we raise an error XPST0005. Except in the case of empty sequence literal. Issue with an empty Function which throws up a conflict.
TimMills: "During the static analysis phase, if the Static Typing Feature is in effect and the static type assigned to an expression other than () or data(()) is empty-sequence(), a static error is raised [err:XPST0005]. This catches cases in which a query refers to an element or attribute that is not present in the in-scope schema definitions, possibly because of a spelling error.”
JRobie example that { } is equivalent to ()
JRobie said that function must say {} is equivalent to { () }
JRobie: As long as we say that they are equivalent then we are fine.
Tim agrees with
JRobie: Concerned that changing each of these things is that each change opens a new discussion and for constructors at least in the body...
Andy said that it would be odd to relax a role that will lead into a error code.
IRC :
jrobie: => want to allow for the second expr
jrobie: TryClause ::= "try" "{" TryTargetExpr “}"
jrobie: try { () } catch * { 0 }
jrobie: CatchClause ::= "catch" CatchErrorList "{" Expr “}"
jrobie: Validate is ok
jrobie: CompDocConstructor ::= "document" "{" Expr “}"
jrobie: CompAttrConstructor ::= "attribute" (EQName | ("{" Expr "}")) "{" Expr? "}"
jrobie: CompNamespaceConstructor ::= "namespace" (Prefix | ("{" PrefixExpr "}")) "{" URIExpr "}"
MikeK: validate{()} is currently a type error, we should change it to return ()
jrobie: CompTextConstructor ::= "text" "{" Expr "}"
jrobie: CompCommentConstructor ::= "comment" "{" Expr "}"
jrobie: CompPIConstructor ::= "processing-instruction" (NCName | ("{" Expr "}")) "{" Expr? "}"
jrobie: element {first] {}
jrobie: attribute {first} { }
DECISION: WG has agreed to refactor the grammar using the EnclosedExpr in the node constructors, but in the case of the element constructor we shall not use it in the first argument because it cannot be an empty sequence. Consider the expressions Try, Catch, Validate, ExtensionExpr, Ordered and Unordered, CompDocConstructor, CompAttrConstructor, CompTextConstructor, CompCommentConstructor CompPIConstructor and Namespace
New ACTION A-621-03: Michael Dyck to update the grammar for empty expressions in braces. ETA: 2015-11-02 (Morning)
New ACTION A-621-04: Jonathan to update the words in in Xquery for empty expressions in braces ETA: 2015-11-03
>
>
>
> 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
None
>
>
>
> Q5. Adjourn
>
>
>
Received on Thursday, 29 October 2015 01:42:26 UTC