XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] RE: James Clark: XML versus the Web

Alain Couthure's XSLTForms actually makes use of the re-entrant capabilities of XSLT on the browser, and I've written a number of apps that use the native XSLT capability within a browser to handle very complex re-entrant applications, as have many other people. XSLT2 support in the browser would significantly enhance this capability - the biggest holdups in seeing more use there is the fact that Mozilla's XSLT engine sucks.

Kurt Cagle
XML Architect
Lockheed / US National Archives ERA Project



On Wed, Dec 15, 2010 at 8:20 PM, James Clark <jjc@jclark.com> wrote:
On Thu, Dec 16, 2010 at 8:05 AM, Henri Sivonen <hsivonen@iki.fi> wrote:
 XSLT hasn't been designed for maintaining a continuous and incrementally updating relationship between the input and output trees.

Not true (at least for XSLT 1; can't speak for XSLT 2).  This is exactly what you need for an XSLT-driven XML editor, which was certainly one of the things XSLT was designed to enable.  It is the reason why certain useful features were left out of XSLT (result tree fragments as node-sets).  There have been implementations of this.

James





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS