Skip to toolbar

Community & Business Groups

  • Accessibility in India

    99 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
  • Accessible Infographics

    48 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
  • Accessible Online Learning

    86 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
  • Accessible Playlist

    7 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
  • Accessible SVG

    38 Participants
    Scalable Vector Graphics offers both opportunities and challenges for accessibility. This group will explore the different conditions and circumstances for SVG use, propose clear use cases and requirements and specification text, and make tests so we can have consistent behavior in various user agents (including different screen readers).
    Join group Report a problem
  • Ad Ops Speaks on DNT

    8 Participants
    Representatives from various publishers and advertising technology firms in ad operations roles discuss W3C's Tracking Protection Working Group's draft papers on Tracking Preference Expression and Tracking Compliance and Scope, and possibly propose alterations and amendments.
    Join group Report a problem
  • African Developers Taking on the Web

    25 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
  • Age Labels Data Model

    13 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
  • Agriculture

    40 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
  • Algorithmic Modelling

    14 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
  • Annotation UX

    16 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
  • Argument Representation

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

    16 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
  • Augmented Reality

    95 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
  • Automated WCAG Monitoring

    67 Participants
    Creating (semi-)automated tests for WCAG is key to affordable, large scale research. The tests are designed in a way that they are useable by people with a variety of skills. The results too should be informative, not just to developers, but to website managers, policy makers and disability advocates and others. The objective of this community is to create and maintain tests that can be implemented in large scale monitoring tools for web accessibility. These tests will be either automated, or semi-automated, in which tools assist non-expert users to evaluate web accessibility. By comparing the test results with results from expert accessibility evaluators, we aim to track the accuracy of the tests we've developed. This allows for an iterative improvement and adjustment of the tests as web development practices change and evolve. It also provides the statistical bases on which large scale accessibility monitoring and benchmarking can be built. This group will not publish specifications.
    Join group Report a problem
  • Automotive Ontology

    62 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
  • Automotive and Web Platform

    140 Participants
    The mission of the Automotive and Web Platform Business Group is to influence the Open Web Platform on the unique needs of the automotive industry, and to help stakeholders within the automotive industry to build a good and practical understanding on the standardization processes within the W3C. The initial scope of this business group will be to determine what vehicle data should be exposed through a Web API(s). The goal or deliverable will be to draft a specification and then hand it off to a W3C working group that can take the spec and finalize it through the W3C specification and community process. If the business group is successful in this initial effort, there are many other technical challenges such as reducing driver distraction and improving safety that this group could address while influencing the Open Web Platform for Automotive. The proposed charter for the group is http://www.w3.org/community/autowebplatform/automotive-and-web-platform-business-group-charter/
    Join group Report a problem
  • Benchmarking for the Web

    7 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
  • Best Practices for Multilingual Linked Open Data

    83 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
  • Bible Perikopes

    1 Participants
    The bible - both as a literary work and as a religious work - has a very typical structure that doesn't always align with regular book structures. The intention of the group is to create a microdata format to allow to specify biblical passages, including perikopes built up from books, chapters, verses and occasionally subverses. There are also different possible translations of the bible.
    Join group Report a problem
  • Big Data

    127 Participants
    This group will explore emerging BIG DATA pipelines and discuss the potential for developing standard architectures, Application Programming Interfaces (APIs), and languages that will improve interoperability, enable security, and lower the overall cost of BIG DATA solutions. The BIG DATA community group will also develop tools and methods that will enable: a) trust in BIG DATA solutions; b) standard techniques for operating on BIG DATA, and c) increased education and awareness of accuracy and uncertainties associated with applying emerging techniques to BIG DATA.
    Join group Report a problem
  • Blockchain

    71 Participants
    The mission of the the Blockchain Community Group is to generate message format standards of Blockchain based on ISO20022 and to generate guidelines for usage of storage including torrent, public blockchain, private blockchain, side chain and CDN. This group will study and evaluate new technologies related to blockchain, and use cases such as interbank communications.
    Join group Report a problem
  • Blockchain Digital Assets

    8 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
  • Browser Extension

    35 Participants
    Problem: There is no cross browser standard for building browser extensions, which requires developers to create extensions for each browser individually. Proposal/Mission: The Browser Extension group will attempt to standardize extension package structure, API, portability etc., across browsers.
    Join group Report a problem
  • Browser Sync

    11 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
  • Browsers and Robotics

    13 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
  • CSS Accessibility

    62 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
  • CSS Selectors as Fragment Identifiers

    28 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
  • CSV on the Web

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

    12 Participants

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

    The group will publish and update:

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

    See the charter for more detailed information.

    Join group Report a problem
  • Cartography

    12 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
  • Character Description Language

    19 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
  • Chinese Digital Publishing

    28 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
  • Client and Server JavaScript APIs

    44 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
  • Cloud Computing

    58 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
  • Collaborative Software

    19 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
  • Colour blindness accessibility

    15 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
  • Community Council

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

    17 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
  • Credentials

    86 Participants
    A "credential" is a qualification, achievement, quality, or piece of information about an entity’s background such as a name, government ID, payment provider, home address, or university degree. The purpose of the Credentials Community Group is to discuss, research, document, prototype and test credential storage and exchange systems for the Web. This work is done in order to make progress toward possible future standardization and interoperability of both low and high-stakes credentials. The goal of this Group is to forge a path for a secure, decentralized system of credentials that would empower both individual people and organizations on the Web to store, transmit, and receive digitally verifiable proof of qualifications and achievements. In addition to documentation, this Group collaborates on and shares various proof-of-concept solutions and components through open source methods, unencumbered by patents or royalties. In general, this Community Group provides an inclusive venue where credentialing solutions, regardless of their origin, can be incubated, evaluated, refined, and tested. The focus of the group is to promote credentialing innovations based primarily on their technical merit. This approach invites competing technical designs to be submitted and incubated in the same group. The hope is that this strategy will lead to either the merging of the best aspects of each technical design, or a clear differentiation emerging between alternative designs.
    Join group Report a problem
  • Cryptoledgers

    21 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
  • Customer Experience Digital Data

    152 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
  • Data Driven Standards

    20 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
  • Data Visualization

    40 Participants
    The mission of this group is to provide a unified data model for data visualization, data visualization API, core model of data visualization methods and category, and domain specific data visualization methods (e.g. scientific data visualization), and further, data interactive analysis method.
    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
  • Decentralized Sharing

    16 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
  • Decisions and Decision-Making

    16 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
  • Declarative 3D for the Web Architecture

    53 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
  • Declarative Linked Data Apps

    51 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
  • Development Linked Data

    28 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
  • Distributed Tasks

    10 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
  • Do-Not-Track

    24 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
  • ETL Markup Language

    8 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
  • EXPath

    30 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
  • Electronic Governance (eGov)

    57 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
  • Emergency Information

    56 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
  • Experience API (xAPI) Vocabulary & Semantic Interoperability

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

    23 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
  • 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
  • Exposing and Linking Cultural Heritage data

    23 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
  • Extensible Data Model Declaration Language for Education

    10 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
  • Extensible Web

    68 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
  • Federated Infrastructures

    16 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
  • Film Industry

    11 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
  • Games

    106 Participants
    The goal of the games community group is to improve the quality of open web standards that game developers rely on to create games. This is done by: * Tracking specifications and vendor implementations related to open web games. * Recommending new specifications to be produced and finding working group homes for them. * Refining use cases to communicate specific needs of games. * Suggesting refinements or fixes to existing specifications to better meet the needs of the game development community * Evangelizing specifications to browser vendors. * Documenting how to best use open web standards for games * Evangelizing open web standards to game developers and game development best practices to web developers The games community group will not develop any specifications, and thus, there will not be any Essential Claims under the W3C Contributor License Agreement or Final Specification Agreement.
    Join group Report a problem
  • Geometry API

    18 Participants
    This group is to explore options and features around a native geometry API for operations on points, vectors, matrices, and so forth. Some features would include finding intersection points, centroids, shape area, and other common use cases, as well as specialized case for mapping.
    Join group Report a problem
  • Geospatial Semantic Web

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

    50 Participants
    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
  • HTML Editing APIs

    26 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
  • HTML Tidy Advocacy

    8 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
  • HTML for email

    97 Participants
    Issues around the use of HTML in email - documenting what works, what doesn't, and considering ways to improve the situation
    Join group Report a problem
  • HTML5 Japanese

    65 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
  • HTML5 Korean

    49 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
  • Haptic Interaction on the Web

    10 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
  • Hardware Based Secure Services

    32 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
  • Healthcare Schema Vocabulary

    33 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
  • High-Performance Computing

    47 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
  • Human Services

    19 Participants
    Goals The goals of the Community Group on Human Service Data are to: 1. Create an ongoing conversation space around data standards in the human service sector that will involve stakeholders from multiple perspectives including: 1a. Both government human service agencies and nonprofits/charities; 1b. Diverse substantive areas (e.g. welfare benefits eligibility, information and referral services, homelessness, substance abuse, child welfare, juvenile justice, etc.); 1c. 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: 2a. Fostering wider recognition of existing efforts and artifacts; 2b. Analyzing the strengths, limitations, and areas of overlap, agreement and divergence of existing efforts and artifacts; 2c. Identifying areas where standards do not yet exist but are needed; 2d. Convening working groups of diverse composition to develop and improve standards; 2e. Promoting the adoption of 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. Dependencies or Liaisons The Community Group will seek to form relationships with organizations including but not limited to: * American Public Human Services Association (APHSA) * [U.S.] National Information Exchange Model (NIEM) Human Service Domain * Alliance of Information and Referral Systems (AIRS) * Software and Technology Vendors’ Association (SATVA) * United Nations Office for the Coordination of Humanitarian Affairs (OCHA) * Sahana Software Foundation * Human Service Information Technology Applications (HUSITA)
    Join group Report a problem
  • Hydra

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

    70 Participants
    The mission of this group is to discuss, and share matters relating to the profession of Information Architecture. Help us spread awareness of Information Architecture and connect with other Information Architecture pros globally and locally. This group will not produce specifications.
    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
  • Interledger Payments

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

    5 Participants
    This group is for the discussion of assigning an IPv6 address for every person on Earth, so everyone has a digital identity. Each individual could use this to proxy or alias other identifiers, permanent or temporary, over different spans of their lifetime. Thus, a person they can manage their domain names, physical or email addresses, phone numbers, WebRTC address, and other contact info as they wish, flexibly maintaining an identity in a decentralized way not controlled by third-party commercial interests or even governments. This system could also be used for organizations, businesses, animals, or any other entity that needs an identity. This group may produce specifications.
    Join group Report a problem
  • Internet of Kendo Secure Equipment

    4 Participants
    Modern Kendo Equipment has been produced based on various standards by machines or craftsmen. In the era of Internet of Things, we think International specifications of Kendo Equipment can be organized and controlled by Web technology with security and safety for usage as well as with respect to the original.
    Join group Report a problem
  • JSON for Linking Data

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

    35 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
  • Law and Technology

    21 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
  • Linked Building Data

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

    35 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
  • Linked Data for Language Technology

    95 Participants
    This group aims to consult with current and potential users of lingusitic data to assemble user cases and requirements for Language Technology Applications that use Linked Data. The results will be used to guide future interoperability, research and development activities spanning the language technology and linked data domains, including via the OntoLex and BP-MLOD community groups. Potential users are companies and public bodies involved in content management, the language services and localisation industry and other applications of content analytics techniques used in search, recommender systems, sentiment analysis and terminology management. The group will engage with users through surveys and international road-mapping events organised by an EU-funded R&D consortium called LIDER. Contributions can be provided openly through engagement with the Community Group or anonymously if preferred. The anonymised outcomes of this exercise, in terms of use case and requirements priorities, technology gaps and interoperability roadblocks will be made publicly available via this community group by May 2014.
    Join group Report a problem
  • Locations and Addresses

    58 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
  • Machine Learning Schema

    31 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
  • Maps For HTML

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

    69 Participants
    The mission of this group is to specify a syntax and provide tests for Markdown. See http://www.codinghorror.com/blog/2012/10/the-future-of-markdown.html
    Join group Report a problem
  • Math Protocol Handler

    2 Participants
    This group's aim is to discuss and agree on the use of a custom protocol handler (math:) and standard parameters for enabling the export of mathematical expressions in MathML to other applications, such as assistive technologies, graphing calculators, math notebooks and other mathematics oriented applications, such as IPython and MATLAB. For more information, see https://wiki.benetech.org/display/MATH/Protocol+Handlers+for+External+Applications+to+Process+MathML
    Join group Report a problem
  • Meat Products

    7 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
  • Media Resource In-band Tracks

    13 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
  • MicroXML

    39 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
  • Microposts

    33 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
  • Mobile Accessibility

    45 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
  • Mobile Web in Indian Languages

    14 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
  • Multi Markup

    7 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
  • Multi-device Timing

    30 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
  • Multi-technology positioning professionals

    15 Participants
    The MULTI-POS CG will provide use cases, requirements, and other information, to ensure that the state of the art research is recognized in the development of global standards. The MULTI-POS CG bridges the W3C community and the MULTI-POS Marie Curie Initial Training Network. The MULTI-POS CG has the following goals: 1) Identify business and technology application scenarios based on the new positioning methods; 2) Specify the key technological, scientific, and industrial elements and their relationships in the new positioning ecosystem; and 3) Identify standardization opportunities. The first concrete work item is a review of the current state of the art, providing a common framework of reference for future work. What is the benefit (for you): Meet the professionals, get the big picture, have influence on use cases and requirements, get cited.
    Join group Report a problem
  • Music Notation

    244 Participants

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

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

    Join group Report a problem
  • Native Web Apps

    54 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
  • Natural Language Interfaces for the Web of Data

    19 Participants
    The Natural Language Interfaces for the Web of Data Community Group aims at analyzing, modelling, unifying and enhancing natural language interfaces for the Web of Data. The core goal is to improve the reusability of systems and to increase their quality and performance. The group will develop diverse modules as well as an unified data vocabulary and ontology to foster a growing interface landscape. This includes question answering, information retrieval, keyword search, answer verbalisation and so on. Furthermore, the Natural-Language Interfaces for the Web of Data CG will incubate a wide and collaborative environment for researchers, industrials and practitioners. We hope, that research as well as industry projects will support and benefit of this community group’s activity.
    Join group Report a problem
  • Network-Friendly App and WebApp Best Practices

    28 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
  • Networked Data

    15 Participants
    The recent years have shown the need to deal with networked data in large-scale, distributed settings. Not only must the systems be scalable, elastic and performant, but also address *ability (usability, manageability, etc.). One key component is doing it the webby way. The Web is the leading concrete exemplar of RESTful design, being the result of posthumous analysis of what was already working with URIs, HTTP and HTML for a system of interlinked documents. Unfortunately the machine equivalent of HTML is still emerging. LinkedData has achieved some powerful results; automated navigation by querying the Linked Open Data cloud shows some of the potential. However many systems also need to evolve and be evolved. This can be expressed as 'service capability' and also needs to be supported with consistency. This should aim to eliminate the wide range of non-interoperable approaches muddling the current landscape of REST APIs through exploiting hypermedia concepts. The Networked Data Community Group aims to provide a forum for collecting use cases including but not limited to the fields of science data (such as biology, astronomy, etc.), economics data (financial markets, etc.), health care, configuration and systems management, Green IT, and smart infrastructures (cities, etc.). Based on the collection of use cases the CG will derive requirements and write up best practices for dealing with the dynamics of the data.
    Join group Report a problem
  • ODRL

    53 Participants
    The W3C ODRL Community Group's aim is to develop and promote an open international specification for Policy Language expressions. The ODRL Policy Language provides a flexible and interoperable information model to support transparent and innovative use of digital assets in the publishing, distribution and consumption of content, applications, and services across all sectors and communities. The ODRL Policy model is targeted to support the business models of open, educational, government, and commercial communities through Profiles that enhance the model to align to their requirements whilst providing a common semantic layer for interoperability.
    Join group Report a problem
  • OFF/X

    8 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
  • OStatus

    31 Participants
    OStatus is a suite of protocols that lets people on different social networks interact. This group will develop the next version of the protocol.
    Join group Report a problem
  • Ontology-Lexica

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

    131 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
  • Open Data Directory

    20 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
  • Open Data Spain

    72 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
  • Open Government

    95 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
  • Open Linked Education

    69 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
  • Open and Interactive Widgets for STEM

    11 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
  • Open and Transparent W3C

    28 Participants
    Although the World Wide Web (WWW) is an open and free information system, participation in the member-based World Wide Web Consortium (W3C) typically requires paying a membership fee to participate in the Consortium's standards setting groups. As such, the W3C is often criticized as a closed organization by those that are not members of the Consortium. This group aspires to help provide non Members with simple mechanisms to provide feedback to the Consortium (the Consortium's Members and the Consortium's Staff) on topics such as (but not limited to): areas where new Web standards are needed (e.g. to help address some interoperability pain point), Consortium priorities, the evolution of the Web, aligning Consortium's activities with the Web, collaboration with other organizations, etc. Anyone - including non-Members - is welcome and encouraged to join this group. Participants include technical contributors to Web standards, Web standards Editors and group Chairs. The group also includes participants from the Consortium's "Advisory Committee" and at least one member of the Consortium's elected Advisory Board. Additionally, the group welcomes members of the Consortium's staff. If someone wants to communicate with this group but does not want to formally join it, that's OK; just send an email to the group's mail list: public-openw3c@w3.org (see for the list archive and RSS feed information). This group will not publish specifications.
    Join group Report a problem
  • Open knowledge-driven service-oriented system architectures and APIs (KiSS)

    15 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
  • Openactive

    10 Participants
    This group's mission is to discuss and prepare data and API specifications which facilitate the use of open and shared data relating to sport and physical activity. We have so far used http://www.openactive.io (along with https://github.com/openactive and Google Docs) to facilitate our work, supported by the Open Data Institute, and created an initial set of specifications within our open group of organisations. We would now like to progress our group to become a W3C CG, sharing our work with the wider community. The group will base its work on existing standards as much as possible, and re-use existing terms wherever appropriate. 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 seek to 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
  • Organisation Profile Documents

    2 Participants
    The aim of this group is to explore and develop a set of specifications for Organisational Profile Documents (OPDs). In particular we are interested in the usefulness of a machine readable OPD for the automatic discovery of resources in UK higher education institutions. Possible outcomes of the project would be: · Produce a specification for OPD · Create the documentation/supporting materials for OPDs · Promote the OPD to new organisations There is some support/resource from a UKHE funded project, data.ac.uk, more information on OPDs http://opd.data.ac.uk
    Join group Report a problem
  • PDF and Open Data

    5 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
  • Permanent Identifier

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

    66 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
  • Places

    24 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
  • Print and Page Layout

    47 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
  • Private User Agent

    7 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
  • Property Graphs Model and API

    24 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
  • PubSubHubbub

    44 Participants
    The group will promote and design a Publish-Subscribe pattern and protocol for the web. The current de-facto protocol for it, PubSubHubbub is already widely used but has a couple issues that we need to address. We hope this protocol can be used in wide range of applications, from social web, to e-commerce or even search engines.
    Join group Report a problem
  • Publications Object Model

    13 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
  • 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
  • RDF JavaScript Libraries

    60 Participants
    The RDF JavaScript Libraries Community Group discusses implementations of libraries for working with RDF and Linked Data in ECMAScript platforms like Web browsers and Node.js
    Join group Report a problem
  • RDF Stream Processing

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

    19 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
  • RDF and XML Interoperability

    27 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
  • Remote DOM

    9 Participants
    Similarly to how the Shadow DOM paved the way for custom elements using web technologies, a "Remote DOM" could allow display of portions of the web app to be displayed on "remote" (i.e. "external") devices, such as screens, Smart TVs, etc. This brings interesting capabilities to web apps, such as leveraging external screens for presentation, supplemental content or second screen experiences.
    Join group Report a problem
  • Research Object for Scholarly Communication

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

    6 Participants
    This group is emerging from a breakout session at an indiewebcamp on 3 December 2015. Short description for now: some people/organizations want to host other people's data without infringing on their privacy or freedom, and they want to set a clear bar for this kind of TOS.
    Join group Report a problem
  • Responsive Issues

    442 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
  • Restaurant Ontology

    10 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
  • Restricted Media

    54 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
  • Revising W3C Process

    44 Participants
    Examine the way W3C works. Propose improvements to the formal processes. These will be given to the Advisory Board, which currently manages that process.
    Join group Report a problem
  • Robustness and Archiving

    12 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
  • SDshare

    20 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
  • SPARQL Maintenance (EXISTS)

    18 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
  • SVG Mapping

    15 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
  • SVG Streaming

    7 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
  • Schema Architypes

    54 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
  • Schema Bib Extend

    107 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
  • Schema Course extension

    38 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
  • Schema.org

    237 Participants
    The Schema.org Community Group provides a forum for discussing all changes, additions and extensions to schema.org. In addition to providing a public setting for the day to day operation of the project, it serves as the mechanism for reviewing extensions and as a liaison point for all parties developing independent extensions to the schema.org core.
    Join group Report a problem
  • Script Library

    25 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
  • Second Screen

    66 Participants
    The group's goal is to define an API that allows web applications to use secondary screens to display Web content. Phones, tablets, laptops and other devices support ways to attach additional display screens. Common methods include attaching through video ports or HDMI, or wirelessly through Miracast, WiDi, or AirPlay. Screens can also be attached over a network. For many of these techniques the operating system hides how the screen is attached and provides ways for applications to use the screens. Native apps on an operating system can easily use these additional screens without having to know how they are attached to the device. The goal of this CG is to define simple APIs to request displaying an HTML page on the second screen and some means for the launching page on the first screen to communicate with and control the second page, wherever it is rendered. That API should hide the details of the underlying connection technologies and use familiar, common web technologies for messaging. The charter for this CG can be found at: https://github.com/webscreens/presentation-api/wiki/Second-Screen-Community-Group-Charter
    Join group Report a problem
  • Semantic News

    49 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
  • Semantic Open Data

    22 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
  • Semantic Sensor Networks

    55 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
  • Semantic Statistics

    25 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
  • Semantic Water interoperability Model

    2 Participants
    The group will work on a controlled vocabulary describing Properties and Services for Things which from part of water and wastewater infrastructure. Context is around standardised data models used for monitoring and control purposes.
    Join group Report a problem
  • Semantic Web Interfaces

    42 Participants
    Although Interface and Interaction design typically pertain to the disciplinary domain of HCI, which can be considered a neighboring discipline to the semantic web, with this proposal we aim to bring the relevant aspects of HCI to address core technological, socio-technical and fundamental challenges for Semantic Web (and Web Science) research. Read more: http://tinyurl.com/8hxlx7x
    Join group Report a problem
  • Semantic Web Programming Languages

    40 Participants
    A community focused on the adoption of Semantic Web concepts within contemporary and new programming languages. These will incorporate W3C Semantic Web standards for Ontology, Linked data and representations as integral parts of the development tool chains. Particularly the group will aim to 1. Develop new semantically-aware programming languages, 2. Modify existing languages to be semantically-aware 3. Develop design patterns for semantically-aware programming. 4. Develop Ontologies for computer programming concepts to allow inter-lingual sharing of basic and domain-specific algorithms.
    Join group Report a problem
  • Semantic Web in Health Care and Life Sciences

    4 Participants
    The mission of the Semantic Web Health Care and Life Sciences Community Group (HCLS CG) is to develop, advocate for, and support the use of Semantic Web technologies across health care, life sciences, clinical research and translational medicine. These domains stand to gain tremendous benefit from intra- and inter-domain application of Semantic Web technologies as they depend on the interoperability of information from many disciplines. The HCLS CG provides a forum for supporting, developing and applying Semantic Web technologies across healthcare, life sciences, clinical research and the continuum of translational medicine. Within these contexts, the HCLS CG focuses on the use of Semantic Web technologies to realize specific use cases which themselves have a specific clinical, research of business values. As use cases are developed, HCLS CG can solicit advice on technical matters from other Semantic Web related groups and give feedback on the use of technologies based on the work they do. The CG may also develop ongoing and mutually productive liaisons with relevant external organizations in healthcare, life sciences, and clinical research, including organizations that are actively working on relevant standards and/or implementations to which the HCLS’s work might contribute.
    Join group Report a problem
  • Smart Manufacturing

    7 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
  • Smart Phone Application Developer

    12 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
  • Social Business

    59 Participants
    This group will focus on social business use cases and application of those use cases to standards, standards improvements, and standards gaps. Initial conversations will be based on the W3C Jam Results recommendations: http://www.w3.org/2011/socialbusiness-jam/report.html This group will not produce specifications.
    Join group Report a problem
  • Social Economy

    17 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
  • Speech API

    73 Participants
    The goal and scope of this Community Group is to produce a JavaScript Speech API that supports the majority of use-cases in the the Speech Incubator Group's Final Report [1], but is a simplified subset API, such as this proposal [2]. For this initial specification, we believe that a simplified subset API will accelerate implementation, interoperability testing, standardization and ultimately developer adoption. This JavaScript Speech API will enable web developers to incorporate scripts into their web pages that can generate text-to-speech output and can use speech recognition as an input for forms, continuous dictation and control. Specification of HTML markup and a network speech protocol are out-of-scope of this Community Group. [1] http://www.w3.org/2005/Incubator/htmlspeech/XGR-htmlspeech/ [2] http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/att-1696/speechapi.html
    Join group Report a problem
  • Sport Schema

    14 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
  • 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
  • Stroke Fonts

    14 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
  • TV Control API

    51 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
  • Technical Architecture

    21 Participants
    This group is an open forum for discussing Web architecture, such as that discussed by the W3C Technical Architecture Group (TAG). Web architecture refers to the underlying principles that should be adhered to by Web components (APIs/Markup), whether developed inside or outside W3C. The architecture captures principles that affect such things as understandability, interoperability, scalability, accessibility, and internationalization. We expect to have a strong working relationship with the W3C TAG.
    Join group Report a problem
  • Technical Documentation in the Semantic Web

    10 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
  • The Hardware Pixel

    2 Participants
    A group for people who love pixels! This group is in support of exposing device pixel densities to web developers and letting web developers have the ability to use 'hardware pixels' instead of 'CSS pixels' on demand. Native developers have this affordance, why can't we? Hardware pixels! We want hardware pixels! ## What we want ## We want metrics! The hardware pixel density of a screen can live in the window.screen object as window.screen.pixelDensity, for example. The value would be the average of the vertical pixel density and the horizontal pixel density of the screen (in hardware pixels per unit). Vertical and horizontal pixel densities of the screen can be exposed in window.screen.verticalPixelDensity and window.screen.horizontalPixelDensity. Yes, the vertical and horizontal values don't always have a ratio of 1 across devices. Pixel Aspect Ratios are important for developers and designers that truly care about device-independence. ## How can it be done? ## Easy. The EDID data in modern screens tells us the width and height of a display in millimeters, the native resolution of the screen, and other interesting information. This info allows us to calculate a screen's hardware pixel density in pixels per millimeter with floating point precision. Exposing these values in window.screen is even more trivial. ## Why do we want these values? ## In this modern day, developers are moving towards device-independent development more than ever before. By exposing physical characteristics of a screen (when supported by the screen (just like how OpenGL is exposed through WebGL when supported by a device)) web developers will be able to make device-independent decisions on their development process. Currently, the lack of these metrics means that a web app can only look *almost* the same across devices, but not necessarily *exactly* as intended. We're engineers; *almost* is not enough. For example, suppose I want to make a push menu that is *always* 1 physical inch wide. This is currently not possible because inches in the web are "CSS inches", not physical inches. CSS units like centimeters, millimeters, and inches are currently unreliable across devices. You might think "why not just create a div element that is 1 cm wide, then get it's width in pixels and that's how many pixels per cm you have". Sure, that works, but those are *CSS* pixels per *CSS* centimeter. On top of that, not all operating systems operate at the same dpi, and to make matters worse not all devices have a devicePixelRatio of 1 (mines 2 by default in Mac OS X Yosemite). So the value that you'll get from this technique, if you adopt it right now, vary a *whole lot* across devices. We can't say with any confidence that something being displayed on various screens on multiple devices is 1 physical inch wide. Giving us these screen metrics will not only help us, it will help the future generation of developers because not only will exposing these screen metrics based on EDID info (when supported by the screen) get us closer to device-independent development more often, it will also promote the use of the EDID standard by screen manufacturers so that the next generation can benefit even more from the exposed screen metrics. ## Pixel Freedom for All! May the pixel be with you! ##
    Join group Report a problem
  • The Tourism Structured Web Data

    24 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
  • Timed Text

    11 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
  • Touch Events

    17 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
  • Traffic Event Ontology

    15 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
  • Trust & Permissions

    13 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
  • URI Specification

    7 Participants
    The URI Specification Community Group endeavors to produce a set of coherent, maintainable artifacts for use by implementors, developers, authors, and everyday users. We will achieve this by creating a formal specification of the ad hoc URI/URL standard described by RFC 3986/3987 and the WHATWG URL Living Standard. The deliverable is a single formal specification source document in Lem (http://www.cl.cam.ac.uk/~pes20/lem/) from which a typical standards document can be generated as well as a set of theorems over the concepts described and an executable test oracle for each specified function. Depending on community support and development of test generation tools, a test suite with proven specification coverage may also be delivered. If you think URI should work predictably and correctly and be able to be understood clearly, please join this group and give us your perspective!
    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
  • Unhosted Web

    40 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
  • Universal Images

    9 Participants
    Our goal is to provide tools and specifications for creatives and agencies to create and distribute multi-format images. These are images which contain metadata that lets them adjust to different sizes, depending of the format of the output device or the layout of the website it is used in. These images can be used to have a web-server automatically create the alternative versions needed for a responsive website.
    Join group Report a problem
  • User Identity on the Web

    21 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
  • User Interaction and Experience

    25 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
  • VIVO Open Research Networking

    20 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
  • Voice Interaction

    16 Participants
    Existing W3C voice interaction standards such as VoiceXML are based on use cases centered around telephony-based voice systems. The typical interaction style that these standards support is system-initiated directed dialog using grammars to constrain the speech recognizer. In recent years, interaction with voice applications has become much more flexible, with a user-initiated dialog style and significantly fewer constraints on spoken input. Many of these new applications take the form of "virtual assistants". These include general-purpose assistants (for example, Siri, Cortana, Google Now and Alexa) as well as virtual assistants with specialized domain expertise. The proposed Community Group will collect new use cases for voice interaction, develop requirements for applications such as virtual assistants and explore areas for possible standardization, possibly producing specifications if appropriate. Depending on interest, this exploration could include such topics as (1) discovery of virtual assistants with specific expertise, for example a way to find a virtual assistant that can supply weather information (2) standard formats for statistical language models for speech recognizers (3) standard representations for references to common concepts such as time (4) interoperability for conversational interfaces and (5) work on dialogue management or ‘workflow' languages . New functionality for existing voice standards can also be a topic of discussion. Speech application developers and voice user interface designers should be particularly interested in this group.
    Join group Report a problem
  • VoiceXML

    9 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
  • W3C Developer Relations

    26 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
  • WAI-Engage: Web Accessibility

    64 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
  • Wearable Web

    7 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
  • Web App Source Code Protection

    38 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
  • Web Application Store

    26 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
  • Web Archivability

    17 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
  • Web Array Math

    6 Participants
    The purpose of this group is to develop a specification for high performance, low latency typed array processing for the Web. The basic idea is to create an API that makes it possible to utilize hardware level parallelism, such as SIMD instructions, by providing methods that operate on whole arrays rather than single elements at a time.
    Join group Report a problem
  • Web Audio Developers

    64 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
  • Web Bluetooth

    85 Participants

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

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

    Join group Report a problem
  • Web Copyright

    11 Participants
    Irrespective of whether we like it or not, of whether W3C or other SDOs eventually accept it or not, DRM seems slated to come to the Web platform. We are looking at video today, but books, apps, and therefore relatively arbitrary Web documents could easily be next. The business pressure to do so is such that there is little in the way that technology can do to stop this process. Our communities may produce everything from learned recantations to bitter rants, words will not suffice to address the problem. The only way in which we can decisively put a stop to DRM is by changing the legal system which can make it seem desirable to some. The goal of this group is to produce a set of realistic proposals for Web-compatible copyright legislation. Its focus is very much pragmatic, the idea being not to produce an idealistic laundry list for some free content utopia, but rather actionable proposals that stand a chance of passing into law. This group will not produce specifications.
    Join group Report a problem
  • Web Crypto API

    45 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
  • Web Dev Data

    15 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
  • Web Education

    210 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
  • Web History

    61 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
  • Web MIDI

    14 Participants
    The Web MIDI Community Group brings together folks interested in enabling MIDI (Musical Instrument Digital Interface) devices on the Web. Some example applications include dynamically generated music for games, alternative input devices, and controlling music instruments and lighting systems. This group will not create specifications.
    Join group Report a problem
  • Web Media Text Tracks

    62 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
  • Web NFC

    32 Participants

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

    Join group Report a problem
  • Web Observatory

    90 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
  • Web Payments

    238 Participants
    The purpose of the Web Payments Community Group is to discuss, research, prototype, and create working systems that enable Universal Payment for the Web. The goal is to create a safe, decentralized system and a set of open, patent and royalty-free specifications that allow people on the Web to send each other money as easily as they exchange instant messages and e-mail today. The group will focus on transforming the way we reward each other on the Web as well as how we organize financial resources to enhance our personal lives and pursue endeavors that improve upon the human condition.
    Join group Report a problem
  • Web Performance

    24 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
  • Web Skill Profiles

    13 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 We Can Afford

    18 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
  • Web and Broadcasting

    71 Participants
    The aim of the Web and Broadcasting Business Group is to study and clarify the influence of Open Web Platform on the professional world of broadcasting, and to help stakeholders within the broadcasting industry to build good and practical understanding on the standardization processes in W3C with the chair-to-chair communication mechanism built into business groups. The business group will create monthly or bi-monthly report to summarize their study on the influence and share the reports internally. Detailed discussion and analysis on the use cases in this area should be done in the Web and TV Interest Group, so the business group will not deal with those items to avoid scope overlap. However, fruitful collaborative works may happen as a result of the chair-to-chair communication between these two groups.
    Join group Report a problem
  • Web of Sensors

    42 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
  • Web of Things

    253 Participants
    The aim of the Web of Things Community Group (CG) is to accelerate the adoption of Web technologies as a basis for enabling services for the combination of the Internet of Things with rich descriptions of things and the context in which they are used.
    Join group Report a problem
  • Web-based Signage

    55 Participants
    The Web-based Signage Business Group is aimed at companies and organizations interested in the standardization of Web based digital signage. The goal of the group is to identify use cases and system image/model for expansion of web browser based digital signage and smarter integration of existing Web standards.
    Join group Report a problem
  • WebApps UI

    14 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
  • WebAssembly

    652 Participants
    The mission of this group is to promote early-stage cross-browser collaboration on a new, portable, size- and load-time-efficient format suitable for compilation to the web.
    Join group Report a problem
  • WebID

    82 Participants
    The WebID Community Group is a continuation of the WebID Incubator Group [1]. The Community Group will continue development of a specification for the WebID protocol, build test suites, document use case, issues, and grow the community of implementations. [1] http://www.w3.org/2005/Incubator/webid/
    Join group Report a problem
  • Webize Everything

    15 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
  • World Archives of Sciences

    3 Participants

    The internet has been considerable development in the world has led to an exponential growth in the number of online documents by scientists. In this sector, the current trend seems to be to digitize all funds scientific libraries and sample Museums and this internationally. Many of these documents: articles, monographs, academic work, digitized specimens and videos are now available online, but remained scattered on the canvas. They do not allow quick consultations and consolidation of information. The new generation of scientists studying species biodiversity, taxonomy, protection, conservation and many other natural sciences, wants more access and use these documents remotely and for free. They suffer, however, that some problem: too wide dissemination of data and information.

    To meet this expectation, we collect (for 10 years) and archive it all these documents in a single point: WAS World Archives of Sciences: WAS-Archives.org : Biodiversity, Zoology, Botany, Taxonomy, Entomology, Paleontology, Geology, Natural History WAS contributes to the development of Knowledge and World Heritage. It allows the recognition of scientific organizations (Museums, Universities...). He participated in an ambitious scientific archiving, Museums becoming true mine of information as well as the Libraries or Documentation Centers. In addition to the departments of Natural History: Zoology, Botany, Taxonomy, Entomology, Paleontology, Geology and Natural History, WAS also archive the academic work of Administrations, Professional Associations, Commercial Societies, Non-Profit Foundations and Universities that become our natural partners and complete the panorama of available public sources of sciences.

    Join group Report a problem
  • XML Hypermedia

    20 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
  • XML Performance

    17 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
  • Zakim on Web

    8 Participants
    The goal of this group is to bring the functionalities of W3C Zakim Teleconference Bridge to web browsers. This group will focus on requirements and issues of open teleconference systems which contain voice communications between web browsers. We will also focus on integrating IRC service for it. This group will not create specifications but may provide feedback to relevant working groups, if necesssary.
    Join group Report a problem
  • experimental protocols

    3 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