Subject: Re: [xsl] Definite list of XSLT 2.0 processors? From: Vyacheslav Sedov <vyacheslav.sedov@xxxxxxxxx> Date: Mon, 18 Jan 2010 17:19:32 +0300 |
for XRX i use eXist-db and it work great with Saxon (both java-based) - see http://atomic.exist-db.org/HowTo/XSLT2/XSLT2 2010/1/18 Justin Johansson <procode@xxxxxxxxxxx>: > Hi Vyacheslav, > > I think you accidentally replied on someone else's micro-thread and not mine > which was: > >>>> Vyacheslav Sedov wrote: >>>> LAMP should go away and leave place to XRX > >>> An unexpected but nevertheless an interesting answer. >>> FWIW, From the first sentence of the Wikipedia writeup on XRX: >>> "In software development XRX is a web application architecture based on >>> XForms, REST and XQuery." >>> Not a mention of XSLT there so to challenge your response ... >>> Would it be reasonable to rephrase my question as: >>> "Given the neglect (i.e. XSLT 2 for XRX), does the XRX community really >>> want one?" >>> (Notwithstanding, and with no disrespect to, Saxon of course). >>> Regards Justin Johansson > >> XSLT not present as single entity in LAMP too ;) > > Accepted. B You have good counter-point that XSLT is not part of the either > acronyms XRX or LAMP. > > Still the overall context of this thread was about XSLT 2 processors for > different platforms > and Michael Kay mentioned LAMP as an platform lacking the same for whatever > (mostly commercial) reasons. > > So even if things were as you would like them to be, namely LAMP go away and > XRX take its place, > question still remains as to where to source your XSLT 2 processor from for > your XRX environment. > > Regards > > Justin Johansson > > > > > Vyacheslav Sedov wrote: >> >> XSLT not present as single entity in LAMP too ;) XSLT is best tool to >> convert XML data that you got from any database as XML and turn it >> into XHTML, ODF, OOXML or any other XML (in most cases), so it just >> similar case when you "call XSLT" from PHP, Perl and so on but best >> "host language" for XSLT is XQuery >> >> for example >> >> let $param := (), >> B B $validation2schm := transform:transform(v:all-rules($department, >> $period), doc("/db/service/form/validation2schematron.xsl"), $param), >> B B $schm2xsl := transform:transform($validation2schm, >> doc("/db/service/schematron/iso_svrl_for_xslt2.xsl"), $param), >> B B $report := transform:transform($table, $schm2xsl, $param),... >> >> just 3 lines of code for 3 xsl transformations ;) >> >> 2010/1/18 Abel Braaksma <abel.online@xxxxxxxxx>: >> >>> >>> Hi Christoph, >>> >>> didn't see your message earlier, sorry for a late reply. Have you anyhow >>> published the (disappointing) results of your efforts? What processors, >>> other than Saxon, have you managed to get running on Linux? >>> >>> Also, to follow-up on my own statements about .NET, Microsoft and XSLT >>> 2.0, >>> I just came across a more recent (2009-11-18) unofficial reply from the >>> Microsoft XML team which is backing up my believe that Microsoft has >>> dropped >>> plans for implementing XSLT 2.0. >>> >>> http://stackoverflow.com/questions/1525299/xpath-and-xslt-2-0-for-net >>> >>> [Begin_Quote] >>> While XML continues to be a key part of our platform going forward, we >>> have >>> decided not to pursue an XSLT 2.0 implementation at this time. If there >>> is a >>> specific XSLT task youbre trying to accomplish and are having difficulty >>> with XSLT 1.0, please let us know and webll do our best to help. >>> [End_Quote] >>> >>> Regards, >>> Abel Braaksma >>> >>> Christoph LANGE wrote: >>> >>>> >>>> Dear all, >>>> >>>> [Michael, sorry that you got the mail several times, I had some trouble >>>> posting to the list] >>>> >>>> B recently I made a very subjective review of all XSLT 2.0 processors >>>> that >>>> I >>>> could get to run on Linux. B The objective was running my XMLbRDF >>>> extraction >>>> library Krextor (http://kwarc.info/krextor/), which makes heavy use of >>>> XSLT >>>> 2.0 features; one might even call it a "stress test". B I also tried >>>> running a >>>> set of much simpler XSLTs called JOMDoc (http://jomdoc.omdoc.org), which >>>> convert OMDoc, a complex DocBook-like markup language for math, to >>>> XHTML. >>>> >>>> The evaluation was biased because before I had only tested the >>>> implementation >>>> with Saxon. B In possible cases where Saxon does not conform to the spec, >>>> my >>>> implementation might be "wrong", but works with Saxon. B And, of course, >>>> the >>>> "evaluation" is quite incomplete, as I got disappointed quickly. >>>> >>>> Quoting from an older mail to my co-developers:
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Definite list of XSLT 2.0, Justin Johansson | Thread | [xsl] xsl-list question: import pre, Lynn Murdock |
Re: [xsl] Definite list of XSLT 2.0, Vyacheslav Sedov | Date | Re: [xsl] Definite list of XSLT 2.0, Justin Johansson |
Month |