W3C home > Mailing lists > Public > www-forms@w3.org > June 2005

RE: Question about XML Schema validation

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Fri, 10 Jun 2005 15:44:15 +0100
Message-ID: <1F598E70-2355-4E10-939B-D9E1A9184E9C@S009>
To: "'Erik Bruchez'" <erik@bruchez.org>
Cc: <www-forms@w3.org>


Thanks for your comments on the EventXformsRevalidate topic.

> About 1.A:
>    This is still a little arcane to me, let's see what the WG 
> comes out
>    with. Maybe a rationale and example would help?

Yes, indeed. There are examples floating around so I'll try to get one of
them. (Fancy putting one in, Roland?)

> About 1.B.a.I:
>    "if true() the node must be non-empty, defined as follows:"
>    Some meaning should be associated with "must be non-empty",
>    i.e. what happens if it is not empty and it is required, i.e. the
>    node is invalid.
>    Maybe this should be clearly specified with an algorithm (like the
>    algorithm for deferred update in the spec), where it would start
>    with a boolean validity flag associated with the node, and explain
>    what happens to that flag when going through the steps.

Good suggestion--I think you're right that it's probably the only way you
can understand it.

>  > During the course of doing this, one thing jumped out 
> which is that  > the spec says events like xforms-readwrite, 
> xforms-enabled and so  > on, are dispatched during 
> xforms-revalidate (see section 4.3.5, step  > 3). However, 
> the MIPs that correspond to these events are not  > 
> themselves calculated here, but in xforms-recalculate, so 
> there is  > no way that these events can be fired at this 
> time. (Also, the event  > is cancellable, which means you'd 
> lose events like xforms-optional,  > which have nothing to do 
> with validity.)  >  > Probably another errata candidate? ;)
> The spec mentions those events:
> 1. xforms-valid/xforms-invalid (constraint, type, required 
> MIPs) 2. xforms-enabled/xforms-disabled (relevant MIP) 3. 
> xforms-optional/xforms-required (required MIP) 4. 
> xforms-readonly/xforms-readwrite (readonly MIP)
> 1) Is covered.


> 2) I don't know ;-)
> 3) xforms-optional and xforms-required can be dispatched for sure at
>     this point, right?

No, because the expressions contained in them are recalculated during

> 4) Regarding calculate: I believe we don't need to actually perform a
>     recalculation to determine whether we need to send xforms-readonly
>     and xforms-readwrite: we just need to evaluate the 
> calculate bind's
>     nodeset attribute to identify which nodes are the targets of
>     calculations, and which therefore become readonly by default. But
>     maybe that's not what you had in mind.

I'm not quite sure what you mean here, but each MIP has its own calculation
in it, and that's what needs to be recalculated, not just @calculate.



Mark Birbeck
x-port.net Ltd.

e: Mark.Birbeck@x-port.net
t: +44 (0) 20 7689 9232
w: http://www.formsPlayer.com/
b: http://internet-apps.blogspot.com/

Download our XForms processor from
Received on Friday, 10 June 2005 15:44:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:15 UTC