http://htmlwg.mn.aptest.com/cgi-bin/xforms-issues/MIPs?id=176;user=guest;selectid=176;statetype=-1;upostype=-1;changetype=-1;restype=-1 John: We need to make a choice … non-relevant nodes are allowed to be set with a setvalue’ how about readonly? … Apparently setting a non-relevant node doesn’t break the model encapsulation … but readonly does … so the choice is saying the model creates a readonly property that nothing else is allowed to violate … or only an annotation that affects the controls Steven: It seems like we have two cow paths here, only one of which can be paved … we need to choose the one that does the least damage Charlie: Or restricts our future movements the least John: We want readonly at the control level as well in the future I’m more focused on trying to move us in the direction we intuit now will be the correct future direction, vs. just avoiding restricting our future options. John: But if we want to encapsulate the model, we can