Re: why split? [was RE: XSL intent survey]

["Oren Ben-Kiki" <oren@xxxxxxxxxxxxx>]

Guy_Murphy@xxxxxxxxxx wrote:

>I know that MS ASP Remote Scripting uses a Java proxy to buffer data
>between the client document and the server, so I suppose there's no reason
>why such a proxy shouldn't be an XSL parser recieving XML.


Seems a pretty natural way to work, actually. After all, in theory we'd like
browsers to be able to do this parsing internally - isn't this what "XSL
support in the browser" is all about?

>Do you know is anybody working on such an implimentation?


I am :-) We're sending XML to the browser, which uses an applet to convert
it to HTML+CSS+JavaScript+whatever and displays the results. In fact, I've
just spent four hours trying to convince my XSL processor to emit
human-readable output from my XML data. I ended up stripping all the white
space from the input document - it is now a single long line - and then
still had to write pretty strange XSL to ensure that the output looks
reasonable. In general you don't care how the generated output looks, but if
it is complex, as in my case, you do want to read and debug it. Of course,
I'm using a beta version of a freeware processor implementing a draft
standard, so I can't really complain. Still, it is a sample of how far XSL
needs to go as a transformation language.

Have fun,

    Oren.




 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list