• From: COUTHURES Alain <alain.couthures@a...>
• To: Amelia A Lewis <amyzing@t...>
• Date: Tue, 14 Dec 2010 09:38:04 +0100

Le 13/12/2010 17:35, Amelia A Lewis a écrit :
>
> Processing instruction not allowed (meaning no presentation in the
> browser via XSLT, either, but that's another issue).  Can't use a PI to
> indicate that this is uXML.
>
XSLT in the browser is not just for presentation. I'm the project leader 
of XSLTForms which converts XForms pages into vanilla HTML+Javascript 
with XSLT 1.0 at browser-side. Every browser, except Konqueror, supports 
XSLT 1.0 applied with a processing instruction and it's a very powerful 
approach (people sometimes complain about the fact that a generated 
processing instruction in the resulting XML is never applied again...). 
Comparing to a full Javascript architecture, performances are much 
better and there are not limitations about elements locations, for 
example. It also good for servers for not having to apply the 
stylesheets themselves.

Another notation for XSLT transformation should be defined if a more 
general processing instructions mechanism would be not allowed anymore...

Regards,

Alain Couthures

• Follow-Ups:
  • Re: MicroXML / XSLT at browser-side
    • From: Olivier Rossel <olivier.rossel@g...>

• References:
  • MicroXML
    • From: James Clark <jjc@j...>
  • Re: MicroXML
    • From: Amelia A Lewis <amyzing@t...>