Managing animation(s)

[zachernuk]

Many model formats have the ability to contain multiple animation tracks, with the expectation that assets will undergo "animation blending" Example in three.js

I would like to see shipping implementations initially support a single animation track played in an MVP only. But, I also believe that we should aim to support multiple animations in the future. The single-track conceptual model is supported by a top-level API for duration, play()/pause(), etc - that's not going to be adequate to manage a multi-track system.

Do we have an analog in other feature development to follow here?

[zachernuk]

/tpac

[zachernuk]

I believe the outcome of the discussion was that the root model element attributes and methods relate to a "root/master" timeline for a model, and if/when we get to the ability to present multiple animations, this leaves us room to create additional API capability to account for them without having to remove the root object's relationship to the concept of animation.

Does that sound accurate? @cabanier @LaszloGombos ? If so we can work out how to get this into the explainer or spec or both!