A variety of W3C groups enable W3C to pursue its mission through the creation of Web standards, guidelines, and supporting materials. Community and Business Groups offer more ways for innovators to bring work to W3C.
The mission of the Audio Working Group is to define a client-side script API adding more advanced audio capabilities than are currently offered by audio elements. The API will support the features required by advanced interactive applications including the ability to process and synthesize audio streams directly in script.
The Authoring Tool Accessibility Guidelines Working Group is chartered to maintain and support the Authoring Tool Accessibility Guidelines 1.0 W3C Recommendation, and develop ATAG 2, a second version of these authoring tools accessibility guidelines.
The mission of the CSV on the Web Working Group is to provide technologies whereby data dependent applications on the Web can provide higher interoperability when working with datasets using the CSV (Comma-Separated Values) or similar formats. As well as single CSV files, the group will define mechanisms for interpreting a set of CSVs as relational data. This will include the definition of a vocabulary for describing tables expressed as CSV and locatable on the web, and the relationships between them.
The mission of the Data on the Web Best Practices Working Group is (1) to develop the open data ecosystem, facilitating better communication between developers and publishers; (2) to provide guidance to publishers that will improve consistency in the way data is managed, thus promoting the re-use of data; (3) to foster trust in the data among developers, whatever technology they choose to use, increasing the potential for genuine innovation.
The mission of the Device APIs and Policy Working Group is to create client-side APIs that enable the development of Web Applications and Web Widgets that interact with devices services such as Calendar, Contacts, Camera, etc. Additionally, the group will produce a framework for the expression of security policies that govern access to security-critical APIs (such as the APIs listed previously).
The mission of the Education and Outreach Working Group (EOWG) is to develop strategies, and awareness and training resources, to educate a variety of audiences regarding the need for Web accessibility and approaches to implementing Web accessibility.
The mission of the Evaluation and Repair Tools Working Group (ERT WG) is to develop techniques and resources to facilitate the evaluation and repair of Web sites with regard to their conformance to the Web Content Accessibility Guidelines 2.0, and to facilitate testing across all three WAI guidelines also including the Authoring Tool Accessibility Guidelines and User Agent Accessibility Guidelines.
The mission of the Indie UI Working Group, part of the WAI Technical Activity, is to develop event models for Application Programming Interfaces (APIs) that facilitate interaction in Web applications that are input method independent, and hence accessible to people with disabilities.
The mission of the Internationalization Core Working Group is to enable universal access to the World Wide Web by proposing and coordinating the adoption by the W3C of techniques, conventions, technologies, and designs that enable and enhance the use of W3C technology and the Web worldwide, with and between the various different languages, scripts, regions, and cultures.
The mission of the Linked Data Platform (LDP) Working Group is to produce a W3C Recommendation for HTTP-based (RESTful) application integration patterns using read/write Linked Data. This work will benefit both small-scale in-browser applications (WebApps) and large-scale Enterprise Application Integration (EAI) efforts. It will complement SPARQL and will be compatible with standards for publishing Linked Data, bringing the data integration features of RDF to RESTful, data-oriented software development.
The mission of the Math Working Group is to facilitate and promote the use of the Web for mathematical and scientific communication. The main purpose of the Working Group is to improve and extend the functionality of the MathML 2.0 (Second Edition) Recommendation (W3C Recommendation, 21 October 2003) in light of several years of experience of large-scale deployment by many individuals and organizations.
The mission of the Protocols and Formats Working Group (PFWG) (Member Confidential PFWG) is to increase the support for accessibility in Web specifications. This mission flows from the W3C mission of promoting universal access and interoperability across the Web.
The mission of the RDF Data Shapes Working Group is to produce a language for defining structural constraints on RDF graphs. In the same way that SPARQL made it possible to query RDF data, the product of the RDF Data Shapes WG will enable the definition of graph topologies for interface specification, code development, and data verification.
The mission of the Research and Development Working Group (RDWG) is to increase the incorporation of accessibility considerations into research on Web technologies, and to identify projects researching Web accessibility and suggest research questions that may contribute to new projects. The desired outcome of more research in Web accessibility and awareness of accessibility in mainstream Web-related research should decrease the number of potential barriers in future Web-related technologies.
The mission of the Social Web Working Group, part of the Social Activity, is to define the techical protocols, vocabularies, and APIs to facilitate access to social functionality as part of the Open Web Platform. These technologies should allow communication between indepedent systems, federation (also called "decentralization") being part of the design.
The mission of the Spatial Data on the Web Working Group is to clarify and formalize the relevant standards landscape around spatial data on the Web. This includes: (1) to determine how spatial information can best be integrated with other data on the Web; (2) to determine how machines and people can discover that different facts in different datasets relate to the same place, especially when 'place' is expressed in different ways and at different levels of granularity; (3) to identify and assess existing methods and tools and then create a set of best practices for their use; (4) where desirable, to complete the standardization of informal technologies already in widespread use.
The mission of the SVG Working Group is to continue the evolution of Scalable Vector Graphics as a format and a platform, and enhance the adoption and usability of SVG in combination with other technologies.
The mission of the System Applications Working Group is to define a runtime environment, security model, and associated APIs for building Web applications with comparable capabilities to native applications. This requires stronger integration with the host platform than is the case for traditional web pages. Browsers are designed to cope with the user visiting untrusted web sites, necessitating a cautious approach to security that narrowly limits what a particular website can do. The contrast between the two contexts can be illustrated by comparing a) an application with limited access to specific fields in the user's contacts, and b) an application that implements a contacts manager, where the application is entrusted with the ability to access, create, delete and update entries.
The mission of the Timed Text Working Group is to produce a W3C Recommendation for media online captioning by refining the W3C specification Timed Text (TT) Authoring Format 1.0 â€” Distribution Format Exchange Profile (DFXP) based in implementation experience and interoperability feedback.
The mission of the Tracking Protection Working Group is to improve user privacy and user control by defining mechanisms for expressing user preferences around Web tracking and for blocking or allowing Web tracking elements.
The mission of the User Agent Accessibility Guidelines Working Group is to produce guidelines for the development of accessible user agents: software that retrieves and renders Web content, including text, graphics, sounds, video, images, etc. In particular, the groups seeks to support the implementation of the User Agent Accessibility Guidelines 1.0 , and to collect requirements for a subsequent version of User Agent Accessibility Guidelines.
The mission of the Voice Browser Working Group, part of the Voice Browser Activity, is to enable users to speak and listen to Web applications by creating standard languages for developing Web-based speech applications. The Voice Browser Working Group concentrates on languages for capturing and producing speech and managing the dialog between user and computer, while a related Group, the Multimodal Interaction Working Group, concentrates on additional input modes including keyboard and mouse, ink and pen, etc.
The mission of the Web Annotation Working Group, part of the Digital Publishing Activity, is to define a generic data model for Annotations, and define the basic infrastructural elements to make it deployable in browsers and reading systems through suitable user interfaces.
The mission of the Web Applications (WebApps) Working Group is to provide specifications that enable improved client-side application development on the Web, including specifications both for application programming interfaces (APIs) for client-side development and for markup vocabularies for describing and controlling client-side application behavior.
The mission of the Web Content Accessibility Guidelines Working Group is to develop guidelines to make Web content accessible for people with disabilities. In particular, the group is responsible for the Web Content Accessibility Guidelines 2.0 as a W3C Recommendation.
The mission of this group is to define an API that lets developers implement secure application protocols on the level of Web applications, including message confidentiality and authentication services, by exposing trusted cryptographic primitives from the browser. Web application developers will no longer have to create their own or use untrusted third-party libraries for cryptographic primitives. This will improve security on the Web.
The mission of the Web Notification Working Group, part of the Rich Web Client Activity, is to produce specifications that define APIs to generate notifications to alert users. A Notification in this context may be displayed asynchronously and may not require user confirmation. Additionally, events are specified for managing user interactions with notifications.
The mission of the Web Real-Time Communications Working Group is to define client-side APIs to enable Real-Time Communications in Web browsers. These APIs should enable building applications that can be run inside a browser, requiring no extra downloads or plugins, that allow communication between parties using audio, video and supplementary real-time communication, without having to use intervening servers.
The mission of the Web Fonts Working Group is to develop specifications that allow the interoperable deployment of downloadable fonts on the Web. Existing specifications (CSS3 Fonts, SVG) explain how to describe and link to fonts, so the main focus will be the standardisation of font formats suited to the task, and a specification defining conformance (for fonts, authoring tools, viewers, etc.) all the technology required for WebFonts.
The XML Processing Model Working Group is defining XProc, an XML-based language that allows the creator of any given XML document to indicate that operations on that document should be performed in a specific order for a particular result, and if so, how to apply those operations.
The mission of the XML Query Working Group is to provide flexible query facilities to extract data from XML and virtual documents, such as contents of databases or other persistent storage that are viewed as XML via a mapping mechanism, on the Web.
The mission of the XSL Working Group is to define and maintain a practical style and transformation language capable of supporting the transformation and presentation of, and interaction with, structured information (e.g., XML documents) for use on servers and clients. The language is designed to build transformations in support of browsing, printing, interactive editing, and transcoding of one XML vocabulary into another XML vocabulary. To enhance accessibility, XSL is able to present information both visually and non-visually. XSL is not intended to replace CSS, but will provide functionality beyond that defined by CSS, for example, element re-ordering.
The mission of the Digital Publishing Interest Group is to provide a forum for experts in the digital publishing ecosystem of electronic journals, magazines, news, or book publishing (authors, creators, publishers, news organizations, booksellers, accessibility and internationalization specialists, etc.) for technical discussions, gathering use cases and requirements to align the existing formats and technologies (e.g., for electronic books) with those used by the Open Web Platform. The goal is to ensure that the requirements of digital publishing can be answered, when in scope, by the Recommendations published by W3C. This group is not chartered to publish Recommendations; instead, the goal is to cooperate with the relevant W3C Working Groups to ensure that the requirements of this particular community are met.
The mission of the HTML5 Chinese Interest Group is to facilitate focused discussion in Chinese of the HTML5 specification and of specifications closely related to HTML5, to gather comments and questions in Chinese about those specifications, to collect information about specific use cases in Chinese speaking region for technologies defined in those specifications, and to report the results of its activities as a group back to the HTML Working Group, as well as to other relevant groups and to the W3C membership and community.
The mission of the Internationalization (I18n) Interest Group, part of the Internationalization Activity, is to help the Working Groups within the Internationalization Activity and provides a forum to discuss issues related to the internationalization of the Web.
The Patent and Standards Interest Group (PSIG) is a forum for W3C Members and Invited Experts to discuss policy issues regarding the implementation of the W3C Patent Policy as well as new Patent-related questions that arise which require action or attention from the W3C Membership. The PSIG has no authority to create new policy. However, input from the PSIG on the operation of the policy and areas that might require further policy development by a W3C Working Group is welcome.
The mission of the Privacy Interest Group, part of the Privacy Activity, is to improve the support of privacy in Web standards by monitoring ongoing privacy issues that affect the Web, investigating potential areas for new privacy work, and providing guidelines and advice for addressing privacy in standards development.
The mission of the Semantic Web Health Care and Life Sciences Interest Group is to develop, advocate for, and support the use of Semantic Web technologies for health care and life science, with focus on biological science and translational medicine. These domains stand to gain tremendous benefit by adoption of Semantic Web technologies, as they depend on the interoperability of information from many domains and processes for efficient decision support.
The Semantic Web Interest Group is a forum for W3C Members and non-Members to discuss innovative Semantic Web applications. The group will focus primarily on applications of the W3C Semantic Web technologies (RDF, OWL, SPARQL, etc), on potential future work items related to technologies, and the relationship of that work to other activities of W3C and to the broader social and legal context in which the Web is situated.
The mission of the Web Accessibility Initiative Interest Group (WAI IG) is to provide a forum for review of deliverables under development by other WAI groups; for exploration of barriers to and potential solutions for accessibility of the Web; and for exchanging information about activities related to Web accessibility around the world.
The mission of the Web and Mobile Interest Group is to accelerate the development of Web technology so that it becomes a compelling platform for mobile applications and the obvious choice for cross platform development.
The mission of the Web and TV Interest Group, part of the Web and TV Activity, is to provide a forum for Web and TV technical discussions, to review existing work, as well as the relationship between services on the Web and TV services, and to identify requirements and potential solutions to ensure that the Web will function well with TV.
The mission of the Web of Things Interest Group, part of the Ubiquitous Web Applications Activity, is to accelerate the development of open markets of applications and services based upon the role of Web technologies for a combination of the Internet of Things (IoT) with the Web of data.
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.
The Data Activity Coordination Group serves as an advisory forum for the Data Activity. This group is designed to coordinate, facilitate and (where possible) direct the efforts of other related groups to avoid duplication of effort and fragmentation by way of incompatible standards and technologies. The Coordination Group does not create standards of its own.
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.
Learn more about Community and Business Groups.
In addition to these groups, W3C has chartered two permanent groups:
See also the list of past Incubator Groups.