# _links.groups[].title
Accessibility at the Edge Community Group

# _links.groups[].title
Accessibility Conformance Testing (ACT) Task Force

# _links.groups[].title
Accessibility Discoverability Vocabulary for Schema.org Community Group

# _links.groups[].title
Accessibility for Children Community Group

# _links.groups[].title
Accessibility Roles and Responsibilities Mapping (ARRM) Community Group

# _links.groups[].title
Accessible Platform Architectures Working Group

# _links.groups[].title
Accessible Rich Internet Applications Working Group

# _links.groups[].title
AI KR (Artificial Intelligence Knowledge Representation) Community Group

# _links.groups[].title
ARIA and Assistive Technologies Community Group

# _links.groups[].title
Audiovisual Media Formats for Browsers Community Group

# _links.groups[].title
Automotive Privacy and Security Task Force

# _links.groups[].title
Automotive Privacy Principles Community Group

# _links.groups[].title
Autonomous Agents on the Web Community Group

# _links.groups[].title
Best Practices for Multilingual Linked Open Data Community Group

# _links.groups[].title
Biomass Open Origin Standard for Tracking (BOOST) Community Group

# _links.groups[].title
Bioschemas for lifesciences Community Group

# _links.groups[].title
Building Device Naming Standards Community Group

# _links.groups[].title
Cascading Style Sheets (CSS) Working Group

# _links.groups[].title
Chemistry for the Web and Publishing Community Group

# _links.groups[].title
Circular Economy and Digital Product Passports Community Group

# _links.groups[].title
Cognitive and Learning Disabilities Accessibility Task Force

# _links.groups[].title
Data Privacy Vocabularies and Controls Community Group

# _links.groups[].title
Decentralized Fact-checking & Provenance Organization (DeFacto) Community Group

# _links.groups[].title
Educational and Occupational Credentials in schema.org Community Group

# _links.groups[].title
Financial Industry Business Ontology Community Group

# _links.groups[].title
Healthcare Schema Vocabulary Community Group

# _links.groups[].title
High-Performance Baseline for Web Apps Community Group

# _embedded.groups[].description
The people named by the Advisory Board to be liaisons to the W3C Board of Directors.

# _embedded.groups[].members[].description
The Advisory Board provides ongoing guidance to the Team on issues of strategy, management, legal matters, process, and conflict resolution.

# _embedded.groups[].name
Accessibility at the Edge Community Group

# _embedded.groups[].description
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 W3C Code of Conduct.

# _embedded.groups[].name
Accessibility Conformance Testing (ACT) Task Force

# _embedded.groups[].description
The objective of the Accessibility Conformance Testing (ACT) Task Force is to evolve and maintain a repository of ACT Rules for WCAG 2, to promote a unified interpretation among different web accessibility test tools and methodologies. ACT Rules conform to the ACT Rules Format 1.0 to document different testing practices. The ACT TF reviews ACT Rules, and present them to AGWG when they meet stringent quality criteria. AGWG may publish such ACT Rules as non-normative W3C resources, as part of the supplemental guidance for WCAG 2.

# _embedded.groups[].members[].description
The mission of the Accessibility Guidelines Working Group (AG WG) is to develop specifications to make content on the Web accessible for people with disabilities and to participate in the development and maintenance of implementation support materials for the Web Content Accessibility Guidelines.

# _embedded.groups[].name
Accessibility Discoverability Vocabulary for Schema.org Community Group

# _embedded.groups[].description
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.

# _embedded.groups[].name
Accessibility for Children Community Group

# _embedded.groups[].description
The mission of this group is to discuss accessibility adapted for children (age appropriate, literacy relevant).

The Community Group welcomes meeting accommodation sponsorship through funding or complimentary services. Many thanks to Patricia Lessard, Things Entertainment, LLC and Deaf Services of Palo Alto for your donations.

# _embedded.groups[].description
The mission of the Accessibility Guidelines Working Group (AG WG) is to develop specifications to make content on the Web accessible for people with disabilities and to participate in the development and maintenance of implementation support materials for the Web Content Accessibility Guidelines.

# _embedded.groups[].description
The mission of the Accessibility Internationalization Community Group is to improve the internationalization of:

The Cognitive and Learning Disabilities Accessibility (COGA) Task Force

The Accessibility Guidelines Working Group (AG)

Scope The Accessibility Internationalization Community Group will include the following efforts:

Improve the internationalization of COGA and AG publications.

Develop criteria and tests for easy-to-understand language in different languages.

Develop criteria and tests for text appearance and semantics in different writing systems

Develop criteria and tests for additional guidance that changes based on additional language, writing system, or culture.

The community group’s initial focus is to help internationalize two accessibility resources that are currently in development:

The next version of Making Content Usable for People with Cognitive and Learning Disabilities

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.

# _embedded.groups[].name
Accessibility Roles and Responsibilities Mapping (ARRM) Community Group

# _embedded.groups[].description
This is the community group for individuals interested in contributing to the development and maintenance of the Accessibility Roles and Responsibilities Mapping (ARRM) framework.

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.

This group will not publish Specifications.

# _embedded.groups[].name
Accessible Platform Architectures Working Group

# _embedded.groups[].description
The mission of the Accessible Platform Architectures Working Group (APA WG, formerly part of the Protocols and Formats Working Group) is to ensure W3C specifications provide support for accessibility to people with disabilities. The group advances this mission through review of W3C specifications, development of technical support materials, collaboration with other Working Groups, and coordination of harmonized accessibility strategies within W3C.

# _embedded.groups[].name
Accessible Rich Internet Applications Working Group

# _embedded.groups[].description
The mission of the Accessible Rich Internet Applications Working Group is to enhance the accessibility of web content through the development of supplemental attributes, including roles, states, and other properties, that can be applied to native host language elements and exposed via platform accessibility APIs.

# _embedded.groups[].description
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.

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.

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. 

This group will not publish specifications.

# _embedded.groups[].description
Our goal is to engage and empower accessibility professionals to advance the W3C WAI mission through community driven initiatives. This work could include:

Creating and maintaining a repository of community-built resources that complement WAI

Being a group of active participants that are continually contributing to resources

Vetting and highlighting external resources that relate to and support this group's resources

Being available to W3C Working Groups and Task Forces to assist in writing specifications and resources

This group will not publish Specifications.

# _embedded.groups[].description
The Advisory Board provides ongoing guidance to the Team on issues of strategy, management, legal matters, process, and conflict resolution.

# _embedded.groups[].members[].description
The Advisory Board provides ongoing guidance to the Team on issues of strategy, management, legal matters, process, and conflict resolution.

# _embedded.groups[].description
The Advisory Committee represents the Members of the W3C at large, which name one individual per Member responsible for managing the organization's rights and responsibilities set out in the W3C Process. This includes reviewing plans for W3C work, electing the Advisory Board and the Technical Architecture Group participants, as well as a portion of the W3C Board of Directors. AC Representatives nominate an unlimited amount of work group participants on behalf of their organizations. Lastly, AC Reps represent their organization in implementing the W3C Patent Policy.

# _embedded.groups[].description
This task force explores gaps in African language support on the Web and in eBooks, and documents requirements.

# _embedded.groups[].members[].description
The mission of the Internationalization (I18n) Interest Group, part of the Internationalization Activity, is to help the Working Groups within the Internationalization Activity and provide a forum to discuss issues related to the internationalization of the Web.

# _embedded.groups[].name
AI KR (Artificial Intelligence Knowledge Representation) Community Group

# _embedded.groups[].description
Welcome post

Group's wiki

See also the group's pages from the right-hand side menu

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.

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.

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.

Proposed outcomes:

A comprehensive list of open access resources in both AI and KR (useful to teaching and research)

A set of metadata derived from these resources

A concept map of the domain

A natural language vocabulary to represent various aspects of AI

One or more encoding/implementations/ machine language version of the vocabulary, such as ChatBot Natural Language Understanding & Natural Language Generation

Methods for KR management, especially Natural Language Learning / Semantic Memory

WHO SHOULD JOIN: researchers and practitioners with an interest in developing AI KR artifacts (ontology, machine learning, markup languages)

Editable doc.

# _embedded.groups[].description
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. 

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.

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.

# _embedded.groups[].description
This task force explores gaps in Arabic and Persian language support on the Web and in eBooks, and documents requirements.

# _embedded.groups[].members[].description
The mission of the Internationalization (I18n) Interest Group, part of the Internationalization Activity, is to help the Working Groups within the Internationalization Activity and provide a forum to discuss issues related to the internationalization of the Web.

# _embedded.groups[].name
ARIA and Assistive Technologies Community Group

# _embedded.groups[].description
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.

This community group is dedicated to:

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.

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.

This group will not publish Specifications.

# _embedded.groups[].description
The ARIA Authoring Practices task force to develop WAI-ARIA Authoring Practices, which describes considerations that might not be evident to most authors from the WAI-ARIA specification alone and recommends approaches to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties.

# _embedded.groups[].members[].name
Accessible Rich Internet Applications Working Group

# _embedded.groups[].members[].description
The mission of the Accessible Rich Internet Applications Working Group is to enhance the accessibility of web content through the development of supplemental attributes, including roles, states, and other properties, that can be applied to native host language elements and exposed via platform accessibility APIs.

# _embedded.groups[].description
Coordination for editors of ARIA specifications

# _embedded.groups[].members[].name
Accessible Rich Internet Applications Working Group

# _embedded.groups[].members[].description
The mission of the Accessible Rich Internet Applications Working Group is to enhance the accessibility of web content through the development of supplemental attributes, including roles, states, and other properties, that can be applied to native host language elements and exposed via platform accessibility APIs.

# _embedded.groups[].description
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.

# _embedded.groups[].description
Mission: To create an open standard file format to support audio description all the way from scripting to mixing.

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.

Deliverables:

<ul>
<li>Requirements document</li>
<li>Draft specification document</li>
<li>Explainer</li>
</ul>

# _embedded.groups[].description
The mission of the Audio Working Group is to add advanced sound and music synthesis capabilities to the Open Web Platform.

# _embedded.groups[].name
Audiovisual Media Formats for Browsers Community Group

# _embedded.groups[].description
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.

# _embedded.groups[].description
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.

# _embedded.groups[].members[].name
Automotive and Transportation Business Group

# _embedded.groups[].members[].description
The mission of the Automotive and Transportation Group was to act as an incubator of ideas for standardization for connected vehicles and the broader transportation data space. It had produced some early draft specifications for making vehicle signals available in a browser runtime as a first class object. Those specifications were the basis for launching the W3C Automotive Working Group (which closed on 22 February 2024).

Fuller description of the scope is in the charter.

# _embedded.groups[].members[].description
The mission of the Web Payments Interest Group is to provide a forum for Web Payments technical discussions to identify use cases and requirements for existing and/or new specifications to ease payments on the Web for users (payers) and merchants (payees), and to establish a common ground for payment service providers on the Web Platform. The overall objective of this group is to identify and leverage the conditions for greater uptake and wider use of Web Payments through the identification of standardization needs to increase interoperability between the different stakeholders and the different payment methods.

# _embedded.groups[].name
Automotive Privacy and Security Task Force

# _embedded.groups[].members[].name
Automotive and Transportation Business Group

# _embedded.groups[].members[].description
The mission of the Automotive and Transportation Group was to act as an incubator of ideas for standardization for connected vehicles and the broader transportation data space. It had produced some early draft specifications for making vehicle signals available in a browser runtime as a first class object. Those specifications were the basis for launching the W3C Automotive Working Group (which closed on 22 February 2024).

Fuller description of the scope is in the charter.

# _embedded.groups[].members[].description
The mission of the Automotive Working Group was to develop specifications for exposing information services for in-vehicle and cloud based uses.

# _embedded.groups[].name
Automotive Privacy Principles Community Group

# _embedded.groups[].description
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 It’s Official: Cars Are the Worst Product Category We Have Ever Reviewed for Privacy.

The goal of this Community Group is to create guiding principles specific to the automotive industry and to work in conjunction with COVESA in prototyping and promoting appropriate solutions.

# _embedded.groups[].name
Autonomous Agents on the Web Community Group

# _embedded.groups[].description
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. 

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.

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).

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.

# _embedded.groups[].name
Best Practices for Multilingual Linked Open Data Community Group

# _embedded.groups[].description
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.

This group will not create specifications.

# _embedded.groups[].description
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. 

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.

# _embedded.groups[].name
Biomass Open Origin Standard for Tracking (BOOST) Community Group

# _embedded.groups[].description
The BOOST Community Group brings together stakeholders from across the biomass value chain to develop interoperable data formats and protocols for tracking biomass materials from source to end-use. Our mission is to improve transparency, verification, and trust in biomass supply chains through standardized digital systems.

Purpose and Scope

This Community Group aims to:

Define common data models, vocabularies, and exchange formats for biomass chain of custody information

Improve interoperability between existing traceability systems

Create specifications supporting sustainable biomass verification across international supply chains

Enable digital integration between forestry, agriculture, processing, and energy production systems

Who Should Participate

We welcome participation from:

Forestry and agricultural organizations

Bioenergy and biomaterial producers

Sustainability certification bodies

Supply chain technology providers

Policymakers and regulators

Academic and research institutions

Join us in shaping open technologies that enhance transparency, reduce administrative burden, and support verified sustainability claims throughout the biomass supply chain.

# _embedded.groups[].name
Bioschemas for lifesciences Community Group

# _embedded.groups[].description
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.  

# _embedded.groups[].description
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.

# _embedded.groups[].description
The purpose of the Committee shall be to serve as an independent and objective party to enable, oversee, and monitor the Audit of the Organization’s finances, and report to the Board.

Learn more in the Audit Committee charter.

# _embedded.groups[].members[].description
The W3C Board of Directors —first seated in September 2022— is the governing body of the World Wide Web Consortium public-interest non-profit organization. The Directors have ultimate authority on W3C's strategic direction, have a legal obligation to ensure that W3C implements its mission to lead the Web to its full potential, and have fiduciary responsibility over W3C as a whole.

Directors are:

Dominique Hazaël-Massieux (P)

Chunming Hu (P)

Koichi Moriyama (M)

Jun Murai (P)

Chris Needham (M)

Florian Rivoal (M)

Eric Siow (M)

Léonie Watson (M)

Chris Wilson (M)

Hongru (Judy) Zhu (M)

Non-voting Board meeting participants include:

Tim Berners-Lee, as the Founder Director

Advisory Board liaisons, currently Tantek Çelik and Max Gendler

The W3C Inc bylaws define three classes of Directors:

Member-elected (M): All Member-elected Directors were elected by the W3C Membership in September 2024 to two-year terms.

Partner-selected (P): These Director were elected by their respective Hosts/Partners to one-year terms during the term of their electing Partner's Partnership.

Board-elected (B): The Board may elect up to two additional Directors for two-year terms. Director Camarillo was elected in November 2022.

Officers

President: Seth Dobbs

Treasurer: Ken Troshinsky

Secretary: Christine Gefaell

Board resources

Board home (Member-only info about contact, operations, meetings, etc.)

W3C, Inc. Bylaws and Certificate of Incorporation

# _embedded.groups[].members[].name
Board Audit Committee Guest participants

# _embedded.groups[].members[].description
Additional participants to the Board Audit Committee that are non-Board participants.

# _embedded.groups[].description
The Board Development Committee enables the Board of Directors to properly discharge its duties, by assuring that its composition is appropriate, that Directors are properly informed, trained, and engaged, and that there is a sufficient, diverse, skilled set of candidates for the Consortium Member Director positions.

Learn more in the Development Committee charter.

# _embedded.groups[].members[].description
The W3C Board of Directors —first seated in September 2022— is the governing body of the World Wide Web Consortium public-interest non-profit organization. The Directors have ultimate authority on W3C's strategic direction, have a legal obligation to ensure that W3C implements its mission to lead the Web to its full potential, and have fiduciary responsibility over W3C as a whole.

Directors are:

Dominique Hazaël-Massieux (P)

Chunming Hu (P)

Koichi Moriyama (M)

Jun Murai (P)

Chris Needham (M)

Florian Rivoal (M)

Eric Siow (M)

Léonie Watson (M)

Chris Wilson (M)

Hongru (Judy) Zhu (M)

Non-voting Board meeting participants include:

Tim Berners-Lee, as the Founder Director

Advisory Board liaisons, currently Tantek Çelik and Max Gendler

The W3C Inc bylaws define three classes of Directors:

Member-elected (M): All Member-elected Directors were elected by the W3C Membership in September 2024 to two-year terms.

Partner-selected (P): These Director were elected by their respective Hosts/Partners to one-year terms during the term of their electing Partner's Partnership.

Board-elected (B): The Board may elect up to two additional Directors for two-year terms. Director Camarillo was elected in November 2022.

Officers

President: Seth Dobbs

Treasurer: Ken Troshinsky

Secretary: Christine Gefaell

Board resources

Board home (Member-only info about contact, operations, meetings, etc.)

W3C, Inc. Bylaws and Certificate of Incorporation

# _embedded.groups[].members[].name
Board Development Committee Guest participants

# _embedded.groups[].members[].description
Additional participants to the Board Development Committee that are non-Board participants.

# _embedded.groups[].description
W3C Board Directors. This group only includes the Directors (i.e. without the Officers or support staff).

# _embedded.groups[].members[].description
The W3C Board of Directors —first seated in September 2022— is the governing body of the World Wide Web Consortium public-interest non-profit organization. The Directors have ultimate authority on W3C's strategic direction, have a legal obligation to ensure that W3C implements its mission to lead the Web to its full potential, and have fiduciary responsibility over W3C as a whole.

Directors are:

Dominique Hazaël-Massieux (P)

Chunming Hu (P)

Koichi Moriyama (M)

Jun Murai (P)

Chris Needham (M)

Florian Rivoal (M)

Eric Siow (M)

Léonie Watson (M)

Chris Wilson (M)

Hongru (Judy) Zhu (M)

Non-voting Board meeting participants include:

Tim Berners-Lee, as the Founder Director

Advisory Board liaisons, currently Tantek Çelik and Max Gendler

The W3C Inc bylaws define three classes of Directors:

Member-elected (M): All Member-elected Directors were elected by the W3C Membership in September 2024 to two-year terms.

Partner-selected (P): These Director were elected by their respective Hosts/Partners to one-year terms during the term of their electing Partner's Partnership.

Board-elected (B): The Board may elect up to two additional Directors for two-year terms. Director Camarillo was elected in November 2022.

Officers

President: Seth Dobbs

Treasurer: Ken Troshinsky

Secretary: Christine Gefaell

Board resources

Board home (Member-only info about contact, operations, meetings, etc.)

W3C, Inc. Bylaws and Certificate of Incorporation

# _embedded.groups[].description
The primary purpose of the Committee is to act on behalf of the Board with respect to the affairs of W3C Inc. when time is of the essence, and it is impossible or impractical to convene a meeting of the full Board or conduct an e-vote.

Learn more in its Emergency Committee charter.

# _embedded.groups[].members[].description
The W3C Board of Directors —first seated in September 2022— is the governing body of the World Wide Web Consortium public-interest non-profit organization. The Directors have ultimate authority on W3C's strategic direction, have a legal obligation to ensure that W3C implements its mission to lead the Web to its full potential, and have fiduciary responsibility over W3C as a whole.

Directors are:

Dominique Hazaël-Massieux (P)

Chunming Hu (P)

Koichi Moriyama (M)

Jun Murai (P)

Chris Needham (M)

Florian Rivoal (M)

Eric Siow (M)

Léonie Watson (M)

Chris Wilson (M)

Hongru (Judy) Zhu (M)

Non-voting Board meeting participants include:

Tim Berners-Lee, as the Founder Director

Advisory Board liaisons, currently Tantek Çelik and Max Gendler

The W3C Inc bylaws define three classes of Directors:

Member-elected (M): All Member-elected Directors were elected by the W3C Membership in September 2024 to two-year terms.

Partner-selected (P): These Director were elected by their respective Hosts/Partners to one-year terms during the term of their electing Partner's Partnership.

Board-elected (B): The Board may elect up to two additional Directors for two-year terms. Director Camarillo was elected in November 2022.

Officers

President: Seth Dobbs

Treasurer: Ken Troshinsky

Secretary: Christine Gefaell

Board resources

Board home (Member-only info about contact, operations, meetings, etc.)

W3C, Inc. Bylaws and Certificate of Incorporation

# _embedded.groups[].description
The W3C Board Finance Committee assists the Board in fulfilling its oversight responsibilities to hold the Consortium to account regarding:

On-going financial viability;
Financial budgets and the availability of all analysis relevant to Consortium finances;
Internal controls and financial/accounting processes;
Accuracy and timeliness of financial statements.

Learn more in the Finance Committee charter.

# _embedded.groups[].members[].description
The W3C Board of Directors —first seated in September 2022— is the governing body of the World Wide Web Consortium public-interest non-profit organization. The Directors have ultimate authority on W3C's strategic direction, have a legal obligation to ensure that W3C implements its mission to lead the Web to its full potential, and have fiduciary responsibility over W3C as a whole.

Directors are:

Dominique Hazaël-Massieux (P)

Chunming Hu (P)

Koichi Moriyama (M)

Jun Murai (P)

Chris Needham (M)

Florian Rivoal (M)

Eric Siow (M)

Léonie Watson (M)

Chris Wilson (M)

Hongru (Judy) Zhu (M)

Non-voting Board meeting participants include:

Tim Berners-Lee, as the Founder Director

Advisory Board liaisons, currently Tantek Çelik and Max Gendler

The W3C Inc bylaws define three classes of Directors:

Member-elected (M): All Member-elected Directors were elected by the W3C Membership in September 2024 to two-year terms.

Partner-selected (P): These Director were elected by their respective Hosts/Partners to one-year terms during the term of their electing Partner's Partnership.

Board-elected (B): The Board may elect up to two additional Directors for two-year terms. Director Camarillo was elected in November 2022.

Officers

President: Seth Dobbs

Treasurer: Ken Troshinsky

Secretary: Christine Gefaell

Board resources

Board home (Member-only info about contact, operations, meetings, etc.)

W3C, Inc. Bylaws and Certificate of Incorporation

# _embedded.groups[].description
The Governance Committee ensures that the governance structures and processes for the Consortium (including the Board) are appropriate and documented. It oversees the governance of the W3C as a global collaboration between Members, Partners, and other contributors.

Learn more in the Governance Committee charter.

# _embedded.groups[].members[].description
The W3C Board of Directors —first seated in September 2022— is the governing body of the World Wide Web Consortium public-interest non-profit organization. The Directors have ultimate authority on W3C's strategic direction, have a legal obligation to ensure that W3C implements its mission to lead the Web to its full potential, and have fiduciary responsibility over W3C as a whole.

Directors are:

Dominique Hazaël-Massieux (P)

Chunming Hu (P)

Koichi Moriyama (M)

Jun Murai (P)

Chris Needham (M)

Florian Rivoal (M)

Eric Siow (M)

Léonie Watson (M)

Chris Wilson (M)

Hongru (Judy) Zhu (M)

Non-voting Board meeting participants include:

Tim Berners-Lee, as the Founder Director

Advisory Board liaisons, currently Tantek Çelik and Max Gendler

The W3C Inc bylaws define three classes of Directors:

Member-elected (M): All Member-elected Directors were elected by the W3C Membership in September 2024 to two-year terms.

Partner-selected (P): These Director were elected by their respective Hosts/Partners to one-year terms during the term of their electing Partner's Partnership.

Board-elected (B): The Board may elect up to two additional Directors for two-year terms. Director Camarillo was elected in November 2022.

Officers

President: Seth Dobbs

Treasurer: Ken Troshinsky

Secretary: Christine Gefaell

Board resources

Board home (Member-only info about contact, operations, meetings, etc.)

W3C, Inc. Bylaws and Certificate of Incorporation

# _embedded.groups[].description
The W3C Board of Directors —first seated in September 2022— is the governing body of the World Wide Web Consortium public-interest non-profit organization. The Directors have ultimate authority on W3C's strategic direction, have a legal obligation to ensure that W3C implements its mission to lead the Web to its full potential, and have fiduciary responsibility over W3C as a whole.

Directors are:

Dominique Hazaël-Massieux (P)

Chunming Hu (P)

Koichi Moriyama (M)

Jun Murai (P)

Chris Needham (M)

Florian Rivoal (M)

Eric Siow (M)

Léonie Watson (M)

Chris Wilson (M)

Hongru (Judy) Zhu (M)

Non-voting Board meeting participants include:

Tim Berners-Lee, as the Founder Director

Advisory Board liaisons, currently Tantek Çelik and Max Gendler

The W3C Inc bylaws define three classes of Directors:

Member-elected (M): All Member-elected Directors were elected by the W3C Membership in September 2024 to two-year terms.

Partner-selected (P): These Director were elected by their respective Hosts/Partners to one-year terms during the term of their electing Partner's Partnership.

Board-elected (B): The Board may elect up to two additional Directors for two-year terms. Director Camarillo was elected in November 2022.

Officers

President: Seth Dobbs

Treasurer: Ken Troshinsky

Secretary: Christine Gefaell

Board resources

Board home (Member-only info about contact, operations, meetings, etc.)

W3C, Inc. Bylaws and Certificate of Incorporation

# _embedded.groups[].description
W3C Board Officers. This group only includes the Officers, including the President, Treasurer, and Secretary of the Board.

# _embedded.groups[].members[].description
The W3C Board of Directors —first seated in September 2022— is the governing body of the World Wide Web Consortium public-interest non-profit organization. The Directors have ultimate authority on W3C's strategic direction, have a legal obligation to ensure that W3C implements its mission to lead the Web to its full potential, and have fiduciary responsibility over W3C as a whole.

Directors are:

Dominique Hazaël-Massieux (P)

Chunming Hu (P)

Koichi Moriyama (M)

Jun Murai (P)

Chris Needham (M)

Florian Rivoal (M)

Eric Siow (M)

Léonie Watson (M)

Chris Wilson (M)

Hongru (Judy) Zhu (M)

Non-voting Board meeting participants include:

Tim Berners-Lee, as the Founder Director

Advisory Board liaisons, currently Tantek Çelik and Max Gendler

The W3C Inc bylaws define three classes of Directors:

Member-elected (M): All Member-elected Directors were elected by the W3C Membership in September 2024 to two-year terms.

Partner-selected (P): These Director were elected by their respective Hosts/Partners to one-year terms during the term of their electing Partner's Partnership.

Board-elected (B): The Board may elect up to two additional Directors for two-year terms. Director Camarillo was elected in November 2022.

Officers

President: Seth Dobbs

Treasurer: Ken Troshinsky

Secretary: Christine Gefaell

Board resources

Board home (Member-only info about contact, operations, meetings, etc.)

W3C, Inc. Bylaws and Certificate of Incorporation

# _embedded.groups[].description
The W3C Board Personnel Committee provides guidance, oversight, and support to W3C management as it develops and implements personnel employment, performance management, and compensation systems.

Learn more in the Personnel Committee charter.

# _embedded.groups[].members[].description
The W3C Board of Directors —first seated in September 2022— is the governing body of the World Wide Web Consortium public-interest non-profit organization. The Directors have ultimate authority on W3C's strategic direction, have a legal obligation to ensure that W3C implements its mission to lead the Web to its full potential, and have fiduciary responsibility over W3C as a whole.

Directors are:

Dominique Hazaël-Massieux (P)

Chunming Hu (P)

Koichi Moriyama (M)

Jun Murai (P)

Chris Needham (M)

Florian Rivoal (M)

Eric Siow (M)

Léonie Watson (M)

Chris Wilson (M)

Hongru (Judy) Zhu (M)

Non-voting Board meeting participants include:

Tim Berners-Lee, as the Founder Director

Advisory Board liaisons, currently Tantek Çelik and Max Gendler

The W3C Inc bylaws define three classes of Directors:

Member-elected (M): All Member-elected Directors were elected by the W3C Membership in September 2024 to two-year terms.

Partner-selected (P): These Director were elected by their respective Hosts/Partners to one-year terms during the term of their electing Partner's Partnership.

Board-elected (B): The Board may elect up to two additional Directors for two-year terms. Director Camarillo was elected in November 2022.

Officers

President: Seth Dobbs

Treasurer: Ken Troshinsky

Secretary: Christine Gefaell

Board resources

Board home (Member-only info about contact, operations, meetings, etc.)

W3C, Inc. Bylaws and Certificate of Incorporation

# _embedded.groups[].description
The mission of the Browser Testing and Tools Working Group is to produce technologies for use in testing, debugging, and troubleshooting of Web applications running in Web browsers.

# _embedded.groups[].name
Building Device Naming Standards Community Group

# _embedded.groups[].description
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.

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. 

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.  

The work of this community group will align with and complement other initiatives in the industry such as BRICK, Haystack, Omniclass, Uniclass, IFC etc. 

In scope for this work are:
<ul>
<li>A simple specification for naming syntax</li>
<li>A register of building device names and labels</li>
</ul>

# _embedded.groups[].name
Cascading Style Sheets (CSS) Working Group

# _embedded.groups[].description
The mission of the group is to develop and maintain CSS.

# _embedded.groups[].name
Chemistry for the Web and Publishing Community Group

# _embedded.groups[].description
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.

# _embedded.groups[].description
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.

# _embedded.groups[].description
This group allows a network of experts to share information about gaps and requirements for support of Simplified and Traditional Chinese on the Web and in eBooks.

本小组探讨在网页和电子书中使用简体、繁体中文时的各语言、文种支持的需求以及目前差距。

# _embedded.groups[].members[].description
The mission of the Internationalization (I18n) Interest Group, part of the Internationalization Activity, is to help the Working Groups within the Internationalization Activity and provide a forum to discuss issues related to the internationalization of the Web.

# _embedded.groups[].description
The Chinese Web Interest Group provides a forum for W3C members to enhance the participation in Web standards work from the Chinese Web community.

# _embedded.groups[].name
Circular Economy and Digital Product Passports Community Group

# _embedded.groups[].description
The mission of this group is to support the technical implementation of infrastructure and applications for the Circular Economy (CE), and one of its digital cornerstones — Digital Product Passports (DPPs). This community group will complement the work of the ISO/TC 323 on CE standardisation, with discussions from a technical and web-focused perspective.

The group will primarily be a discussion group, but may in the future decide to produce reports or other deliverables. This group will not publish Specifications. Starting out, the group will discuss the requirements set by the CE and DPPs on web technologies and standards, to identify standardisation challenges that are not yet met. Group members will share ideas, experiences and thoughts on usage of web technologies in these areas, their strengths and weaknesses, and open challenges — for instance in the form of use cases.

For this community group we welcome all parties interested in the technical aspects of CE, and DPP implementation. We envision that participants either have knowledge and expertise on CE and DPPs, e.g. material flows, manufacturing, modelling, or business aspects, so they are able to, for instance, contribute use cases, needs, and test scenarios. Additionally, we welcome participants with knowledge and expertise on web infrastructure, technologies, and standards who are interested in applying their expertise to address CE-related challenges.

# _embedded.groups[].description
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.

# _embedded.groups[].description
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.

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.

3. Out of Scope The following are out of scope: Actual development of standards.

4. Success Criteria The Group will have succeeded if it can achieve the following:

- 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.

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.

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.

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.

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.

9. Dependencies or Liaisons The group may collaborate with other relevant groups within W3C.

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.

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.

The W3C Code of Ethics and Professional Conduct applies to participation in this group.

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.

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.

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.

All Github repositories attached to the Community Group must contain a copy of the CONTRIBUTING and LICENSE files.

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.

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.

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.

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.

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.

# _embedded.groups[].description
Mission

The mission of the COGA Community Group is to work with and support the Cognitive and Learning Disabilities Accessibility (COGA) Task Force  to improve web accessibility for people with cognitive and learning disabilities.

This group supports the COGA Task Force by supplying user needs and feedback.

Scope
The COGA Community Group’s work will include:
- Sharing challenges when using the web and other digital displays
- Suggesting user needs
- Helping with research
- Suggesting ways to improve accessibility for the community
- Reviewing COGA’s drafts
- Outreach and collecting feedback from the community
- Helping with policy and the business cases for COGA guidance
- Having open meetings to discuss these points
Open meetings may be live video conferences or in other discussion formats

Participation

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.

The COGA Community Group will also work together on some topics, brainstorming and building a community dedicated to improved access for all.

Anyone can join this group as long as they follow the community guidelines.

However, the community group will specifically benefit from including:
- people with learning and cognitive disabilities,
people with mental health challenges,
- caregivers, therapists and people who work with people with learning, cognitive challenges and in mental health,
- researchers,
developers, quality assurance professionals, and user interface experts,
industry, looking to share and support ideas, and
policy makers.

Additional details of participation
- Joining the COGA Community Group does not involve joining the COGA Task Force.
- If you would prefer to join this group anonymously, please send an email to ran@w3.org.
- The community group will not publish specifications, but may make suggestions to the COGA taskforce.
- For more information about community groups, please visit Community and Business Groups Frequently Asked Questions.
- Short link to this document: bit.ly/coga-community

# _embedded.groups[].description
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.

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:

• Cognitive AI CG GitHub Repository

• Chunks and Rules Specification

• Keynote on Cognitive AI for the 2020 Summer School on AI in Industry 4.0

• An older talk on Cognitive AI and the Sentient Web

• Longer treatise on Cognitive AI

• Public mailing list archive

• Contributing to the Cognitive AI Community Group

# _embedded.groups[].name
Cognitive and Learning Disabilities Accessibility Task Force

# _embedded.groups[].description
The Cognitive and Learning Disabilities Accessibility Task Force will develop draft proposed guidance and techniques to make web content, content authoring, and user agent implementation accessible and more useable by people with cognitive and learning disabilities.

# _embedded.groups[].members[].description
The mission of the Accessibility Guidelines Working Group (AG WG) is to develop specifications to make content on the Web accessible for people with disabilities and to participate in the development and maintenance of implementation support materials for the Web Content Accessibility Guidelines.

# _embedded.groups[].members[].name
Accessible Platform Architectures Working Group

# _embedded.groups[].members[].description
The mission of the Accessible Platform Architectures Working Group (APA WG, formerly part of the Protocols and Formats Working Group) is to ensure W3C specifications provide support for accessibility to people with disabilities. The group advances this mission through review of W3C specifications, development of technical support materials, collaboration with other Working Groups, and coordination of harmonized accessibility strategies within W3C.

# _embedded.groups[].description
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.

Current Charter

# _embedded.groups[].description
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.

# _embedded.groups[].description
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. 

# _embedded.groups[].description
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:

Synchronizing Semantic Stores with Commutative Replicated Data Types

RDF Delta - Replicating RDF Datasets

Conflict-Free Replicated Data Types (CRDT)

m-ld Specification

Conflict-Free Replicated Datatypes (CRDT)

rdf-dataset-changelog

Linked Data Objects: Transactions

As well as broader CRDT and local-first community https://localfirstweb.dev/

This CG would offer a neutral space to help coordinate those efforts.

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.

# _embedded.groups[].description
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.

# _embedded.groups[].description
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.

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.

Please see the group wiki for more details.

# _embedded.groups[].description
A group to debate and define CSS4.

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. 

Discussion began at: https://github.com/w3c/csswg-drafts/issues/4770

This WICG group is a place to work out the details. 

# _embedded.groups[].description
Discussions and mutual support for implementers, publishers and spec developers of the technologies developed by the CSV on the Web 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.

# _embedded.groups[].name
Data Privacy Vocabularies and Controls Community Group

# _embedded.groups[].description
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 General Data Protection Regulation (GDPR), 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.

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 Data Privacy Vocabulary (DPV) as a deliverable.

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 requested here. The group meets usually through online meeting calls, details of which, including past minutes, can be found here. The group also interacts through a mailing list regarding topics, discussions, sharing of agendas, actions, and other relevant items. The resources and work relevant to the group is hosted on the GitHub platform under the DPVCG name.

The group is currently chaired by:

Harshvardhan J. Pandit (ADAPT SFI Research Centre, Trinity College Dublin)

Previously, it was chaired by:

Bert Bos (ERCIM W3C)

Axel Polleres (WU Wirschaftsuniversitat Wien – Vienna University of Economics and Business)

Participation in Group Activities

The working of the group is fairly open and transparent in its process, with most of the information present on the wiki. For past work, actions, issues, and records – please refer to the wiki and threads on the mailing list. Anyone can use the mailing list 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.

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.

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 GitHub repo.

Data Privacy Vocabulary (DPV)

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 personal data categories are undergoing a what kind of processing by a specific data controller and/or transferred to some recipient for a particular purpose, based on a specific legal basis (e.g., consent, or other legal grounds such as legitimate interest, etc.), with specified technical and organisational measures and restrictions (e.g., storage locations and storage durations) in place.

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.

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.

# _embedded.groups[].description
The mission of the Data Shapes Working Group is to update data shapes standards in line with the versions of core Semantic Web standards that cater for RDF-star and to extend the applications of data shapes with new packaging and use specifications.

# _embedded.groups[].description
The mission of the Dataset Exchange WG is to:
1. Maintain and revise the Data Catalog Vocabulary, DCAT, taking into account feature requests from the DCAT user community.
2. Define and publish guidance on the specification and use of application profiles when requesting and serving data on the Web.

# _embedded.groups[].description
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.

# _embedded.groups[].members[].description
The mission of the Dataset Exchange WG is to:
1. Maintain and revise the Data Catalog Vocabulary, DCAT, taking into account feature requests from the DCAT user community.
2. Define and publish guidance on the specification and use of application profiles when requesting and serving data on the Web.

# _embedded.groups[].name
Decentralized Fact-checking & Provenance Organization (DeFacto) Community Group

# _embedded.groups[].description
The Decentralized Fact-checking & Provenance Community Group (DFCP) is committed to actively researching, developing, building, maintaining, managing, upgrading, and implementing robust amendments for a decentralized fact-checking system and stringent provenance standards for text-based literature and content. We will drive this initiative forward with determination and efficacy.

DFCP strives to empower societies with tools to identify and mitigate/counter misinformation, disinformation, and Fake News at scale.

This group will publish Specifications.

# _embedded.groups[].description
The mission of the Decentralized Identifier Working Group is two-fold. First, it will maintain the Decentralized Identifiers (DIDs) specification and related Working Group Notes. Second, it will seek consensus around the best way to achieve effective interoperability through common requirements, algorithms, architectural options, and various considerations for the DID resolution and DID URL dereferencing processes.

Minutes of past meetings

Past resolutions

Information about the previous DID Working Group is still available on its old homepage.

# _embedded.groups[].description
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.

# _embedded.groups[].description
The mission of the Devices and Sensors Working Group (DAS WG) is to create secure and privacy-preserving client-side APIs that enable the development of web applications that interact with device capabilities.

# _embedded.groups[].description
The mission of the Distributed Tracing is to define standards for interoperability between tracing tools.

# _embedded.groups[].description
The mission of the W3C Documentation Community Group (W3C Docs CG) is to ensure web developers and designers worldwide have the best information available so they can build things on the web platform.

See its proposed charter.

This group will not publish Specifications.

# _embedded.groups[].name
Educational and Occupational Credentials in schema.org Community Group

# _embedded.groups[].description
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 glossary of credentialing terms.

Related work includes: the Credential Transparency Description Language (CTDL) developed for the Credential Engine; IMS Global's Badge Alliance; and, the W3C Verifiable Claims Working Group. 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.

# _embedded.groups[].description
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/

# _embedded.groups[].description
Working on a standard annotation facility for EPUB Publications

# _embedded.groups[].members[].description
The mission of the Publishing Maintenance Working is to maintain the W3C Recommendations, as well as related Notes, in the area of Digital Publishing published by the Audiobooks and the EPUB Working Groups.

# _embedded.groups[].description
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).

# _embedded.groups[].description
This task force explores gaps in Ethiopic script support on the Web and in eBooks, and documents requirements.

# _embedded.groups[].members[].description
The mission of the Internationalization (I18n) Interest Group, part of the Internationalization Activity, is to help the Working Groups within the Internationalization Activity and provide a forum to discuss issues related to the internationalization of the Web.

# _embedded.groups[].description
This task force explores gaps in European language support on the Web and in eBooks, and documents requirements.

# _embedded.groups[].members[].description
The mission of the Internationalization (I18n) Interest Group, part of the Internationalization Activity, is to help the Working Groups within the Internationalization Activity and provide a forum to discuss issues related to the internationalization of the Web.

# _embedded.groups[].description
The mission of this group is to lead to extension of XPath and all related technologies (XSLT, XQuery, XProc, XForms, XML Schema).

# _embedded.groups[].description
The mission of the Exploration Interest Group is to provide W3C Members with a forum to explore and discuss emerging web-related technology trends and consider how the community could collaborate to shape those trends for the benefit of web users.

# _embedded.groups[].description
FAST TF is to develop the FAST to collect user and functional needs, develop guidance to meet those needs in technologies and work with other groups to develop this guidance for content developers.

# _embedded.groups[].members[].name
Accessible Platform Architectures Working Group

# _embedded.groups[].members[].description
The mission of the Accessible Platform Architectures Working Group (APA WG, formerly part of the Protocols and Formats Working Group) is to ensure W3C specifications provide support for accessibility to people with disabilities. The group advances this mission through review of W3C specifications, development of technical support materials, collaboration with other Working Groups, and coordination of harmonized accessibility strategies within W3C.

# _embedded.groups[].description
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. 

# _embedded.groups[].description
The mission of the Federated Identity Working Group is to develop specifications to allow a website to request a federated identity credential or assertion with the purpose of authenticating a user and/or requesting a set of claims in a compatible way to OIDC or SAML.

# _embedded.groups[].description
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.

# _embedded.groups[].name
Financial Industry Business Ontology Community Group

# _embedded.groups[].description
The mission of Financial Industry Business Ontology Community Group is to propose, discuss, create and maintain extensions to schema.org related to Financial Industries. 

# _embedded.groups[].description
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:

Track specifications and vendor implementations related to open web games.

Recommend new specifications to be produced and find group homes for them.

Refine use cases to communicate specific needs of games.

Suggest refinements or fixes to existing specifications to better meet the needs of the game development community.

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.

Evangelize specifications to browser vendors.

Document how to best use open web standards for games.

Evangelize open web standards to game developers and game development best practices to web developers.

The Games community group will not develop any normative specification. As such, there will not be any Essential Claims under the W3C Contributor License Agreement or Final Specification Agreement.

Please see the adopted charter for details.

# _embedded.groups[].description
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 draft charter. 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.

# _embedded.groups[].description
The mission of the GPU for the Web Working Group is to provide an interface between the Web Platform and modern 3D graphics and computation capabilities present on native system platforms.

# _embedded.groups[].name
Healthcare Schema Vocabulary Community Group

# _embedded.groups[].description
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.

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.

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.

# _embedded.groups[].description
This group exists to explore gaps and requirements for support of languages using the Hebrew script on the Web and in eBooks.

# _embedded.groups[].members[].description
The mission of the Internationalization (I18n) Interest Group, part of the Internationalization Activity, is to help the Working Groups within the Internationalization Activity and provide a forum to discuss issues related to the internationalization of the Web.

# _embedded.groups[].name
High-Performance Baseline for Web Apps Community Group

# _embedded.groups[].description
The High-Performance Baseline Community Group aims to enhance the diversify the ecosystem of Web user agents by enabling a baseline or subset of standards to increase efficiency and optimize the user experience on Web and WebView-based apps while maintaining compatibility with existing standards. The subsets will allow the implementation of lighter and more efficient user agents for specific purposes (e.g., MiniApps, IoT applications, and cross-platform apps, among others). This forum intends to gather vendors of embedded browsers, hybrid cross-platform app frameworks, JS engines and others interested in providing specific scenarios and use cases to define proper subsets of the specifications and even propose additional activities to existing Working Groups.

This CG expects good alignment with other incubation groups, including WebViews CG and WICG, and standardization groups (e.g., CSS WG, Web Applications WG, and WHATCG, among others). After getting support for this idea, more specific goals and a tentative timeline will be defined in the charter.

# _embedded.groups[].description
The mission of the HTML Working Group is to give input to and bring the WHATWG HTML and DOM Review Drafts to W3C Recommendations.

# _embedded.groups[].description
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. 

This group may produce technical specifications.

# _embedded.groups[].description
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.

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.

More information about these technologies can be found on our homepage: http://www.hydra-cg.com/