W3C home > Mailing lists > Public > www-forms@w3.org > July 2006

Re: Wildcard in the <value> element

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Thu, 27 Jul 2006 16:35:35 +0200
To: "Alessandro Triglia" <sandro@mclink.it>, "[Public XForms]" <www-forms@w3.org>
Message-ID: <op.tdcqtlqrsmjzpq@acer3010.lan>

On Fri, 21 Jul 2006 19:36:36 +0200, Alessandro Triglia <sandro@mclink.it>  

> I am looking at the XForms schema at  
> http://www.w3.org/MarkUp/Forms/2002/XForms-Schema.xsd.   It is unclear  
> to me why the <value> element supports mixed content (as opposed to  
> simple content).
> The <value> element can only occur within an <item> or an <itemset>.  No?
>> From the paragraphs beginning with "Data Binding Restrictions: any  
>> simpleContent" (in Select and Select1), I infer that, when a <value>  
>> occurs within an <item>, it must be a simple type.  Am I wrong?
> As for <itemset>, it is unclear to me how <value> can be used within an  
> <itemset>, given that a <value> would provide a single value and not a  
> nodeset.   The specification of the <itemset> element describes the use  
> of the <copy> element but not the use of the <value> element.
> So my question is, in what cases (if any) would a <value> element  
> contain a child element?

Hello Allessandro,

I have to admit that I had to rack my brains to find an answer too. It was  
obvious once pointed out: creating a constructed value using <output>.

		<value>there were <output ref="n"/> <output ref="colour"/>  

Received on Thursday, 27 July 2006 14:36:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:18 UTC