W3C home > Mailing lists > Public > www-forms-editor@w3.org > November 2002

Re: XForms CR - 6.1.3/6.1.4 - Catch 22 Interaction?

From: Roland Merrick <roland_merrick@uk.ibm.com>
Date: Wed, 13 Nov 2002 17:29:54 +0000
To: AndrewWatt2001@aol.com
Cc: www-forms@w3.org, www-forms-editor@w3.org
Message-ID: <OF98B1303F.D7DDDEA5-ON80256C70.005F36D6@portsmouth.uk.ibm.com>
Greetings, what you describe is the intention. e.g. I will only insist on 
knowing the name of you first born if you have indicated that you have 

i.e. <firstBornName> is specified as required.

however, it also has a relevant clause which is dependent on another 
element e.g. <hasChild/ >. 


<bind nodeset="firstBornName" required="true" relevant="hasChild = 1" />

If <hasChild> is false, <firstBornName> is irrelevant and is not 

Regards, Roland

Sent by: www-forms-request@w3.org
13/11/2002 15:52

        To:     www-forms@w3.org, www-forms-editor@w3.org, Xforms@yahoogroups.com
        Subject:        XForms CR - 6.1.3/6.1.4 - Catch 22 Interaction?


It seems to me that there is a potential problem for the user of a form if 
is possible for required="true()" and relevant="false()" to co-exist. In 
scenario the table at the end of 6.1.4 indicates that the required by
non-relevant form control would likely be inaccessible to the user (unless 
had diagnostic powers which it is probably unreasonable to expect).

As I read the CR it would not be possible to submit the form because
required="true()" and the data hasn't been entered and it might not be
possible to access the required form control because relevant="false()".

Hopefully such a situation would occur rarely, but wouldn't it be better 
ensure that it cannot happen? It seems to me that it might be better if 
were a rule which indicated that a piece of data which is not relevant 
be required.

Andrew Watt
Received on Wednesday, 13 November 2002 12:30:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:25:05 UTC