Re: [Xsltforms-support] XSLTForms enhancements?

[<bc...@sh...>]

Hello everyone

I've been reading these enhancement suggestions (and others) and I realise
that the XForms specification allows for extensions and leaves things open
for implementation choices in some areas.

My concern -- and I am saying the following (and perhaps with no great
qualification to do so) without insinuation that XSLTForms is going this
way -- is to ask that careful consideration be paid to sticking to XForms
published standards/specification and to watch carefully that the
implementation in XSLTForms does not grow into some application full of
non-standard and/or deviated approaches to meet a perceived shortcoming.

What are your views ?

Regards
Habs

On 10 April 2016 at 20:45, Alain Couthures <ala...@ag...>
wrote:

> Hi Mats,
>
> - Allowing XSLTForms to be run as Chrome Apps, with file save/open
> functionality etc.
>
> Could you please write some documentation about how you succeeded? It
> might be added in XSLTForms Wikibook, for example.
>
> - Embedding SaxonCE library so that transform() function can run XSLT2
> transforms
>
> Have you modified the transform() function so that it is looking at the
> version of the stylesheet? Could this better be considered as a global
> option to be added in config files?
>
> - Adding @async attribute to xf:setvalue/xf:insert elements for
> non-blocking evaluation of long running XPath expressions in Web Workers
>
> Web Workers are not available in old browsers but all recent ones do now!
> I did not try to use them yet (priorities...) and I still wonder how they
> can access the XML DOM in the main page: is it a problem??
>
> - Adding validate-with-xml-schema() function, using xmllint library
>
> Is it that Chrome Apps allow you to link C libraries?
>
> - Adding validate-with-schematron() function, using SaxonCE. Useful for
> doing more advanced form validations using SVRL.
>
> Is it an XPath function? When are you calling it? Before submission?
> XForms is based on validation at node level whenever a value has been
> modified: do you think that it is also compatible with SVRL?
>
> - Adding parse-xml() function, believe replacing need for xf:setnode
>
> xf:setvalue is there to set a value not to import nodes... That's why I
> added xf:setnode with the serialized XML string as parameter. In what
> context do you use parse-xml()? Which document/instance owns the resulting
> nodes?
>
>
> Would be glad to contribute these as well as some other extensions and
> performance optimizations.
>
> Will be glad to look at them in details!! Is it your intent to publish
> source files independently or to fork the repository?
>
> Thanks!
>
> Alain
>
>
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications
> Manager
> Applications Manager provides deep performance insights into multiple
> tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
> gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>