|
[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: 'nother xslt2 engine
It appears I should have read the docs a little deeper as it definitely
says in terms that are easy to understand and in complete clarity that
this processor is not SchemaAware. In reading through the element
support (or lack there of) I do question whey the following functions
and elements, deemed as XSLT 2.0 functions and elements, are listed as
not supported...
functions: element-available Not supported. format-date Not supported. format-dateTime Not supported. format-time Not supported. generate-id Not supported. key Not supported. system-property Not supported. unparsed-entity-public-id Not supported. unparsed-entity-uri Not supported. unparsed-text Not supported.
While some of these are additions on the 2.0 spec obviously there are some that were also a part of the 1.0 spec. Is this engine a completey new, from the ground up architecture and code-base. Also, this statement comes straight from the site: "The Altova XSLT 1.0 Engine is an XSLT processor that is fully compatible with the W3C XSLT 1.0 </specs_xslt.html> specification, and the Altova XSLT 2.0 Engine is completely conformant with the XSLT 2.0 <http://www.w3.org/TR/xslt20/> specification. Both engines are packaged as Windows executables with command-line control and are suitable for use in both client- and server-side application development. Now you can use the exact same XSLT processor that is available in our award-winning XMLSpy development environment in your solutions! This is the same engine that is used in the XSLT Debugger inside XMLSpy, so once you have debugged your XSLT 1.0 or 2.0 stylesheets, you can be sure that they execute in exactly the same way when you use the respective Altova XSLT Engine." If I read this without having read the additional specs I would have assumed that both processors had full compliance which, according to the above, they do not... This is obviously not the place to be asking Altova about there product but it does bring up some points that I think a lot of people on this list have an interest in so I think its worth, at very least, getting these discrepancies in documentation cleared up and publicized to those most likely to use the XSLT processor... the people on this list :) Comments? <M:D/> David Carlisle wrote: not tried it yet but...
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|

Cart








