This is the list of current Community and Business Groups. Anyone may join; W3C Membership is not required. However, you must have a W3C account.
Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.
316
Groups found
The overall goal/mission of this community group is to explore the requirements, best practices and implementation options for the conceptualization and specification of domain knowledge in AI.
We plan to place particular emphasis on the identification and the representation of AI facets and various aspects (technology, legislation, ethics etc) with the purpose to facilitate knowledge exchange and reuse.
Therefore the proposed outcomes could be instrumental to research and advancement of science and inquiry, as well as to increase the level of public awareness in general to enable learning and participation.
Proposed outcomes:
WHO SHOULD JOIN: researchers and practitioners with an interest in developing AI KR artifacts (ontology, machine learning, markup languages)
Accessibility is often provided through accommodations. Schools are legally obligated to provide accommodations to enrolled students with identified disabilities, based on their needs—sign language interpreters in lectures for deaf students, digital copies of textbooks for students who are blind or have reading difficulties, extended time on exams for students who need more time due to cognitive or physical disabilities.
With online learning, the obligations are less clear—for example, with MOOCs, where students around the world are taking courses but are not enrolled at the sponsoring school or organization. Also, accommodations are not well established—sign language interpreters and note takers are typically accommodations for the physical classroom. How does an organization ensure they are meeting obligations and giving online students the support they need participate fully and to be successful?
Providers of online learning are best off delivering courses that are accessible out-of-the-box, without the need for special accommodations. And many of the features that provide an accessible experience for people with disabilities benefit all learners. For example, lecture transcripts are an excellent tool for study and review. However, without deliberate attention to the technologies, standards, and guidelines that comprise the Web Platform, accessibility may be difficult to achieve, and learners with disabilities may be left behind.
The activities of the Accessible Online Learning W3C Community Group take place at the intersection of accessibility and online learning. We focus on reviewing current W3C resources and technologies to ensure the requirements for accessible online learning experiences are considered. We also identify areas where additional resources and technologies are needed to ensure full participation of people with disabilities in online learning experiences.
This group will not publish Specifications.
The W3C Augmented Reality Community Group is an open forum for collaborative discussions about the intersection of Augmented Reality and the Web, or more simply the Augmented Web. This forum welcomes discussions about related standards, the standardisation process, related market developments and the broader social implications of this new generation of the web.
We believe that the Augmented Web brings a unique perspective that pushes standards, APIs, hardware technologies and the broader web platform to the edge of their performance limits. The Augmented Web embraces the changes brought about by HTML5 and other related standards including Geolocation, DeviceOrientation, DeviceMotion, WebGL, Web Audio, Media Capture & Streams and WebRTC. The Augmented Web integrates all of these disparate technologies into an integrated new vision of the web.
This group will not produce specifications.
Instead it aims to build an integrated community voice that reaches out to all of the other relevant working groups and standards bodies to ensure that the Augmented Web perspective is clearly represented and considered. Our goal is to help ensure that the disparate standards and APIs being planned and implemented by these other groups can be seamlessly integrated into this new vision for the Augmented Web.
Read more about goals and operating guidelines in the Charter: http://www.w3.org/community/ar/wiki/Charter
This 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:
An initial related activity is the Mozilla Factory Open Hardware Project.
Furthermore, this group may publish specifications based on those knowledge such as webGPIO, webI2C API and so on.
The mission of this group is to establish a standard for creating a universally verifiable proof of any data, file, or series of events, by anchoring data to the blockchain and other sources. This allows anyone to prove the data existed at a point in time and has not been modified.
The group will publish and formalize the Chainpoint specification as a stable reference, maintain a test suite, and take feedback and use cases for the future evolution for the specification.
The Chainpoint Community Group will coordinate with the Blockchain Community Group for general standardization of blockchain-related technology, and will operate according to the Chainpoint CG charter. You can read more about Chainpoint, its history, and goals, on our recent blog post announcing Chainpoint 2.0.
This group invites participants who are actively developing and deploying proof-of-existence, timestamping, and data integrity solutions, who are skilled in blockchain technologies, and who can work on use cases for Chainpoint and related technologies.
The mission of the W3C Credible Web Community Group is to help shift the Web toward more trustworthy content without increasing censorship or social division. We want users to be able to tell when content is reliable, accurate, and shared in good faith, and to help them steer away from deceptive content. At the same time, we affirm the need for users to find the content they want and to interact freely in the communities they choose. To balance any conflict between these goals, we are committed to providing technologies which keep end-users in control of their Web experience.
The group's primary strategy involves data sharing on the Web, in the style of schema.org, using existing W3C data standards like JSON-LD. We believe significant progress toward our goals can be reached by properly specifying "credibility indicators", a vocabulary/schema for data about content and the surrounding ecosystem, which can help a person and/or machine decide whether a content item should be trusted.
Please see the group wiki for more details.
The mission of the W3C Data Privacy Vocabularies and Controls CG (DPVCG) is to develop a taxonomy of privacy terms, which include in particular terms from the new European General Data Protection Regulation (GDPR), such as a taxonomy of personal data as well as a classification of purposes (i.e., purposes for data collection), and events of disclosures, consent, and processing such personal data.
The Community Group shall officially start on 25th of May 2018, the official data of the GDPR coming into force, as a result of the W3C Workshop on Data Privacy Controls and Vocabularies in Vienna earlier this year.
It is the goal of the CG to harmonize related efforts and bring together stakeholders that already have brought forward proposals to develop respective vocabularies to enable semantic interoperability and interchange of transparency logs about personal data processing, enable data portability for data subjects, etc. The exact scope of use cases related to making personal data processing interoperable by respective standards in order to ease proof of compliance with the GDPR and related privacy protection regulations will be the first deliverable of the CG.
More concretely, the following steps and deliverables are planned so far.
For the moment, we plan the following milestones:
Milestones beyond the second meeting shall be defined as outcome of these first two F2F meetings. The current goal is to agree on first public drafts of minimal sets of vocabularies to be finished by December 2018, with first stable working drafts being reached latest on 25 May 2019.
The CG shall work in an agile manner to iteratively propose and refine its scope, starting from (i) collecting and prioritizing requirements and existing input vocabularies, (ii) extracting minimal overlaps/coverage, (iii) agreement on minimal representations, (iv) iterate.
In this sense the deliverables structure above shall be understood as current snapshot of the planned focus which directly reflects the prioritized outcomes of the Vienna workshop. If more is needed in terms of standardization, e.g., a discussion of protocols/architectures then we shall be open to extend the scope later on, as soon as first results have been achieved on those primary, initial goals.
The CG invites all interested stakeholders to contribute, particularly those people who expressed interest at the Vienna workshop, but as all W3C CGs considers itself an Open Community with the intention to grow to a critical mass to finally bring its results into a W3C working group for standardization.
In order to reach our goal to launch this CG on 25 May 2018 please support the launch of this group. You will need a W3C account to do so; request an account if necessary.
The mission of this group is to define the standard for distributed trace context propagation. Distributed trace context is used to enable monitoring and diagnostics scenarios in micro-services environment. It consists of request identifiers and key properties that needs to be propagated from one micro-service to another. These identifiers and properties are used to analyze an end-to-end distributed traces.
The group primary objective is to publish a specification for the protocols to use for distributed trace context propagation. Protocol includes wire format and recommended scenarios to use these protocols in applications, web servers, libraries, and platforms. The group also targets to produce reference implementation for some languages.
Standardized and universally used trace context propagation protocols enable monitoring and diagnostics scenarios that are hard to achieve otherwise. Authors of libraries, web servers, and application performance management (APM) vendors who are interested to improve micro-services monitoring and diagnostics story are encouraged to participate in this group.
We invite you to visit the main site for this Community Group (<https://w3c.github.io/mathonwebpages/>)
There are many technical issues in presenting mathematics in today's Open Web Platform, which has led to the poor access to Mathematics in Web Pages. This is in spite of the existing de jure or de facto standards for authoring mathematics, like MathML, LaTeX, or asciimath, which have been around for a very long time and are widely used by the mathematical and technical communities.
While MathML was supposed to solve the problem of rendering mathematics on the web it lacks in both implementations and general interest from browser vendors. However, in the past decade, many math rendering tools have been pushing math on the web forward using HTML/CSS and SVG.
One of the identified issues is that, while browser manufacturers have continually improved and extended their HTML and CSS layout engines, the approaches to render mathematics have not been able to align with these improvements. In fact, the current approaches to math layout could be considered to be largely disjoint from the other technologies of OWP. Another key issue, is that exposing (and thus leveraging) semantic information of mathematical and scientific content on the web needs to move towards modern practices and standards instead of being limited to a single solution (MathML). Such information is critical for accessibility, machine-readability, and re-use of mathematical content.
This Community Group intends to look at the problems of math on the web in a very bottom-up manner. Experts in this group should identify how the core OWP layout engines, centered around HTML, SVG, and CSS, can be re-used for the purpose of mathematical layout by mapping mathematical entities on top of these, thereby ensuring a much more efficient result, and making use of current and future OWP optimization possibilities. Similarly, experts should work to identify best practices for semantics from the point of view of today's successful solutions.
This work should also reveal where the shortcomings are, from the mathematical layout point of view, in the details of these OWP technologies, and propose improvements and possible additions to these, with the ultimate goal of reaching out to the responsible W3C Working Groups to make these changes. This work may also reveal new technology areas that should be specified and standardized on their own right, for example in the area of Web Accessibility.
The ultimate goal is to pave the way for a standard, highly optimized implementation architecture, on top of which mathematical syntaxes, like LaTeX or MathML, may be mapped to provide an efficient display of mathematical formulae. Note that, although this community group will concentrate on mathematics, many other areas, e.g., science and engineering, will benefit from (and factor into) the approach and from the core architecture.
The mission of the HTML5 Korean Community Group includes the following:
This Community Group is the successor of the HTML5 Korean Interest Group. This group will not publish Specifications.
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.
The Music Notation Community Group develops and maintains format and language specifications for notated music used by web, desktop, and mobile applications. The group aims to serve a broad range of users engaging in music-related activities involving notation, and will document these use cases.
The initial task of the Community Group is to maintain and update the MusicXML and SMuFL (Standard Music Font Layout) specifications. The goals are to evolve the specifications to handle new use cases and technologies, including greater use of music notation on the web, while maximizing the existing investment in implementations of the existing MusicXML 3.0 and SMuFL specifications.
The ODRL Community Group supports the promotion and future development of the W3C ODRL recommendations:
Specifically, the ODRL CG will:
Currently a file URL (file:///) is the defined way to access a local file in a browser. For various reasons (some outdated) this is not a preferred mechanism. There have been several unsuccessful attempts to create an alternative, but these were focused on application-type functionality and not content.
For content originally created in HTML, it makes the most sense to offer a mechanism to store the file locally in the same format. While, if this is desired, that process is the responsibility of the site, the browser functionality for it must be a recognized standard.
This initiative is focused on creating an offline url standard to access HTML files and containers stored locally in a compressed format, but otherwise behave as close to possible as an online site accessed via http.
The charter for this group is currently under development on GitHub. If you are interested please follow and contribute there.
This community group is part of the OpenActive initiative. Our goal is to develop technical specifications and best practices that will support the use of open and shared data relating to sports and physical activities.
Our primary focus is on standardising how to publish data about opportunities to be physically activity, defining best practices and APIs to enable booking of events and facilities, and improving interoperability of data across the sector.
To ensure that our specifications will support a variety of use cases, we welcome contributions from a range of organisations, including existing platforms and new startups.
While our work is technical, you don’t have to be a developer to contribute to our standards group. We are looking for input from product and service managers whose domain knowledge can help us to create better outputs.
2018-03-21: Group closed
The Paid Content Community Group exists to promote support for paid-for content on the web, including enabling better mechanisms for discovery, pricing, transactions, storage and access control. As the web matures, users are increasingly willing to pay for quality content. Advertising revenue for conventional publishing is also in decline. Consequently the ability to sell content efficiently is increasingly important to sustain expensively produced content such as investigative journalism.
The PCCG considers issues including:
The Publishing Business Group fosters ongoing participation by members of the publishing industry and overall publishing ecosystem in the development of the Web for publishing, and serves as a conduit for feedback between the publishing ecosystem and W3C. See the Publishing Business Group Charter for details.
The Business Group maintains a separate “Working” Web site, which includes documents, like information on meetings, index for meeting minutes, and other working documents. There is also a separate wiki for BG members. Finally, if necessary or convenient, Google Documents can also be used; these are collected in a separate Google Drive folder.
(The Working Web site’s content is actually served from a dedicated Github repository.)
The mission of the Schema Generator Community Group is to improve the availability, discovery and innovation of RDFa, Microdata, JSON-LD and other structured data related tooling. Schema generation tools pertaining to this group aim to ensure output can be validated with the W3C Schema validator or similar tools.
The group will assist others with discovering existing tools, updating online materials to find tools and supporting the development of new tools. The goal of this group is to foster the development of the ‘web of data’ through developer support, community engagement and advocacy. The Schema Generator Community Group will also assist by incubating support for works that include, but are not limited to, new RDF-related tools.
The Second Screen Community Group (CG) explores the use of secondary screens from Web pages. This Community Group incubates and develops specifications of network protocols that implement the Presentation API and the Remote Playback API.
This work has three primary purposes:
The scope of work proposed here goes beyond the current scope of the Second Screen Working Group (WG). Given wider support and adequate stability, we plan to migrate the proposals generated in this Community Group to an appropriate standards track, for example the IETF Standards Track or a W3C Working Group, for further contributions and formal standardization.
See the CG charter for more information.
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!)
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
A place for women participating in all aspects of the W3C, to connect, collaborate, and support each other.
The Community Group itself is only for people who identify as women, but anyone who supports our mission is encouraged to subscribe to the public mailing list, [email protected] (subscribe to this list) without becoming a CG member.
We use [email protected] as the address for W3C Women. Emails sent to this address, and its web mail archive, are only visible to W3C Women members.
This group will not produce Specifications.
Bluetooth is a standard for short-range wireless communication between devices. This group is developing a specification for Bluetooth APIs to allow websites to communicate with devices in a secure and privacy-preserving way. In particular the web Bluetooth API focuses on minimizing the device attack surface exposed to malicious websites, possibly by removing access to some existing Bluetooth features that are hard to implement securely. Further, the API takes the approach of a user interface to select and approve access to devices as opposed to using certification and installation.
Most of our activity happens in our GitHub repository, with supporting code in adjacent repositories in the WebBluetoothCG GitHub organization.
Media web application developers want to deploy their content on a wide and heterogeneous range of devices and platforms, e.g. televisions, set-top boxes, and mobile devices. To ensure a smooth user experience across devices, these user agents need to support a minimum set of Web technologies that developers can rely on being supported. This Community Group plans to specify such a set of Web technologies and additionally plans to provide guidance for developers and implementers e.g. on performance constraints and portability issues.
See the CG charter for more information.
The Web NFC Community Group will create a Near Field Communication API that is browser-friendly and adheres to the Web's security model. We believe that means the API will not expose full, low level NFC functionality, but rather a higher level subset that is safe for Web pages, protects user privacy, and does not annoy users with unnecessary or complex permission requests. See the Web NFC Community Group Charter and the Web NFC specification for more information.
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.
