-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathcharter.html
387 lines (372 loc) · 19.9 KB
/
charter.html
1
<?xml version="1.0" encoding="utf-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html lang="en-US" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US"> <head> <meta http-equiv="content-type" content="application/xhtml+xml; charset=utf-8" /> <title>Open License Expression Working Group Charter (DRAFT)</title> <link rel="stylesheet" href="http://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen" /> <link rel="stylesheet" type="text/css" href="http://www.w3.org/Guide/pubrules-style.css" /> <link rel="stylesheet" type="text/css" href="http://www.w3.org/2006/02/charter-style.css" /> <style type="text/css">.issue { background-color: #ffff00; margin-top: 1em; padding: 0.5em; border: solid thin black;}#warning { font-size: 124%; -epub-text-transform: lowercase; text-transform: lowercase; font-variant: small-caps; border-width: medium; border-style: ridge; padding: 0.5em; box-shadow: 5px 5px 0px 0px gray; margin-right: 10em;}li {padding: 0;}ul#navbar li { padding-bottom: 0em;}ul li ul {list-style-type:circle}</style></head> <body> <div id="template"> <ul id="navbar" style="font-size: small"> <li><a href="#scope">Scope</a></li> <li><a href="#deliverables">Deliverables</a></li> <li><a href="#coordination">Dependencies and Liaisons</a></li> <li><a href="#participation">Participation</a></li> <li><a href="#communication">Communication</a></li> <li><a href="#decisions">Decision Policy</a></li> <li><a href="#patentpolicy">Patent Policy</a></li> <li><a href="#about">About this Charter</a></li> </ul> <p><a href="https://www.w3.org/" shape="rect"><img width="72" height="48" alt="W3C" src="https://www.w3.org/Icons/w3c_home" /></a> </p> <div id="warning"> <p>This is a draft charter only. It has not been endorsed by W3C Management or Members and is therefore entirely speculative.</p> <p>Comments on this draft are welcome via <a href="mailto:public-ole-comment@w3.org">public-ole-comment@w3.org</a> [<a href="https://lists.w3.org/Archives/Public/public-ole-comment/">Archive</a>, <a href="mailto:public-ole-comment-request@w3.org?subject=subscribe">Subscribe</a>].</p> </div> <h1 id="title">Open License Expression Working Group Charter (Draft)</h1> <br /> <p class="mission">The <strong>mission</strong> of the <a href="">Open License Expression Working Group</a>, part of the <a href="">Data Activity</a>, is to define a semantic data model for expressing license statements for digital content, and define the technical elements to make it deployable across browsers and content systems. </p> <div class="noprint"> <p class="join">@@@Join the Open License Expression Working Group@@@.</p> </div> <table class="summary-table"> <tbody> <tr id="Duration"> <th rowspan="1" colspan="1">End date</th> <td rowspan="1" colspan="1">31 December 2017</td> </tr> <tr> <th rowspan="1" colspan="1">Confidentiality</th> <td rowspan="1" colspan="1">Proceedings are <a href="/2005/10/Process-20051014/comm.html#confidentiality-levels" shape="rect"> public </a></td> </tr> <tr> <th rowspan="1" colspan="1">Initial Chairs</th> <td rowspan="1" colspan="1">Renato Iannella, <a href="http://semanticidentity.com/">Semantic Identity</a><br /> A.N. Other</td> </tr> <tr> <th rowspan="1" colspan="1">Initial Team Contacts<br /> (FTE %: 20)</th> <td rowspan="1" colspan="1">Phil Archer</td> </tr> <tr> <th rowspan="1" colspan="1">Usual Meeting Schedule</th> <td rowspan="1" colspan="1">Teleconferences: weekly <br /> Face-to-face: twice annually </td> </tr> </tbody> </table> <div class="scope"> <h2 id="scope">Scope</h2> <p> The web has provided the wider community with standardised mechanisms for numerous content-management services; publishing, distribution, consumption, describing, and sharing. However, the key areas of content licensing has not been addressed in web standards to date. Content licenses express the terms of usage for content for end users. Hence, content owners can express terms and processing systems can determine what permissions and other terms are associated with a given resource. End users can then be made aware of any usage conditions associated with that content. </p> <p> A license expression system should provide a flexible and interoperable information model that supports transparent and innovative use of digital content across all sectors and communities. The underlying model should be targeted to support the business models of open, educational, government, and commercial communities through profiles that enhance the model to align to their requirements whilst providing a common semantic layer for wider interoperability. </p> <p>In order to address these needs, this working group will work on deliverables focused in the following approaches:<ul><li>Semantic Information Model: An abstract information model for license statements</li><li>Vocabulary: A precise vocabulary defining the information model and its elements </li><li>Serializations: one or more serialization formats of the information model and vocabulary, such as XML, RDF/OWL, JSON/JSON-LD</li></ul><p> This work will take the form of several specifications as Recommendation Track documents and where possible, this working group will collaborate with other working groups to fulfill the goals of these deliverables.</p><p>The semantic information model, vocabulary, and serializations will start from the ODRL specifications, developed by the <a href="https://www.w3.org/community/odrl/">W3C ODRL Community Group</a>. The ODRL work began 15 years ago and has been evolving the specification to meet industry and communiuty requirements with widescale adoption (for example in the mobile sector [ref OMA]. Over the past few years the group transformed in the W3C ODRL Community Group and has created five updated Version 2.1 specifications (an information model, vocabulary, XML encoding, JSON encoding, and ontology). The current ODRL specifications are deployed as profiles by business sectors, for example the IPTC has adopted ODRL for licensing online news articles [REF].</p> <p>The Open License Expression Working Group will take into account any additional needs of the wider community including commercial and non-commercial publishers, consumers and re-users of human readable content and machine readable data. In addition, implementation feedback from related license expression languages and initiatives will be considered in the final deliverables. </p> </div> <div class="scope"> <h2 id="noscope">Out of Scope</h2> <p>The Open License Expression Working Group will <strong>not</strong> be considering: <ul> <li>access control mechanisms</li> <li>digital rights management</li> <li>enforcement mechanisms</li> <li>jurisdictional legal issues</li> </ul> </p> </div> <div> <h2 id="deliverables">Deliverables</h2> <p>The titles of the deliverables are not final; the Working Group will have to decide on the final titles as well as the structures of the documents. The Working Group may also decide to merge some deliverables into one document or produce several documents that together constitute one of the deliverables.</p> <ul> <li>Additional Use Cases and Requirements document (NOTE)</li> <li>A technology-neutral license information model (Recommendation)</li> <li>A vocabulary of license terms (Recommendation)</li> <li>Encoding of the model/terms in XML (Recommendation)</li> <li>Encoding of the model/terms in RDF/OWL (Recommendation)</li> <li>Encoding of the model/terms in JSON-LD (Recommendation)</li> </ul> </div> <div> <h3>Inputs</h3> <p>The Open License Expression Working Group will use the following W3C ODRL Community Group specifications as the starting position: <ul> <li><a href="http://www.w3.org/community/odrl/model/2.1/" class="none">ODRL Version 2.1 Core Model</a></li> <li><a href="http://www.w3.org/community/odrl/vocab/2.1/" class="none">ODRL Version 2.1 Common Vocabulary</a></li> <li><a href="http://www.w3.org/community/odrl/xml/2.1/" class="none">ODRL Version 2.1 XML Encoding</a></li> <li><a href="http://www.w3.org/community/odrl/json/2.1/" class="none">ODRL Version 2.1 JSON Encoding</a></li> <li><a href="http://www.w3.org/ns/odrl/2/ODRL21" class="none">ODRL Version 2.1 Ontology</a></li> </ul> </p> <p>Other similar license expression models, langauges, and terms will also be considered by the Open License Expression Working Group through the additional Use Cases and Requirements collected and analysed.</p> </div> <div> <h3>Success Criteria</h3> <p>To advance the encoding specifications to Proposed Recommendation, evidence will be gathered of independent deployments of license expression systems (at least two per encoding).</p> </div> <h3>Milestones (Recommendation)</h3> <table width="80%" class="roadmap"> <caption> Milestones (Rec Track)</caption> <tfoot> <tr> <td colspan="7" rowspan="1">Note: The group will document significant changes from this initial schedule on the group home page.</td> </tr> </tfoot> <tbody> <tr> <th rowspan="1" colspan="1">Deliverable</th> <th rowspan="1" colspan="1"><acronym title="First Working Draft">FPWD</acronym></th> <th rowspan="1" colspan="1"><acronym title="Last Call/Candidate Recommendation">LCCR</acronym></th> <th rowspan="1" colspan="1"><acronym title="Proposed Recommendation">PR</acronym></th> <th rowspan="1" colspan="1"><acronym title="Recommendation">Rec</acronym></th> </tr> <tr> <th rowspan="1" colspan="1">License Expression - Information Model</th> <td class="WD1" rowspan="1" colspan="1">December 2016</td> <td class="CR" rowspan="1" colspan="1">April 2017</td> <td class="PR" rowspan="1" colspan="1">August 2017</td> <td class="REC" rowspan="1" colspan="1">October 2017</td> </tr> <tr> <th rowspan="1" colspan="1">License Expression - Vocabulary</th> <td class="WD1" rowspan="1" colspan="1">December 2016</td> <td class="CR" rowspan="1" colspan="1">April 2017</td> <td class="PR" rowspan="1" colspan="1">August 2017</td> <td class="REC" rowspan="1" colspan="1">October 2017</td> </tr> <tr> <th rowspan="1" colspan="1">License Expression - XML Encoding</th> <td class="WD1" rowspan="1" colspan="1">Febuary 2017</td> <td class="CR" rowspan="1" colspan="1">June 2017</td> <td class="PR" rowspan="1" colspan="1">October 2017</td> <td class="REC" rowspan="1" colspan="1">December 2017</td> </tr> <tr> <th rowspan="1" colspan="1">License Expression - JSON-LD Encoding</th> <td class="WD1" rowspan="1" colspan="1">Febuary 2017</td> <td class="CR" rowspan="1" colspan="1">June 2017</td> <td class="PR" rowspan="1" colspan="1">October 2017</td> <td class="REC" rowspan="1" colspan="1">December 2017</td> </tr> <tr> <th rowspan="1" colspan="1">License Expression - RDF/OWL Encoding</th> <td class="WD1" rowspan="1" colspan="1">Febuary 2017</td> <td class="CR" rowspan="1" colspan="1">June 2017</td> <td class="PR" rowspan="1" colspan="1">October 2017</td> <td class="REC" rowspan="1" colspan="1">December 2017</td> </tr> </tbody> </table> <table width="80%" class="roadmap"> <caption> Milestones (Notes)</caption> <tfoot> <tr> <td colspan="7" rowspan="1">Note: The group will document significant changes from this initial schedule on the group home page.</td> </tr> </tfoot> <tbody> <tr> <th rowspan="1" colspan="1">Deliverable</th> <th rowspan="1" colspan="1"><acronym title="First Working Draft">FPWD</acronym></th> <th rowspan="1" colspan="1"><acronym title="WG Note">WG Note</acronym></th> </tr> <tr> <th rowspan="1" colspan="1">Licence Expression - Use Cases & Requirements</th> <td class="WD1" rowspan="1" colspan="1">April 2016</td> <td class="LC" rowspan="1" colspan="1">October 2016</td> </tr> </tbody> </table> <div> <h3 id="timeline">Timeline View Summary</h3> <ul> <li>November 2015: First teleconference</li> <li>February 2016: First face-to-face meeting</li> <li>March 2016: UCR</li> <li>May 2016: Data Model FPWD</li> <li>November 2016: Encodings FPWD (after TPAC)</li> <li>February 2017: Processing Model FPWD</li> <li>April 2017: Encodings to LCCR</li> <li>July 2017 Processing model to LCCR</li> <li>November 2017: Encodings and Processing to REC</li> </ul> </div> </div> <div class="dependencies"> <h2 id="coordination">Dependencies and Liaisons</h2> <h3>W3C Groups</h3> <dl> <dt><a href="http://www.w3.org/dpub/IG/">Digital Publishing Interest Group</a></dt> <dd>The License & Rights Statements WG's work is equally relevant in both Digital Dublishing and the Data Activity.</dd> <dt><a href="/International/" shape="rect">Internationalization Activity</a></dt> <dd>Licensing and Rights Statements must take account of multilingualism as well as jurisdictional differences.</dd> <dt><a href="http://www.w3.org/Privacy/" shape="rect">Privacy Interest Group</a></dt> <dd>Ensure that the privacy concerns are properly included in the WG's considerations.</dd> </dl> <div id="conformance"> <p>Furthermore, the LRS Working Group expects to follow these W3C Recommendations:</p> <ul> <li><a href="/TR/qaframe-spec/" shape="rect">QA Framework: Specification Guidelines</a>.</li> <li><a href="/TR/charmod/" shape="rect">Character Model for the World Wide Web 1.0: Fundamentals</a></li> <li><a href="/TR/webarch/" shape="rect">Architecture of the World Wide Web, Volume I</a></li> </ul> </div> </div> <div class="participation"> <h2 id="participation">Participation</h2> <p>To be successful, the License & Rights Statements Working Group is expected to have 20 or more active participants for its duration. To get the most out of this work, participants should expect to devote several hours a week; for budgeting purposes, we recommend at least half a day a week. For chairs and document editors the commitment will be higher, say, 1-2 days a week. Participants who follow the work less closely should be aware that if they miss decisions through inattention further discussion of those issues may be ruled out of order. However, most participants follow some areas of discussion more closely than others, and the time needed to stay in good standing therefore varies from week to week. The Working Group will also allocate the necessary resources for building Test Suites for each specification.</p> </div> <div class="communication"> <h2 id="communication">Communication</h2> <p>This group primarily conducts its work on the @@@public mailing list@@@. Administrative tasks may be conducted in @@@Member-only@@@ communications. Comments on the group's work will be welcome via the <a href="https://lists.w3.org/Archives/Public/public-lrs-comment/">public comment list</a>.</p> <p>Information about the group (deliverables, participants, face-to-face meetings, teleconferences, etc.) is available from the LRS Working Group home page.</p> </div> <div class="decisions"> <h2 id="decisions">Decision Policy</h2> <p>As explained in the Process Document (<a href="/Consortium/Process/policies#Consensus">section 3.3</a>), this group will seek to make decisions when there is consensus. When the Chair puts a question and observes dissent, after due consideration of different opinions, the Chair should record a decision (possibly after a formal vote) and any objections, and move on. <br /> <br /> A formal vote should allow for remote asynchronous participation—using, for example, email and/or web-based survey techniques. Any resolution taken in a face-to-face meeting or teleconference is to be considered provisional until 5 working days after the publication of the resolution in draft minutes sent to the group's mailing list. </p> <p>This charter is written in accordance with <a href="/Consortium/Process/policies#Votes">Section 3.4, Votes</a> of the W3C Process Document and includes no voting procedures beyond what the Process Document requires. </p> </div> <div class="patent"> <h2 id="patentpolicy">Patent Policy </h2> <p>This Working Group operates under the <a href="/Consortium/Patent-Policy-20040205/" shape="rect">W3C Patent Policy</a> (5 February 2004 Version). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis.</p> <p>For more information about disclosure obligations for this group, please see the <a href="/2004/01/pp-impl/" shape="rect">W3C Patent Policy Implementation</a>.</p> </div> <h2 id="about">About this Charter</h2> <p>This charter for the Data on the Web Best Practices Working Group has been created according to <a href="/Consortium/Process/groups#GAGeneral" shape="rect">section 6.2</a> of the <a href="/Consortium/Process" shape="rect">Process Document</a>. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.</p> <hr /> <address> Phil Archer </address> <p class="copyright"><a rel="Copyright" href="/Consortium/Legal/ipr-notice#Copyright" shape="rect">Copyright</a> © 2015 <a href="/" shape="rect"><acronym title="World Wide Web Consortium">W3C</acronym></a> <sup>®</sup> (<a href="http://www.csail.mit.edu/" shape="rect"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/" shape="rect"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/" shape="rect">Keio</a>, <a href="http://ev.buaa.edu.cn/" shape="rect">Beihang</a>), All Rights Reserved.</p> </body></html>