Re: Multi-device Timing Community Group

Hi Anssi,

On 2015-03-17 11:22, Kostiainen, Anssi wrote:
[...]
> I observed there's now a Timing Object draft spec that "aims to make it possible and easy to synchronize playback of media (and non-media) content across Web clients":
>
>    http://webtiming.github.io/timingobject/
>
> The spec attempts to address the use cases are described at:
>
>    https://lists.w3.org/Archives/Public/public-web-and-tv/2014Dec/0017.html
>
> Francois - since you're the editor of the Timing Object spec, you're probably in the best position to give us an update on how this might fit in with the potential future extensions to the Presentation API that this Community Group may be working on.

Ah, we were trying to hide the spec until Ingar fixes some of the 
nonsense I wrote in there. I guess we failed ;)

The Timing Object spec is a rough first draft attempt at defining timing 
resources on the Web while trying to align with existing HTML5 concepts. 
I don't expect the spec to be anywhere near stable at this stage. The 
main goal is to have something concrete to chew on to bootstrap 
discussions within the Multi-Device Timing Community Group. Actually, 
the spec has not yet been shared with the Community Group but will soon be.

Within the Multi-Device Timing Community Group, the idea is to follow a 
classic client-server architecture where synchronization between device 
A and device B is achieved by synchronizing each of them with an online 
timing resource hosted by some timing server S.

I do not know yet how this could fit in with potential future extensions 
to the Presentation API. There may not be any need for it to fit in, 
actually. Or the need may arise if the proposal gets extended to cover 
synchronization using peer-to-peer communication channels.


> My expectation is the work on Timing Object is too early to be of relevance to the Presentation API spec being worked on in the Working Group?

That's correct!

Francois.

Received on Wednesday, 18 March 2015 08:34:00 UTC