Rejecting stateful model content #129
Description
Some 3D resources have encoding of stateful behavior - e.g. the glTF Interactivity proposal and the now-defunct (but still honored) Preliminary_Action API introduced in Reality Composer 2019.
We've discussed in the group, and indicated in the explainer, that the contents of a model resource - independent of the input format - should not be stateful in and of itself. The question, then: What do we do with input files that are intrinsically stateful? The current behavior in visionOS from 1.0 to 26 is to reject the file. Should we codify that?
/agenda