Community & Business Groups

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

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.

• 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

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

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

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

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

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

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

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

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

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

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

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

• Cognitive AI CG GitHub Repository

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

• An older talk on Cognitive AI and the Sentient Web

• Longer treatise on Cognitive AI

• Public mailing list archive

• Contributing to the Cognitive AI Community Group

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

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

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

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

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 HTML5 Korean Community Group includes the following:

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

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

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

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.

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.

The mission of the W3C Inclusion and Diversity Community Group (ID CG) is to increase the presence of under-represented groups at the W3C, and strengthen W3C culture by supporting diversity. To serve this mission, the CG will:

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

This group will not produce Specifications.

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.

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

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.

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)

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

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.

• 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 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 mission of this group is to gather and incubate new features and requirements for SVG — making it easier for software developers and content creators in the SVG community to engage with the SVG standardization process.

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

This group may publish specifications.

See the SVG CG charter for more information.

The mission of the Schema Generator Community Group is to improve the availability, discovery and innovation of RDFa, Microdata, JSON-LD and other structured data related tooling. Schema generation tools pertaining to this group aim to ensure output can be validated with the W3C Schema validator or similar tools.

The group will assist others with discovering existing tools, updating online materials to find tools and supporting the development of new tools. The goal of this group is to foster the development of the ‘web of data’ through developer support, community engagement and advocacy. The Schema Generator Community Group will also assist by incubating support for works that include, but are not limited to, new RDF-related tools.

The mission of the Second Screen Community Group (CG) is to explore, incubate, and define interfaces that enable new multi-display and multi-window computing user experiences on the Web. This Community Group defines new additions to the Presentation API and Remote Playback API, and incubates the Screen Enumeration, Window Placement and Window Segments Enumeration APIs.

In this group we work on various web technologies needed for managing all kinds of economic relationships between individuals and organizations. While recognizing nowadays dominance of commerce, we take here more general approach which gives equal attention to all kind of non-commercial approaches, including Social Economy, Sharing/Collaborative Economy, Solidarity Economy, Informal Economy etc.

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

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

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

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

Relevant W3C Domains and Activities

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

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

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

Relevant non W3C Groups

• Open Value Network
• OuiShare Labs

The Solid project aims to improve privacy and data ownership on the Web through a proposed set of conventions and tools for building decentralized social applications.

The mission of the Solid Community Group is to try to reshape the web by fostering a new breed of applications with capabilities above and beyond anything that exists today. Participants in this group will create applications, author technical specifications, and capture best practices.

Participants in this group who contribute to the Solid code base should also review the guidelines and best practices for contributing to the Solid project.

This group will publish Specifications.

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

Much is said about the mismatch between the needs of employers for qualified employee candidates and a pool of available candidates. One major factor contributing to this mismatch is the signaling between the demand-side (i.e., employers) and supply-side (i.e., education, training and credentialing providers, students and workers) of the talent pipeline. This mismatch frequently results in neither party coming into view of the other. The goal of the Talent Marketplace Signaling (TalentSignal) Community Group is to assist Schema.org in improving workforce signaling by refining existing schema.org types serving the talent pipeline and suggesting new types and properties where improved signaling cannot otherwise be achieved. Currently, workforce signaling sits at the intersection of a number of existing schema.org types: Course, JobPosting, Occupation, Organization, Person and the proposed EducationalOccupationalCredential.

The TalentSignal Community Group will focus initially on refinement of the JobPosting Schema and related types as it survey's specifications from domain entities such as HR Open Standards and PESC as well as the US Chamber of Commerce Foundation's Job Data Exchange (JDX) and T3 Innovation Network initiatives for better means to strong, more effective supply- and demand-side signaling.

Bluetooth is a standard for short-range wireless communication between devices. This group is developing a specification for Bluetooth APIs to allow websites to communicate with devices in a secure and privacy-preserving way. In particular the web Bluetooth API focuses on minimizing the device attack surface exposed to malicious websites, possibly by removing access to some existing Bluetooth features that are hard to implement securely. Further, the API takes the approach of a user interface to select and approve access to devices as opposed to using certification and installation.

Most of our activity happens in our GitHub repository, with supporting code in adjacent repositories in the WebBluetoothCG GitHub organization.

Media web application developers want to deploy their content on a wide and heterogeneous range of devices and platforms, e.g. televisions, set-top boxes, and mobile devices. To ensure a smooth user experience across devices, these user agents need to support a minimum set of Web technologies that developers can rely on being supported. This Community Group plans to specify such a set of Web technologies and additionally plans to provide guidance for developers and implementers e.g. on performance constraints and portability issues.

See the CG charter for more information.

The Web NFC Community Group will create a Near Field Communication API that is browser-friendly and adheres to the Web's security model. We believe that means the API will not expose full, low level NFC functionality, but rather a higher level subset that is safe for Web pages, protects user privacy, and does not annoy users with unnecessary or complex permission requests. See the Web NFC Community Group Charter and the Web NFC specification for more information.

1. Define a WebSocket sub-protocol for the Web of Things, using the W3C “Web of Things (WoT) Thing Description” data model and operations
2. Define an HTTP protocol binding for the Web of Things (or support the Web of Things Working Group in defining this protocol binding and ensuring consistency with the WebSocket sub-protocol where appropriate)
3. Evaluate other potential Web of Things protocol bindings (e.g. CoAP)

This group aims to encourage uptake of Web Video Map Tracks (WebVMT) to help establish an online ecosystem of users and developers by providing a forum in which to:

• identify & refine use cases;
• ensure that the design is fit for purpose;
• resolve implementation issues;
• develop supporting documentation & tools;
• progress towards standardisation.

Participation is welcomed by anyone providing constructive input regarding these topics within the scope of 'synchronising geolocation with video for the web', and by those with relevant expertise in particular.

See also:

• www.webvmt.org
• Editor's Draft

The group aims to agree extensions to the XSLT 3.0 Recommendation published on 8 June 2017, along with supporting changes to the other specifications (XPath, Functions and Operators) on which it depends.

A preliminary proposal describing requirements for such extensions can be found in Michael Kay's Proposal for XSLT 4.0 published in the Proceedings of XML Prague 2020

It is intended that the group will operate primarily by use of email and forums but may hold a face-to-face meeting to resolve issues prior to final publication of a specification.

The group may publish specifications.