Subject:XPath 2.0 problem? Author:Paul Hermans Date:22 Aug 2005 10:40 AM
Dear,
Included you will find an XML file and two related xsd files (example files of a competitor) which I use for testing.
Running following XPath 2.0 query:
"//element(*,xs:positiveInteger)" does return 0 hits.
At 08.18 23/08/2005 -0400, stylus-studio-tech Listmanager wrote:
>Thanks for this clarification.
>
>I have some additional questions.
>
>Is this documented in the documentation or help somewhere?
No, it looks this limitation is not documented (yet)
>What's the rationale of this difference and are there plans to make
>the XPath evaluator schema-aware?
The issue is that the XPath evaluator available from the XML editor
works on a "live" DOM, that the user can change and query without
having to go through a parsing step. But schema informations cannot
be reliably attached to a live DOM, as moving/deleting/adding nodes
could make them invalid.
Making the evaluator schema aware would have two drawbacks: we would
need to always parse the source XML with schema validation enabled,
and we wouldn't be able to backmap from the query result window to
the XML editor. Would this still be useful to you?
Subject:Re: XPath 2.0 problem? Author:Paul Hermans Date:25 Aug 2005 07:39 AM
>Making the evaluator schema aware would have two drawbacks: we would
>need to always parse the source XML with schema validation enabled,
>and we wouldn't be able to backmap from the query result window to
>the XML editor. Would this still be useful to you?
Yes, since I rather would not like to switch to the XQuery environment for evaluating some very simple (although schema-sensitive) XPath expressions.
Subject:Re: XPath 2.0 problem? Author:Paul Hermans Date:25 Aug 2005 07:39 AM
>Making the evaluator schema aware would have two drawbacks: we would
>need to always parse the source XML with schema validation enabled,
>and we wouldn't be able to backmap from the query result window to
>the XML editor. Would this still be useful to you?
Yes, since I rather would not like to switch to the XQuery environment for evaluating some very simple (although schema-sensitive) XPath expressions.