About W3C GroupsA 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.[Submitter's Note: The mission statements have not been captured for all of the 337 Community Groups. Those for the rest of them can be viewed at https://www.w3.org/groups/cg/]World Wide Web ConsortiumW3C_ba25b042-92e3-4875-a5d5-389a1f54c910_5a594bde-fce8-11ea-a46f-2f432d83ea00To document the roles of W3C groups_5a594cec-fce8-11ea-a46f-2f432d83ea00DeliverablesProduce deliverables_5a594da0-fce8-11ea-a46f-2f432d83ea001W3C Working GroupsWorking Groups typically produce deliverables (e.g., standards track technical reports, software, test suites, and reviews of the deliverables of other groups)...There are currently 37 open Working Groups.Accessibility Education and Outreach Working Group (EOWG)The mission of the Accessibility Education and Outreach Working Group is to develop strategies and resources to promote awareness, understanding, implementation, and conformance testing for W3C accessibility standards; and to support the accessibility work of other W3C Groups.Accessibility Guidelines Working GroupThe 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.Accessible Platform Architectures Working GroupThe 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.Accessible Rich Internet Applications Working GroupThe mission of the Accessible Rich Internet Applications Working Group (ARIA WG, formerly part of the Protocols and Formats Working Group) is to develop technologies that enhance accessibility of web content for people with disabilities. This includes continued development of the Accessible Rich Internet Applications (WAI-ARIA) suite of technologies and other technical specifications when needed to bridge known gaps.Audio Working GroupThe mission of the Audio Working Group is to add advanced sound and music synthesis capabilities to the Open Web Platform.Automotive Working GroupThe mission of the Automotive Working Group is to develop Open Web Platform specifications for application developers, including but not limited to HTML5/JavaScript, enabling Web connectivity through in-vehicle infotainment systems and vehicle data access protocols. The API is agnostic with regard to the connection used.Browser Testing and Tools Working GroupThe 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.Cascading Style Sheets (CSS) Working GroupThe mission of the group is to develop and maintain CSS.Dataset Exchange Working GroupThe 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.Decentralized Identifier Working GroupThe mission of the Decentralized Identifier Working Group is to standardize the DID URI scheme, the data model and syntax of DID Documents, which contain information related to DIDs that enable the aforementioned initial use cases, and the requirements for DID Method specifications.Devices and Sensors Working GroupThe mission of the Device and Sensors Working Group is to create client-side APIs that enable the development of Web Applications that interact with device hardware, sensors, services and applications such as the camera, microphone, proximity sensors, native address books, calendars and native messaging applications.Distributed Tracing Working GroupThe mission of the Distributed Tracing is to define standards for interoperability between tracing tools.EPUB 3 Working GroupThe mission of the EPUB 3 Working Group is to maintain and develop the EPUB 3 family of specifications, to represent the EPUB community in the W3C, and to support EPUB 3 content creators and consumers by further advancing, refining, and clarifying the current EPUB 3 specification.GPU for the Web Working GroupThe 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.HTML Working GroupThe mission of the HTML Working Group is to give input to and bring the WHATWG HTML and DOM Review Drafts to W3C Recommendations.Immersive Web Working GroupThe mission of the Immersive Web Working Group is to help bring high-performance Virtual Reality (VR) and Augmented Reality (AR) (collectively known as XR) to the open Web via APIs to interact with XR devices and sensors in browsers.Internationalization Working GroupThe mission of the Internationalization 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 various different languages, scripts, regions, and cultures.JSON-LD Working GroupThe mission of the JSON-LD Working Group is to maintain the family of JSON-LD 1.1 Recommendations and related Working Group Notes.Media Working GroupThe mission of the Media Working Group is to develop and improve client-side media processing and playback features on the Web.Pointer Events Working GroupThe mission of the Pointer Events Working Group is to provide methods to enable simple device independent input from pointing devices such as mouse, pen, and multi-touch screen.Publishing Working GroupThe mission of the Publishing Working Group is to enable all publications—with all their specificities and traditions—to become first-class entities on the Web. The group will provide the necessary technologies on the Open Web Platform to make the combination of traditional publishing and the Web complete in terms of accessibility, usability, portability, distribution, archiving, offline access, and reliable cross referencing.Second Screen Working GroupThe mission of the Second Screen Working Group is to provide specifications that enable web pages to use secondary screens to display web content.Service Workers Working GroupThe mission of the Service Workers Working Group is to enable Web applications to take advantage of persistent background processing, including hooks to enable bootstrapping of web applications while offline.SVG Working GroupThe mission of the Scalable Vector Graphics (SVG) Working Group is to develop and maintain SVG.Timed Text Working GroupThe mission of the Timed Text Working Group is to develop W3C Recommendations for media online captioning by developing and maintaining new versions of the Timed Text Markup Language (TTML) and WebVTT (Web Video Text Tracks) based on implementation experience and interoperability feedback, and the creation of semantic mappings between those languages.Verifiable Credentials Working GroupThe mission of the Verifiable Credentials Working Group is to maintain the Verifiable Credentials Data Model specification and related Working Group Notes.Web Application Security Working GroupThe mission of the Web Application Security Working Group is to develop security and policy mechanisms to improve the security of Web Applications, and enable secure cross-site communication.Web Applications Working GroupThe mission of the Web Applications Working Group (WebApps WG) is to produce specifications that facilitate the development of client-side web applications.Web Authentication Working GroupThe mission of the Web Authentication Working Group, in the Security Activity is to define a client-side API providing strong authentication functionality to Web Applications.Web Fonts Working GroupThe mission of the Web Fonts Working Group is to develop specifications that allow the interoperable deployment of downloadable fonts on the Web.Web of Things Working GroupThe Web of Things seeks to counter the fragmentation of the IoT through standard complementing building blocks (e.g., metadata and APIs) that enable easy integration across IoT platforms and application domains.Web Payments Working GroupThe mission of the Web Payments Working Group is to make payments easier and more secure on the Web.Web Performance Working GroupThe mission of the Web Performance Working Group is to provide methods to measure aspects of application performance of user agent features and APIs.Web Platform Working GroupThe mission of the Web Platform Working Group is to continue the development of the HTML language and provide specifications that enable improved client-side application development on the Web, including application programming interfaces (APIs) for client-side development and markup vocabularies for describing and controlling client-side application behavior.Web Real-Time Communications Working GroupThe 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.WebAssembly Working GroupThe mission of the WebAssembly Working Group is to standardize a size- and load-time-efficient format and execution environment, allowing compilation to the web with consistent behavior across a variety of implementations.WebTransport Working GroupThe mission of the WebTransport Working Group is to develop APIs that enable data transfer between browsers and servers with support for multiple data flows, unidirectional data flows, out-of-order delivery, variable reliability and pluggable protocols.Working Groups are the heart of the W3C Process. The W3C Team spends a certain amount of resources reviewing Submissions, running Workshops, and otherwise tracking Web developments, which culminates in the process of re-allocating W3C resources:1. The Director announces the development of a proposal for one or more new Working Group charters.2. Advisory Committee representatives review the proposed charters.3. The Director announces a decision to approve the group(s) (or otherwise), as proposed or with modifications suggested by reviewers.Working Groups and Interest Groups produce Recommendations and other technical reports, and sample code.More information about the role of Working Groups can be found in the Process document._5a594e7c-fce8-11ea-a46f-2f432d83ea00Technologies & PoliciesBring together people who wish to evaluate potential Web technologies and policies._5a594f3a-fce8-11ea-a46f-2f432d83ea002W3C Interest GroupsThe primary goal of an Interest Group is to bring together people who wish to evaluate potential Web technologies and policies. An Interest Group is a forum for the exchange of ideas...There are currently 10 open Interest Groups.Chinese Web Interest GroupThe Chinese Web Interest Group provides a forum for W3C members to enhance the participation in Web standards work from the Chinese Web community.Internationalization Interest GroupThe 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.Media and Entertainment Interest GroupThe mission of the Media and Entertainment Interest Group is to provide a forum for media-related technical discussions to track progress of media features on the Web within W3C groups and use of Web technologies by external organizations, and to identify use cases and requirements that existing and/or new specifications need to meet to achieve a tighter support of media services on the Web.Patents and Standards Interest GroupThe 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.Privacy Interest GroupThe mission of the Privacy Interest Group is to improve privacy on the Web by advising groups developing standards on how to avoid and mitigate privacy issues with their technologies. PING also suggests changes to existing standards and technologies to improve the privacy of existing systems. Finally, PING makes recommendations to the W3C Advisory Committee and the W3C TAG about whether a proposed standard would be beneficial or harmful for privacy on the web.Spatial Data on the Web Interest GroupThe Spatial Data on the Web Interest Group develops and maintains vocabularies and best practices that encourage better sharing of spatial data on the Web; and identify areas where standards should be developed jointly by both W3C and OGC.WAI Interest GroupThe 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.Web & Networks Interest GroupThe mission of the Web & Networks Interest Group is to explore solutions for web applications to leverage network capabilities in order to achieve better performance and resources allocation, both on the device and network.Web of Things Interest GroupThe mission of the Web of Things Interest Group is to counter the fragmentation of the Internet of Things by introducing a Web-based abstraction layer capable of interconnecting existing Internet of Things platforms and complementing available standards. We aim to reduce costs through the global reach of Web standards, to enable open markets of services, and to unleash the power of the network effect. As a W3C Interest Group, we are seeking to build a shared understanding of the Web of Things, and to identify opportunities for initiating standards track work within W3C working groups. Liaisons between W3C, industry alliances and standards development organizations are already in discussion for two critical areas: semantic interoperability and end-to-end security across different platforms.Web Payment Security Interest GroupThe mission of the Web Payment Security Interest Group is to enhance the security and interoperability of Web payments. The group pursues its mission by creating a forum for organizations to define areas of collaboration and identify gaps between existing technical specifications in order to increase compatibility among different technologies.Interest Groups, like Working Groups, are the heart of the W3C Process. The W3C Team spends a certain amount of resources tracking Web developments, which culminates in the process of re-allocating W3C resources:1. The Director announces the development of a proposal for one or more new Interest Group charters.2. Advisory Committee representatives review the proposed charters.3. The Director announces a decision to approve the group(s) (or otherwise), as proposed or with modifications suggested by reviewers...Interest Groups do not publish Recommendation Track technical reports.More information about the role of Interest Groups can be found in the Process document._5a594fee-fce8-11ea-a46f-2f432d83ea00IdeasSocialize ideas for the Web at the W3C for possible future standardization. _5a5950ac-fce8-11ea-a46f-2f432d83ea003W3C Community GroupsCommunity Groups enable anyone to socialize their ideas for the Web at the W3C for possible future standardization...There are currently 337 open Community Groups.3D FOSS Web Development Community GroupAccessibility for Children Community GroupAccessibility in India Community GroupAccessible Infographics Community GroupAccessible Online Learning Community GroupAccessible Playlist Community GroupAccessible SVG Community GroupACT Rules Community GroupAdvancing Web Platform Application Testing Community GroupAfrican Developers Taking on the Web Community GroupAge Labels Data Model Community GroupAgriculture Community GroupAI KR (Artificial Intelligence Knowledge Representation) Community GroupThe 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.Algorithmic Modelling Community GroupAnnotation UX Community GroupAppsDesignLab Community GroupArgument Representation Community GroupArgumentation Community GroupARIA and Assistive Technologies Community GroupArt & Culture (Museums) On The Web Community GroupAtomic Data Community GroupAudio Community GroupAudio Description Community GroupAugmented Reality Community GroupAutomotive Ontology Community GroupBD Comics Manga Community GroupBenchmarking for the Web Community GroupAs web "applications" become more complex, it is felt that not only conformance but also performance of software is at issue. This is especially true for those on embedded systems such as mobile terminals. This CG will discuss how to assess performance characteristics of web browsers and web applications and how to provide a method of comparing the performance of various subsystems across different web systems. The group will deliver guidelines on these issues.Best Practices for Multilingual Linked Open Data Community GroupBibframe2Schema.org Community GroupBig Data Community GroupThis group will explore emerging BIG DATA pipelines and discuss the potential for developing standard architectures, Application Programming Interfaces (APIs), and languages that will improve interoperability, enable security, and lower the overall cost of BIG DATA solutions. The BIG DATA community group will also develop tools and methods that will enable: a) trust in BIG DATA solutions; b) standard techniques for operating on BIG DATA, and c) increased education and awareness of accuracy and uncertainties associated with applying emerging techniques to BIG DATA.Big Data Europe Community GroupThe group to discuss technical issues arising from the Big Data Europe Project.Bioschemas for lifesciences Community GroupBitcoin Hypermedia Community GroupBlockchain and Decentralized Apps Community GroupThe group's mission is to discuss and eventually create and propose Web Specifications for creating and using Decentralized app (Dapp) on a Blockchain. The groups primary activities will be to start discussions with regards to use cases of Dapps on blockchains and identify the issues that we have now. Eventually, the group will publish technical thought papers on Dapps and eventually produce deliverables like sample codes, use cases, proof of concepts, etc. in order for this community group to become a W3C Working Group to propose technical specifications related to creating and using Dapps on Blockchains. The ideal members that should join this group are those who has skills in Web standards and have interests in Blockchain technologies especially in the creation Dapps on Blockchains.Blockchain Community GroupThe mission of the the Blockchain Community Group is to generate message format standards of Blockchain based on ISO20022 and to generate guidelines for usage of storage including torrent, public blockchain, private blockchain, side chain and CDN. This group will study and evaluate new technologies related to blockchain, and use cases such as interbank communications.Blockchain Digital Assets Community GroupThe group's mission is to discuss and eventually create and propose Web Specifications for creating and using Digital Assets on a Blockchain. The groups primary activities will be to start discussions with regards to use cases of digital assets on blockchains and identify the issues that we have now. Eventually, the group will publish technical thought papers on Digital Assets on Blockchains and eventually produce deliverables like sample codes, use cases, proof of concepts, etc. in order for this community group to become a W3C Working Group to propose technical specifications related to creating and using Digital Assets on Blockchains. The ideal members that should join this group are those who has skills in Web standards and have interests in Blockchain technologies especially in the creation and using of digital assets on Blockchains.Brazilian Publishing Community GroupBridging GraphQL and RDF Community GroupBrowser Extension Community GroupProblem: There is no cross browser standard for building browser extensions, which requires developers to create extensions for each browser individually. Proposal/Mission: The Browser Extension group will attempt to standardize extension package structure, API, portability etc., across browsers.Browser Sync Community GroupThe major browsers provide users with a means of synchronizing their data across browser instances, but the services behind that synchronization process are not controlled by users, and users don't have the ability to sync the data of their choice, or sync with other browsers. Our goal is to create a specification for a browser sync process that gives users more control over their data, gives developers the ability to sync specific data for their web applications, and allows for a diverse marketplace of sync backend providers.Browsers and Robotics Community GroupBuilding Device Naming Standards Community GroupBullet Chatting Community GroupBusiness Data APIs and Interchange Community GroupToday, transmission of business data between software currently happens in the EDI format. This format is confusing, unreadable, and not publicly published. Many implementations are custom and involve high maintenance costs. The goal of this group is to define standards for transmission of various business data in a public, extensible, and humanly readable manner.Cartography Community Groupceddl html attribute-based markup and javascript api Community GroupA lightweigt html attribute-based markup and javascript api you used for surfacing digital data on a web application intended for web analytics, website personalization and DMP implementations. Applying lessons learnt by many implementations of Customer Experience Digital Data Layer (CEDDL) and bringing this back into a specification for the browser.Chainpoint Community GroupThe mission of this group is to establish a standard for creating a universally verifiable proof of any data, file, or series of events, by anchoring data to the blockchain and other sources. This allows anyone to prove the data existed at a point in time and has not been modified.The group will publish and formalize the Chainpoint specification as a stable reference, maintain a test suite, and take feedback and use cases for the future evolution for the specification.The Chainpoint Community Group will coordinate with the Blockchain Community Group for general standardization of blockchain-related technology, and will operate according to the Chainpoint CG charter. You can read more about Chainpoint, its history, and goals, on our recent blog post announcing Chainpoint 2.0.This group invites participants who are actively developing and deploying proof-of-existence, timestamping, and data integrity solutions, who are skilled in blockchain technologies, and who can work on use cases for Chainpoint and related technologies.Change Tracking Markup Community GroupThe mission of this group is to develop a proto-spec for marking up changes to documents.Character Description Language Community GroupChemistry for the Web and Publishing Community GroupChinese Digital Publishing Community GroupChinese Web Accessibility Community GroupClient and Server JavaScript APIs Community GroupCloud Computing Community GroupCognitive AI Community GroupThe 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* 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 GroupCollaborative Software Community GroupThe mission of the Collaborative Software Community Group is to provide a forum for experts in collaborative software and groupware for technical discussions, gathering use cases and requirements to align the existing formats, software, platforms, systems and technologies (e.g. wiki technology) with those used by the Open Web Platform. The goal is to ensure that the requirements of collaborative technology and groupware can be answered, when in scope, by the Recommendations published by W3C. This group is chartered to publish documents when doing so can enhance collaborative technology and groupware. The goal is to cooperate with relevant groups and to publish documents to ensure that the requirements of the collaborative software and groupware community are met.Color on the Web Community GroupColour blindness accessibility Community GroupCommunity CouncilThe 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.Community I/O Community GroupThis group will focus on applying current information technologies to create a foundation of infrastructure for organizing the flow of resources and support with services within human community. All peers (individuals or projects) can state their needs (input) and offers (output). Using Semantic Web, Federated Social Web and other related technologies people can develop various approaches of connecting those needs and offers. Including variants with and without use of currencies.Consent on the Web Community GroupThe mission of this group is to improve the experience of consent on the web 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 issues and problems about consent on the web (iii) propose and develop solutions. Some concrete areas for the working of this group are: (a) developing solutions using legal, or technical, or a combination of both; (b) documenting and achieving legal compliance; (c) improving the user experience; and (d) utilising existing and developing new web standards for consent.Content Blocking Community GroupConversational Interfaces Community GroupCoVid-19 Remote Meet, Work, Class Community GroupCredentials Community GroupCredible Web Community GroupThe 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.Croatian Web Developers Community GroupCryptoledgers Community GroupCSS Accessibility Community GroupCSS Print Community GroupCSS Selectors as Fragment Identifiers Community GroupCSS4 Community GroupCSV on the Web Community GroupCustomer Experience Digital Data Community GroupData Driven Standards Community GroupThe Data Driven Standards Community Group focuses on researching, analyzing and publicly documenting current usage patterns on the Internet. Inspired by the Microformats Process, the goal of this group is to enlighten standards development with real-world data. This group will collect and report data from large Web crawls, produce detailed reports on protocol usage across the Internet, document yearly changes in usage patterns and promote findings that demonstrate that the current direction of a particular specification should be changed based on publicly available data. All data, research, and analysis will be made publicly available to ensure the scientific rigor of the findings. The group will be a collection of search engine companies, academic researchers, hobbyists, protocol designers and specification editors in search of data that will guide the Internet toward a brighter future.Data on the Web Best Practices Community GroupThis group will continue the work started by the Data on the Web Best Practices Working Group in investigating topics such as data versioning, subsetting, data access and metadata. It will promote discussions about Data on the Web challenges and best practices, evaluating its benefits and any drawbacks. In so doing, the CG will collect new evidence of the DWBP implementation around the world and offer additional material that will help the adoption of the DWBP. Needs for further standardization will be identified.Data Pipelining Use Cases Community GroupData Privacy Vocabularies and Controls Community GroupData Visualization Community GroupDataSheets Community GroupDecoupling content and data from HTML, by providing a DataSheet Language (CSS-like) to source, store and apply data to the HTML DOM. The browser will be able to take the responsibility of retrieving the data from a variety of sources and rendering it. The group will outline the language and the full specifications for making this a reality.Decentralized Communications Community GroupThe mission of this group is to specify and build a reference implementation of Decentralized Communications. Decentralized Communications enables natively inter-operable communication services that are able to trustfully use peer to peer connections without having to use central authorities or services. Decentralized Comms are inherently inter-operable without using standard protocols by using the Protocol on-the-fly concept, where the most appropriate protocol stack to be used, is selected and instantiated at run-time.Decentralized Identity Korean Community GroupDecentralized Sharing Community GroupThe goal is to work on interoperable sharing between decentralized platforms. The idea is not to design the perfect protocol but find a consensus that would lead to an interoperable data exchange with sync capabilities, access control, discovery, etc.Decisions and Decision-Making Community GroupThe group will discuss and tentatively specify a format for representing decisions, i.e. decision information, so they can be used across diverse systems. Because of the great variety of applications and decision technologies, this format should focus on the generic, core components of decisions and decision-making information. Decisions are a source of information in themselves, i.e. each decision that is made is in itself a piece of information the may need to be stored, tracked, shared, combined and compared to other decisions. The same holds for information about the decision process. In particular, this group will discuss and study how Semantic Web technologies can facilitate the representation and sharing of decision information. Ultimately, the aim of the group is to study and develop technologies and methods to support better, rapid, and agile decision making.Declarative 3D for the Web Architecture Community GroupDeclarative Linked Data Apps Community GroupThe mission of this group is to produce a specification that describes how Web and Linked Data applications can be built using declarative technologies only, minimizing the need for source code. Current software development models involve writing source code (mostly in imperative languages) and building programs from it. Source code is prone to bugs, and managing it requires developers. The declarative approach is instead to push as much application logic from source code to data, so that the application can be managed and reused as data itself, while the software become generic and application-independent. This approach is related to functional languages and to processing pipelines. The generic software works as a processor: it takes the incoming request and the declarative application description and runs it through a pipeline, first retrieving the state of the requested resource (or changing it) and then rendering it into the requested format, such as a Web page. This is similar to an XSLT processor transforming XML documents. Graphity is a production-level platform for declarative end-user Linked Data applications with an RDF triplestore backend. It processes ontologies describing application structure, which seemlesly combine multiple declarative technolgies: URI templates, SPIN SPARQL templates, XSLT stylesheets (both server- and client-side), and RDF/POST encoding. Please join this group if you're interested in any practical or theoretical aspects of Linked Data, declarative technologies, or Graphity software.Declarative WebVR Community GroupDesign Tokens Community GroupDevelopment Linked Data Community GroupData is commonly considered as a new kind of fuel powering economical, cultural and societal changes. From e-governance to smart cities, many examples can be found to argue for the value of open and connected data. By turning the Web into a data publishing platform Linked Data is a key enabling technology for this. It has yet to be kept in mind that as of 2012 65% of the world does not have access to the Web and are thus deprived from Linked Data. Furthermore is this population sorely in need for the changes data-driven societies benefit from. This community group is there to discuss some important questions such as: * How can development related data be published as Linked Data? * What kind of data is out there and what is relevant to drive societal changes in underprivileged countries? * How can those without Web access can consume open data set published as Linked Open Data? * How can the Linked Data principles be revised to be applicable in Web-less contexts? This group will not publish Specifications.Digital Asset Management Industry Business Ontology Community GroupDigital Identity Community GroupThe mission of the W3C Digital Identity Community Group is to identify and resolve real world identity issues, to explore and build a more secure trusted digital identity ecosystem on internet for people, organizations and things fully controlling, protecting and expressing their identity. Our work focuses on the ecosystem's scalability, interoperability, mobility, security and privacy. We intend to integrate interoperable identity solutions, systems and networks in our ecosystem.Digital ssset standard Community GroupDistributed Compute Protocol Community GroupDistributed Tasks Community GroupCommon ground for people developing various collaboration software with notion of "tasks." Aiming for increasing interoperability across all such software and improving experience of a person contributing to big number of projects. Emphasis on interoperability, portability and extensibility!Distributed User Interfaces Community GroupDo-Not-Track Community GroupE-learning: Evolving technologies and growing reach Community GroupEducational and Occupational Credentials in schema.org Community GroupEducational Exercises and Activities Community GroupEfficient Extensible Interchange Community GroupElectronic Governance (eGov) Community GroupThe mission of the Electronic Governance Community Group (formerly W3C e-Government Interest Group) is to build and strengthen the community of people who actively develop, use or promote the use of W3C technologies to improve the working of government (Electronic Government) and its interactions with citizens, businesses, civil society and other arms of government (Electronic Governance). As a part of its activities, the Group will identify and discuss essential areas of technology, organizational and social change, and related policy issues. Such areas include but are not limited to: access and accessibility; cloud computing; data licensing; education and outreach; government as a platform; interoperability; information sharing; innovation and innovation transfer; impact, public value and economic evaluation; knowledge management; mobile government; open government; privacy, security and sensitive data; standardization versus adaptation; transparency and accountability; whole-of-government; and others. The discussions will occur, among other places, on the Group's mailing list, in teleconference seminars, and at face-to-face gatherings. On the topics with sufficient interest and motivated participants, the group will form task forces to produce technical documents and policy recommendations, reach out to relevant communities, and even encourage the formation of specialized EGOV-related community groups.Emergency Information Community GroupEnterprise Ethereum Community GroupEntity Reconciliation Community GroupEPUB 3 Community GroupETL Markup Language Community GroupEXPath Community GroupThe mission of this group is to lead to extension of XPath and all related technologies (XSLT, XQuery, XProc, XForms, XML Schema).Experience API (xAPI) Vocabulary & Semantic Interoperability Community Groupexperimental protocols Community GroupExploration of Semantic Data Community GroupExposing and Linking Cultural Heritage data Community GroupExposing IEEE LOM metadata as Linked Data Community GroupExtensible Data Model Declaration Language for Education Community GroupXDMDL is proposed as a high level schema language that will allow people to define, share, combine, reference and profile data models. The proposal has grown out of a requirement recognised within the education community working in the SCORM and xAPI traditions, and it is intended to pilot the specification by demonstrating how it can help improve data interoperability between software systems designed to manage and deliver learning activities.Extensible Web Community GroupThe Extensible Web Community Group is an incubator for web technologies enabling authors to extends the native web technologies via scripting (ie: shims & polyfills).Federated Commerce Community GroupDecentralized e-commerce and storefront apps will more easily share and syndicate their products rather than relying on single and proprietary APIs from hosts to operate a storefront. By structuring portable commerce data stores, protocols, and semantics, this group seeks to enable marketplaces to be built more eaily and made more easily discoverable.This group's efforts will complement existing activities such as Web Payments, Linked Data, and DID, to deliver a search, browse, configure, checkout, and payment workflow for physical and digital products with mostly existing web technologies.At a higher-level, it would be potentially beneficial to include support for an aggregate query language, (such as SPARQL) to enable applications to query a known network of compatible applications for product information to better support web resource-to-web resource indexing and listing of products, increasing visibility without the need for central search engines. This would potentially utilize HTTP methods to register product catalogs in other web apps or request product catalogs from other web apps, enabling products to be purchased outside of the scope of the original commerce site, creating an aggregate marketing power across the web rather than depending on singular, monolithic e-commerce platforms.Federated Identities for the Open Web Community GroupThe mission of this group is to propose new APIs that allow for secure identity federation across domains on the open web.Federated Infrastructures Community GroupThe mission of this group is to create a set of upper ontologies to describe federated infrastructures and their resources. The ontologies will support a number of use cases to semantically manage the whole life cycle of a resource: discovery, selection, reservation, provisioning, monitoring, control, termination, authentication, authorization, and trustworthiness.Film Industry Community GroupFinancial Industry Business Ontology Community GroupFont and Text Community GroupFunctional Knowledge Graph Community GroupGames Community GroupGeospatial Semantic Web Community GroupGetting Math onto Web Pages Community GroupGPU for the Web Community GroupHaptic Interaction on the Web Community GroupHardware Based Secure Services Community GroupHealthcare Schema Vocabulary Community GroupHigh-Performance Computing Community GroupHTML Editing APIs Community GroupHTML for email Community GroupHTML Tidy Advocacy Community GroupHTML5 Japanese Community GroupHTML5 Korean Community GroupHTML5 Specifications Community GroupHTTPS in Local Network Community GroupHuman Services Community GroupHydra Community GroupImmersive Captions Community GroupImmersive Web Community GroupInclusion and Diversity Community GroupInclusive Design for the Immersive Web Community GroupInformation Architecture Community GroupThe mission of this group is to discuss, and share matters relating to the profession of Information Architecture. Help us spread awareness of Information Architecture and connect with other Information Architecture pros globally and locally. This group will not produce specifications.Interactive APIs Community GroupInterledger Payments Community GroupInterlinear Text Layout Community GroupJSON for Linking Data Community GroupKnowledge Domain Community GroupExploring effective architectural and best practices support for publishing content on, and author content for the web effectively expressing knowledge domain specific content according to standard practices in that knowledge domain discipline. By knowledge domain we mean such human disciplines as mathematics, physics, chemistry and other STEM disciplines. We also include disciplines such as music, economics, history and linguistics. We are particularly interested in disciplines that convey knowledge using discipline specific symbology which cannot currently gain effective communication through HTML. We further include domain specific markup systems as well as graphical representation such as SVG rendering.This group may publish Specifications.Knowledge Graph Construction Community GroupThe overall goal of this community group is to support its participants into developing better methods for Knowledge Graphs construction. The Community Group will (i) study current Knowledge Graph construction methods and implementations, (ii) identify the corresponding requirements and issues that hinter broader Knowledge Graph construction, (iii) discuss use cases, (iv) formulate guidelines, best practices and test cases for Knowledge Graph construction, (v) develop methods, resources and tools for evaluating Knowledge Graphs construction, and in general (vi) continue the development of the W3C-recommended R2RML language beyond relational databases. The proposed Community Group could be instrumental to advance research, increase the level of education and awareness and enable learning and participation with respect to Knowledge Graph construction.Law and Technology Community GroupThe mission of the Law and Technology Community Group is to serve as a place for legal professionals and those interested in the law to share information on how current laws affect the implementation of new web technologies as well as how those new technologies can affect the law.LDP Next Community GroupLDP Next aims to continue the work started by the LDP Working Group. LDP Next hopes to address the following topics that were not covered by LDP 1.0: (1) extensibility and discovery — allow clients to easily discover server affordances; (2) inlining on GET and POST — allow clients to request and create multiple resource with a single HTTP request; (3) query / search over LDPCs and LDPRs; (4) access control — provide a mechanism to control access to Linked Data Platform Resources.Linked Building Data Community GroupLinked Data for Accessibility Community GroupLinked Data for Language Technology Community GroupLinked Data Models for Emotion and Sentiment Analysis Community GroupLocations and Addresses Community GroupMachine Learning for the Web Community GroupThe mission of the Machine Learning for the Web Community Group (WebML CG) is to make Machine Learning a first-class web citizen by incubating and developing a dedicated low-level Web API for machine learning inference in the browser. Please see the charter for more information. The group invites browser engine developers, hardware vendors, web application developers, and the broader web community with interest in Machine Learning to participate.Machine Learning Schema Community GroupThis group represents a collaborative, community effort with a mission to develop, maintain, and promote standard schemas for data mining and machine learning algorithms, datasets, and experiments. Our target is a community agreed schema as a basis for ontology development projects, markup languages and data exchange standards; and an extension model for the schema in the area of data mining and machine learning. The goals of this group are: To define a simple shared schema of data mining/ machine learning (DM/ML) algorithms, datasets, and experiments that may be used in many different formats: XML, RDF, OWL, spreadsheet tables. Collect use cases from the academic community and industry Use this schema as a basis to align existing DM/ML ontologies and develop more specific ontologies with specific purposes/applications Prevent a proliferation of incompatible DM/ML ontologies Turn machine learning algorithms and results into linked open data Promote the use of this schema, including involving stakeholders like ML tool developers Apply for funding (e.g. EU COST, UK Research Councils, Horizon2020 Coordination and Support Actions) to organize workshops, and for disseminationMaps For HTML Community GroupMathML Refresh Community GroupMeat Products Community GroupMedia Delivery Community GroupMedia Resource In-band Tracks Community GroupMerging of Web and Mobile APP Community GroupMFX Media Community GroupMicroposts Community GroupMicroXML Community GroupMiniApps Ecosystem Community GroupMixed Reality Service Community GroupMobile Accessibility Community GroupMobile Web in Indian Languages Community GroupMulti Markup Community GroupWeb Service specifications and vocabularies are faced with the challenge of providing dual (or more) normative (or alternative) markups for their specifications or vocabularies. For example it is becoming common to require both an XML and JSON normative markup for documents and messages. This group will discuss options and propose practices for authoring and maintaining specifications and vocabularies in multiple markups. This may include, but not limited to, authoring in a 'meta markup' or automatic translation between markup formats.Multi-device Timing Community GroupMultidimensional Quality Metrics (MQM) Community GroupMultilingual Web Sites Community GroupMusic Notation Community GroupNative Web Apps Community GroupNetwork Maintenance Notifications Community GroupNetwork-Friendly App and WebApp Best Practices Community GroupNetworked Data Community GroupThe recent years have shown the need to deal with networked data in large-scale, distributed settings. Not only must the systems be scalable, elastic and performant, but also address *ability (usability, manageability, etc.). One key component is doing it the webby way. The Web is the leading concrete exemplar of RESTful design, being the result of posthumous analysis of what was already working with URIs, HTTP and HTML for a system of interlinked documents. Unfortunately the machine equivalent of HTML is still emerging. LinkedData has achieved some powerful results; automated navigation by querying the Linked Open Data cloud shows some of the potential. However many systems also need to evolve and be evolved. This can be expressed as 'service capability' and also needs to be supported with consistency. This should aim to eliminate the wide range of non-interoperable approaches muddling the current landscape of REST APIs through exploiting hypermedia concepts. The Networked Data Community Group aims to provide a forum for collecting use cases including but not limited to the fields of science data (such as biology, astronomy, etc.), economics data (financial markets, etc.), health care, configuration and systems management, Green IT, and smart infrastructures (cities, etc.). Based on the collection of use cases the CG will derive requirements and write up best practices for dealing with the dynamics of the data.Notation 3 (N3) Community GroupODRL Community GroupOFF/X Community GroupOntology-Lexica Community GroupOpen and Interactive Widgets for STEM Community GroupOpen Annotation Community GroupOpen Data Directory Community GroupThe Open Data Directory lists products, services and research projects that leverage Linked Data. Currently, the Directory serves as an aggregator of use cases and web sites using Linked Data and is expected to evolve over time in response user requirements. The Directory is a community service project to foster ease-of-use and awareness of Open Data on the Web. The Directory has an easy to use Web interface enabling users to list: - Organization name - Contact name - Product(s) - Service(s) - Projects & Use Cases The Open Data Directory periodically gathers Linked Data from designated sites and compiles it into a summarized view of the community. It is a purely Linked Data application and not another "walled garden." Organizations are responsible for publishing their own Linked Data for the Directory to consume. The Open Data Directory includes some basic visualizations that are expected to expand over time. The site is built on open Web standards and an Open Source data platform hosted on the cloud. All of the data is freely available for download as RDF. The Open Data Directory is open and does not require W3C affiliation.Open Data Nepal Community GroupOpen Data Spain Community GroupOpen Educational Resources Schema Community GroupOpen Government Community GroupThis group's mission is to discuss and prepare data and API specifications relating to open government information, which may include: * people, such as legislators * organizations, such as legislatures or committees * people's positions within organizations * areas, such as electoral districts * events, such as elections * documents, such as bills or agendas * speeches, such as those given by legislators in legislatures * votes The group will base its work on existing standards as much as possible, and re-use existing terms (classes and properties) wherever appropriate. The group may define various serializations of the specifications, including but not limited to RDF and JSON. The group will seek consensus around, and support for, these specifications which may then be brought to an appropriate Working Group to advance a specification from draft to standard. The group will coordinate as appropriate with the Web Schemas Task Force of the Semantic Web Interest Group and other relevant groups within the W3C.Open knowledge-driven service-oriented system architectures and APIs (KiSS) Community GroupW3C provide a great variety of standards that can be used to build applications that use the Internet as a platform for communication and integration. The open Knowledge-driven Service-oriented System architectures and APIs (KiSS) community group is created for sharing, elaborating and evolving knowledge-driven approaches for system integration. The KiSS community group takes service-oriented architecture as a main paradigm for application creation. However, it is not enough to say that there is a set of some services that can be integrated according to the application needs. The integration is facilitated with semantic descriptions of the services. Furthermore, the special support components are required at system run time in order to allow dynamic composition of the services accordingly semantic representation of adjusted or new system goals. Thus, the community aims to categorise different possible architectures to allow knowledge-driven approach for system integration; it provides reference architectures that also point out possible technologies for the solution implementation. The community targets different application domains and industries in order to benefit from cross-domain vision on development of knowledge-driven systems. The abbreviation of the community group highlights the integrative nature of the group (small i among K (knowledge), S (service) and S (system)). The group is managed by 6 re-electable chairs.Open Linked Education Community GroupOpen Science Community GroupOpen Science has considered as a alternative of the entire research cycle to improve sustainable value of science. This group's goal is to develop various resource including documents and sources based on an existing knowledge (e.g. open access, open data, open source, etc.) for motivating and smooth landing on doing the open science. As a alternative of a existing scientific paradigm, this group is to introduce a general and standard filed guide for Open Science Research Cycle, to generate a logical alternative for conflict concern for open science, to provide a framework(or IDE) to implement the open science paradigm, and to develop meta data using existing knowledge (e.g. ontology, semantic web, machine learning)Open UI Community GroupOpenActive Community GroupOpenTrack Community GroupORTC (Object Real-time Communications) Community GroupOWL: Experiences and Directions Community GroupPDF and Open Data Community GroupPerforming Arts Information Representation Community GroupPermanent Identifier Community GroupPhilosophy of the Web Community GroupMany philosophical issues have arisen in the technical design of Web standards over the years. Philosophical conundrums sometimes seem out of context in the light of seemingly more pressing technical problems. Yet, the very fact that these philosophical problems are constantly raised indicates that they are not easily dispensed with, but should instead be the focus of serious and ongoing long-term discussions. This is why this CG aims at undertaking such discussions, even outsourcing them to alleviate the task of other groups. To clarify the goal of this CG: it should not be a place to do unconstrained philosophical research but rather a forum to examine issues arising from the W3C technical community. Open discussion and precise descriptions of the minutiae of the Web will help guide the work in the CG, which should output short guides on precise topics to help case progress and discussions in other groups. The PhiloWeb Community group aims to undertake such discussions by bringing together experts from the web and the philosophical community to help the task of "philosophical engineering", a term coined by Tim Berners-Lee.Physical Ledger Community GroupPlaces Community GroupPositive Work Environment Community GroupPrint and Page Layout Community GroupPrivacy Community GroupPrivate User Agent Community GroupProperty Graphs Model and API Community GroupPublications Object Model Community GroupPublishing Community GroupQuick-fix support for XML Community GroupSometimes an error reported against an XML document can be fixed automatically, for example if the error refers to an unexpected attribute then an automatic fix will be to delete that unexpected attribute. We want to explore the issues related to applying quick fixes (like preserving DOCTYPE declarations, entities, etc.) and determine what actions will be needed be able to apply quick fixes on a document as well as a representation language to describe these actions. Quick fixes are especially interesting when we use Schematron for XML validation, as in this case the quick-fix should be specified by the schema author, so we have user-defined quick fixes. Imagine for example a business rule implemented in Schematron that says that a list should contain between 4 and 8 items. If we determine that there are two items then a quick fix will propose to add automatically two more items to the list or if the list has 10 items then a quick fix may propose to delete two items or to split the list in two lists, etc.RDF and XML Interoperability Community GroupThe goal of this group is to 1) identify application areas in which the combined processing of XML and RDF data and tooling is beneficial; 2) identify issues that hinder the joint usage of the two technology stacks 3) formulate best practices to resolve the issues or propose standardization topics. The goal does not only take into account the data representation formats XML and RDF, but all related technologies (e.g. for XML: XSLT, XQuery; for RDF: RDF Schema, SPARQL) and selected XML (e.g. OData) or RDF vocabularies. The group should be driven by needs of industries that already deploy one or both technology stacks. This will also cover adjacent technologies like JSON with respect to the topics covered in this group. The outcome should focus not on a big architecture of how to work with XML and RDF, but on small building blocks (as best practices or standardization topics) that can be re-used across industries and application scenarios.RDF JavaScript Libraries Community GroupRDF Stream Processing Community GroupRDF Test Suite Curation Community GroupRDF-DEV Community GroupRead Write Web Community GroupThe activity of this group is to apply Web standards to trusted read and write operations.Research Object for Scholarly Communication Community GroupResponsive Issues Community GroupRestaurant Ontology Community GroupRestricted Media Community GroupRevising W3C Process Community GroupRights Automation for Market Data Community GroupRobustness and Archiving Community GroupSchema Architypes Community GroupSchema Bib Extend Community GroupSchema Course extension Community GroupSchema Extensions for IoT Community GroupSchema Generator Community GroupSchema.org Community GroupSchema.org for datasets Community GroupScholarly HTML Community GroupScript Library Community GroupSDshare Community GroupSecond Screen Community GroupSemantic Industries Community GroupSemantic News Community GroupSemantic Open Data Community GroupSemantic Sensor Networks Community GroupSemantic Statistics Community GroupSemantic Web in Health Care and Life Sciences Community GroupSHACL Community GroupShape Expressions Community GroupSilver Community GroupSKOS and OWL for Interoperabilty Community GroupBased on our #SDSVoc bar camp session we would like to discuss best practices for using SKOS and OWL for interoperabilitySmart Contracts Community GroupSmart Manufacturing Community GroupSmart Phone Application Developer Community GroupSocial Economy Community GroupIn this group we work on various web technologies needed for managing all kinds of economic relationships between individuals and organizations. While recognizing nowadays dominance of commerce, we take here more general approach which gives equal attention to all kind of non-commercial approaches, including Social Economy, Sharing/Collaborative Economy, Solidarity Economy, Informal Economy etc.Social Web Incubator Community GroupThe purpose of the Social Web Incubator Community Group is to continue and extend the development of vocabularies, formats and protocols to support the distributed / federated social web, as well as related technologies (such as anti-abuse and anti-spam techniques suitable for an open web). This group continues the work of the W3C Social Web Working Group. As proposals gain support and become more stable and mature, they will be considered for migration to a W3C Working Group where they can be put on the Recommendation track with appropriate status and Intellectual Property (IP) considerations.Solid Community GroupThe Solid project aims to improve privacy and data ownership on the Web through a proposed set of conventions and tools for building decentralized social applications.The mission of the Solid Community Group is to try to reshape the web by fostering a new breed of applications with capabilities above and beyond anything that exists today. Participants in this group will create applications, author technical specifications, and capture best practices.Participants in this group who contribute to the Solid code base should also review the guidelines and best practices for contributing to the Solid project.This group will publish Specifications.SPARQL 1.2 Community GroupThe SPARQL 1.2 Community Group is a forum for discussion and refinement of SPARQL 1.1. It will document features found as extensions to available triple stores and also document common needs from the user community. The CG aims to create consensus and understanding of the impact of new features with special emphasis on features that leave existing SPARQL 1.1 queries and systems unchanged. The CG will build a collection of such features leading to a CG report on use cases and requirements.SPARQL Maintenance (EXISTS) Community GroupThe "SPARQL Maintenance (EXISTS)" Community Group is a forum to discuss and address problems with the "EXISTS" feature in SPARQL 1.1. The SPARQL 1.1 suite of specifications and the SPARQL 1.1 test suite are frozen. A process exists to record errata and that will be one input to any working group chartered to revise SPARQL. In the meantime, SPARQL is being used in real-work systems in industry and public-sector. The user community expects a high degree of conformance across implementations. The EXISTS feature has been found to be problematic. This feature is used by the RDF Data Shapes Working Group. This community group will create CG Notes and accompanying test suites to describe one or more improvements with an emphasis on maintaining compatibility. This group is not producing specifications. Any tests produced by the will submitted to the RDF Test Suite Curation CG for long-term stewardship.Speech API Community GroupSport Schema Community GroupStereoscopic 3D Web Community GroupStroke Fonts Community GroupSustainable Web Design Community GroupA community group dedicated to creating sustainable websites. This group will not publish specifications.SVG Community GroupSVG glyphs for OpenType Community GroupSVG Mapping Community GroupSVG Streaming Community Groupsvg-zh Community GroupSynchronized Multimedia for Publications Community Groupsyndicated.media Community GroupSynthetic Media Community GroupTalent Marketplace Signaling Community GroupTechnical Architecture Community GroupThis group is an open forum for discussing Web architecture, such as that discussed by the W3C Technical Architecture Group (TAG). Web architecture refers to the underlying principles that should be adhered to by Web components (APIs/Markup), whether developed inside or outside W3C. The architecture captures principles that affect such things as understandability, interoperability, scalability, accessibility, and internationalization. We expect to have a strong working relationship with the W3C TAG.Technical Documentation in the Semantic Web Community GroupThe complexity of machines and software has grown dramatically in the past years. The technical documentation became a fundamental source for service technicians and professionals in their daily work. Fast and focused access methods are necessary to handle massive volumes of technical documents. Semantic technologies have proven their ability to improve accessibility of information (see Linked Open Data). However, existing corpora of technical documents are usually not semantically prepared. This group shall focus on applying semantic technologies to technical documentation. All peers (individuals or projects) can state their needs (input) and offers (output).The Tourism Structured Web Data Community GroupThe mission of this group is to discuss and prepare proposals, examples, and best practice guidance for the sharing, via the web, structured data descriptions of resources associated with the tourism industry. Initial focus will be on extending Schema.org schemas for the improved representation of tourism related information markup and sharing. The group will seek consensus around, and support for, proposal(s) to be made to the Schema.org community.The Unitive Web Community GroupCurrently, there is a growing movement from the independence of the web, towards dominant companies. These companies offer organized information, but this comes at a price. We lose our independence more and more. The Unitive Web is a proposal to have both organized information and independence. It offers one generic approach closely compatible with the current web, which makes it possible to create a global open virtual space of information which is responsive and reliable. It offers open customization of user interaction, open bottom-up schema mapping, integration of (AI) algorithms, and facilitates in the protection of privacy. The aim of this group is to discuss any aspect of it and share specifications.Timed Text Community GroupTNS Blockchain Community GroupTouch Events Community GroupTraffic Event Ontology Community GroupTrust & Permissions Community GroupTV Control API Community GroupUbiquitous Application Design Community GroupUnhosted Web Community GroupUniversal Images Community GroupUser Identity on the Web Community GroupUser Interaction and Experience Community GroupVeres One Community GroupVideo Game Schema Community GroupVirtual Reality website and Metaverse Community GroupVIVO Open Research Networking Community GroupVocabularies for big data analysis Community GroupThis group discusses semantic ontologies for the Big Data space. It is supported initially by the H2020 Big Data Europe project. The mission of this group is to cooperate, discuss and agree on semantic vocabularies to support applications in the domain of big data processing. It is a conscious choice to initiate one forum to discuss and agree on various new vocabularies and/or their amendments. With this one group we hope to reach a broader public. The different ontologies have a common aim: describe tools such that they can be reused in semantic empowered applications for big data processing. At launch this will include ontologies for the Docker ecosystem and for Har-files. The former is used for setting up stacks in the Big Data Europe project, the latter for analysing HTTP requests.Voice Assistant Standardisation Community GroupVoice Interaction Community GroupVoiceXML Community GroupThe mission of this group is to bring together voice application developers interested in VoiceXML. This group will not produce specifications, but will discuss use cases that may be recommended to the VoiceXML Working Group. Of particular interest will be use of VoiceXML for mobile applications.Volunteering Ontology Community GroupThe Volunteering Ontology group seeks to provide the volunteering community with a shared vocabulary for the open exchange of data relating to volunteering. Entities of interest include volunteering opportunities, the organizations hosting those opportunities, and the volunteers themselves.Voter Decision Support Community GroupThis community group discusses voter decision support systems and related topics. This community group shall advance the theory and practice of decision-making software and decision support systems for use by citizens during voting-related and civic participation activities. This community group shall advance the theory and practice of voter-centric design, empowering and equipping citizens. This community group may draft suggestions and best practices and may coordinate with other groups to support pertinent standards.W3C Developer Relations Community GroupDevelopers and designers form an important audience for W3C standards, but the standards process itself is not an ideal way to engage with them. W3C has made strides in terms of developer relations in recent years, through W3Conf, Web Education XG and CG, easy access to W3C through community groups, more documentation, and online training. More can be done to reach more people and better reflect their interests in W3C. Initial ideas: * Create a developer relations activity or domain, to coordinate and explore different ways to directly engage with developers and designers, to gain early feedback on our specifications. * Make W3C a home for more useful documentation, demos, etc. * Support developer advocacy, in which ideas, use cases, and requirements for features or specification fixes are collected in detail from developers and designers, and presented to the appropriate W3C Groups. * Liaise with Members' developer relations departments on projects of mutual benefit. This group will not publish Specifications.WAI-Engage: Web Accessibility Community GroupWearable Web Community GroupWeb App Source Code Protection Community GroupWeb Application Store Community GroupWeb Archivability Community GroupWeb Archivability is interested in proposing best practices that help the web developers and designers in building web site that can be easily captured, preserved, and replayed using the web archiving tools.Web Audio Developers Community GroupWeb Bluetooth Community GroupWeb Certificate API Community GroupWeb Copyright Community GroupWeb Crypto API Community GroupWeb Dev Data Community GroupThis group intends to analyse web development data from around the world and publish monthly reports. By leveraging open source tools, we hope to create an open source project to do this. This group does not plan to publish specifications that require patent commitments.Web Education Community GroupWeb fights covid19 Community GroupWeb History Community GroupThis group gathers people interested in the history of the World Wide Web: how it was invented, what was out there that made it possible, and what happened in its early years. Our main goal is to collect and preserve valuable information (software, documents, testimonials) before it is lost. This group will not produce specifications.Web Media API Community GroupWeb Media Text Tracks Community GroupWeb NFC Community GroupWeb Observatory Community GroupWeb of Sensors Community GroupWeb of Things Community GroupThe aim of the Web of Things Community Group (CG) is to accelerate the adoption of Web technologies as a basis for enabling services for the combination of the Internet of Things with rich descriptions of things and the context in which they are used.Web Payments and Commerce Accessibility Community GroupWeb Payments Community GroupWeb Performance Community GroupThe goal of the Web Performance is to produce a general guideline to help people who work in the web field increasing their websites' performances. From the server abilities and rapidity to the analysis of the website's code (whatever would the markup language be), we try to help web designers making faster websites.Web Platform Incubator Community GroupThe Web Platform Incubator Community Group (WICG) provides a lightweight venue for proposing and discussing new web platform features.Web Skill Profiles Community GroupWeb Thing Protocol Community GroupWeb Video Map Tracks (WebVMT) Community GroupWeb We Can Afford Community GroupWebAPI Discovery Community GroupWebApps UI Community GroupWebAssembly Community GroupWebAuthN Adoption Community GroupWebID Community GroupWebize Everything Community GroupXForms Users Community GroupA group for XForms users to discuss the use of XForms and propose changes and additions to the markup.XML Error Recovery Community GroupThis group's purpose is the discussion of applying error recovery parsing methods inspired from HTML to XML.XML Hypermedia Community GroupDiscuss possible benefits and implications of adding hypermedia affordance components to the XML language. Specifically, but not limited to discussion of Bugzilla bug# 17659.XML Performance Community GroupThe Mission of the XML Performance Community Group is to determine the requirements, use cases to get performance measurements of the whole XML technology stack. One of the goal is to be able to understand how XML (versus other technologies) could be used as ground to make efficient processing and identifies bottlenecks and features of this XML stack. One later goal will be to compare XML implementations among them. To do so, we might give hint on defining Efficient Profiles of existing Specifications.XPath Next Community GroupCreate a place for gathering requirement from existing user of XPath, potential user of XPath and research in this areaXProc Next Community GroupCreate a place for gathering requirements from existing and potential users of XProc, research in this area, and for supporting and writing the community-driven effort to define an XProc 3.0 specification (formerly 1.1) .XSLT Extensions Community GroupThe group aims to agree extensions to the XSLT 3.0 Recommendation published on 8 June 2017, along with supporting changes to the other specifications (XPath, Functions and Operators) on which it depends.A preliminary proposal describing requirements for such extensions can be found in Michael Kay's Proposal for XSLT 4.0 published in the Proceedings of XML Prague 2020It is intended that the group will operate primarily by use of email and forums but may hold a face-to-face meeting to resolve issues prior to final publication of a specification.The group may publish specifications.zot protocol Community Group_5a59516a-fce8-11ea-a46f-2f432d83ea00Web TechnologyProvide companies with access to the expertise and community needed to develop open Web technology._5a59521e-fce8-11ea-a46f-2f432d83ea004W3C Business GroupsBusiness Groups provide companies anywhere in the world with access to the expertise and community needed to develop open Web technology...There are currently 8 open Business Groups.Automotive and Transportation Business GroupThe mission of the Automotive and Transportation Group is 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. The Auto Working Group has since changed to service specifications to expose signals in a broader range of computing environments and bringing this extremely useful telematics information to the cloud.Fuller description of current and evolving scope is in the charter.Graph Standardization Business GroupThe Graph Standardization Business Group will take the output from the recent W3C Graph Data Workshop and develop a strategy for how the work should move ahead. The things we will explore are:* What Use Cases are organizations trying to solve? What are the business needs that need to be addressed?* What are the possible areas of technical work that needs to be done in W3C and what organizations will support it?* Which other organizations does W3C need to work with to insure interoperability?Improving Web Advertising Business GroupThe mission of the Improving Web Advertising Business Group is to identify areas where standards and changes in the Web itself can improve the ecosystem and experience for users, advertisers, publishers, distributors, ad networks, agencies and others, and to oversee liaison with existing Working Groups and to create new Working Groups as neededMerchant Business GroupThe mission of the Merchant Business Group (“Merchant BG”) is to improve the Web for people and organisations that sell goods or services, or accept donations online. This includes both business-to-business (B2B) merchants, business-to-consumer (B2C) merchants as well as not-for-profit donation acceptors. In this non-technical forum, participants will discuss merchant challenges, how emerging Web technologies could help address them, and what additional Web capabilities may be necessary. Publishing Business GroupThe Publishing Business Group fosters ongoing participation by members of the publishing industry and overall publishing ecosystem in the development of the Web for publishing, and serves as a conduit for feedback between the publishing ecosystem and W3C. See the Publishing Business Group Charter for details.The Business Group maintains a separate “Working” Web site, which includes documents, like information on meetings, index for meeting minutes, and other working documents. There is also a separate wiki for BG members. Finally, if necessary or convenient, Google Documents can also be used; these are collected in a separate Google Drive folder.(The Working Web site’s content is actually served from a dedicated Github repository.)Web and Broadcasting Business GroupThe aim of the Web and Broadcasting Business Group is to study and clarify the influence of Open Web Platform on the professional world of broadcasting, and to help stakeholders within the broadcasting industry to build good and practical understanding on the standardization processes in W3C with the chair-to-chair communication mechanism built into business groups. The business group will create monthly or bi-monthly report to summarize their study on the influence and share the reports internally. Detailed discussion and analysis on the use cases in this area should be done in the Web and TV Interest Group, so the business group will not deal with those items to avoid scope overlap. However, fruitful collaborative works may happen as a result of the chair-to-chair communication between these two groups.Web-based Signage Business GroupThe Web-based Signage Business Group is aimed at companies and organizations interested in the standardization of Web based digital signage. The goal of the group is to identify use cases and system image/model for expansion of web browser based digital signage and smarter integration of existing Web standards.Web5G Based Communications Accessibility Business GroupDiscussion communications accessibility based on Web5G and AI.The purpose is to collect information on accessibility issues and implement the communications accessibility between normal people and disabled people, natives and foreigners, people and robots.CompaniesW3C Working GroupsNew 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.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._5a5952e6-fce8-11ea-a46f-2f432d83ea00Web ArchitectureDocument and build consensus around principles of Web architecture._5a595458-fce8-11ea-a46f-2f432d83ea005W3C Technical Architecture Group (TAG)W3C created the TAG to document and build consensus around principles of Web architecture and to interpret and clarify these principles when necessary. The TAG also helps to resolve issues involving general Web architecture brought to the TAG, and helps coordinate cross-technology architecture developments inside and outside W3C. Some TAG Participants are elected by by the W3C Members, others are appointed by the W3C Director.Daniel AppelquistCo-ChairTim Berners-LeeCo-ChairPeter LinssCo-ChairYves LafonStaff Contact - W3CDaniel AppelquistSamsung Electronics Co., Ltd.Rossen AtanassovMicrosoft CorporationDavid BaronHadley BeemanAlice BoxhallGoogle, Inc.Kenneth ChristiansenIntel CorporationSangwhan MoonTheresa O'ConnorApple, Inc.The TAG is a special working group within the W3C, chartered (under the W3C Process Document) with stewardship of the Web architecture.As outlined in its charter, there are three aspects to this mission:PrinciplesDocument and build consensus around principles of Web architecture and to interpret and clarify these principles when necessary_5a595570-fce8-11ea-a46f-2f432d83ea005.1IssuesResolve issues involving general Web architecture brought to the TAG_5a595674-fce8-11ea-a46f-2f432d83ea005.2CoordinationCoordinate cross-technology architecture developments inside and outside W3C_5a595764-fce8-11ea-a46f-2f432d83ea005.3GuidanceProvides guidance on issues of strategy, management, legal matters, process, and conflict resolution._5a59584a-fce8-11ea-a46f-2f432d83ea006W3C Advisory Board (AB)The Advisory Board provides ongoing guidance to the Team on issues of strategy, management, legal matters, process, and conflict resolution. The Advisory Board also serves the Members by tracking issues raised between Advisory Committee meetings, soliciting Member comments on such issues, and proposing actions to resolve these issues. The Advisory Board manages the evolution of the Process Document. AB Participants are elected by the W3C Members.Jeff JaffeChair - W3CRalph SwickStaff Contact - W3CTantek ÇelikMozilla FoundationElika EtemadTatsuya IgarashiSony CorporationFlorian RivoalWendy SeltzerW3CTzviya SiegmanWileyDavid SingerApple, Inc.Avneesh SinghDAISY ConsortiumEric SiowIntel CorporationLéonie WatsonTetraLogicalChris WilsonGoogle, Inc.Hongru (Judy) ZhuAlibaba Group_5a595980-fce8-11ea-a46f-2f432d83ea002020-09-22https://www.w3.org/groups/OwenAmburOwen.Ambur@verizon.net