- From: Francois Daoust <fd@w3.org>
- Date: Fri, 24 Jul 2015 16:04:13 +0200
- To: public-webtiming@w3.org
Dear Multi-Device Timing Community Group participants, As you may have gathered from previous emails sent to the mailing-list, I have made a few updates to the Timing Object specification recently and started to raise issues against it. The goal was to have a technical spec that explains how the suggested approach could work so that we have a basis for discussions. I would now like to request that everyone here reviews the latest draft and send comments and/or raise issues on GitHub: Latest draft: https://webtiming.github.io/timingobject/ Issues on GitHub: https://github.com/webtiming/timingobject/issues Would the spec fit your needs? Would it be easy to use? Can it be implemented? The spec defines in particular: 1. what a timing object is 2. how a timing object can be associated with an online timing resource through a third-party TimingProvider object 3. how a media element can be extended to use a TimingObject as timing source 4. how a timing object can be used to sequence TextTrack objects I did not attempt to spec out a chaining mechanism between TimingObjects, see: https://github.com/webtiming/timingobject/issues/13 There remain "grey" areas in the spec. For instance the section that describes the association between a media element and a TimingObject is incomplete. Of course, pull requests on the spec are more than welcome! Among other thing, the examples section needs to be completed, some use cases as well, and procedures need to be reviewed and fixed, in particular to adjust how they interact with the event loop. If people are are satisfied with the direction of this spec, the idea would be to get in touch with relevant groups early September to gather further feedback and possible implementors interest. Thanks, Francois.
Received on Friday, 24 July 2015 14:04:22 UTC