Meeting minutes
ACTION: Steven MIPs on controls
https://
https://
Steven: Any remarks?
Erik: Seems fine.
Alain: A use case with <group>
… with no binding
Steven: The same would be true of trigger
Steven: So how should we describe that?
… "If there is no binding, the property applies to the control"?
Erik: How would the processing model work then?
Alain: The properties on the control don't modify the properties of the node
Steven: So the suggestion is that the properties on the control only refer to the control, and do not affect the node if there is a binding, but combine with the properties of that node
<ebruchez> <input ref="a" relevant="false()"/>
<ebruchez> <input ref="a"/>
<input ref="a" relevant=". > 0"/>
Steven: So if a is relevant and > 0 then the whole thing is relevant; if a is < 0 it is not relevant, and if a is not relevant then neither is the input.
Alain, Erik: Yes
ACTION: Steven to update properties on controls
Steven: And do we agree that the combination rules are the same? Eg no whitespace on the control if there is one on the node?
https://
Erik: Does it even make sense to have @whitespace on controls?
… inituitively it does.
… but whitespace is more like a calculate.
Steven: My original question was about the rules for combinations.
Erik: Keep the logic, wven though there are some combinations that looks OK, for whitespace
AOB
Next call next week.
[ADJOURN]