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

RE: Wildcard in the <value> element

From: Alessandro Triglia <sandro@mclink.it>
Date: Fri, 21 Jul 2006 23:04:17 +0200
To: www-forms@w3.org, aaronr@us.ibm.com
Message-Id: <1.3.200607212304.17633@mclink.it>


Hi Aaron,

> -----Original Message-----
> From: www-forms-request@w3.org 
> [mailto:www-forms-request@w3.org] On Behalf Of Aaron Reed
> Sent: Friday, July 21, 2006 15:46
> To: www-forms@w3.org
> Subject: Re: Wildcard in the <value> element
> 
> So this would effectively create two items:
> <xf:item>
>    <xf:label>Bob Smith</xf:label>
>    <xf:value>123-45-6789</xf:value>
> </xf:item>
> <xf:item>
>    <xf:label>Mary Smith</xf:label>
>    <xf:value>987-65-4321</xf:value>
> </xf:item>


Thanks for your answer.

So... I see that a <value> element carrying a "ref" attribute can be used within an <itemset> (so long as the value of the "ref" attribute is a relative location path).

However, I still don't see how the child elements of <value> can be used with an <itemset> or within an <item>.   Why is there a wildcard in the content model of the <value> element?

<xsd:any namespace="##any" processContents="skip" minOccurs="0" maxOccurs="unbounded"/>

Alessandro


> > 
> > So my question is, in what cases (if any) would a <value> 
> element contain a child element?
> > 
> 
> I can't think of an example of this off of the top of my head.
> 
> --Aaron
> 
Received on Friday, 21 July 2006 21:05:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:22:05 GMT