You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Method definitions like range(), activeChildren(), editOffsets(), and activeDescendants() are included in the spec.
Given that our goal is around documenting the data model and to my knowledge these methods aren’t in the current implementations, would you mind giving some context around their inclusion in the spec?
The text was updated successfully, but these errors were encountered:
The methods documented by the specification are intended to unambiguously specify the timing model and other aspects of OTIO that are not captured by the static data model. The methods are not mean to specify an API, which is highly dependent on the target programming language and overall system requirements.
Method definitions like
range()
,activeChildren()
,editOffsets()
, andactiveDescendants()
are included in the spec.Given that our goal is around documenting the data model and to my knowledge these methods aren’t in the current implementations, would you mind giving some context around their inclusion in the spec?
The text was updated successfully, but these errors were encountered: