Re: Circular dependencies

>
> If a compute is computationally dependent on an element in L and part of a
>> circular dependency, then an xforms-compute-error event must be dispatched
>> to the model element."
>>
>> It looks like
>>
>>         <bind ref="a" constraint=". != 13">
>>
>> is a circular dependency according to these definitions.
>
>
> Mmh, it says explicitly at the beginning "excluded are references to the
> current node's value in calculate expressions (such an instance node does
> not take itself as a dependent)." So I guess not?
>
>
> calculate != constraint
>
> This is excluded:
>
>    <bind ref="a" calculate="if(../condition, ., 0)"/>
>

Got it. In that case it seems wrong as there is clearly not a circular
dependency here.

This said it could become right in the big picture if we allowed the new
`valid()` [1], etc. functions in MIPs.

    <bind ref="a" constraint="valid(.)">

But currently we explicitly disallow/discourage this:

    "If the function is used in a model binding expression the XForms
Processor should dispatch the event xforms-binding-error Event to the
model. If the function is used in a computed expression the XForms
Processor should dispatch the event xforms-expression-error Event to the
model."

-Erik

[1]
https://www.w3.org/community/xformsusers/wiki/XPath_Expressions_Module#The_valid.28.29_Function