Saxon » SaxonC

Looking back at the discussions on the mailing list there were a few options on the table. See summary of them below:

1. XSLT2Processor. The point was raised that this would not make sense since Saxon supports XSLT 3.0. Maybe we could also have XSLT3Processor.

2. SAXONProcessor. This might be a safe option to avoid name clashes, but not keen on having Saxon within the name explicitly.

3. Use the namespace feature in PHP.

For option 3. see details for Jirka Kosek:

Also note that PHP since 5.3 support namespaces (aka Java packages). So

you can still use XsltProcessor classname without any collisions if you

put it inside Saxon namespaces. New instance is then created by syntax like:

$xsltProc = new Saxon\XsltProcessor(...);

This naming pattern is not common yet for extensions as namespaces are

quite recent PHP feature.

I am probably in favour of option 3.