Community Groups | Discover W3C groups

<!doctype html> <html dir="ltr" lang="en" class="no-js"> <head> <title>Community Groups | Discover W3C groups | W3C</title> <meta charset="utf-8"/> <meta name="viewport" content="width=device-width, initial-scale=1"> <meta name="description" content="The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards."/> <meta name="thumbnail" content="https://www.w3.org/assets/website-2021/images/w3c-opengraph-image.png"/> <meta property="og:url" content="https://www.w3.org/groups/cg/"/> <meta property="og:type" content="website"/> <meta property="og:title" content="Community Groups"/> <meta property="og:image" content="https://www.w3.org/assets/website-2021/images/w3c-opengraph-image.png"/> <meta property="og:image:width" content="1200"/> <meta property="og:image:height" content="630"/> <meta property="og:description" content="The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards."/> <meta property="og:site_name" content="W3C"/> <meta name="twitter:card" content="summary_large_image"/> <meta name="twitter:site" content="w3c"/> <meta name="twitter:url" content="https://www.w3.org/groups/cg/"/> <meta name="twitter:title" content="Community Groups"/> <meta name="twitter:description" content="The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards."/> <meta name="twitter:image" content="https://www.w3.org/assets/website-2021/images/w3c-opengraph-image.png"/> <link rel="home" href="https://www.w3.org/"/> <link rel="stylesheet" href="/assets/website-2021/styles/core.css?ver=1.4" media="screen"/>  <link rel="stylesheet" id="advanced-stylesheet" href="/assets/website-2021/styles/advanced.css?ver=1.4" media=" only print, only all and (pointer: fine), only all and (pointer: coarse), only all and (pointer: none), only all and (min--moz-device-pixel-ratio:0) and (display-mode:browser), (min--moz-device-pixel-ratio:0) and (display-mode:fullscreen) "> <link rel="stylesheet" href="/assets/website-2021/styles/print.css" media="print"/> <link rel="stylesheet" href="/_sf/build/styles/917.ec064f2802ca2db0aa97.css"> <script src="/assets/website-2021/js/libraries/fontfaceobserver.js"></script> <script> var myFont = new FontFaceObserver('Noto Sans'); Promise.all([myFont.load()]).then(function () { document.documentElement.className += " fonts-loaded"; }); (function () { var linkEl = document.getElementById('advanced-stylesheet'); if (window.matchMedia && window.matchMedia(linkEl.media).matches) { var script = document.createElement('script'); script.src = '/assets/website-2021/js/main.js?ver=1.4'; script.defer = true; document.querySelector('head').appendChild(script); (function (H) { H.className = H.className.replace(/\bno-js\b/, 'js') })(document.documentElement); } })(); </script> <script src="/_sf/build/js/runtime.5282c7bdf5acd937a88e.js"></script><script src="/_sf/build/js/app.8e568c15507562ca860a.js"></script> </head> <body class="listing"> <a class="skip-link" href="#main">Skip to content</a> <div class="grid-wrap"> <div class="wrap"> <header class="global-header"> <span role="status" aria-live="polite"></span> <nav id="lang-nav" aria-label="Language options"> <div class="l-center"> <div class="l-cluster"> <ul class="clean-list" role="list"> <li><a href="https://www.w3.org/ja/" hreflang="ja" lang="ja">日本語ホームページ<span class="visuallyhidden" lang="en">Japanese website</span></a></li> <li><a href="https://www.w3.org/zh-hans/" hreflang="zh-hans" lang="zh-hans">简体中文首页<span class="visuallyhidden" lang="en">Chinese website</span></a></li> </ul> </div> </div> </nav> <nav id="global-nav" aria-label="Main"> <div class="global-nav__inner l-center"> <a class="logo-link" href="https://www.w3.org/" hreflang="en"> <span class="logo"> <img src="https://www.w3.org/assets/logos/w3c/w3c-no-bars.svg" alt="W3C" role="img"/> </span> <span class="visuallyhidden">Visit the W3C homepage</span> </a> <button type="button" class="button button--ghost with-icon--after with-icon--larger" data-trigger="mobile-nav" style="display: none;"></button> <ul data-component="nav-double-intro"> <li class="top-nav-item has-children"> <a href="https://www.w3.org/standards/" class="nav-link">Standards</a> <div class="nav__submenu" data-nav="submenu" style="display: none;"> <div class="l-center"> <div class="nav__submenu__intro"> <h2 class="nav__submenu__intro__heading">Standards</h2> <div class="nav__submenu__intro__text"> <p>Understand the various specifications, their maturity levels on the web standards track, and their adoption.</p> <a href="https://www.w3.org/standards/">Explore web standards</a> </div> </div> <ul> <li > <a href="https://www.w3.org/standards/about/">About W3C web standards</a> </li> <li > <a href="https://www.w3.org/TR/">W3C standards & drafts</a> </li> <li > <a href="https://www.w3.org/standards/types/">Types of documents W3C publishes</a> </li> <li > <a href="https://www.w3.org/translations/">Translations of W3C standards & drafts</a> </li> <li > <a href="https://www.w3.org/standards/review/">Reviews & public feedback</a> </li> <li > <a href="https://www.w3.org/liaisons/">Liaisons</a> </li> <li > <a href="https://www.w3.org/get-involved/promote/">Promote web standards</a> </li> </ul> </div> </div> </li> <li class="top-nav-item has-children"> <a href="https://www.w3.org/groups/" class="nav-link">Groups</a> <div class="nav__submenu" data-nav="submenu" style="display: none;"> <div class="l-center"> <div class="nav__submenu__intro"> <h2 class="nav__submenu__intro__heading">Groups</h2> <div class="nav__submenu__intro__text"> <p>A variety of groups develop Web Standards, guidelines, or supporting materials.</p> <a href="https://www.w3.org/groups/">About W3C groups</a> </div> </div> <ul> <li > <a href="https://www.w3.org/groups/wg/">Working Groups</a> </li> <li > <a href="https://www.w3.org/groups/ig/">Interest Groups</a> </li> <li > <a href="https://www.w3.org/groups/cg/">Community Groups</a> </li> <li > <a href="https://www.w3.org/groups/bg/">Business Groups</a> </li> <li > <a href="https://www.w3.org/groups/other/tag/">Technical Architecture Group</a> </li> <li > <a href="https://www.w3.org/invited-experts/">Invited Experts</a> </li> <li > <a href="https://www.w3.org/guide/">Participant guidebook</a> </li> <li > <a href="https://www.w3.org/about/positive-work-environment/">Positive work environment</a> </li> </ul> </div> </div> </li> <li class="top-nav-item has-children"> <a href="https://www.w3.org/get-involved/" class="nav-link">Get involved</a> <div class="nav__submenu" data-nav="submenu" style="display: none;"> <div class="l-center"> <div class="nav__submenu__intro"> <h2 class="nav__submenu__intro__heading">Get involved</h2> <div class="nav__submenu__intro__text"> <p>W3C works at the nexus of core technology, industry needs, and societal needs.</p> <a href="https://www.w3.org/get-involved/">Find ways to get involved</a> </div> </div> <ul> <li > <a href="https://www.w3.org/ecosystems/">Browse our work by industry</a> </li> <li > <a href="https://www.w3.org/membership/">Become a Member</a> </li> <li > <a href="https://www.w3.org/Member/">Member Home (restricted)</a> </li> <li > <a href="https://www.w3.org/email/">Mailing lists</a> </li> <li > <a href="https://www.w3.org/donate/">Make a donation</a> </li> <li > <a href="https://www.w3.org/sponsor/">Sponsor an event</a> </li> </ul> </div> </div> </li> <li class="top-nav-item has-children"> <a href="https://www.w3.org/resources/" class="nav-link">Resources</a> <div class="nav__submenu" data-nav="submenu" style="display: none;"> <div class="l-center"> <div class="nav__submenu__intro"> <h2 class="nav__submenu__intro__heading">Resources</h2> <div class="nav__submenu__intro__text"> <p>Master Web fundamentals, use our developer tools, or contribute code.</p> <a href="https://www.w3.org/resources/">Learn from W3C resources</a> </div> </div> <ul> <li > <a href="https://www.w3.org/developers/">Developers</a> </li> <li > <a href="https://www.w3.org/developers/tools/">Validators & tools</a> </li> <li > <a href="https://www.w3.org/WAI/fundamentals/">Accessibility fundamentals</a> </li> <li > <a href="https://www.w3.org/International/i18n-drafts/nav/about">Internationalization</a> </li> <li > <a href="https://www.w3.org/translations/">Translations of W3C standards and drafts</a> </li> <li > <a href="https://www.w3.org/policies/code-of-conduct/">Code of conduct</a> </li> <li > <a href="https://www.w3.org/reports/">Reports</a> </li> </ul> </div> </div> </li> <li class="top-nav-item has-children"> <a href="https://www.w3.org/news-events/" class="nav-link">News & events</a> <div class="nav__submenu" data-nav="submenu" style="display: none;"> <div class="l-center"> <div class="nav__submenu__intro"> <h2 class="nav__submenu__intro__heading">News & events</h2> <div class="nav__submenu__intro__text"> <p>Recent content across news, blogs, press releases, media; upcoming events.</p> <a href="https://www.w3.org/news-events/">Follow news & events</a> </div> </div> <ul> <li > <a href="https://www.w3.org/news/">News</a> </li> <li > <a href="https://www.w3.org/blog/">Blog</a> </li> <li class="break-after"> <a href="https://www.w3.org/press-releases/">Press releases</a> </li> <li > <a href="https://www.w3.org/about/press-media/">Press & media</a> </li> <li > <a href="https://www.w3.org/events/">Events</a> </li> <li > <a href="https://www.w3.org/news-events/w3c-tpac/">Annual W3C Conference (TPAC)</a> </li> <li > <a href="https://www.w3.org/policies/code-of-conduct/">Code of conduct</a> </li> </ul> </div> </div> </li> <li class="top-nav-item has-children"> <a href="https://www.w3.org/about/" class="nav-link">About</a> <div class="nav__submenu" data-nav="submenu" style="display: none;"> <div class="l-center"> <div class="nav__submenu__intro"> <h2 class="nav__submenu__intro__heading">About</h2> <div class="nav__submenu__intro__text"> <p>Understand our values and principles, learn our history, look into our policies, meet our people.</p> <a href="https://www.w3.org/about/">Find out more about us</a> </div> </div> <ul> <li > <a href="https://www.w3.org/mission/">Our mission</a> </li> <li > <a href="https://www.w3.org/about/leadership/">Leadership</a> </li> <li > <a href="https://www.w3.org/staff/">Staff</a> </li> <li > <a href="https://www.w3.org/evangelists/">Evangelists</a> </li> <li class="break-after"> <a href="https://www.w3.org/careers/">Careers</a> </li> <li > <a href="https://www.w3.org/about/diversity/">Diversity</a> </li> <li > <a href="https://www.w3.org/about/corporation/">Corporation</a> </li> <li > <a href="https://www.w3.org/sponsor/">Sponsoring W3C</a> </li> <li > <a href="https://www.w3.org/about/press-media/">Media kit</a> </li> <li > <a href="https://www.w3.org/contact/">Contact</a> </li> <li > <a href="https://www.w3.org/policies/">Policies & legal information</a> </li> <li > <a href="https://www.w3.org/help/">Help</a> </li> </ul> </div> </div> </li> <li class="top-nav-item"> <a hreflang="en" href="https://www.w3.org/help/search/" class="nav-link icon-link"> <img class="icon" src="https://www.w3.org/assets/website-2021/svg/search.svg" width="24" height="24" alt aria-hidden="true"><span class="hide-at-max-width">Search</span> </a> </li> <li class="top-nav-item"> <a hreflang="en" href="https://www.w3.org/users/myprofile/" id="account-login-link" class="account-login icon-link with-icon--after"> My account <span class="avatar avatar--small icon"> <img src="https://www.w3.org/assets/website-2021/svg/avatar.svg" width="24" height="24" alt aria-hidden="true"/> </span> </a> </li> </ul> </div> </nav> </header> <nav id="breadcrumb" aria-label="Breadcrumb"> <div class="l-center"> <div class="l-cluster"> <ol class="breadcrumbs clean-list" role="list"> <li><a href="/">Home</a></li> <li><a href="/groups/">Discover W3C groups</a></li> <li><a href="/groups/cg/" aria-current="page">Community Groups</a></li> </ol> </div> </div> </nav> <main id="main" > <div class="u-full-width hero hero--listing"> <div class="l-center"> <h1>Community Groups</h1> <div class="component component--text"> <p> W3C has created Community and Business Groups to meet the needs of a growing community of Web stakeholders. Community Groups enable anyone to socialize their ideas for the Web at the W3C for possible future standardization. Business Groups provide companies anywhere in the world with access to the expertise and community needed to develop open Web technology. New W3C Working Groups can then build mature Web standards on top of best of the experimental work, and businesses and other organizations can make the most out of W3C's Open Web Platform in their domain of interest. </p> <p> Learn more about <a href="/community/">Community and Business Groups</a>. </p> </div> <form method="get" class="l-switcher filters" novalidate="novalidate"> <div> <div> <div class="field"> <label for="search"> <span class="faux-label">Search</span> </label> <input type="search" id="search" name="search" /> </div> </div> <fieldset > <div class="checkbox-item"><input type="checkbox" id="closed" name="closed" value="1" /> <label for="closed"> <span for="closed" class="faux-label">Closed</span> </label> </div> </fieldset> <div class="input-group-wrap"> <div class="input-group"> <button class="button" type="submit">Show results</button> </div> </div> </div> </form> </div> </div> <div aria-live="polite" aria-atomic="true"> There are currently 146 open Community Groups. <a href="/groups/cg/?closed=1">View closed groups</a> </div> <div class="u-full-width component component--group-list"> <div class="l-center"> <div class="group-list"> <div class="card card--group" data-component="card" id="a11yedge"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/a11yedge/"> Accessibility at the Edge Community Group </a> </h2> <p>The mission of the Accessibility at the Edge Community Group is to examine improvements to internet accessibility via "edge computing", a relatively new paradigm that focuses on performing tasks at the edge of the network. Unlike cloud computing, edge computing emphasizes activities that occur closer to the user; these could include accessibility oriented user-agent extensions, applications on content delivery networks, JavaScript-enabled capabilities, AI or ML. The group is a forum for discussing both currently available products, potentially new applications not yet commercially available, as well as objective measures of the quality of any one of these. Our tasks can include inventorying both opportunities and challenges, drafting and incubating Internet specifications for further assessment, standardization, prototyping and testing of reference implementations. A11Y-EDGE CG meetings work and operate under the <a href="https://www.w3.org/Consortium/cepc/">W3C Code of Ethics and Professional Conduct</a>.</p> </div> </div> <div class="card card--group" data-component="card" id="a11y-discov-vocab"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/a11y-discov-vocab/"> Accessibility Discoverability Vocabulary for Schema.org Community Group </a> </h2> <p>The primary objective of this group is to maintain and develop the vocabularies for the accessibility discoverability properties in schema.org, that enable discovery of accessible content. This community group is a successor to the Accessibility Metadata Project that first proposed the properties, which were based on the Access for All metadata. The group may also propose additional properties in the future, if needed.</p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/publishing/"> Publishing </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="accessibility4children"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/accessibility4children/"> Accessibility for Children Community Group </a> </h2> <p>The mission of this group is to discuss accessibility adapted for children (age appropriate, literacy relevant).</p> <p>The Community Group welcomes <a href="https://www.w3.org/community/accessibility4children/2022/01/13/invitation-to-sponsor-accommodations/">meeting accommodation sponsorship</a> through funding or complimentary services. Many thanks to Patricia Lessard, <a href="http://www.thingsentertainment.net">Things Entertainment, LLC</a> and <a href="https://dspa.org">Deaf Services of Palo Alto</a> for your donations.</p> </div> </div> <div class="card card--group" data-component="card" id="global-inclusion"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/global-inclusion/"> Accessibility Internationalization Community Group </a> </h2> <p>The mission of the Accessibility Internationalization Community Group is to improve the internationalization of: </p> <ul> <li>The Cognitive and Learning Disabilities Accessibility (COGA) Task Force</li> <li>The Accessibility Guidelines Working Group (AG)</li> </ul> <p>Scope The Accessibility Internationalization Community Group will include the following efforts: </p> <ul> <li>Improve the internationalization of COGA and AG publications.</li> <li>Develop criteria and tests for easy-to-understand language in different languages.</li> <li>Develop criteria and tests for text appearance and semantics in different writing systems</li> <li>Develop criteria and tests for additional guidance that changes based on additional language, writing system, or culture.</li> </ul> <p>The community group’s initial focus is to help internationalize two accessibility resources that are currently in development: </p> <ul> <li>The next version of Making Content Usable for People with Cognitive and Learning Disabilities </li> <li>WCAG 3.0, with two guidelines as the top priorities: “Clear Language” and “Text Appearance and Semantics,” which will have tests and criteria in different languages.</li> </ul> </div> </div> <div class="card card--group" data-component="card" id="arrm"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/arrm/"> Accessibility Roles and Responsibilities Mapping (ARRM) Community Group </a> </h2> <p>This is the community group for individuals interested in contributing to the development and maintenance of the Accessibility Roles and Responsibilities Mapping (ARRM) framework. </p> <p>The purpose of the ARRM is to guide web teams (designers, developers and content creators) and subject matter experts in successfully distributing accessibility responsibilities by roles in a web development lifecycle, so that every stakeholder understands the role that they have to play in embedding accessibility requirements and best practices in their workflow in order to make digital content more usable to - and inclusive of - people with various types of disabilities.</p> <p>This group will not publish Specifications.</p> </div> </div> <div class="card card--group" data-component="card" id="act-r"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/act-r/"> ACT Rules Community Group </a> </h2> <p>The ACT Rules Community Group (previously known as Auto-WCAG), is an open forum set up to document and harmonise the interpretation of W3C accessibility standards, such as WCAG and WAI-ARIA, for testing purposes.</p> <p>The ACT Rules Community Group (ACT-R) achieves this by bringing together the people developing, implementing and using various accessibility testing tools and methodologies to document interpretations as test rules. Test rules are defined using the ACT Rules Format, and reviewed by the community. The process of researching, documenting, and sharing knowledge from different perspectives within the group, builds towards a common understanding. Publishing rules is not an end point for harmonization, it's a starting point. By publishing such test rules, ACT-R hopes to motivate organisations to share their own insights, and encourage adoption of commonly agreed test rules.</p> <p>ACT-R is not set up to remove differences or impose changes on accessibility testing tools and methodologies. There is value in innovation and diverse approaches. Rather it aims to contribute to more consistent results, regardless of how the testing is done. Knowing when something meets a requirement, and when it does not, should be clear and consistent. </p> <p>This group will not publish specifications.</p> </div> </div> <div class="card card--group" data-component="card" id="adva11yresources"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/adva11yresources/"> Advancing Accessibility Resources Community Group </a> </h2> <p>Our goal is to engage and empower accessibility professionals to advance the W3C WAI mission through community driven initiatives. This work could include:</p> <ul> <li>Creating and maintaining a repository of community-built resources that complement WAI</li> <li>Being a group of active participants that are continually contributing to resources</li> <li>Vetting and highlighting external resources that relate to and support this group's resources</li> <li>Being available to W3C Working Groups and Task Forces to assist in writing specifications and resources</li> </ul> <p>This group will not publish Specifications.</p> </div> </div> <div class="card card--group" data-component="card" id="aikr"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/aikr/"> AI KR (Artificial Intelligence Knowledge Representation) Community Group </a> </h2> <ul> <li><a href="https://www.w3.org/community/aikr/welcome/">Welcome post</a></li> <li><a href="https://www.w3.org/community/aikr/wiki">Group's wiki</a></li> <li>See also the group's pages from the right-hand side menu</li> </ul> <p>The overall goal/mission of this community group is to explore the requirements, best practices and implementation options for the conceptualization and specification of domain knowledge in AI.</p> <p>We plan to place particular emphasis on the identification and the representation of AI facets and various aspects (technology, legislation, ethics etc) with the purpose to facilitate knowledge exchange and reuse.</p> <p>Therefore the proposed outcomes could be instrumental to research and advancement of science and inquiry, as well as to increase the level of public awareness in general to enable learning and participation.</p> <p><strong>Proposed outcomes:</strong></p> <ul> <li>A comprehensive <a href="https://www.w3.org/community/aikr/welcome/ai-kr-task-list/knowledge-sources-for-ai-kr/">list of open access resources</a> in both AI and KR (useful to teaching and research)</li> <li>A set of <a href="https://www.w3.org/community/aikr/welcome/ai-kr-task-list/metadata/">metadata</a> derived from these resources</li> <li>A <a href="https://www.w3.org/community/aikr/concept-maps/">concept map</a> of the domain</li> <li>A natural language vocabulary to represent various aspects of AI</li> <li>One or more encoding/implementations/ machine language version of the vocabulary, such as ChatBot Natural Language Understanding & Natural Language Generation</li> <li>Methods for KR management, especially Natural Language Learning / Semantic Memory</li> </ul> <p><strong>WHO SHOULD JOIN:</strong> researchers and practitioners with an interest in developing AI KR artifacts (ontology, machine learning, markup languages)</p> <p><a href="https://tinyurl.com/yb6h72w8">Editable doc</a>.</p> </div> </div> <div class="card card--group" data-component="card" id="antifraud"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/antifraud/"> Anti-Fraud Community Group </a> </h2> <p>The mission of the Anti Fraud Community Group is to identify and define scenarios involving fraud and unwanted traffic, as well as to incubate and develop web features and APIs to address those scenarios while improving user security, privacy, and accessibility. Fraud and unwanted traffic can include web activity perpetrated by botnets, attackers impersonating users, and other activity that intends to harm users or compromise web services. </p> <p>The group welcomes participation from anti-fraud service providers, common targets of unwanted traffic, browser vendors, web privacy advocates, web application developers, web hosting and cloud service providers, and other interested parties.</p> <p>The Community Group will discuss issues that server operators and anti-fraud service providers face in this area and ideas for new web features and APIs intended to be implemented in browsers or similar user agents.</p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/e-commerce/"> E-commerce </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="aria-at"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/aria-at/"> ARIA and Assistive Technologies Community Group </a> </h2> <p>How WAI-ARIA is supported by assistive technologies, such as screen readers, is highly variable. This variation in WAI-ARIA rendering adds unnecessary complexity to the development of high-quality web experiences for users of assistive technologies and places significant limitations on the types of web widgets that can be made widely accessible.</p> <p>This community group is dedicated to:</p> <p>1. helping assistive technology developers converge on a set of clear norms for baseline support of WAI-ARIA. 2. Helping web developers understand the current state of support for WAI-ARIA by assistive technologies.</p> <p>WAI-ARIA is as important to assistive technology presentation as CSS is to visual presentation. Join us to help make WAI-ARIA as reliable as CSS.</p> <p>This group will not publish Specifications.</p> </div> </div> <div class="card card--group" data-component="card" id="audio-comgp"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/audio-comgp/"> Audio Community Group </a> </h2> <p>A group to gather and incubate new features and requirements for the Web Audio API. Making it easier for the community to engage with the Audio Working Group.</p> </div> </div> <div class="card card--group" data-component="card" id="audio-description"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/audio-description/"> Audio Description Community Group </a> </h2> <p>Mission: To create an open standard file format to support audio description all the way from scripting to mixing.</p> <p>Scope: To agree requirements and propose a workable open standard file format for audio description, probably a profile of TTML2, with the intention of moving to the Rec track within a Working Group.</p> <p>Deliverables:</p> <ul> <li>Requirements document</li> <li>Draft specification document</li> <li>Explainer</li> </ul> </div> </div> <div class="card card--group" data-component="card" id="av4browsers"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/av4browsers/"> Audiovisual Media Formats for Browsers Community Group </a> </h2> <p>Over the past decade, a growing number of sound and imaging media formats have been established offering increasingly sophisticated user experiences such as High Dynamic Range (HDR) and Spatial Audio. On the imaging side, these media formats provide the technical means to facilitate increased spatial and temporal resolutions, higher bit depths, as well as varying color volumes and the mapping between them. Similarly, on the audio side, higher bit-depth, sample rates and more immersive surround sound and speech processing options are available. These experiences are facilitated through tools and technical mechanisms available to both professional and consumer content providers and are readily available for linear content types. However, options to provide such experiences through the web are still limited as potential solutions are fragmented and often insular or significantly limited in capabilities among open source as well as proprietary options. This typically results in incorrect presentation to an end user or even error messages. Therefore, there is need to consider how to support modern audiovisual formats in a W3C context. To alleviate friction in development and deployment, it seems highly beneficial to our community to synchronize open and proprietary solutions so that they can co-exist within a W3C framework. The scope of this community group is to provide a forum for those discussions. </p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/media/"> Media & Entertainment </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="gao"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/gao/"> Automotive Ontology Community Group </a> </h2> <p>The Automotive Ontology Working Group is an informal group of individuals and corporations who want to advance the use of shared conceptual structures in the form of Web ontologies for better data interoperability in the automotive industry, and this at Web scale. In particular, we want to develop extension proposals for schema.org so that automotive information can be better understood by search engines and OWL Web ontologies for the automotive industry. Also, we want to provide a forum for bringing together researchers and practitioners who are working on advancing the field.</p> </div> </div> <div class="card card--group" data-component="card" id="autoprivacy"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/autoprivacy/"> Automotive Privacy Principles Community Group </a> </h2> <p>Vehicles are becoming increasingly connected, enabling rich data and useful services. A major obstacle to transportation's information transformation is better protection of personal privacy. The Mozilla Foundation properly called in out in their assessment <a href="https://foundation.mozilla.org/en/privacynotincluded/articles/its-official-cars-are-the-worst-product-category-we-have-ever-reviewed-for-privacy/">It’s Official: Cars Are the Worst Product Category We Have Ever Reviewed for Privacy</a>.</p> <p>The goal of this Community Group is to create guiding principles specific to the automotive industry and to work in conjunction with <a href="https://covesa.global">COVESA</a> in prototyping and promoting appropriate solutions. </p> </div> </div> <div class="card card--group" data-component="card" id="webagents"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/webagents/"> Autonomous Agents on the Web Community Group </a> </h2> <p>This community group is interested in the design of Web-based Multi-Agent Systems (MAS) for the deployment of world-wide hybrid communities of people and artificial agents on the Web. </p> <p>Our aim is to design a new class of Web-based MAS that are aligned with the Web Architecture to inherit the properties of the Web (world-wide, open, long-lived, etc.), and are also transparent and accountable to support acceptance by people.</p> <p>We are especially interested in the use of Linked Data and Semantic Web standards for weaving a hypermedia fabric that enables uniform interaction among heterogeneous entities: people, artificial agents, devices, digital services, knowledge repositories, etc. We refer to this new class of Web-based MAS as Hypermedia MAS (hMAS).</p> <p>This community group brings together experts actively contributing to advances in autonomous agents and MAS, the Web Architecture and the Web of Things, Semantic Web and Linked Data, and Web standards in general — as well as any other areas that could contribute to this approach for distributed intelligence on the Web.</p> </div> </div> <div class="card card--group" data-component="card" id="bpmlod"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/bpmlod/"> Best Practices for Multilingual Linked Open Data Community Group </a> </h2> <p>The target for this group is to crowd-source ideas from the community regarding best practises for producing multilingual linked open data. The topics for discussion are mainly focused on naming, labelling, interlinking, and quality of multilingual linked data, among others. Use cases will be identified to motivate discussions. Participation both from academia and industry is expected. The main outcome of the group will be the documentation of patterns and best practices for the creation, linking, and use of multilingual linked data.</p> <p>This group will not create specifications.</p> </div> </div> <div class="card card--group" data-component="card" id="bibframe2schema"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/bibframe2schema/"> Bibframe2Schema.org Community Group </a> </h2> <p>The objective of the community group is: to facilitate a consensually agreed route for the conversion and/or mapping of bibliographic data into Schema.org; building on the development, initiated by the Library of Congress, of the BIBFRAME 2.0 Linked Data vocabulary; utilising the specifications of BIBFRAME 2.0 as a stable base to develop upon. </p> <p>The initial objectives of the community are: 1. The creation of a reference metadata mapping from BIBFRAME 2.0 to Schema.org. 2. To facilitate agreed development and open sharing of reference software implementation(s) to: Enrich BIBFRAME data with Schema.org Terms and/or Create Schema.org terms from BIBFRAME 2.0 data.</p> </div> </div> <div class="card card--group" data-component="card" id="bioschemas"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/bioschemas/"> Bioschemas for lifesciences Community Group </a> </h2> <p>Bioschemas aims to improve data interoperability in life sciences. It does this by encouraging people in the life sciences to use schema.org markup, so that their websites and services contain consistently structured information. This structured information then makes it easier to discover, collate and analyse distributed data. The main outcome of the Bioschemas community group will be a collection of specifications that provide guidelines to facilitate a more consistent adoption of schema.org markup within the life sciences. </p> </div> </div> <div class="card card--group" data-component="card" id="bc2"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/bc2/"> Blockchain2 Community Group </a> </h2> <p>The group will incubate specifications for decentralized web applications, with a goal of enhancing security, privacy, and efficiency through the use of blockchain technologies. Our first deliverable will comprise a list of value-adds and benefits that blockchain technology may be able to provide for the World Wide Web community. Subsequently, based on our findings, we aim to agree on a set of general, high-level requirements and capabilities that blockchain-based application architectures would need to fulfill in order to deliver value. Finally, we aim to explore the potential impacts of these architectures on the privacy, resiliency, incentives, and accessibility of the web, and to establish relationships with other groups to ensure alignment as these solutions are developed.</p> </div> </div> <div class="card card--group" data-component="card" id="bdns"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/bdns/"> Building Device Naming Standards Community Group </a> </h2> <p>Being able to efficiently collect, analyse and leverage data insights from buildings is a catalyst for optimising building performance, improving the use of resources and moving towards predictive maintenance and buildings that can respond to the climate emergency.</p> <p>The lack of standardised naming and labelling for connected devices in the built environment means we are failing to leverage the value of data to allow interoperability, improve building efficiency and increase occupant productivity. </p> <p>A naming and labelling standard (complementing other industry initiatives) will simplify and drive consistency thus increasing value by unlocking the application of technologies such as machine learning. </p> <p>The work of this community group will align with and complement other initiatives in the industry such as BRICK, Haystack, Omniclass, Uniclass, IFC etc. </p> <p>In scope for this work are: </p> <ul> <li>A simple specification for naming syntax</li> <li>A register of building device names and labels</li> </ul> </div> </div> <div class="card card--group" data-component="card" id="chem-web-pub"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/chem-web-pub/"> Chemistry for the Web and Publishing Community Group </a> </h2> <p>the "Chemistry for the Web and Publishing" Community Group will focus on moving beyond simply providing images of Chemistry content on the web and in published materials to a semantically rich form that will work for everybody, including persons with disabilities.</p> </div> </div> <div class="card card--group" data-component="card" id="cndid"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/cndid/"> Chinese DID & VC Community Group </a> </h2> <p>The Chinese DID & VC Community Group provides a forum to identify and discuss the technical, use cases and best practices of DID and VC technologies, with the goal to bring better user experience and collect requirements for future DID and VC related specifications. </p> </div> </div> <div class="card card--group" data-component="card" id="civics"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/civics/"> Civic Technology Community Group </a> </h2> <p>The Civic Technology Community Group will bring together those interested in civic technology, open government, and artificial intelligence to share information, to discuss these topics, to advance the state of the art, and to ensure that the Web is well-suited for these applications.</p> </div> </div> <div class="card card--group" data-component="card" id="cloud-edge-client"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/cloud-edge-client/"> Cloud-Edge-Client Coordination Community Group </a> </h2> <p>1. Goals The mission of this group is to explore mechanisms and interfaces between Cloud, Edge, and Client for computing workload offloading and orchestration. The typical use cases include AI acceleration, cloud gaming, and streaming acceleration. The goal is to explore the feasibility of defining a set of new APIs and mechanisms that enable computing workload offloading and orchestration between Cloud, Edge, and Client. It should leverage existing mechanisms as much as possible and should coordinate with related W3C working groups and other SDOs and open-source communities if necessary.</p> <p> 2. Scope of Work This group aims to discuss proposals for Cloud-Edge-Client coordination, including: - Use cases and requirements for Cloud-Edge-Client coordination - Proposals for APIs and mechanisms (including protocols) that enable computing workload offloading and orchestration between Cloud, Edge, and Client - Secure networking and trust model requirements in the context of edge computing and offload to edge.</p> <p>3. Out of Scope The following are out of scope: Actual development of standards.</p> <p>4. Success Criteria The Group will have succeeded if it can achieve the following:</p> <p>- Participation from various stakeholder communities, especially from startups and innovators in the space of distributed computing; - Consensus on a standard solution architecture for workload offloading.</p> <p>5. Deliverables Work items can be documents, such as specifications, technical reports, best practices and guidelines, use cases and requirements, white papers, etc. Work items can also be software, for instance test suites, samples, proof of concept work, etc. In general, all work items in scope of the group are welcome. If there are individuals who will commit to being editors for a document, the group should record agreement to accept it as a work item even if it conflicts with previous work adopted by the community. Newly-accepted work items that extend beyond the scope of this Community Group Charter will lead to a reconsideration of the Charter. The Community Group may vote to revise the Charter in order to include new work, or to determine that the proposed work is unrelated.</p> <p>6. Specifications The group may produce Specifications that are not on the W3C Standards track. Development of W3C Standards should be done in appropriate Working Groups.</p> <p>7. Non-Normative Reports The group may produce other Community Group Reports within the scope of this charter that are not Specifications, for instance Techinal Reports, Use Cases, Requirements, Primers, White Papers, etc.</p> <p>8. Test Suites and Other Software The group MAY produce test suites to support the Specifications. Please see the GitHub LICENSE file for test suite contribution licensing information.</p> <p>9. Dependencies or Liaisons The group may collaborate with other relevant groups within W3C.</p> <p>10. Community and Business Group Process The group operates under the Community and Business Group Process. Terms in this Charter that conflict with those of the Community and Business Group Process are void.</p> <p>As with other Community Groups, W3C seeks organizational licensing commitments under the W3C Community Contributor License Agreement (CLA). When people request to participate without representing their organization's legal interests, W3C will in general approve those requests for this group with the following understanding: W3C will seek and expect an organizational commitment under the CLA starting with the individual's first request to make a contribution to a group Deliverable. The section on Contribution Mechanics describes how W3C expects to monitor these contribution requests.</p> <p>The W3C Code of Ethics and Professional Conduct applies to participation in this group.</p> <p>11. Work Limited to Charter Scope The group will not publish Specifications on topics other than those listed under Specifications above. See below for how to modify the charter.</p> <p>12. Contribution Mechanics Substantive Contributions to Specifications can only be made by Community Group Participants who have agreed to the W3C Community Contributor License Agreement (CLA). Specifications created in the Community Group must use the W3C Software and Document License. All other documents produced by the group should use that License where possible.</p> <p>Community Group participants agree to make all contributions in the GitHub repo the group is using for the particular document. This may be in the form of a pull request (preferred), by raising an issue, or by adding a comment to an existing issue.</p> <p>All Github repositories attached to the Community Group must contain a copy of the CONTRIBUTING and LICENSE files.</p> <p>13. Transparency The group will conduct all of its technical work in public. If the group uses GitHub, all technical work will occur in its GitHub repositories (and not in mailing list discussions). This is to ensure contributions can be tracked through a software tool.</p> <p>Meetings may be restricted to Community Group participants, but a public summary or minutes must be posted to the group's public mailing list, or to a GitHub issue if the group uses GitHub.</p> <p>14. Decision Process If the decision policy is documented somewhere, update this section accordingly to link to it. This group will seek to make decisions where there is consensus. Groups are free to decide how to make decisions (e.g. Participants who have earned Committer status for a history of useful contributions assess consensus, or the Chair assesses consensus, or where consensus isn't clear there is a Call for Consensus [CfC] to allow multi-day online feedback for a proposed course of action). It is expected that participants can earn Committer status through a history of valuable contributions as is common in open source projects. After discussion and due consideration of different opinions, a decision should be publicly recorded (where GitHub is used as the resolution of an Issue). If substantial disagreement remains (e.g. the group is divided) and the group needs to decide an Issue in order to continue to make progress, the Committers will choose an alternative that had substantial support (with a vote of Committers if necessary). Individuals who disagree with the choice are strongly encouraged to take ownership of their objection by taking ownership of an alternative fork. This is explicitly allowed (and preferred to blocking progress) with a goal of letting implementation experience inform which spec is ultimately chosen by the group to move ahead with. Any decisions reached at any meeting are tentative and should be recorded in a GitHub Issue for groups that use GitHub and otherwise on the group's public mail list. Any group participant may object to a decision reached at an online or in-person meeting within 7 days of publication of the decision provided that they include clear technical reasons for their objection. The Chairs will facilitate discussion to try to resolve the objection according to this decision process.</p> <p>It is the Chairs' responsibility to ensure that the decision process is fair, respects the consensus of the CG, and does not unreasonably favour or discriminate against any group participant or their employer.</p> <p>15. Amendments to this Charter The group can decide to work on a proposed amended charter, editing the text using the Decision Process described above. The decision on whether to adopt the amended charter is made by conducting a 30-day vote on the proposed new charter. The new charter, if approved, takes effect on either the proposed date in the charter itself, or 7 days after the result of the election is announced, whichever is later. A new charter must receive 2/3 of the votes cast in the approval vote to pass. The group may make simple corrections to the charter such as deliverable dates by the simpler group decision process rather than this charter amendment process. The group will use the amendment process for any substantive changes to the goals, scope, deliverables, decision process or rules for amending the charter.</p> </div> </div> <div class="card card--group" data-component="card" id="coga-community"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/coga-community/"> Cognitive Accessibility Community Group </a> </h2> <p>Mission</p> <p>The mission of the COGA Community Group is to work with and support the <a href="https://www.w3.org/WAI/GL/task-forces/coga/wiki/Main_Page">Cognitive and Learning Disabilities Accessibility (COGA) Task Force</a> to improve web accessibility for people with cognitive and learning disabilities.</p> <p>This group supports the COGA Task Force by supplying user needs and feedback.</p> <p>Scope<br />The COGA Community Group’s work will include:<br />- Sharing challenges when using the web and other digital displays<br />- Suggesting user needs<br />- Helping with research<br />- Suggesting ways to improve accessibility for the community<br />- Reviewing COGA’s drafts<br />- Outreach and collecting feedback from the community<br />- Helping with policy and the business cases for COGA guidance<br />- Having open meetings to discuss these points<br />Open meetings may be live video conferences or in other discussion formats</p> <p>Participation</p> <p>You do not need to be an expert in all topics related to cognitive accessibility to join the community group. The COGA Community Group will work in smaller groups for specific subjects, giving you the opportunity to participate on the topics you choose.</p> <p>The COGA Community Group will also work together on some topics, brainstorming and building a community dedicated to improved access for all.</p> <p>Anyone can join this group as long as they follow the<a href="https://www.w3.org/community/about/"> community guidelines</a>.</p> <p>However, the community group will specifically benefit from including:<br />- people with learning and cognitive disabilities,<br />people with mental health challenges,<br />- caregivers, therapists and people who work with people with learning, cognitive challenges and in mental health,<br />- researchers,<br />developers, quality assurance professionals, and user interface experts,<br />industry, looking to share and support ideas, and<br />policy makers.</p> <p>Additional details of participation<br />- Joining the COGA Community Group does not involve joining the COGA Task Force.<br />- If you would prefer to join this group anonymously, please send an email to ran@w3.org.<br />- The community group will not publish specifications, but may make suggestions to the COGA taskforce.<br />- For more information about community groups, please visit <a href="https://www.w3.org/community/about/faq/">Community and Business Groups Frequently Asked Questions</a>.<br />- Short link to this document: bit.ly/coga-community</p> </div> </div> <div class="card card--group" data-component="card" id="cogai"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/cogai/"> Cognitive AI Community Group </a> </h2> <p>The real world is frustratingly uncertain, incomplete and inconsistent. This is challenging for traditional approaches to information systems, and a new paradigm is needed that combines symbolic and statistical techniques, building upon decades of work in the cognitive sciences, and over 500 million years of natural selection. This will allow us to create cognitive agents that learn and reason based upon prior knowledge and past experience, and which can satisfy the need for, transparency in decision making, and continuous learning for adapting to ever changing needs. This community group will address opportunities for cognitive agents using graphs, statistics, rules and graph algorithms, starting with an amalgam of RDF and Property Graphs, together with Web architecture for cognitive databases.</p> <p>More specifically, the Cognitive AI Community Group will work on use cases and requirements, demo's, open source, and scaling experiments. For more details, see:</p> <p>• <a href="https://github.com/w3c/cogai">Cognitive AI CG GitHub Repository</a></p> <p>• <a href="https://w3c.github.io/cogai/">Chunks and Rules Specification</a></p> <p>• <a href="https://www.w3.org/Data/demos/chunks/talks/Sentient-Web-Raggett-2020-07-31.pdf">Keynote on Cognitive AI for the 2020 Summer School on AI in Industry 4.0</a></p> <p>• <a href="https://www.w3.org/2020/sentient-web-20200608.pdf">An older talk on Cognitive AI and the Sentient Web</a></p> <p>• <a href="https://www.w3.org/Data/demos/chunks/chunks.html">Longer treatise on Cognitive AI</a></p> <p>• <a href="https://lists.w3.org/Archives/Public/public-cogai/">Public mailing list archive</a></p> <p>• <a href="https://github.com/w3c/cogai/blob/master/Contributing.md">Contributing to the Cognitive AI Community Group</a></p> </div> </div> <div class="card card--group" data-component="card" id="colorweb"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/colorweb/"> Color on the Web Community Group </a> </h2> <p>Discussion forum between CSS experts, Color Management experts, and TV/Movie/Broadcast experts to explore use cases and inform W3C specification work (such as CSS Color 4 and subsequent levels). Both SDR and HDR are in scope. Wide gamut displays and the Web is in scope. Web use of ICC (v.4 and ICCMax) is in scope.</p> <p><a href="https://w3c.github.io/ColorWeb-CG/charter.html">Current Charter</a></p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/media/"> Media & Entertainment </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="council"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/council/"> Community Council </a> </h2> <p>The mission of the Community Council is to promote Community and Business Groups and ensure that they function smoothly. The Council's activities include: documenting good community practices, reaching out to new communities, identifying opportunities for collaboration between groups, helping groups transition to the standards track if they so desire, and routine group maintenance. The Community Council will also discuss existing and new features and other ways to enhance the Community Group experience. Anyone may join the Community Council. In particular, W3C encourages Chairs of other Community and Business Groups to participate (e.g., in monthly meetings that will include W3C staff). This group will seek to make decisions when there is consensus and with due process.</p> </div> </div> <div class="card card--group" data-component="card" id="computationalicg"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/computationalicg/"> Computational Intelligence Community Group </a> </h2> <p>The Computational Intelligence Community Group's main objective is to promote engagement from members of the Computational Intelligence Research and Development community and the broader ecosystem, aiming to mold the Web's foundation for Computational Intelligence as a Service (CIaaS). The group serves as a conduit for dialogue, enabling mutual feedback between the CIaaS community and the W3C.</p> <p>The group's fundamental operation revolves around nurturing the acceptance and ongoing evolution of pertinent W3C Working Groups, such as Machine Learning, Ontology, Dataset, and WoT. The primary collaboration will be creating use cases and adopting emerging technologies related to the CIaaS ecosystem.</p> <p>The Community Group (CG) works closely with members, chapters to support additional operations that help guide the Web to its full potential for CIaaS Services. These operations include events, webinars, training, marketing, and promotional activities.</p> <p>The CG encompasses Product R&D teams, CIaaS service providers, end-users (developers, data scientists, startups, and corporations), regulatory entities overseeing service usage and application; Platforms supplying the infrastructure and tools required to execute CIaaS; Machine learning frameworks that are essential components of the CIaaS; Specific product applications or services available through CIaaS; and the AI and Machine Learning Community.</p> <p>This group aims to release W3C Community Group Reports, suggesting Use Cases and Specifications for integration into existing and forthcoming Standards.</p> </div> </div> <div class="card card--group" data-component="card" id="consent"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/consent/"> Consent Community Group </a> </h2> <p>The concept of consent plays an essential role in the use of digital technologies as an enabler of the individual’s ownership, control, and agency. Regulations such as the GDPR assert this relationship by permitting use of consent as one of the possible legal bases for the lawful practice of data processing. Through this, obtaining consent is widely practised in the digital world, and can be perceived as an essential means to enable the individual’s agency regarding the management and ownership of their personal data. While different legal frameworks specify various requirements and obligations regarding the legal validity of consent, which should be, e.g. valid, freely given, specific, informed and active; existing and ongoing research shows that the majority of people are not empowered to practice their digital right to privacy and lawful "consenting" due to various malpractices and a lack of technological means acting in the individuals' interest. This group aims to contribute towards the empowerment of humans concerning their rights of privacy and agency, by advocating interdisciplinary, pluralist, human-centric approaches to digital consent that are technologically and legally enforceable. The mission of this group is to improve the experience of digital "consenting" while ensuring it remains adherent to relevant standards and laws. For this, the group will: (i) provide a space for people and stakeholders to come together (ii) highlight and analyse concepts, issues and problems about digital consenting (iii) propose and develop solutions. Some concrete areas for the working of this group are: (a) developing interdisciplinary solutions; (b) documenting and achieving legal compliance; (c) improving the user experience; and (d) utilising existing and developing new concepts and standards for digital consent. </p> </div> </div> <div class="card card--group" data-component="card" id="cns"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/cns/"> Consent Name System Community Group </a> </h2> <p>Our mission: design and build the 3rd generation of the CNS to be deployed globally as a free commons, a sibling to the DNS. Our scope: a hyper-cube bitmap that contains 1's and 0's for ALL GLEIF (businesses/agencies), Jurisdictions, and Legal Uses of Data, set initially by jurisdictions, then businesses/agencies, and finally by data subjects. Our deliverables: essential documents and code to stand-up a working CNS as an open source server. Gen 2 docs and video: https://bit.ly/FalconCNS </p> </div> </div> <div class="card card--group" data-component="card" id="crdt4rdf"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/crdt4rdf/"> CRDT for RDF Community Group </a> </h2> <p>Conflict-Free Replicated Data Types and the local-first approach they enable are evolving very rapidly. This community group will focus on coordinating efforts to specify CRDT for RDF. There are various existing efforts already working on CRDT for RDF or some aspects of it such as:</p> <ul> <li><a href="https://inria.hal.science/hal-00686484/document">Synchronizing Semantic Stores with Commutative Replicated Data Types</a></li> <li><a href="https://afs.github.io/rdf-delta/">RDF Delta - Replicating RDF Datasets</a></li> <li><a href="https://docs.nextgraph.org/en/framework/crdts/">Conflict-Free Replicated Data Types (CRDT)</a></li> <li><a href="https://spec.m-ld.org/">m-ld Specification</a></li> <li><a href="https://vocab.noeldemartin.com/crdt/">Conflict-Free Replicated Datatypes (CRDT)</a></li> <li><a href="https://www.npmjs.com/package/rdf-dataset-changelog">rdf-dataset-changelog</a></li> <li><a href="https://ldo.js.org/api/ldo/transactions/">Linked Data Objects: Transactions</a></li> </ul> <p>As well as broader CRDT and local-first community https://localfirstweb.dev/</p> <p>This CG would offer a neutral space to help coordinate those efforts. </p> <p>This group will publish Specifications. Outcomes from this group could be submitted to a future RDF-focused WG. The work of this group could be beneficial to other groups at W3C such as the Linked Web Storage Working Group.</p> </div> </div> <div class="card card--group" data-component="card" id="credentials"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/credentials/"> Credentials Community Group </a> </h2> <p>The mission of the W3C Credentials Community Group is to explore the creation, storage, presentation, verification, and user control of credentials. We focus on a verifiable credential (a set of claims) created by an issuer about a subject—a person, group, or thing—and seek solutions inclusive of approaches such as: self-sovereign identity; presentation of proofs by the bearer; data minimization; and centralized, federated, and decentralized registry and identity systems. Our tasks include drafting and incubating Internet specifications for further standardization and prototyping and testing reference implementations.</p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/data/"> Data and knowledge </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="credibility"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/credibility/"> Credible Web Community Group </a> </h2> <p>The mission of the W3C Credible Web Community Group is to help shift the Web toward more trustworthy content without increasing censorship or social division. We want users to be able to tell when content is reliable, accurate, and shared in good faith, and to help them steer away from deceptive content. At the same time, we affirm the need for users to find the content they want and to interact freely in the communities they choose. To balance any conflict between these goals, we are committed to providing technologies which keep end-users in control of their Web experience.</p> <p>The group's primary strategy involves data sharing on the Web, in the style of schema.org, using existing W3C data standards like JSON-LD. We believe significant progress toward our goals can be reached by properly specifying "credibility indicators", a vocabulary/schema for data about content and the surrounding ecosystem, which can help a person and/or machine decide whether a content item should be trusted.</p> <p>Please see the <a href="wiki/">group wiki</a> for more details.</p> </div> </div> <div class="card card--group" data-component="card" id="css4"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/css4/"> CSS4 Community Group </a> </h2> <p>A group to debate and define CSS4.</p> <p>The umbrella term "CSS3" was incredibly useful in teaching the new additions to CSS around 2010. It seems time to loosely group together more recent additions under another umbrella, to help increase adoption and make it easier to teach. This will not change how the CSSWG operates, will not affect spec numbering, and will be separate from the official CSS snapshots. </p> <p>Discussion began at: https://github.com/w3c/csswg-drafts/issues/4770</p> <p>This WICG group is a place to work out the details. </p> </div> </div> <div class="card card--group" data-component="card" id="csvw"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/csvw/"> CSV on the Web Community Group </a> </h2> <p>Discussions and mutual support for implementers, publishers and spec developers of the technologies developed by the <a href="https://www.w3.org/2013/csvw/wiki/Main_Page">CSV on the Web</a> Working Group. The group is not chartered to change published W3C documents, but can record new issues, errata, and test cases for those specification. The CG may also discuss related work, e.g. R2RML or other potential extensions.</p> </div> </div> <div class="card card--group" data-component="card" id="dpvcg"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/dpvcg/"> Data Privacy Vocabularies and Controls Community Group </a> </h2> <p>The mission of the W3C Data Privacy Vocabularies and Controls CG (DPVCG) is to develop a taxonomy of privacy and data protection related terms, which include in particular terms from the new European <a href="http://eur-lex.europa.eu/eli/reg/2016/679/oj">General Data Protection Regulation (GDPR)</a>, such as a taxonomy of personal data as well as a classification of purposes (i.e., purposes for data collection), and events of disclosures, consent, and processing such personal data.</p> <p>The DPVCG was created as an outcome of the W3C Workshop on Data Privacy Controls and Vocabularies in Vienna in 2017, and started on 25th May 2018 – the date of the enforcement of GDPR. Since then, the DPVCG has worked to fulfil its aims and objectives, and produced the <a href="https://www.w3.org/ns/dpv">Data Privacy Vocabulary (DPV)</a> as a deliverable. </p> <p>Membership to the group is open to all interested individuals and organisations. To join the group, you need a valid W3C account – which is free to get and can be <a href="https://www.w3.org/accounts/request">requested here</a>. The group meets usually through online meeting calls, details of which, including past minutes, can be <a href="https://www.w3.org/community/dpvcg/wiki/Meeting_Calls">found here</a>. The group also interacts through a <a href="https://lists.w3.org/Archives/Public/public-dpvcg/">mailing list</a> regarding topics, discussions, sharing of agendas, actions, and other relevant items. The resources and work relevant to the group is hosted on the <a href="https://github.com/dpvcg/">GitHub platform under the DPVCG name</a>.</p> <p>The group is currently chaired by:</p> <ul><li><a href="https://harshp.com">Harshvardhan J. Pandit</a> (<a href="https://www.adaptcentre.ie/">ADAPT SFI Research Centre</a>, <a href="https://www.tcd.ie/">Trinity College Dublin</a>)</li></ul> <p>Previously, it was chaired by:</p> <ul><li><a href="https://www.w3.org/People/Bos/">Bert Bos</a> (<a href="https://www.ercim.eu/">ERCIM </a><a href="https://www.w3.org">W3C</a>)</li><li><a href="http://polleres.net/">Axel Polleres</a> <a href="https://www.wu.ac.at/">(WU Wirschaftsuniversitat Wien – Vienna University of Economics and Business</a>)</li></ul> <h2>Participation in Group Activities</h2> <p>The working of the group is fairly open and transparent in its process, with most of the information present on the <a href="https://www.w3.org/community/dpvcg/wiki/">wiki</a>. For past work, actions, issues, and records – please refer to the <a href="https://www.w3.org/community/dpvcg/wiki/">wiki</a> and threads on the <a href="https://lists.w3.org/Archives/Public/public-dpvcg/">mailing list</a>. Anyone can use the <a href="https://lists.w3.org/Archives/Public/public-dpvcg/">mailing list</a> to ask questions, suggest topics, raise issues, and offer solutions. Non-members might receive an automated reply asking them to authenticate their email or email address for posting.</p> <p>Similarly, calls are usually open to attend, with the agenda shared on the public mailing list. Call details may be shared on the internal mailing lists accessible to only members for security purposes – so it may be best to ask the chair(s) or a member for attending a call.</p> <p>General questions regarding what the group considers in scope can be determined from the aims and objectives. Specific queries or propositions should be conveyed to the mailing list. For issues regarding the DPV, including addition of concepts or a query or other relevant topics – you can use the mailing list or the issues feature in a <a href="https://github.com/dpvcg/">GitHub repo</a>.</p> <h2>Data Privacy Vocabulary (DPV)</h2> <p>The DPV is a vocabulary (terms) and an ontology (relationships) serialised using semantic-web standards to represent concepts associated with privacy and data protection, primarily derived from GDPR. It enables representation of which <em>personal data categories</em> are undergoing a what kind of <em>processing</em> by a specific <em>data controller</em> and/or transferred to some <em>recipient</em> for a particular <em>purpose</em>, based on a specific <em>legal basis</em> (e.g., consent, or other legal grounds such as legitimate interest, etc.), with specified <em>technical and organisational measures and restrictions</em> (e.g., storage locations and storage durations) in place.</p> <p>The DPV is useful as a machine-readable representation of personal data processing and can be adopted in relevant use-cases such as legal compliance documentation and evaluation, policy specification, consent representation and requests, taxonomy of legal terms, and annotation of text and data.</p> <p>The DPV is an evolving vocabulary – as the DPVCG continues to work on updating it with broader concepts as well as enriching its hierarchy of concepts. For this, we invite contributions of concepts, use-cases, requirements, and applications.</p> </div> </div> <div class="card card--group" data-component="card" id="dataspaces"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/dataspaces/"> Dataspaces Community Group </a> </h2> <p>Dataspaces gather requirements for seamless and trusted data exchange within specific domains and translate the requirements into technical specifications. The W3C already recommends standards for trust, interoperability, and data value. Our goal in this group is to collect scenarios from the dataspaces built by our members and manage best practices for implementing them with W3C specifications. Where those standards are not sufficient, we envision formulating questions to other community and working groups, and providing dataspace-specific normative text for specific scenarios. The Dataspaces Community Group aims to meet every year at the ESWC conference. </p> </div> </div> <div class="card card--group" data-component="card" id="declarative3d"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/declarative3d/"> Declarative 3D for the Web Architecture Community Group </a> </h2> <p>The mission of the Declarative 3D for the Web Architecture Community Group is to determine the requirements, options, and use cases for an integration of interactive 3D graphics capabilities into the W3C technology stack. This group is aimed to extract core features out of the requirements as foundation to propose feasible technical solutions. These should cover the majority of 3D use cases for the Web - but not necessarily all of them. There are upcoming open (e.g., WebGL) and proprietary (e.g., Adobe) proposals for imperative graphics APIs in the Web context but we are missing an easy way to add interactive high-level declarative 3D objects to the HTML-DOM to allow anyone to easily create, share, and experience interactive 3D graphics - with possibly wide ranging effects similar to those caused by the broad availability of video on the Web. The goal of this CG is to evaluate the necessary requirements for a successful standardization of a declarative approach to interactive 3D graphics as part of HTML documents.</p> </div> </div> <div class="card card--group" data-component="card" id="design-tokens"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/design-tokens/"> Design Tokens Community Group </a> </h2> <p>The Design Tokens Community Group's goal is to provide standards upon which products and design tools can rely for sharing stylistic pieces of a design system at scale.</p> </div> </div> <div class="card card--group" data-component="card" id="eocred-schema"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/eocred-schema/"> Educational and Occupational Credentials in schema.org Community Group </a> </h2> <p>The aim of this community group is to show how educational and occupational credentials may be described with schema.org, and to propose any additional terms for schema.org that may be necessary. Educational and Occupational Credentials are defined as diplomas, academic degrees, certifications, qualifications, badges, etc., that a person can obtain through learning, education and/or training. They are typically awarded on successful completion of an assessment of relevant capabilities. See also the Connecting Credentials <a href="http://connectingcredentials.org/common-language-work-group-glossary/">glossary of credentialing terms</a>.</p> <p>Related work includes: the <a href="https://credreg.net/ctdl/handbook">Credential Transparency Description Language</a> (CTDL) developed for the Credential Engine; IMS Global's <a href="https://www.badgealliance.org/">Badge Alliance</a>; and, the W3C <a href="https://www.w3.org/2017/vc/WG/">Verifiable Claims Working Group</a>. The work of this group will complement these, with a focus on integration with schema.org and on describing a credential that is being offered rather than the claim to posses one.</p> </div> </div> <div class="card card--group" data-component="card" id="reconciliation"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/reconciliation/"> Entity Reconciliation Community Group </a> </h2> <p>Matching entities across data sources using different identifiers and formats is a pervasive issue on the web. This group revolves around developing a web API that data providers can expose, which eases the reconciliation of third-party data to their own identifiers. OpenRefine's reconciliation API is used as a starting point. Our goals are to document this existing API, share our experiences and lessons learnt from it, propose an improved protocol in the view of promoting it as a standard, and build tooling around it. A description of the existing protocol can be found here: https://reconciliation-api.github.io/specs/latest/ </p> </div> </div> <div class="card card--group" data-component="card" id="epub3"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/epub3/"> EPUB 3 Community Group </a> </h2> <p>The EPUB 3 Community Group is a forum for ongoing technical development of EPUB 3 and related extension specifications and ancillary deliverables. The <a href="https://www.w3.org/2017/02/EPUB3CGcharter">EPUB 3 Community Group charter</a> contains full details. </p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/publishing/"> Publishing </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="equity"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/equity/"> Equity Community Group </a> </h2> <p>The Equity CG seeks to enable equity in W3C processes, specifications, and expertise. Equality is equal access, while 'equity' is equal outcomes (Antoinette Carroll, Creative Reaction Lab Founder (https://crxlab.org/)). The Equity CG will discuss approaches to creating more equitable specifications and implementations of those specifications. The group will determine whether it wants to address internal specifications (as in a self-review questionnaire before CR) or provide a tool for assessing equity (like WCAG). This will require recruiting experts in equity as well as those who reflect the diversity of the world and will take time. In time, the CG hopes to propose an Equity Horizontal Review Board (HRB).</p> </div> </div> <div class="card card--group" data-component="card" id="expath"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/expath/"> EXPath Community Group </a> </h2> <p>The mission of this group is to lead to extension of XPath and all related technologies (XSLT, XQuery, XProc, XForms, XML Schema).</p> </div> </div> <div class="card card--group" data-component="card" id="fed-id"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/fed-id/"> Federated Identity Community Group </a> </h2> <p>The purpose of the Federated Identity Community Group is to provide a forum focused on incubating web features that will both support federated identity and prevent untransparent, uncontrollable tracking of users across the web. While the community group will take privacy concerns into consideration, these concerns will be balanced against the need to explore innovative ideas around federated authentication on the web. </p> </div> </div> <div class="card card--group" data-component="card" id="federated-learning"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/federated-learning/"> Federated Learning Community Group </a> </h2> <p>The purpose of this community group is to establish and explore the necessary standards related with the Web for federated learning via the analysis of current implementations related with federated learning such as TensorFlow Federated. The main idea of federated learning is to build machine learning models based on data sets that are distributed across multiple clients (e.g. mobile devices or whole organizations) while preventing data leakage. Therefore, federated learning can give benefits like mitigation of privacy risks and costs.</p> </div> </div> <div class="card card--group" data-component="card" id="fibo"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/fibo/"> Financial Industry Business Ontology Community Group </a> </h2> <p>The mission of Financial Industry Business Ontology Community Group is to propose, discuss, create and maintain extensions to schema.org related to Financial Industries. </p> </div> </div> <div class="card card--group" data-component="card" id="games"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/games/"> Games Community Group </a> </h2> <p>The goal of the Games Community Group is to improve the quality of open web standards that games developers rely on to create games. To achieve its goal, the Games community group will:</p> <ul> <li>Track specifications and vendor implementations related to open web games.</li> <li>Recommend new specifications to be produced and find group homes for them.</li> <li>Refine use cases to communicate specific needs of games.</li> <li>Suggest refinements or fixes to existing specifications to better meet the needs of the game development community.</li> <li>Explore capabilities —APIs, semantics, techniques for rendering, processing, personalization, customization, interoperability, etc.— that developers can leverage to localize games and guarantee that they are accessible.</li> <li>Evangelize specifications to browser vendors.</li> <li>Document how to best use open web standards for games.</li> <li>Evangelize open web standards to game developers and game development best practices to web developers.</li> </ul> <p>The Games community group will not develop any normative specification. As such, there will not be any Essential Claims under the W3C <a href="https://www.w3.org/community/about/process/cla/">Contributor License Agreement</a> or <a href="https://www.w3.org/community/about/process/final/">Final Specification Agreement</a>.</p> <p>Please see the <a href="https://www.w3.org/2020/07/games-cg-charter.html">adopted charter</a> for details.</p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/media/"> Media & Entertainment </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="gpu"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/gpu/"> GPU for the Web Community Group </a> </h2> <p>The mission of the GPU on the Web Community Group is to provide an interface between the Web Platform and modern 3D graphics and computation capabilities present in native system platforms. The goal is to design a new Web API that exposes these modern technologies in a performant, powerful and safe manner. It should work with existing platform APIs such as Direct3D 12 from Microsoft, Metal from Apple, and Vulkan from the Khronos Group. This API will also expose the generic computational facilities available in today's GPUs to the Web, and investigate shader languages to produce a cross-platform solution. Please see the <a href="https://gpuweb.github.io/admin/cg-charter.html">draft charter</a>. The group is inviting browser engine developers, GPU hardware vendors, 3D software engineers, as well as the broader Web community who have an interest in 3D graphics and efficient computation to participate.</p> </div> </div> <div class="card card--group" data-component="card" id="schemed"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/schemed/"> Healthcare Schema Vocabulary Community Group </a> </h2> <p>This community effort aims to provide medical,healthcare and life-science specialized web schemas and vocabulary through improving and extending the existing schemas, concepts, terms and definitions in schema.org vocabulary. Ultimate goal is to enable the use of schema.org not only by webmasters but also in indexing health records, healthcare documents, and as a pillar open source of medical and healthcare and life science ontology/vocabulary for formalization of healthcare information.</p> <p>This will make healthcare and medical data on web easy to describe correctly (with their correct meaning and context), easy to expose /index so ready to be accessible and will highly improve to re-usability and exchanging in semantic way, with their correct meaning and context.</p> <p>The intention is not to replace existing ontologies, nor making upper level ontology nor creating yet another clinical information model/standards. The aim is mainly to provide most useful and frequently used (so, demand driven) classes and properties related to the medical and healthcare domain. Within this scope all concepts are mapped as far as it's feasible to the existing terminology like SNOMED CT, ICD, LOINC, ATC, RxNorm, HL7 FHIR, etc.</p> </div> </div> <div class="card card--group" data-component="card" id="humancentricai"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/humancentricai/"> Human Centric AI Community Group </a> </h2> <p>The W3C Human Centric AI Groups mission is to investigate, articulate, refine, consider and respond to the various safety and human rights related implications of Web connected online systems; and to define recommendations, and useful tools, to respond to these challenges via any applicable Human Centric AI compatible system. </p> <p>This group may produce technical specifications.</p> </div> </div> <div class="card card--group" data-component="card" id="hydra"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/hydra/"> Hydra Community Group </a> </h2> <p>Building Web APIs seems still more an art than a science. How can we build APIs such that generic clients can easily use them? And how do we build those clients? Current APIs heavily rely on out-of-band information such as human-readable documentation and API-specific SDKs. However, this only allows for very simple and brittle clients that are hardcoded against specific APIs. Hydra, in contrast, is a set of technologies that allow to design APIs in a different manner, in a way that enables smarter clients.</p> <p>The foundation is laid by the Hydra Core Vocabulary. It defines a number of fundamental concepts, such as hypermedia controls and collections, which allow machines to understand how to interact with an API. Since all information about the API is available in a machine-readable form, completely generic clients become possible. The Core Vocabulary is complemented by Linked Data Fragments, a set of specifications that enable advanced yet efficient client-side querying of Web APIs.</p> <p>More information about these technologies can be found on our homepage: http://www.hydra-cg.com/</p> </div> </div> <div class="card card--group" data-component="card" id="immersive-captions"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/immersive-captions/"> Immersive Captions Community Group </a> </h2> <p>The goal of this community group is to determine and publish best practices for access, activation, and display settings for captions with different types of Immersive Media - AR, VR & Games. </p> <p>We plan to research current examples, identify best practices, and do research on those ideas over different surfaces: Smartphone AR, AR glasses, VR goggles, etc. Where appropriate, we will share our results and discuss opportunities with the TTML WG (recommendations for media online captioning) and the W3C Immersive Web WG (APIs to interact with XR devices and sensors in browsers).</p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/media/"> Media & Entertainment </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="immersive-web"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/immersive-web/"> Immersive Web Community Group </a> </h2> <p>Our goal is to help bring high-performance Virtual Reality and Augmented Reality to the open Web.</p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/network-communications/"> Network & Communications </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="informationarchitecture"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/informationarchitecture/"> Information Architecture Community Group </a> </h2> <p>The W3C Information Architecture community group is for anyone interested in Information Architecture and standards, and to participate, discuss, share, support, develop, and learn about them.</p> </div> </div> <div class="card card--group" data-component="card" id="interledger"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/interledger/"> Interledger Payments Community Group </a> </h2> <p>The primary goal of the Interledger Payments Community Group is connecting the many payment networks (ledgers) around the world via the Web. The group's vision is an open, universal payment scheme built on Web standards that allows any payer to pay any payee regardless of the payer’s choice of payment instrument or the payee’s account.</p> </div> </div> <div class="card card--group" data-component="card" id="ixml"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/ixml/"> Invisible Markup Community Group </a> </h2> <p>We choose which representations of our data to use, JSON, CSV, XML, or whatever, depending on habit, convenience, or the context we want to use that data in. On the other hand, having an interoperable generic toolchain such as that provided by XML to process data is of immense value. How do we resolve the conflicting requirements of convenience, habit, and context, and still enable a generic toolchain? Invisible XML (ixml) is a method for treating non-XML documents as if they were XML, enabling authors to write documents and data in a format they prefer while providing XML for processes that are more effective with XML content. This is an ongoing project to provide software that lets you treat any parsable format as if it were XML, without the need for markup.</p> </div> </div> <div class="card card--group" data-component="card" id="json-ld"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/json-ld/"> JSON for Linked Data Community Group </a> </h2> <p>JSON-LD (JavaScript Object Notation for Linking Data) is a lightweight Linked Data format that gives your data context. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on the already successful JSON format and provides a way to help JSON data interoperate at Web-scale. If you are already familiar with JSON, writing JSON-LD is very easy. These properties make JSON-LD an ideal Linked Data interchange language for JavaScript environments, Web service, and unstructured databases such as CouchDB and MongoDB.</p> </div> </div> <div class="card card--group" data-component="card" id="jsxml"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/jsxml/"> JSX as markup language Community Group </a> </h2> <p>The proposal is that jsx be implemented as a dynamic markup language for the web since just HTML + DOM are still not enough to create applications like the ones we currently build using frameworks.</p> <p>With JSX updating conventional HTML ideas to create better-designed static websites and using dynamic data structures, with repetition loops and adding event hooks more easily, the group's idea would be to bring together people who share the same idea so that together we can do tests in different scenarios and create polyfills if necessary</p> </div> </div> <div class="card card--group" data-component="card" id="kg-construct"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/kg-construct/"> Knowledge Graph Construction Community Group </a> </h2> <p>The overall goal of this community group is to support its participants into developing better methods for Knowledge Graphs construction. The Community Group will (i) study current Knowledge Graph construction methods and implementations, (ii) identify the corresponding requirements and issues that hinter broader Knowledge Graph construction, (iii) discuss use cases, (iv) formulate guidelines, best practices and test cases for Knowledge Graph construction, (v) develop methods, resources and tools for evaluating Knowledge Graphs construction, and in general (vi) continue the development of the W3C-recommended R2RML language beyond relational databases. The proposed Community Group could be instrumental to advance research, increase the level of education and awareness and enable learning and participation with respect to Knowledge Graph construction. </p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/data/"> Data and knowledge </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="lbd"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/lbd/"> Linked Building Data Community Group </a> </h2> <p>This group brings together experts in the area of building information modelling (BIM) and Web of Data technologies to define existing and future use cases and requirements for linked data based applications across the life cycle of buildings. A list of recommended use cases will be produced by this community group. </p> <p>The envisioned target beneficiaries of this group are both industrial and governmental organisations who use data from building information modelling applications and other data related to the building life cycle (sensor data, GIS data, material data, geographical data, and so forth) to achieve their business processes and whom will benefit from greater integration of data and interoperability between their data sets and the wider linked data communities. For example, benefit may be obtained by publishing and combining localised data on new cheaper building materials, energy efficient building devices and systems, along with real time data on weather patterns, energy prices and geodata. By making this data available to applications, they will be better able to support decision makers during the whole of the building life cycle, which includes design, construction, commissioning, operation, retrofitting/refurbishment/reconfiguration, demolition, and recycling of buildings. </p> <p>The group will engage with these beneficiaries through surveys and events organised in conjunction with the affiliated workshop series on Linked Data for Architecture and Construction (LDAC). </p> </div> </div> <div class="card card--group" data-component="card" id="ld4lt"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/ld4lt/"> Linked Data for Language Technology Community Group </a> </h2> <p>This group aims to consult with current and potential users of linguistic data to assemble use cases and requirements for Language Technology Applications that use Linked Data. The results will be used to guide future interoperability, research and development activities spanning the language technology and linked data domains. Potential users are companies and public bodies involved in natural language processing, language resources, content management, the language services and localisation industry and other applications of content analytics techniques used in search, recommender systems, sentiment analysis and terminology management. The group does engage with users through surveys, international events and training activities organized in conjunction with partners from academia or industry, resp. designated research projects and networking efforts (esp., EU or other multi-national projects). We identify use case and requirements priorities, technology gaps and interoperability roadblocks. We work towards community group reports that describe our findings and/or solutions to the challenges identified in our work. </p> </div> </div> <div class="card card--group" data-component="card" id="maps4html"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/maps4html/"> Maps For HTML Community Group </a> </h2> <p>The Maps in HTML Community Group seeks to establish at least one hypermedia type which can be considered to be consumed by a (new) "map" element for HTML. Follow-on from Bar Camp at #lgd14. The objective will be to define a hypermedia type which can be linked to from a hypothetical (but prototyped in Web Components) "map" or (geo-map for Web Components) element which will provide simple mashup capabilities and user interface.</p> <p>This group will publish specifications.</p> </div> </div> <div class="card card--group" data-component="card" id="mcm-jp"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/mcm-jp/"> Media Content Metadata Japanese Community Group </a> </h2> <p>The mission of this group is sharing use cases, technical challenges, best practices and possible implementations for inter-industry collaboration of media content metadata to improve the interoperability of the metadata and promote media content distribution among various industries. This group facilitates discussion with Japanese companies and organizations from different industries using Japanese language.</p> <p>This group will not publish any specifications.</p> </div> </div> <div class="card card--group" data-component="card" id="metaverse-interop"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/metaverse-interop/"> Metaverse Interoperability Community Group </a> </h2> <p>Our mission is to bridge virtual worlds by designing and promoting protocols for identity, social graphs, inventory, and more.</p> </div> </div> <div class="card card--group" data-component="card" id="miniapps"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/miniapps/"> MiniApps Ecosystem Community Group </a> </h2> <p>A community group to incubate work on MiniApps and serve as a base for analysis and proposals of specific work items</p> </div> </div> <div class="card card--group" data-component="card" id="webtiming"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/webtiming/"> Multi-device Timing Community Group </a> </h2> <p>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.</p> <p>Charter : http://webtiming.github.io</p> </div> </div> <div class="card card--group" data-component="card" id="music-notation"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/music-notation/"> Music Notation Community Group </a> </h2> <p>The Music Notation Community Group develops and maintains format and language specifications for notated music used by web, desktop, and mobile applications. The group aims to serve a broad range of users engaging in music-related activities involving notation, and will document these use cases. </p> <p> The Community Group documents, maintains and updates the MusicXML and SMuFL (Standard Music Font Layout) specifications. The goals are to evolve the specifications to handle a broader set of use cases and technologies, including use of music notation on the web, while maximizing the existing investment in implementations of the existing MusicXML and SMuFL specifications. </p> <p> The group is developing a new specification to embody this broader set of use cases and technologies, under the working title of MNX. The group is proposing the development of an additional new specification to provide a standard, machine-readable source of musical instrument data. </p> </div> </div> <div class="card card--group" data-component="card" id="nordic-accessibility"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/nordic-accessibility/"> Nordic Accessibility Community Group </a> </h2> <p>The Nordic Accessibility Community Group serves as an open forum to discuss challenges, network with accessibility professionals, and promote the importance of inclusive design in the Nordic countries.</p> </div> </div> <div class="card card--group" data-component="card" id="smartcity-nordic"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/smartcity-nordic/"> Nordic Chapter Smart City / Web of Things Community Group </a> </h2> <p>A community group around smart city technologies and challenges in the nordic region</p> </div> </div> <div class="card card--group" data-component="card" id="nordic-data"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/nordic-data/"> Nordic Web of Data Community Group </a> </h2> <p>The mission of this group is to provide a forum for discussing challenges and establishing best practices for publishing data in the Nordic region.</p> <p>The foreseen focus will be on topics like: </p> <ul><li>Metadata profiles within data publishing</li> <li>Best practices for a national web of data infrastructure</li> <li>Best practices for domain specific data specifications</li> <li>How to utilize linked data principles to improve data quality and interoperability</li> </ul> <p>Practitioners in data publishing as well as anyone interested in furthering a web of data in both private and public sector are welcome to join.</p> </div> </div> <div class="card card--group" data-component="card" id="nostr"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/nostr/"> nostr Community Group </a> </h2> <p>The Nostr Protocol is a new communications for the social web, based on the w3c websockets standard. </p> <p>The mission of the Nostr Community group is to foster its intersection with web standards, documenting existing patterns and bridges, and proposing further integration with web standards.</p> <p>This group may publish Specifications.</p> </div> </div> <div class="card card--group" data-component="card" id="n3-dev"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/n3-dev/"> Notation 3 (N3) Community Group </a> </h2> <p>Further development, implementation, and standardization of Notation 3 - an assertion and logic language - including the N3 Rules language.</p> </div> </div> <div class="card card--group" data-component="card" id="odrl"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/odrl/"> ODRL Community Group </a> </h2> <p>The ODRL Community Group supports the promotion and future development of the W3C ODRL recommendations:</p> <ul class="show_items"> <li><a href="https://www.w3.org/TR/odrl-model/">ODRL Information Model</a></li> <li><a href="https://www.w3.org/TR/odrl-vocab/">ODRL Vocabulary & Expression</a></li> </ul> <p>Specifically, the ODRL CG will:</p> <ul class="show_items"> <li>Promote ODRL V2.2 to existing and new sectors/industries</li> <li>Nurture an ODRL implementors community</li> <li>Publish reports related to ODRL usage</li> <li>Support development of ODRL Profiles (and host for smaller communities)</li> <li>Register ODRL Profiles</li> <li>Collaborate with W3C on ODRL errata maintenance</li> <li>Plan for future major enhancements to ODRL (V3.0)</li> </ul> </div> </div> <div class="card card--group" data-component="card" id="ontolex"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/ontolex/"> Ontology-Lexica Community Group </a> </h2> <p>The mission of the Ontology-Lexicon community group is to: (1) Develop models for the representation of lexica (and machine readable dictionaries) relative to ontologies. These lexicon models are intended to represent lexical entries containing information about how ontology elements (classes, properties, individuals etc.) are realized in multiple languages. In addition, the lexical entries contain appropriate linguistic (syntactic, morphological, semantic and pragmatic) information that constrains the usage of the entry. (2) Demonstrate the added value of representing lexica on the Semantic Web, in particularly focusing on how the use of linked data principles can allow for the re-use of existing linguistic information from resource such as WordNet. (3) Provide best practices for the use of linguistic data categories in combination with lexica. (4) Demonstrate that the creation of such lexica in combination with the semantics contained in ontologies can improve the performance of NLP tools. (5) Bring together people working on standards for representing linguistic information (syntactic, morphological, semantic and pragmatic) building on existing initiatives, and identifying collaboration tracks for the future. (6) Cater for interoperability among existing models to represent and structure linguistic information. (7) Demonstrate the added value of applications relying on the use of the combination of lexica and ontologies. </p> </div> </div> <div class="card card--group" data-component="card" id="ocm"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/ocm/"> Open Cloud Mesh Community Group </a> </h2> <p>This community group is equivalent to the loose "Open Cloud Mesh" collaboration which started at individual vendors such as https://oc.owncloud.com/opencloudmesh.html, then moved to Géant https://wiki.geant.org/display/OCM/Open+Cloud+Mesh and most recently found a home within the CS3 community https://github.com/cs3org/OCM-API</p> <p>As of september 2023, work on OCM is co-funded by NLnet, CERN, and individual implementers.</p> <p>By creating this W3C CG we want to make our ongoing work more visible to the wider web standards community.</p> </div> </div> <div class="card card--group" data-component="card" id="open-ui"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/open-ui/"> Open UI Community Group </a> </h2> <p>The group will be researching components and controls across the web and also looking to native paradigms to bring interoperability for design systems, frameworks and the web platform.</p> </div> </div> <div class="card card--group" data-component="card" id="openactive"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/openactive/"> OpenActive Community Group </a> </h2> <p>This community group is part of <a href="https://www.openactive.io/">the OpenActive initiative</a>. Our goal is to develop technical specifications and best practices that will support the use of open and shared data relating to sports and physical activities.</p> <p>Our primary focus is on standardising how to publish data about opportunities to be physically activity, defining best practices and APIs to enable booking of events and facilities, and improving interoperability of data across the sector.</p> <p>To ensure that our specifications will support a variety of use cases, we welcome contributions from a range of organisations, including existing platforms and new startups.</p> <p>While our work is technical, you don’t have to be a developer to contribute to our standards group. We are looking for input from product and service managers whose domain knowledge can help us to create better outputs.</p> </div> </div> <div class="card card--group" data-component="card" id="opentrack"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/opentrack/"> OpenTrack Community Group </a> </h2> <p>This group aims to develop an open standard for interchange of data in Athletics (including Track and Field), running and related disciplines. Such a standard should allow the development of better software to manage the sport, resulting in major savings of time for volunteers; more efficient management of events and federations; and more enjoyment for participants and fans.</p> </div> </div> <div class="card card--group" data-component="card" id="perma-id"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/perma-id/"> Permanent Identifier Community Group </a> </h2> <p>The Permanent Identifier Community Group maintains a secure, permanent UL re-direction service for the Web located at w3id.org. Web applications that deal with Linked Data often need to specify and use URLs that are very stable. They utilize services such as the one run by this community to ensure that applications using their URLs will always be re-directed to a working website. The concept operates much like a switchboard, connecting requests for information with the true location of the information on the Web. Entries in the switchboard can be reconfigured to point to a new location if the old location stops working.</p> <p>The community is responsible for all administrative tasks associated with operating the service. The social contract between organizations involved in the community gives each of them full access to all information required to maintain and operate the website. The agreement is setup such that a number of these organizations could fail, lose interest, or become unresponsive for long periods of time without negatively affecting the operation of the site. </p> <p> The service operates in HTTPS-only mode to ensure end-to-end security. This means that it may be used for Linked Data applications that require high levels of security such as those found in the financial, medical, and public infrastructure sectors. </p> <p>All identifiers associated with the service are intended to be around for as long as the Web is around. This means decades, if not centuries. If the final destination for popular identifiers used by this service fail in such a way as to be a major inconvenience or danger to the Web, the community will mirror the information for the popular identifier and setup a working redirect to restore service to the rest of the Web. </p> <p>You may join this community by getting a W3C account and clicking the join button. If you wish to engage the community in discussion about this service for your Web application, please send an e-mail to the public-perma-id@w3.org mailing list. </p> <p>This group does not create specifications.</p> </div> </div> <div class="card card--group" data-component="card" id="pwe"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/pwe/"> Positive Work Environment Community Group </a> </h2> <p>W3C is a global community where participants choose to work together. In that community, we experience differences in language, location, nationality, and experience. In such a diverse environment, misunderstandings and disagreements happen, and in most cases can be resolved informally. This CG will pick up the work of the PWE Task Force (https://www.w3.org/Consortium/pwe/) focusing on the Code of Ethics and Professional Conduct.</p> </div> </div> <div class="card card--group" data-component="card" id="privacycg"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/privacycg/"> Privacy Community Group </a> </h2> <p>The mission of the Privacy Community Group is to develop privacy-focused web standards and APIs to improve user privacy on the web through enhanced browser behavior.</p> <p>Charter: <a href="https://privacycg.github.io/charter.html">https://privacycg.github.io/charter.html</a></p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/advertising/"> Web Advertising </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="patcg"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/patcg/"> Private Advertising Technology Community Group </a> </h2> <p>The mission of the Private Advertising Technology Community Group is to incubate web features and APIs that support advertising while acting in the interests of users, in particular providing strong privacy assurances.</p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/advertising/"> Web Advertising </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="publishingcg"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/publishingcg/"> Publishing Community Group </a> </h2> <p>Incubation zone for Publishing@W3C. Bring your experiments here.</p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/publishing/"> Publishing </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="rdfjs"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/rdfjs/"> RDF JavaScript Libraries Community Group </a> </h2> <p>The RDF JavaScript Libraries Community Group discusses implementations of libraries for working with RDF and Linked Data in ECMAScript platforms like Web browsers and Node.js</p> </div> </div> <div class="card card--group" data-component="card" id="r2c2"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/r2c2/"> RDF Rust Common Crates Community Group </a> </h2> <p>The mission of the RDF Rust Common Crates Community Group is to develop common crates for working with RDF in Rust. The goal is to improve the interoperability of the RDF ecosystem in Rust.</p> </div> </div> <div class="card card--group" data-component="card" id="rsp"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/rsp/"> RDF Stream Processing Community Group </a> </h2> <p>The mission of the RDF Stream Processing Community Group (RSP) is to define a common model for producing, transmitting and continuously querying RDF Streams. This includes extensions to both RDF and SPARQL for representing streaming data, as well as their semantics. Moreover this work envisions an ecosystem of streaming and static RDF data sources whose data can be combined through standard models, languages and protocols. Complementary to related work in the area of databases, this Community Group looks at the dynamic properties of graph-based data, i.e., graphs that are produced over time and which may change their shape and data over time. </p> </div> </div> <div class="card card--group" data-component="card" id="rdfsurfaces"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/rdfsurfaces/"> RDF Surfaces Community Group </a> </h2> <p>The RDF Surfaces sets out to create a sublanguage of Notation3 in order to implement classical first-order logic with negation in RDF as envisioned by Pat Hayes in his 2009 ISWC Invited Talk: BLOGIC</p> </div> </div> <div class="card card--group" data-component="card" id="rdf-tests"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/rdf-tests/"> RDF Test Suite Curation Community Group </a> </h2> <p>The purpose of this group is to provide a home for the test suites and implementation reports of various Semantic Web/Linked Data specifications. After the end of a working group, the test suites often become frozen, and it is difficult to add new tests for issues that come to light later on. Similarly, some specs are implemented on a base technology, which eventually evolves (e.g. SPARQL 1.1 and RDF 1.1), and developers need access to updated tests.</p> <p>This group will create a home for forks of the various test suites that would be appropriate to act as a redirect for existing tests. Test updates will be considered based on the consensus of those invested in the related specifications. Implementation reports can be updated as new reports are received, giving implementations visibility.</p> <p>This group will not publish Specifications.</p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/data/"> Data and knowledge </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="rdf-dev"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/rdf-dev/"> RDF-DEV Community Group </a> </h2> <p>RDF-DEV, for developments relating to W3C RDF, including collaboration around applications, schemas, and past/present/future related standards. Successor to SWIG/RDFIG. </p> </div> </div> <div class="card card--group" data-component="card" id="realestate"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/realestate/"> Real Estate Community Group </a> </h2> <p>The mission of the Real Estate Community Group is to provide a forum for real estate-related technical discussions to track progress of technology features on the Web within W3C groups, educate on the use of Web technologies by external organizations, and to identify use cases and requirements that existing and/or new specifications need to meet to deliver a more inclusive, robust experiences to the Real Estate ecosystem. </p> </div> </div> <div class="card card--group" data-component="card" id="md-odrl-profile"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/md-odrl-profile/"> Rights Automation for Market Data Community Group </a> </h2> <p>The aim of the Rights Automation for Market Data Community Group is to develop and publish a market-data profile for ODRL.</p> <p>Market data is mostly the pricing and trading data for financial instruments (and their associated indices) generated by trading venues. The licenses controlling its use are frequently complex, and tightly segment the underlying data.</p> <p>We will model these licenses using ODRL and extend the language with a profile that defines the new terms required. This group will publish Specifications.</p> <p>With a standard, machine-readable way of describing market data licenses, we can look towards automating rights-management along the market data supply chain and drive efficiencies in financial markets.</p> <p>The group welcomes the involvement of domain experts in licensing (especially market data) and those skilled in modeling licenses (especially using ODRL). </p> <p>If you are not a group participant you can still <a href="mailto:public-md-odrl-profile-request@w3.org?Subject=Subscribe">subscribe to our list</a>.</p> </div> </div> <div class="card card--group" data-component="card" id="rumcg"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/rumcg/"> RUM Community Group </a> </h2> <p>The mission of the RUM Community Group is to improve and expand the capabilities of developers and businesses who are using Real User Monitoring (RUM) to measure user experience on the web.</p> <p>We are focused on the measurement of performance, errors, logs, tracing, activity, and any other facet that indicates user experience.</p> <p>Our deliverables would include: Collaborative research projects (sharing the experimental results and any findings), and generating documents for external consumption (principles, opinions, positions, recommendations to Working Groups and others).</p> </div> </div> <div class="card card--group" data-component="card" id="architypes"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/architypes/"> Schema Architypes Community Group </a> </h2> <p>The mission of this group is to discuss and prepare proposal(s) for extending Schema.org schema for the improved representation of digital and physical archives and their contents. </p> <p>The goal being focused upon the creation and future maintenance of an archive.schema.org extension.</p> </div> </div> <div class="card card--group" data-component="card" id="schemabibex"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/schemabibex/"> Schema Bib Extend Community Group </a> </h2> <p>The mission of this group is to discuss and prepare proposal(s) for extending Schema.org schemas for the improved representation of bibliographic information markup and sharing. The group will seek consensus around, and support for, proposal(s) to the W3C WebSchemas Group. This Community Group will not, itself, produce technical specifications.</p> </div> </div> <div class="card card--group" data-component="card" id="schema-course-extend"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/schema-course-extend/"> Schema Course extension Community Group </a> </h2> <p>This mission of this group, initiated by LRMI, is to develop an extension for schema.org concerning the discovery of any type of educational course (online/offline, long/short, scheduled/on-demand). Educational course is defined as "some sequence of events and/or creative works which aims to build the knowledge, competence or ability of learners". (Out of scope: information about students and their progression etc; information needed internally for course management rather than discovery).</p> </div> </div> <div class="card card--group" data-component="card" id="iotschema"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/iotschema/"> Schema Extensions for IoT Community Group </a> </h2> <p>This Community Group is for creating extensions to Schema.org for IoT use cases. We have been holding regular community teleconferences since 2017 and now would like to formalize our work and accept contributions from the community. </p> <p>A W3C CG is the logical next step in our organization, as we already work with other W3C CG, IG, and WG entities.</p> <p>Our original charter is at: https://github.com/iot-schema-collab/ws-charter/blob/master/iotschema-charter.txt</p> <p>A revised charter for the CG is at: https://github.com/iot-schema-collab/intro-materials/blob/master/wg-charter.md</p> </div> </div> <div class="card card--group" data-component="card" id="schemaorg"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/schemaorg/"> Schema.org Community Group </a> </h2> <p>The Schema.org Community Group provides a forum for discussing all changes, additions and extensions to <a href="http://schema.org/">schema.org</a>. In addition to providing a public setting for the day to day operation of the project, it serves as the mechanism for reviewing <a href="http://schema.org/docs/extension.html">extensions</a> and as a liaison point for all parties developing independent extensions to the schema.org core.</p> </div> </div> <div class="card card--group" data-component="card" id="schemaorg4datasets"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/schemaorg4datasets/"> Schema.org for datasets Community Group </a> </h2> <p>Focussed on improving interoperability between schema.org's DCAT-based approach to dataset description and related approaches e.g. CSVW, VoID, Data Cube, R2RML, SpatialWeb, DCAT-AP and others including liaison to any new W3C work.</p> </div> </div> <div class="card card--group" data-component="card" id="sccg"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/sccg/"> Screen Capture Community Group </a> </h2> <h2>Background</h2> <p>Screen capture is useful in many contexts, such as when delivering presentations, collaborating with remote colleagues, or producing local recordings. The Web Platform offers APIs to that end, allowing Web applications to capture screens, windows or tabs, and allowing the captured media to be manipulated in various productive ways.</p> <p>The popularity of these APIs, and the ubiquity of the applications that use them, are a testament to the importance of the work that has been done thus far.</p> <h2>Mission</h2> <p>We believe that there is yet more untapped potential in the realm of screen capture. It is our mission to innovate further and unblock additional novel uses of screen capture, creating new business opportunities for developers and enriching the lives of users.</p> <h2>Scope</h2> <p>As part of this charter, the Screen capture Community Group is focusing its activities on producing new screen capture APIs and extending existing ones. APIs directly involving screen capture are in scope, as are APIs that would typically be used in tandem with screen capture.</p> <h2>Work mode</h2> <p>The group will conduct all of its technical work in public, on GitHub repositories, with a supporting mailing list for logistical and administrative purposes.</p> <p>Meetings will normally be public and open to anyone to join. Should the need arise, meetings may be restricted to Community Group participants and guests invited by the group chairs. In either case, a public summary or minutes will be made available publicly.</p> <h2>Amendments to this charter</h2> <p>The group chairs can amend the charter.</p> </div> </div> <div class="card card--group" data-component="card" id="webscreens"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/webscreens/"> Second Screen Community Group </a> </h2> <p>The mission of the <a href="https://www.w3.org/community/webscreens/">Second Screen Community Group (CG)</a> is to explore, incubate, and define interfaces that enable new form factors and usages for multi-display and multi-window computing user experiences on the Web.</p> <p>The scope of work for this Community Group extends beyond the current scope of the <a href="https://www.w3.org/2014/secondscreen/">Second Screen Working Group (WG)</a>. Given wider support and adequate stability, we plan to migrate the proposals generated in this Community Group to an appropriate <a href="https://www.w3.org/Consortium/activities#Working">W3C Working Group</a> for further contributions and formal standardization.</p> </div> </div> <div class="card card--group" data-component="card" id="swag"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/swag/"> Security Web Application Guidelines Community Group </a> </h2> <p>The mission of this Community Group is to increase the overall security of web application development, thereby making the web a more secure platform for web users. It will accomplish this by writing web developers security best practices and providing a platform for stakeholder collaboration.</p> <p>This group will not publish Specifications.</p> </div> </div> <div class="card card--group" data-component="card" id="htmlvoc"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/htmlvoc/"> Semantic HTML-vocabulary Community Group </a> </h2> <p>The mission of this community group is to establish a draft standard for a RDF-based representation of the HTML-vocabulary. With the HTML-vocabulary in RDF, any type of an HTML-document can be meaningfully represented, generated and validated using nothing but standard semantic technologies, without any vendor lock-in. In addition, full provenance can be provided for a generated HTML-document, as every atom of the document can be described and semantically enriched, ex ante (RDF) and ex post (Rdfa). For instance, the originating algorithm that calculates a certain budget amount in a governmental HTML-document can be linked to the table cell containing the very value. HTML-documents have a wide variety of use and so has the HTML vocabulary. The HTML-vocabulary can be used to generate 100% correct HTML or xHTML and to validate this. The HTML vocabulary can be used to model the front end of a website or application, whereas the logic behind the front end can be captured in SHACL Advanced Features, making for a full semantic representation and execution of digital infrastructure, without any vendor lock-in. An HTML-document can be generated with full compliance to laws and regulations, as these norms can be linked and applied while using the HTML-vocabulary. With full provenance, an HTML-document can battle fake news and show realtime how certain sensitive data in the document (privacy, security) was derived.</p> <p>The community group will come up with a 0.1 draft specification. This will be input for a future working group within W3C. The community group can make use of the currently available draft specification as developed by the Dutch Ministry of Finance in a working prototype for the Dutch governmental budget cycle. By starting this community group, the Dutch Ministry wants to contribute to an open source based digital infrastructure.</p> </div> </div> <div class="card card--group" data-component="card" id="shacl"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/shacl/"> SHACL Community Group </a> </h2> <p>The mission of the SHACL Community Group is to continue the development of SHACL-related specifications and to support the further adoption of SHACL after the <a href="https://www.w3.org/2014/data-shapes/">W3C Data Shapes Working Group</a> has ended. Desirable outcomes include the development of educational material (primers, best practices), the application of SHACL to frequently used RDF vocabularies, libraries of constraint components for common constraint types, improved integration with established technologies such as JavaScript, further work on theory and practice around SHACL rules, a compact SHACL syntax, and a SHACL internet protocol. Additional work may go into delivering "de-facto standard" fixes to some gaps left in the current SHACL specifications (e.g., handling recursion, and addressing more comprehensive syntax checks). </p> </div> </div> <div class="card card--group" data-component="card" id="shex"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/shex/"> Shape Expressions Community Group </a> </h2> <p>This group serves to promote and expand ShEx – Shape Expressions. ShEx is a grammar for RDF graphs which can be used for description, validation, parsing and transformation.</p> <p>The Shape Expressions (ShEx) language describes RDF nodes and graph structures. A node constraint describes an RDF node (IRI, blank node or literal) and a shape describes the triples touching nodes in RDF graphs. These descriptions identify predicates and their associated cardinalities and datatypes. ShEx shapes can be used to communicate data structures associated with some process or interface, generate or validate data, or drive user interfaces.</p> <p>Spec at https://shexspec.github.io/spec/</p> </div> </div> <div class="card card--group" data-component="card" id="silver"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/silver/"> Silver Community Group </a> </h2> <p>Support the research and prototyping of the next major version of Web Content Accessibility Guidelines (WCAG).</p> <p>This group may publish Specifications.</p> </div> </div> <div class="card card--group" data-component="card" id="socialcg"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/socialcg/"> Social Web Incubator Community Group </a> </h2> <p>The Social Web Incubator Community Group (also known as SocialCG, or SWICG) is the successor of the Social Web Working Group, which ran from 2014 to 2017. The SocialCG provides space to collaborate and coordinate for implementors who are building on any of the <a href="https://www.w3.org/TR/social-web-protocols/">specifications published by the Social Web WG</a>, and related technologies. It is also a place to incubate new proposals which build on or complement the Social Web WG recommendations.<br /><br /></p> <p>Discussions and meeting announcements happen on <a href="https://socialhub.activitypub.rocks/">the SocialHub forum</a> or on project-specific version control repositories.<br /><br /></p> <p>Meetings are not always weekly, but can be requested or convened by any member of the group. If you have a specific item to discuss, please contact a chair if you need help with <a href="https://www.w3.org/wiki/SocialCG#Meetings">meeting logistics</a>, and make a post on the SocialHub forum, ideally with two or more weeks notice.</p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/data/"> Data and knowledge </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="solid"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/solid/"> Solid Community Group </a> </h2> <p>The aims of the <a href="https://solidproject.org/">Solid project</a> are in line with those of the Web itself: empowerment towards an equitable, informed and interconnected society. Solid adds to existing Web standards to realise a space where individuals can maintain their autonomy, control their data and privacy, and choose applications and services to fulfil their needs.</p> <p>The mission of the Solid Community Group is to describe the interoperability between different classes of products by using Web communication protocols, global identifiers, authentication and authorization mechanisms, data formats and shapes, notifications, and query interfaces.</p> <p>To contribute towards a net positive social benefit, we use the <a href="https://www.w3.org/TR/ethical-web-principles/">Ethical Web Principles</a> to orient ourselves. The consensus on the technical designs are informed by common use cases, implementation experience, and use.</p> <p><a href="https://solidproject.org/TR/">Solid Technical Reports</a> lists Work Items, information on how to Participate, and the Solid of Code of Conduct (in addition to the <a href="https://www.w3.org/Consortium/cepc/">Positive Work Environment at W3C: Code of Ethics and Professional Conduct</a>.)</p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/data/"> Data and knowledge </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="sparql-dev"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/sparql-dev/"> SPARQL-dev Community Group </a> </h2> <p>The SPARQL-dev Community Group is a forum for discussion and refinement of SPARQL. It will document features found as extensions to available triple stores and also document common needs from the user community. The CG aims to create consensus and understanding of the impact of new features with special emphasis on features that leave existing SPARQL queries and systems unchanged. The CG will build a collection of such features leading to a CG report on use cases and requirements.</p> </div> </div> <div class="card card--group" data-component="card" id="speced-cg"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/speced-cg/"> Spec Editors Community Group </a> </h2> <p>The Spec Editors Community Group aims to be an inclusive space where spec editors, and those wanting to become spec editors, can learn from each other.</p> <p>The Spec Ed CG focuses on the practice (the art?) of writing technical specifications across the Web ecosystem (W3C, WHATWG, ECMA, IETF, etc.). By looking across the ecosystem, we hope to improve our specification development practices at the W3C. </p> <p>As part of this CG, we hope to run hands-on virtual tutorial sessions that will cover: </p> <ul> <li>spec writing: writing algorithms, types of statements. </li><li>tooling: ReSpec and Bikeshed. </li><li>testing: Web Platform Tests. </li><li>How review specs: what to look for, commenting on pull requests. </li><li>leveraging fundamental technologies: WebIDL, Infra standard, HTML, etc. </li><li>Using GitHub effectively for spec development: labels, milestones, managing your community. </li><li>More things! Let us know... </li></ul> </div> </div> <div class="card card--group" data-component="card" id="sport-schema"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/sport-schema/"> Sport Schema Community Group </a> </h2> <p>The purpose of this group is to propose an expanded vocabulary for describing sporting information within schema.org. The goal is to create a proposal which will build on the existing vocabulary within schema.org updating or adding only where needed. The group should leverage existing work in the area of sport vocabularies, thinking globally with a focus on supporting the 'head' of sports vocabularies while keeping in mind the 'body' and 'tail'.</p> </div> </div> <div class="card card--group" data-component="card" id="sustainability"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/sustainability/"> Sustainability Community Group </a> </h2> <p>The Sustainability CG is a group for discussing all aspects of sustainability (s12y) with respect to web technologies present & future, including developing horizontal reviews of sustainability (e.g. energy use or device obsolescence impacts of technologies).</p> </div> </div> <div class="card card--group" data-component="card" id="sustyweb"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/sustyweb/"> Sustainable Web Design Community Group </a> </h2> <p>A community group dedicated to creating sustainable websites.</p> </div> </div> <div class="card card--group" data-component="card" id="sync-media-pub"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/sync-media-pub/"> Synchronized Multimedia for Publications Community Group </a> </h2> <p>This community group's goal is to propose a way to synchronize audio or video with Web Publications and other document formats being developed by the Publishing Working Group, in order to make the publications accessible to people with different types of reading requirements. The CG may recommend the best way to integrate an existing technology, or it may provide an outline for developing a new format.</p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/publishing/"> Publishing </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="talent-signal"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/talent-signal/"> Talent Marketplace Signaling Community Group </a> </h2> <p>Much is said about the mismatch between the needs of employers for qualified employee candidates and a pool of available candidates. One major factor contributing to this mismatch is the signaling between the demand-side (i.e., employers) and supply-side (i.e., education, training and credentialing providers, students and workers) of the talent pipeline. This mismatch frequently results in neither party coming into view of the other. The goal of the Talent Marketplace Signaling (TalentSignal) Community Group is to assist Schema.org in improving workforce signaling by refining existing schema.org types serving the talent pipeline and suggesting new types and properties where improved signaling cannot otherwise be achieved. Currently, workforce signaling sits at the intersection of a number of existing schema.org types: Course, JobPosting, Occupation, Organization, Person and the proposed EducationalOccupationalCredential.</p> <p>The TalentSignal Community Group will focus initially on refinement of the <a href="https://schema.org/JobPosting">JobPosting Schema</a> and related types as it survey's specifications from domain entities such as <a href="https://hropenstandards.org/">HR Open Standards</a> and <a href="http://www.pesc.org/home.html">PESC</a> as well as the US Chamber of Commerce Foundation's <a href="https://www.uschamberfoundation.org/workforce-development/JDX">Job Data Exchange (JDX)</a> and <a href="https://www.uschamberfoundation.org/t3-innovation">T3 Innovation Network</a> initiatives for better means to strong, more effective supply- and demand-side signaling.</p> </div> </div> <div class="card card--group" data-component="card" id="tdmrep"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/tdmrep/"> Text and Data Mining Reservation Protocol Community Group </a> </h2> <p>The goal of this Group is to facilitate Text and Data Mining (TDM) Reservation Protocol in Europe and elsewhere, by specifying a simple and practical machine-readable solution, capable of expressing the reservation of TDM rights - following the rules set by the new European DSM Directive / Art.4 - and the availability of machine-readable licenses for TDM actors. </p> </div> </div> <div class="card card--group" data-component="card" id="tourismdata"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/tourismdata/"> The Tourism Structured Web Data Community Group </a> </h2> <p>The mission of this group is to discuss and prepare proposals, examples, and best practice guidance for the sharing, via the web, structured data descriptions of resources associated with the tourism industry.</p> <p>Initial focus will be on extending Schema.org schemas for the improved representation of tourism related information markup and sharing. The group will seek consensus around, and support for, proposal(s) to be made to the Schema.org community. </p> </div> </div> <div class="card card--group" data-component="card" id="tmcg"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/tmcg/"> Threat Modeling Community Group </a> </h2> <p>The group's purpose is to provide a meeting point for Security, Privacy, and Human Rights experts, along with technology domain experts, to create Threat Models together.</p> <p>This group will not publish Specifications.</p> </div> </div> <div class="card card--group" data-component="card" id="treecg"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/treecg/"> TREE hypermedia Community Group </a> </h2> <p>The TREE hypermedia community group will discuss materializable hypermedia interfaces. Its goals are to: 1. Further evolve the TREE hypermedia specification (https://w3id.org/tree/specification) and its vocabulary (https://w3id.org/tree/) 2. Create a test suite for spec compliance of both servers and clients 3. Deliver a specification on view definitions for source selection</p> </div> </div> <div class="card card--group" data-component="card" id="unhosted"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/unhosted/"> Unhosted Web Community Group </a> </h2> <p>We propose per-user cross-origin cloud storage, much in the sense described in http://www.w3.org/DesignIssues/CloudStorage.html We are a non-profit project and have so far defined a first draft of our standard for this: http://unhosted.org/spec/dav/0.1 We have researched a lot of aspects in the last few months, and are about move to version 0.2 of our standard. People are starting to implement this with significant user base sizes, and other people are starting to develop apps that rely on it, which is now would be a good time to make this into a w3c cg.</p> </div> </div> <div class="card card--group" data-component="card" id="robotstxt"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/robotstxt/"> Update robots.txt standards Community Group </a> </h2> <p>Robots.txt is currently based on opting out of what you do not want your website to be a part of. </p> <p>This is hard to maintain (almost a full time job right now) if you do not wish for your websites content to be applied for e.g. training AI, be a part of market research (e.g. price robots), to be a part of non-search engine databases and more.</p> <p>This proposal is to update what type of instructions robots.txt should support to rather be treated as an opt-in, where you can give instructions based on intent of robots rather than a wildcard or in granular detail.</p> <p>Example: Agent-group: searchengines</p> <p>Applies to all robots that seeks to update, process or maintain websites for search engine databases. Does not grant permission to apply scraped data for AI purposes (this should have its own Agent-group).</p> <p>Also, the absence of instructions should be treated as not having opted in, and for robots working on behalf of AI, there might need to be additional instructions (e.g. max-snippet and if you require a citation if your content is applied to provide an answer).</p> </div> </div> <div class="card card--group" data-component="card" id="voiceinteraction"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/voiceinteraction/"> Voice Interaction Community Group </a> </h2> <p>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. </p> <p>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.</p> </div> </div> <div class="card card--group" data-component="card" id="w3process"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/w3process/"> W3C Process Community Group </a> </h2> <p>Examine the way W3C works. Propose improvements to the formal processes. These will be given to the Advisory Board, which currently manages that process.</p> </div> </div> <div class="card card--group" data-component="card" id="web-bluetooth"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/web-bluetooth/"> Web Bluetooth Community Group </a> </h2> <p>Bluetooth is a standard for short-range wireless communication between devices. This group is developing a <a href="https://webbluetoothcg.github.io/web-bluetooth/">specification for Bluetooth APIs</a> to allow websites to communicate with devices in a secure and privacy-preserving way. In particular the web Bluetooth API focuses on minimizing the device attack surface exposed to malicious websites, possibly by removing access to some existing Bluetooth features that are hard to implement securely. Further, the API takes the approach of a user interface to select and approve access to devices as opposed to using certification and installation.</p> <p>Most of our activity happens in our <a href="https://github.com/WebBluetoothCG/web-bluetooth">GitHub repository</a>, with supporting code in adjacent repositories in the <a href="https://github.com/WebBluetoothCG">WebBluetoothCG GitHub organization</a>.</p> </div> </div> <div class="card card--group" data-component="card" id="webcomponents"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/webcomponents/"> Web Components Community Group </a> </h2> <p>This group is for collaboration between people working on web components libraries, tools, documentation and standards.</p> <p>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.</p> <p>Areas we expect to work on include gap analysis, design principles, common protocols, discoverability and quality, documentation, tooling, and more. </p> </div> </div> <div class="card card--group" data-component="card" id="webhistory"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/webhistory/"> Web History Community Group </a> </h2> <p>This group gathers people interested in the history of the World Wide Web: how it was invented, what was out there that made it possible, and what happened in its early years. Our main goal is to collect and preserve valuable information (software, documents, testimonials) before it is lost. </p> <p>This group will not produce specifications.</p> </div> </div> <div class="card card--group" data-component="card" id="webmachinelearning"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/webmachinelearning/"> Web Machine Learning Community Group </a> </h2> <p>The mission of the Web Machine Learning Community Group (WebML CG) is to make Machine Learning a first-class web citizen by incubating and developing a dedicated low-level Web API for machine learning inference in the browser. Please see the <a href="https://webmachinelearning.github.io/charter/">charter</a> for more information.</p> <p>The group invites browser engine developers, hardware vendors, web application developers, and the broader web community with interest in Machine Learning to participate.</p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/data/"> Data and knowledge </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="webmediaapi"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/webmediaapi/"> Web Media API Community Group </a> </h2> <p>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.</p> <p>See the <a href="https://www.w3.org/2016/09/webmediaapi-cg-charter.html">CG charter</a> for more information.</p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/media/"> Media & Entertainment </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="texttracks"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/texttracks/"> Web Media Text Tracks Community Group </a> </h2> <p>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:</p> <p>1) Documenting a semantic model underlying the caption formats in use, notably TTML, CEA 608/708, EBU STL, and WebVTT.</p> <p>2) Creating a community specification for WebVTT.</p> <p>3) Defining the mappings between WebVTT and some selected formats, including at least TTML (W3C/SMPTE), and CEA 608/708.</p> <p>4) Creating web developer reference and tutorial material, including worked examples.</p> <p>5) Creating a test suite and/or tools.</p> <p>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.</p> <p>The group may produce recommendations for work in other groups, such as CSS, HTML5, and TTWG.</p> </div> </div> <div class="card card--group" data-component="card" id="web-nfc"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/web-nfc/"> Web NFC Community Group </a> </h2> <p>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 <a href="https://w3c.github.io/web-nfc/charter/">Web NFC Community Group Charter</a> and the <a href="https://w3c.github.io/web-nfc/">Web NFC specification</a> for more information.</p> </div> </div> <div class="card card--group" data-component="card" id="wot"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/wot/"> Web of Things Community Group </a> </h2> <p>The goal of Web of Things Community Group is to accelerate the community activities around the recommendations and notes published by the WoT Working Group and Interest Group. This group does not publish Specifications.</p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/web-of-things/"> Web of Things </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="wot-jp"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/wot-jp/"> Web of Things Japanese Community Group </a> </h2> <p>The mission of the Web of Things Japanese Community Group includes the following:</p> <ul> <li>to facilitate focused discussion in Japanese on the Web of Things specifications and related specifications</li> <li>to gather comments and questions in Japanese about those specifications </li> <li>to collect information about specific use cases in Japanese for technologies defined in those specifications</li> <li> to report the results of its activities as a group back to the Web of Things Working Group/Interest Group, the W3C membership and the Web community.</li> </ul> <p>This group will not publish any specifications.</p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/web-of-things/"> Web of Things </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="wicg"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/wicg/"> Web Platform Incubator Community Group </a> </h2> <p>The Web Platform Incubator Community Group (WICG) provides a lightweight venue for proposing and discussing new web platform features. Please see the <a href="http://wicg.github.io/admin/charter.html">charter</a> for more information.</p> </div> </div> <div class="card card--group" data-component="card" id="web-thing-protocol"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/web-thing-protocol/"> Web Thing Protocol Community Group </a> </h2> <p>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 <a href="https://www.w3.org/WoT/">Web of Things</a>.</p> <p>Deliverables of the group may include use cases, requirements and specifications.</p> <p>The group will collaborate with the W3C Web of Things Interest Group and Working Group to ensure any specifications complement or extend the “<a href="https://www.w3.org/TR/wot-thing-description">Web of Things (WoT) Thing Description</a>” specification.</p> <p>Objectives: </p> <ol> <li>Define a WebSocket sub-protocol for the Web of Things, using the W3C “Web of Things (WoT) Thing Description” data model and operations</li> <li>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)</li> <li>Evaluate other potential Web of Things protocol bindings (e.g. CoAP)</li> </ol> <p>See the proposed <a href="https://benfrancis.github.io/web-thing-protocol-charter/">Community Group Charter</a> for more information.</p> <dl class="txt-pluto"> <dt class="visuallyhidden"> Ecosystem </dt> <dd> <a href="/ecosystems/web-of-things/"> Web of Things </a> </dd> </dl> </div> </div> <div class="card card--group" data-component="card" id="wintercg"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/wintercg/"> Web-interoperable Runtimes Community Group </a> </h2> <p>The Web-interoperable Runtimes Community Group (wintercg) is intended to augment the work of other existing community and working groups focusing on the development of Web Platform features and APIs by focusing directly on the specific needs of non-Web Browser based implementations. Whereas existing community groups such as the Web Incubator Community Group (WICG) and the Web Hypertext Application Technology Working Group (WHATWG) are each explicitly scoped to features "that would be implemented in a browser or similar user agent", it will be the goal of the wintercg to focus on implementation of those same features in environments such as backend servers, serverless compute, IoT, command-line tools, and so forth -- essentially, everything that is not a browser.</p> </div> </div> <div class="card card--group" data-component="card" id="webassembly"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/webassembly/"> WebAssembly Community Group </a> </h2> <p>The mission of this group is to promote early-stage cross-browser collaboration on a new, portable, size- and load-time-efficient format suitable for compilation to the web.</p> </div> </div> <div class="card card--group" data-component="card" id="webauthn-adoption"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/webauthn-adoption/"> WebAuthn Adoption Community Group </a> </h2> <p>This group helps coordinate research and actions to help with broader adoption of the Web Authentication ecosystem.</p> <p>Group participants will contribute to identifying the obstacles that slow down adoption of WebAuthn - these obstacles may be e.g. technical, business-related, linked to communication or training.</p> <p>Based on this analysis, the group participants will work together in addressing these challenges.</p> <p>This group will not produce specifications.</p> </div> </div> <div class="card card--group" data-component="card" id="webdx"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/webdx/"> WebDX Community Group </a> </h2> <p>The mission of the Web Developer Experience (WebDX) Community Group is to facilitate coordinated approaches to improve the overall experience of developing for the Web platform when such coordination provides unique opportunities for these improvements. Coordinated work includes research on developer needs to inform improvements in Web platform developers experience, and explorations of Web platform features adoptability. See the <a href="https://github.com/web-platform-dx/admin/blob/main/charter.md">group's charter</a>.</p> </div> </div> <div class="card card--group" data-component="card" id="webextensions"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/webextensions/"> WebExtensions Community Group </a> </h2> <p>We will specify a model, permissions, and a common core of APIs for web browser extensions. By specifying the APIs, functionality, and permissions of WebExtensions, we can make it even easier for extension developers to enhance end user experience, while moving them towards APIs that improve performance and prevent abuse.</p> <p>Charter: https://github.com/w3c/webextensions/blob/main/charter.md</p> </div> </div> <div class="card card--group" data-component="card" id="webtoon-meta"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/webtoon-meta/"> Webtoon Metadata Community Group </a> </h2> <p>The mission of this group is to share use cases, technical challenges, best practices, and possible implementations for the interoperability of webtoon metadata in order to improve the interoperability of webtoon metadata and enable diverse uses of derivative works.</p> </div> </div> <div class="card card--group" data-component="card" id="webview"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/webview/"> WebView Community Group </a> </h2> <p>The WebViews Community Group aims to identify, understand and reduce the issues arising from the use of software components (typically referred as WebViews) that are used to render Web technology-based content outside of a Web browser (Native Apps, MiniApps, etc). See the <a href="https://github.com/WebView-CG/charter/blob/main/charter.md">proposed charter</a> that scopes its first expected phase of work.</p> </div> </div> <div class="card card--group" data-component="card" id="xformsusers"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/xformsusers/"> XForms Users Community Group </a> </h2> <p>A group for XForms users to discuss the use of XForms and propose changes and additions to the markup.</p> </div> </div> <div class="card card--group" data-component="card" id="xproc-next"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/xproc-next/"> XProc Next Community Group </a> </h2> <p>Create a place for gathering requirements from existing and potential users of XProc, research in this area, and for supporting and writing the community-driven effort to define an XProc 3.0 specification (formerly 1.1) .</p> </div> </div> <div class="card card--group" data-component="card" id="xslt-40"> <div class="card__text"> <h2 class="card__heading"> <a class="card__link" href="/groups/cg/xslt-40/"> XQuery and XSLT Extensions Community Group </a> </h2> <p>The group aims to agree extensions to the XSLT 3.0 Recommendation published on 8 June 2017, along with supporting changes to the other specifications (XPath, Functions and Operators) on which it depends. </p> <p>A preliminary proposal describing requirements for such extensions can be found in Michael Kay's Proposal for XSLT 4.0 published in the <a href="https://archive.xmlprague.cz/2020/files/xmlprague-2020-proceedings.pdf#page=121">Proceedings of XML Prague 2020</a></p> <p>It is intended that the group will operate primarily by use of email and forums but may hold a face-to-face meeting to resolve issues prior to final publication of a specification.</p> <p>The group may publish specifications.</p> </div> </div> </div> </div> </div> <section class="rss"> <h2 class="txt-jupiter">API</h2> <p class="with-icon--before with-icon--larger"> <svg class="icon icon--larger" width="30" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 640 512">  <path d="M512.1 191l-8.2 14.3c-3 5.3-9.4 7.5-15.1 5.4-11.8-4.4-22.6-10.7-32.1-18.6-4.6-3.8-5.8-10.5-2.8-15.7l8.2-14.3c-6.9-8-12.3-17.3-15.9-27.4h-16.5c-6 0-11.2-4.3-12.2-10.3-2-12-2.1-24.6 0-37.1 1-6 6.2-10.4 12.2-10.4h16.5c3.6-10.1 9-19.4 15.9-27.4l-8.2-14.3c-3-5.2-1.9-11.9 2.8-15.7 9.5-7.9 20.4-14.2 32.1-18.6 5.7-2.1 12.1.1 15.1 5.4l8.2 14.3c10.5-1.9 21.2-1.9 31.7 0L552 6.3c3-5.3 9.4-7.5 15.1-5.4 11.8 4.4 22.6 10.7 32.1 18.6 4.6 3.8 5.8 10.5 2.8 15.7l-8.2 14.3c6.9 8 12.3 17.3 15.9 27.4h16.5c6 0 11.2 4.3 12.2 10.3 2 12 2.1 24.6 0 37.1-1 6-6.2 10.4-12.2 10.4h-16.5c-3.6 10.1-9 19.4-15.9 27.4l8.2 14.3c3 5.2 1.9 11.9-2.8 15.7-9.5 7.9-20.4 14.2-32.1 18.6-5.7 2.1-12.1-.1-15.1-5.4l-8.2-14.3c-10.4 1.9-21.2 1.9-31.7 0zm-10.5-58.8c38.5 29.6 82.4-14.3 52.8-52.8-38.5-29.7-82.4 14.3-52.8 52.8zM386.3 286.1l33.7 16.8c10.1 5.8 14.5 18.1 10.5 29.1-8.9 24.2-26.4 46.4-42.6 65.8-7.4 8.9-20.2 11.1-30.3 5.3l-29.1-16.8c-16 13.7-34.6 24.6-54.9 31.7v33.6c0 11.6-8.3 21.6-19.7 23.6-24.6 4.2-50.4 4.4-75.9 0-11.5-2-20-11.9-20-23.6V418c-20.3-7.2-38.9-18-54.9-31.7L74 403c-10 5.8-22.9 3.6-30.3-5.3-16.2-19.4-33.3-41.6-42.2-65.7-4-10.9.4-23.2 10.5-29.1l33.3-16.8c-3.9-20.9-3.9-42.4 0-63.4L12 205.8c-10.1-5.8-14.6-18.1-10.5-29 8.9-24.2 26-46.4 42.2-65.8 7.4-8.9 20.2-11.1 30.3-5.3l29.1 16.8c16-13.7 34.6-24.6 54.9-31.7V57.1c0-11.5 8.2-21.5 19.6-23.5 24.6-4.2 50.5-4.4 76-.1 11.5 2 20 11.9 20 23.6v33.6c20.3 7.2 38.9 18 54.9 31.7l29.1-16.8c10-5.8 22.9-3.6 30.3 5.3 16.2 19.4 33.2 41.6 42.1 65.8 4 10.9.1 23.2-10 29.1l-33.7 16.8c3.9 21 3.9 42.5 0 63.5zm-117.6 21.1c59.2-77-28.7-164.9-105.7-105.7-59.2 77 28.7 164.9 105.7 105.7zm243.4 182.7l-8.2 14.3c-3 5.3-9.4 7.5-15.1 5.4-11.8-4.4-22.6-10.7-32.1-18.6-4.6-3.8-5.8-10.5-2.8-15.7l8.2-14.3c-6.9-8-12.3-17.3-15.9-27.4h-16.5c-6 0-11.2-4.3-12.2-10.3-2-12-2.1-24.6 0-37.1 1-6 6.2-10.4 12.2-10.4h16.5c3.6-10.1 9-19.4 15.9-27.4l-8.2-14.3c-3-5.2-1.9-11.9 2.8-15.7 9.5-7.9 20.4-14.2 32.1-18.6 5.7-2.1 12.1.1 15.1 5.4l8.2 14.3c10.5-1.9 21.2-1.9 31.7 0l8.2-14.3c3-5.3 9.4-7.5 15.1-5.4 11.8 4.4 22.6 10.7 32.1 18.6 4.6 3.8 5.8 10.5 2.8 15.7l-8.2 14.3c6.9 8 12.3 17.3 15.9 27.4h16.5c6 0 11.2 4.3 12.2 10.3 2 12 2.1 24.6 0 37.1-1 6-6.2 10.4-12.2 10.4h-16.5c-3.6 10.1-9 19.4-15.9 27.4l8.2 14.3c3 5.2 1.9 11.9-2.8 15.7-9.5 7.9-20.4 14.2-32.1 18.6-5.7 2.1-12.1-.1-15.1-5.4l-8.2-14.3c-10.4 1.9-21.2 1.9-31.7 0zM501.6 431c38.5 29.6 82.4-14.3 52.8-52.8-38.5-29.6-82.4 14.3-52.8 52.8z"/> </svg> Data available in <a href="/api/">API</a> </p> </section> </main> </div> <footer class="global-footer"> <div class="l-center"> <div class="global-footer__links"> <div class="l-cluster"> <ul class="clean-list" role="list"> <li> <a href="https://www.w3.org/" hreflang="en"> <span lang="en" dir="ltr">Home</span> </a> </li> <li> <a href="https://www.w3.org/contact/" hreflang="en"> <span lang="en" dir="ltr">Contact</span> </a> </li> <li> <a href="https://www.w3.org/help/" hreflang="en"> <span lang="en" dir="ltr">Help</span> </a> </li> <li> <a href="https://www.w3.org/donate/" hreflang="en"> <span lang="en" dir="ltr">Donate</span> </a> </li> <li> <a href="https://www.w3.org/policies/" hreflang="en"> <span lang="en" dir="ltr">Legal & Policies</span> </a> </li> <li> <a href="https://www.w3.org/about/corporation/" hreflang="en"> <span lang="en" dir="ltr">Corporation</span> </a> </li> <li> <a href="https://status.w3.org/" hreflang="en"> <span lang="en" dir="ltr">System Status</span> </a> </li> </ul> </div> <ul class="clean-list" role="list"> <li><a class="with-icon--larger" href="https://w3c.social/@w3c" hreflang="en"> <img class="icon icon--larger" src="/assets/website-2021/svg/mastodon.svg" width="20" height="20" alt aria-hidden="true" loading="lazy"/> <span class="visuallyhidden"><span lang="en" dir="ltr">W3C on Mastodon</span></span></a> </li> <li><a class="with-icon--larger" href="https://github.com/w3c/" hreflang="en"> <img class="icon icon--larger" src="/assets/website-2021/svg/github.svg" width="20" height="20" alt aria-hidden="true" loading="lazy"/> <span class="visuallyhidden"><span lang="en" dir="ltr">W3C on GitHub</span></span></a> </li> </ul> </div> <p class="copyright"><span lang="en" dir="ltr">Copyright © 2024 <a href="https://www.w3.org/">World Wide Web Consortium</a>.<br> <abbr title="World Wide Web Consortium">W3C</abbr><sup>®</sup> <a href="https://www.w3.org/policies/#disclaimers">liability</a>, <a href="https://www.w3.org/policies/#trademarks">trademark</a> and <a rel="license" href="https://www.w3.org/copyright/document-license/" title="W3C Document License">permissive license</a> rules apply.</span></p> </div> </footer> </div> </body> </html>

CINXE.COM

Community Groups | Discover W3C groups | W3C