Reports

<!DOCTYPE html> <html lang="en" dir="ltr"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width"> <link rel="shortcut icon" href="https://www.w3.org/community/wp-content/themes/StoryTeller/favicon.ico" type="image/x-icon"/> <link rel="stylesheet" href="https://www.w3.org/community/wp-content/themes/StoryTeller/style.css"> <title>Reports</title> <style> div.w3c_message { background: #FFF; letter-spacing: .5px; border-left: 3px solid #D69E88; color: #9d3718; font-size: 95%; margin: 0 auto; } .w3c_message ul { list-style: none; padding-top: 10px; padding-bottom: 10px; } .w3c_message h3 { display: none; } </style> <script src="/_sf/build/js/runtime.5282c7bdf5acd937a88e.js"></script><script src="/_sf/build/js/841.d3e8078f261ad782f1d5.js"></script><script src="/_sf/build/js/993.1a64c3bd5d421efc2252.js"></script><script src="/_sf/build/js/725.1d0b14139869141d898f.js"></script><script src="/_sf/build/js/cglist.7c4f8fc76aae10fc0a91.js"></script> </head> <body> <header> <div class="logos"> <a href="https://www.w3.org/" class="w3-logo"><img alt="w3c logo" class="animated fadeInLeft" src="https://www.w3.org/community/wp-content/themes/StoryTeller/img/svg/w3c-logo.svg"/></a> <a href="/community/" class="cgbg-logo"><img alt="w3c community group logo" class="animated fadeInRotate height" src="https://www.w3.org/community/wp-content/themes/StoryTeller/img/svg/cgbg-logo.svg"/></a> <a href="/community/" class="cgbg-logo-title"><h1 class="animated fadeInRight">Community & Business Groups</h1> </a> </div> <div class="white-bar"></div> <div class="white-circle"></div> <div class="blue-top"></div> </header> <div class="center ov-visible"> <nav id="access" class="right main-nav"> <ul id="menu-top-menu"> <li id="menu-item-60" class="cg menu-item menu-item-type-custom menu-item-object-custom current-menu-item menu-item-home menu-item-60"> <a title="Groups" href="/community/groups/"><span>Current Groups</span></a></li> <li id="menu-item-57" class="rp menu-item menu-item-type-custom menu-item-object-custom menu-item-57"><a href="/community/reports/"><span>Reports</span></a></li> <li id="menu-item-59" class="ab menu-item menu-item-type-post_type menu-item-object-page menu-item-59"><a title="About" href="/community/about/"><span>About</span></a></li> </ul> </nav> </div> <div class="center"> <div id="primary" class="maincolumn" role="complementary"> <div class="breadcrumbs"> <ul> <li><a href="/community/" title="Community & Business Groups">Home</a> / </li> <li>Reports</li> </ul> </div> <section class="group" id="content"> <h2 class="group-title">Reports</h2> <div id="w3c_content_body"> </div> <article class="page type-page status-publish hentry"> <div class="entry-content"> <p class="intro dark-blue">These are the Reports published by W3C Community Groups and Business Groups.</p> <p>Reports are either “Draft” or “Final.” When a group announces a Final Report that is a Specification, the group asks participants to make patent licensing commitments under the <a href="/community/about/process/final/">W3C Community Final Specification Agreement</a>. These commitments help to ensure that the Specification may be implemented by anyone without payment of royalties.</p> <p><strong>Note:</strong> Community and Business Group Reports are not W3C standards or <a href="/TR/">on the W3C standards track</a>.</p> </div> </article> </section> </div> <div class="sidebar"> <section id="custom_html-7" class="widget_text widget-container widget_custom_html"> <h3>About Publishing</h3> <div class="textwidget custom-html-widget"> <div> <p>Group Chairs publish reports. Publication announces the Report on the group’s blog, adds it to the list of Reports on the group’s home page, and adds it to this page. Learn more <a href="/community/about/faq/#how-do-we-publish-a-report">how to publish a report</a>.</p> </div> </div> </section> <section id="nav_menu-16" class="widget-container widget_nav_menu"> <h3>Quick Links</h3> <div class="menu-reports-rhs-menu-container"> <ul id="menu-reports-rhs-menu" class="menu"> <li id="menu-item-4656" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-4656"><a href="/community/reports/reqs/">Report Requirements</a></li> <li id="menu-item-4654" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-4654"><a title="W3C Community Contributor License Agreement (CLA) Deed" href="/about/process/cla-deed/">CLA Deed</a></li> <li id="menu-item-4655" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-4655"><a title="W3C Community Final Specification Agreement (FSA) Deed" href="/community/about/process/fsa-deed/">FSA Deed</a></li> </ul> </div> </section> </div> </div> <div class="full-width ov-visible"> <div id="first" class="widget-area center"> <section class="sidebar facets"> <div id="undefined-sticky-wrapper" class="sticky-wrapper" style="height: 80.7333px;"><div class="wrap-filtering"> <form id="filtering"> <div class="upper-filters clearfix"> <div id="live-search"> <label for="filter" class="visuallyhidden">Live search by group name:</label> <input type="text" id="filter" class="text-input" value="" placeholder="Search by group name" name="search"> <a class="clear" style="display: none;">x</a> </div> <ul class="sort-box"> <li> <a data-order="ASC" data-sort="title" class="sort-button" id="sort-title" title="Sort groups by title (repeat to reverse sort order)">Sort by title</a> </li> <li> <a data-order="" data-sort="created" class="sort-button" id="sort-date" title="Sort groups by creation date (repeat to reverse sort order)">Sort by creation date</a> </li> </ul> </div> <div class="lower-filters clearfix"> <ul id="types" class="sort-box"> <li> <label for="cgroups">Show community groups</label> <input id="cgroups" type="checkbox" checked="checked"> </li> <li> <label for="bgroups">Show business groups</label> <input id="bgroups" type="checkbox" checked="checked"> </li> </ul> <ul class="radio-box"> <li> <label for="expand-groups">Expand all groups</label> <input id="expand-groups" type="radio" value="Expand all groups" name="groups"> </li> <li> <label for="collapse-groups">Collapse all groups</label> <input id="collapse-groups" type="radio" value="Collapse all groups" name="groups"> </li> </ul> </div> </form> <div class="status active"> <p id="group_count">85</p> <p id="filter-count">Group<span class="plural">s</span> found</p> </div> </div> </div> </section> <section class="maincolumn group-list sortable-list" data-sortedby="activity"> <ul> <li data-title="Accessibility at the Edge Community Group" data-created="2022-05-26T23:56Z" class="sortable-entry cg"> <article id="a11yedge"> <h2 class="group-title"><a href="https://www.w3.org/community/a11yedge/" id="a11yedge">Accessibility at the Edge Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The mission of the Accessibility at the Edge Community Group is to examine improvements to internet accessibility via "edge computing", a relatively new paradigm that focuses on performing tasks at the edge of the network. Unlike cloud computing, edge computing emphasizes activities that occur closer to the user; these could include accessibility oriented user-agent extensions, applications on content delivery networks, JavaScript-enabled capabilities, AI or ML. The group is a forum for discussing both currently available products, potentially new applications not yet commercially available, as well as objective measures of the quality of any one of these. Our tasks can include inventorying both opportunities and challenges, drafting and incubating Internet specifications for further assessment, standardization, prototyping and testing of reference implementations. A11Y-EDGE CG meetings work and operate under the <a href="https://www.w3.org/Consortium/cepc/">W3C Code of Ethics and Professional Conduct</a>.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://a11yedge.github.io/overlays/" rel="nofollow">Overlay Applications in Web Accessibility</a></td> </tr> <tr> <td><a href="https://a11yedge.github.io/capabilities/" rel="nofollow">Overlay Capabilities Inventory</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="AI KR (Artificial Intelligence Knowledge Representation) Community Group" data-created="2018-07-03T10:22Z" class="sortable-entry cg"> <article id="aikr"> <h2 class="group-title"><a href="https://www.w3.org/community/aikr/" id="aikr">AI KR (Artificial Intelligence Knowledge Representation) Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc"><ul> <li><a rel="nofollow" href="https://www.w3.org/community/aikr/welcome/">Welcome post</a></li> <li><a rel="nofollow" href="https://www.w3.org/community/aikr/wiki">Group's wiki</a></li> <li>See also the group's pages from the right-hand side menu</li> </ul> <p>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.</p> <p>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.</p> <p>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.</p> <p><strong>Proposed outcomes:</strong></p> <ul> <li>A comprehensive <a rel="nofollow" href="https://www.w3.org/community/aikr/welcome/ai-kr-task-list/knowledge-sources-for-ai-kr/">list of open access resources</a> in both AI and KR (useful to teaching and research)</li> <li>A set of <a rel="nofollow" href="https://www.w3.org/community/aikr/welcome/ai-kr-task-list/metadata/">metadata</a> derived from these resources</li> <li>A <a rel="nofollow" href="https://www.w3.org/community/aikr/concept-maps/">concept map</a> of the domain</li> <li>A natural language vocabulary to represent various aspects of AI</li> <li>One or more encoding/implementations/ machine language version of the vocabulary, such as ChatBot Natural Language Understanding & Natural Language Generation</li> <li>Methods for KR management, especially Natural Language Learning / Semantic Memory</li> </ul> <p><strong>WHO SHOULD JOIN:</strong> researchers and practitioners with an interest in developing AI KR artifacts (ontology, machine learning, markup languages)</p> <p><a rel="nofollow" href="https://tinyurl.com/yb6h72w8">Editable doc</a>.</p> </div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2021-10-25T08:48Z"> 2021-10-25</time></td> <td><a href="https://www.w3.org/community/aikr/wiki/File:AI_KR_FIRST_REPORT_PUBLISHED_VERSION.pdf">aikrcgfirstreportfinalvaug22</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/aikr/spec/200/commitments">Licensing commitments</a></td> </tr> </tbody> </table> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://www.w3.org/community/aikr/files/2022/04/AIKRCG202110.pdf">First Draft Report</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Algorithmic Modelling Community Group" data-created="2013-05-21T02:22Z" class="sortable-entry cg"> <article id="model"> <h2 class="group-title"><a href="https://www.w3.org/community/model/" id="model">Algorithmic Modelling Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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.</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2013-05-31T07:13Z"> 2013-05-31</time></td> <td><a href="https://www.w3.org/2013/06/model-ref-20130418.html">Algorithmic Modelling Reference Model</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/model/spec/57/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Automotive and Transportation Business Group" data-created="2013-02-21T15:02Z" class="sortable-entry bg"> <article id="autowebplatform"> <h2 class="group-title"><a href="https://www.w3.org/community/autowebplatform/" id="autowebplatform">Automotive and Transportation Business Group</a></h2> <div class="group-content collapse-small"> <div class="desc"><p>The mission of the Automotive and Transportation Group was to act as an incubator of ideas for standardization for connected vehicles and the broader transportation data space. It had produced some early draft specifications for making vehicle signals available in a browser runtime as a first class object. Those specifications were the basis for launching the <a rel="nofollow" href="/groups/wg/auto/">W3C Automotive Working Group</a> (which closed on 22 February 2024).</p> <p>Fuller description of the scope is in <a rel="nofollow" href="/2020/auto-transportation-charter">the charter</a>.</p></div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2014-05-14T16:41Z"> 2014-05-14</time></td> <td><a href="https://www.w3.org/2014/automotive/vehicle_spec.html">Vehicle Information API</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/autowebplatform/spec/75/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2014-05-14T16:45Z"> 2014-05-14</time></td> <td><a href="https://www.w3.org/2014/automotive/data_spec.html">Vehicle Data Interfaces</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/autowebplatform/spec/77/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2022-02-08T13:28Z"> 2022-02-08</time></td> <td><a href="https://www.w3.org/2022/auto/bg-report/vsso-core-re.html">VSSo Core: Vehicle Signal Specification Core Ontology</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/autowebplatform/spec/204/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2022-02-08T13:29Z"> 2022-02-08</time></td> <td><a href="https://www.w3.org/2022/auto/bg-report/vsso-re.html">VSSo: Vehicle Signal Specification Ontology</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/autowebplatform/spec/205/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="BDE-Secure societies - protecting freedom and security of Europe and its citizens Community Group" data-created="2015-04-22T17:34Z" class="sortable-entry cg"> <article id="bde-secure-societies"> <h2 class="group-title"><a href="https://www.w3.org/community/bde-secure-societies/" id="bde-secure-societies">BDE-Secure societies - protecting freedom and security of Europe and its citizens Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc"><p>This group is now closed; its work has moved to the <a rel="nofollow" href="https://www.w3.org/community/bde/">Big Data Europe Community Group</a>.</p> <p>This is one of 7 Community Groups established under the <a rel="nofollow" href="http://www.big-data-europe.eu/">BigDataEurope Project</a>, a Coordination and Support Action under the European Union’s Horizon 2020 Programme, each one tailored to a specific <a rel="nofollow" href="http://ec.europa.eu/programmes/horizon2020/en/h2020-section/societal-challenges">Societal Challenge</a>. The discussions in this group will be used to design and realise the ICT infrastructure needed to benefit from big data technologies, maximising the opportunities of the latest European RTD developments, including multilingual data harvesting, data analytics, and data visualisation.</p> <p>This Community Group is specifically interested in the challenge related to secure societies - protecting freedom and security of Europe and its citizens, and is lead by the <a rel="nofollow" href="http://www.satcen.europa.eu/">European Union Satellite Centre</a> (SatCen).</p> <p>This group will not publish specifications.</p></div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://www.w3.org/community/bde-secure-societies/2015/07/10/bigdataeurope-workshop-on-h2020-societal-challenge-secure-societies/">BigDataEurope Workshop on H2020 societal challenge Secure Societies</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Best Practices for Multilingual Linked Open Data Community Group" data-created="2013-04-09T10:50Z" class="sortable-entry cg"> <article id="bpmlod"> <h2 class="group-title"><a href="https://www.w3.org/community/bpmlod/" id="bpmlod">Best Practices for Multilingual Linked Open Data Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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.</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2015-07-30T12:36Z"> 2015-07-30</time></td> <td><a href="https://www.w3.org/2015/09/bpmlod-reports/multilingual-dictionaries/">Guidelines for Linguistic Linked Data Generation: Multilingual Dictionaries (BabelNet)</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/bpmlod/spec/100/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2015-07-30T12:38Z"> 2015-07-30</time></td> <td><a href="https://www.w3.org/2015/09/bpmlod-reports/bilingual-dictionaries/">Guidelines for Linguistic Linked Data Generation: Bilingual Dictionaries</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/bpmlod/spec/101/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2015-09-29T09:01Z"> 2015-09-29</time></td> <td><a href="https://www.w3.org/2015/09/bpmlod-reports/multilingual-terminologies/">Guidelines for Linguistic Linked Data Generation: Multilingual Terminologies (TBX)</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/bpmlod/spec/103/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2015-10-27T16:29Z"> 2015-10-27</time></td> <td><a href="https://www.w3.org/2015/09/bpmlod-reports/nif-based-nlp-webservices/">Guidelines for developing NIF-based NLP Web Services</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/bpmlod/spec/105/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2015-10-27T16:31Z"> 2015-10-27</time></td> <td><a href="https://www.w3.org/2015/09/bpmlod-reports/lld-exploitation/">Guidelines for LLD Exploitation</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/bpmlod/spec/106/commitments">Licensing commitments</a></td> </tr> </tbody> </table> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://bpmlod.github.io/Crosslingual_linking_report/" rel="nofollow">Guidelines for Cross-lingual linking</a></td> </tr> <tr> <td><a href="http://bpmlod.github.io/report/WordNets/index.html" rel="nofollow">Guidelines for Linguistic Linked Data Generation: WordNets</a></td> </tr> <tr> <td><a href="http://bpmlod.github.io/report/nif-corpus/index.html" rel="nofollow">Guidelines for Linked Data corpus creation using NIF</a></td> </tr> <tr> <td><a href="http://bpmlod.github.io/report/LLOD-aware-services/index.html" rel="nofollow">Guidelines for LLOD aware services</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Chinese DID & VC Community Group" data-created="2023-08-16T12:47Z" class="sortable-entry cg"> <article id="cndid"> <h2 class="group-title"><a href="https://www.w3.org/community/cndid/" id="cndid">Chinese DID & VC Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The Chinese DID & VC Community Group provides a forum to identify and discuss the technical, use cases and best practices of DID and VC technologies, with the goal to bring better user experience and collect requirements for future DID and VC related specifications. </div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2024-07-25T09:31Z"> 2024-07-25</time></td> <td><a href="https://www.w3.org/community/reports/cndid/CG-FINAL-iifaa-did-20241231/">IIFAA Decentralized Trusted Authentication Technical Specification - Part 1: General Requirements</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/cndid/spec/267/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Cloud Computing Community Group" data-created="2011-11-03T16:01Z" class="sortable-entry cg"> <article id="cloud"> <h2 class="group-title"><a href="https://www.w3.org/community/cloud/" id="cloud">Cloud Computing Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The group will examine and create specifications related to distributed computation and storage, with an XML network transport layer and possible mapping to RDF.</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2012-09-28T02:00Z"> 2012-09-28</time></td> <td><a href="https://www.w3.org/2013/04/cloud-ucr-20120518.html">Use Cases and Requirements</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/cloud/spec/35/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2012-09-28T02:01Z"> 2012-09-28</time></td> <td><a href="https://www.w3.org/2013/04/cloud-svc-20130422.html">Cloud Provider Service Engagement</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/cloud/spec/36/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2012-11-20T08:37Z"> 2012-11-20</time></td> <td><a href="https://www.w3.org/2013/04/cloud-mdl-20130422.html">Cloud Processing Model</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/cloud/spec/38/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2012-12-30T12:08Z"> 2012-12-30</time></td> <td><a href="https://www.w3.org/2013/04/cloud-strge-20120425.html">Storage Mapping</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/cloud/spec/40/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2013-02-01T05:30Z"> 2013-02-01</time></td> <td><a href="https://www.w3.org/2013/04/cloud-api-20130426.html">Cloud API</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/cloud/spec/43/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2013-03-13T08:36Z"> 2013-03-13</time></td> <td><a href="https://www.w3.org/2013/04/cloud-rdf-20130429.html">Cloud Processing in RDF</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/cloud/spec/46/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2013-04-07T07:11Z"> 2013-04-07</time></td> <td><a href="https://www.w3.org/2013/04/cloud-vsltn-20130403.html">Cloud Visualisation</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/cloud/spec/52/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Cognitive AI Community Group" data-created="2019-12-10T14:28Z" class="sortable-entry cg"> <article id="cogai"> <h2 class="group-title"><a href="https://www.w3.org/community/cogai/" id="cogai">Cognitive AI Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc"><p>The real world is frustratingly uncertain, incomplete and inconsistent. This is challenging for traditional approaches to information systems, and a new paradigm is needed that combines symbolic and statistical techniques, building upon decades of work in the cognitive sciences, and over 500 million years of natural selection. This will allow us to create cognitive agents that learn and reason based upon prior knowledge and past experience, and which can satisfy the need for, transparency in decision making, and continuous learning for adapting to ever changing needs. This community group will address opportunities for cognitive agents using graphs, statistics, rules and graph algorithms, starting with an amalgam of RDF and Property Graphs, together with Web architecture for cognitive databases.</p> <p>More specifically, the Cognitive AI Community Group will work on use cases and requirements, demo's, open source, and scaling experiments. For more details, see:</p> <p>• <a rel="nofollow" href="https://github.com/w3c/cogai">Cognitive AI CG GitHub Repository</a></p> <p>• <a rel="nofollow" href="https://w3c.github.io/cogai/">Chunks and Rules Specification</a></p> <p>• <a rel="nofollow" href="https://www.w3.org/Data/demos/chunks/talks/Sentient-Web-Raggett-2020-07-31.pdf">Keynote on Cognitive AI for the 2020 Summer School on AI in Industry 4.0</a></p> <p>• <a rel="nofollow" href="https://www.w3.org/2020/sentient-web-20200608.pdf">An older talk on Cognitive AI and the Sentient Web</a></p> <p>• <a rel="nofollow" href="https://www.w3.org/Data/demos/chunks/chunks.html">Longer treatise on Cognitive AI</a></p> <p>• <a rel="nofollow" href="https://lists.w3.org/Archives/Public/public-cogai/">Public mailing list archive</a></p> <p>• <a rel="nofollow" href="https://github.com/w3c/cogai/blob/master/Contributing.md">Contributing to the Cognitive AI Community Group</a></p></div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://w3c.github.io/cogai/chunks-and-rules.html">Chunks and Rules</a></td> </tr> <tr> <td><a href="https://w3c.github.io/cogai/pkn.html">Plausible Knowledge Notation (PKN)</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Conversational Interfaces Community Group" data-created="2019-02-28T07:35Z" class="sortable-entry cg"> <article id="conv"> <h2 class="group-title"><a href="https://www.w3.org/community/conv/" id="conv">Conversational Interfaces Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The mission of the Conversational Interfaces Community Group is to enable web developers to collaborate and share conversational experiences for a variety of domains. Most dialogue systems serve interactive experiences in their own domain specific language, causing a fragmented zoo of proprietary formats. For example, Google Home or Alexa do not share a common intermediate representation, which makes writing wide-spread content inaccessible to the mass audience. We study existing specs and design standards to harness proven techniques into common agreement. See the <a href="https://conversational-interfaces.github.io/charter/" rel="nofollow">the Community Group's charter</a>.</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2019-03-19T19:49Z"> 2019-03-19</time></td> <td><a href="https://www.w3.org/2019/04/dmpl/">Dialogue Manager Programming Language (DMPL)</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/conv/spec/162/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2019-11-14T19:31Z"> 2019-11-14</time></td> <td><a href="https://www.w3.org/2019/11/dms/">DM Script</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/conv/spec/177/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2020-04-13T19:41Z"> 2020-04-13</time></td> <td><a href="https://www.w3.org/2020/04/dms/">DM Script 2020</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/conv/spec/182/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2020-04-13T19:42Z"> 2020-04-13</time></td> <td><a href="https://www.w3.org/2020/04/dmpl/">Dialogue Manager Programming Language (DMPL) 2020</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/conv/spec/183/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Core Mobile Web Platform Community Group" data-created="2012-02-27T12:03Z" class="sortable-entry cg"> <article id="coremob"> <h2 class="group-title"><a href="https://www.w3.org/community/coremob/" id="coremob">Core Mobile Web Platform Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">This group is closed, it work has moved to the Web and Mobile Interest Group (http://www.w3.org/Mobile/IG/). The goal of the Core Mobile Web Platform Community Group (CG) is to accelerate the adoption of the Mobile Web as a compelling platform for the development of modern mobile web applications. In order to achieve this mission, the CG will bring developers, equipment manufacturers, browser vendors, operators and other relevant members of the industry together to agree on core features developers can depend on, create related conformance test suites and provide to W3C (and non-W3C) groups use cases, scenarios, and other input related to successful mobile development. Read the full charter: http://www.w3.org/community/coremob/charter/</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2012-12-24T12:04Z"> 2012-12-24</time></td> <td><a href="https://coremob.github.com/coremob-2012/FR-coremob-20130131.html">Core Mobile Web Platform - 2012</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/coremob/spec/39/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Credentials Community Group" data-created="2014-08-06T18:25Z" class="sortable-entry cg"> <article id="credentials"> <h2 class="group-title"><a href="https://www.w3.org/community/credentials/" id="credentials">Credentials Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The mission of the W3C Credentials Community Group is to explore the creation, storage, presentation, verification, and user control of credentials. We focus on a verifiable credential (a set of claims) created by an issuer about a subject—a person, group, or thing—and seek solutions inclusive of approaches such as: self-sovereign identity; presentation of proofs by the bearer; data minimization; and centralized, federated, and decentralized registry and identity systems. Our tasks include drafting and incubating Internet specifications for further standardization and prototyping and testing reference implementations.</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2024-12-10T15:11Z"> 2024-12-10</time></td> <td><a href="https://www.w3.org/community/reports/credentials/CG-FINAL-traceability-interop-20241204/">Traceability Interoperability v1.0</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/credentials/spec/277/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2024-12-10T15:12Z"> 2024-12-10</time></td> <td><a href="https://www.w3.org/community/reports/credentials/CG-FINAL-traceability-vocab-20241204/">Traceability Vocabulary v1.0</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/credentials/spec/278/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2017-05-12T16:36Z"> 2017-05-12</time></td> <td><a href="https://www.w3.org/2017/05/vc-use-cases/CGFR/2017-05-01/">Verifiable Claims Use Cases 1.0</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/credentials/spec/131/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2017-05-12T16:38Z"> 2017-05-12</time></td> <td><a href="https://www.w3.org/2017/05/vc-data-model/CGFR/2017-05-01/">Verifiable Claims Data Model and Representations 1.0</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/credentials/spec/132/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2019-09-13T03:29Z"> 2019-09-13</time></td> <td><a href="https://www.w3.org/2019/08/did-20190828/">Decentralized Identifiers (DIDs) v0.13 Data Model and Syntaxes</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/credentials/spec/174/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2022-07-26T13:01Z"> 2022-07-26</time></td> <td><a href="https://www.w3.org/community/reports/credentials/CG-FINAL-lds-jws2020-20220721/">JSON Web Signature 2020</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/credentials/spec/214/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2022-07-26T13:02Z"> 2022-07-26</time></td> <td><a href="https://www.w3.org/community/reports/credentials/CG-FINAL-di-ecdsa-2019-20220724/">ECDSA Cryptosuite v2019</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/credentials/spec/215/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2022-07-26T13:02Z"> 2022-07-26</time></td> <td><a href="https://www.w3.org/community/reports/credentials/CG-FINAL-di-eddsa-2020-20220724/">EdDSA Cryptosuite v2020</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/credentials/spec/216/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2022-07-26T13:31Z"> 2022-07-26</time></td> <td><a href="https://www.w3.org/community/reports/credentials/CG-FINAL-data-integrity-20220722/">Data Integrity 1.0</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/credentials/spec/217/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2022-10-12T13:03Z"> 2022-10-12</time></td> <td><a href="https://www.w3.org/community/reports/credentials/CG-FINAL-rdf-dataset-canonicalization-20221009/">RDF Dataset Canonicalization</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/credentials/spec/220/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Credible Web Community Group" data-created="2017-10-28T13:20Z" class="sortable-entry cg"> <article id="credibility"> <h2 class="group-title"><a href="https://www.w3.org/community/credibility/" id="credibility">Credible Web Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc"><p>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.</p> <p>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.</p> <p>Please see the <a rel="nofollow" href="wiki/">group wiki</a> for more details.</p></div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2018-10-11T21:37Z"> 2018-10-11</time></td> <td><a href="https://www.w3.org/2018/10/credibility-tech/">Technological Approaches to Improving Credibility Assessment on the Web</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/credibility/spec/152/commitments">Licensing commitments</a></td> </tr> </tbody> </table> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://credweb.org/reviewed-signals/" rel="nofollow">Reviewed Credibility Signals</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Customer Experience Digital Data Community Group" data-created="2012-11-05T16:52Z" class="sortable-entry cg"> <article id="custexpdata"> <h2 class="group-title"><a href="https://www.w3.org/community/custexpdata/" id="custexpdata">Customer Experience Digital Data Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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. </div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2013-12-16T14:09Z"> 2013-12-16</time></td> <td><a href="https://www.w3.org/2013/12/ceddl-201312.pdf">Customer Experience Digital Data Layer</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/custexpdata/spec/67/commitments">Licensing commitments</a></td> </tr> </tbody> </table> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://www.w3.org/community/custexpdata/wiki/images/9/93/W3C_CustomerExperienceDigitalDataAcquisition_Draft_v0.5.pdf" rel="nofollow">Customer Experience Digital Data Acquisition</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Data Privacy Vocabularies and Controls Community Group" data-created="2018-05-24T10:14Z" class="sortable-entry cg"> <article id="dpvcg"> <h2 class="group-title"><a href="https://www.w3.org/community/dpvcg/" id="dpvcg">Data Privacy Vocabularies and Controls Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc"><p>The mission of the W3C Data Privacy Vocabularies and Controls CG (DPVCG) is to develop a taxonomy of privacy and data protection related terms, which include in particular terms from the new European <a href="http://eur-lex.europa.eu/eli/reg/2016/679/oj" target="_blank" rel="noreferrer noopener nofollow">General Data Protection Regulation (GDPR)</a>, 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.</p> <p>The DPVCG was created as an outcome of the W3C Workshop on Data Privacy Controls and Vocabularies in Vienna in 2017, and started on 25th May 2018 – the date of the enforcement of GDPR. Since then, the DPVCG has worked to fulfil its aims and objectives, and produced the <a rel="noreferrer noopener nofollow" href="https://www.w3.org/ns/dpv" target="_blank">Data Privacy Vocabulary (DPV)</a> as a deliverable. </p> <p>Membership to the group is open to all interested individuals and organisations. To join the group, you need a valid W3C account – which is free to get and can be <a rel="noreferrer noopener nofollow" href="https://www.w3.org/accounts/request" target="_blank">requested here</a>. The group meets usually through online meeting calls, details of which, including past minutes, can be <a rel="noreferrer noopener nofollow" href="https://www.w3.org/community/dpvcg/wiki/Meeting_Calls" target="_blank">found here</a>. The group also interacts through a <a rel="noreferrer noopener nofollow" href="https://lists.w3.org/Archives/Public/public-dpvcg/" target="_blank">mailing list</a> regarding topics, discussions, sharing of agendas, actions, and other relevant items. The resources and work relevant to the group is hosted on the <a rel="noreferrer noopener nofollow" href="https://github.com/dpvcg/" target="_blank">GitHub platform under the DPVCG name</a>.</p> <p>The group is currently chaired by:</p> <ul><li><a rel="noreferrer noopener nofollow" href="https://harshp.com" target="_blank">Harshvardhan J. Pandit</a> (<a rel="noreferrer noopener nofollow" href="https://www.adaptcentre.ie/" target="_blank">ADAPT SFI Research Centre</a>, <a rel="noreferrer noopener nofollow" href="https://www.tcd.ie/" target="_blank">Trinity College Dublin</a>)</li></ul> <p>Previously, it was chaired by:</p> <ul><li><a rel="nofollow" href="https://www.w3.org/People/Bos/">Bert Bos</a> (<a href="https://www.ercim.eu/" target="_blank" rel="nofollow">ERCIM </a><a rel="nofollow" href="https://www.w3.org">W3C</a>)</li><li><a href="http://polleres.net/" target="_blank" rel="nofollow">Axel Polleres</a> <a href="https://www.wu.ac.at/" target="_blank" rel="nofollow">(WU Wirschaftsuniversitat Wien – Vienna University of Economics and Business</a>)</li></ul> <h2>Participation in Group Activities</h2> <p>The working of the group is fairly open and transparent in its process, with most of the information present on the <a rel="nofollow" href="https://www.w3.org/community/dpvcg/wiki/">wiki</a>. For past work, actions, issues, and records – please refer to the <a rel="nofollow" href="https://www.w3.org/community/dpvcg/wiki/">wiki</a> and threads on the <a href="https://lists.w3.org/Archives/Public/public-dpvcg/" target="_blank" rel="nofollow">mailing list</a>. Anyone can use the <a href="https://lists.w3.org/Archives/Public/public-dpvcg/" target="_blank" rel="nofollow">mailing list</a> to ask questions, suggest topics, raise issues, and offer solutions. Non-members might receive an automated reply asking them to authenticate their email or email address for posting.</p> <p>Similarly, calls are usually open to attend, with the agenda shared on the public mailing list. Call details may be shared on the internal mailing lists accessible to only members for security purposes – so it may be best to ask the chair(s) or a member for attending a call.</p> <p>General questions regarding what the group considers in scope can be determined from the aims and objectives. Specific queries or propositions should be conveyed to the mailing list. For issues regarding the DPV, including addition of concepts or a query or other relevant topics – you can use the mailing list or the issues feature in a <a href="https://github.com/dpvcg/" target="_blank" rel="nofollow">GitHub repo</a>.</p> <h2>Data Privacy Vocabulary (DPV)</h2> <p>The DPV is a vocabulary (terms) and an ontology (relationships) serialised using semantic-web standards to represent concepts associated with privacy and data protection, primarily derived from GDPR. It enables representation of which <em>personal data categories</em> are undergoing a what kind of <em>processing</em> by a specific <em>data controller</em> and/or transferred to some <em>recipient</em> for a particular <em>purpose</em>, based on a specific <em>legal basis</em> (e.g., consent, or other legal grounds such as legitimate interest, etc.), with specified <em>technical and organisational measures and restrictions</em> (e.g., storage locations and storage durations) in place.</p> <p>The DPV is useful as a machine-readable representation of personal data processing and can be adopted in relevant use-cases such as legal compliance documentation and evaluation, policy specification, consent representation and requests, taxonomy of legal terms, and annotation of text and data.</p> <p>The DPV is an evolving vocabulary – as the DPVCG continues to work on updating it with broader concepts as well as enriching its hierarchy of concepts. For this, we invite contributions of concepts, use-cases, requirements, and applications.</p> </div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2019-06-07T15:49Z"> 2019-06-07</time></td> <td><a href="https://www.w3.org/community/reports/dpvcg/CG-FINAL-dpv-20221205">Data Privacy Vocabulary (DPV)</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/dpvcg/spec/171/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2019-06-07T15:50Z"> 2019-06-07</time></td> <td><a href="https://www.w3.org/community/reports/dpvcg/CG-FINAL-dpv-gdpr-20221205">DPV-GDPR: GDPR Extension for DPV</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/dpvcg/spec/172/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2022-12-04T23:31Z"> 2022-12-04</time></td> <td><a href="https://www.w3.org/community/reports/dpvcg/CG-FINAL-dpv-pd-20221205">DPV-PD: Extended Personal Data categories for DPV</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/dpvcg/spec/221/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2022-12-05T08:17Z"> 2022-12-05</time></td> <td><a href="https://www.w3.org/community/reports/dpvcg/CG-FINAL-primer-20221205">Primer</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/dpvcg/spec/222/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2022-12-05T08:29Z"> 2022-12-05</time></td> <td><a href="https://www.w3.org/community/reports/dpvcg/CG-FINAL-guide-dpv-owl-20221006">Guide for using DPV in OWL2</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/dpvcg/spec/223/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Design Tokens Community Group" data-created="2019-07-31T20:49Z" class="sortable-entry cg"> <article id="design-tokens"> <h2 class="group-title"><a href="https://www.w3.org/community/design-tokens/" id="design-tokens">Design Tokens Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The Design Tokens Community Group's goal is to provide standards upon which products and design tools can rely for sharing stylistic pieces of a design system at scale.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://design-tokens.github.io/community-group/format/" rel="nofollow">Design Tokens Format Module</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Distributed Trace Context Community Group" data-created="2017-12-13T11:25Z" class="sortable-entry cg"> <article id="trace-context"> <h2 class="group-title"><a href="https://www.w3.org/community/trace-context/" id="trace-context">Distributed Trace Context Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc"><p><strong>This group has completed its work. People interested in this topic should join the <a href="https://www.w3.org/groups/wg/distributed-tracing/">Distributed Tracing Working Group</a>.</strong></p> <p>The mission of this group was 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.</p> <p>The group primary objective was 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 targetted to produce reference implementation for some languages.</p> <p>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 interested to improve micro-services monitoring and diagnostics story were encouraged to participate in this group.</p></div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://w3c.github.io/distributed-tracing/report-trace-context.html">trace context</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Entity Reconciliation Community Group" data-created="2019-06-11T06:09Z" class="sortable-entry cg"> <article id="reconciliation"> <h2 class="group-title"><a href="https://www.w3.org/community/reconciliation/" id="reconciliation">Entity Reconciliation Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">Matching entities across data sources using different identifiers and formats is a pervasive issue on the web. This group revolves around developing a web API that data providers can expose, which eases the reconciliation of third-party data to their own identifiers. OpenRefine's reconciliation API is used as a starting point. Our goals are to document this existing API, share our experiences and lessons learnt from it, propose an improved protocol in the view of promoting it as a standard, and build tooling around it. A description of the existing protocol can be found here: https://reconciliation-api.github.io/specs/latest/ </div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2019-12-15T14:20Z"> 2019-12-15</time></td> <td><a href="https://www.w3.org/community/reports/reconciliation/CG-FINAL-specs-0.1-20230321/">Reconciliation Service API v0.1</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/reconciliation/spec/179/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2022-07-16T16:41Z"> 2022-07-16</time></td> <td><a href="https://www.w3.org/community/reports/reconciliation/CG-FINAL-specs-0.2-20230410/">Reconciliation Service API v0.2</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/reconciliation/spec/212/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="EPUB 3 Community Group" data-created="2017-02-06T19:48Z" class="sortable-entry cg"> <article id="epub3"> <h2 class="group-title"><a href="https://www.w3.org/community/epub3/" id="epub3">EPUB 3 Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The EPUB 3 Community Group is a forum for ongoing technical development of EPUB 3 and related extension specifications and ancillary deliverables. The <a rel="nofollow" href="https://www.w3.org/2017/02/EPUB3CGcharter">EPUB 3 Community Group charter</a> contains full details. </div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2018-09-24T19:50Z"> 2018-09-24</time></td> <td><a href="https://www.w3.org/publishing/epub32/epub-spec.html">EPUB 3.2</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/epub3/spec/150/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2019-05-15T17:15Z"> 2019-05-15</time></td> <td><a href="https://www.w3.org/publishing/epub32/epub-packages.html">EPUB Packages 3.2</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/epub3/spec/165/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2019-05-15T17:19Z"> 2019-05-15</time></td> <td><a href="https://www.w3.org/publishing/epub32/epub-contentdocs.html">EPUB Content Documents 3.2</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/epub3/spec/166/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2019-05-15T17:19Z"> 2019-05-15</time></td> <td><a href="https://www.w3.org/publishing/epub32/epub-ocf.html">EPUB Open Container Format (OCF) 3.2</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/epub3/spec/167/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2019-05-15T17:20Z"> 2019-05-15</time></td> <td><a href="https://www.w3.org/publishing/epub32/epub-mediaoverlays.html">EPUB Media Overlays 3.2</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/epub3/spec/168/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="EXPath Community Group" data-created="2012-04-24T12:00Z" class="sortable-entry cg"> <article id="expath"> <h2 class="group-title"><a href="https://www.w3.org/community/expath/" id="expath">EXPath Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The mission of this group is to lead to extension of XPath and all related technologies (XSLT, XQuery, XProc, XForms, XML Schema).</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2013-03-13T16:54Z"> 2013-03-13</time></td> <td><a href="https://www.w3.org/2013/12/expath-binary-20131203/">Binary Module</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/expath/spec/47/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2018-08-30T13:15Z"> 2018-08-30</time></td> <td><a href="https://www.w3.org/2018/11/http-client-20181120.html">HTTP Client</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/expath/spec/149/commitments">Licensing commitments</a></td> </tr> </tbody> </table> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://expath.org/spec/pkg/latest" rel="nofollow">Packaging System</a></td> </tr> <tr> <td><a href="http://expath.org/spec/file/latest" rel="nofollow">File Module</a></td> </tr> <tr> <td><a href="http://expath.org/spec/webapp/latest" rel="nofollow">Web Applications</a></td> </tr> <tr> <td><a href="http://expath.github.io/expath-cg/specs/http-client-2/" rel="nofollow">HTTP Client 2.0</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Exposing IEEE LOM metadata as Linked Data Community Group" data-created="2015-03-10T13:34Z" class="sortable-entry cg"> <article id="lom2ld"> <h2 class="group-title"><a href="https://www.w3.org/community/lom2ld/" id="lom2ld">Exposing IEEE LOM metadata as Linked Data Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://www.erajabi.com/Uploads/W3CDraft.html" rel="nofollow">Exposing IEEE LOM as Linked Data (Draft Community Group)</a></td> </tr> <tr> <td><a href="http://data.opendiscoveryspace.eu/ODS_LOM2LD/ODS_SecondDraft.html" rel="nofollow">Second draft of exposing IEEE LOM as Linked Data</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Federated Learning Community Group" data-created="2021-11-22T11:56Z" class="sortable-entry cg"> <article id="federated-learning"> <h2 class="group-title"><a href="https://www.w3.org/community/federated-learning/" id="federated-learning">Federated Learning Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The purpose of this community group is to establish and explore the necessary standards related with the Web for federated learning via the analysis of current implementations related with federated learning such as TensorFlow Federated. The main idea of federated learning is to build machine learning models based on data sets that are distributed across multiple clients (e.g. mobile devices or whole organizations) while preventing data leakage. Therefore, federated learning can give benefits like mitigation of privacy risks and costs.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://w3c.github.io/federated-learning-cg/reports/index-0.1.html">Federated Learning API</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="HTML Editing APIs Community Group" data-created="2011-08-16T16:56Z" class="sortable-entry cg"> <article id="editing"> <h2 class="group-title"><a href="https://www.w3.org/community/editing/" id="editing">HTML Editing APIs Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://dvcs.w3.org/hg/editing/raw-file/tip/editing.html" rel="nofollow">HTML Editing APIs</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Hydra Community Group" data-created="2013-06-17T14:29Z" class="sortable-entry cg"> <article id="hydra"> <h2 class="group-title"><a href="https://www.w3.org/community/hydra/" id="hydra">Hydra Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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/</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://www.hydra-cg.com/spec/latest/core/" rel="nofollow">Hydra Core Vocabulary</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Immersive Captions Community Group" data-created="2019-09-17T09:55Z" class="sortable-entry cg"> <article id="immersive-captions"> <h2 class="group-title"><a href="https://www.w3.org/community/immersive-captions/" id="immersive-captions">Immersive Captions Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The goal of this community group is to determine and publish best practices for access, activation, and display settings for captions with different types of Immersive Media - AR, VR & Games. We plan to research current examples, identify best practices, and do research on those ideas over different surfaces: Smartphone AR, AR glasses, VR goggles, etc. Where appropriate, we will share our results and discuss opportunities with the TTML WG (recommendations for media online captioning) and the W3C Immersive Web WG (APIs to interact with XR devices and sensors in browsers).</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2024-04-11T17:51Z"> 2024-04-11</time></td> <td><a href="https://www.w3.org/community/reports/immersive-captions/360-captions/">Recommendations for accessible captions in 360 degree video</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/immersive-captions/spec/239/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2024-04-23T18:45Z"> 2024-04-23</time></td> <td><a href="https://www.w3.org/community/reports/immersive-captions/CG-FINAL-360-captions-20240412/">Final Recommendations</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/immersive-captions/spec/241/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Invisible Markup Community Group" data-created="2021-03-16T16:37Z" class="sortable-entry cg"> <article id="ixml"> <h2 class="group-title"><a href="https://www.w3.org/community/ixml/" id="ixml">Invisible Markup Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">We choose which representations of our data to use, JSON, CSV, XML, or whatever, depending on habit, convenience, or the context we want to use that data in. On the other hand, having an interoperable generic toolchain such as that provided by XML to process data is of immense value. How do we resolve the conflicting requirements of convenience, habit, and context, and still enable a generic toolchain? Invisible XML (ixml) is a method for treating non-XML documents as if they were XML, enabling authors to write documents and data in a format they prefer while providing XML for processes that are more effective with XML content. This is an ongoing project to provide software that lets you treat any parsable format as if it were XML, without the need for markup.</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2024-03-05T14:56Z"> 2024-03-05</time></td> <td><a href="https://www.w3.org/community/reports/ixml/CG-FINAL-ixml-20231212/">Invisible XML Specification</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/ixml/spec/238/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="JSON for Linked Data Community Group" data-created="2011-09-01T12:02Z" class="sortable-entry cg"> <article id="json-ld"> <h2 class="group-title"><a href="https://www.w3.org/community/json-ld/" id="json-ld">JSON for Linked Data Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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.</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2012-06-27T14:41Z"> 2012-06-27</time></td> <td><a href="http://json-ld.org/spec/FCGS/json-ld-syntax/20120626/">JSON-LD Syntax 1.0</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/json-ld/spec/22/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2012-06-27T14:42Z"> 2012-06-27</time></td> <td><a href="http://json-ld.org/spec/FCGS/json-ld-api/20120626/">JSON-LD API 1.0</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/json-ld/spec/23/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2013-03-28T15:03Z"> 2013-03-28</time></td> <td><a href="http://json-ld.org/spec/FCGS/json-ld/20130328/">JSON-LD 1.0</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/json-ld/spec/49/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2013-03-28T15:06Z"> 2013-03-28</time></td> <td><a href="http://json-ld.org/spec/FCGS/json-ld-api/20130328/">JSON-LD 1.0 Processing Algorithms and API</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/json-ld/spec/50/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2018-06-08T23:00Z"> 2018-06-08</time></td> <td><a href="https://www.w3.org/2018/jsonld-cg-reports/json-ld/">JSON-LD 1.1 A JSON-based Serialization for Linked Data</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/json-ld/spec/145/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2018-06-08T23:01Z"> 2018-06-08</time></td> <td><a href="https://www.w3.org/2018/jsonld-cg-reports/json-ld-api/">JSON-LD 1.1 Processing Algorithms and API</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/json-ld/spec/146/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2018-06-08T23:02Z"> 2018-06-08</time></td> <td><a href="https://www.w3.org/2018/jsonld-cg-reports/json-ld-framing/">JSON-LD 1.1 Framing</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/json-ld/spec/147/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2023-12-12T20:16Z"> 2023-12-12</time></td> <td><a href="https://www.w3.org/community/reports/json-ld/CG-FINAL-yaml-ld-20231206/">YAML-LD</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/json-ld/spec/236/commitments">Licensing commitments</a></td> </tr> </tbody> </table> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://json-ld.org/spec/latest/json-ld-framing/" rel="nofollow">JSON-LD Framing API 1.0</a></td> </tr> <tr> <td><a href="http://json-ld.org/spec/latest/rdf-graph-normalization/" rel="nofollow">RDF Universal Graph Normalization 2011</a></td> </tr> <tr> <td><a href="https://json-ld.github.io/json-ld-star/publications/2021-02-18.html" rel="nofollow">JSON-LD-star</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Linked Data Models for Emotion and Sentiment Analysis Community Group" data-created="2014-01-07T14:38Z" class="sortable-entry cg"> <article id="sentiment"> <h2 class="group-title"><a href="https://www.w3.org/community/sentiment/" id="sentiment">Linked Data Models for Emotion and Sentiment Analysis Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc"><p>The Sentiment Analysis Community Group is a forum to promote sentiment analysis research. Topics addressed are:</p> <ul> <li>Definition of a Linked Data based vocabulary for emotion and sentiment analysis.</li> <li>Requirements beyond text-based analysis, i.e. emotion/sentiment analysis from images, video, social network analysis, etc.</li> <li>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.).</li> <li>Marl and Onyx are vocabularies for emotion and sentiment analysis that can be taken as a starting point for discussion in the CG.</li> </ul></div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://www.gsi.upm.es/otros/ldmesa/" rel="nofollow">Guidelines for developing Linked Data Emotion and Sentiment Analysis services</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Machine Learning Schema Community Group" data-created="2015-09-28T13:04Z" class="sortable-entry cg"> <article id="ml-schema"> <h2 class="group-title"><a href="https://www.w3.org/community/ml-schema/" id="ml-schema">Machine Learning Schema Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://htmlpreview.github.com/?https://github.com/ML-Schema/documentation/blob/gh-pages/ML%20Schema.html" rel="nofollow">ML Schema Core Specification</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Maps For HTML Community Group" data-created="2014-03-27T12:07Z" class="sortable-entry cg"> <article id="maps4html"> <h2 class="group-title"><a href="https://www.w3.org/community/maps4html/" id="maps4html">Maps For HTML Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc"><p>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.</p> <p>This group will publish specifications.</p></div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2021-02-12T18:51Z"> 2021-02-12</time></td> <td><a href="https://www.w3.org/2020/maps/report">Report on the Joint W3C-OGC Workshop on Maps for the Web</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/maps4html/spec/192/commitments">Licensing commitments</a></td> </tr> </tbody> </table> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://maps4html.org/MapML-Specification/spec/" rel="nofollow">Map Markup Language</a></td> </tr> <tr> <td><a href="https://maps4html.github.io/HTML-Map-Element-UseCases-Requirements/" rel="nofollow">Use Cases and Requirements for Standardizing Web Maps</a></td> </tr> <tr> <td><a href="https://maps4html.github.io/HTML-Map-Element/spec/" rel="nofollow">The HTML map element proposal</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="MFX Media Community Group" data-created="2020-02-04T06:59Z" class="sortable-entry cg"> <article id="mfxmedia"> <h2 class="group-title"><a href="https://www.w3.org/community/mfxmedia/" id="mfxmedia">MFX Media Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The exploration and development of media containers that protect and serve the growing needs of the content creator. A media container with global tracking and accountability will ensure the upmost transparency and data management. The world needs a new media file that can meet the modern technological needs.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://mfx.world/w3c/w3c-1.html" rel="nofollow">MFX Media Streaming Process</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="MicroXML Community Group" data-created="2012-07-16T14:56Z" class="sortable-entry cg"> <article id="microxml"> <h2 class="group-title"><a href="https://www.w3.org/community/microxml/" id="microxml">MicroXML Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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. </div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://dvcs.w3.org/hg/microxml/raw-file/tip/spec/microxml.html" rel="nofollow">MicroXML</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Multi-device Timing Community Group" data-created="2015-02-03T12:58Z" class="sortable-entry cg"> <article id="webtiming"> <h2 class="group-title"><a href="https://www.w3.org/community/webtiming/" id="webtiming">Multi-device Timing Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc"><p>The Multi-Device Timing Community Group is now closed. The <a href="https://www.w3.org/community/reports/webtiming/CG-FINAL-timingobject-20241203/">Timing Object</a> specification was published as a final Community Group Report in the hope that it may prove a useful basis for renewed discussions on a timing model for the Web in the future. Interested parties are encouraged to reach out to the <a href="https://www.w3.org/groups/ig/me/">Media and Entertainment Interest Group</a> for coordination, through its <a href="mailto:public-web-and-tv@w3.org">public-web-and-tv@w3.org</a> mailing-list (<a href="https://lists.w3.org/Archives/Public/public-web-and-tv/">archives</a>).</p> <p>The <a href="https://www.w3.org/community/sync-on-the-web/">Sync on the Web Community Group</a> was also created in January 2025 to identify and define the requirements, solutions, and mechanisms for reproducing sender-side state, including all data, with precise timing and minimal jitter on the client side.</p></div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2024-12-04T09:43Z"> 2024-12-04</time></td> <td><a href="https://www.w3.org/community/reports/webtiming/CG-FINAL-timingobject-20241203/">Timing Object Final Community Group Report</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/webtiming/spec/276/commitments">Licensing commitments</a></td> </tr> </tbody> </table> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://webtiming.github.io/timingobject/" rel="nofollow">Timing Object Draft Specification</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Multidimensional Quality Metrics (MQM) Community Group" data-created="2017-06-22T10:59Z" class="sortable-entry cg"> <article id="mqmcg"> <h2 class="group-title"><a href="https://www.w3.org/community/mqmcg/" id="mqmcg">Multidimensional Quality Metrics (MQM) Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The Multidimensional Quality Metrics (MQM) Community Group fosters the development of MQM for translation and localization quality assessment and its interoperability with W3C’s Internationalization Tag Set (ITS) 2.0 recommendation. Membership is open to parties interested in contributing to or implementing MQM.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://www.w3.org/community/mqmcg/2018/10/04/draft-2018-10-04/">Multidimensional Quality Metrics (MQM) Issue Types: DRAFT 2018-10-04</a></td> </tr> <tr> <td><a href="https://www.w3.org/community/mqmcg/mqm-top-level-2019-04-11/">MQM Top Level (2019-04-11)</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Music Notation Community Group" data-created="2015-07-27T16:21Z" class="sortable-entry cg"> <article id="music-notation"> <h2 class="group-title"><a href="https://www.w3.org/community/music-notation/" id="music-notation">Music Notation Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc"><p>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. </p> <p> The Community Group documents, maintains and updates the MusicXML and SMuFL (Standard Music Font Layout) specifications. The goals are to evolve the specifications to handle a broader set of use cases and technologies, including use of music notation on the web, while maximizing the existing investment in implementations of the existing MusicXML and SMuFL specifications. </p> <p> The group is developing a new specification to embody this broader set of use cases and technologies, under the working title of MNX. The group is proposing the development of an additional new specification to provide a standard, machine-readable source of musical instrument data. </p></div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2017-12-13T17:54Z"> 2017-12-13</time></td> <td><a href="https://www.w3.org/2017/12/musicxml31/">MusicXML Version 3.1</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/music-notation/spec/137/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2019-01-30T14:54Z"> 2019-01-30</time></td> <td><a href="https://www.w3.org/2019/03/smufl13/">SMuFL 1.3</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/music-notation/spec/156/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2021-02-14T20:46Z"> 2021-02-14</time></td> <td><a href="https://www.w3.org/2021/03/smufl14/">SMuFL 1.4</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/music-notation/spec/193/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2021-05-15T01:35Z"> 2021-05-15</time></td> <td><a href="https://www.w3.org/2021/06/musicxml40/">MusicXML 4.0</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/music-notation/spec/196/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Notation 3 (N3) Community Group" data-created="2018-11-27T17:42Z" class="sortable-entry cg"> <article id="n3-dev"> <h2 class="group-title"><a href="https://www.w3.org/community/n3-dev/" id="n3-dev">Notation 3 (N3) Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">Further development, implementation, and standardization of Notation 3 - an assertion and logic language - including the N3 Rules language.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://w3c.github.io/N3/reports/20230703/">Notation3 Language</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="ODRL Community Group" data-created="2011-06-29T15:02Z" class="sortable-entry cg"> <article id="odrl"> <h2 class="group-title"><a href="https://www.w3.org/community/odrl/" id="odrl">ODRL Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc"><p>The ODRL Community Group supports the promotion and future development of the W3C ODRL recommendations:</p> <ul class="show_items"> <li><a href="https://www.w3.org/TR/odrl-model/" rel="nofollow">ODRL Information Model</a></li> <li><a href="https://www.w3.org/TR/odrl-vocab/" rel="nofollow">ODRL Vocabulary & Expression</a></li> </ul> <p>Specifically, the ODRL CG will:</p> <ul class="show_items"> <li>Promote ODRL V2.2 to existing and new sectors/industries</li> <li>Nurture an ODRL implementors community</li> <li>Publish reports related to ODRL usage</li> <li>Support development of ODRL Profiles (and host for smaller communities)</li> <li>Register ODRL Profiles</li> <li>Collaborate with W3C on ODRL errata maintenance</li> <li>Plan for future major enhancements to ODRL (V3.0)</li> </ul></div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2012-04-12T23:23Z"> 2012-04-12</time></td> <td><a href="https://www.w3.org/community/odrl/model/2.0/">ODRL Version 2.0 Core Model</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/odrl/spec/2/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2012-04-12T23:24Z"> 2012-04-12</time></td> <td><a href="https://www.w3.org/community/odrl/vocab/2.0/">ODRL Version 2.0 Common Vocabulary</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/odrl/spec/3/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2012-04-12T23:24Z"> 2012-04-12</time></td> <td><a href="https://www.w3.org/community/odrl/xml/2.0/">ODRL Version 2.0 XML Encoding</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/odrl/spec/4/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2013-01-22T02:48Z"> 2013-01-22</time></td> <td><a href="https://www.w3.org/community/odrl/model/2.1/">ODRL Version 2.1 Core Model</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/odrl/spec/41/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2013-01-22T04:41Z"> 2013-01-22</time></td> <td><a href="https://www.w3.org/community/odrl/xml/2.1/">ODRL Version 2.1 XML Encoding</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/odrl/spec/42/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2013-02-18T00:48Z"> 2013-02-18</time></td> <td><a href="https://www.w3.org/community/odrl/vocab/2.1/">ODRL Version 2.1 Common Vocabulary</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/odrl/spec/45/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2013-09-26T03:03Z"> 2013-09-26</time></td> <td><a href="https://www.w3.org/community/odrl/json/2.1/">ODRL Version 2.1 JSON Encoding</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/odrl/spec/62/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2013-10-11T02:05Z"> 2013-10-11</time></td> <td><a href="https://www.w3.org/ns/odrl/2/ODRL21">ODRL Version 2.1 Ontology</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/odrl/spec/64/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2018-02-15T09:49Z"> 2018-02-15</time></td> <td><a href="https://www.w3.org/TR/2018/REC-odrl-model-20180215/">W3C ODRL Information Model Version 2.2</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/odrl/spec/138/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2018-02-15T09:50Z"> 2018-02-15</time></td> <td><a href="https://www.w3.org/TR/2018/REC-odrl-vocab-20180215/">W3C ODRL Vocabulary & Expression Version 2.2</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/odrl/spec/139/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2019-10-04T11:17Z"> 2019-10-04</time></td> <td><a href="https://www.w3.org/community/reports/odrl/CG-FINAL-profile-bp-20240808.html">ODRL Profile Best Practices</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/odrl/spec/176/commitments">Licensing commitments</a></td> </tr> </tbody> </table> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://w3c.github.io/odrl/community-vocab/">ODRL Community Vocabulary</a></td> </tr> <tr> <td><a href="https://w3c.github.io/odrl/profile-dataspaces/">ODRL Profile: Data Spaces</a></td> </tr> <tr> <td><a href="https://w3c.github.io/odrl/bp/">ODRL Implementation Best Practices</a></td> </tr> <tr> <td><a href="https://w3c.github.io/odrl/profile-bigdata/">ODRL Profile Big Data</a></td> </tr> <tr> <td><a href="https://w3c.github.io/odrl/profile-temporal/">ODRL Temporal Profile</a></td> </tr> <tr> <td><a href="https://w3c.github.io/odrl/formal-semantics/">ODRL Formal Semantics</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Ontology-Lexica Community Group" data-created="2011-07-03T20:52Z" class="sortable-entry cg"> <article id="ontolex"> <h2 class="group-title"><a href="https://www.w3.org/community/ontolex/" id="ontolex">Ontology-Lexica Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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. </div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2016-05-04T04:55Z"> 2016-05-04</time></td> <td><a href="https://www.w3.org/2016/05/ontolex/">Lexicon Model for Ontologies</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/ontolex/spec/118/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2019-09-19T15:00Z"> 2019-09-19</time></td> <td><a href="https://www.w3.org/2019/09/lexicog/">The Ontolex Lemon Lexicography Module</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/ontolex/spec/175/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Open Annotation Community Group" data-created="2011-12-08T23:32Z" class="sortable-entry cg"> <article id="openannotation"> <h2 class="group-title"><a href="https://www.w3.org/community/openannotation/" id="openannotation">Open Annotation Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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/</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://www.openannotation.org/spec/core/" rel="nofollow">Core Open Annotation Specification (Community Draft 1)</a></td> </tr> <tr> <td><a href="http://www.openannotation.org/spec/extension/" rel="nofollow">Open Annotation Extension Specification (Community Draft 1)</a></td> </tr> <tr> <td><a href="http://www.openannotation.org/spec/core/20130208/" rel="nofollow">Open Annotation Specification (Community Draft 2)</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Open Data Nepal Community Group" data-created="2018-02-19T17:12Z" class="sortable-entry cg"> <article id="opendatanepal"> <h2 class="group-title"><a href="https://www.w3.org/community/opendatanepal/" id="opendatanepal">Open Data Nepal Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">A forum for the open network of open data enthusiasts, government officers, students, researchers, and a non-profit leader who are working to improve the condition of open data in Nepal. This space will help individual volunteers, groups, students to collaborate and discuss how one can help to boost the open data momentum in Nepal. This group will not have any criteria and specification, anyone can join and may reuse the group works. This group will not publish Specifications.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://oknp.org/beta-version-of-open-data-nepal-a-portal-to-make-nepals-data-accessible-online-is-now-live/" rel="nofollow">Beta Version of Open Data Nepal – A Portal to Make Nepal’s Data Accessible Online</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Open Educational Resources Schema Community Group" data-created="2016-06-16T22:43Z" class="sortable-entry cg"> <article id="oerschema"> <h2 class="group-title"><a href="https://www.w3.org/community/oerschema/" id="oerschema">Open Educational Resources Schema Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">Our mission is to develop a universal RDF vocabulary to enhance open educational resources throughout the internet.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://oerschema.org" rel="nofollow">Open Educational Resource Schema</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Open knowledge-driven service-oriented system architectures and APIs (KiSS) Community Group" data-created="2015-11-17T14:52Z" class="sortable-entry cg"> <article id="kiss"> <h2 class="group-title"><a href="https://www.w3.org/community/kiss/" id="kiss">Open knowledge-driven service-oriented system architectures and APIs (KiSS) Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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: <ul> <li>General chair: Ideologist. Overall synchronization between different pillars of the KiSS. PR with other groups and external stakeholders. Member attraction, community group development. </li> <li>Chair for integration: Integration technologies, web service composition.</li> <li>Chair for knowledge: Knowledge representation and reasoning standards and methodologies.</li> <li>Chair for devices: Embedded devices, their adoption for KiSS.</li> <li>Chair for services: Web services, standards, methodologies for service definition.</li> <li>Chair for application domains: KiSS in different application domains. Cross-domain learning and development. Benchmarking.</li> </ul></div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://w3c.github.io/kiss/specs/recipes_draft_20160708.html">Recipes for building service-oriented knowledge-driven systems</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="OpenActive Community Group" data-created="2016-04-11T12:35Z" class="sortable-entry cg"> <article id="openactive"> <h2 class="group-title"><a href="https://www.w3.org/community/openactive/" id="openactive">OpenActive Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc"><p>This community group is part of <a href="https://www.openactive.io/" rel="nofollow">the OpenActive initiative</a>. 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.</p> <p>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.</p> <p>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.</p> <p>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.</p></div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2017-03-30T12:13Z"> 2017-03-30</time></td> <td><a href="https://www.w3.org/2017/08/modelling-opportunity-data/">Modelling Opportunity Data</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/openactive/spec/124/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2017-07-14T15:46Z"> 2017-07-14</time></td> <td><a href="https://www.w3.org/2017/08/realtime-paged-data-exchange/">Realtime Paged Data Exchange</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/openactive/spec/135/commitments">Licensing commitments</a></td> </tr> </tbody> </table> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://www.openactive.io/ns/" rel="nofollow">OpenActive Vocabulary</a></td> </tr> <tr> <td><a href="https://www.openactive.io/opportunity-data-primer/" rel="nofollow">Publishing opportunity data: a primer</a></td> </tr> <tr> <td><a href="https://www.openactive.io/activity-list/" rel="nofollow">OpenActive Activity List</a></td> </tr> <tr> <td><a href="https://www.openactive.io/open-booking-api/EditorsDraft/" rel="nofollow">Open Booking Specification: Editors Draft</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="OpenTrack Community Group" data-created="2017-01-31T12:10Z" class="sortable-entry cg"> <article id="opentrack"> <h2 class="group-title"><a href="https://www.w3.org/community/opentrack/" id="opentrack">OpenTrack Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">This group aims to develop an open standard for interchange of data in Athletics (including Track and Field), running and related disciplines. Such a standard should allow the development of better software to manage the sport, resulting in major savings of time for volunteers; more efficient management of events and federations; and more enjoyment for participants and fans.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://w3c.github.io/opentrack-cg/spec/competition/">Sports Competition Data Model and Vocabulary</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="ORCA - Object-RTC API Community Group" data-created="2013-07-24T20:55Z" class="sortable-entry cg"> <article id="orca"> <h2 class="group-title"><a href="https://www.w3.org/community/orca/" id="orca">ORCA - Object-RTC API Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">See the <a href="https://www.w3.org/community/ortc/">ORTC CG</a> instead. A group of like-minded individuals that are interested in the Object-RTC API model for WebRTC. It's likely these individuals or organizations are also taking part in the IETF RTCWEB and W3C WebRTC working group discussions.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://htmlpreview.github.io/?https://raw.github.com/openpeer/ortc/20131103/ortc.html" rel="nofollow">Object RTC (ORTC) API for WebRTC</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="ORTC (Object Real-time Communications) Community Group" data-created="2014-03-05T23:36Z" class="sortable-entry cg"> <article id="ortc"> <h2 class="group-title"><a href="https://www.w3.org/community/ortc/" id="ortc">ORTC (Object Real-time Communications) Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The mission of the Object Real-Time Communications Community Group, is to define Object-centric APIs (client-side at first) to enable Real-Time Communications in Web browsers, Mobile endpoints and Servers.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://ortc.org/wp-content/uploads/2014/04/ortc1.html" rel="nofollow">Object RTC (ORTC) API for WebRTC</a></td> </tr> <tr> <td><a href="http://ortc.org/wp-content/uploads/2014/05/ortc.html" rel="nofollow">Object RTC (ORTC) API for WebRTC [2014/05/14]</a></td> </tr> <tr> <td><a href="http://ortc.org/wp-content/uploads/2014/08/ortc.html" rel="nofollow">Object RTC (ORTC) API for WebRTC [2014/08/19]</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Quick-fix support for XML Community Group" data-created="2014-02-20T11:42Z" class="sortable-entry cg"> <article id="quickfix"> <h2 class="group-title"><a href="https://www.w3.org/community/quickfix/" id="quickfix">Quick-fix support for XML Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://schematron-quickfix.github.io/sqf" rel="nofollow">Schematron Quick Fixes Specification</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="RDF Stream Processing Community Group" data-created="2013-08-01T14:12Z" class="sortable-entry cg"> <article id="rsp"> <h2 class="group-title"><a href="https://www.w3.org/community/rsp/" id="rsp">RDF Stream Processing Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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. </div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://streamreasoning.github.io/RSP-QL/RSP_Requirements_Design_Document/" rel="nofollow">RDF Stream Processing: Requirements and Design Principles</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="RDF Surfaces Community Group" data-created="2022-12-14T16:44Z" class="sortable-entry cg"> <article id="rdfsurfaces"> <h2 class="group-title"><a href="https://www.w3.org/community/rdfsurfaces/" id="rdfsurfaces">RDF Surfaces Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The RDF Surfaces sets out to create a sublanguage of Notation3 in order to implement classical first-order logic with negation in RDF as envisioned by Pat Hayes in his 2009 ISWC Invited Talk: BLOGIC</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://w3c-cg.github.io/rdfsurfaces/" rel="nofollow">RDF Surfaces Primer</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="RDF-DEV Community Group" data-created="2018-10-16T11:24Z" class="sortable-entry cg"> <article id="rdf-dev"> <h2 class="group-title"><a href="https://www.w3.org/community/rdf-dev/" id="rdf-dev">RDF-DEV Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">RDF-DEV, for developments relating to W3C RDF, including collaboration around applications, schemas, and past/present/future related standards. Successor to SWIG/RDFIG. </div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2022-06-15T16:50Z"> 2022-06-15</time></td> <td><a href="https://www.w3.org/2021/12/rdf-star.html">RDF-star and SPARQL-star</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/rdf-dev/spec/210/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Responsive Issues Community Group" data-created="2012-02-20T03:27Z" class="sortable-entry cg"> <article id="respimg"> <h2 class="group-title"><a href="https://www.w3.org/community/respimg/" id="respimg">Responsive Issues Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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." </div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2012-07-02T22:05Z"> 2012-07-02</time></td> <td><a href="http://dvcs.w3.org/hg/html-proposals/raw-file/9443de7ff65f/responsive-images/responsive-images.html">Picture Element Proposal</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/respimg/spec/26/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Second Screen Community Group" data-created="2013-11-07T03:19Z" class="sortable-entry cg"> <article id="webscreens"> <h2 class="group-title"><a href="https://www.w3.org/community/webscreens/" id="webscreens">Second Screen Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The mission of the <a rel="nofollow" href="https://www.w3.org/community/webscreens/">Second Screen Community Group (CG)</a> is to explore, incubate, and define interfaces that enable new form factors and usages for multi-display and multi-window computing user experiences on the Web. The scope of work for this Community Group extends beyond the current scope of the <a rel="nofollow" href="https://www.w3.org/2014/secondscreen/">Second Screen Working Group (WG)</a>. Given wider support and adequate stability, we plan to migrate the proposals generated in this Community Group to an appropriate <a rel="nofollow" href="https://www.w3.org/Consortium/activities#Working">W3C Working Group</a> for further contributions and formal standardization.</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2014-12-02T14:43Z"> 2014-12-02</time></td> <td><a href="https://www.w3.org/2014/secondscreen/presentation-api/20141118/">Presentation API</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/webscreens/spec/96/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Semantic Industries Community Group" data-created="2019-06-11T06:18Z" class="sortable-entry cg"> <article id="semind"> <h2 class="group-title"><a href="https://www.w3.org/community/semind/" id="semind">Semantic Industries Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">This Community Group brings together people from research and industry who are interested in semantic modelling. Researchers are interested in understanding the actual needs of industrial partners, gathering use cases and example data, and clarifying the challenges that further research can help address, as well as refining the methodologies for developing semantic based solutions. Industrial partners are interested in having clear benefits for adopting semantic technologies in relation to the digital transformation of industry. How can these benefits be realised by average developers using higher level frameworks and better tooling. The W3C Community Group will make extensive use of the GitHub issue tracker to raise and discuss ideas, and to prepare W3C Community Group reports with our findings.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://www.w3.org/community/semind/2022/07/08/kick-off-meeting-report-july-2022/">Semantic Industries: Kickoff Meeting July 2022</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Semantic Statistics Community Group" data-created="2013-12-18T01:27Z" class="sortable-entry cg"> <article id="semstats"> <h2 class="group-title"><a href="https://www.w3.org/community/semstats/" id="semstats">Semantic Statistics Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://linked-statistics.github.io/SDMX-Metadata/sdmx-metadata.html" rel="nofollow">SDMX Metadata</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Semantic Web in Health Care and Life Sciences Community Group" data-created="2016-07-27T03:47Z" class="sortable-entry cg"> <article id="hclscg"> <h2 class="group-title"><a href="https://www.w3.org/community/hclscg/" id="hclscg">Semantic Web in Health Care and Life Sciences Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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.</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2019-05-15T20:39Z"> 2019-05-15</time></td> <td><a href="https://www.w3.org/2019/05/pddi/">A Minimum Representation of Potential Drug-Drug Interaction Knowledge and Evidence - Technical and User-centered Foundation</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/hclscg/spec/169/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Semantic Web Interfaces Community Group" data-created="2012-10-12T01:55Z" class="sortable-entry cg"> <article id="swisig"> <h2 class="group-title"><a href="https://www.w3.org/community/swisig/" id="swisig">Semantic Web Interfaces Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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: https://docs.google.com/document/d/1z-WtxO67ndfgLVmnZAld-7XA5P-CAg7XgMDZ4mbXgqs/edit</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://www.w3.org/community/swisig/preliminary-report-april-2014/" rel="nofollow">Preliminary Report</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Shape Expressions Community Group" data-created="2016-12-12T13:50Z" class="sortable-entry cg"> <article id="shex"> <h2 class="group-title"><a href="https://www.w3.org/community/shex/" id="shex">Shape Expressions Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">This group serves to promote and expand ShEx – Shape Expressions. ShEx is a grammar for RDF graphs which can be used for description, validation, parsing and transformation. The Shape Expressions (ShEx) language describes RDF nodes and graph structures. A node constraint describes an RDF node (IRI, blank node or literal) and a shape describes the triples touching nodes in RDF graphs. These descriptions identify predicates and their associated cardinalities and datatypes. ShEx shapes can be used to communicate data structures associated with some process or interface, generate or validate data, or drive user interfaces. Spec at https://shexspec.github.io/spec/</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://shex.io/shex-primer/" rel="nofollow">Shape Expressions (ShEx) Primer</a></td> </tr> <tr> <td><a href="http://shex.io/shex-semantics/" rel="nofollow">Shape Expressions Language 2.0</a></td> </tr> <tr> <td><a href="http://shex.io/shape-map/" rel="nofollow">ShapeMap Structure and Language</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Silver Community Group" data-created="2017-03-02T23:55Z" class="sortable-entry cg"> <article id="silver"> <h2 class="group-title"><a href="https://www.w3.org/community/silver/" id="silver">Silver Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">Support the research and prototyping of the next major version of Web Content Accessibility Guidelines (WCAG). This group may publish Specifications.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://www.w3.org/community/silver/stakeholder-job-stories/">Stakeholder Job Stories</a></td> </tr> <tr> <td><a href="https://www.w3.org/community/silver/draft-final-report-of-silver/">Silver Design Sprint Report</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Social Web Incubator Community Group" data-created="2016-11-18T19:59Z" class="sortable-entry cg"> <article id="socialcg"> <h2 class="group-title"><a href="https://www.w3.org/community/socialcg/" id="socialcg">Social Web Incubator Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The Social Web Incubator Community Group (also known as SocialCG, or SWICG) is the successor of the Social Web Working Group, which ran from 2014 to 2017. The SocialCG provides space to collaborate and coordinate for implementors who are building on any of the <a href="https://www.w3.org/TR/social-web-protocols/">specifications published by the Social Web WG</a>, and related technologies. It is also a place to incubate new proposals which build on or complement the Social Web WG recommendations.<br><br> Discussions and meeting announcements happen on <a href="https://socialhub.activitypub.rocks/">the SocialHub forum</a> or on project-specific version control repositories.<br><br> Meetings are not always weekly, but can be requested or convened by any member of the group. If you have a specific item to discuss, please contact a chair if you need help with <a href="https://www.w3.org/wiki/SocialCG#Meetings">meeting logistics</a>, and make a post on the SocialHub forum, ideally with two or more weeks notice.</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2024-09-19T18:04Z"> 2024-09-19</time></td> <td><a href="https://www.w3.org/community/reports/socialcg/CG-FINAL-apwf-20240608/">ActivityPub and WebFinger</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/socialcg/spec/272/commitments">Licensing commitments</a></td> </tr> </tbody> </table> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://swicg.github.io/extensions-policy/" rel="nofollow">Process for Including Extensions in Activity Streams 2.0</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Speech API Community Group" data-created="2012-04-03T17:34Z" class="sortable-entry cg"> <article id="speech-api"> <h2 class="group-title"><a href="https://www.w3.org/community/speech-api/" id="speech-api">Speech API Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The goal and scope of this Community Group is to produce a JavaScript Speech API that supports the majority of use-cases in <a href="https://www.w3.org/2005/Incubator/htmlspeech/XGR-htmlspeech/">the Speech Incubator Group's Final Report</a>, but is a simplified subset API, such as <a href="http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/att-1696/speechapi.html">this proposal</a>. 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.</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2012-06-13T22:37Z"> 2012-06-13</time></td> <td><a href="https://wicg.github.io/speech-api/">Web Speech API</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/speech-api/spec/16/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Sustainable Web Design Community Group" data-created="2013-04-04T01:25Z" class="sortable-entry cg"> <article id="sustyweb"> <h2 class="group-title"><a href="https://www.w3.org/community/sustyweb/" id="sustyweb">Sustainable Web Design Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The Sustainable Web Design Community Group is now closed. Its activities are now under the direction of the <a href="https://www.w3.org/groups/ig/sustainableweb/">W3C Sustainable Web Interest Group</a>. This includes the curation of the <a href="https://w3c.github.io/sustainableweb-wsg">Web Sustainability Guidelines</a>. Thank you for supporting us as we reached this stage in our journey and we hope you will continue to support our work as it develops at our new home (where you are welcome to get involved).</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://w3c.github.io/sustyweb/">Web Sustainability Guidelines (WSG) 1.0</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="SVG glyphs for OpenType Community Group" data-created="2011-10-27T22:24Z" class="sortable-entry cg"> <article id="svgopentype"> <h2 class="group-title"><a href="https://www.w3.org/community/svgopentype/" id="svgopentype">SVG glyphs for OpenType Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">Extension of OpenType to allow multicolor, animated SVG glyphs while reusing the OpenType layout facilities.</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2013-10-09T23:20Z"> 2013-10-09</time></td> <td><a href="https://www.w3.org/2013/10/SVG_in_OpenType/">SVG Glyphs in OpenType Specification</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/svgopentype/spec/63/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="SVG Streaming Community Group" data-created="2013-11-15T09:07Z" class="sortable-entry cg"> <article id="svgstreaming"> <h2 class="group-title"><a href="https://www.w3.org/community/svgstreaming/" id="svgstreaming">SVG Streaming Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://dev.w3.org/SVG/modules/streaming/" rel="nofollow">SVG Streaming</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Text and Data Mining Reservation Protocol Community Group" data-created="2021-01-20T11:49Z" class="sortable-entry cg"> <article id="tdmrep"> <h2 class="group-title"><a href="https://www.w3.org/community/tdmrep/" id="tdmrep">Text and Data Mining Reservation Protocol Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The goal of this Group is to facilitate Text and Data Mining (TDM) Reservation Protocol in Europe and elsewhere, by specifying a simple and practical machine-readable solution, capable of expressing the reservation of TDM rights - following the rules set by the new European DSM Directive / Art.4 - and the availability of machine-readable licenses for TDM actors. </div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2024-08-09T11:57Z"> 2024-08-09</time></td> <td><a href="https://www.w3.org/community/reports/tdmrep/CG-FINAL-tdmrep-20240510/">TDM Reservation Protocol, version 3</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/tdmrep/spec/268/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2022-02-16T14:26Z"> 2022-02-16</time></td> <td><a href="https://www.w3.org/2022/tdmrep/">TDM Reservation Protocol, version 1</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/tdmrep/spec/206/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2024-04-16T13:56Z"> 2024-04-16</time></td> <td><a href="https://www.w3.org/community/reports/tdmrep/CG-FINAL-tdmrep-20240202/">TDM Reservation Protocol, version 2</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/tdmrep/spec/240/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="TNS Blockchain Community Group" data-created="2020-04-07T02:00Z" class="sortable-entry cg"> <article id="tnsblockchain"> <h2 class="group-title"><a href="https://www.w3.org/community/tnsblockchain/" id="tnsblockchain">TNS Blockchain Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">A web based blockchain project to explore the use of Digital Names within existing web applications and PaaS and IaaS platforms. The English or human language naming solution presented by Digital Names solves a big problem related to the scale-up of blockchain networks and cryptocurrency systems. Over a hundred million consumers in the globally currently use eWallets. There are over 100 million Crypto trading accounts registered on the worlds crypto exchanges. All currently use Public Crypto Keys for transaction settlement. New companies and individuals entering the emerging blockchain / crypto financial system for the first time frequently find it difficult to understand how to easily send and receive money from eWallets. To regular people or mainstream users the precise steps involved with sending and receiving digital money is currently limiting usage of the blockchain. It is confusing and intimidating, and creates insecurity of inputting keys wrong and losing the value of a transaction. Digital Names simplifies the remembering, typing and everyday usage of digital wallets for crypto and kind of crypto payments or receipts into or out of a Digital Wallet.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://tnsblockchain.com/w3c/firstdraft.html" rel="nofollow">TNS Blockchain</a></td> </tr> <tr> <td><a href="http://tnsblockchain.com/w3c/tns-blockchain-newest-features.html" rel="nofollow">Newest Features- TNS Blockchain</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Touch Events Community Group" data-created="2013-10-28T20:41Z" class="sortable-entry cg"> <article id="touchevents"> <h2 class="group-title"><a href="https://www.w3.org/community/touchevents/" id="touchevents">Touch Events Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc"><p>This group is closed. See the <a rel="nofollow" href="https://www.w3.org/community/reports/touchevents/CG-FINAL-touch-events-20240704/">Final Community Group Report for Touch Events Level 2</a>.</p> <p>The Touch Events community group was formed by members of the <a rel="nofollow" href="https://www.w3.org/groups/wg/webevents">Web Events Working Group</a> (responsible for the <a rel="nofollow" href="https://www.w3.org/TR/touch-events/">Touch Events</a> specification) and the <a rel="nofollow" href="https://www.w3.org/groups/wg/pointer-events">Pointer Events Working Group</a> (responsible for the <a rel="nofollow" href="https://www.w3.org/TR/pointerevents/">Pointer Events</a> specification). The group's focus was to determine differences in touch event behavior between browsers.</p></div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2024-07-08T17:15Z"> 2024-07-08</time></td> <td><a href="https://www.w3.org/community/reports/touchevents/CG-FINAL-touch-events-20240704/">Touch Events - Level 2 / Final Community Group Report / 04 July 2024</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/touchevents/spec/266/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="TREE hypermedia Community Group" data-created="2023-03-28T23:12Z" class="sortable-entry cg"> <article id="treecg"> <h2 class="group-title"><a href="https://www.w3.org/community/treecg/" id="treecg">TREE hypermedia Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The TREE hypermedia community group will discuss materializable hypermedia interfaces. Its goals are to: 1. Further evolve the TREE hypermedia specification (https://w3id.org/tree/specification) and its vocabulary (https://w3id.org/tree/) 2. Create a test suite for spec compliance of both servers and clients 3. Deliver a specification on view definitions for source selection</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://w3id.org/tree/specification" rel="nofollow">The TREE hypermedia specification</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Trustworthy AI Community Group" data-created="2022-01-11T13:39Z" class="sortable-entry cg"> <article id="tai"> <h2 class="group-title"><a href="https://www.w3.org/community/tai/" id="tai">Trustworthy AI Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The purpose of this community group is to establish and explore the necessary standards, requirements, metrics, and methodologies related to understanding, building, and ensuring trustworthy AI systems.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://dx.doi.org/10.13140/RG.2.2.16353.79200" rel="nofollow">Towards User-Centered Metrics for Trustworthy AI in Immersive Cyberspace</a></td> </tr> <tr> <td><a href="https://www.researchgate.net/publication/339251886_Trustworthy_AI_in_the_Age_of_Pervasive_Computing_and_Big_Data" rel="nofollow">Trustworthy AI in the Age of Pervasive Computing and Big Data</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="TV Control API Community Group" data-created="2014-04-24T12:15Z" class="sortable-entry cg"> <article id="tvapi"> <h2 class="group-title"><a href="https://www.w3.org/community/tvapi/" id="tvapi">TV Control API Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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. </div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2015-11-30T21:47Z"> 2015-11-30</time></td> <td><a href="https://www.w3.org/2015/tvapi/Overview.html">TV Control API Specification v1.0</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/tvapi/spec/110/commitments">Licensing commitments</a></td> </tr> </tbody> </table> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://w3c.github.io/tvapi/spec/" rel="nofollow">TV Control API Specification (Draft Candidate)</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Universal Images Community Group" data-created="2015-12-16T13:35Z" class="sortable-entry cg"> <article id="universalimages"> <h2 class="group-title"><a href="https://www.w3.org/community/universalimages/" id="universalimages">Universal Images Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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. </div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://universalimages.github.io/rmd/" rel="nofollow">Responsive Metadata XMP Standard</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Virtual Reality website and Metaverse Community Group" data-created="2015-11-16T13:45Z" class="sortable-entry cg"> <article id="vrwebmetaverse"> <h2 class="group-title"><a href="https://www.w3.org/community/vrwebmetaverse/" id="vrwebmetaverse">Virtual Reality website and Metaverse Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">This group is to start a discussion on how to level up our current world wide web to 3d and virtual reality.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://www.googledrive.com/host/0B-FytjBBSdXYUUtMNGVWT1RiTFE" rel="nofollow">Technologies to be investigated for VR and multiverse viability</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Voice Interaction Community Group" data-created="2016-06-07T11:10Z" class="sortable-entry cg"> <article id="voiceinteraction"> <h2 class="group-title"><a href="https://www.w3.org/community/voiceinteraction/" id="voiceinteraction">Voice Interaction Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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.</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://w3c.github.io/voiceinteraction/voice%20interaction%20drafts/emmaJSON/emmaJSON.htm">JSON Representation of Semantic Information</a></td> </tr> <tr> <td><a href="https://github.com/w3c/voiceinteraction/blob/master/voice%20interaction%20drafts/paArchitecture/paArchitecture-1-3.htm" rel="nofollow">Architecture and Potential for Standardization</a></td> </tr> <tr> <td><a href="https://w3c.github.io/voiceinteraction/voice%20interaction%20drafts/paInterfaces/paInterfaces.htm">Intelligent Personal Assistant Architecture</a></td> </tr> <tr> <td><a href="https://w3c.github.io/voiceinteraction/voice%20interaction%20drafts/paRequirements/paRequirements.htm">Architecture Requirements for Intelligent Personal Assistants</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Web and Broadcasting Business Group" data-created="2012-03-26T08:39Z" class="sortable-entry bg"> <article id="webandbroadcasting"> <h2 class="group-title"><a href="https://www.w3.org/community/webandbroadcasting/" id="webandbroadcasting">Web and Broadcasting Business Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The aim of the Web and Broadcasting Business Group was 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. </div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://webandbroadcasting.github.io/a-smarter-combination/" rel="nofollow">Towards a Smarter Combination of Broadcasting and the Web</a></td> </tr> <tr> <td><a href="http://webandbroadcasting.github.io/id-tech-on-the-web-a-primer/" rel="nofollow">Identity Technologies on the Web: A Primer</a></td> </tr> <tr> <td><a href="http://webandbroadcasting.github.io/tvs-n-other-screens/" rel="nofollow">Repository of Existing Business-Level Use Cases for TVs In Tandem With Other Screens that Enrich Programs and Commercials via the Web</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Web Components Community Group" data-created="2020-12-06T15:04Z" class="sortable-entry cg"> <article id="webcomponents"> <h2 class="group-title"><a href="https://www.w3.org/community/webcomponents/" id="webcomponents">Web Components Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc"><p>This group is for collaboration between people working on web components libraries, tools, documentation and standards. </p><p>We will work together on projects of shared interest in order to enhance interoperability, solve common problems, build shared community resources, and ultimately continue to grow a cooperative, productive, and happy web components ecosystem. </p><p>Areas we expect to work on include gap analysis, design principles, common protocols, discoverability and quality, documentation, tooling, and more. </p></div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://w3c.github.io/webcomponents-cg/">Web Components Community Group: 2021 Spec/API status</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Web Crypto API Community Group" data-created="2011-08-31T03:41Z" class="sortable-entry cg"> <article id="webcryptoapi"> <h2 class="group-title"><a href="https://www.w3.org/community/webcryptoapi/" id="webcryptoapi">Web Crypto API Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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/</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://html5.creation.net/webcrypto-api/" rel="nofollow">Web Crypto API — An Authentification of Data and People in SSL</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Web Hypertext Application Technology Community Group" data-created="2012-04-23T21:36Z" class="sortable-entry cg"> <article id="whatwg"> <h2 class="group-title"><a href="https://www.w3.org/community/whatwg/" id="whatwg">Web Hypertext Application Technology Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">See the <a rel="nofollow" href="https://whatwg.org/">WHATWG</a> and the <a rel="nofollow" href="https://www.w3.org/2019/04/WHATWG-W3C-MOU.html">Memorandum of Understanding Between W3C and WHATWG</a>. Community group around the HTML living specification and its related Web Application technology specifications.</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2014-07-30T19:16Z"> 2014-07-30</time></td> <td><a href="https://www.whatwg.org/specs/url/2014-07-30/">URL Standard</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/whatwg/spec/82/commitments">Licensing commitments</a></td> </tr> </tbody> </table> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="http://dvcs.w3.org/hg/encoding/raw-file/tip/Overview.html" rel="nofollow">Encoding</a></td> </tr> <tr> <td><a href="http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html" rel="nofollow">Fullscreen</a></td> </tr> <tr> <td><a href="http://dvcs.w3.org/hg/quirks-mode/raw-file/tip/Overview.html" rel="nofollow">Quirks Mode</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Web Media API Community Group" data-created="2016-09-06T14:23Z" class="sortable-entry cg"> <article id="webmediaapi"> <h2 class="group-title"><a href="https://www.w3.org/community/webmediaapi/" id="webmediaapi">Web Media API Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc"><p>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.</p> <p>See the <a rel="nofollow" href="https://www.w3.org/2016/09/webmediaapi-cg-charter.html">CG charter</a> for more information.</p></div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2024-10-16T17:09Z"> 2024-10-16</time></td> <td><a href="https://www.w3.org/community/reports/webmediaapi/CG-FINAL-webmediaapi-20241016/">Web Media API Snapshot 2024</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/webmediaapi/spec/273/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2017-07-22T03:14Z"> 2017-07-22</time></td> <td><a href="https://www.w3.org/2017/12/webmediaapi.html">Web Media API Snapshot 2017</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/webmediaapi/spec/136/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2018-12-11T01:22Z"> 2018-12-11</time></td> <td><a href="https://www.w3.org/2018/12/webmediaguidelines.html">Web Media Application Developer Guidelines</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/webmediaapi/spec/153/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2018-12-18T16:17Z"> 2018-12-18</time></td> <td><a href="https://www.w3.org/2018/12/webmediaapi.html">Web Media API Snapshot 2018</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/webmediaapi/spec/154/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2019-12-04T19:06Z"> 2019-12-04</time></td> <td><a href="https://www.w3.org/2019/12/webmediaapi.html">Web Media API Snapshot 2019</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/webmediaapi/spec/178/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2020-12-14T19:18Z"> 2020-12-14</time></td> <td><a href="https://www.w3.org/2020/12/webmediaapi.html">Web Media API Snapshot 2020</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/webmediaapi/spec/187/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2021-12-14T15:48Z"> 2021-12-14</time></td> <td><a href="https://www.w3.org/2021/12/webmediaapi.html">Web Media API Snapshot 2021</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/webmediaapi/spec/202/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2022-12-15T16:36Z"> 2022-12-15</time></td> <td><a href="https://www.w3.org/2022/12/webmediaapi.html">Web Media API Snapshot 2022</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/webmediaapi/spec/224/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2023-06-21T15:37Z"> 2023-06-21</time></td> <td><a href="https://www.w3.org/2023/06/webmediaguidelines.html">Web Media Application Developer Guidelines (deprecated)</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/webmediaapi/spec/228/commitments">Licensing commitments</a></td> </tr> <tr> <td class="col-date"><time datetime="2023-11-06T21:43Z"> 2023-11-06</time></td> <td><a href="https://www.w3.org/2023/11/webmediaapi.html">Web Media API Snapshot 2023</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/webmediaapi/spec/234/commitments">Licensing commitments</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Web Media Text Tracks Community Group" data-created="2011-09-30T02:24Z" class="sortable-entry cg"> <article id="texttracks"> <h2 class="group-title"><a href="https://www.w3.org/community/texttracks/" id="texttracks">Web Media Text Tracks Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">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.</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2014-02-20T19:37Z"> 2014-02-20</time></td> <td><a href="http://dev.w3.org/html5/webvtt/e0a5a82bd5be3501e7649a949fcce4c7b83a427c.html">WebVTT</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/texttracks/spec/68/commitments">Licensing commitments</a></td> </tr> </tbody> </table> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://dvcs.w3.org/hg/text-tracks/raw-file/default/608toVTT/608toVTT.html" rel="nofollow">Conversion of 608/708 captions to WebVTT</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Web NFC Community Group" data-created="2015-03-12T12:07Z" class="sortable-entry cg"> <article id="web-nfc"> <h2 class="group-title"><a href="https://www.w3.org/community/web-nfc/" id="web-nfc">Web NFC Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc"><p>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 <a rel="nofollow" href="https://w3c.github.io/web-nfc/charter/">Web NFC Community Group Charter</a> and the <a rel="nofollow" href="https://w3c.github.io/web-nfc/">Web NFC specification</a> for more information.</p></div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://w3c.github.io/web-nfc/">Web NFC</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Web Payments Charter Development Community Group" data-created="2014-05-05T16:03Z" class="sortable-entry cg"> <article id="webpaymentsigcharter"> <h2 class="group-title"><a href="https://www.w3.org/community/webpaymentsigcharter/" id="webpaymentsigcharter">Web Payments Charter Development Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">See the Web Payments Interest Group http://www.w3.org/Payments/IG/ This group was set up as a follow-up on the W3C Web Payments Workshop that took place 23-24 March 2014. The workshop participants advocated W3C to launch a dedicated steering group (W3C Interest Group) to engage further in the development of core standard technologies to better support payments on the Web. This community group is a first step in that direction, and will host the discussions around the future charter of the interest group. The objective is to ensure that all stakeholders are able to provide inputs on the role and actions of the future group, and to ensure that a critical mass of representatives from the different stakeholder groups are ready to engage in this work. This group will not publish specifications.</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2014-05-06T06:06Z"> 2014-05-06</time></td> <td><a href="https://www.w3.org/2013/10/payments/final_report.html">W3C Web Payments Workshop Report</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/webpaymentsigcharter/spec/74/commitments">Licensing commitments</a></td> </tr> </tbody> </table> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://www.w3.org/2014/04/payments/webpayments_charter.html" rel="nofollow">Web Payments Interest Group Charter</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Web Payments Community Group" data-created="2011-06-29T15:05Z" class="sortable-entry cg"> <article id="webpayments"> <h2 class="group-title"><a href="https://www.w3.org/community/webpayments/" id="webpayments">Web Payments Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">What follows is the original mission statement. 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.</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2014-11-29T17:07Z"> 2014-11-29</time></td> <td><a href="https://dvcs.w3.org/hg/webpayments/raw-file/default/FCGS/use-cases/2014-11-29/index.html">Web Payments CG Use Cases 1.0</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/webpayments/spec/86/commitments">Licensing commitments</a></td> </tr> </tbody> </table> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://web-payments.org/specs/source/design-principles/" rel="nofollow">Web Payments Design Principles 1.0</a></td> </tr> <tr> <td><a href="https://web-payments.org/specs/source/roadmap/" rel="nofollow">Web Payments CG Roadmap 1.0</a></td> </tr> <tr> <td><a href="https://web-payments.org/specs/source/web-commerce/" rel="nofollow">Web Payments CG Commerce 1.0</a></td> </tr> <tr> <td><a href="https://web-payments.org/specs/source/web-commerce-api/" rel="nofollow">Web Payments CG Web Commerce API 1.0</a></td> </tr> <tr> <td><a href="https://web-payments.org/specs/source/vocabs/commerce.html" rel="nofollow">Web Payments CG Commerce Vocabulary 1.0</a></td> </tr> <tr> <td><a href="https://web-payments.org/specs/source/vocabs/payswarm.html" rel="nofollow">Web Payments CG Web Payments Vocabulary 1.0</a></td> </tr> <tr> <td><a href="https://web-payments.org/specs/source/http-signatures/" rel="nofollow">Web Payments CG HTTP Signatures 1.0</a></td> </tr> <tr> <td><a href="https://web-payments.org/specs/source/secure-messaging/" rel="nofollow">Web Payments CG Secure Messaging 1.0</a></td> </tr> <tr> <td><a href="https://web-payments.org/specs/source/vocabs/security.html" rel="nofollow">Web Payments CG Security Vocabulary 1.0</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Web Thing Protocol Community Group" data-created="2019-09-17T09:58Z" class="sortable-entry cg"> <article id="web-thing-protocol"> <h2 class="group-title"><a href="https://www.w3.org/community/web-thing-protocol/" id="web-thing-protocol">Web Thing Protocol Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The mission of this group is to define a common protocol for communicating with connected devices over the web, to enable ad-hoc interoperability on the <a rel="nofollow" href="https://www.w3.org/WoT/">Web of Things</a>. Deliverables of the group may include use cases, requirements and specifications. The group will collaborate with the W3C Web of Things Interest Group and Working Group to ensure any specifications complement or extend the “<a rel="nofollow" href="https://www.w3.org/TR/wot-thing-description">Web of Things (WoT) Thing Description</a>” specification. Objectives: <ol> <li>Define a WebSocket sub-protocol for the Web of Things, using the W3C “Web of Things (WoT) Thing Description” data model and operations</li> <li>Define an HTTP protocol binding for the Web of Things (or support the Web of Things Working Group in defining this protocol binding and ensuring consistency with the WebSocket sub-protocol where appropriate)</li> <li>Evaluate other potential Web of Things protocol bindings (e.g. CoAP)</li> </ol> See the proposed <a rel="nofollow" href="https://benfrancis.github.io/web-thing-protocol-charter/">Community Group Charter</a> for more information.</div> <section> <h3>Final reports / <a href="/community/about/process/final/">licensing info</a></h3> <table> <thead> <tr> <th>Date</th> <th>Name</th> <th>Commitments</th> </tr> </thead> <tbody> <tr> <td class="col-date"><time datetime="2022-08-11T11:45Z"> 2022-08-11</time></td> <td><a href="https://www.w3.org/community/reports/web-thing-protocol/CG-FINAL-web-thing-protocol-requirements-20231101/">Web Thing Protocol Use Cases & Requirements</a></td> <td><a title="View and make commitments under the Final Specification Agreement" href="/community/web-thing-protocol/spec/218/commitments">Licensing commitments</a></td> </tr> </tbody> </table> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://w3c.github.io/web-thing-protocol/">Web Thing Protocol</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="Web-based Signage Business Group" data-created="2012-04-17T01:45Z" class="sortable-entry bg"> <article id="websignage"> <h2 class="group-title"><a href="https://www.w3.org/community/websignage/" id="websignage">Web-based Signage Business Group</a></h2> <div class="group-content collapse-small"> <div class="desc">The goal of the group was to identify use cases and system image/model for expansion of web browser based digital signage and smarter integration of existing Web standards. </div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://www.w3.org/2016/websigns/ucr/">Web-based Signage Use cases and Requirements</a></td> </tr> <tr> <td><a href="https://www.w3.org/2016/websigns/core/">Architecture and Requirements for Web-based Signage Player - Core Profile</a></td> </tr> <tr> <td><a href="https://www.w3.org/2016/websigns/basic-media/">Architecture and Requirements for Web-based Signage Player - Basic Media Profile</a></td> </tr> <tr> <td><a href="https://www.w3.org/2016/websigns/storage/">Architecture and Requirements for Web-based Signage Player - Storage Profile</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="WebAPI Discovery Community Group" data-created="2016-12-13T12:13Z" class="sortable-entry cg"> <article id="web-api-discovery"> <h2 class="group-title"><a href="https://www.w3.org/community/web-api-discovery/" id="web-api-discovery">WebAPI Discovery Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">A group to develop a mechanism for the automatic discovery of WebAPIs, by extending the schema.org vocabulary. Increasingly, large online platforms and services provide one or more Web APIs for third-party developers. Moreover, many companies build WebAPIs as their primary product (Email API, SMS API, etc.). This has resulted in an explosion of the number of WebAPIs in recent years. Developers spend a significant amount of time searching for suitable WebAPIs to meet their needs. Our intention is to work closely with Schema.org to define a WebAPI-specific extension and promote usage of this extension among API owners. In the long run, our aim is to contribute this extension into the core Schema.org vocabulary. To achieve these goals we are seeking feedback and collaboration from API owners, DX specialists, API description language experts and maintainers of various API catalogs. </div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://webapi-discovery.github.io/rfcs/rfc0001.html" rel="nofollow">WADG0001 WebAPI type extension</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> <li data-title="XPath Next Community Group" data-created="2017-03-10T16:36Z" class="sortable-entry cg"> <article id="xpath-next"> <h2 class="group-title"><a href="https://www.w3.org/community/xpath-next/" id="xpath-next">XPath Next Community Group</a></h2> <div class="group-content collapse-small"> <div class="desc">Create a place for gathering requirement from existing user of XPath, potential user of XPath and research in this area</div> <section> <h3>Drafts / <a href="/community/about/process/cla/">licensing info</a></h3> <table> <thead> <tr> <th>Name</th> </tr> </thead> <tbody> <tr> <td><a href="https://github.com/XPath-Next/XPath-Next/blob/master/README.md" rel="nofollow">ReadMe</a></td> </tr> </tbody> </table> </section> </div> <a href="" class="right tooltip read-more"><span>Read more</span></a> </article> </li> </ul> </section> </div> </div>  <aside id="w3c_footer"> <div class="logo-footer"><a href="/community/"><img src="https://www.w3.org/community/wp-content/themes/StoryTeller/img/svg/cgbg-logo-footer.svg" alt="Community and Business Groups"></a></div> <div class="center"> <h2 class="visuallyhidden">Footer Navigation</h2> <div class="footer-nav"> <h3>Navigation</h3> <ul class="footer_top_nav"> <li><a href="/">Home</a></li> <li><a href="/standards/">Standards</a></li> <li><a href="/groups/">Groups</a></li> <li><a href="/get-involved/">Get involved</a></li> <li><a href="/resources/">Resources</a></li> <li><a href="/news-events/">News & Events</a></li> <li><a href="/about/">About W3C</a></li> </ul> </div> <div class="footer-nav"> <h3>Contact W3C</h3> <ul class="footer_bottom_nav"> <li><a href="/contact/">Contact</a></li> <li><a accesskey="0" href="/help/">Help</a></li> <li><a href="/donate/">Donate</a></li> <li><a href="/policies/">Legal & Policies</a></li> <li><a href="/about/corporation/">Corporation</a></li> <li><a href="https://status.w3.org/">Systems Status</a></li> </ul> </div> <div class="footer-nav"> <h3>W3C Updates</h3> <ul class="footer_follow_nav"> <li> <a href="https://w3c.social/@w3c" title="W3C on Mastodon"><img src="https://www.w3.org/community/wp-content/themes/StoryTeller/img/svg/mastodon-logo.svg" alt="Mastodon" class="social-icon" height="40"/></a> </li> </ul> </div>  <footer class="clear copyright">Copyright © 2025 <a href="/">World Wide Web Consortium</a>.<br> <abbr title="World Wide Web Consortium">W3C</abbr><sup>®</sup> <a href="/policies/#disclaimers">liability</a>, <a href="/policies/#trademarks">trademark</a> and <a rel="license" href="/copyright/document-license/" title="W3C Document License">permissive license</a> rules apply. </footer> </div> </aside> <script src="/_sf/build/js/community_groups.a958515d975b4af52039.js"></script> </body> </html>

CINXE.COM

Reports