[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

Re: [xsl] Saxon/C going forward


Subject: Re: [xsl] Saxon/C going forward
From: Jirka Kosek <jirka@xxxxxxxx>
Date: Sun, 05 Jan 2014 22:14:28 +0100

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 18.12.2013 18:11, O'Neil Delpratt wrote:
> In the development of the PHP extension we tried to follow the
> functions available in the PHP XSL extension (i.e. libxslt) where
> possible. Please see the API of the Saxon/C PHP extension:
> 
> To those who use XSL on PHP are you happy with the way it is done
> or would do it differently?

Ideally PHP API including method names should be as similar to
existing API as possible, see:

http://cz1.php.net/manual/en/class.xsltprocessor.php

> Bearing in mind that we may need to make changes to support the
> XPath 2.0 type system. Also is interop with the libxml parser
> important?

Many existing PHP applications run transformation against DOM
constructed in memory. So ideally transformation should be possible to
run over libxml2 DOM, or at least Saxon could on-the-fly create copy
of this DOM into TinyTree or what's used in Saxon/C.

				Jirka

- -- 
- ------------------------------------------------------------------
  Jirka Kosek      e-mail: jirka@xxxxxxxx      http://xmlguru.cz
- ------------------------------------------------------------------
       Professional XML consulting and training services
  DocBook customization, custom XSLT/XSL-FO document processing
- ------------------------------------------------------------------
 OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep.
- ------------------------------------------------------------------
    Bringing you XML Prague conference    http://xmlprague.cz
- ------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlLJyzQACgkQzwmSw7n0dR7oBACeKdANiiLM/NKiiBAbsmNam/rM
+L0An3gvZrfQlQopLw1yuRGXCDte4XjX
=Z3b9
-----END PGP SIGNATURE-----


Current Thread
Keywords