W3C home > Mailing lists > Public > public-xsl-query@w3.org > May 2016

Re: ACTION A-642-04

From: Josh Spiegel <josh.spiegel@oracle.com>
Date: Wed, 4 May 2016 20:39:03 -0700 (PDT)
Message-ID: <7B3665D9-77B7-40E2-80D8-059EA84105D5@oracle.com>
To: Michael Kay <mike@saxonica.com>
Cc: Public Joint XSLT XQuery XPath <public-xsl-query@w3.org>
I’m not sure why there would be such a restriction.  However, I don’t mind tweaking the assertions.  Is XQuery allowed in <assert>?

Thanks,
Josh

> On May 4, 2016, at 4:38 PM, Michael Kay <mike@saxonica.com> wrote:
> 
> Oh dear.
> 
> -s:prod-MapConstructor -t:MapConstructor-034
> net.sf.saxon.s9api.SaxonApiException: Unexpected token "<" at start of expression
> 	at net.sf.saxon.s9api.XPathCompiler.internalCompile(XPathCompiler.java:509)
> 
> Seems you've broken an unwritten rule that the expression in assert-deep-eq can be parsed as an XPath expression ...
> 
> Michael Kay
> Saxonica
> 
> 
>> On 4 May 2016, at 20:59, Josh Spiegel <josh.spiegel@oracle.com <mailto:josh.spiegel@oracle.com>> wrote:
>> 
>>> ACTION A-642-04 Josh to create test cases for NCName:* change to 1b in
>>> https://lists.w3.org/Archives/Public/public-xsl-query/2016Mar/0035.html <https://lists.w3.org/Archives/Public/public-xsl-query/2016Mar/0035.html>
>> I have added new test cases to prod/MapConstructor.xml.  Good luck!
>> 
>> Josh
> 


Received on Thursday, 5 May 2016 03:41:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:43:16 UTC