• From: Olivier Rossel <olivier.rossel@g...>
• To: COUTHURES Alain <alain.couthures@a...>
• Date: Wed, 8 Dec 2010 18:31:55 +0100

XSLTForms is REALLY cool !!!!
And it shows immediate benefit for web developpers:
a clean semantics hidding the JS mess.


Question:
how would you handle the case where the data XML is available in a
separate document
(or at a REST URL, for example)? Do you have another webpage that
shows that usecase, on your website?

Another question:
if the data XML can be in a separate document, can this document be
another XSLTForms?
== does the web browser handle recursive XSLTForms?

Thanks for your answers.
(and a BIIIG thumb up for your work!)


On Wed, Dec 8, 2010 at 4:58 PM, COUTHURES Alain
<alain.couthures@a...> wrote:
> XSLTForms already has an XPath transform function. I used it to dynamically
> generate SVG graphs at client-side:
> http://www.agencexml.com/svgopen/graphs.xml
>
> -Alain
>
> Le 08/12/2010 12:42, Philip Fennell a écrit :
>
> Micheal wrote:
>
>
>
>> The main drawback seems to be that it's hard to parameterize it, that is,
>
>> to make anything dependent on data content or user input.
>
>
>
> I’d say you’d want to consider what is being planned for the xf:transform
> action in XForms. Currently, XForms has all the pieces necessary to do this
> bar the invoking of the transform, but that is already available as an
> extension in some implementations. With XForms it doesn’t all come out of a
> single element, you need to define an instance for the data and some events
> that trigger actions and something with which to bind the result to the
> view. But then that’s probably why it is difficult to parameterize all in
> one element.
>
>
>
> Regards
>
>
>
> Philip Fennell
> Consultant
> MarkLogic Corporation
>
>
>
>
>
>
>
> From: Michael Kay [mailto:mike@s...]
> Sent: 05 December, 2010 11:45 PM
> To: xml-dev@l...
> Subject: Re:  Where is XML going
>
>
>
>
>
> Personally, I'd like to see an inline <transform> tag in HTML5:
>
>
>
> <transform
>
>     stylesheet="xs:anyURI"
>
>     data="xs:anyURI"
>
>     type="mime-type"
>
>     refresh="timeInterval"
>
>     asynch="xs:boolean"
>
>     media="xs:NMTokens"
>
>     id="xs:ID">
>
>       Default Internal Content
>
> </transform>
>
>
>
> This would be a display tag that would load the data either from a server or
> from a block of XML in the client, then would apply they associated
> stylesheet to that data in order to provide output that would replace the
> current child content.
>
> I've been thinking about doing something like this as an alternative to
> having to invoke a transformation using Javascript. The main drawback seems
> to be that it's hard to parameterize it, that is, to make anything dependent
> on data content or user input.
>
> Michael Kay
> Saxonica
>