Community & Business Groups

Improving the accessibility features of browsers, other user agents, and operating systems makes every app and web site they render more accessible to people with disabilities. The Accessibility Features Community Group (AFCG) promotes the development of these accessibility features.

People with disabilities will find similar features across browsers and operating systems that also work consistently for all provided content. For content creators, reliable built-in features will help to focus their accessibility efforts on addressing challenges unique to their content. These accessibility features can come in a variety of forms, such as:

• Always-on features, such as page and app resizing
• Toggles, such as always-visible focus indicators and high contrast modes
• Settings, like preferred fonts and smallest text size
• Fallback features, like automated captions and heading detection

To promote the development of new accessibility features, AFCG will develop a list of recommended accessibility features. This list will include accessibility features already available, but also ideas for new accessibility features that can be shown to work through prototypes. To encourage the implementation of recommended accessibility features, AFCG will track which of these are supported in common browsers and operating systems.

The Accessibility Features Community Group will not develop any normative specification. As such, there will not be any Essential Claims under the W3C Contributor License Agreement or Final Specification Agreement.

Accessibility is often provided through accommodations. Schools are legally obligated to provide accommodations to enrolled students with identified disabilities, based on their needs—sign language interpreters in lectures for deaf students, digital copies of textbooks for students who are blind or have reading difficulties, extended time on exams for students who need more time due to cognitive or physical disabilities.

With online learning, the obligations are less clear—for example, with MOOCs, where students around the world are taking courses but are not enrolled at the sponsoring school or organization. Also, accommodations are not well established—sign language interpreters and note takers are typically accommodations for the physical classroom. How does an organization ensure they are meeting obligations and giving online students the support they need participate fully and to be successful?

Providers of online learning are best off delivering courses that are accessible out-of-the-box, without the need for special accommodations. And many of the features that provide an accessible experience for people with disabilities benefit all learners. For example, lecture transcripts are an excellent tool for study and review. However, without deliberate attention to the technologies, standards, and guidelines that comprise the Web Platform, accessibility may be difficult to achieve, and learners with disabilities may be left behind.

The activities of the Accessible Online Learning W3C Community Group take place at the intersection of accessibility and online learning. We focus on reviewing current W3C resources and technologies to ensure the requirements for accessible online learning experiences are considered. We also identify areas where additional resources and technologies are needed to ensure full participation of people with disabilities in online learning experiences.

This group will not publish Specifications.

This group is now closed, see also the ActivityPub W3C Recommendation and the Social Web Incubator Community Group.

The W3C Augmented Reality Community Group is an open forum for collaborative discussions about the intersection of Augmented Reality and the Web, or more simply the Augmented Web. This forum welcomes discussions about related standards, the standardisation process, related market developments and the broader social implications of this new generation of the web.

We believe that the Augmented Web brings a unique perspective that pushes standards, APIs, hardware technologies and the broader web platform to the edge of their performance limits. The Augmented Web embraces the changes brought about by HTML5 and other related standards including Geolocation, DeviceOrientation, DeviceMotion, WebGL, Web Audio, Media Capture & Streams and WebRTC. The Augmented Web integrates all of these disparate technologies into an integrated new vision of the web.

This group will not produce specifications.

Instead it aims to build an integrated community voice that reaches out to all of the other relevant working groups and standards bodies to ensure that the Augmented Web perspective is clearly represented and considered. Our goal is to help ensure that the disparate standards and APIs being planned and implemented by these other groups can be seamlessly integrated into this new vision for the Augmented Web.

Read more about goals and operating guidelines in the Charter: http://www.w3.org/community/ar/wiki/Charter

This group has been replaced by the ACT Rules Community Group.

This group is now closed, its work has moved to the Big Data Europe Community Group.

This is one of 7 Community Groups established under the BigDataEurope Project, a Coordination and Support Action under the European Union's Horizon 2020 Programme, each one tailored to a specific Societal Challenge. The discussions in this group will be used to design and realise the ICT infrastructure needed to benefit from big data technologies, maximising the opportunities of the latest European RTD developments, including multilingual data harvesting, data analytics, and data visualisation.

This Community Group is specifically interested in the challenge related to climate action, environment, resource efficiency and raw materials and is led by the Institute of Nuclear & Radiological Sciences & Technology, Energy & Safety (I.N.RA.S.T.E.S.) at NCSR Demokritos.

This group will not publish specifications.

This group is now closed, its work has moved to the Big Data Europe Community Group.

This is one of 7 Community Groups established under the BigDataEurope Project, a Coordination and Support Action under the European Union’s Horizon 2020 Programme, each one tailored to a specific Societal Challenge. The discussions in this group will be used to design and realise the ICT infrastructure needed to benefit from big data technologies, maximising the opportunities of the latest European RTD developments, including multilingual data harvesting, data analytics, and data visualisation.

This Community Group is specifically interested in the challenge related to Europe in a changing world - inclusive, innovative and reflective societies and is lead by CESSDA.

This group will not publish specifications.

This group is now closed; its work has moved to the Big Data Europe Community Group.

This is one of 7 Community Groups established under the BigDataEurope Project, a Coordination and Support Action under the European Union’s Horizon 2020 Programme, each one tailored to a specific Societal Challenge. The discussions in this group will be used to design and realise the ICT infrastructure needed to benefit from big data technologies, maximising the opportunities of the latest European RTD developments, including multilingual data harvesting, data analytics, and data visualisation.

This Community Group is specifically interested in the challenge related to food security, sustainable agriculture and forestry, marine research and the bioeconomy and is led by the Food and Agriculture Organization of the United Nations.

This group will not publish specifications.

This group is now closed; its work has moved to the Big Data Europe Community Group.

This is one of 7 Community Groups established under the BigDataEurope Project, a Coordination and Support Action under the European Union’s Horizon 2020 Programme, each one tailored to a specific Societal Challenge. The discussions in this group will be used to design and realise the ICT infrastructure needed to benefit from big data technologies, maximising the opportunities of the latest European RTD developments, including multilingual data harvesting, data analytics, and data visualisation.

This Community Group is specifically interested in the Health, demographic change and wellbeing challenge and is lead by the Open Phacts Foundation.

This group will not publish specifications.

This group is now closed; its work has moved to the Big Data Europe Community Group.

This is one of 7 Community Groups established under the BigDataEurope Project, a Coordination and Support Action under the European Union’s Horizon 2020 Programme, each one tailored to a specific Societal Challenge. The discussions in this group will be used to design and realise the ICT infrastructure needed to benefit from big data technologies, maximising the opportunities of the latest European RTD developments, including multilingual data harvesting, data analytics, and data visualisation.

This Community Group is specifically interested in the challenge related to secure societies - protecting freedom and security of Europe and its citizens, and is lead by the European Union Satellite Centre (SatCen).

This group will not publish specifications.

This group is now closed; its work has moved to the Big Data Europe Community Group.

This is one of 7 Community Groups established under the BigDataEurope Project, a Coordination and Support Action under the European Union’s Horizon 2020 Programme, each one tailored to a specific Societal Challenge. The discussions in this group will be used to design and realise the ICT infrastructure needed to benefit from big data technologies, maximising the opportunities of the latest European RTD developments, including multilingual data harvesting, data analytics, and data visualisation.

This Community Group is specifically interested in the challenge related to secure, clean and efficient energy and is led by the Centre for Renewable Energy Sources and Saving (CRES).

This group will not publish specifications.

This group is now closed; its work has moved to the Big Data Europe Community Group.

This is one of 7 Community Groups established under the BigDataEurope Project, a Coordination and Support Action under the European Union’s Horizon 2020 Programme, each one tailored to a specific Societal Challenge. The discussions in this group will be used to design and realise the ICT infrastructure needed to benefit from big data technologies, maximising the opportunities of the latest European RTD developments, including multilingual data harvesting, data analytics, and data visualisation.

This Community Group is specifically interested in the challenge related to smart, green and integrated transport and is led by the ERTICO.

This group will not publish specifications.

We will explore the sui generis nature of the "bit : coin :: info : creation" network/system/tree rooted in the Genesis block planted by Satoshi Nakamoto on January 3, 2009.
This group may publish specifications, but it is initially focused on the facilitation of focused, collaborative discussions.

• Read/Write Access (CRUD) to and from RDF data via GraphQL queries and/or interfaces
• Validation of RDF graphs using GraphQL schemas
• Mapping between GraphQL and RDF-based shape languages

• An overview of all known approaches that combine GraphQL and RDF. This overview will include a brief description of each approach, the company/organization that has developed it, and links to the corresponding documentation.
• An analysis of all known approaches that combine GraphQL and RDF. This analysis will include a categorization across one or more facets that will be identified.
• A final report on suggestions/possibilities for standardization.

This community group will discuss the applications of web browsers as the computer for controlling robots (robotics, in other words). And it will be also intended to feedback knowledge obtained from this discussion to standardization activity about Web of Things.

What kinds of values are contained in using a Web browser not only in drawing graphical user interface but also in controlling and manipulating robots, and what kinds of difficulties and problems are there in that case? To search their answers may become the driving force of this activity.

As an example, there may be the following questions in the discussion:

• Is a case applying a Web browser as a simple controller of the robots which does not have UI such as screens or the pointing devices still meaningful? For example, connectivity with web services and interlocking operation between robots (Swarm Robotics via web) may be one of its values.
• Is it possible to relate a graphical user interface of HTML to interactive and physical user interface of the robots? Is it meaningful? As an example, a relation between a physical push button and 'input' type="button" element in the HTML may deserve considering.
• Are cases using relatively low-level interface used in many robots such as PWM of the motor, digital or analog signal interfaces, I2C, SPI, UART and GPIOs by the application on the web browsers meaningful?
• Is real-time computing at the same level as RTOS feasible on the web browser-based general-purpose computing environments?

An initial related activity is the Mozilla Factory Open Hardware Project.

Furthermore, this group may publish specifications based on those knowledge such as webGPIO, webI2C API and so on.

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

Note: The original name for this group was the Ad Blocker Community Group.

The purpose of the CV 2.0 - Global Resume group is to move the current textual data and partly chaotic graphical resumes to a well-structured and accessible CV 2.0 that supports applicants as well as recruiters.

The group will publish and update:

1. specifications on the creation and usage of a CV 2.0,
2. guidance on the implementation of new systems using the CV 2.0 and integration into existing professional networks or resume filtering software,
3. templates, styleguides, and more.

See the charter for more detailed information.

Data-Centric Digital Rights (DCDR), is a framework for technologists composed of Principles, Taxonomies and other technical tools. It enables them to develop a deeper understanding about the nature of data, the digital twins that emerge from it and make possible for them to embrace their role as NextGen Rights Defenders.

Decentralized Identifier and Verifiable Credentials Applications Community Group follows below charter:

1. Promote open, focussed, fair, rich discussions and collaboration towards application of DIDs and VCs in global public and private domains.
2. Is guided by various W3C Working and Interest Groups, and collaborates with various Industry Implementors for use of DIDs and VCs in Web, IOT, and Edge computing networks.
3. Publishes unbiased best practices and reference implementations for easy standards-based adoption and application development.
4. Collect Questions and Discussion Topics, conduct knowledge sharing sessions and publish reports and minutes of such sessions.

• to facilitate focused discussion in Korean of the Decentralized Identity – Decentralized Identifiers (DIDs), Verifiable Credentials(VC) and of related specifications
• to gather comments and questions in Korean about those specifications
• to collect information about specific use cases in Korea for technologies defined in those specifications
• to report the results of its activities as a group back to the DID Working Group, the Verifiable Credentials Working Group and to the W3C membership and community
• to share an experience of Decentralized Identity best practice in the aspect of web app developer
• to share up to date information for Decentralized Identity industry including browser tech, web service, hybrid apps, dapps and extra.

The mission of this group is to write the specification of a set of HTML declarative extensions that allow :

• to write factorised HTML (with help of the handlebars template engine), perform some advanced dynamic behaviors (without javascript requirements),
• and resolve some separation of concerns problems by adding a design layer between styles and the html document itself.

This group will produce reports after discussions, specification(s), and maybe a javascript experimental implementation. One or more of this skills and expertise are desired from participants : HTML, XML, Javascript, and an attention to the importance of the javascript unobstrusive recommendation (declarative HTML should be full functionnal , security reasons, stability...).

This group may publish Specifications.

The primary mission of the community group is to bring together (top companies, universities, and teams involved in digital finance technology in various industries) and frontier technology in digital finance to push forward the development to digital asset standardization.

What is a digital asset? A digital asset is data with unique identity attributes that are binary coded, owned, or controlled by a company or individual. The data has various manifestations, including text content, images, multimedia, Computer programs, etc. Generally speaking, digital assets include websites and their content, domain names, application software, codes, electronic documents, image content, media content, electronic money, emails, game accounts, other accounts & their content, social network accounts & their relationships and cloud service accounts & their data, etc.

The digital asset on the blockchain owns all the general attributes of digital assets above, it also has other characteristics: the computer programs registered on blockchain ledger or distributed ledger, as well as the virtual assets existed in the form of bit structure, can be programmed. The exchange of assets is essentially the exchange of code. The digital assets on the blockchain can achieve complete disintermediation of autonomous and autonomous point-to-point transactions without the need for third-party manual intervention. Once the asset is issued on the blockchain, the subsequent circulation link can be independent of the issuer’s system. As the asset circulation is changed from single-center control to socialized communication, any channel with resources can become a catalyst for asset circulation, which greatly improve the efficiency of digital asset circulation, and truly achieve the effect of "multi-party issuance and free circulation."

To welcome the era of asset digitization, the group is formed to technically communicate and cooperate with other members, and to develop a broader market together. The problems that we are trying to solve in this group are:

1. Digital asset operation, trading, development, and supervision standardization;
2. Formation of industry alliances and specification of industry standards;
3. Universal education of digital assets

The group aims to support pioneer companies that explore digital assets, encourage communication and cooperation. We are expecting deliverables such as published reports and a service platform on this basis.

This group is closed; see the Credentials Community Group instead.

This group has completed its work. People interested in this topic should join the Distributed Tracing Working Group.

The mission of this group was to define the standard for distributed trace context propagation. Distributed trace context is used to enable monitoring and diagnostics scenarios in micro-services environment. It consists of request identifiers and key properties that needs to be propagated from one micro-service to another. These identifiers and properties are used to analyze an end-to-end distributed traces.

The group primary objective was to publish a specification for the protocols to use for distributed trace context propagation. Protocol includes wire format and recommended scenarios to use these protocols in applications, web servers, libraries, and platforms. The group also targetted to produce reference implementation for some languages.

Standardized and universally used trace context propagation protocols enable monitoring and diagnostics scenarios that are hard to achieve otherwise. Authors of libraries, web servers, and application performance management (APM) vendors interested to improve micro-services monitoring and diagnostics story were encouraged to participate in this group.

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

This group is closed; see also the Social Web Incubator Community Group.

This group will explore issues surrounding Generative AI risks, benefits, and best practices. We will document guidelines and potentially begin work on a technical proposal. Charter to come.

This group is closed - see also the W3C CSS Working Group Geometry API.

We invite you to visit the main site for this Community Group.

There are many technical issues in presenting mathematics in today's Open Web Platform, which has led to the poor access to Mathematics in Web Pages. This is in spite of the existing de jure or de facto standards for authoring mathematics, like MathML, LaTeX, or asciimath, which have been around for a very long time and are widely used by the mathematical and technical communities.

While MathML was supposed to solve the problem of rendering mathematics on the web it lacks in both implementations and general interest from browser vendors. However, in the past decade, many math rendering tools have been pushing math on the web forward using HTML/CSS and SVG.

One of the identified issues is that, while browser manufacturers have continually improved and extended their HTML and CSS layout engines, the approaches to render mathematics have not been able to align with these improvements. In fact, the current approaches to math layout could be considered to be largely disjoint from the other technologies of OWP. Another key issue, is that exposing (and thus leveraging) semantic information of mathematical and scientific content on the web needs to move towards modern practices and standards instead of being limited to a single solution (MathML). Such information is critical for accessibility, machine-readability, and re-use of mathematical content.

This Community Group intends to look at the problems of math on the web in a very bottom-up manner. Experts in this group should identify how the core OWP layout engines, centered around HTML, SVG, and CSS, can be re-used for the purpose of mathematical layout by mapping mathematical entities on top of these, thereby ensuring a much more efficient result, and making use of current and future OWP optimization possibilities. Similarly, experts should work to identify best practices for semantics from the point of view of today's successful solutions.

This work should also reveal where the shortcomings are, from the mathematical layout point of view, in the details of these OWP technologies, and propose improvements and possible additions to these, with the ultimate goal of reaching out to the responsible W3C Working Groups to make these changes. This work may also reveal new technology areas that should be specified and standardized on their own right, for example in the area of Web Accessibility.

The ultimate goal is to pave the way for a standard, highly optimized implementation architecture, on top of which mathematical syntaxes, like LaTeX or MathML, may be mapped to provide an efficient display of mathematical formulae. Note that, although this community group will concentrate on mathematics, many other areas, e.g., science and engineering, will benefit from (and factor into) the approach and from the core architecture.

This mission of this group is to help re-establish platform interoperability between descendants of the original "High Fidelity Virtual Reality Platform" (HFVRP) open source project.

The group will initially host discussions and coordinate volunteer research efforts in order to identify relevant areas of common ground across HFVRP projects.

For example, it was once possible to use the "interface" client from one platform to connect to a "domain server" hosted on a similar, but different platform. As these projects have continued to evolve, the once-shared protocol version (for example) between them has fallen out of sync, inadvertently breaking the possibility of cross-connections.

By gathering together common interest across multiple projects, this group hopes to then help collectively estimate efforts and help champion neutral sub-projects that can restore specific compatibilities.

It is suggested that neutral community sub-projects emerging from this group adopt the permissive Lesser GNU Public License (LGPL) open source license. LGPL currently seems to align best with the mission at hand and for these reasons:

• interoperability across diverse projects is likely to be an ongoing, multi-platform, community-driven effort -- adopting LGPL for these components can help ensure the collective community effort remains transparent and improvable across the entire project space
• as degrees of interoperability are restored LGPL dependencies can be version-managed and upgraded per each projects typical dependency update schedules
• LGPL is already an approved dependency license across HFVRP projects (ie: all known platforms critically depend on Qt by way of the LGPL) -- by not introducing a new license for these shared efforts, existing open source project audits can remain intact

This effort will hopefully span across diverse project politics, technical minds, and social circles which can come together and approach compatibility as a shared effort.

All platforms forked from the original HFVRP code base are welcome to join forces this way and in particular contributing developers, community members, and any others interested in helping broaden platform interoperability.

Some of the low-level technology skills likely needed to restore interoperability are:

• familiarity with HFVRP networking protocols and versioning
• "HFM" internal model formats and corresponding C++ structures
• overall "Oven" asset baking tool and filesystem layouts
• Baked asset structures (materials.json, ktx, modded FBX format w/draco compression, etc.)
• Entities "models.json.gz" world persistence format and "domain server" archive formats
• "Avatar.fst" and internal blendshape "de facto" standards
• "Interface" client, "domain server," and "assignment client" JSON configuration formats
• (as common sub-projects emerge) help setting up multi-project Continuous Integration systems

We think it will be easiest for volunteers in cases where interested projects have remained open source, but all HFVRP projects (including closed source ones) are welcome to join and suggest specific layers or features they would nonetheless be interested in seeing reemerged as a common open source dependency.

This group will not publish Specifications.

The mission of the HTML5 Korean Community Group includes the following:

• to facilitate focused discussion in Korean of the HTML5 specification and of related specifications
• to gather comments and questions in Korean about those specifications
• to collect information about specific use cases in Korea for technologies defined in those specifications
• to report the results of its activities as a group back to the HTML Working Group and to the W3C membership and community
• to share an experience of HTML5 best practice in the aspect of web app developer
• to share up to date information for HTML5 industry including browser tech, web service, hybrid apps and extra.

This Community Group is the successor of the HTML5 Korean Interest Group. This group will not publish Specifications.

• Improve security and privacy of communication between browsers and server-capable devices.
• Enable web applications in secure contexts to communicate with server-capable devices in local network via XMLHttpRequest, Fetch API, and WebSocket.
• Enable service discovery mechanisms to advertise existence of TLS-enabled server-capable devices.
• Encourage adoption and implementation of the specification by browser vendors and device manufacturers.

The goals of the Community Group on Human Service Data are to:

1. Create an ongoing conversation space around world data standards in the human service sector, involving stakeholders from multiple perspectives including:
   1. government human service agencies, for-profit companies, and NGOs;
   2. diverse substantive areas, such as welfare benefits eligibility, health interfaces, information and referral services, homelessness, substance abuse, child welfare, aging and disability resources, juvenile justice, etc.;
   3. diverse stakeholder purposes including exchange of data for operational purposes and collection of data for performance measurement, evaluation and policy research.
2. Facilitate the development, improvement and convergence of human service data standards, vocabularies, ontologies, and domain models by:
   1. Cataloging human services ontologies worldwide, and creating a Linked Open Data directory of the ontologies. The directory should contain metadata, such as audience, jurisdiction, potential ontology improvements, related ontologies, and other notes. See Github site linked off the group page for group artifacts.
   2. Fostering wider recognition of existing efforts and artifacts
   3. Analyzing the strengths, limitations, and areas of overlap, agreement and divergence of existing efforts and artifacts
   4. Identifying areas where standards do not yet exist, but are needed
   5. Convening working groups of diverse composition to develop and improve standards
3. Promote the adoption of human services standards

Scope of Work:

The boundary of the Community Group’s work is the set of substantive areas which are recognized in the United States and/or internationally as falling within the human service sector. This includes but is not limited to information and referral services, income support and other welfare benefits, employment training, homelessness, substance abuse, mental health, child welfare, juvenile justice, domestic violence, and senior services.

The borders between the human service sector on the one hand and the health, education and justice sectors on the other hand are not firmly defined. The community group will be open to working on any area that is related to the human services and is not entirely within the boundaries of the health, education or justice sectors.

This group is closed, please, join the Positive Work Environment Community Group with which the W3C Inclusion and Diversity Community Group (ID CG) has merged.

The mission of the group was to increase the presence of under-represented groups at W3C, and strengthen W3C culture by supporting diversity. To serve this mission, the CG determined to:

• provide a space to share experiences and information;
• produce best practices and use case documents regarding gathering data, reporting/feedback mechanisms, and practical ways to support each other;
• advise the W3C Management (W3M), Advisory Board (AB), Advisory Committee (AC), and Positive Work Environment CG about potential enhancements to our working environment to better support inclusion and diversity.

Following on the W3C Inclusive Design for the Immersive Web standards Workshop held in November 2019, the Inclusive Immersive Web Community Group tracks and promotes progress on accessibility issues identified across the many relevant W3C and Khronos groups working on aspects of XR (virtual reality and augmented reality), and ensures progress towards a consistent set of guidance, technologies and techniques to make the Immersive Web accessible to people with disabilities.

The group also acts as a liaison with the XR Access Initiative and its relevant sub-groups.

Work Mode: The primary work modes for the group will be to track and respond to accessibility issues logged in the group's repo. The group will endeavor to have a representative from each of the groups identified as relevant to the progress of the said issues and will meet a minimum of quarterly to review progress on all issues including those which have been logged but have not been actively taken up in order to ensure that there is a coordinated view of issues raised.

The mission of this group is to discuss and ultimately formalise a communication framework to enable mutual validation and attestation of workloads performed in distinct confidential computing environments. The goal is to empower developers to leverage seamlessly the developing ecosystem of confidential computing solutions agnostically across vendors and opensource. It is not the motivation of this group to publish reports but rather work on testable deliveries, example implementation, user-stories. This group may publish Specifications. Individuals and organisations with intimate knowledge of the confidential computing world and adjacent topics such as cryptography and privacy are most welcome to participate.

The Interactive Media Community Group is interested in all forms of interactive media, e.g., interactive storytelling, digital gamebooks, motion comics, visual novels, interactive films, hypervideo, and serious games.

This Group considers and discusses how standardization can support all forms of interactive media. This Group may work on a number of deliverables, reports, and specifications.

The mission of this group is to help legal regulators understand and apply Internet and Web architectural principles -- like privacy, security, internationalisation, and accessibility -- when requiring 'big tech' companies to implement technical specifications.

See the CG GitHub page for more information, including a full charter.

This group does not publish Specifications.

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

The Sentiment Analysis Community Group is a forum to promote sentiment analysis research. Topics addressed are:

• Definition of a Linked Data based vocabulary for emotion and sentiment analysis.
• Requirements beyond text-based analysis, i.e. emotion/sentiment analysis from images, video, social network analysis, etc.
• Clarifying requirements and the need for consensus as e.g. systems currently use widely varying features for describing polarity values (1-5, -2/-1/0/1/2, positive/neutral/negative, good/very good etc.).
• Marl and Onyx are vocabularies for emotion and sentiment analysis that can be taken as a starting point for discussion in the CG.

This group will specify a Query Language for the Linked Data Platform 1.0.

eLDQL will make it possible to query LDP Containers to retrieve their members. It will feature simple/limited filtering capabilities, ordering, aggregation, built-in paging, and resource inlining.

The mission of the Low Vision Community Group is to work with and support the Low Vision Task Force of the Accessibility Guidelines Working Group to improve web accessibility for people with low vision.

The Managed Component Community Group aims to standardize the specifications and usage of Managed Components, an open format for loading third-party tools on the Web. Managed Components use a sandboxed server-side environment to run, making them more secure, private and performant than more traditional methods of loading third-party tools online. The group also aims to potentially pursue changes to browser and runtime APIs that will better support the integration of Managed Components.

This group is closed - see the CommonMark instead.

The mission of the Merchant Community Group (“Merchant CG”) 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. Likely topics include:

• Customer interaction, capture and retention via accessible immersive Web experiences;
• Web checkout experiences, including the value merchants should gain with W3C's Web payments standards;
• Emerging regulatory requirements (e.g., related to privacy or accessibility) and ensuring good customer experience;
• The evolution of Web advertising;
• Good practices for reducing online fraud;
• Enhancements to transaction integrity and assurance;
• Improving mobile Web commerce experiences.

Scope

Participants will choose and prioritize discussion topics.

Activities in Scope

• Education about Web technology trends and the impact on merchants, including through discussions with other W3C groups. These activities will include non-technical briefings.
• Identification of current merchant challenges, best practices for addressing them, and how those practices may change for various reasons (e.g., due to evolving privacy practices).
• Communication of merchant use cases and requirements to groups within and outside W3C.
• Coordinating reviews of the work of other W3C groups (e.g., the Web Payments Working Group, Web Authentication Working Group or Immersive Web Working Group). It is a goal that this group enable high-bandwidth, two-way communication channels with other W3C groups.

Activities out of Scope

• Development of technical specifications.
• Discussion of specific products or implementations consistent with W3C's Antitrust and Competition Guidance.

The aim of this group is preparation for a future web standard for worldwide valid searchable metric spaces, so that these spaces can be defined by all domain name owners to all interesting topics.

The MULTI-POS CG has the following goals: 1) Identify business and technology application scenarios based on the new positioning methods; 2) Specify the key technological, scientific, and industrial elements and their relationships in the new positioning ecosystem; and 3) Identify standardization opportunities.

The first concrete work item is a review of the current state of the art, providing a common framework of reference for future work.

What is the benefit (for you): Meet the professionals, get the big picture, have influence on use cases and requirements, get cited.

• General chair: Ideologist. Overall synchronization between different pillars of the KiSS. PR with other groups and external stakeholders. Member attraction, community group development.
• Chair for integration: Integration technologies, web service composition.
• Chair for knowledge: Knowledge representation and reasoning standards and methodologies.
• Chair for devices: Embedded devices, their adoption for KiSS.
• Chair for services: Web services, standards, methodologies for service definition.
• Chair for application domains: KiSS in different application domains. Cross-domain learning and development. Benchmarking.

• Find an Asian restaurant for a business meal, near my job place.
• Schedule a meal with friends, and add it to my calendar.
• Find a restaurant with good reviews of people I trust.
• Find a cheap restaurant near a cinema where I can see the last movie of my favorite director (yes, we need an ontology for cinemas too!)

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

Some of relevant topics (by no means an exhaustive list!)

• mobility - public transport, carsharing, ridesharing /carpooling, hitchhiking, bikesharing
• housing - coliving, coworking, cohousing, hospitality exchange, flatshare / Wohngemeinschaft
• food - food hubs, food networks, producer and consumer cooperatives, community supported agriculture, gleaning, foodsharing, foodsaving, mealsharing, volksküche / langar
• learning - skillsharing, learning groups, webinars, workshops
• products - toolsharing, booksharing
• services - volunteering, help exchange
• energy - energy cooperatives
• communication - mesh networks communities
• manufacturing - research and development, design, assembly, 3D printing, open source hardware, worker cooperatives, open value networks
• health, sports & recreation
• culture & entertainment

We based our work on Linked Data technologies and assume decentralized architecture.

During first year of operation (2016) we will hold regular monthly teleconference, use github for collaboration and follow other recommendations from Modern Tooling

Relevant W3C Domains and Activities

• Technology & Society Domain
  • Social Activity
  • Web Payments Activity

• Social IG
• Social WG
• Web Schemas
• Web Payments IG
• Web Payments WG
• Web Payments CG
• Credentials CG
• Agriculture
• Automotive Ontology
• BDE-Climate action, environment, resource efficiency and raw materials
• BDE-Europe in a changing world - inclusive, innovative and reflective societies
• BDE-Food security, sustainable agriculture and forestry, marine and maritime and inland water research, and the Bioeconomy
• BDE-Health, Demographic Change and Wellbeing
• BDE-Secure, clean and efficient energy
• BDE-Smart, green and integrated transport
• Collaborative Software
• CV 2.0 - Global Resume
• Decisions and Decision-Making
• Healthcare Schema Vocabulary
• Human Services
• Linked Building Data
• Open Linked Education
• Restaurant Ontology
• Sport Schema
• Web of Sensors
• Web of Things

• Social Business CG
• Web Currencies CG
• Community I/O
• Distributed Tasks

Relevant non W3C Groups

• Open Value Network
• OuiShare Labs

An attempt to find ways of using stroke fonts in design workflows

The mission of this group is to gather and incubate new features and requirements for SVG — making it easier for software developers and content creators in the SVG community to engage with the SVG standardization process.

This group will complement the SVG working group, and covers the same scope of technologies. Draft proposals for new SVG features, developed in the community group, may transition to recommendation-track specifications in the working group.

This group may publish specifications.

See the SVG CG charter for more information.

This group is closed. See the Final Community Group Report for Touch Events Level 2.

The Touch Events community group was formed by members of the Web Events Working Group (responsible for the Touch Events specification) and the Pointer Events Working Group (responsible for the Pointer Events specification). The group's focus was to determine differences in touch event behavior between browsers.

See the Web Assembly Community Group instead.

The purpose of this group is to develop a specification for high performance, low latency typed array processing for the Web.

The basic idea is to create an API that makes it possible to utilize hardware level parallelism, such as SIMD instructions, by providing methods that operate on whole arrays rather than single elements at a time.

The purpose of this group should be to discuss anything that could enhance the web and reduce its impact on environment. Discussion could be about, for example:

• Improving efficiency of apis
• Reducing data consumption
• Upgrading apis to make them less greedy in energy

Millions of kilowatts are wasted in the world each year because of various reasons, such as:

• Bad algorithms
• Data storing (ex : spams)
• Wrong processes

Any idea that could make the web more respectful for environment is welcome to this group.