<\/p>\n
For an introduction to term definitions and architecture, please consult<\/p>\n
T.1 Timing Object<\/a><\/p><\/blockquote>\n<\/iframe><\/p>\n<p>The MTCG will concern itself with the following tasks.<\/p>\n<p><b>T1. TimingObject<\/b><\/p>\n<p>TimingObjects are local objects, mediating access to local or online timing resources. The TimingObject is essentially an ideal clock\/stop-watch, advancing deterministically in accordance with a system clock. So, for a mediacontroller based on a TimingObject it should take exactly 2.0 seconds for the currentTime property to advance from 3.0 to 5.0, given that playbackRate is 1.0. This deterministic behavior is required for reliable distributed synchronization. Note however that this assumption is currently not valid for HTMLMediaElements, as playback is often too slow or too fast measured relative to the local system clock. This task will draft a specification for a common API for the TimingObject, using the Shared Motion API as a starting point.<\/p>\n<p><a href=\"https:\/\/www.w3.org\/community\/webtiming\/timingobject\/\">https:\/\/www.w3.org\/community\/webtiming\/timingobject\/<\/a><\/p>\n<p> <\/p>\n<p><b>T.2 Timed Media<\/b><\/p>\n<p>Currently HTMLMediaElements accept external timing control through the association with the HTMLMediaController. MTCG will work to facilitate similar integration with the HTMLTimingObject. MTCG initially targets precise timing of HTMLMediaElements through JavaScript extension libraries, but will also discuss possible benefits of native browser support for timed media. This task shall review the current spec and implementation of the HTMLMediaElement. The task output includes bug reports, suggestions for API modifications, as well as a reference implementation of JavaScript integration with the TimingObject. This task shall also propose a test suite for the HTMLMediaElement with respect to precise timing.<\/p>\n<p><a href=\"https:\/\/www.w3.org\/community\/webtiming\/timedmedia\/\">https:\/\/www.w3.org\/community\/webtiming\/timedmedia\/<\/a><\/p>\n<p><b>T.3 Timed Data<\/b><\/p>\n<p>MTCG aims to facilitate the integration of timed data with multi-device timing by defining the TimingTextTrack, \u00a0based on the established concept of TextTrack. TimingTextTrack will not take direction from a HTMLMediaElement (as is currently the case for text tracks), but integrate directly with the TimingObject. \u00a0This task shall review the current spec and implementation of the TextTrack and TimingTextTrack. The task output includes bug reports, suggestions for API modifications, as well as a reference implementation in JavaScript, integrating with multi-device timing proxies.<\/p>\n<p><a href=\"https:\/\/www.w3.org\/community\/webtiming\/timeddata\/\">https:\/\/www.w3.org\/community\/webtiming\/timeddata\/<\/a><\/p>\n<p> <\/p>\n<p> <\/p>\n<p><b>T.4 Timing Providers<\/b><\/p>\n<p>Timing services implement a protocol allowing TimingObjects to connect, synchronize and interact with server side timing resources. As a first approach the Multi-device Timing Community Group proposes to NOT standardize such a protocol, but instead introducing the concept of a Timing Provider, allowing third party implementations of such protocols.<\/p>\n<p><a href=\"https:\/\/www.w3.org\/community\/webtiming\/timingprovider\/\">https:\/\/www.w3.org\/community\/webtiming\/timingprovider\/<\/a><\/p>\n<p> <\/p>\n","protected":false},"excerpt":{"rendered":"<p> For an introduction to term definitions and architecture, please consult T.1 Timing Object The MTCG will concern itself with the following tasks. T1. TimingObject TimingObjects are local objects, mediating access to local or online timing resources. The TimingObject is … <a href=\"https:\/\/www.w3.org\/community\/webtiming\/tasks\/\">Continue reading <span class=\"meta-nav\">→<\/span><\/a><\/p>\n","protected":false},"author":7427,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"open","template":"","meta":{"_s2mail":"yes","footnotes":""},"class_list":["post-8","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/pages\/8","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/users\/7427"}],"replies":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/comments?post=8"}],"version-history":[{"count":13,"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/pages\/8\/revisions"}],"predecessor-version":[{"id":135,"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/pages\/8\/revisions\/135"}],"wp:attachment":[{"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/media?parent=8"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/iframe><\/p>\n<p>The MTCG will concern itself with the following tasks.<\/p>\n<p><b>T1. TimingObject<\/b><\/p>\n<p>TimingObjects are local objects, mediating access to local or online timing resources. The TimingObject is essentially an ideal clock\/stop-watch, advancing deterministically in accordance with a system clock. So, for a mediacontroller based on a TimingObject it should take exactly 2.0 seconds for the currentTime property to advance from 3.0 to 5.0, given that playbackRate is 1.0. This deterministic behavior is required for reliable distributed synchronization. Note however that this assumption is currently not valid for HTMLMediaElements, as playback is often too slow or too fast measured relative to the local system clock. This task will draft a specification for a common API for the TimingObject, using the Shared Motion API as a starting point.<\/p>\n<p><a href=\"https:\/\/www.w3.org\/community\/webtiming\/timingobject\/\">https:\/\/www.w3.org\/community\/webtiming\/timingobject\/<\/a><\/p>\n<p> <\/p>\n<p><b>T.2 Timed Media<\/b><\/p>\n<p>Currently HTMLMediaElements accept external timing control through the association with the HTMLMediaController. MTCG will work to facilitate similar integration with the HTMLTimingObject. MTCG initially targets precise timing of HTMLMediaElements through JavaScript extension libraries, but will also discuss possible benefits of native browser support for timed media. This task shall review the current spec and implementation of the HTMLMediaElement. The task output includes bug reports, suggestions for API modifications, as well as a reference implementation of JavaScript integration with the TimingObject. This task shall also propose a test suite for the HTMLMediaElement with respect to precise timing.<\/p>\n<p><a href=\"https:\/\/www.w3.org\/community\/webtiming\/timedmedia\/\">https:\/\/www.w3.org\/community\/webtiming\/timedmedia\/<\/a><\/p>\n<p><b>T.3 Timed Data<\/b><\/p>\n<p>MTCG aims to facilitate the integration of timed data with multi-device timing by defining the TimingTextTrack, \u00a0based on the established concept of TextTrack. TimingTextTrack will not take direction from a HTMLMediaElement (as is currently the case for text tracks), but integrate directly with the TimingObject. \u00a0This task shall review the current spec and implementation of the TextTrack and TimingTextTrack. The task output includes bug reports, suggestions for API modifications, as well as a reference implementation in JavaScript, integrating with multi-device timing proxies.<\/p>\n<p><a href=\"https:\/\/www.w3.org\/community\/webtiming\/timeddata\/\">https:\/\/www.w3.org\/community\/webtiming\/timeddata\/<\/a><\/p>\n<p> <\/p>\n<p> <\/p>\n<p><b>T.4 Timing Providers<\/b><\/p>\n<p>Timing services implement a protocol allowing TimingObjects to connect, synchronize and interact with server side timing resources. As a first approach the Multi-device Timing Community Group proposes to NOT standardize such a protocol, but instead introducing the concept of a Timing Provider, allowing third party implementations of such protocols.<\/p>\n<p><a href=\"https:\/\/www.w3.org\/community\/webtiming\/timingprovider\/\">https:\/\/www.w3.org\/community\/webtiming\/timingprovider\/<\/a><\/p>\n<p> <\/p>\n","protected":false},"excerpt":{"rendered":"<p> For an introduction to term definitions and architecture, please consult T.1 Timing Object The MTCG will concern itself with the following tasks. T1. TimingObject TimingObjects are local objects, mediating access to local or online timing resources. The TimingObject is … <a href=\"https:\/\/www.w3.org\/community\/webtiming\/tasks\/\">Continue reading <span class=\"meta-nav\">→<\/span><\/a><\/p>\n","protected":false},"author":7427,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"open","template":"","meta":{"_s2mail":"yes","footnotes":""},"class_list":["post-8","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/pages\/8","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/users\/7427"}],"replies":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/comments?post=8"}],"version-history":[{"count":13,"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/pages\/8\/revisions"}],"predecessor-version":[{"id":135,"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/pages\/8\/revisions\/135"}],"wp:attachment":[{"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/media?parent=8"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}