immersive-web / immersive-web/model-element
Rejecting stateful model content
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 86
- Forks
- 12
- Avg merge
- 7h 12m
- Merged PRs (30d)
- 1
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the explainer and the linked glTF Interactivity proposal, then compare their treatment of stateful model content with the stated visionOS behavior from versions 1.0 through 26. The work is done when the group has decided whether intrinsically stateful input files must be rejected and that decision is codified in the relevant specification text.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100