[Monetdb-developers] Q: pathfinder - cdata
sjoerd at acm.org
Thu Jul 12 22:22:35 CEST 2007
On 07/12/2007 08:46 PM, Arjen P. de Vries wrote:
> I have two followup questions then:
> <a><![CDATA[<sjoerd at acm.org>]]></a>
> not leave the CDATA intact and not replace the < to < ?
> Disclaimer: I am not very sure what should be correct.
> This is phrased to permit an implementor to provide an option that
> attempts to preserve
> CDATA sections present in the source document.
CDATA is CDATA, no matter the representation. In both cases the content
of the <a> element is CDATA, it's just encoded differently. I doubt
that there is a way for MonetDB/XQuery to find out which encoding was used.
> xquery><![CDATA[<sjoerd at acm.org>]]></a>
> more>MAPI = monetdb at localhost:50000
> QUERY = <![CDATA[<sjoerd at acm.org>]]></a>
> ERROR = !parse error: syntax error, unexpected <![CDATA[ on line 1,
> column 9 (next token is `<![CDATA[')
> !parse error: XQuery parsing failed
> also have been allowed - a bit weird if it is allowed inside another element?
I don't know enough about XQuery, but my guess is: no.
When you look at the XQuery grammar
(http://www.w3.org/TR/xquery/#nt-bnf) you'll see that (after the
optional prologue stuff) the query consists of a list of comma-separated
ExprSingles, and that an ExprSingle is one of FLWORExpr, QuantifiedExpr,
TypeswitchExpr, IfExpr, OrExpr. The only one (in a quick scan) that
doesn't have to start with a keyword is OrExpr in the guise of a
PathExpr. And the only CDataSection (<![CDATA[...]]>) is inside a
> On 12/07/07, Sjoerd Mullender <sjoerd at acm.org> wrote:
>> Arjen P. de Vries wrote:
>>> <a />
>>> is accepted as a query,
>>> is not.
>>> !parse error: syntax error, unexpected <![CDATA[ on line 1, column 9
>>> (next token is `<![CDATA[')
>>> !parse error: XQuery parsing failed
>>> Is that the expected behaviour?
>>> Context: I try to output email addresses as "test <test at my.org>" and failing
>> This works:
>> xquery><a><![CDATA[<sjoerd at acm.org>]]></a>
>> <a><sjoerd at acm.org></a>
>> Sjoerd Mullender
More information about the developers-list