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

Re: server-side validation: relevance

From: Jay Knight <jhknight@gmail.com>
Date: Wed, 15 Feb 2006 18:50:51 -0600
Message-ID: <f95b617c0602151650n2da527e3o18f28c9b3ecea5e6@mail.gmail.com>
To: www-forms@w3.org

Anyone have any ideas on this?

On 2/11/06, Jay Knight <jhknight@gmail.com> wrote:
> I'm playing arround with validating xforms submission on the
> server.... and this question came up.... How can I tell if something
> was supposed to be relevant on submission?  Consider this simple
> example.
>
> <model>
>     <instance>
>         <things>
>             <something />
>             <else />
>         </things>
>     </instance>
>     <bind nodeset="something" relevant="../else = 4" />
>     <submission action="..." method="post" />
> </model>
>
> ... snip ...
>
> <input ref="something"><label>Something</label></input>
> <input ref="else"><label>Else</label></input>
>
> And two possible (valid) submitted instances are:
>
> <things>
>     <something>blah</something>
>     <else>4</else>
> </things>
>
>
> <things>
>     <else>3</else>
> </things>
>
> (Pease excuse any errors... I haven't actually tested this one out :)
>
> The idea is that "something" should only be relevant if the value of
> 'else' is 4.  The problem is that "../else = 4" is a relative xpath
> expression whose context node is /things/something, which in the case
> of the second submission is not present.  Therfore, I cannot evaluate
> that xpath expression meaningfully (so it seems).
>
> Any ideas?
>
> Jay K
>
Received on Thursday, 16 February 2006 00:50:57 GMT

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