DRAFT XML Query/XSL WG Joint Teleconference #617 Minutes 2015-09-22

DRAFT XML Query/XSL WG Joint Teleconference #617 Minutes 2015-09-22

Chair: Andy
Scribe: Norm

> 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.
>
> 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-617-01 Jonathan to bring discussion of bug 29119 to the mailing list.

ACTION A-617-02: ETA 2015-09-29 Michael Dyck to write a grammar for
string templates with names and delimiters he chooses.

ACTION A-617-03: ETA 2015-09-29 Jonathan to start an email discussion
about the selection of actual delimiters.

ACTION A-617-04: ETA 2015-09-29 Jonathan to write prose for the section
on string templates.

> ===================================================
> Joint XML Query Working Group and XSL Working Group
> ===================================================
>
> J1. Administrative Items
>
> J1.1 Selection of secretary(s)
>
> Adam has been asked to take the minutes. Norm has been asked to stand
> by.
>
> 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.
>
> Adam Retter - 2015-04-21, 2015-01-20, 2014-09-23
> Jonathan Robie - 2015-05-12, 2015-01-13, 2014-10-28
> Michael Sprbrg-McQn - 2015-06-09, 2015-03-03, 2014-11-25
> Liam Quin - 2015-06-16, 2015-03-10, 2014-10-27
> O'Neil Delpratt - 2015-06-23, 2015-03-17, 2014-12-02
> 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
>
> J1.2 Call the Roll -- NOT DONE DURING TELECONFERENCE

Present: Norman, Andy, John, Jonathan, Josh, O'Neil, Tim, Michael Dyck
Regrets: Michael Kay, Michael Sperberg-McQueen, Liam

> 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:
>
> J1.3 Approval of agenda

Approved.

> J1.3.1 Additions, deletions, or corrections?

Smart quotes even in the absence of some interested parties.

> J1.4 Review of recent minutes and administrative items
>
> J1.4.1 Minutes of meeting #615 (Tim)
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Sep/0061.html

Accepted.

> J1.5 Review of action items
>
> NOTE: Please be prepared to respond quickly on your action items!
>
> J1.5.1 Outstanding action items
>
> ACTION A-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

Continued. Revised ETA.

> 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
>
> Status: Pending; ETA 2015-11-24

Continued. Revised ETA.

> ACTION A-613-04 O'Neil to ensure that the use cases in the XQuery 3.1
> requirements and use cases document are added to the QT3 test suite.
>
> Status: Pending; ETA 2015-09-29

Continued. Revises ETA.

> ACTION A-613-23: Norm Walsh to implement the changes from comment 3
> and 4 of bug 28299 in XDM 3.1, including moving the definition of
> xs:numeric from F&O 3.1 to XDM 3.1. All other editors to refer to the
> definition of xs:numeric in XDM 3.1.
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=28299#c3
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=28299#c4
>
> Status: Pending; ETA not specified.

Completed.

> ACTION A-613-26: Norm Walsh to replace the text in XDM 3.1 section
> 17.1 by implementing the changes from comment 6 of bug 28795.
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=28795#c6
>
> Status: Pending; ETA not specified.

Not my bug?

Josh: Make reference to op:same-key, and take out the date-time stuff.

Revised ETA: 2015-09-29.

> 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
>
> Status: Pending; ETA 2015-09-29

Continued.

> ACTION A-614-01 on JRobie to work with Zed to build FT 3.1 docs before
> checking them in.
>
> Status: Pending; ETA 2015-09-29

Continued.

> ACTION A-614-11 on JRobie re Bug 28966: make the change described in
> the bug
> and mark the bug fixed.
>
> Status: Pending; ETA 2015-09-29

Continued.

> ACTION A-614-13 on JRobie to propose wording to resolve Bug 29027.
>
> Status: Pending; ETA 2015-09-29

Continued.

> ACTION A-616-01: Loren to explain the changes he made to the
> serialization schema in response to Josh's email.
>
> Status: Pending; ETA not specified.

Continued.

> ACTION A-616-02: Michael SpMQ to make changes to serialization
> specification detailed in
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=26862
>
> Status: Pending; ETA 2015-09-29

Continued.

> ACTION A-616-03: Andy to contact Christian to see if he would take
> ownership of the XQUTS.
>
> Status: Pending; ETA not specified.

Completed.

Andy spoke with Christian. He's willing to donate tests, but he
doesn't think it'll be avaialble until later this year. He said he'd
consider being the owner of the test suite, but isn't prepared to
commit just at the moment.

Some discussion with Jonathan about who's willing to take Update 3.1
forward. Christian and Jonathan are interested. Andy will contact
Adam to see if he's interested.

> ACTION A-616-04: JRobie to update smart quotes (AKA string templates)
> proposal with syntax discussed.
>
> Status: Pending; ETA not specified.

Completed. Finished last week and only on this agenda accidentally.

> ACTION A-616-05: MikeK to add note to F&O offering more explanation in
> light of decision on Bug 20602 - [QT3TS] fn-resolve-uri-32.
>
> Status: Pending; ETA not specified.

Continued.

> ACTION A-616-06: MikeK to update specification in light of adoption of
> proposal in Comment #2
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29009#c2
>
> Status: Pending; ETA not specified.

Continued.

> ACTION A-616-07: MikeK to update specification regarding J4.7.3 Bug
> 29024
> - fn:serialize needs clarification when method parameter set from a
> map
> and J4.7.4 Bug 29028 - fn:serialize should specify the required type
> for
> QNames-type with accepted proposal in
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29024#c3
>
> Status: Pending; ETA not specified.

Continued.

> J1.5.2 Completed action items
>
> ACTION A-614-10 on Andy to make the changes suggested by Josh in
> August msgs 14+15.
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Sep/0052.html
>
> ACTION A-614-14 on Josh to resolve Bug 29045 as he suggests.
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Sep/0015.html
>
> ACTION A-615-01 on Josh to email Loren with questions about A-613-37.
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Sep/0015.html
>
> ACTION A-615-02 on Mike Kay to resolve bug 29009 by removing the
> restriction on xml-to-json to untyped instances.
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Sep/0038.html
>
> ACTION A-615-03 on Mike Kay to propose a solution for bugs 29024 and
> 29028.
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Sep/0038.html
>
> ACTION A-615-04 on Mike Kay to check whether the proposed solution to
> bug 29044 is consistent with "order by” in the case of NaN and the
> empty sequence.
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Sep/0038.html
>
> ACTION A-615-05 on Michael Sprbrg-McQn to propose a solution for bug
> 26862 that validates parameter elements individually instead of
> validating the parameter document as a whole.
>
> Status: Closed; See
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=26862#c5
>
> ACTION A-615-06 on O’Neil to address bug 28997 by (1) changing the
> XQuery tests to have a schema import declaration and (2) defining a
> mechanism in the test suite to allow schemas to be imported in the
> static context automatically for XPath queries.
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Sep/0035.html
>
> ACTION A-615-07 on O’Neil to fix the result of try-012 (bug 29097).
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Sep/0036.html
>
> ACTION A-615-08 on Josh to fix bug 29099 as suggested in comment 0.
>
> Status: Closed; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Sep/0016.html
>
> J1.6 Update on related activities
>
> J1.6.1 Update on XSLT WG activities (Sharon, MikeK)

No update available.

> J1.6.2 Update on EXPath/EXQuery CG activities (Loren)

No update available.

> 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
>
> J1.7.2 Future F2F Meetings
>
> J1.7.2.1 Other future F2F meetings
>
> The XML Query WG decided NOT to meet in conjunction with the W3C Tech
> Plenary in October 2015 in Hokkaido, Japan.
>
> 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
>
> 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
>
> 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
>
> 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-diff.html
> 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
>
> (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-diff.html
> 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
>
> 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
>
> (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-diff.html
> 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-diff.html
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/src/changes.txt
>
> J4.7.1 Bug 28845 - fn:format-number, formatting rules for exponential
> notation
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=28845
>
> Status: Ready to discuss; See
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Sep/0008.html
>
> J4.7.2 Bug 29044 - array:sort does not define a total order when keys
> contain NaN
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29044
>
> Status: Ready to discuss
>
> 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-diff.html
> http://www.w3.org/XML/Group/qtspecs/specifications/xslt-xquery-serialization-31/src/changes.txt
>
> (none)
>
> 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-diff.html
> http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/src/changes.txt
>
> J4.9.1 Bug 29096 - [XP31] URIQualifiedName syntax: Q{}local and Q{}*
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29096
>
> Status: Ready to discuss

Josh asserts this is resolved. Josh to close.

> J4.9.2 Bug 29119 - [XP31] xs:error always raises a type error
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29119
>
> Status: Ready to discuss

Some discussion about whether or not the example is exactly right. The
type declaration is missing.

Jonathan asks, what do we think this does?

 let $e as xs:error := xs:error()
 return 12

We could say that this is always an error because you cannot assign any
value to a variable of that type.

Jonathan: if you have a variable binding with a type of xs:error,
that's an error.

MDyck: But that's only in XQuery, it could still happen in XPath.

Jonathan: But you can declare it as a sequence type in inline functions,
even in XPath, so where is that allowed in XPath.

Some discussion about what situations can arise and the extent to
which they are valid.

ACTION A-617-01 Jonathan to bring discussion of bug 29119 to the mailing list.

> 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
>
> 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.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-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 String Templates (smart quotes)
> See
> https://lists.w3.org/Archives/Public/public-xsl-query/2015Sep/0072.html
>
> Status: Ready to discuss

Andy expresses reservations about discussing this issue without Liam.

Jonathan: If we could agree everything about which concrete delimiters
to use, I would feel that that was progress.

Jonathan: There are two basic questions: organization and naming of
productions. I propose we take his proposed names. And I think we
should put something in the grammar, with any delimiters, and we vote
on the actual delimiters next week.

From IRC:

<jrobie> [104]     TypedFunctionTest     ::=     "function" "(" (SequenceType ("," SequenceType)*)? ")" "as" SequenceType
<jrobie> InlineFunctionExpr     ::=     "function" "(" ParamList? ")" ("as" SequenceType)? FunctionBody
<jrobie> [28]     CastExpr     ::=     ArrowExpr ( "cast" "as" SingleType )?
<jrobie> [27]     CastableExpr     ::=     CastExpr ( "castable" "as" SingleType )?
<jrobie> [26]     TreatExpr     ::=     CastableExpr ( "treat" "as" SequenceType )?
<jrobie> https://lists.w3.org/Archives/Public/public-xsl-query/2015Sep/0074.html
<jrobie> mdyck, if we ask you to put the productions for smart quotes
in the grammar, using the production names you proposed, could you do
that?
<jrobie> mdyck, the exact delimiters may change next week
<jrobie> <{  }>
<jrobie> <[ ]>
<jrobie> ~~<   >~~
<jrobie> ~~[ ]~~
<Andy> @@{ ... }@@
<jrobie> @@[ ]@@
<mdyck> yeah, i should be able to do that
<josh> I would like to add <[" and "]> instead of <[ ]> because "]>"
seems to occur frequently in XML and HTML

Andy: We need to decide to have something that really sticks out or
something that looks reasonably unobtrusive.

Some discussion of the quote marks in Josh's proposal.

Jonathan: I think people not on the call should have a chance to reply.

Josh: Several languages use """ and "here" documents often use <<<.

Jonathan: Let's try to limit the poll, even if that doesn't work.

Suggestions from IRC:

  <<[ ... ]>>  and <<{ ... }>>
   <[ ... ]>   and  <{ ... }>
  @@[ ... ]@@  and @@{ ... }@@
   <{ ... }>   and  <[" ... "]>


Jonathan: I don't think the occurrence of the string in languages is
all that important. You can stick them in variables if you like:

  let $s := "<{"
  let $e := "}>"
  return
     <{ $s, foo, $e, }>

or:

  <{ "<{", foo, "}>", }>

Josh: I agree with everything you said, except for ]> which occurs
quite frequently.

Jonathan: I think that's a really good argument. Does >> work?

Josh: Yeah, I think that resolves the issue. But I think the " is
easier. But it's getting more bike-shed between those two.

Jonathan: So <<" ... ">> vs <<{ ... }>>

Josh: Why do you want two for the expression ones?

Jonathan/Norm: Becaues it would be confusing.

Andy: The double brackets will probably appeal to Liam more.

Josh: The only problem I see is that people might confuse it with
Jhere-doc.

Jonathan: How about <" ... "> and <{ ... }>

Josh: That's very common.

Andy: I think the double angle brackets with the quotes stand out more
to the human reader.

MDyck: <<" would change the validity/semantics of existing XQueries.

Jonathan: Because << and >> are for before and after.

Some concern about changes to query parsing "<<". 

Jonathan proposes an action to MDyck to put something in the grammar
and Jonathan to start an email discussion and write text.

ACTION A-617-02: ETA 2015-09-29 Michael Dyck to write a grammar for
string templates with names and delimiters he chooses.

ACTION A-617-03: ETA 2015-09-29 Jonathan to start an email discussion
about the selection of actual delimiters.

ACTION A-617-04: ETA 2015-09-29 Jonathan to write prose for the section
on string templates.

> Q2.3.2 Bug 29027 - [qt3] contextDecl-022
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29027
>
> Status: Pending completion of A-614-13
>
> Q2.3.3 Bug 29131 - Function ext:sc missing definition in example. See
> section 3.7
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29131
>
> Status: Ready to discuss

Jonathan observes that the missing function would be very difficult to
write, which is why it's external.

Andy: We shouldn't try to put this one in the test suite.

O'Neil: Ok, I'll remove that one and close the bug.

> 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
>
> (none)
>
> Q3. Test Suite Development
>
> Q3.1 Update Facility 3.0 Test Suite (????)
>
> * Need test suite developer/manager
>
> * Need tests
>
> Q4. Any other business

Josh: When are we going to get to REC?

Andy: We need two implementations. How are we doing?

O'Neil: We only have one. And there hasn't been any real progress on
other implementations since June.

Jonathan: We've been running the test suite, but we probably aren't
going to like the results well enough to publish them before early
next year.

Josh: I'm in the same boat with the additional complexity that I'm not
going to implement higher ordeer functions.

John: We're not likely to have results to submit.

Tim: We're not going to have anything to submit this year.

Andy: We ask Christian, but that's where we are. We can't get out of
CR until we have at least another implementation reporting results.

Josh: That's the bottleneck?

Andy: That's entirely the bottleneck.

Josh: Do we need two implementations of optional features, or just one?

Andy: We need two implementations of each optional feature, but they
don't have to be the same implementations.

Some discussion of what the implementation reports must contain.

> Q5. Adjourn

Adjourned.

                                        Be seeing you,
                                          norm

--
Norman Walsh
Lead Engineer
MarkLogic Corporation
Phone: +1 512 761 6676
www.marklogic.com