What happens if a model contains a nested model that sets //model/static to true, i.e., how does //model/model/static behave if true? Will the child's __model__ frame be attached to the parent model's __model__ frame, or will it be attached to the world frame as per the docs and the spec?

The latter would mean that any static model will be left behind as the parent model moves, which strikes me as odd/unexpected behavior. However, I do realize that the former might cause trouble for some physics engines since they may use special optimizations if they know that a model will be static and that they may break if the object does end up moving.

If someone could clarify the behavior here, I can update the description of //model/static to reflect the discussion here.