XSLT 2 Processors

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • bllfrnch@gmail.com
    #1

    XSLT 2 Processors

    Hi all,

    We use XSLT extensively here at work and made the jump to XSLT 2 back
    in January. Doing so increased productivity by leaps and bounds. Before
    we made the switch, we were often doing "transformation s" with Perl
    because of XPath 1's lack of support for regular expressions. Now, it's
    all built in, and we haven't looked back.

    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?

    Thanks in advance for any information. I can't find anything!

    Best regards,

    --Bill

    Tags: None
    • Joe Kesselman
      #2
      Re: XSLT 2 Processors

      bllfrnch@gmail. com wrote:
      >Why have these other
      projects been so slow to adopt the XPath 2/XSLT 2 specification?
      Lack of demand (XSLT 1.0 really does cover most needs, especially with
      EXSLT to support it), combined with lack of resources (I used to be
      deeply involved in the Xalan effort, but have been unable to donate much
      time to it for the past year or two).

      But I agree that I would Really Like to have seen more 2.0 support by now.

      --
      () ASCII Ribbon Campaign | Joe Kesselman
      /\ Stamp out HTML e-mail! | System architexture and kinetic poetry

        Comment

        • Martin Honnen
          #3
          Re: XSLT 2 Processors



          bllfrnch@gmail. com 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.c om/blog/archives/000590.htmlthat 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.c om/group/microsoft.publi c.xsl/msg/70b7d60f96648b5 3>
          and tell them your needs.


          --

          Martin Honnen
          Attention Required! | Cloudflare
          http://JavaScript.FAQTs.com/

            Comment

            Previous template Next
            Working...