Community & Business Groups

Drafts / licensing information

Name
Universal DID-Native Addressing (UDNA) Architecture 1.0
Read more
  • Universal Images Community Group

    Our goal is to provide tools and specifications for creatives and agencies to create and distribute multi-format images. These are images which contain metadata that lets them adjust to different sizes, depending of the format of the output device or the layout of the website it is used in. These images can be used to have a web-server automatically create the alternative versions needed for a responsive website.

    Drafts / licensing information

    Name
    Responsive Metadata XMP Standard
    Read more
  • User Journey Graph (UJG) Community Group

    Problem: User journeys are often documented as diagrams and narratives, but they rarely get implemented as designed. Design and Product lack a precise artifact they can follow 1:1, and Engineering lacks a clear way to validate whether the implementation matches the intended journey.

    Mission: The User Journey Graph (UJG) Community Group will define an interoperable, machine-readable representation of user journeys so that design, PM, and engineering can share the same explicit “source of truth” and verify alignment over time.

    Scope: Define the core UJG model and modular specifications (e.g., serialization), plus guidance and examples for exchanging, reviewing, versioning, and validating journeys across tools.

    Who should participate: People building journey/UX tooling, product analytics, workflow/process mining, graph data, and interoperability formats.

    This group may publish Specifications.

    Drafts / licensing information

    Name
    First Editors’ Draft
    UJG 1.0 Release Candidate 1
    Read more
  • Virtual Reality website and Metaverse Community Group

    This group is to start a discussion on how to level up our current world wide web to 3d and virtual reality.

    Drafts / licensing information

    Name
    Technologies to be investigated for VR and multiverse viability
    Read more
  • Voice Interaction Community Group

    Existing W3C voice interaction standards such as VoiceXML are based on use cases centered around telephony-based voice systems. The typical interaction style that these standards support is system-initiated directed dialog using grammars to constrain the speech recognizer. In recent years, interaction with voice applications has become much more flexible, with a user-initiated dialog style and significantly fewer constraints on spoken input. Many of these new applications take the form of "virtual assistants". These include general-purpose assistants (for example, Siri, Cortana, Google Now and Alexa) as well as virtual assistants with specialized domain expertise. The proposed Community Group will collect new use cases for voice interaction, develop requirements for applications such as virtual assistants and explore areas for possible standardization, possibly producing specifications if appropriate. Depending on interest, this exploration could include such topics as (1) discovery of virtual assistants with specific expertise, for example a way to find a virtual assistant that can supply weather information (2) standard formats for statistical language models for speech recognizers (3) standard representations for references to common concepts such as time (4) interoperability for conversational interfaces and (5) work on dialogue management or ‘workflow' languages . New functionality for existing voice standards can also be a topic of discussion. Speech application developers and voice user interface designers should be particularly interested in this group.

    Drafts / licensing information

    Name
    JSON Representation of Semantic Information
    Architecture and Potential for Standardization
    Intelligent Personal Assistant Architecture
    Architecture Requirements for Intelligent Personal Assistants
    Read more
  • Web and Broadcasting Business Group

    The aim of the Web and Broadcasting Business Group was to study and clarify the influence of Open Web Platform on the professional world of broadcasting, and to help stakeholders within the broadcasting industry to build good and practical understanding on the standardization processes in W3C with the chair-to-chair communication mechanism built into business groups.

    Drafts / licensing information

    Name
    Towards a Smarter Combination of Broadcasting and the Web
    Identity Technologies on the Web: A Primer
    Repository of Existing Business-Level Use Cases for TVs In Tandem With Other Screens that Enrich Programs and Commercials via the Web
    Read more
  • Web Components Community Group

    This group is for collaboration between people working on web components libraries, tools, documentation and standards.

    We will work together on projects of shared interest in order to enhance interoperability, solve common problems, build shared community resources, and ultimately continue to grow a cooperative, productive, and happy web components ecosystem.

    Areas we expect to work on include gap analysis, design principles, common protocols, discoverability and quality, documentation, tooling, and more.

    Drafts / licensing information

    Name
    Web Components Community Group: 2021 Spec/API status
    Read more
  • Web Crypto API Community Group

    This group discusses Web Crypto APIs for signing the message by the user certificate issuing from the certificate authority for SSL communications. It is based on http://html5.creation.net/webcrypto-api/

    Drafts / licensing information

    Name
    Web Crypto API — An Authentification of Data and People in SSL
    Read more
  • Web Hypertext Application Technology Community Group

    See the WHATWG and the Memorandum of Understanding Between W3C and WHATWG. Community group around the HTML living specification and its related Web Application technology specifications.

    Final reports / licensing information

    Date Name Commitments
    URL Standard Licensing commitments

    Drafts / licensing information

    Name
    Encoding
    Fullscreen
    Quirks Mode
    Read more
  • Web Media API Community Group

    Media web application developers want to deploy their content on a wide and heterogeneous range of devices and platforms, e.g. televisions, set-top boxes, and mobile devices. To ensure a smooth user experience across devices, these user agents need to support a minimum set of Web technologies that developers can rely on being supported. This Community Group plans to specify such a set of Web technologies and additionally plans to provide guidance for developers and implementers e.g. on performance constraints and portability issues.

    See the CG charter for more information.

    Final reports / licensing information

    Date Name Commitments
    Web Media API Snapshot 2024 Licensing commitments
    Web Media API Snapshot 2024 (April 2025 update with Errata) Licensing commitments
    Web Media API Snapshot 2025 Licensing commitments
    Web Media API Snapshot 2017 Licensing commitments
    Web Media Application Developer Guidelines Licensing commitments
    Web Media API Snapshot 2018 Licensing commitments
    Web Media API Snapshot 2019 Licensing commitments
    Web Media API Snapshot 2020 Licensing commitments
    Web Media API Snapshot 2021 Licensing commitments
    Web Media API Snapshot 2022 Licensing commitments
    Web Media Application Developer Guidelines (deprecated) Licensing commitments
    Web Media API Snapshot 2023 Licensing commitments
    Read more
  • Web Media Text Tracks Community Group

    This group will work on text tracks for video on the Web, applied to captioning, subtitling and other purposes. This group plans to work initially on: 1) Documenting a semantic model underlying the caption formats in use, notably TTML, CEA 608/708, EBU STL, and WebVTT. 2) Creating a community specification for WebVTT. 3) Defining the mappings between WebVTT and some selected formats, including at least TTML (W3C/SMPTE), and CEA 608/708. 4) Creating web developer reference and tutorial material, including worked examples. 5) Creating a test suite and/or tools. A possible transition to REC-track for some of these document(s) is envisaged and that possibility will be used to guide the work and procedures. The group may produce recommendations for work in other groups, such as CSS, HTML5, and TTWG.

    Final reports / licensing information

    Date Name Commitments
    WebVTT Licensing commitments

    Drafts / licensing information

    Name
    Conversion of 608/708 captions to WebVTT
    Read more
  • Web NFC Community Group

    The Web NFC Community Group will create a Near Field Communication API that is browser-friendly and adheres to the Web's security model. We believe that means the API will not expose full, low level NFC functionality, but rather a higher level subset that is safe for Web pages, protects user privacy, and does not annoy users with unnecessary or complex permission requests. See the Web NFC Community Group Charter and the Web NFC specification for more information.

    Drafts / licensing information

    Name
    Web NFC
    Read more
  • Web Payments Charter Development Community Group

    See the Web Payments Interest Group http://www.w3.org/Payments/IG/ This group was set up as a follow-up on the W3C Web Payments Workshop that took place 23-24 March 2014. The workshop participants advocated W3C to launch a dedicated steering group (W3C Interest Group) to engage further in the development of core standard technologies to better support payments on the Web. This community group is a first step in that direction, and will host the discussions around the future charter of the interest group. The objective is to ensure that all stakeholders are able to provide inputs on the role and actions of the future group, and to ensure that a critical mass of representatives from the different stakeholder groups are ready to engage in this work. This group will not publish specifications.

    Final reports / licensing information

    Date Name Commitments
    W3C Web Payments Workshop Report Licensing commitments

    Drafts / licensing information

    Name
    Web Payments Interest Group Charter
    Read more
  • Web Payments Community Group

    What follows is the original mission statement. The purpose of the Web Payments Community Group is to discuss, research, prototype, and create working systems that enable Universal Payment for the Web. The goal is to create a safe, decentralized system and a set of open, patent and royalty-free specifications that allow people on the Web to send each other money as easily as they exchange instant messages and e-mail today. The group will focus on transforming the way we reward each other on the Web as well as how we organize financial resources to enhance our personal lives and pursue endeavors that improve upon the human condition.

    Final reports / licensing information

    Date Name Commitments
    Web Payments CG Use Cases 1.0 Licensing commitments

    Drafts / licensing information

    Name
    Web Payments Design Principles 1.0
    Web Payments CG Roadmap 1.0
    Web Payments CG Commerce 1.0
    Web Payments CG Web Commerce API 1.0
    Web Payments CG Commerce Vocabulary 1.0
    Web Payments CG Web Payments Vocabulary 1.0
    Web Payments CG HTTP Signatures 1.0
    Web Payments CG Secure Messaging 1.0
    Web Payments CG Security Vocabulary 1.0
    Read more
  • Web Thing Protocol Community Group

    The mission of this group is to define a common protocol for communicating with connected devices over the web, to enable ad-hoc interoperability on the Web of Things. Deliverables of the group may include use cases, requirements and specifications. The group will collaborate with the W3C Web of Things Interest Group and Working Group to ensure any specifications complement or extend the “Web of Things (WoT) Thing Description” specification. Objectives:
    1. Define a WebSocket sub-protocol for the Web of Things, using the W3C “Web of Things (WoT) Thing Description” data model and operations
    2. Define an HTTP protocol binding for the Web of Things (or support the Web of Things Working Group in defining this protocol binding and ensuring consistency with the WebSocket sub-protocol where appropriate)
    3. Evaluate other potential Web of Things protocol bindings (e.g. CoAP)
    See the proposed Community Group Charter for more information.

    Final reports / licensing information

    Date Name Commitments
    Web Thing Protocol Use Cases & Requirements Licensing commitments

    Drafts / licensing information

    Name
    Web Thing Protocol
    Read more
  • Web-based Signage Business Group

    Read more
  • WebAPI Discovery Community Group

    A group to develop a mechanism for the automatic discovery of WebAPIs, by extending the schema.org vocabulary. Increasingly, large online platforms and services provide one or more Web APIs for third-party developers. Moreover, many companies build WebAPIs as their primary product (Email API, SMS API, etc.). This has resulted in an explosion of the number of WebAPIs in recent years. Developers spend a significant amount of time searching for suitable WebAPIs to meet their needs. Our intention is to work closely with Schema.org to define a WebAPI-specific extension and promote usage of this extension among API owners. In the long run, our aim is to contribute this extension into the core Schema.org vocabulary. To achieve these goals we are seeking feedback and collaboration from API owners, DX specialists, API description language experts and maintainers of various API catalogs.

    Drafts / licensing information

    Name
    WADG0001 WebAPI type extension
    Read more
  • XPath Next Community Group

    Create a place for gathering requirement from existing user of XPath, potential user of XPath and research in this area

    Drafts / licensing information

    Name
    ReadMe
    Read more