Proposal HTMLSequencerObject [via Multi-device Timing Community Group]

The timing group aims to improve the current timing model of the Web. The core
idea of the group is to provide a new HTMLTimingObject for precise temporal
control, and to modify/extend HTMLMediaElements and HTMLTrackElements so that
they may interface directly with the HTMLTimingObject.

This proposes HTMLSequencerObject as an improvement on the HTMLTrackElement.

https://www.w3.org/community/webtiming/htmlsequencerobject/

This document is not a draft specification, but mainly a presentation of the
rationale behind this proposal. We invite feedback particularly on the following
discussion points:

 Should we, as suggested, advocate the introduction of a new
HTMLSequencerObject and keep the existing HTMLTrackElement for backward
compatibility? Or should we rather advocate changes to the original
HTMLTrackElement.
 Is HTMLSequencerObject an appropriate name? Does the term “sequencer” have
too much baggage from the context of music and audio processing? Other possible
names may include : HTMLTrackObject, HTMLSchedulerObject, other suggestions?
 What would be reasonable as next step, a draft specification for the
HTMLSequencerObject, or a bug report for the HTMLTtrackElement?

 



----------

This post sent on Multi-device Timing Community Group



'Proposal HTMLSequencerObject'

https://www.w3.org/community/webtiming/2015/05/12/proposal-htmlsequencerobject/



Learn more about the Multi-device Timing Community Group: 

https://www.w3.org/community/webtiming

Received on Tuesday, 12 May 2015 11:27:09 UTC