Skip to toolbar

Community & Business Groups

  • Mixed Reality Service

    (61 participants)
    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.
    Join group Report a problem
  • Physical Ledger

    (8 participants)
    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.
    Join group Report a problem
  • XPath Next

    (8 participants)
    Create a place for gathering requirement from existing user of XPath, potential user of XPath and research in this area
    Join group Report a problem
  • Open Science

    (16 participants)
    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)
    Join group Report a problem
  • Distributed User Interfaces

    (10 participants)
    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.
    Join group Report a problem
  • Schema Generator

    (18 participants)

    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.

    Join group Report a problem
  • Data on the Web Best Practices

    (22 participants)
    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.
    Join group Report a problem
  • HTTPS in Local Network

    (41 participants)
    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.
    Join group Report a problem
  • Enterprise Ethereum

    (24 participants)
    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.
    Join group Report a problem
  • Schema.org for datasets

    (41 participants)
    Focussed on improving interoperability between schema.org's DCAT-based approach to dataset description and related approaches e.g. CSVW, VoID, Data Cube, R2RML, SpatialWeb, DCAT-AP and others including liaison to any new W3C work.
    Join group Report a problem
  • Declarative WebVR

    (41 participants)
    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
    Join group Report a problem
  • Web Media API

    (44 participants)

    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.

    Join group Report a problem
  • PDF and Open Data

    (17 participants)
    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.
    Join group Report a problem
  • Blockchain Digital Assets

    (39 participants)
    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.
    Join group Report a problem
  • experimental protocols

    (11 participants)
    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.
    Join group Report a problem
  • SPARQL Maintenance (EXISTS)

    (15 participants)
    The "SPARQL Maintenance (EXISTS)" Community Group is a forum to discuss and address problems with the "EXISTS" feature in SPARQL 1.1. The SPARQL 1.1 suite of specifications and the SPARQL 1.1 test suite are frozen. A process exists to record errata and that will be one input to any working group chartered to revise SPARQL. In the meantime, SPARQL is being used in real-work systems in industry and public-sector. The user community expects a high degree of conformance across implementations. The EXISTS feature has been found to be problematic. This feature is used by the RDF Data Shapes Working Group. This community group will create CG Notes and accompanying test suites to describe one or more improvements with an emphasis on maintaining compatibility. This group is not producing specifications. Any tests produced by the will submitted to the RDF Test Suite Curation CG for long-term stewardship.
    Join group Report a problem
  • Smart Manufacturing

    (12 participants)
    The mission of this community group is to extend schema.org vocabulary through introducing the necessary classes and properties for semantic description of the manufacturing capabilities of Small-to-medium sized manufacturing companies. The group members come from a variety of backgrounds from the government, academia, and industry.
    Join group Report a problem
  • Accessible Playlist

    (11 participants)
    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).
    Join group Report a problem
  • RDF and XML Interoperability

    (33 participants)
    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.
    Join group Report a problem
  • Hardware Based Secure Services

    (34 participants)
    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....
    Join group Report a problem
  • Data Pipelining Use Cases

    (24 participants)
    Gathering requirements and discussing data pipelines (think XProc but for JSON, HTML, text, XML, binary, EPUB...)
    Join group Report a problem
  • Meat Products

    (13 participants)
    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.
    Join group Report a problem
  • Web We Can Afford

    (60 participants)
    Most scientists now seem to agree that we've entered a new epoch dubbed the "Anthropocene", where the environmental consequences of human development have a tremendous impact on Earth's equilibrium. Those effects are already set in motion and will have far-reaching consequences in the coming years despite all the measures we could take to mitigate them (considering we simply do not fail to take action). While trying to avoid some of the consequences of the Anthropocene is an issue that is well-worth striving for, another task would be to reconsider the design of things at the time of the Anthropocene and that includes the Web. For instance, a 2008 study by the University of Dresden stated that if no measure was taken, the energy needed to power the infrastructure of the Web in 2030 would be tantamount to the energy consumed by humanity in 2008. The agendas of the stakeholders who are trying to set the Web forward in motion are mainly focused on adding new technological layers to the existing ones. Yet, the logic behind these developments remains that of tapping into unlimited resources, not limited ones. Lots of endeavors are currently focused on reshaping the Web into a "Web we want", a redecentralized open Web fit for an enlightened digital age. Those who advocate such an agenda and those who oppose it generally both share a common assumption: that enlightened or not, the future will be even more digital than the present. Yet, life at the time of the Anthropocene, at least in the coming decades, might not remain as pervasively digital as it is today. Other efforts that see the ongoing battle for the decentralization of the Web as an opportunity to “downscale” it (in particular in Africa) seem to be aware of that. Maybe it's time to take into account other perspectives on the future and concretely act towards building a sustain-able (Tony Fry) Web. In other words, a Web We Can Afford. This group would like to reconcile the development of the Web and an awareness to the environmental issues by appealing to Web architects and designers, eco-designers, activists, philosophers, social scientists, etc., so as to make the issue a public one to begin with, before devising a set of guidelines as a first step towards concrete action.
    Join group Report a problem
  • Schema Course extension

    (46 participants)
    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).
    Join group Report a problem
  • The Tourism Structured Web Data

    (52 participants)
    The mission of this group is to discuss and prepare proposals, examples, and best practice guidance for the sharing, via the web, structured data descriptions of resources associated with the tourism industry. Initial focus will be on extending Schema.org schemas for the improved representation of tourism related information markup and sharing. The group will seek consensus around, and support for, proposal(s) to be made to the Schema.org community.
    Join group Report a problem
  • Scholarly HTML

    (54 participants)
    The mission of this group is to build a common, open format for the exchange of scholarly information.
    Join group Report a problem
  • Open knowledge-driven service-oriented system architectures and APIs (KiSS)

    (14 participants)
    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.
    Join group Report a problem
  • Financial Industry Business Ontology

    (55 participants)
    The mission of Financial Industry Business Ontology Community Group is to propose, discuss, create and maintain extensions to schema.org related to Financial Industries.
    Join group Report a problem
  • DataSheets

    (5 participants)
    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.
    Join group Report a problem
  • Publications Object Model

    (14 participants)
    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.
    Join group Report a problem
  • Technical Documentation in the Semantic Web

    (11 participants)
    The complexity of machines and software has grown dramatically in the past years. The technical documentation became a fundamental source for service technicians and professionals in their daily work. Fast and focused access methods are necessary to handle massive volumes of technical documents. Semantic technologies have proven their ability to improve accessibility of information (see Linked Open Data). However, existing corpora of technical documents are usually not semantically prepared. This group shall focus on applying semantic technologies to technical documentation. All peers (individuals or projects) can state their needs (input) and offers (output).
    Join group Report a problem
  • Advancing Web Platform Application Testing

    (28 participants)
    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.
    Join group Report a problem
  • Machine Learning Schema

    (58 participants)
    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
    Join group Report a problem
  • Social Economy

    (21 participants)

    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

    Active Groups Inactive Groups

    Relevant non W3C Groups

    Join group Report a problem
  • RDF Test Suite Curation

    (21 participants)
    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.
    Join group Report a problem
  • LDP Next

    (36 participants)
    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.
    Join group Report a problem
  • Schema Architypes

    (64 participants)
    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.
    Join group Report a problem
  • Sport Schema

    (21 participants)
    The purpose of this group is to propose an expanded vocabulary for describing sporting information within schema.org. The goal is to create a proposal which will build on the existing vocabulary within schema.org updating or adding only where needed. The group should leverage existing work in the area of sport vocabularies, thinking globally with a focus on supporting the 'head' of sports vocabularies while keeping in mind the 'body' and 'tail'.
    Join group Report a problem
  • Exposing and Linking Cultural Heritage data

    (20 participants)
    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.
    Join group Report a problem
  • Automotive Ontology

    (88 participants)
    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.
    Join group Report a problem
  • Restaurant Ontology

    (14 participants)
    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!)
    Join group Report a problem
  • Annotation UX

    (27 participants)
    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.
    Join group Report a problem
  • Wearable Web

    (12 participants)
    User devices are getting smaller, and more of them are now wearable: smart glasses, smart watches, and smart clothing are all working their way into our lives and onto our bodies. These devices are online, web-accessible, and increasingly interconnected. The desirable mission of this group is to investigate the technical standardization issues for web technology on wearable devices and IoWT(Internet of Wearable Things) environment.
    Join group Report a problem
  • Accessible Online Learning

    (134 participants)

    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.

    Join group Report a problem
  • Federated Infrastructures

    (18 participants)
    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.
    Join group Report a problem
  • HTML5 Korean

    (52 participants)

    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.

    Join group Report a problem
  • Extensible Data Model Declaration Language for Education

    (11 participants)
    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.
    Join group Report a problem
  • Exposing IEEE LOM metadata as Linked Data

    (7 participants)
    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.
    Join group Report a problem
  • Multi-device Timing

    (26 participants)
    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
    Join group Report a problem
  • HTML Tidy Advocacy

    (11 participants)
    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.
    Join group Report a problem
  • HTML5 Japanese

    (66 participants)
    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.
    Join group Report a problem
  • Benchmarking for the Web

    (9 participants)
    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.
    Join group Report a problem
  • Colour blindness accessibility

    (20 participants)
    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.
    Join group Report a problem
  • Browsers and Robotics

    (18 participants)

    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.

    Join group Report a problem
  • Agriculture

    (61 participants)
    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.
    Join group Report a problem
  • Character Description Language

    (21 participants)
    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
    Join group Report a problem
  • Human Services

    (32 participants)

    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.

    Join group Report a problem
  • Browser Sync

    (12 participants)
    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.
    Join group Report a problem
  • Robustness and Archiving

    (11 participants)
    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.
    Join group Report a problem
  • TV Control API

    (43 participants)
    The convergence of Internet-based IPTV, Video-on-Demand (VoD), Personal Video, IP multicasting video, cellular multicasting video etc. with traditional broadcasting video, satellite video and cable video is emerging on market. The technology gap between web apps and native apps is rapidly narrowing. Thus a web-based application controlling various TV channels with detailed information regarding TV programs is becoming a more and more main stream TV control application for the integrated video service. Furthermore, in many regions TV broadcasters are developing web applications that can overlay their channel in a hybrid broadcast/broadband environment. Scope of Work The W3C TV Control API Community Group is to define an API layer that is agnostic of any underlying video sourcing technologies to enable a web-based application to: - provide EPG information, including the list of TV programs and related information such as channel number, producers, directors, actors, synopsis, rating etc., - control and switch the TV sourcing based on channel identifier from EPG data - interact with TV platform for presenting the TV program appropriately - interact with TV platform for presenting other supplemental content appropriately The underlying video sourcing method and technologies, the presentation technology and/or presentation application of TV program and supplemental content are all out of scope. Operating Guidelines This group operates under the rules of the Community and Business Group Process. All matters relating to intellectual property are governed by the Community Contributor License Agreement (CLA). All participants within this group agree that their discussions will follow the General Communications Policies.
    Join group Report a problem
  • Collaborative Software

    (24 participants)
    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.
    Join group Report a problem
  • ORTC (Object Real-time Communications)

    (105 participants)
    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.
    Join group Report a problem
  • Declarative Linked Data Apps

    (64 participants)
    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.
    Join group Report a problem
  • Webize Everything

    (13 participants)
    "The web is extended in two ways - by adding new bits of technology to the existing stuff, and by 'webizing' existing applications and systems. Webizing is really important, not only as a way of bootstrapping the web using large amount of legacy information, but because the existing systems have been researched and designed over the years and it is really important we do not lose the knowledge accrued during that process." --Tim Berners-Lee http://www.w3.org/DesignIssues/Webize.html This Group aims to webize as many existing systems and applications as possible, and is committed to producing 5 star linked data, in line with the original vision of the web. This group will not publish specifications.
    Join group Report a problem
  • Chinese Digital Publishing

    (29 participants)
    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.
    Join group Report a problem
  • Linked Data Models for Emotion and Sentiment Analysis

    (42 participants)
    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.
    Join group Report a problem
  • SVG Streaming

    (6 participants)
    This group will work on developing guidelines and possible extensions to the SVG language enabling the authoring of streamable SVG content, in particular for the creation of streamable cartoon animations, synchronized graphically-rich karaoke, or synchronized graphical overlays on top of video streams.
    Join group Report a problem
  • Media Resource In-band Tracks

    (11 participants)
    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.
    Join group Report a problem
  • Open and Interactive Widgets for STEM

    (4 participants)
    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.
    Join group Report a problem
  • Stereoscopic 3D Web

    (9 participants)
    The Stereoscopic 3D Web Community Group is focused on determining the requirements, available options, and use cases for the addition of stereoscopic depth into the W3C technology stack. The group also evaluates areas where S3D can be interesting to apply focusing on perception and interaction in different scenarios. The main objective is to evaluate the necessary requirements for a successful implementation of a declarative approach to stereoscopic 3D depth as part of HTML documents.
    Join group Report a problem
  • Traffic Event Ontology

    (10 participants)
    The mission of this group is to design a set of vocabularies and ontologies used to represent road/traffic event and accident data, i.e. involving Event, Vehicle, Juridiction, Accident, Persons, Environment, etc. We plan to re-use existing schema when possible.
    Join group Report a problem
  • Property Graphs Model and API

    (21 participants)
    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.
    Join group Report a problem
  • Federated Identities for the Open Web

    (16 participants)
    The mission of this group is to propose new APIs that allow for secure identity federation across domains on the open web.
    Join group Report a problem
  • Age Labels Data Model

    (9 participants)
    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.
    Join group Report a problem
  • OFF/X

    (4 participants)
    [Web] Open Font Format for Exchange -- developing a list of recommendations and best practices in font development for best compatibility with web browsers
    Join group Report a problem
  • Electronic Governance (eGov)

    (53 participants)
    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.
    Join group Report a problem
  • Ubiquitous Application Design

    (23 participants)
    People are looking to use applications and services on a ubiquitous range of devices. For developers, this raises the challenge of tailoring the user experience according to the device and context in which it is used. Application development teams involve a wide range of roles and skills: business requirements, information systems, usability and accessibility, graphical design and brand management, as well as the expertise required for specific target platforms. This Community Group seeks to bring together developers and researchers to explore and promote techniques for context aware design that separates out different aspects of design to speed development and reduce costs. We will do this through gathering and discussing techniques, together with developing open source demonstrators.
    Join group Report a problem
  • Argument Representation

    (6 participants)
    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.
    Join group Report a problem
  • Algorithmic Modelling

    (18 participants)
    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.
    Join group Report a problem
  • Best Practices for Multilingual Linked Open Data

    (73 participants)
    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.
    Join group Report a problem
  • Restricted Media

    (37 participants)
    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.
    Join group Report a problem
  • Open Government

    (81 participants)
    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.
    Join group Report a problem
  • Interactive APIs

    (16 participants)
    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.
    Join group Report a problem
  • Emergency Information

    (46 participants)
    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.
    Join group Report a problem
  • Haptic Interaction on the Web

    (11 participants)
    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/
    Join group Report a problem
  • Accessibility in India

    (119 participants)
    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.
    Join group Report a problem
  • Open Data Spain

    (53 participants)
    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.
    Join group Report a problem
  • Web Dev Data

    (10 participants)
    This group intends to analyse web development data from around the world and publish monthly reports. By leveraging open source tools, we hope to create an open source project to do this. This group does not plan to publish specifications that require patent commitments.
    Join group Report a problem
  • Extensible Web

    (44 participants)
    The Extensible Web Community Group is an incubator for web technologies enabling authors to extends the native web technologies via scripting (ie: shims & polyfills).
    Join group Report a problem
  • Cartography

    (9 participants)
    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.
    Join group Report a problem
  • Change Tracking Markup

    (22 participants)
    The mission of this group is to develop a proto-spec for marking up changes to documents.
    Join group Report a problem
  • SVG Mapping

    (11 participants)
    The mission of SVG Mapping Community Group (SVGMapCG) is to build requirements for SVG based Web Mapping through a discussion of use cases regarding map services. One of the key technologies for SVG Web Mapping is dynamic Tiling & Layering, which realizes zoom and pan display of maps in an efficient manner. The other technologies for the mapping (e.g. Shared Path, Vector Effects and etc.) are also necessary. Although these functionalities will be standardized as part of SVG 2 in SVG WG, the focus of discussion is for general use and the discussion may lack particular aspects for map services. Therefore, our main scope is to investigate whether these generic functions are enough or not to resolve challenges inherent in mapping, and to provide WGs (e.g. SVG and Geolocation) feedback from our observation. Envisioned issues for Web Mapping are a common coordinate system for map contents and a projection. Another issue is a relationship to other GIS communities (OpenLayers, Open Street Map, WMS, and etc.) outside W3C. They have developed map-related standards and frameworks, and we need to clarify our interrelationship and consider collaboration if necessary. This group will not create specifications.
    Join group Report a problem
  • SDshare

    (12 participants)
    SDshare is a highly RESTful protocol for synchronization of RDF (and potentially other) data, by publishing feeds of data changes as Atom feeds.
    Join group Report a problem
  • Places

    (19 participants)
    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.
    Join group Report a problem
  • Law and Technology

    (27 participants)
    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.
    Join group Report a problem
  • Locations and Addresses

    (49 participants)
    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).
    Join group Report a problem
  • Mobile Accessibility

    (41 participants)
    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.
    Join group Report a problem
  • MicroXML

    (31 participants)
    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.
    Join group Report a problem
  • XML Hypermedia

    (6 participants)
    Discuss possible benefits and implications of adding hypermedia affordance components to the XML language. Specifically, but not limited to discussion of Bugzilla bug# 17659.
    Join group Report a problem
  • Web History

    (51 participants)
    This group gathers people interested in the history of the World Wide Web: how it was invented, what was out there that made it possible, and what happened in its early years. Our main goal is to collect and preserve valuable information (software, documents, testimonials) before it is lost. This group will not produce specifications.
    Join group Report a problem
  • Argumentation

    (20 participants)
    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.
    Join group Report a problem
  • Client and Server JavaScript APIs

    (35 participants)
    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.
    Join group Report a problem
  • EXPath

    (31 participants)
    The mission of this group is to lead to extension of XPath and all related technologies (XSLT, XQuery, XProc, XForms, XML Schema).
    Join group Report a problem
  • Microposts

    (17 participants)
    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.
    Join group Report a problem
  • African Developers Taking on the Web

    (23 participants)
    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.
    Join group Report a problem
  • WAI-Engage: Web Accessibility

    (76 participants)
    WAI-Engage is an open forum for responsive development of material supporting web accessibility, including support for Web Accessibility Initiative (WAI) resources. Developers, designers, project leaders, administrators, scholars, producers and consumers with disabilities, and anyone interested in accessibility -- please join us and share your perspectives to help build resources that will be useful to the broader community. We welcome everyone to this Community. There is no time commitment or experience expected. This is a place to suggest, share, and develop ideas. This group will not publish specifications.
    Join group Report a problem
  • Web Application Store

    (15 participants)
    Since the launch of Apple's App Store in 2008, developers found a market delivery channel that greatly reduced time-to-market and time-to-payment and provided a direct channel to consumers. The result: users started buying more and more smartphones, accessing app stores and downloading billions upon billions of apps. At same reason, web developers are also expressing interest in an app store model for the Web that would enable them to get paid for their efforts without having to abandon Web development in exchange for proprietary silos. The purpose for this Web Application Store community group is to discuss about the web application store, related technologies, and various issues for Open Web Application Store. This Web Application Store CG's activities include: * Tracking specifications and implementations related to Web Application Store. * Refining use cases to communicate specific needs of Web Application Store. * Discussing technological issues related to Web Apps & Web Application Store * Suggesting refinements or fixes to existing specifications to better meet the needs of the Web Application Development community * Evangelizing specifications to browser vendors. * Documenting how to best use open web standards for Web Application Store * Evangelizing open web standards and best practices for Web Application Store Anyone can join the Web Application Store Community Group.
    Join group Report a problem
  • Multilingual Web Sites

    (28 participants)
    The objective is to produce specifications to facilitate the use and creation of multilingual web sites.
    Join group Report a problem
  • Web Observatory

    (54 participants)
    The sister organisation of W3C, the Web Science Trust (www.webscience.org) proposes to create a global "Web Observatory". The Open Data movement and the Transparency Agenda are successfully advocating the release of very large institutional and commercial data sets describing social phenomena, economic indicators and geographic trends. This proliferation of data represents great opportunity for researchers and industry but this data abundance also threatens to make it ever more difficult to locate, analyse, compare and interpret useful information in a consistent and reliable way; a situation which can only get worse unless we can help stakeholders perform useful analysis rather than drowning in a sea of data. The Web Observatory will offer an institutional framework to promote the use of W3C and other standards in the development of; Semantic Catalogues to globally locate existing data sets, Collection Systems to gather new global data sets, and Analytics Tools and methodologies to analyse these data sets. This community group seeks to articulate the business and technical requirements for the Web Observatory.
    Join group Report a problem
  • Film Industry

    (13 participants)
    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.
    Join group Report a problem
  • User Identity on the Web

    (25 participants)
    Currently, more and more services are created on the web and require information about you, me, all of us. Therefore, users have to give away a lot of information about themselves to many different services. The point is that the users lose control of their identity on the web, by filling a lot of forms (e.g., through subscriptions). Privacy on the Internet is extremely important and must remain. Personal information is used by services we, sometimes, don't even know about, and it is a real problem. The aim of this group would be to think about new ways to identify individuals over the internet using trusted web based identities embedded directly into the core protocols of the web. At the same time it is important to maintain equilibrium between total privacy and providing information when needed, which means, when the user wants to.
    Join group Report a problem
  • Print and Page Layout

    (46 participants)
    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.
    Join group Report a problem
  • CSS Selectors as Fragment Identifiers

    (26 participants)
    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.
    Join group Report a problem
  • Semantic Sensor Networks

    (47 participants)
    To continue the work of the Semantic Sensor Networks Incubator Group (the SSN-XG) in defining and using ontologies and mappings for querying, managing and understanding sensors, sensor networks and observations. This community group will also serve as a community and access point for ontologies (such as the group's SSN ontology) and technologies developed for semantic sensor networks.
    Join group Report a problem
  • Responsive Issues

    (302 participants)
    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."
    Join group Report a problem
  • HTML5 Specifications

    (76 participants)
    A group addresses and discusses proposed ideas for HTML5 specifications.
    Join group Report a problem
  • XML Error Recovery

    (13 participants)
    This group's purpose is the discussion of applying error recovery parsing methods inspired from HTML to XML.
    Join group Report a problem
  • Decisions and Decision-Making

    (19 participants)
    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.
    Join group Report a problem
  • Smart Phone Application Developer

    (10 participants)
    This Group will help developers create Internet based Smart Phone applications. Participants will collaborate and code to make the web equally and easily accessible through Smart Phones. This group will document the new research papers created by group members regarding Internet based Phone applications.
    Join group Report a problem
  • Distributed Tasks

    (6 participants)
    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!
    Join group Report a problem
  • Mobile Web in Indian Languages

    (9 participants)
    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.
    Join group Report a problem
  • Network-Friendly App and WebApp Best Practices

    (22 participants)
    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.
    Join group Report a problem
  • Data Driven Standards

    (16 participants)
    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.
    Join group Report a problem
  • Cloud Computing

    (44 participants)
    The group will examine and create specifications related to distributed computation and storage, with an XML network transport layer and possible mapping to RDF.
    Join group Report a problem
  • Script Library

    (13 participants)
    A forum for improved communication between script library authors and users, and W3C working groups working on relevant specifications.
    Join group Report a problem
  • Do-Not-Track

    (14 participants)
    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.
    Join group Report a problem
  • SVG glyphs for OpenType

    (14 participants)
    Extension of OpenType to allow multicolor, animated SVG glyphs while reusing the OpenType layout facilities.
    Join group Report a problem
  • Timed Text

    (10 participants)
    A number of organisations are now working with the TTML specification, and a degree of parallel discussion is happening. Some of that discussion is behind closed doors. There is a need to cross fertilize such groups so that the standard does not diverge, in addition new features and errata are being developed. This group is established to act as a forum for individuals, companies and consortia that are working with the TTML specification to address such issues. The core activities of the group will be as follows: - To act as a central forum for technical questions and answers on TTML - To act as a point of coordination for extensions and features being created in other organizations. - To identify issues, gaps and errata in the specification for future standardization. - Support the Timed Text Working Group (TTWG)) to develop a community standard which updates TTML 1.0 to address issues, gaps, and errata. - To develop and document tutorials, examples and best practice workflows - To host example code, templates, test data, and implementation code
    Join group Report a problem
  • CSS Accessibility

    (46 participants)
    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.
    Join group Report a problem
  • Web Media Text Tracks

    (50 participants)
    This group will work on text tracks for video on the Web, applied to captioning, subtitling and other purposes. This group plans to work initially on: 1) Documenting a semantic model underlying the caption formats in use, notably TTML, CEA 608/708, EBU STL, and WebVTT. 2) Creating a community specification for WebVTT. 3) Defining the mappings between WebVTT and some selected formats, including at least TTML (W3C/SMPTE), and CEA 608/708. 4) Creating web developer reference and tutorial material, including worked examples. 5) Creating a test suite and/or tools. A possible transition to REC-track for some of these document(s) is envisaged and that possibility will be used to guide the work and procedures. The group may produce recommendations for work in other groups, such as CSS, HTML5, and TTWG.
    Join group Report a problem
  • VIVO Open Research Networking

    (8 participants)
    VIVO (http://vivoweb.org, http://vivo.sourceforge.net) is an open source semantic web platform and ontology for representing researchers and their associated training, background, activities, organizations, and outputs including publications and research resources. VIVO publishes linked open data integrated from a variety of authoritative sources as well as from direct user input. This group will bring together developers, ontologists, adopters, outreach and policy strategists, end users, and members of closely related communities (e.g., http://orcid.org, https://www.eagle-i.org/home/) for discussion on the use of semantic data for research representation and networking, related tools, and opportunities for collaboration and synergy.
    Join group Report a problem
  • High-Performance Computing

    (36 participants)
    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.
    Join group Report a problem
  • Unhosted Web

    (24 participants)
    We propose per-user cross-origin cloud storage, much in the sense described in http://www.w3.org/DesignIssues/CloudStorage.html We are a non-profit project and have so far defined a first draft of our standard for this: http://unhosted.org/spec/dav/0.1 We have researched a lot of aspects in the last few months, and are about move to version 0.2 of our standard. People are starting to implement this with significant user base sizes, and other people are starting to develop apps that rely on it, which is now would be a good time to make this into a w3c cg.
    Join group Report a problem
  • Community I/O

    (11 participants)
    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.
    Join group Report a problem
  • Augmented Reality

    (113 participants)

    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

    Join group Report a problem
  • Native Web Apps

    (25 participants)
    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.
    Join group Report a problem
  • HTML Editing APIs

    (18 participants)
    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.
    Join group Report a problem
  • Web Skill Profiles

    (8 participants)
    This group has the mission to extend the discussion and development of the Web Skill Profiles originally developed by IWA/HWG (http://www.skillprofiles.eu) based on the EU Framework for education and outreach.
    Join group Report a problem
  • Web Education

    (121 participants)
    The Web Education Community Group (CG) aims to evolve the Web and improve the overall skill set of the web industry by improving the quality of available web education resources and courses around the world. To do this, we are engaging in several activities, which are the responsibilities of different projects inside the CG: 1. Learning material: Creating a comprehensive series of tutorial articles to teach all the W3C technologies, which will constantly be updated so that it remains current and best practice. The main basis of this is currently the Web standards curriculum. 2. Curriculum: Creating a series of structured courses based on the learning material, which educators from around the world can use to teach web design and development in a consistent, effective way. 3. Outreach: Contacting educators, companies and trainers and getting them to adopt our learning material and curricula. 4. Training and certification: Training the trainers to help them teach web design and development more effectively, and formulating a plan to, and researching the feasibility of, partnering with them to provide W3C endorsed qualifications. 5. Membership and policy: Dealing with issues of membership and policy. 6. International Education: Different groups responsible for outreach and translations into specific languages to serve groups for whom English is not the primary language. For more information, follow the relevant links in the Pages list. Please note that the Web Education Community Group will not be developing any specifications.
    Join group Report a problem
  • XML Performance

    (8 participants)
    The Mission of the XML Performance Community Group is to determine the requirements, use cases to get performance measurements of the whole XML technology stack. One of the goal is to be able to understand how XML (versus other technologies) could be used as ground to make efficient processing and identifies bottlenecks and features of this XML stack. One later goal will be to compare XML implementations among them. To do so, we might give hint on defining Efficient Profiles of existing Specifications.
    Join group Report a problem
  • Declarative 3D for the Web Architecture

    (38 participants)
    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.
    Join group Report a problem
  • Web Ecology

    (5 participants)

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

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

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

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

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

    Join group Report a problem
  • Document Services

    (9 participants)
    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.
    Join group Report a problem
  • Handshake Protocol

    (9 participants)
    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/
    Join group Report a problem
  • Rebase

    (5 participants)
    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.
    Join group Report a problem
  • HFVRP

    (12 participants)

    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.

    Join group Report a problem
  • Product Tracing & Blockchain

    (10 participants)
    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.
    Join group Report a problem
  • Performing Arts Information Representation

    (25 participants)
    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.
    Join group Report a problem
  • Federated Commerce

    (8 participants)

    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.

    Join group Report a problem
  • 3D FOSS Web Development

    (12 participants)
    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.
    Join group Report a problem
  • Digital ssset standard

    (15 participants)

    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.

    Join group Report a problem
  • svg-zh

    (2 participants)
    The mission of this group is to translate W3C SVG specifications into Chinese.
    Join group Report a problem
  • XSLT Extensions

    (33 participants)

    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.

    Join group Report a problem
  • Media Delivery

    (11 participants)
    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
    Join group Report a problem
  • Web fights covid19

    (11 participants)
    There is no doubt that the Web is demonstrating its potential in these hard times of the covid19 pandemic. The Web is allowing us to share information quickly and globally. Also, It is enabling the quick deployment of remote-working solutions as a response to the lockdown measures imposed by a majority of Governments. But the Web goes far beyond. Lots of Web ressources have been launched in the last weeks from different parts of the World supporting tools to fight the covid19: websites implementing AI screening and detection solutions; with data visualization tools; accessing bots and humans for telemedicine services; sharing information about medical resources... all these are some of the examples, and the list grows every day. This Community Group is proposed for achieving the following objectives: (1) to create a repository of already existing Web resources related to covid19 (2) to identify other Web-based initiatives which are on-going (3) to share Web-based initiatives of CG Members in order to get on-board other Members and achieve the maximum impact
    Join group Report a problem
  • Network Maintenance Notifications

    (8 participants)
    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.
    Join group Report a problem
  • CoVid-19 Remote Meet, Work, Class

    (14 participants)
    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.
    Join group Report a problem
  • Decentralized Identity Korean

    (16 participants)
    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.

    탈중앙 신원 대한민국 커뮤니티 그룹의 임무는 다음과 같습니다.

    • 탈중앙 신원에 관계된 표준(DIDs, VC 그리고 연관기술들)에 초점을 둔 논의를 활성화 합니다.
    • 이들 표준과 관련된 대한민국의 코멘트와 질문들을 모읍니다.
    • 이들 표준에 정의된 기술에 대한 대한민국의 특별한 유즈케이스(Use Case)를 정리합니다.
    • 그리고 이러한 활동 결과를 DIDs 작업 그룹, VC작업 그룹, 그리고 W3C 구성원 및 커뮤니티에 보고합니다.
    • 탈중앙 신원의 개발에 있어 모범사례를 공유합니다.
    • 탈중앙 신원 산업 전반의 최신 정보를 공유합니다.
    Join group Report a problem
  • Synthetic Media

    (16 participants)
    Our group is interested in every component of the modern architectures of artificial intelligence with which to generate or synthesize media and interactive media content. We intend to advance the state of the art with a number of new standards. With new and improved standards, teams and organizations will be better able to explore and develop the interoperable components which comprise these modern architectures of artificial intelligence.
    Join group Report a problem
  • The Unitive Web

    (6 participants)
    Currently, there is a growing movement from the independence of the web, towards dominant companies. These companies offer organized information, but this comes at a price. We lose our independence more and more. The Unitive Web is a proposal to have both organized information and independence. It offers one generic approach closely compatible with the current web, which makes it possible to create a global open virtual space of information which is responsive and reliable. It offers open customization of user interaction, open bottom-up schema mapping, integration of (AI) algorithms, and facilitates in the protection of privacy. The aim of this group is to discuss any aspect of it and share specifications. For more information, see this video about Unitive Web.
    Join group Report a problem
  • MFX Media

    (10 participants)
    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.
    Join group Report a problem
  • Building Device Naming Standards

    (15 participants)
    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
    Join group Report a problem
  • Business Data APIs and Interchange

    (9 participants)
    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.
    Join group Report a problem
  • Bullet Chatting

    (17 participants)
    A community group to incubate work on bullet chatting.
    Join group Report a problem
  • Web Thing Protocol

    (11 participants)
    The mission of this group is to define a common protocol for communicating with connected devices over the web, to enable ad-hoc interoperability on the Web of Things. Deliverables of the group may include use cases, requirements and specifications. The group will collaborate with the W3C Web of Things Interest Group and Working Group to ensure any specifications complement or extend the “Web of Things (WoT) Thing Description” specification. Objectives:
    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)
    See the proposed Community Group Charter for more information.
    Join group Report a problem
  • Web Certificate API

    (8 participants)
    The goal of Web Certificate API Community Group is to provide a JavaScript API for certificate related operations in web applications, such as retrieving a list of certificates, obtaining a public key and a private key associated with a certificate.
    Join group Report a problem
  • zot protocol

    (18 participants)
    To standardize the Zot protocol currently used in Hubzilla and Zap, and to push its adoption for social web.
    Join group Report a problem
  • Semantic Industries

    (14 participants)
    This Community Group brings together people from research and industry who are interested in semantic modelling. Researchers are interested in understanding the actual needs of industrial partners, gathering use cases and example data, and clarifying the challenges that further research can help address, as well as refining the methodologies for developing semantic based solutions. Industrial partners are interested in having clear benefits for adopting semantic technologies in relation to the digital transformation of industry. How can these benefits be realised by average developers using higher level frameworks and better tooling. The W3C Community Group will make extensive use of the GitHub issue tracker to raise and discuss ideas, and to prepare W3C Community Group reports with our findings.
    Join group Report a problem
  • Functional Knowledge Graph

    (9 participants)
    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
    Join group Report a problem
  • SVG

    (38 participants)

    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.

    Join group Report a problem
  • Talent Marketplace Signaling

    (36 participants)

    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.

    Join group Report a problem
  • Schema Extensions for IoT

    (19 participants)
    This Community Group is for creating extensions to Schema.org for IoT use cases. We have been holding regular community teleconferences since 2017 and now would like to formalize our work and accept contributions from the community. A W3C CG is the logical next step in our organization, as we already work with other W3C CG, IG, and WG entities. Our original charter is at: https://github.com/iot-schema-collab/ws-charter/blob/master/iotschema-charter.txt A revised charter for the CG is at: https://github.com/iot-schema-collab/intro-materials/blob/master/wg-charter.md
    Join group Report a problem
  • Bibframe2Schema.org

    (18 participants)
    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.
    Join group Report a problem
  • Voter Decision Support

    (8 participants)
    This community group discusses voter decision support systems and related topics. This community group shall advance the theory and practice of decision-making software and decision support systems for use by citizens during voting-related and civic participation activities. This community group shall advance the theory and practice of voter-centric design, empowering and equipping citizens. This community group may draft suggestions and best practices and may coordinate with other groups to support pertinent standards.
    Join group Report a problem
  • BD Comics Manga

    (55 participants)
    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.
    Join group Report a problem
  • Voice Assistant Standardisation

    (41 participants)
    Exploration and discussion of standards for voice assistants.
    Join group Report a problem
  • Volunteering Ontology

    (8 participants)
    The Volunteering Ontology group seeks to provide the volunteering community with a shared vocabulary for the open exchange of data relating to volunteering. Entities of interest include volunteering opportunities, the organizations hosting those opportunities, and the volunteers themselves.
    Join group Report a problem
  • Efficient Extensible Interchange

    (11 participants)
    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.
    Join group Report a problem
  • Educational Exercises and Activities

    (64 participants)
    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.
    Join group Report a problem
  • AppsDesignLab

    (13 participants)
    Our mission is to design & prototype ideas for mobile platforms and web apps.
    Join group Report a problem
  • Audio Description

    (25 participants)
    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
    Join group Report a problem
  • Open Data Nepal

    (10 participants)
    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.
    Join group Report a problem
  • Distributed Compute Protocol

    (9 participants)
    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.
    Join group Report a problem
  • Merging of Web and Mobile APP

    (7 participants)
    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.
    Join group Report a problem
  • Digital Asset Management Industry Business Ontology

    (54 participants)
    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.
    Join group Report a problem
  • syndicated.media

    (20 participants)
    An open community group focused on the technical and production aspects of podcasting and other applications of media distributed via feeds. Current areas of interest include extending RSS to support the modern needs of producers and their content; standardizing host and client behavior; improving the availability and accuracy of metrics and analytics; establishing and publishing best practices for de facto standards that have been adopted in the industry; thinking about the future of podcasting and needs that may arise.
    Join group Report a problem
  • Brazilian Publishing

    (40 participants)
    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.
    Join group Report a problem
  • Multidimensional Quality Metrics (MQM)

    (18 participants)
    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.
    Join group Report a problem
  • Croatian Web Developers

    (2 participants)
    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.
    Join group Report a problem
  • Decentralized Communications

    (28 participants)
    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.
    Join group Report a problem
  • WebAPI Discovery

    (28 participants)
    A group to develop a mechanism for the automatic discovery of WebAPIs, by extending the schema.org vocabulary. Increasingly, large online platforms and services provide one or more Web APIs for third-party developers. Moreover, many companies build WebAPIs as their primary product (Email API, SMS API, etc.). This has resulted in an explosion of the number of WebAPIs in recent years. Developers spend a significant amount of time searching for suitable WebAPIs to meet their needs. Our intention is to work closely with Schema.org to define a WebAPI-specific extension and promote usage of this extension among API owners. In the long run, our aim is to contribute this extension into the core Schema.org vocabulary. To achieve these goals we are seeking feedback and collaboration from API owners, DX specialists, API description language experts and maintainers of various API catalogs.
    Join group Report a problem
  • SKOS and OWL for Interoperabilty

    (17 participants)
    Based on our #SDSVoc bar camp session we would like to discuss best practices for using SKOS and OWL for interoperability
    Join group Report a problem
  • Video Game Schema

    (12 participants)
    The purpose of this group is to discuss extending the schema.org vocabulary for improved representation of video games in structured data. Our goal is to create proposal(s) that will extend video game-related schemas to make them more expressive, and so enable video game publishers, video game vendors, video game streaming services and news outlets to provide data consumers with more precise information about video games than is possible with the current vocabulary.
    Join group Report a problem
  • Getting Math onto Web Pages

    (58 participants)

    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.

    Join group Report a problem
  • Big Data Europe

    (34 participants)
    The group to discuss technical issues arising from the Big Data Europe Project.
    Join group Report a problem
  • Virtual Reality website and Metaverse

    (21 participants)
    This group is to start a discussion on how to level up our current world wide web to 3d and virtual reality.
    Join group Report a problem
  • Web Archivability

    (21 participants)
    Web Archivability is interested in proposing best practices that help the web developers and designers in building web site that can be easily captured, preserved, and replayed using the web archiving tools.
    Join group Report a problem
  • Stroke Fonts

    (16 participants)

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

    A stroked font is based on the idea of describing a collection of glyphs by their center line or the movement of a pen rather than their outlines. The center line, or skeleton, would then be styled either from inside the font, either from any software that acts downstream on the text, according to parameters that are yet to be defined. But might be based on the concept of an object following a path. This could be a very different approach than those embedded in the font formats currently in wide use. There will be a lot of issues to address for this to move forward. Drawing letters from their skeleton allow users for other styling options, but also allows the computer for a larger understanding of a glyphs shape as a whole or it's important features, regions, parts. Based on this understanding it woud be easier to algorithmically alter these glyphs' shapes -- while composing texts for example. It would enlarge the scope of what this group aims to do. Going towards a parametric approach of designing fonts, and considering the resulting transformation of the composition process. From fonts to lettering, from typography to writing. We aim to discover, adapt or develop a way to make these fonts usable and stylable in a variety of scenarios, such as web pages, canvas based design tools, as well as pen plotters, CNC, PCP and cartography design environments.
    Join group Report a problem
  • Healthcare Schema Vocabulary

    (44 participants)

    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.

    Join group Report a problem
  • Decentralized Sharing

    (21 participants)
    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.
    Join group Report a problem
  • Cryptoledgers

    (29 participants)
    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.
    Join group Report a problem
  • Trust & Permissions

    (10 participants)
    As the Open Web Platform expands, and apps are developed that access various sensitive resources, new ways of managing permissions to access these resources are likely to arise. This Community Group will explore and evaluate such ways based upon experience with native and hybrid platforms, and drawing upon research studies. This follows on from the Paris meeting on trust and permissions held on 3-4 September 2014, see [1]. Resources vary in sensitivity and timeliness, e.g. when and to whom a password should be disclosed is quite different from when access to the user’s webcam should be granted. Similarly, modes of obtaining user permission vary, including asking users upfront for permission when an app is installed or first run (exemplified in Android and Windows) or asking users for permission when the application is attempting to use a given capability (exemplified in iOS) and permission can even be obtained after the fact by inviting the user to continue or to cancel an action after it has occurred, i.e. asking for forgiveness rather than permission. In some cases, the user's actions can be taken as implicitly granting permission, such as the Windows file chooser dialog. A further approach is for users to delegate decisions on permissions to a trusted 3rd party. The goal of this CG is to develop and articulate best practices for which modes of obtaining permission best match which resource types, and make these best practices available to both platform developers (browser and operating system vendors) and app developers. Ideally the APIs offered to apps to obtain permission to access resources should be consistent across platforms, while allowing platforms the flexibility to present a user experience that meets each platform’s needs. The scope of this Community Group is limited to discussion and guidance on best practices, to review draft APIs from individual WG's, and pre-standardization work on promising ideas for better user experience obtaining permission, including trusted UI and trust delegation per Roesner et al, see [2]. Work on best practices will focus on the kinds of resources that need protection, the enumeration of good ways to obtain user permission, to dis-recommend permission models that are known to be problematic, and to recommend the preferred user experience for a given kind of resource. The main focus is on the Open Web Platform, but packaged apps are not excluded. This group will not publish Specifications. [1] http://www.w3.org/2014/07/permissions/ [2] http://research.microsoft.com/pubs/152495/user-driven-access-control-nov2011.pdf
    Join group Report a problem
  • Exploration of Semantic Data

    (32 participants)
    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.
    Join group Report a problem
  • Quick-fix support for XML

    (24 participants)
    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.
    Join group Report a problem
  • Semantic Statistics

    (33 participants)
    This community group aims to be a forum for the statistics community and the Linked Data community to examine issues arising from applying semantic technologies in the statistical production process and to report on best practises in the use of statistics on the Web of data. In particular the group will discuss use cases of the application of the Data Cube vocabulary in the production of official statistics and establish if there is a need for more standardisation of vocabularies to ensure comparability of statistics data on the Web of Data. Potential participants in this group are members of official statistics agencies and other government bodies that produce data (e.g. administrative, geospatial, government funded research results), statisticians, researchers and anyone in the Web of Data community who is interested in the publication of statistical data that can lead to statistical analysis of the maximum rigour. The group will coordinate as appropriate with the Government Linked Data WG and other relevant groups within the W3C Data Activity Coordination Group. This group will not publish specifications.
    Join group Report a problem
  • Touch Events

    (10 participants)
    The Touch Events community group was formed by members of the Web Events Working Group (responsible for the Touch Events specification) and the Pointer Events Working Group (responsible for the Pointer Events spec). The group's focus is to determine differences in touch event behavior between browsers. The group seeks to form consensus on the best approaches for interoperability outside of what's already standardized. Among the topics in scope for this group: * Defining how touch-action should be implemented in browsers that support touch events; see: https://docs.google.com/document/d/1CV2AXyrdPdGSRypAQcfGrgQVuWYi50EzTmVsMLWgRPM/ * Defining the "right" TouchEvent / PointerEvent interaction for both browsers and pointer event polyfills; see: https://docs.google.com/document/d/1Sasl1qYJV6agrDvGplEYlZznzc38U-TFN_3a67-nlSc/ * Trying to form consensus on how exactly browsers should behave in sending touch events when scrolling starts (f.ex. see the following public-webevents thread: http://lists.w3.org/Archives/Public/public-webevents/2013AprJun/0040.html * Identifying other differences that exist between these events. * Discussing problems web/framework developers have with the design of touch events; see: https://docs.google.com/document/d/12-HPlSIF7-ISY8TQHtuQ3IqDi-isZVI0Yzv5zwl90VU/ * Define "mappings" between Touch Events and Pointer Events; for example, see: https://docs.google.com/spreadsheet/ccc?key=0AvdBn9Kvx22qdGRnRXNPb0ZBTUl3SEkwdUdtaW9pWWc&usp=sharing * Define the relationships between touch-pointer-mouse. The group also expects to make proposals for potential future standards.
    Join group Report a problem
  • ETL Markup Language

    (10 participants)
    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.
    Join group Report a problem
  • Chinese Web Accessibility

    (32 participants)
    The mission of this group is to help Chinese developers and designers to build an accessible web. This group will not produce technical specifications.
    Join group Report a problem
  • Multi Markup

    (3 participants)
    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.
    Join group Report a problem
  • Open Data Directory

    (18 participants)
    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.
    Join group Report a problem
  • Web App Source Code Protection

    (16 participants)
    The goal of this community group is to explore solutions for protecting web app source codes. It is well-known that web page source codes are visible to the public due to the openness of the Internet and the W3C standards. With the advent of HTML5, the web apps become popular, especially the mobile web apps. Web apps can be classified as either Hosted App or Packaged App. The source code of Packaged Apps (such as the apps in Firefox OS or Tizen OS) are installed and running locally. Users can easily view the source code. Similarly front end source code of Hosted App can also be easily seen by anyone. In this case, the publicity of source codes becomes a problem. Because web developers never hope their web apps are easily copied by others. Therefore, this group intends to find mechanisms of code protection for web apps, especially for packaged apps, making the source codes (e.g. HTML, CSS, JavaScript), as well as relevant resource files (image, audio and video, etc.) cannot be seen easily. Thus, the interests of web developers will be protected.
    Join group Report a problem
  • Open Linked Education

    (64 participants)
    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.
    Join group Report a problem
  • VoiceXML

    (7 participants)
    The mission of this group is to bring together voice application developers interested in VoiceXML. This group will not produce specifications, but will discuss use cases that may be recommended to the VoiceXML Working Group. Of particular interest will be use of VoiceXML for mobile applications.
    Join group Report a problem
  • Automotive and Transportation

    (119 participants)
    The mission of the Automotive and Transportation Group is to act as an incubator of ideas for standardization for connected vehicles and the broader transportation data space. It had produced some early draft specifications for making vehicle signals available in a browser runtime as a first class object. Those specifications were the basis for launching the W3C Automotive Working Group. The Auto Working Group has since changed to service specifications to expose signals in a broader range of computing environments and bringing this extremely useful telematics information to the cloud.

    Fuller description of current and evolving scope is in the charter.
    Join group Report a problem
  • Web Audio Developers

    (60 participants)
    The Web Audio Developers Community Group brings together hackers and developers interested in using the emerging Web Audio API. By providing community support on using the API and surfacing issues with the draft standard, it complements the work of the W3C Audio Working Group where the specification is being developed. This group will not create specifications.
    Join group Report a problem
  • Semantic Open Data

    (21 participants)
    This group intends to explore ways to leverage OData as a contributor to the Semantic Web vision and to help achieve a common understanding of both technologies as well as their relationship to each other.
    Join group Report a problem
  • Customer Experience Digital Data

    (108 participants)
    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.
    Join group Report a problem
  • Web Performance

    (22 participants)
    The goal of the Web Performance is to produce a general guideline to help people who work in the web field increasing their websites' performances. From the server abilities and rapidity to the analysis of the website's code (whatever would the markup language be), we try to help web designers making faster websites.
    Join group Report a problem
  • Private User Agent

    (6 participants)
    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.
    Join group Report a problem
  • Schema Bib Extend

    (74 participants)
    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.
    Join group Report a problem
  • Development Linked Data

    (26 participants)
    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.
    Join group Report a problem
  • Philosophy of the Web

    (59 participants)
    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.
    Join group Report a problem
  • WebApps UI

    (13 participants)
    Web applications employ a range of UI methods from CSS, SVG, HTML Forms, Canvas and ARIA. Our focus is to ensure that UI methods are accessible, maintainable and of high quality across vendors and specifications. We use WCAG and ATAG to examine cross-specification techniques and identify issues with implementations and associated specifications.
    Join group Report a problem
  • W3C Developer Relations

    (23 participants)
    Developers and designers form an important audience for W3C standards, but the standards process itself is not an ideal way to engage with them. W3C has made strides in terms of developer relations in recent years, through W3Conf, Web Education XG and CG, easy access to W3C through community groups, more documentation, and online training. More can be done to reach more people and better reflect their interests in W3C. Initial ideas: * Create a developer relations activity or domain, to coordinate and explore different ways to directly engage with developers and designers, to gain early feedback on our specifications. * Make W3C a home for more useful documentation, demos, etc. * Support developer advocacy, in which ideas, use cases, and requirements for features or specification fixes are collected in detail from developers and designers, and presented to the appropriate W3C Groups. * Liaise with Members' developer relations departments on projects of mutual benefit. This group will not publish Specifications.
    Join group Report a problem
  • Web of Sensors

    (32 participants)
    This group explores how the Web platform could interact with sensors around us. For instance, how do we hook up an Arduino and interact with it through the Web platform? The scope is to explore we can safely expose sensor data to the Web platform in way that protects user's privacy and meets the needs of developers.
    Join group Report a problem
  • Open Annotation

    (130 participants)
    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/
    Join group Report a problem
  • E-learning: Evolving technologies and growing reach

    (47 participants)
    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.
    Join group Report a problem
  • Accessible Infographics

    (44 participants)
    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.
    Join group Report a problem
  • User Interaction and Experience

    (18 participants)
    As the number of Web applications is exponential, the capability to link user activity from application to another is also growing. However, these connections are more or less relying on specific models and APIs and set-up of a new connected application needs a tons of one-to-one configuration. This group will try to gather from these experience in order to build a more coherent model for sharing - semantically enabled & privacy safe - interaction data in order to provide better user experience among web applications.
    Join group Report a problem
  • Web Crypto API

    (27 participants)
    This group discusses Web Crypto APIs for signing the message by the user certificate issuing from the certificate authority for SSL communications. It is based on http://html5.creation.net/webcrypto-api/
    Join group Report a problem
  • Semantic News

    (40 participants)
    The Semantic News Community Group is a forum for exploring the intersection of W3C semantic technologies and news gathering, production, distribution and consumption. It will focus on a common representation for abstract ideas in the news domain such as a 'news event' or a domain ontology for news. This includes the following subject areas: 1. Review, test and comment on existing and proposed standards for semantic technologies in the news domain. 2. Encourage the reuse of well-known datasets and ontologies and propose mappings between them as required. 3. Best practices for publishing, exchanging and linking data, including use cases. 4. Development of prototypes to help build the business case for this approach. 5. Discuss design principles of schemas and ontologies.
    Join group Report a problem
  • SPARQL-ML

    (10 participants)
    The technological advancement in computational power and the significant increase in data generation allowed the successful implementation and application of many machine learning methods that were not possible before. On the one hand side, those methods need a lot of data to succeed. On the other hand side, the Semantic Web community has successfully published a large amount of machine-readable data on the Web. RDF data is often accessible over not machine-learning-ready protocols. The purpose of this community is to discuss how to leverage machine learning methods in RDF data through the SPARQL query language and protocol.
    Join group Report a problem
  • Universal Safety Net for Online Learning

    (4 participants)
    Learning to make the case for a new kind of user-learner help becoming common to the basic UI of browsers. One aspect: every html rendered word an invisible button that opens a help system able to provide anything any learner might need to recognize-read and/or understand the word (eventually) regardless of language, reading skill, vocabulary, background knowledge, or age. Example: https://learningstewards.org/io-pq-pop-up/ Online Learning Safety Net (OLSN)
    Join group Report a problem
  • Web-Native

    (7 participants)
    The Web-Native Community Group is a focused initiative to bring the current developer community overrun by frameworks back to native web technologies, so that everyone can bank more on the platform and less on abstractions. This is a targeted intervention to the now sweeping "framework-first" thinking for a new "native-first" thinking among developers. Whatever were the reasons for the former at the time, it no longer aligns with the current state of the platform and its fast-evolving future. It is now, more so than ever, a compelling problem to fix, and this community group will do just that! We hope to build on the work of existing posts in the community, that are, at least, looking for a paradigm shift. More importantly, our key activity will be working with the developer community and other W3C community groups to: (1) implement strategies that engage the developer community to put native languages, APIs, and methodologies at the heart of their everyday work, and (2) facilitate proposals that can bring various common development paradigms to native implementation, or to say the least, provide low-level primitives to support higher-level implementations of these paradigms that represents the modern web.
    Join group Report a problem
  • Atomic Data

    (7 participants)
    Develop a standard for exchanging type-safe data on the web. https://docs.atomicdata.dev
    Join group Report a problem
  • Font and Text

    (61 participants)
    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.
    Join group Report a problem
  • CSS4

    (30 participants)
    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.
    Join group Report a problem
  • CSS Print

    (48 participants)
    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.
    Join group Report a problem
  • Inclusive Design for the Immersive Web

    (10 participants)

    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.

    Join group Report a problem
  • Bridging GraphQL and RDF

    (52 participants)
    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.
    Join group Report a problem
  • Content Blocking

    (16 participants)
    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.

    Join group Report a problem
  • Bitcoin Hypermedia

    (42 participants)
    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.
    Join group Report a problem
  • Knowledge Domain

    (16 participants)

    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.

    Join group Report a problem
  • Web Video Map Tracks (WebVMT)

    (3 participants)

    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:

    Join group Report a problem
  • Veres One

    (46 participants)
    The mission of the Veres One Project is to facilitate the creation of open standards, software, and provide the governance to enable anyone in the world to create and manage their own decentralized identifiers.
    Join group Report a problem
  • Blockchain and Decentralized Apps

    (17 participants)
    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.
    Join group Report a problem
  • Synchronized Multimedia for Publications

    (23 participants)
    This community group's goal is to propose a way to synchronize audio or video with Web Publications and other document formats being developed by the Publishing Working Group, in order to make the publications accessible to people with different types of reading requirements. The CG may recommend the best way to integrate an existing technology, or it may provide an outline for developing a new format.