Doing a search and replace in the xslt file as follows seems to work:
xs:token -> xs:string
xs:ID -> xs:string
xs:IDREF -> xs:string
xs
ositiveInteger -> xs:integer
xs:nonNegativeInteger -> xs:integer
Should that be safe, or am I creating problems for myself?
"Martin Honnen" <mahotrash@yahoo.de> wrote in message
news:u$JrdyIJJHA.3424@TK2MSFTNGP05.phx.gbl...
> Susan Harris wrote:
>> Are there any powerful native .NET royalty free solution for working with
>> XSLT 2.0? The Altova engine uses a COM object, which I prefer not to
>> deploy, and the basic Saxon parser can't handle xsl:sequence, etc. And it
>> doesn't look like you can distribute the commerical one freely.
>
> Saxon is not a parser, it is an XSLT 2.0 and XQuery 1.0 engine. Saxon uses
> the XML parser in the .NET framework or the Java runtime.
>
> And I am sure the basic Saxon version can handle the XSLT 2.0 instruction
> xsl:sequence, otherwise it would not comply with the XSLT 2.0
> specification. What the basic Saxon version does not support is schema
> aware XSLT 2.0 or XQuery 1.0. What exactly do you think the basic Saxon
> version does not support?
>
> Otherwise I am afraid there are no current options for XSLT 2.0 under
> .NET.
>
> --
>
> Martin Honnen --- MVP XML
> http://JavaScript.FAQTs.com/