[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Re: [xsl] Replacing = with == and ===
Subject: Re: [xsl] Replacing = with == and === From: "L2L 2L emanuelallen@xxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Date: Sun, 3 Aug 2014 15:55:24 -0000 |
What's EXPath and the likes? E-S4L > On Aug 3, 2014, at 11:50 AM, "Dimitre Novatchev dnovatchev@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > On Sun, Aug 3, 2014 at 12:13 AM, BR Chrisman brchrisman@xxxxxxxxx > <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: >> But when it comes down to it, I'd also like an XPath-like-language >> that implicitly lets me parse/address XPath within XSLT attributes >> (like select=) in order to gain further insight into what a particular >> template/routine/etc is doing (and whether I need to modify it via my >> XSLT-transforming-XSLT program. > > > XQueryX is a *standard* W3C Recommendation: > > http://www.w3.org/TR/2014/REC-xqueryx-30-20140408/ > http://www.w3.org/TR/xqueryx/ > > And at least for the previous version I think there was a Java-based > parser for XQuery, that produced an XQueryX XML document from an > XQuery expression. > > Certainly XPath is a true subset of XQuery. This means that the parser > will successfully produce an XQueryX document for any input XPath > expression. > > So, one will simply use *XPath* to navigate an XPath expression that > is converted to XQueryX. > > I think it wouldn't be too much effort to refactor the XQueryX > grammar, so that a subset of it will be the grammar of what we could > call "XPathX". Maybe an idea for EXPath? > > > -- > Cheers, > Dimitre Novatchev
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Replacing = with == and =, Dimitre Novatchev dn | Thread | Re: [xsl] Replacing = with == and =, Dimitre Novatchev dn |
Re: [xsl] Replacing = with == and =, Dimitre Novatchev dn | Date | Re: [xsl] Replacing = with == and =, Dimitre Novatchev dn |
Month |