Meeting minutes
ACTION: Steven to add var evaluation to the model
https://
https://
Erik: I thought we had agreed to do textual order evaluation, but I'm not against using dependency order
… as long as we define 'dependency order' better.
Steven: Sorry, maybe I misread last week's minutes
Erik: For variables outside the model (in the view) ...
<ebruchez_> <input ref="$foo"/>
<ebruchez_> <var name="foo" value="instance()"/>
<ebruchez_> <var name="foo" value="instance()"/>
<ebruchez_> <input ref="$foo"/>
Erik: In our implementation, declaration has to come before use
Steven: So that affects scope, but not evaluation?
Steven: So we have to specify that variables need to be declared before use?
Erik: I think that is best.
Steven: Should we forbid two VARs with the same name?
Steven: Do we have scope anywhere else?
Erik: You can't see vars in the model that are declared in the view
Steven: True, but the declare before use rule would cover that
Erik: Possibly
Steven: Questions: Scope? Declare before use? Duplicate var names?
Steven: Another question: do we want a central definition of 'dependency order'.
Erik: I think that it is easier to not require dependency order
… the view can see vars in the current model
Erik: And within a scope there cannot be duplicates
Erik: Vars inside actions are not visible outside, but are allowed to have duplicate names
… XSLT has the same issues
… they allow a local variable to shadow global
ACTION: Steven to update Var evaluation accordingly
Coming calls
Steven: Calls on 13, 20th December then 2 weeks off, following call 10 Jan.
AOB
[None]
[ADJOURN]