Community Groups

Our mission is to build and share 3D software that can connect and communicate in free and open ways on AR, VR, and 2D displays.

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.

The mission of this group is to discuss accessibility adapted for children (age appropriate, literacy relevant).

This group focuses on accessibility awareness in India. With India, being an IT, it is important to look at accessibility and build awareness on the web and mobile and ebooks. This group will not publish specifications.

The goal of the Accessible Infographics CG is to make information graphics, like bar charts and maps, as accessible as possible to all. The plan is to bring together experts and pioneers in the fields of data visualization and accessibility, to create use cases and requirements in a systematic manner, to devise and propose additions to SVG that improve accessible options for data in that and other graphics formats, and to document best practices and tutorials for making infographics accessible.

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.

The mission of this group is to develop a media playlist format, or an extension to an existing format such as XSPF, in order to ensure playlists support all resources necessary to deliver accessible HTML5 media (e.g., media files in multiple formats, captions, subtitles, descriptions, chapters, metadata, and sign language).

Scalable Vector Graphics offers both opportunities and challenges for accessibility. This group will explore the different conditions and circumstances for SVG use, propose clear use cases and requirements and specification text, and make tests so we can have consistent behavior in various user agents (including different screen readers).

The ACT Rules Community Group (previously known as Auto-WCAG), is an open forum set up to document and harmonise the interpretation of W3C accessibility standards, such as WCAG and WAI-ARIA, for testing purposes. The ACT Rules Community Group (ACT-R) achieves this by bringing together the people developing, implementing and using various accessibility testing tools and methodologies to document interpretations as test rules. Test rules are defined using the ACT Rules Format, and reviewed by the community. The process of researching, documenting, and sharing knowledge from different perspectives within the group, builds towards a common understanding. Publishing rules is not an end point for harmonization, it's a starting point. By publishing such test rules, ACT-R hopes to motivate organisations to share their own insights, and encourage adoption of commonly agreed test rules. ACT-R is not set up to remove differences or impose changes on accessibility testing tools and methodologies. There is value in innovation and diverse approaches. Rather it aims to contribute to more consistent results, regardless of how the testing is done. Knowing when something meets a requirement, and when it does not, should be clear and consistent. This group will not publish specifications.

This community develops test cases, requirements for testing and using the web platform. It works with existing communities and to enhance them, not replace them.

The mission of this group is to create and support a Pan-African community of competent, internationally certified IT professionals focused on developing the IT Web and mobile based tools for African Agriculture, Business, Education, Health Care, Government and general Social needs.

The objective of the community group is to propose a technology-neutral data model for electronic content labels, i.e. age labels or content descriptors. The data model will include agreed categories and fields that may contain content-specific information. The proposal is planned to include a documentation, code snippet examples and probable queries to support implementing the data model in existing age classification contexts. The data model proposal and the documentation are planned to serve as guidelines for either existing players to implement the data model in their existing schemes (and thus providing users additional information in an interoperable way) or for new players that plan to label online content and thus reduce the risk of sunk costs.

The initial mission of the Agriculture Community Group is to gather and categorise existing user scenarios, which use Web APIs and services, in the agriculture industry from around the world, and to serve as a portal which helps both web developers and agricultural stakeholders create smarter devices, Web applications & services, and to provide bird's eye view map of this domain which enables W3C and other SDOs to find overlaps and gaps of user scenarios and the Open Web Platform. We'll try to collect facts and knowledge from around the world through crowd-sourcing, while, at the same time, build a scaffold for it by quickly gathering key topics from Japanese agricultural stakeholders. Smart Platform Forum supports this early stages by connecting relevant stakeholders in Japan and organising face-to-face meetings if needed to proceed faster. This group will not publish specifications.

• Welcome post
• Group's wiki
• See also the group's pages from the right-hand side menu

The overall goal/mission of this community group is to explore the requirements, best practices and implementation options for the conceptualization and specification of domain knowledge in AI.

We plan to place particular emphasis on the identification and the representation of AI facets and various aspects (technology, legislation, ethics etc) with the purpose to facilitate knowledge exchange and reuse.

Therefore the proposed outcomes could be instrumental to research and advancement of science and inquiry, as well as to increase the level of public awareness in general to enable learning and participation.

Proposed outcomes:

• A comprehensive list of open access resources in both AI and KR (useful to teaching and research)
• A set of metadata derived from these resources
• A concept map of the domain
• A natural language vocabulary to represent various aspects of AI
• One or more encoding/implementations/ machine language version of the vocabulary, such as ChatBot Natural Language Understanding & Natural Language Generation
• Methods for KR management, especially Natural Language Learning / Semantic Memory

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

Editable doc.

The mission of this group is to propose foundational specifications relating to "algorithmic modelling": a "model", in this context, being a description of the composition and relative dynamic behaviour of the sub-parts of a system, as exemplified by the Object Management Group's Model Driven Architecture. The output of this group may then act as a reference point for groups requiring the use of specific types of models, conceptual and computational being two such.

This group will explore annotation user interface challenges, examples, and best practices. The group will produce an informative guide to annotation user experience. This group will not publish specifications.

Our mission is to design & prototype ideas for mobile platforms and web apps.

Argument-Representation's mission is to recommend a standardized representation for formal argument. It is not intended to augment XML in any other way. The group does not necessarily commit to creating a novel representation. For instance, after due consideration it could endorse an existing one or recommend accepting an existing one with minor changes. Formal argument means a formalizable set of connected statements or statement-like objects intended to establish a proposition.

The Argumentation Community Group will facilitate and promote the use of the Web for all forms of argumentation. The group will discuss and design both argumentation representation formats and systems.

How WAI-ARIA is supported by assistive technologies, such as screen readers, is highly variable. This variation in WAI-ARIA rendering adds unnecessary complexity to the development of high-quality web experiences for users of assistive technologies and places significant limitations on the types of web widgets that can be made widely accessible. This community group is dedicated to: 1. helping assistive technology developers converge on a set of clear norms for baseline support of WAI-ARIA. 2. Helping web developers understand the current state of support for WAI-ARIA by assistive technologies. WAI-ARIA is as important to assistive technology presentation as CSS is to visual presentation. Join us to help make WAI-ARIA as reliable as CSS. This group will not publish Specifications.

The Art & Culture (Museums) On The Web Community Group is an open forum for collaborative discussions about making the Web a better place for the artifacts and other objects of artistic, cultural, historical, or scientific importance in the museums worldwide. Use cases and requirements collection, gap analysis, standardization ideas incubation and technical proposal might be included in the work scale of this group.

Develop a standard for exchanging type-safe data on the web. https://docs.atomicdata.dev

A group to gather and incubate new features and requirements for the Web Audio API. Making it easier for the community to engage with the Audio Working Group.

Mission: To create an open standard file format to support audio description all the way from scripting to mixing. Scope: To agree requirements and propose a workable open standard file format for audio description, probably a profile of TTML2, with the intention of moving to the Rec track within a Working Group. Deliverables:

• Requirements document
• Draft specification document
• Explainer

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

The Automotive Ontology Working Group is an informal group of individuals and corporations who want to advance the use of shared conceptual structures in the form of Web ontologies for better data interoperability in the automotive industry, and this at Web scale. In particular, we want to develop extension proposals for schema.org so that automotive information can be better understood by search engines and OWL Web ontologies for the automotive industry. Also, we want to provide a forum for bringing together researchers and practitioners who are working on advancing the field.

Motion Comics, Web Comics, Visual novels, Interactive Manga, Webtoon, Turbomedia, Parallax strip, Still motion art ... all digital variants of visual narratives share a common underlying model, which must be clearly expressed before a universal publication format can be designed and released as a Web standard. The mission of the BD Comics Manga Community Group (*) is to study and document, for all kinds of visual narratives expressed digitally, a common conceptual model and associated sets of controlled values. (*) Bande dessinée, Comics, Manga are terms broadly used for sequential art in Europe, USA and Asia; this underlies the global scope of the study.

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

The target for this group is to crowd-source ideas from the community regarding best practises for producing multilingual linked open data. The topics for discussion are mainly focused on naming, labelling, interlinking, and quality of multilingual linked data, among others. Use cases will be identified to motivate discussions. Participation both from academia and industry is expected. The main outcome of the group will be the documentation of patterns and best practices for the creation, linking, and use of multilingual linked data. This group will not create specifications.

The objective of the community group is: to facilitate a consensually agreed route for the conversion and/or mapping of bibliographic data into Schema.org; building on the development, initiated by the Library of Congress, of the BIBFRAME 2.0 Linked Data vocabulary; utilising the specifications of BIBFRAME 2.0 as a stable base to develop upon. The initial objectives of the community are: 1. The creation of a reference metadata mapping from BIBFRAME 2.0 to Schema.org. 2. To facilitate agreed development and open sharing of reference software implementation(s) to: Enrich BIBFRAME data with Schema.org Terms and/or Create Schema.org terms from BIBFRAME 2.0 data.

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

The group to discuss technical issues arising from the Big Data Europe Project.

Bioschemas aims to improve data interoperability in life sciences. It does this by encouraging people in the life sciences to use schema.org markup, so that their websites and services contain consistently structured information. This structured information then makes it easier to discover, collate and analyse distributed data. The main outcome of the Bioschemas community group will be a collection of specifications that provide guidelines to facilitate a more consistent adoption of schema.org markup within the life sciences.

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 using the seed (hash) value 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f. This group may publish specifications, but it is initially focused on the facilitation of focused, collaborative discussions.

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

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

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

The purpose of the Brazilian’s community group is to promote and foster the discussions around digital publications in Brazil, stimulate the adoption of the EPUB 3.1 standard by publishers and developers. The local group will translate W3C documents, guidelines and specifications to minimize barriers with the non-native language and help in the understanding of the standards for a growing number of people. It is also the responsibility of this group, bring questions and pertinent feedback to W3C’s Publishing Working Group. The group will organize regular meetings and events to mobilize more and more participants in local debates and also as a way to stimulate the EPUB 3.1 adoption by the Brazilian publishing industry. This group will not publish original Specifications.

The aim of this group is to explore how GraphQL and RDF can be combined, and to what respect they can benefit each other. This group explores possible combinations of GraphQL and RDF. We identify and compare existing approaches that bridge these worlds, collect use cases and requirements for such approaches, and characterize corresponding application areas. This will produce deliverables that may serve as input for one or more possible future standardization efforts. Examples of application areas combining GraphQL and RDF are:

• 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

This group aims to produce the following deliverables:

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

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

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

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.

Being able to efficiently collect, analyse and leverage data insights from buildings is a catalyst for optimising building performance, improving the use of resources and moving towards predictive maintenance and buildings that can respond to the climate emergency. The lack of standardised naming and labelling for connected devices in the built environment means we are failing to leverage the value of data to allow interoperability, improve building efficiency and increase occupant productivity. A naming and labelling standard (complementing other industry initiatives) will simplify and drive consistency thus increasing value by unlocking the application of technologies such as machine learning. The work of this community group will align with and complement other initiatives in the industry such as BRICK, Haystack, Omniclass, Uniclass, IFC etc. In scope for this work are:

• A simple specification for naming syntax
• A register of building device names and labels

A community group to incubate work on bullet chatting.

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

The mission of this group is to explore how open data and metadata may be realised through animated maps and games that facilitate forecasting and understanding of risk across knowledge domains. And to help create the necessary tools that are easy to use and produce multimodal accessible resources that engage.

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

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.

The mission of this group is to develop a proto-spec for marking up changes to documents.

This group will develop Character Description Language (CDL), an XML application for stroke-based representation of any CJK character. For more information about this technology, see: * Character Description Language (CDL) draft specification: http://www.wenlin.com/cdl/ * Appendix F: “CJK Strokes Documentation” (Unicode 6.1): http://www.unicode.org/versions/Unicode6.1.0/appF.pdf

the "Chemistry for the Web and Publishing" Community Group will focus on moving beyond simply providing images of Chemistry content on the web and in published materials to a semantically rich form that will work for everybody, including persons with disabilities.

Chinese Digital Publishing Community Group aims to provide a platform for the Chinese digital publishing industry to share perspectives on Chinese text layout, copyrights and other occupational standards. Also we hope to help build network of contacts within the Chinese digital publishing companies and the publishing industry. This group will not publish specifications.

The mission of this group is to help Chinese developers and designers to build an accessible web. This group will not produce technical specifications.

REST seven's rule was "Code on Demand," meaning the ability for the server to deliver code able to run on the client. Some, to use the same code everywhere, tried to do it with Java, .NET (ActiveX). Today, even Flash is fading out to let this place to JavaScript. HTML5 and offline support contributed in the creation of a bunch of APIs which only made sense on server-side in first place: File/FileSystem, Workers, Sockets, Storage/Session, Blob, ImageData. Most of those APIs, and even the already existing XMLHttpRequest (now in version 2) have been designed from the beginning to be usable via either synchronous or asynchronous APIs from the very early stages (synchronous is not blocking any more the user interface in browsers when used in workers). Now that the Server-Side JavaScript is rising again either in synchronous and asynchronous implementations, it is time, if we really want interoperable code/libraries/modules, to make those APIs taking into account the server-side context, and then on the other end, to push Server-Side JavaScript implementations to support them. CommonJS started a great project, it is now time to make its ambitions real.

The group will examine and create specifications related to distributed computation and storage, with an XML network transport layer and possible mapping to RDF.

Mission

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

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

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

Participation

You do not need to be an expert in all topics related to cognitive accessibility to join the community group. The COGA Community Group will work in smaller groups for specific subjects, giving you the opportunity to participate on the topics you choose.

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

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

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

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

The real world is frustratingly uncertain, incomplete and inconsistent. This is challenging for traditional approaches to information systems, and a new paradigm is needed that combines symbolic and statistical techniques, building upon decades of work in the cognitive sciences, and over 500 million years of natural selection. This will allow us to create cognitive agents that learn and reason based upon prior knowledge and past experience, and which can satisfy the need for, transparency in decision making, and continuous learning for adapting to ever changing needs. This community group will address opportunities for cognitive agents using graphs, statistics, rules and graph algorithms, starting with an amalgam of RDF and Property Graphs, together with Web architecture for cognitive databases.

More specifically, the Cognitive AI Community Group will work on use cases and requirements, demo's, open source, and scaling experiments. For more details, see:

• Cognitive AI CG GitHub Repository

• Chunks and Rules Specification

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

• An older talk on Cognitive AI and the Sentient Web

• Longer treatise on Cognitive AI

• Public mailing list archive

• Contributing to the Cognitive AI Community Group

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

Discussion forum between CSS experts, Color Management experts, and TV/Movie/Broadcast experts to explore use cases and inform W3C specification work (such as CSS Color 4 and subsequent levels). Both SDR and HDR are in scope. Wide gamut displays and the Web is in scope. Web use of ICC (v.4 and ICCMax) is in scope.

The aim of our project is to build new HTML5 specifications that can be used later by developers who wish to create more accessible websites for colour-blind people. The goal is that the specifications, that we are going to suggest, will one day become a standard of HTML5. According to WHO, 246 million people worldwide, whilst not being blind, suffer from moderate or severe visual impairment. This includes various forms of colour blindness and other visual deficiencies such as glaucoma and cataract. Just like everyone else, colour-blind people use the Internet for professional and private purposes. However, they often encounter accessibility problems. Our challenge is to improve their situation by providing easy-to-use HTML5 specifications to developers. To understand, define and bring solutions to colour-blind people who interact with web interfaces, we are going to conduct user tests with them based on the eye tracking technology. This will allow us to define a corpus of usability rules, according to the level of deficiency of the colour-blind persons. These rules will help us to develop solutions, validate them with other user tests and later develop HTML5 specifications that can be used in CSS. The challenge is not only helping developers with easy-to-use HTML5 markups, but also make them aware of the situation and together build a better Internet with more accessible websites. Feel free to join this group if you: * are suffering from colour-blindness * or have field experience developing accessibility solutions for the colour-blind or other visual impairment * or have experience working with a previous submission to the W3C.

The mission of the Community Council is to promote Community and Business Groups and ensure that they function smoothly. The Council's activities include: documenting good community practices, reaching out to new communities, identifying opportunities for collaboration between groups, helping groups transition to the standards track if they so desire, and routine group maintenance. The Community Council will also discuss existing and new features and other ways to enhance the Community Group experience. Anyone may join the Community Council. In particular, W3C encourages Chairs of other Community and Business Groups to participate (e.g., in monthly meetings that will include W3C staff). This group will seek to make decisions when there is consensus and with due process.

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

The concept of consent plays an essential role in the use of digital technologies as an enabler of the individual’s ownership, control, and agency. Regulations such as the GDPR assert this relationship by permitting use of consent as one of the possible legal bases for the lawful practice of data processing. Through this, obtaining consent is widely practised in the digital world, and can be perceived as an essential means to enable the individual’s agency regarding the management and ownership of their personal data. While different legal frameworks specify various requirements and obligations regarding the legal validity of consent, which should be, e.g. valid, freely given, specific, informed and active; existing and ongoing research shows that the majority of people are not empowered to practice their digital right to privacy and lawful "consenting" due to various malpractices and a lack of technological means acting in the individuals' interest. This group aims to contribute towards the empowerment of humans concerning their rights of privacy and agency, by advocating interdisciplinary, pluralist, human-centric approaches to digital consent that are technologically and legally enforceable. The mission of this group is to improve the experience of digital "consenting" while ensuring it remains adherent to relevant standards and laws. For this, the group will: (i) provide a space for people and stakeholders to come together (ii) highlight and analyse concepts, issues and problems about digital consenting (iii) propose and develop solutions. Some concrete areas for the working of this group are: (a) developing interdisciplinary solutions; (b) documenting and achieving legal compliance; (c) improving the user experience; and (d) utilising existing and developing new concepts and standards for digital consent.

The mission of this group is to improve web standards by conveying to Working Groups use cases from a content blocking perspective (for example web technologies used in areas related to ad blocking, anti-tracking or even accessibility).

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

The mission of the Conversational Interfaces Community Group is to enable web developers to collaborate and share conversational experiences for a variety of domains. Most dialogue systems serve interactive experiences in their own domain specific language, causing a fragmented zoo of proprietary formats. For example, Google Home or Alexa do not share a common intermediate representation, which makes writing wide-spread content inaccessible to the mass audience. We study existing specs and design standards to harness proven techniques into common agreement. See the the Community Group's charter.

A clearinghouse for experience and guidelines for people who are suddenly called to avoid travel or meetings, work-at-home or do classes online. Focus on current capabilities and future needs.

The mission of the W3C Credentials Community Group is to explore the creation, storage, presentation, verification, and user control of credentials. We focus on a verifiable credential (a set of claims) created by an issuer about a subject—a person, group, or thing—and seek solutions inclusive of approaches such as: self-sovereign identity; presentation of proofs by the bearer; data minimization; and centralized, federated, and decentralized registry and identity systems. Our tasks include drafting and incubating Internet specifications for further standardization and prototyping and testing reference implementations.

The mission of the W3C Credible Web Community Group is to help shift the Web toward more trustworthy content without increasing censorship or social division. We want users to be able to tell when content is reliable, accurate, and shared in good faith, and to help them steer away from deceptive content. At the same time, we affirm the need for users to find the content they want and to interact freely in the communities they choose. To balance any conflict between these goals, we are committed to providing technologies which keep end-users in control of their Web experience.

The group's primary strategy involves data sharing on the Web, in the style of schema.org, using existing W3C data standards like JSON-LD. We believe significant progress toward our goals can be reached by properly specifying "credibility indicators", a vocabulary/schema for data about content and the surrounding ecosystem, which can help a person and/or machine decide whether a content item should be trusted.

Please see the group wiki for more details.

The mission of this group is to create and support a community of competent, internationally certified IT professionals focused on developing the IT Web and mobile based tools for Croatian Agriculture, Business, Education, Health Care, Government and general Social needs.

This group aims at creating an international and interdisciplinary network of researchers - academic and non-academic - interested in exploring the economic, legal, technical and societal challenges raised and faced by cryptoledger-based applications, such as Bitcoin or Ethereum. The purpose of this group is to enable peer support and collaboration for researchers across institutions and disciplines to achieve a better understanding of the opportunities and risks posed by cryptocurrencies and other cryptoledger-based applications. This group includes those doing theoretical analysis, investigating tools and applications that might hinder or support the adoption of alternative cryptocurrencies, or collaborating on the development of new tools to further promote their deployment worldwide. This group will not publish specifications.

Document and describe how browsers and assistive technology currently implement CSS in regards to accessibility and guidance on how they should. The documentation and guidance will be directed at both CSS implementers and developers who use CSS.

We are a community of users of CSS print, working together to gather use cases, help with specifications, and advocate for more and better implementations.

Decades after the web emerged, hypertext creators pointing to a specific place in a resource they don't control still have to hope or beg that there's a convenient link anchor placed there by the author. CSS selectors let us point anywhere in a document - let's bring them to hypertext! You can see a very rough initial plan of this at http://simonstl.com/articles/cssFragID.html.

A group to debate and define CSS4. The umbrella term "CSS3" was incredibly useful in teaching the new additions to CSS around 2010. It seems time to loosely group together more recent additions under another umbrella, to help increase adoption and make it easier to teach. This will not change how the CSSWG operates, will not affect spec numbering, and will be separate from the official CSS snapshots. Discussion began at: https://github.com/w3c/csswg-drafts/issues/4770 This WICG group is a place to work out the details.

Discussions and mutual support for implementers, publishers and spec developers of the technologies developed by the CSV on the Web Working Group. The group is not chartered to change published W3C documents, but can record new issues, errata, and test cases for those specification. The CG may also discuss related work, e.g. R2RML or other potential extensions.

The Customer Experience Digital Data Community Group will work on reviewing and upgrading the W3C Member Submission in Customer Experience Digital Data, starting with the Customer Experience Digital Data Acquisition submission linked here (http://www.w3.org/Submission/2012/04/). The group will also focus on developing connectivity between the specification and the Data Privacy efforts in the industry, including the W3C Tracking Protection workgroup. The goal is to upgrade the Member Submission specification via this Community Group and issue a Community Group Final Specification.

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

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

Gathering requirements and discussing data pipelines (think XProc but for JSON, HTML, text, XML, binary, EPUB...)

The mission of the W3C Data Privacy Vocabularies and Controls CG (DPVCG) is to develop a taxonomy of privacy and data protection related terms, which include in particular terms from the new European General Data Protection Regulation (GDPR), such as a taxonomy of personal data as well as a classification of purposes (i.e., purposes for data collection), and events of disclosures, consent, and processing such personal data.

The DPVCG was created as an outcome of the W3C Workshop on Data Privacy Controls and Vocabularies in Vienna in 2017, and started on 25th May 2018 – the date of the enforcement of GDPR. Since then, the DPVCG has worked to fulfil its aims and objectives, and produced the Data Privacy Vocabulary (DPV) as a deliverable.

Membership to the group is open to all interested individuals and organisations. To join the group, you need a valid W3C account – which is free to get and can be requested here. The group meets usually through online meeting calls, details of which, including past minutes, can be found here. The group also interacts through a mailing list regarding topics, discussions, sharing of agendas, actions, and other relevant items. The resources and work relevant to the group is hosted on the GitHub platform under the DPVCG name.

The group is currently chaired by:

• Harshvardhan J. Pandit (ADAPT SFI Research Centre, Trinity College Dublin)
• Bert Bos (ERCIM W3C)
• Axel Polleres (WU Wirschaftsuniversitat Wien – Vienna University of Economics and Business)

Participation in Group Activities

The working of the group is fairly open and transparent in its process, with most of the information present on the wiki. For past work, actions, issues, and records – please refer to the wiki and threads on the mailing list. Anyone can use the mailing list to ask questions, suggest topics, raise issues, and offer solutions. Non-members might receive an automated reply asking them to authenticate their email or email address for posting.

Similarly, calls are usually open to attend, with the agenda shared on the public mailing list. Call details may be shared on the internal mailing lists accessible to only members for security purposes – so it may be best to ask the chair(s) or a member for attending a call.

General questions regarding what the group considers in scope can be determined from the aims and objectives. Specific queries or propositions should be conveyed to the mailing list. For issues regarding the DPV, including addition of concepts or a query or other relevant topics – you can use the mailing list or the issues feature in a GitHub repo.

Data Privacy Vocabulary (DPV)

The DPV is a vocabulary (terms) and an ontology (relationships) serialised using semantic-web standards to represent concepts associated with privacy and data protection, primarily derived from GDPR. It enables representation of which personal data categories are undergoing a what kind of processing by a specific data controller and/or transferred to some recipient for a particular purpose, based on a specific legal basis (e.g., consent, or other legal grounds such as legitimate interest, etc.), with specified technical and organisational measures and restrictions (e.g., storage locations and storage durations) in place.

The DPV is useful as a machine-readable representation of personal data processing and can be adopted in relevant use-cases such as legal compliance documentation and evaluation, policy specification, consent representation and requests, taxonomy of legal terms, and annotation of text and data.

The DPV is an evolving vocabulary – as the DPVCG continues to work on updating it with broader concepts as well as enriching its hierarchy of concepts. For this, we invite contributions of concepts, use-cases, requirements, and applications.

The mission of this group is to provide a unified data model for data visualization, data visualization API, core model of data visualization methods and category, and domain specific data visualization methods (e.g. scientific data visualization), and further, data interactive analysis method.

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

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

The mission of the Decentralized Identity (DID) Korean Community Group includes the following:

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

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

The mission of the Declarative 3D for the Web Architecture Community Group is to determine the requirements, options, and use cases for an integration of interactive 3D graphics capabilities into the W3C technology stack. This group is aimed to extract core features out of the requirements as foundation to propose feasible technical solutions. These should cover the majority of 3D use cases for the Web - but not necessarily all of them. There are upcoming open (e.g., WebGL) and proprietary (e.g., Adobe) proposals for imperative graphics APIs in the Web context but we are missing an easy way to add interactive high-level declarative 3D objects to the HTML-DOM to allow anyone to easily create, share, and experience interactive 3D graphics - with possibly wide ranging effects similar to those caused by the broad availability of video on the Web. The goal of this CG is to evaluate the necessary requirements for a successful standardization of a declarative approach to interactive 3D graphics as part of HTML documents.

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

Our mission is to define and describe a declarative method for developing VR content. The hope is to define a new set of HTML tags and CSS properties that will allow web developers across the globe to write VR content for display in modern browsers

The Design Tokens Community Group's goal is to provide standards upon which products and design tools can rely for sharing stylistic pieces of a design system at scale.

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

The mission of Digital Asset Management Business Ontology Community Group is to propose, discuss, create and maintain extensions to schema.org related to the Digital Asset Management Industry.

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

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 working group is for the discussion and design of the specification of a protocol for standardized distributed ECMAScript and WebGL applications. Distributed Compute Protocol (DCP) will become the standard for distributed computing by seamlessly integrating with the internet protocol suite. DCP will be introduced on top of HTTPs/TCP/IP to transmit JSON package files for execution, transforming computational power into a public utility. The Compute Resource Allocation algorithm (CRAa) matches demand for suppliers by efficiently comparing a variety of requirements. DCP is a foundational building block for web 3.0 and is an enabler of technology including, but not limited to, allowing other distributed applications and blockchains to move to the world wide web.

Common 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!

Current technology and ICT models generate configurations where the same user interface can be offered through different interactions. These new technological ecosystems appear as a result of the existence of many heterogeneous devices and interaction mechanisms. Consequently, new conditions and possibilities arise which not only affects the distribution of the user interfaces but also the distribution of the involved users’ interactions. Thus, we move the focus from addressing the distribution of user interfaces to the distribution of the users’ interactions which poses new challenges that deserve to be explored. In this context Web engineering appears as a fundamental research field since it helps to develop device-independent Web applications with user interfaces capable of being distributed and accessed through different interaction modes. This fact makes Web environments to be especially interesting within the scope of this community group. The main goal is to join people working on Distributed Interactions and share their knowledge in aspects related to new interaction paradigms and the way we can manage them in a distributed setting on the World Wide Web.

This community group, started by Lee Tien of the Electronic Frontier Foundation, is intended as a companion to the Tracking Protection Working Group with the goal of enabling consumer and privacy groups to participate meaningfully in the WG even if they do not participate in WG conference calls, mailing lists, or in-person workshops. In the short term, this community group's major goal will be to analyze and respond to the First Public Working Draft, which is expected soon.

Document services are client-local, on-prem, or remote services upon documents, portions of documents, or selections of document content. Examples of document services include: spellchecking, grammar checking, proofreading, fact checking, mathematical proof checking, reasoning checking, argumentation checking, and narrative checking. The Document Services Community Group intends to, in coordination with other groups, create a general-purpose architecture, API's, and protocols for both free and paid-subscription-based document services to convenience document service providers and to equip and empower end-users who will be able to make use of multiple document services simultaneously to better author and review documents.

This Community Group focuses on e-learning. Participants will discuss new and existing technologies for e-learning and M-learning. The group will also talk about the reach, social change and impact of e-learning.

The aim of this community group is to show how educational and occupational credentials may be described with schema.org, and to propose any additional terms for schema.org that may be necessary. Educational and Occupational Credentials are defined as diplomas, academic degrees, certifications, qualifications, badges, etc., that a person can obtain through learning, education and/or training. They are typically awarded on successful completion of an assessment of relevant capabilities. See also the Connecting Credentials glossary of credentialing terms. Related work includes: the Credential Transparency Description Language (CTDL) developed for the Credential Engine; IMS Global's Badge Alliance; and, the W3C Verifiable Claims Working Group. The work of this group will complement these, with a focus on integration with schema.org and on describing a credential that is being offered rather than the claim to posses one.

The mission of the Educational Exercises and Activities Community Group is to develop standards for educational exercises and activities and to make recommendations with regard to other standards.

To complete EXI WG's EXI4JSON (EXI for JSON) work on efficient data encoding for JSON. We will also investigate compression, performance and power-reduction techniques using a variety of data representations.

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

The aim of the Emergency Information Community Group is to support the development of semantic vocabularies and common frameworks for information interoperability to ensure the meaningful sharing and aggregation of information to assist in emergency, crisis, and humanitarian functions. This Community Group provides a forum for the exchange of ideas and experiences, scenarios and requirements, and the development of community specifications to drive future formal standardisation.

The mission of Enterprise Ethereum is building and advancing Ethereum to enterprise grade technology. The group will build, promote and broadly support Ethereum-based technology best practices, standards and reference architectures.

Matching entities across data sources using different identifiers and formats is a pervasive issue on the web. This group revolves around developing a web API that data providers can expose, which eases the reconciliation of third-party data to their own identifiers. OpenRefine's reconciliation API is used as a starting point. Our goals are to document this existing API, share our experiences and lessons learnt from it, propose an improved protocol in the view of promoting it as a standard, and build tooling around it. A description of the existing protocol can be found here: https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API

The EPUB 3 Community Group is a forum for ongoing technical development of EPUB 3 and related extension specifications and ancillary deliverables. The EPUB 3 Community Group charter contains full details.

This group is to discuss requirements for an open standard for describing ETL projects, including project structure, sequencing, data flow transformations, data source connectors, for the purpose of transporting ETL projects between commercial and open source ETL tools.

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

Currently Experience API (xAPI) mostly focuses on providing “structural” interoperability via JavaScript Object Notation Language (JSON). Structural interoperability defines the syntax of the data exchange and ensures the data exchanged between systems can be interpreted at the data field level. In comparison, semantic interoperability leverages the structural interoperability of the data exchange, but provides a vocabulary so other systems and consumers can also interpret the data. Analytics produced by xAPI statements would benefit from more consistent and semantic approaches to describing domain-specific verbs. The xAPI specification recommends implementers to adopt community-defined vocabularies, but the only current guidance is to provide very basic, human-readable identifier metadata (e.g., literal string name(display), description). The main objective of the Vocabulary and Semantic Interoperability Working Group (WG) is to research machine-readable, semantic technologies (e.g., RDF, JSON-LD) in order to produce guidance for Communities of Practice (CoPs) on creating, publishing, or managing controlled vocabulary datasets (e.g., verbs).

The mission for this group is to propose a unified, consensual structure for representing experimental protocols in the biomedical domain. This group will start by publishing use cases, discussions on published use cases, evaluations of existing reporting structures, ontologies, minimal amounts of informations, etc applicable to the problem of representing and reporting experimental protocols. This group will address semantic and syntactic issues.

Semantic data is available widely and semantic data exploration is becoming a key activity in a range of application domains, such as government organisations, education, life science, cultural heritage, and media. Several novel interfaces and interaction means for exploration of semantic data are being proposed, for example exploratory search systems, semantic data browsers, ontology/content visualisation environments and semantic wikis. Although on the rise, the current solutions are still maturing and need to take into account human factors to make exploration intuitive or employ necessary computational models to aid the intuitiveness and improve the effectiveness of exploration tasks. Lessons also can be learned from the commonalities and differences in exploration requirements between different domains. Hence, greater benefits can be achieved by bringing together expertise from different communities, including HCI, Semantic Web, and personalisation with the potential application domain demands. This group is an effort to bring these community together to benefit from the mutual experiences in solving some new and exciting problems. This group will not publish specifications.

The wealth of data about cultural heritage collections held within archives world-wide is of great interest for humanities research and education activities. Yet this data is too often hard to find, created in isolated silos and poorly documented. Large projects such as RES (https://bbcarchdev.github.io/res/) , HuNI (https://huni.net.au), Europeana (http://www.europeana.eu) and CLARIAH (http://www.clariah.nl/) express a clear need for making that data easier to find, link and consume. The mission of this community group is to discuss which standards are needed to facilitate this process. The aim is to produce recommendations for cultural heritage data exposure using the work of RES, HuNI, Europeana and CLARIAH as a starting point.

This community recommends an approach for exposing IEEE Learning Object Metadata (LOM), a metadata standard for educational contents, as Linked Data. It is intended as a bridge for linkage of educational metadata into Linked Open Data (LOD). This community aims to describe a mapping of IEEE LOM elements to RDF based on Linked Data principles.

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

The Extensible Web Community Group is an incubator for web technologies enabling authors to extends the native web technologies via scripting (ie: shims & polyfills).

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.

The mission of this group is to propose new APIs that allow for secure identity federation across domains on the open web.

The purpose of the Federated Identity Community Group is to provide a forum focused on incubating web features that will both support federated identity and prevent untransparent, uncontrollable tracking of users across the web. While the community group will take privacy concerns into consideration, these concerns will be balanced against the need to explore innovative ideas around federated authentication on the web.

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

The aim of the Film Industry Community Group is to explore the implementation of Open Web Platform and Semantic Web technologies within the professional world of filmmaking.

The mission of Financial Industry Business Ontology Community Group is to propose, discuss, create and maintain extensions to schema.org related to Financial Industries.

The Font and Text Community Group gathers individuals and organizations interested in discussing and developing specifications and implementations for technologies which operate on and at the interface between text encoding and font formats. Examples of such technologies are shaping engines and text layout applications.

The mission of FKG group is to create specifications for encoding ontologies that AI Assistants can operate upon enabling them to execute functions embedded in a web page. FKGs are encoded in JSON-LD, this group defines the vocabulary. A detailed proposal can be found at: https://github.com/keyvan-m-sadeghi/assister/blob/assister-conception/rfcs/text/assister-conception/README.md

The goal of the Games Community Group is to improve the quality of open web standards that games developers rely on to create games. To achieve its goal, the Games community group will:

• Track specifications and vendor implementations related to open web games.
• Recommend new specifications to be produced and find group homes for them.
• Refine use cases to communicate specific needs of games.
• Suggest refinements or fixes to existing specifications to better meet the needs of the game development community.
• Explore capabilities —APIs, semantics, techniques for rendering, processing, personalization, customization, interoperability, etc.— that developers can leverage to localize games and guarantee that they are accessible.
• Evangelize specifications to browser vendors.
• Document how to best use open web standards for games.
• Evangelize open web standards to game developers and game development best practices to web developers.

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

Please see the adopted charter for details.

GeoKnow addresses a bold challenge in the area of intelligent information management: the exploitation of the Web as a platform for geospatial knowledge integration as well as for exploration of geographic information. This group will bring together scientists, GIS users, linked Data users, data consumers and providers, interested in the exploitation of linked geospatial data. This group will not produce specifications.

We invite you to visit the main site for this Community Group (<https://w3c.github.io/mathonwebpages/>)

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.

The mission of the GPU on the Web Community Group is to provide an interface between the Web Platform and modern 3D graphics and computation capabilities present in native system platforms. The goal is to design a new Web API that exposes these modern technologies in a performant, powerful and safe manner. It should work with existing platform APIs such as Direct3D 12 from Microsoft, Metal from Apple, and Vulkan from the Khronos Group. This API will also expose the generic computational facilities available in today's GPUs to the Web, and investigate shader languages to produce a cross-platform solution. Please see the draft charter. The group is inviting browser engine developers, GPU hardware vendors, 3D software engineers, as well as the broader Web community who have an interest in 3D graphics and efficient computation to participate.

The Handshake project aims to solve certificate authorities problems caused by the centralization of the DNS root zone. The goal is to replace the current DNS root zone with a decentralized blockchain database that allows everyone to own a TLD. To learn more, see https://learn.namebase.io/

Haptic feedback can offer significant benefits in terms of accessibility and usability of touch-based interfaces. Many mobile devices, such as smart phones and tablets, incorporate built in vibration feedback. The W3C Vibration API [1] will allow Web application developers to utilize vibration effects via Javascript and some have previously proposed the addition of haptic properties to CSS [2] [3]. As new haptic technologies are expected to emerge in the near term, now is the time to bring interested parties from the research, user, and vendor communities together to examine and discuss standardization, accessibility, authoring, and user experience. [1] http://www.w3.org/TR/vibration/ [2] https://lists.webkit.org/pipermail/webkit-dev/2010-June/013334.html [3] http://chrisnager.com/touchable-textures-with-css-can-you-feel-me/

Hardware token are offering secure services in the field of cryptographic operation, citizen identity and payment to native applications. This community group will analyze use cases where browser (and web application developers) could benefit from those secure services. The expected deliverables of this community group are (1) documented use cases, (2) technical requirements for implementing those secure services in user agents, (3) draft APIs, (4) group charter - integrating suggested improvements received during the W3C Hardware Security WG charter proposal review. Note : by hardware tokens, we mean technologies such as secure chips or secure elements, trusted execution environment, TPM....

This community effort aims to provide medical,healthcare and life-science specialized web schemas and vocabulary through improving and extending the existing schemas, concepts, terms and definitions in schema.org vocabulary. Ultimate goal is to enable the use of schema.org not only by webmasters but also in indexing health records, healthcare documents, and as a pillar open source of medical and healthcare and life science ontology/vocabulary for formalization of healthcare information.

This will make healthcare and medical data on web easy to describe correctly (with their correct meaning and context), easy to expose /index so ready to be accessible and will highly improve to re-usability and exchanging in semantic way, with their correct meaning and context.

The intention is not to replace existing ontologies, nor making upper level ontology nor creating yet another clinical information model/standards. The aim is mainly to provide most useful and frequently used (so, demand driven) classes and properties related to the medical and healthcare domain. Within this scope all concepts are mapped as far as it's feasible to the existing terminology like SNOMED CT, ICD, LOINC, ATC, RxNorm, HL7 FHIR, etc.

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.

This community group is focused on bringing high performance computing (HPC) to the web. In particular, we're interested in making the computing and data resources that underlie simulation science, scientific computing, and data-centric science easily accessible through web browsers. Our members are working on APIs that expose HPC resources via the web, as well as gateways and web applications that take advantage of these APIs. The major goal of this community is to accelerate the pace of development of web-based HPC applications. Recognizing that we can build on each other's work, and that a consistent approach to developing such tools can enable features that require communication across multiple computing centers, we are interested in sharing technologies and ideas.

A group to work on APIs and other functionality related to rich-text HTML editing, such as (1) the contenteditable and designMode attributes (2)The execCommand(), queryCommandEnabled(), queryCommandIndeterm(), queryCommandState(), queryCommandSupported(), and queryCommandValue() methods on the Document interface (3) what exact effect user actions (such as typing text or hitting Enter) should have on rich-text editable regions (4) the Selection interface (5) spellcheck for rich-text editable regions, and (6) other functionality related to the foregoing. The group is expected to work on writing high-quality, detailed technical specifications suited for implementation by major browsers. It will start work with the preliminary specification hosted at http://aryeh.name/spec/editing/editing.html, and later add the Selection part of http://html5.org/specs/dom-range.html, both of which are currently developed entirely outside the W3C and are not close to interoperable implementation. The group's deliverables are expected to be submitted to the Recommendation track in the WebApps WG after they mature sufficiently.

Issues around the use of HTML in email - documenting what works, what doesn't, and considering ways to improve the situation

The HTML Tidy Advocacy Community Group ("HTACG") is dedicated to the continued support, development, and evolution of the HTML Tidy command line application and library. The Community in cooperation with the W3C aims to become the canonical release group for HTML Tidy, which has been without a stable, public release since 2008. The Community aspires to achieve the agreement and support of the original and current developers to this end. The Community will continue to develop HTML Tidy to adapt it to modern standards; to implement testing systems; and to implement robust build systems. The Community will also promote the continued relevance of HTML Tidy in modern software systems. This group will not publish Specifications.

The mission of the HTML5 Japanese Community Group includes the following: * to facilitate focused discussion in Japanese of the HTML5 specification and of related specifications * to gather comments and questions in Japanese about those specifications * to collect information about specific use cases in Japan 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 This Community Group is the successor of the HTML5 Japanese Interest Group. 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.

A group addresses and discusses proposed ideas for HTML5 specifications.

The HTTPS in Local Network Community Group (CG) explores the manner of secure communication between browsers and server-capable devices in local network such as set-top boxes, network attached storages, etc. We propose that this Community Group clarify requirements for browsers and devices in issuing valid certificates and establishment of HTTPS and WebSocket connections over TLS and incubate relevant specifications of APIs and/or network protocols. This work has four primary purposes:

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

Given wider support and adequate stability, we plan to migrate the proposals generated in this Community Group to an appropriate standards track, for example the IETF Standards Track or a W3C Working Group, for further contributions and formal standardization.

Goals

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.

Deliverables

To be determined.

Building Web APIs seems still more an art than a science. How can we build APIs such that generic clients can easily use them? And how do we build those clients? Current APIs heavily rely on out-of-band information such as human-readable documentation and API-specific SDKs. However, this only allows for very simple and brittle clients that are hardcoded against specific APIs. Hydra, in contrast, is a set of technologies that allow to design APIs in a different manner, in a way that enables smarter clients. The foundation is laid by the Hydra Core Vocabulary. It defines a number of fundamental concepts, such as hypermedia controls and collections, which allow machines to understand how to interact with an API. Since all information about the API is available in a machine-readable form, completely generic clients become possible. The Core Vocabulary is complemented by Linked Data Fragments, a set of specifications that enable advanced yet efficient client-side querying of Web APIs. More information about these technologies can be found on our homepage: http://www.hydra-cg.com/

The goal of this community group is to determine and publish best practices for access, activation, and display settings for captions with different types of Immersive Media - AR, VR & Games. We plan to research current examples, identify best practices, and do research on those ideas over different surfaces: Smartphone AR, AR glasses, VR goggles, etc. Where appropriate, we will share our results and discuss opportunities with the TTML WG (recommendations for media online captioning) and the W3C Immersive Web WG (APIs to interact with XR devices and sensors in browsers).

Our goal is to help bring high-performance Virtual Reality and Augmented Reality to the open Web.

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

The goal of the Interactive API Community Group is to develop an HTML annotation approach - similar in spirit and style to micro-formats - to equip a piece of UI (e.g., parts of a web page, such as a table or a sub-area) with a programmable interface (API). That is, the goal is to equip pieces of UI with dynamic and programmable behavior, so as to foster reuse on the Web and enable a set of web-based integration scenarios that are currently more the result of hacking and less of principled software development: programmatically operating UIs, extracting data, extracting application logic, and cloning pieces of UIs. The intuition is to design a new type of interpreted API, the so-called interactive API (iAPI), that enables (i) programmatic access to UIs and (ii) interactive, live programming. The purpose of iAPIs is not merely to provide access to static content inside a web page, but rather to bridge between the Surface Web (the UIs) and the Deep Web (common web APIs and web services). The concrete results this Group aims to produce are therefore: - An HTML annotation format for the specification of iAPIs; - An set of programming abstractions and code libraries for iAPI programming; and - A set of supporting browser extensions for iAPI parsing and instantiation. The final vision is twofold: first, to found a programming paradigm based on the reuse of UIs, i.e., UI-oriented computing; second, to enable interactive, live reuse to non-programmers directly inside the web browser.

The primary goal of the Interledger Payments Community Group is connecting the many payment networks (ledgers) around the world via the Web. The group's vision is an open, universal payment scheme built on Web standards that allows any payer to pay any payee regardless of the payer’s choice of payment instrument or the payee’s account.

The mission of the Interlinear Text Layout Community Group is to: (1) Document use cases and requirements for interlinear text practices. (2) Develop models for the representation of interlinear text. (3) Develop recommendations for other communities working on standards that could support interlinear text presentation requirements (e.g. HTML, CSS, etc.). The Interlinear Text Layout Community Group aims to serve a broad range of users engaging in manuscript digitization activities, linguistic annotation, multilingual annotation and related where representing interlinear text in web, ebook and related formats is either limited or not currently possible.

We choose which representations of our data to use, JSON, CSV, XML, or whatever, depending on habit, convenience, or the context we want to use that data in. On the other hand, having an interoperable generic toolchain such as that provided by XML to process data is of immense value. How do we resolve the conflicting requirements of convenience, habit, and context, and still enable a generic toolchain? Invisible XML (ixml) is a method for treating non-XML documents as if they were XML, enabling authors to write documents and data in a format they prefer while providing XML for processes that are more effective with XML content. This is an ongoing project to provide software that lets you treat any parsable format as if it were XML, without the need for markup.

JSON-LD (JavaScript Object Notation for Linking Data) is a lightweight Linked Data format that gives your data context. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on the already successful JSON format and provides a way to help JSON data interoperate at Web-scale. If you are already familiar with JSON, writing JSON-LD is very easy. These properties make JSON-LD an ideal Linked Data interchange language for JavaScript environments, Web service, and unstructured databases such as CouchDB and MongoDB.

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

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

This group brings together experts in the area of building information modelling (BIM) and Web of Data technologies to define existing and future use cases and requirements for linked data based applications across the life cycle of buildings. A list of recommended use cases will be produced by this community group. The envisioned target beneficiaries of this group are both industrial and governmental organisations who use data from building information modelling applications and other data related to the building life cycle (sensor data, GIS data, material data, geographical data, and so forth) to achieve their business processes and whom will benefit from greater integration of data and interoperability between their data sets and the wider linked data communities. For example, benefit may be obtained by publishing and combining localised data on new cheaper building materials, energy efficient building devices and systems, along with real time data on weather patterns, energy prices and geodata. By making this data available to applications, they will be better able to support decision makers during the whole of the building life cycle, which includes design, construction, commissioning, operation, retrofitting/refurbishment/reconfiguration, demolition, and recycling of buildings. The group will engage with these beneficiaries through surveys and events organised in conjunction with the affiliated workshop series on Linked Data for Architecture and Construction (LDAC).

The Linked Data for Accessibility Community Group’s mission is to make accessibility information about buildings, services and routes easier to find — everywhere where people need it. This is done (1) by creating a common and open standard vocabulary for accessibility and (2) by providing a central place for the web community to discuss issues around physical accessibility data. (3) This group may publish Specifications based on the outcome of (1) and (2).

This group aims to consult with current and potential users of linguistic data to assemble use cases and requirements for Language Technology Applications that use Linked Data. The results will be used to guide future interoperability, research and development activities spanning the language technology and linked data domains. Potential users are companies and public bodies involved in natural language processing, language resources, content management, the language services and localisation industry and other applications of content analytics techniques used in search, recommender systems, sentiment analysis and terminology management. The group does engage with users through surveys, international events and training activities organized in conjunction with partners from academia or industry, resp. designated research projects and networking efforts (esp., EU or other multi-national projects). We identify use case and requirements priorities, technology gaps and interoperability roadblocks. We work towards community group reports that describe our findings and/or solutions to the challenges identified in our work.

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 not publish specifications.

There have been several recent efforts to standardize vocabularies for describing locations, using existing geometry specifications. GeoSPARQL, NeoGeo and the EU ISA Programme's Location Core Vocabulary join schema.org's vocabulary and more. Is there a set of use cases that an usefully be served by greater collaboration in this space? What problems remain? Where are the awkward edges that need to be knocked into shape? The mission of the Location and Addresses Community Group is to review the existing efforts in this space (notably GeoSPARQL, NeoGeo, the EU's INSPIRE Directive and schema.org) and assess whether any use cases would be served by harmonization and/or new standardization work. This group may produce specifications or use cases and requirements documents, which may be proposed for adoption by the Government Linked Data (GLD) Working Group consistent with its charter (http://www.w3.org/2011/gld/charter).

This 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 dissemination

The Maps in HTML Community Group seeks to establish at least one hypermedia type which can be considered to be consumed by a (new) "map" element for HTML. Follow-on from Bar Camp at #lgd14. The objective will be to define a hypermedia type which can be linked to from a hypothetical (but prototyped in Web Components) "map" or (geo-map for Web Components) element which will provide simple mashup capabilities and user interface.

This group will publish specifications.

MathML first became a W3C recommendation in 1998. It has wide support in the publishing industry and with assistive technology. MathML has had several updates, but is showing its age and needs to be updated. This group will focus on changes to the MathML 3 recommendation so that it better aligns with the current web environment, eases the burden on browser implementations, and increases support for assistive technology. The group will propose a new revision for MathML, potentially with profiles for browsers, publishers, and other subgroups such as authors or online tests. The group will also develop tests so that authors/publishers can be confident that what they see as an author is what the user will see as a reader when the same font is used. Participation is encouraged if you are in involved in publishing, authoring, or rendering math. The group strongly encourages the participation of those involved with browser implementations, recommendations, and APIs that potentially affect the rendering of math.

The mission of Meat Products Community Group is to propose, discuss, create and maintain extensions to schema.org related to meat items commonly traded internationally.

The mission of this group is to define several APIs that provide a standardised method of processing, optimizing and delivering images and video over the web

This group will develop a specification defining how user agents should expose in-band tracks as HTML5 media element video, audio and text tracks so that Web applications can access the in-band track information, through the media element, in a interoperable manner across user agent implementations. Media formats of interest are MPEG-2 transport stream, WebM and MPEG-4 file format. Other media formats containing in-band tracks may be considered.

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 mission of this community is to be an incubator of optimizing Web technology for the merging of Web and mobile APP, and to develop related requirements and approaches.

Our mission is to bridge virtual worlds by designing and promoting protocols for identity, social graphs, inventory, and more.

The exploration and development of media containers that protect and serve the growing needs of the content creator. A media container with global tracking and accountability will ensure the upmost transparency and data management. The world needs a new media file that can meet the modern technological needs.

The purpose of this group is to connect the multidisciplinary (Social Science, Semantic Web, Information Retrieval, ...) research community interested in the study and treatment of low-effort user generated content on the Web (tweets, checkins, status messages, likes,...), called microposts. The objective of this community is to develop ways to leverage this massively growing, yet informationally poor source of data on the Web for different practical use cases. This group will not publish specifications.

MicroXML is a subset of XML intended for use in contexts where full XML is, or is perceived to be, too large and complex. MicroXML provides a set of rules for defining markup languages intended for use in encoding data objects, and specifies behavior for certain software modules that access them.

A community group to incubate work on MiniApps and serve as a base for analysis and proposals of specific work items

The Mixed Reality Service Community Group will work to define an open protocol that provides a mapping between geospatial or virtual coordinates and URIs. Mixed Reality Service has numerous applications in areas as varied as gaming, autonomous vehicles, health & safety, and affordances for the disabled. More details can be found at mixedrealitysystem.org This group will expand upon the work presented at WWW1, and re-introduced in a lightning talk at the initial WebVR meeting in October 2016.

The mission of this group is the discussion and investigation of the intersection of mobile and accessibility. A place to discuss emerging efforts, document needs and requirements and investigate emergent techniques and best practices. This group will not be developing any specifications.

The W3C India Office is setting up this Community Group on Mobile Web in Indian Languages with the objective of addressing the issues concerning with the enablement of mobile, smartphones and next generation wireless devices with Indian Languages support, seamless SMS and MMS sending and receiving in Indian Language , Uniform user experience on the mobile through using Indian Languages, and access to Indian Languages websites from mobiles. The goal is to achieve seamless access and operation irrespective of the mobile manufacturers and service providers. This group will help in building the ecosystem for enhancing the penetration of mobiles in the country to the rural areas using the Indian Languages enablement. The Group will also explore and develop the Indian Language requirements in existing and future Mobile Communication standards.

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

Timing mechanisms allow operations to be executed at the correct time. The Web already has several mechanisms supporting timed operations, including setTimeout and setInterval, as well as controllers for media frameworks and animations. However, the Web lacks support for multi-device timing. A multi-device timing mechanism would allow timed operations across Web pages hosted by different devices. Multi-device timing is particularly important for the broadcasting industry, as it is the key enabler for web-based secondary device offerings. More generally, multi-device timing has wide utility in communication, collaboration and multi-screen presentation. This Community Group aims to define a common, multi-device, timing mechanism and a practical programming model. This will improve the Web as a platform for time-sensitive, multi-device Web applications. Charter : http://webtiming.github.io

The mission of the Multicast web community group is to enable multicast IP transport for web traffic to efficiently solve scalability problems in networking and web operations. Please see the charter for details.

The Multidimensional Quality Metrics (MQM) Community Group fosters the development of MQM for translation and localization quality assessment and its interoperability with W3C’s Internationalization Tag Set (ITS) 2.0 recommendation. Membership is open to parties interested in contributing to or implementing MQM.

The objective is to produce specifications to facilitate the use and creation of multilingual web sites.

The Music Notation Community Group develops and maintains format and language specifications for notated music used by web, desktop, and mobile applications. The group aims to serve a broad range of users engaging in music-related activities involving notation, and will document these use cases.

The initial task of the Community Group is to maintain and update the MusicXML and SMuFL (Standard Music Font Layout) specifications. The goals are to evolve the specifications to handle new use cases and technologies, including greater use of music notation on the web, while maximizing the existing investment in implementations of the existing MusicXML 3.0 and SMuFL specifications.

A community driven take on the concepts driving the Widgets and Device APIs. Collectively understood these technologies form the basis for installable web apps. Living in a secured context these applications give the web access to traditionally native capabilities.

The objective of this community is to discuss the possibility of creating a schema to describe network maintenance notifications. This topic has received traction in the industry, and thus a standard should at least be discussed. Currently the industry is adopting embedded metadata within iCalendar attachments, as well as APIs. A standard could be used in both of these scenarios. This group may or may not decide to create specifications.

Welcome to the W3C Community Group for Network Friendly applications! In this group, we are looking for contributions to help us reach the widest possible consensus in a critical area facing the mobile industry. Smartphones and smartphone applications have established themselves as a major success story in the industry over the past few years. As the number of smartphones and smartphone applications has increased the industry has learnt much on how to create efficient applications for smartphones. The GSMA has created a set of guidelines for application developers that will enable improvements across a number of areas including application connectivity, power consumption, network reliability and security. By following these guidelines - Developers will be better equipped to create fit-for-purpose apps - Users will experience more responsive and reliable apps and improved battery life - Mobile operators will see a reduced strain on their networks For a copy of these guidelines check out http://www.gsma.com/go/download/file=gsmasmarterappsforsmarterphones0112v.0.14.pdf GSMA intends to issue an update of the above document by end of 2012. As such, it has compiled a list of items for inclusion in the update after consulting GSMA’s members; they include network operators and device manufactures. To ensure the new update will have the widest possible support by all communities across the industry, we have created a Community Group called ‘network friendly Developer guidelines’ under auspices of W3C. The new CG is formed with a view to engage other developers or interested parties and reach a consensus as what needs to be added beyond what has already been proposed by GSMA. The proposed items for inclusion are embedded in this document. Check out http://www.w3.org/community/networkfriendly/wiki/images/b/be/Proposed_items_for_inclusion_in_the_update.doc to download the current suggestions as approved by GSMA. As the update will be released by end of 2012, all changes should be agreed in time before the actual work of writing and editing the document starts in earnest and no later than 1st September 2012. That means the outcome of activities in the CG would be a list of items for inclusion beyond what has already been proposed by GSMA. The outcome would be considered by GSMA for inclusion when updating the document. In Brief, the goal and milestones to bear in mind are as follows. Goal To produce a set of items for inclusion in the updated document beyond what has already been suggested (see the enclosed document) Key milestones 19th April to 10th August 2012 to discuss the base document and the proposed updates and reach consensus in the CG on any additional proposals 11th August to 18th August is the cooling off period to take on board last minute suggestions and final touches 19th August to 31st August, GSMA will consider the final input from CG prior to commencing work on the update in September As a rule of thumb, the entire process would be transparent and inclusive to reach agreement by discussion. In the unlikely event of not reaching consensus on burning issues, the (yet to be named) CG chair would make the final decision only as a last resort. You are invited to actively engage with the process to make the resulting document much better than its debut version. We welcome views and contribution with an open mind.

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

Further development, implementation, and standardization of Notation 3 - an assertion and logic language - including the N3 Rules language.

The ODRL Community Group supports the promotion and future development of the W3C ODRL recommendations:

• ODRL Information Model
• ODRL Vocabulary & Expression

Specifically, the ODRL CG will:

• Promote ODRL V2.2 to existing and new sectors/industries
• Nurture an ODRL implementors community
• Publish reports related to ODRL usage
• Support development of ODRL Profiles (and host for smaller communities)
• Register ODRL Profiles
• Collaborate with W3C on ODRL errata maintenance
• Plan for future major enhancements to ODRL (V3.0)

[Web] Open Font Format for Exchange -- developing a list of recommendations and best practices in font development for best compatibility with web browsers

The mission of the Ontology-Lexicon community group is to: (1) Develop models for the representation of lexica (and machine readable dictionaries) relative to ontologies. These lexicon models are intended to represent lexical entries containing information about how ontology elements (classes, properties, individuals etc.) are realized in multiple languages. In addition, the lexical entries contain appropriate linguistic (syntactic, morphological, semantic and pragmatic) information that constrains the usage of the entry. (2) Demonstrate the added value of representing lexica on the Semantic Web, in particularly focusing on how the use of linked data principles can allow for the re-use of existing linguistic information from resource such as WordNet. (3) Provide best practices for the use of linguistic data categories in combination with lexica. (4) Demonstrate that the creation of such lexica in combination with the semantics contained in ontologies can improve the performance of NLP tools. (5) Bring together people working on standards for representing linguistic information (syntactic, morphological, semantic and pragmatic) building on existing initiatives, and identifying collaboration tracks for the future. (6) Cater for interoperability among existing models to represent and structure linguistic information. (7) Demonstrate the added value of applications relying on the use of the combination of lexica and ontologies.

The goal of this group is to create a library of open source JavaScript interactive widgets commonly used in STEM educational resources. The widgets will conform to WCAG guidelines and will provide interfaces to various educational technology APIs, such as Tin Can. Examples of commonly used widgets are interactive number lines used in assessments and EPUB 3 eTextbooks, physics simulations, interactive software code editors or graphing calculators that support sonification.

The purpose of the Open Annotation Community Group is to work towards a common, RDF-based, specification for annotating digital resources. The effort will start by working towards a reconciliation of two proposals that have emerged over the past two years: the Annotation Ontology [1] and the Open Annotation Model [2]. Initially, editors of these proposals will closely collaborate to devise a common draft specification that addresses requirements and use cases that were identified in the course of their respective efforts. The goal is to make this draft available for public feedback and experimentation in the second quarter of 2012. The final deliverable of the Open Annotation Community Group will be a specification, published under an appropriate open license, that is informed by the existing proposals, the common draft specification, and the community feedback. [1] http://code.google.com/p/annotation-ontology/ [2] http://www.openannotation.org/spec/beta/

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

A forum for the open network of open data enthusiasts, government officers, students, researchers, and a non-profit leader who are working to improve the condition of open data in Nepal. This space will help individual volunteers, groups, students to collaborate and discuss how one can help to boost the open data momentum in Nepal. This group will not have any criteria and specification, anyone can join and may reuse the group works. This group will not publish Specifications.

Forum where Spanish public bodies, citizens and industry involved in Open Data and PSI reuse are gathered together to discuss and seize synergies among them. This Group is an evolution of the "Grupo Zaragoza", a non-profit community, composed of all-governmental-level administrations and key players in PSI reuse, which has boosted the Open Data in Spain. Future and ongoing Open Data initiatives may reuse this group's work in terms of technology, formats, ontologies, tools, guidelines, etc. This group will not create specifications.

Our mission is to develop a universal RDF vocabulary to enhance open educational resources throughout the internet.

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

W3C 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. The roles and responsibilities of the chairs go as follows:

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

As a burgeoning and emerging area, open linked data for education is currently experiencing momentum across several initiatives and organisations including Open Education, LinkedUp, LinkedUniversities or LinkedEducation., and the Open Knowledge Foundation, to name just a few. We believe that we are now at a time when these efforts should converge, with this group representing a focus point for the community to collect, capture and adopt the practices that are going to be the foundation of the web of educational data. We therefore set the following set of goals for this group: 1. To collect from existing initiatives the practices currently used to share education-related data on the web. This includes the vocabularies that are employed as well as the ways in which common aspects of the data are being modelled with these vocabularies (e.g.course catalogues, resources, university facilities, research results). Further statistical analysis can provide sound guidance on vocabulary usage within the educational Web of data. 2. To identify common, best practices amongst those and document them (including concrete examples). 3. To facilitate the adoption of these common best practices, through direct interaction with community stakeholders, as well as through showing the benefits of the reuse of data modelling practices in application developments. While this has some similarities with the idea of “creating an ontology of education”, it is not what we are aiming to achieve. Education is very broad, and our goal is therefore rather to provide common “patterns” that use existing vocabularies for the representation of common education-related data. We do expect this to create resources of interest whenever our efforts will contribute to filling a gap, and to refer to other of such resources (such as LRMI for learning resources) in other cases. This group will not publish specifications.

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

The group will be researching components and controls across the web and also looking to native paradigms to bring interoperability for design systems, frameworks and the web platform.

This community group is part of the OpenActive initiative. Our goal is to develop technical specifications and best practices that will support the use of open and shared data relating to sports and physical activities.

Our primary focus is on standardising how to publish data about opportunities to be physically activity, defining best practices and APIs to enable booking of events and facilities, and improving interoperability of data across the sector.

To ensure that our specifications will support a variety of use cases, we welcome contributions from a range of organisations, including existing platforms and new startups.

While our work is technical, you don’t have to be a developer to contribute to our standards group. We are looking for input from product and service managers whose domain knowledge can help us to create better outputs.

This group aims to develop an open standard for interchange of data in Athletics (including Track and Field), running and related disciplines. Such a standard should allow the development of better software to manage the sport, resulting in major savings of time for volunteers; more efficient management of events and federations; and more enjoyment for participants and fans.

The mission of the Object Real-Time Communications Community Group, is to define Object-centric APIs (client-side at first) to enable Real-Time Communications in Web browsers, Mobile endpoints and Servers.

Everything related to the Web Ontology Language.

PDF has a reputation of being bad for 'open data', but there are already features of PDF that can be used for storing and retrieving data associated with parts of a PDF file, and more features coming. A draft charter will be posted soon.

Performing Arts Information Representation (PAIR) is a community group dedicated to advancing the use of shared conceptual models for better data interoperability in the performing arts domain. This domain stands to gain tremendous benefit from using Semantic Web technologies as it relies on the interoperability of information across many fields such as event publishing and discovery, digital archiving, and research (to name a few). The group’s mission is to support the development and use of semantic vocabularies and common representational frameworks to ensure the meaningful sharing and aggregation of information related to the performing arts. This Community Group provides a forum for the exchange of ideas and experiences, scenarios and requirements while bringing together key stakeholders. The group will act as an advocate for representational standardization in the performing arts sector. PAIR will strive to develop mutually beneficial collaborations with groups and organizations that are actively working on relevant standards and/or implementations. In particular, the group will work to develop extensions to existing representational standards such as Schema.org and Wikidata so that Performing Arts information can be better understood by search engines and other web applications. While designing, maintaining and revising vocabularies and foundational specifications for the performing arts, the group will make efforts to involve the performing arts community at large through solicitation of requests, comments and suggestions from non PAIR members. This may take the form of symposiums, workshops, events or community curated open resources.

The Permanent Identifier Community Group maintains a secure, permanent UL re-direction service for the Web located at w3id.org. Web applications that deal with Linked Data often need to specify and use URLs that are very stable. They utilize services such as the one run by this community to ensure that applications using their URLs will always be re-directed to a working website. The concept operates much like a switchboard, connecting requests for information with the true location of the information on the Web. Entries in the switchboard can be reconfigured to point to a new location if the old location stops working. The community is responsible for all administrative tasks associated with operating the service. The social contract between organizations involved in the community gives each of them full access to all information required to maintain and operate the website. The agreement is setup such that a number of these organizations could fail, lose interest, or become unresponsive for long periods of time without negatively affecting the operation of the site. The service operates in HTTPS-only mode to ensure end-to-end security. This means that it may be used for Linked Data applications that require high levels of security such as those found in the financial, medical, and public infrastructure sectors. All identifiers associated with the service are intended to be around for as long as the Web is around. This means decades, if not centuries. If the final destination for popular identifiers used by this service fail in such a way as to be a major inconvenience or danger to the Web, the community will mirror the information for the popular identifier and setup a working redirect to restore service to the rest of the Web. You may join this community by getting a W3C account and clicking the join button. If you wish to engage the community in discussion about this service for your Web application, please send an e-mail to the public-perma-id@w3.org mailing list. This group does not create specifications.

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

The initial mission of the Physical Ledger community group is to develop a Distributed Ledger Technology (DLT) that allows physical IoT devices to create, disseminate and store transactional data using the web technologies. The group develops a technical specification and produce sample codes. The ideal members are those who has skills in Web technologies and have interests in the IoT technologies.

Place data has many uses, including augmented reality browsers, gazetteers, location-based social networking games, geocaching, mapping, navigation systems, and many others. In addition, the group will explore how the geospatial industry could best use, influence and contribute to Web standards.

A problem with terms of service agreements is that they often require an all-or-none acceptance or rejection. In addition, they may be in a form that is not accessible to persons with disabilities making it difficult to make an informed decision. The mission of this community group is to find ways that help users understand what they are being asked to commit to, and to provide a finer grain of control in terms of what they are willing to share. The overall goal is to put control of personal data into an individual’s hands. The group's primary activity is to discuss and report on how to make terms of service agreements comprehensible to users and to provide a means by which users can express their preferences regarding their personal data. The reports may include descriptions of use cases, user interface wire frames, plain language proposals, and supports that educate users about personal data and data sharing. The group will define a way for users to express preferences regarding the collection, use, and disclosure of their personal information. These preferences will be "portable" in the sense that they are encoded once and can be used on a variety of platforms including websites, desktops, and mobile devices, among others. People interested in educating users regarding personal data and data sharing, inclusive user interface design, and the use of plain language in policies and service agreements are welcome. This group may publish specifications. Charter (WIP): https://inclusive-design.github.io/cg-portable-personal-data-preferences/CGCharter.html

W3C is a global community where participants choose to work together. In that community, we experience differences in language, location, nationality, and experience. In such a diverse environment, misunderstandings and disagreements happen, and in most cases can be resolved informally. This CG will pick up the work of the PWE Task Force (https://www.w3.org/Consortium/pwe/) focusing on the Code of Ethics and Professional Conduct.

The Print & Page Layout Community Group is open to all aspects of page layout theory and practice. We can and will cover everything from the Crystal Goblet through to specifications and on to the nitty-gritty of writing stylesheets. You will find XSL-FO and CSS discussed here, but you will also find other stylesheet languages, and all are equally welcome.

The mission of the Privacy Community Group is to develop privacy-focused web standards and APIs to improve user privacy on the web through enhanced browser behavior. Charter: https://privacycg.github.io/charter.html

The Private User Agent Community Group is chartered to improve user privacy and user control by designing the User Agent to minimize fingerprinting and to improve the control the user has over information shared over the Web and to improve the security of the User Agent in these regards. The group seeks to standardize the designs necessary to achieve these goals, to develop extensions designed for privacy to mitigate inevitable losses of functionality, to foster consideration of privacy in the design of other Web standards, and to discuss and develop implementations and test suits. Mechanisms for expressing user privacy preferences to servers and content provides are outside the scope of this group.

WEB OF PRODUCT TRACEABILITY This is the landing page for Web of Product Traceability Community Group. In the modern commercial society, product traceability is an important technical system to support the business credit of enterprises.Product traceability is also widely used in product quality supervision, modern logistics, financing Mortgage, commercial consumption and other fields. Therefore, many countries and organizations attach great importance to the development of Traceability Technology. Many independent traceability systems have been built by different countries and organizations. Uniform standards will help to improve the interconnection between them. With the development of technology, two-dimensional code has gradually replaced the commodity bar code, and the data contained in the RFID tag can reach 64K bytes, or even more.The article code based on URL is compatible with traditional GS. 1 commodity code and other coding systems.Therefore, an open product traceability network can be established from bottom to top based on WWW technology. Master data, transaction data and event data can be described by XML / JSON technology. Technologies such as Internet of things and blockchain will also play an important role in the network.The web of product traceability community is aims to build an open traceability network that can run on the public Internet.The original closed traceback network will not disappear, they can access to the open network as an autonomous domain.In the field of product traceability, there are also problems of data mining and information security. The community is aims to build various application models and interfaces to mine the value of traceability data.In order to ensure that the traceability data is not leaked, the community also needs to formulate corresponding information security standards to strictly control the access rights of traceability data. This will be a very promising and exciting work. We expect more enterprises and experts to join in and build an open traceability network.

This group will explore the Property Graph data model and API and decide whether this area is ripe for standardization. Property Graphs are used to analyze social networks and in other Big Data applications using NoSQL databases. The group may want to investigate several extensions to the data model. For example, should nodes be typed; what datatypes are allowed for property values; can properties have multiple values and should we add collection types such as sets and maps to the data model? At the same time, we need to bear in mind that there are several Property Graph vendors and implementations and we may not want to deviate significantly from current practice. Existing Property Graph APIs are either navigational e.g. Tinkerpop or declarative e.g. Neo4j. For a W3C standard we may want to design a more HTTP and REST-oriented interface in the style of OData Protocol and OData URL Conventions. In this style, you construct URls for collections of nodes and edges. For example, a GET on http://server/nodes would return the collection of nodes on the server. A GET on http://server/nodes/in(type = ‘knows’ ) would return the collection of incoming arcs with type = ‘knows’ and a GET on http://server/nodes/out(type = ‘created’ ) would return the collection of outgoing arcs with type = ‘created’. Once a collection of nodes or arcs is selected with the URI, query operators can be used to add functions to select properties to be returned. Functions can also be used to return aggregate properties such as count and average. The group will deliver a recommendation to the W3C regarding whether and how the Property Graph work should be taken forward towards standardization.

The goal of this CG is to develop specs to describe an object model for Publications (think EPUB, PDF, OOXML, and other complex friends) that hides the complexity of package, metadata and resource access inside those formats. A secondary goal is the development and release of a multi-purpose framework, in at least JavaScript and if possible c++ too, implementing those specs.

Incubation zone for Publishing@W3C. Bring your experiments here.

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

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

The RDF JavaScript Libraries Community Group discusses implementations of libraries for working with RDF and Linked Data in ECMAScript platforms like Web browsers and Node.js

The mission of the RDF Stream Processing Community Group (RSP) is to define a common model for producing, transmitting and continuously querying RDF Streams. This includes extensions to both RDF and SPARQL for representing streaming data, as well as their semantics. Moreover this work envisions an ecosystem of streaming and static RDF data sources whose data can be combined through standard models, languages and protocols. Complementary to related work in the area of databases, this Community Group looks at the dynamic properties of graph-based data, i.e., graphs that are produced over time and which may change their shape and data over time.

The purpose of this group is to provide a home for the test suites and implementation reports of various Semantic Web/Linked Data specifications. After the end of a working group, the test suites often become frozen, and it is difficult to add new tests for issues that come to light later on. Similarly, some specs are implemented on a base technology, which eventually evolves (e.g. SPARQL 1.1 and RDF 1.1), and developers need access to updated tests. This group will create a home for forks of the various test suites that would be appropriate to act as a redirect for existing tests. Test updates will be considered based on the consensus of those invested in the related specifications. Implementation reports can be updated as new reports are received, giving implementations visibility. This group will not publish Specifications.

RDF-DEV, for developments relating to W3C RDF, including collaboration around applications, schemas, and past/present/future related standards. Successor to SWIG/RDFIG.

The activity of this group is to apply Web standards to trusted read and write operations.

The goal of this community group is to establish reliable Public Key Infrastructure on the Internet in a privacy-preserving way by allowing people and organizations to link their various public and semi-public accounts to cryptographic key materials at their own will.

Research investigations are increasingly collaborative and require ‘‘borrowing strength’’ from the outputs of other research. Conventional digital publications are becoming less sufficient for the scientists to access, share, communicate, and enable the reuse of scientific outputs. The need to have a community-wide container data model to encapsulate the actual research data and methods with all the contextual information essential for interpreting and reusing them is becoming more and more imperative, for the science, publisher, as well as digital library communities. A number of different community groups and projects are now creating some form of container, bundling or aggregation mechanism (particularly using ORE OAI), partially driven by the above goal. There is a clear need and benefit to facilitate a consensus among these representations. In the ROSC community group we aim to provide an open platform for gathering and discussing current development of various container models and their implementations. These data models should be driven by the need of facilitating the reuse and exchange of the actual digital knowledge and the inspection of the reproducibility of scientific investigation results. They should consider not only the data used, methods employed to produce and analyse that data, but also the people involved in the investigation and annotations about these resources, which are essential to the understanding and interpretation of the scientific outcomes. As outcomes from the community group we aim to facilitate the establishment of a community data model and a set of community agreements that can effectively assist the establishment of a new form of scholarly communication, that is a prominent issue of today. This group will not publish specifications.

Our goal is a markup-based means of delivering alternate image sources based on device capabilities, to prevent wasted bandwidth and optimize display for both screen and print. Note: When the group expanded its scope in November 2014, it changed the name from "Responsive Images" to "Responsive Issues."

The mission of this group is to create a new ontology to describe restaurants, and reservations to those restaurants. The ontology will support queries such as:

• 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!)

The Restricted Media CG will discuss and analyze methods of restricting access to or use of Web media, and their implementation on the open Web. This group will not publish specifications.

The aim of the Rights Automation for Market Data Community Group is to develop and publish a market-data profile for ODRL.

Market data is mostly the pricing and trading data for financial instruments (and their associated indices) generated by trading venues. The licenses controlling its use are frequently complex, and tightly segment the underlying data.

We will model these licenses using ODRL and extend the language with a profile that defines the new terms required. This group will publish Specifications.

With a standard, machine-readable way of describing market data licenses, we can look towards automating rights-management along the market data supply chain and drive efficiencies in financial markets.

The group welcomes the involvement of domain experts in licensing (especially market data) and those skilled in modeling licenses (especially using ODRL).

If you are not a group participant you can still subscribe to our list.

The goal of this community is to design web architecture and specifications to mitigate problems such as link rot, content drift, Internet censorship, and denial-of-service attacks. If, after following a hyperlink, the content is missing or not what you expected, we want it to be easier to find what you were looking for.

The mission of this group is to discuss and prepare proposal(s) for extending Schema.org schema for the improved representation of digital and physical archives and their contents. The goal being focused upon the creation and future maintenance of an archive.schema.org extension.

The mission of this group is to discuss and prepare proposal(s) for extending Schema.org schemas for the improved representation of bibliographic information markup and sharing. The group will seek consensus around, and support for, proposal(s) to the W3C WebSchemas Group. This Community Group will not, itself, produce technical specifications.

This mission of this group, initiated by LRMI, is to develop an extension for schema.org concerning the discovery of any type of educational course (online/offline, long/short, scheduled/on-demand). Educational course is defined as "some sequence of events and/or creative works which aims to build the knowledge, competence or ability of learners". (Out of scope: information about students and their progression etc; information needed internally for course management rather than discovery).