Re: XSLT 2 Processors





bllfrnch@xxxxxxxxx wrote:


However, I can't find any information about processors other than
Saxon. Does anyone know what the development roadmaps are for
Sablotron, Xalan, MSXML, and/or other processors? Why have these other
projects been so slow to adopt the XPath 2/XSLT 2 specification?

One reason certainly is that there are various specifications (e.g. XSLT 2.0, XPath 2.0) involved that are still a work in progress.
Microsoft for instance decided not to ship XSLT/XPath 2.0 or XQuery support in the .NET framework before those standards are a W3C recommendation.
Comments in blogs indicate <http://www.tkachenko.com/blog/archives/000590.html> that now work has started to implement XSLT 2.0 in the .NET framework.
If you want XSLT 2.0 support in MSXML then look at this post
<http://groups.google.com/group/microsoft.public.xsl/msg/70b7d60f96648b53>
and tell them your needs.


--

Martin Honnen
http://JavaScript.FAQTs.com/
.



Relevant Pages

  • Re: Access XML Imprt
    ... denn Du hast ja schon MSXML ... Das wesentliche ist aber die Kenntnis von XSLT. ... Prev by Date: ... Next by Date: ...
    (microsoft.public.de.access)
  • Re: What should I keep?
    ... .NET Framework 1.1 Hotfix ... I also have the following MSXML listed: ... MSXML 4.0 SP2 ... MSXML 4.0 SP2 Parser & SDK ...
    (microsoft.public.windowsxp.general)
  • Re: What should I keep?
    ... .NET Framework 1.1 Hotfix ... I also have the following MSXML listed: ... MSXML 4.0 SP2 ... MSXML 4.0 SP2 Parser & SDK ...
    (microsoft.public.windowsxp.general)
  • RE: XSLT transforms and complex parameter types
    ... I understand that XSLTransform works incorrectly when the ... this is a known issue in current .net framework. ... Since IE uses MSXML to process xml data, ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: What should I keep?
    ... .NET Framework 1.1 Hotfix ... I also have the following MSXML listed: ... MSXML 4.0 SP2 ... MSXML 4.0 SP2 Parser & SDK ...
    (microsoft.public.windowsxp.general)