RE: XForms Requirements document

Isn't this sort of thing what the required property in the XForms Model is
supposed to address? If this property can be computed dynamically in terms
of other fields, which the WD seems to imply it is, then you could use this
to get the sort of behaviour you described. See section 5.2.4.
 
Laura Nolan
 

-----Original Message-----
From: Waleed Nema [mailto:wNema@MediaOne.net]
Sent: 11 July 2001 18:12
To: AndrewWatt2001@aol.com; www-forms@w3.org
Subject: RE: XForms Requirements document


Yes, you're right about that one but what about making a group of fields
required if one of the list is selected -as in my example?

-----Original Message-----
From: www-forms-request@w3.org [mailto:www-forms-request@w3.org]On Behalf Of
AndrewWatt2001@aol.com
Sent: Wednesday, July 11, 2001 11:38 AM
To: www-forms@w3.org
Subject: Re: XForms Requirements document


In a message dated 11/07/01 16:27:31 GMT Daylight Time, wNema@MediaOne.net 
writes: 




It would be nice to include a means for specifying a field as a "Required 
Field". Additionally, to take it a step further, one should be able to 
define a "Required-Field Mask Set" where one could define the allowable 
field combination sets of which at least one must be met. For instance, on a

search screen, the user must enter one of the following: 
a) zip code 
b) city and state, or 
c) phone number 

This requirement would fit under section 3.6.



Waleed, 

I think that functionality is already present implicitly. If an XSD Schema 
datatype is restricted so that it cannot accept an empty string (or
whatever) 
then that, I think, would work out de facto as a required field. 

Andrew Watt