On Tue, Dec 14, 2010 at 9:38 AM, COUTHURES Alain
<alain.couthures@a...> wrote:
> 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...

+1
Hiding insane Javascript tricks behind a clean XML vocabulary and a simple PI
is a BRILLIANT idea.
In my opinion, you should write a position paper to detail it.
So developpers can benefit from your experience and spend as few time
as possible resolving problems you have already solved.

This is really what web developpers want: clean libraries to manage their HTML.
And JS dispatched via XSLT is the perfect team.

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php