RE: New XPath extension function called xslt()

Hi, all,

First of all, thank you for paying attention to this proposal and for sharing your opinions about it. All these opinions are very instructive and reveal different facets of the discussed topic both from conceptual point of view and from practical usage in real-world web applications.

I would like to share my comments, too.

So, I maintain my initial opinion about an xslt action for the following reasons: 

1. When using xslt as a function, the syntax is by far more simple. But, conceptually speaking, an XSL transformation has nothing to do with XPath functions. I consider that, within XForms  scope, it is an action, just like the other XForms actions (setvalue, insert, delete, etc.).

2. Considering xslt as an action, one can avoid all the "problems" caused by "dependencies" (as were mentioned above).

3. Such xslt action can be easily be used, wrapped in an action element, to process data when "xforms-submit" event is triggered, just like other actions we are doing right now before submissions in our webapps. It can also be used, wrapped in an action element, to process data when "xforms-value-changed" event is triggered, in order to update an UI subform. It can receive @if, @while. Or it can be wrapped by an action element acting as handler called by a listener, according to XML Events.


Claudius Teodorescu
http://kuberam.ro