- From: Erik Bruchez <ebruchez@orbeon.com>
- Date: Fri, 23 Jun 2006 10:14:27 +0100
- To: 'www-forms' <www-forms@w3.org>
Great! And thanks :-) -Erik David Landwehr wrote: > > Ok good point, I will change it to @select. I will update the extension > on sunday. > > I had the similar problem with the sorting extension and ended with > using select instead of ref. > > Best regards, > David > > On Jun 22, 2006, at 2:43 PM, Erik Bruchez wrote: > >> >> All (but especially David), >> >> Based on practical experience I am at this point 100% convinced that >> support for variables in XForms views (not so much in models) is >> necessary (hopefully for XForms 1.2 or 2.0), so it's great to see that >> other people have recognized this need and are experimenting with it. >> >> The only thing that bugs me with eXForms's variable proposal [1] is >> that it uses a @value attribute, and not a @select attribute. >> >> I understand that @value is already used on xforms:output, but it is >> confusing, knowing XSLT, not to have @select instead of @value. >> >> In addition to the confusion due to the difference with XSLT, I think >> that using @value is not correct because the variable can hold >> anything that can be returned by an XPath expression, in particular a >> node-set, and the term "value" is usually understood to mean "a string >> value". See for example xsl:value-of vs. xsl:copy-of for another >> example of this. >> >> So I strongly suggest the use of @select instead of @value there. >> >> -Erik >> >> [1] http://exforms.org/variable.html >> >> --Orbeon - XForms Everywhere: >> http://www.orbeon.com/blog/ >> > > -- Orbeon - XForms Everywhere: http://www.orbeon.com/blog/
Received on Friday, 23 June 2006 09:14:36 UTC