RE: relevant and required

Hi...

well, the idea is that both relevant and required are computed values,
and that their values can change as the user completes the form. For
example, there might be a question about (more precisely, a data item
for) the spouse's name, with required="true" (hardwired). At the same
time, the relevant property of the same data item may be set to
relevant="/data/married = 'true'" - which refers to the outcome of a
question "are you married" or some such.

In that scenario, the user would receive a form that is initialized with
"not married", hence the question about the spouse's name is disabled.
While completing the form, the user may indicate that he is married. At
that moment, the question about the spouse's name becomes relevant (in
technical terms, the relevant property is re-computed and changes state
to "true"), and input is required.
  
Does this help?

Josef

-----Original Message-----
From: Rodrigue Vaudan [mailto:vaudrodr@students.hevs.ch]
Sent: Monday, October 29, 2001 11:31 AM
To: www-forms@w3.org
Subject: relevant and required


I don't understand the difference between "... relevant=false
required=true ..." and "... relevant=false required=false ..." specified
in the last WD.
The difference specified in the WD is that, in the first case, "the
XForms User Interface may indicate that should the form control become
relevant, a value would be required". I don't know why.

Rodrigue Vaudan

Received on Monday, 29 October 2001 05:54:37 UTC