- From: <AndrewWatt2001@aol.com>
- Date: Thu, 12 Jul 2001 11:58:26 EDT
- To: Laura_Nolan@hplb.hpl.hp.com, www-forms@w3.org
- Message-ID: <d0.18514a40.287f2322@aol.com>
In a message dated 12/07/01 12:54:39 GMT Daylight Time, Laura_Nolan@hplb.hpl.hp.com writes: > 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 > > Laura, I agree with you. Of course at the moment virtually all of the detail of the XForms Model per se has still to be defined. But given some of the examples earlier in the WD ... the credit card one comes to mind ... it seems likely that if credit is the preferred method of payment then the cardnumber and cardexpiry become "relevant". I assume (or suggest) that there should be some way to combine the notion of being "relevant" and "required" as per 5.2.4 so that Waleed's desire is met. Since both the "required" and "relevant" model item properties are stated to be computed expressions it looks pretty promising to me. Andrew Watt
Received on Thursday, 12 July 2001 12:00:50 UTC