-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update from upstream cg/webtiming/group.json
- Loading branch information
Showing
1 changed file
with
1 addition
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,7 +2,7 @@ | |
"id": 76245, | ||
"name": "Multi-device Timing Community Group", | ||
"is_closed": false, | ||
"description": "Timing mechanisms allow operations to be executed at the correct time. The Web already has several mechanisms supporting timed operations, including setTimeout and setInterval, as well as controllers for media frameworks and animations. However, the Web lacks support for multi-device timing. A multi-device timing mechanism would allow timed operations across Web pages hosted by different devices. Multi-device timing is particularly important for the broadcasting industry, as it is the key enabler for web-based secondary device offerings. More generally, multi-device timing has wide utility in communication, collaboration and multi-screen presentation. This Community Group aims to define a common, multi-device, timing mechanism and a practical programming model. This will improve the Web as a platform for time-sensitive, multi-device Web applications.\r\n\r\nCharter : http://webtiming.github.io", | ||
"description": "<p>The Multi-Device Timing Community Group is now closed. The <a href=\"https://www.w3.org/community/reports/webtiming/CG-FINAL-timingobject-20241203/\">Timing Object</a> specification was published as a final Community Group Report in the hope that it may prove a useful basis for renewed discussions on a timing model for the Web in the future. Interested parties are encouraged to reach out to the <a href=\"https://www.w3.org/groups/ig/me/\">Media and Entertainment Interest Group</a> for coordination, through its <a href=\"mailto:[email protected]\">[email protected]</a> mailing-list (<a href=\"https://lists.w3.org/Archives/Public/public-web-and-tv/\">archives</a>).</p>\r\n\r\n<p>The <a href=\"https://www.w3.org/community/sync-on-the-web/\">Sync on the Web Community Group</a> was also created in January 2025 to identify and define the requirements, solutions, and mechanisms for reproducing sender-side state, including all data, with precise timing and minimal jitter on the client side.</p>", | ||
"shortname": "webtiming", | ||
"spec-publisher": true, | ||
"discr": "w3cgroup", | ||
|