Relevance W3C Groups and Web Frameworks
Web Animations
http://www.w3.org/TR/web-animations/
Web Animations provide a framework for animations with progress controls. Web animations is based on local time, and integration with multi-device timing should immediately extend its scope to multi-device, and allow Web Animations easily to be combined and synchronized with other forms of linear media.
Web MIDI
http://www.w3.org/community/webmidi/
http://webaudio.github.io/web-midi-api/
Web MIDI provides integration with the classical MIDI protocol. This means that Web browsers may take part in controlling musical instruments (e.g. the beat), and also be controlled by external MIDI controllers. MIDI is a pulse-driven protocol, and its scope is therefore mostly limited to cabled, in-house setups. Multi-device timing for Web could be used to remove this limitation and allow global MIDI sync.
Web Audio
http://www.w3.org/community/audio-dev/
https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html
The Web Audio API offers web support for creation and playback of music. The core of this framework has much to do with timing, as the framework allows music to be generated from combining audio samples, sequentially and in parallel. Multi-device timing would enable these tools to be put to work in multi-device scenarios, such as collaborative live music production and multi-device concerts.
Remote DOM
http://www.w3.org/community/remotedom/
The Remote DOM CG suggests a programming model where a source device can control a target device programmatically, through operations on a proxy DOM. The proxy may exchange DOM events directly with a remote device, or via a server. In any case, multi-device timing would enable precisely timed operations across source and target, e.g. video on target, audio on source.
Second Screen Presentation
http://www.w3.org/community/webscreens/
The Second Screen Presentation aims to provide an API for launching and controlling HTML pages on secondary devices. Multi-device timing may be particularly relevant for control of time sensitive features, such as media playback, or if symmetric control is required (e.g., pause video on second screen, resume from first). Additionally, multi-device timing will be useful in scenarios involving more than one secondary screen.
TV Control API
http://www.w3.org/community/tvapi/
TV Control API aims to provide access to program related information (e.g., EPG) and allow Web based interaction to switch channels and control the co-presentation of supplementary content in HTML5 overlays. Multi-device timing would help Web-based overlays be timed correctly, and possibly also share timing information with smart devices used for personal interaction and control. Looking further ahead, it is also imaginable that tuners may use multi-device timing to schedule presentation of broadcast content, thereby providing a time consistent experience across different platforms and devices.
Timed Text and Web Media Text Tracks
http://www.w3.org/community/timed-text/
http://www.w3.org/community/texttracks/
Timed Text and Web Media Text Tracks are concerned with standardization of data formats for timed text such as the TTML specification (Timed Text Markup Language). Multi-device timing is generally relevant for timed data formats, as it enables multi-device playback of such resources. However, by virtue of being data agnostic, multi-device timing opens up for of any kind of timed data source, be it timed css, html, JSON, geographical data or audio samples. In short, time-sensitive, web-based playback only requires an application-specific JavaScript parser in order to extract relevant timing info from application-specific data format, and then feed it into a TrackElement (connected to a multi-device timing source) .
SMIL (Synchronized Multimedia Integration Language) http://www.w3.org/TR/SMIL3/smil-timing.html
SMIL defines an extensive framework for declarative authoring and execution of timed web-based media. Similar to Web animations, the execution model is based on local time and interactive controls are supported. Integration with multi-device timing would allow SMIL to escape the single screen limitation, or to be used as component in a larger productions.
