sure but it also makes sense to say child::sub
I don't think most doc-heads would accept as valid the idea that a
mixed content element (especially if the element has the mixed content
in it) is of type string.
Cheers,
Bryan Rasmussen
On Tue, Mar 4, 2008 at 5:54 PM, Michael Kay <mike@xxxxxxxxxxxx> wrote:
> > >
> > > <person><first>Michael</first><last>Kay</last></person>
> >
> >
>
> > Out of interest, what is the reasoning behind allowing a
> > mixed content element's typed-value to be its string value,
> > but making it an error for element-only content?
> >
>
> data-heads vs doc-heads.
>
> The data people felt that saying person='Kay' should be caught as a type
> error.
>
> But with mixed content, for example
>
> <title>Water, or H<sub>2</sub>O</title>
>
> it clearly makes sense to say contains(title, 'Water')
>
>
> Michael Kay
> http://www.saxonica.com/
|