This is the list of proposed Community and Business Groups. To express support for a group, you must have a W3C account. Once a group has sufficient support (5 supporters), W3C announces its creation, lists it on the current groups page, and people can join it to begin work.
Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.
The mission of this group is to help maintain some of the Notes originally published by the W3C Semantic Web Interest Group (now closed). This group will identify potential modifications to those Notes that account for changes to RDF, SPARQL, SHACL, OWL and other core standards, as well as the evolution of the supporting community.
Note: The original Notes were published with a document license that does not allow for derivative works without permission. The W3C staff is investigating the topic in search of an approach to enable Community Groups to evolve Specifications originally published under the W3C Document License.
This group expects to publish Specifications.
Background
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. Now, 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. These protocol advancements enable the web to deliver orchestrated, immersive experiences that seamlessly integrate virtual and real-world elements in real time. To 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.
Statement
The Sync on the Web Community Group defines its mission as follows:
1. Define the use cases that require "Sync on the Web." 2. Identify the conditions and criteria necessary to achieve "Sync on the Web." 3. Collaborate with related working groups to explore potential solutions for "Sync on the Web," including reviewing existing implementations.
Out of Scope
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.
