Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] Use of data() function

From: "bryan rasmussen" <rasmussen.bryan@--------->
To:
Date: 3/4/2008 9:19:00 PM
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/


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent