Review of the Timing Object specification

Hi Web and TV IG participants,

Back at TPAC in Sapporo, I presented the Timing Object specification, developed by the Multi-Device Timing Community Group to enable single- and cross-device synchronization scenarios. I took an action to send the draft spec to the Web and TV IG for review.

The Multi-Device Timing Community Group would welcome your feedback on the spec by 8 January 2016 (so that it can decide on next steps early next year). The latest draft is available for review at:

  http://webtiming.github.io/timingobject/

The Multi-Device Timing Community Group does not anticipate any major change to the specification by January. Main open issues are referenced from within the spec itself to ease review from an external perspective. The group uses GitHub to track issues otherwise:

  https://github.com/webtiming/timingobject/issues

At this stage, the CG is particularly interested in:

1. discovering Web and TV use cases and requirements that the spec may not properly address
2. discussing the proposed mechanism to associate a timing object to an external timing resource through code provided by a third-party timing resource provider;
3. evaluating the main technical hurdles from an implementation perspective.

The CG also invites all interested parties to join the Multi-Device Timing CG and let themselves known.

Thanks,
Francois.

PS: Some of you wondered at TPAC whether there existed an open-source prototype implementation of the spec in JavaScript. Ingar and Njaal have been working on it, see announcement today at:
 https://www.w3.org/community/webtiming/2015/11/30/first-implementation-of-timing-object-draft-spec/

Received on Monday, 30 November 2015 16:22:10 UTC