Hi, I have actually been running all the asserts (<=3.0) as XPath 2 expressions Just fails now, because someone added a has-children assert Best, Benito On 05/05/2016 05:39 AM, Josh Spiegel wrote: > 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 >> <mailto: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 >>> >>> I have added new test cases to prod/MapConstructor.xml. Good luck! >>> >>> Josh >> >
Received on Thursday, 5 May 2016 09:27:51 UTC