- From: Erik Bruchez <ebruchez@orbeon.com>
- Date: Wed, 16 Aug 2006 11:34:15 -0700
- To: www-forms@w3.org
Klotz, Leigh wrote: > Two issues come to mind: > 1. Currently @selected it's defined as an xsd:boolean (an enumeration of the strings "true", "false", "1", and "0". > Unfortunately, "true" isn't an XPath expression that evaluates to "true"; that would have to be "true()", so there's not the smooth upgrade path that it seems like there might be. One possible direction, syntactically, would be to use a nested element, as we may do for xforms:submission in 1.1. E.g.: <xforms:case> <xforms:selected value="instance('my-instance')/my-value = 3"/> ... or something like this. Ideally I would prefer attribute value templates (post-1.1)but as you point out there is a discrepancy between 'true' and true(). -Erik -- Orbeon - XForms Everywhere: http://www.orbeon.com/blog/
Received on Wednesday, 16 August 2006 20:17:41 UTC