From 42d83c0a2d295e8d5a13d52563233d49d06633b7 Mon Sep 17 00:00:00 2001
From: W3C Bot <w3cbot-gh@w3.org>
Date: Tue, 7 Jan 2025 15:48:22 +0400
Subject: [PATCH] Update from upstream cg/sync-on-the-web/group.json

---
 cg/sync-on-the-web/group.json | 54 +++++++++++++++++++++++++++++++++++
 1 file changed, 54 insertions(+)
 create mode 100644 cg/sync-on-the-web/group.json

diff --git a/cg/sync-on-the-web/group.json b/cg/sync-on-the-web/group.json
new file mode 100644
index 00000000..5e7d403d
--- /dev/null
+++ b/cg/sync-on-the-web/group.json
@@ -0,0 +1,54 @@
+{
+ "id": 163456,
+ "name": "Sync on the Web Community Group",
+ "is_closed": false,
+ "description": "<h4>Background</h4>\r\n\r\n<p>The utilization of data from locally connected devices has nearly become a reality, thanks to remarkable advancements over the past decade. For instance, the Web MIDI API enables bi-directional communication of MIDI messages between MIDI devices and web browser applications.\r\nNow, with the emergence of new real-time protocols like Media over QUIC, real-time utilization of data from locally connected devices is extending beyond local clients to reach remote clients across the network. This evolution makes such data usage increasingly common on the web.\r\nThese protocol advancements enable the web to deliver orchestrated, immersive experiences that seamlessly integrate virtual and real-world elements in real time.\r\nTo fully leverage these opportunities and ensure precise reproduction of such experiences on client devices, our current focus is on timing synchronization at the sender's side, particularly synchronizing data from locally connected devices.</p>\r\n\r\n<h4>Statement</h4>\r\n\r\n<p>The Sync on the Web Community Group defines its mission as follows:</p>\r\n1. Define the use cases that require \"Sync on the Web.\"\r\n2. Identify the conditions and criteria necessary to achieve \"Sync on the Web.\"\r\n3. Collaborate with related working groups to explore potential solutions for \"Sync on the Web,\" including reviewing existing implementations.</p>\r\n\r\n<h4>Out of Scope</h4>\r\n<P>Our primary focus is 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. As such, Synchronization of data from multiple clients falls outside the scope of this mission.</p>",
+ "shortname": "sync-on-the-web",
+ "spec-publisher": true,
+ "discr": "w3cgroup",
+ "_links": {
+  "self": {
+   "href": "https://api.w3.org/groups/cg/sync-on-the-web"
+  },
+  "homepage": {
+   "href": "https://www.w3.org/community/sync-on-the-web/"
+  },
+  "users": {
+   "href": "https://api.w3.org/groups/cg/sync-on-the-web/users"
+  },
+  "services": {
+   "href": "https://api.w3.org/groups/cg/sync-on-the-web/services"
+  },
+  "chairs": {
+   "href": "https://api.w3.org/groups/cg/sync-on-the-web/chairs"
+  },
+  "join": {
+   "href": "https://www.w3.org/community/sync-on-the-web/join"
+  },
+  "participations": {
+   "href": "https://api.w3.org/groups/cg/sync-on-the-web/participations"
+  }
+ },
+ "type": "community group",
+ "tr-publisher": false,
+ "group-type": "cg",
+ "identifier": "cg/sync-on-the-web",
+ "services": [
+  {
+   "href": "https://api.w3.org/services/45387",
+   "title": "RSS"
+  },
+  {
+   "href": "https://api.w3.org/services/45388",
+   "title": "Chat"
+  },
+  {
+   "href": "https://api.w3.org/services/45389",
+   "title": "Mailing List"
+  },
+  {
+   "href": "https://api.w3.org/services/45390",
+   "title": "Mailing List"
+  }
+ ]
+}
\ No newline at end of file