- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Wed, 18 Mar 2015 09:26:24 +0000
- To: Francois Daoust <fd@w3.org>
- CC: Ingar Mæhlum Arntzen <ingar.arntzen@gmail.com>, "public-webscreens@w3.org" <public-webscreens@w3.org>
Hi Francois, > On 18 Mar 2015, at 10:33, Francois Daoust <fd@w3.org> wrote: > > 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 ;) It looked like something that's beyond first stab for someone who's not an expert in distributed synchronization :-) [...] > 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. Good to be aware of the work nevertheless, so thanks for sharing -- even if it was not meant to be ready for prime time yet. >> 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! Ok, then I won't bring this up in the WG. Thanks, -Anssi
Received on Wednesday, 18 March 2015 09:26:58 UTC