This repository has been archived by the owner on Dec 18, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 8
/
Copy pathcharter.html
308 lines (298 loc) · 17.9 KB
/
charter.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
<?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" xml:lang="en-US" xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type" content="application/xhtml+xml; charset=utf-8" />
<title>License & Rights Statements Working Group Charter (DRAFT)</title>
<link media="screen" type="text/css" href="http://www.w3.org/2005/10/w3cdoc.css"
rel="stylesheet" />
<link href="http://www.w3.org/Guide/pubrules-style.css" type="text/css" rel="stylesheet" />
<link href="http://www.w3.org/2006/02/charter-style.css" type="text/css" rel="stylesheet" />
<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 style="font-size: small" id="navbar">
<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 shape="rect" href="https://www.w3.org/"><img width="72" height="48" src="https://www.w3.org/Icons/w3c_home"
alt="W3C" /></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:[email protected]">[email protected]</a>
[<a href="https://lists.w3.org/Archives/Public/public-lrs-comment/">Archive</a>, <a href="mailto:[email protected]?subject=subscribe">Subscribe</a>].</p>
</div>
<h1 id="title">License & Rights Statements Working Group Charter (Draft)</h1>
<p>The ease of access to online content, whether it's text, video or data, often leaves the question of rights and licenses unanswered. In many cases this is unimportant: a reader does not need to know and will rarely care what license terms are associated with an online article. However, if content is to be re-used in some way – perhaps an image is being re-used in another article, a presentation is embedded in a Web page, or a dataset is being used in a novel application - then the terms and conditions of use are important. If the re-user is a commercial operation then the terms are critical. The situation becomes more complex if multiple resources are used in a single publication or application, each with its own license terms. Can they be used together? If so, what are the license terms of the new work?</p>
<p>Several attempts have been made to solve this problem, not least Creative Commons which, since 2001, has worked to 'keep the internet creative, free and open' by offering a set of widely understood licenses. Other well known licenses include GPL, MIT, Apache, the UK Open Government Licence and more. In May 2013, the Open Data Institute developed its vocabulary for Open Data Rights Statements. In each case, the aim is to offer clear information on what can and can't be done with the relevant resource.</p>
<p>The Open Digital Rights Language, ODRL, addresses a large number of use cases. Driven largely by the publishing industry, it offers “…a flexible and interoperable information model to support transparent and innovative use of digital assets in the publishing, distribution and consumption of content, applications, and services across all sectors and communities.”</p>
<p class="mission">The <strong>mission</strong> of the License & Rights Statements Working Group, part of the <a href="/2013/data/">Data Activity</a>, is to develop standards to:</p>
<ol>
<li>allow <strong>automated or semi-automated processing of license information/rights statements</strong> to determine what permissions and obligations are associated with a given resource;</li>
<li>automatically, or semi-automatically, <strong>generate license/rights statements</strong> for new work derived from resources that are themselves covered by such restrictions.</li>
</ol>
<p>Without wishing to limit its ability to fulfill these goals as it sees fit, the <abbr title="License & Rights Statements">LRS</abbr> WG is explicitly asked to re-use and build upon existing work as much as possible, noting that implementation and investment in Creative Commons and ODRL in particular are significant.</p>
<div class="noprint">
<p class="join">@@@Join the License & Rights Statements Working Group@@@.</p>
</div>
<table class="summary-table">
<tbody>
<tr id="Duration">
<th colspan="1" rowspan="1">End date</th>
<td colspan="1" rowspan="1">31 December 2017</td>
</tr>
<tr>
<th colspan="1" rowspan="1">Confidentiality</th>
<td colspan="1" rowspan="1">Proceedings are <a shape="rect" href="/2005/10/Process-20051014/comm.html#confidentiality-levels">
public </a></td>
</tr>
<tr>
<th colspan="1" rowspan="1">Initial Chairs</th>
<td colspan="1" rowspan="1">Renato Ianella, <a href="http://semanticidentity.com/">Semantic Identity</a><br />
A.N. Other</td>
</tr>
<tr>
<th colspan="1" rowspan="1">Initial Team Contacts<br />
(FTE %: 20)</th>
<td colspan="1" rowspan="1">Phil Archer</td>
</tr>
<tr>
<th colspan="1" rowspan="1">Usual Meeting Schedule</th>
<td colspan="1" rowspan="1">Teleconferences: weekly <br />
Face-to-face: twice annually </td>
</tr>
</tbody>
</table>
<div class="scope">
<h2 id="scope">Scope</h2>
<p>The License & Rights Statements WG will take into account the needs of as wide a community as possible including commercial and non-commercial publishers, consumers and re-users of human readable content and machine readable data. </p>
</div>
<div class="scope">
<h2 id="noscope">Out of Scope</h2>
<p>Access control mechanisms, digital rights management. Legal information is clearly in scope, however, it is not the task of the Working Group to try and encode laws directly, nor to define a system designed to be legally rigorous. </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>Use Cases and Requirements document (NOTE)</li>
<li>A technology-neutral data model (NOTE)</li>
<li>Encoding of the data model in RDF (Recommendation)</li>
<li>Encoding of the model in XML (Recommendation)</li>
<li>Processing model for combining multiple licenses/rights statements (Recommendation)</li>
</ul>
<p class="issue">More detail needed? Is this the right list?</p>
</div>
<div>
<h3>Inputs</h3>
<ul>
<li><a href="https://creativecommons.org/">Creative Commons</a>, including <a href="http://www.w3.org/Submission/ccREL/">ccREL: The Creative Commons Rights Expression Language</a></li>
<li>The work of the <a href="https://www.w3.org/community/odrl/">Open Digital Rights Language Community Group</a></li>
<li><a href="http://schema.theodi.org/odrs/">Open Data Rights Statement Vocabulary</a></li>
<li>… More?</li>
</ul>
</div>
<div>
<h3>Success Criteria</h3>
<p>To advance the encoding specifications to Proposed Recommendation, evidence will be gathered of independent deployments of license/rights data (at least two per encoding).</p>
<p>For the processing model, evidence will be gathered of independent implementations where license/rights statement data has been gathered and used in a relevant application, such as a publishing tool chain, data portal etc.</p>
</div>
<h3>Milestones (Recommendation)</h3>
<p class="issue">Is this realistic? Can we be done by December 2017?</p>
<table width="80%" class="roadmap">
<caption> Milestones (Rec Track)</caption>
<tfoot>
<tr>
<td rowspan="1" colspan="7">Note: The group will document significant changes from this initial schedule on the group home
page.</td>
</tr>
</tfoot>
<tbody>
<tr>
<th colspan="1" rowspan="1">Deliverable</th>
<th colspan="1" rowspan="1"><acronym title="First Working Draft">FPWD</acronym></th>
<th colspan="1" rowspan="1"><acronym title="Last Call/Candidate Recommendation">LCCR</acronym></th>
<th colspan="1" rowspan="1"><acronym title="Proposed Recommendation">PR</acronym></th>
<th colspan="1" rowspan="1"><acronym title="Recommendation">Rec</acronym></th>
</tr>
<tr>
<th colspan="1" rowspan="1">RDF & XML Encodings</th>
<td colspan="1" rowspan="1" class="WD1">November 2016</td>
<td colspan="1" rowspan="1" class="CR">July 2017</td>
<td colspan="1" rowspan="1" class="PR">October 2017</td>
<td colspan="1" rowspan="1" class="REC">December 2017</td>
</tr>
<tr>
<th colspan="1" rowspan="1">Processing Model</th>
<td colspan="1" rowspan="1" class="WD1">November 2016</td>
<td colspan="1" rowspan="1" class="CR">July 2017</td>
<td colspan="1" rowspan="1" class="PR">October 2017</td>
<td colspan="1" rowspan="1" class="REC">December 2017</td>
</tr>
</tbody>
</table>
<table width="80%" class="roadmap">
<caption> Milestones (Notes)</caption>
<tfoot>
<tr>
<td rowspan="1" colspan="7">Note: The group will document
significant changes from this initial schedule on the group home
page.</td>
</tr>
</tfoot>
<tbody>
<tr>
<th colspan="1" rowspan="1">Deliverable</th>
<th colspan="1" rowspan="1"><acronym title="First Working Draft">FPWD</acronym></th>
<th colspan="1" rowspan="1"><acronym title="WG Note">WG Note</acronym></th>
</tr>
<tr>
<th colspan="1" rowspan="1">Use Cases & Requirements</th>
<td colspan="1" rowspan="1" class="WD1">March 2016</td>
<td colspan="1" rowspan="1" class="LC">November 2016</td>
</tr>
<tr>
<th colspan="1" rowspan="1">Data Model</th>
<td colspan="1" rowspan="1" class="WD1">July 2016</td>
<td colspan="1" rowspan="1" class="LC">January 2017</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 shape="rect" href="/International/">Internationalization Activity</a></dt>
<dd>Licensing and Rights Statements must take account of multilingualism as well as jurisdictional differences.</dd>
<dt><a shape="rect" href="http://www.w3.org/Privacy/">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 shape="rect" href="/TR/qaframe-spec/">QA Framework: Specification Guidelines</a>.</li>
<li><a shape="rect" href="/TR/charmod/">Character Model for the World Wide Web 1.0: Fundamentals</a></li>
<li><a shape="rect" href="/TR/webarch/">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 shape="rect" href="/Consortium/Patent-Policy-20040205/">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 shape="rect" href="/2004/01/pp-impl/">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 shape="rect" href="/Consortium/Process/groups#GAGeneral">section
6.2</a> of the <a shape="rect" href="/Consortium/Process">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 shape="rect" href="/Consortium/Legal/ipr-notice#Copyright"
rel="Copyright">Copyright</a> © 2015 <a shape="rect" href="/"><acronym
title="World Wide Web Consortium">W3C</acronym></a> <sup>®</sup> (<a
shape="rect" href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>,
<a shape="rect" href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
<a shape="rect" href="http://www.keio.ac.jp/">Keio</a>, <a shape="rect" href="http://ev.buaa.edu.cn/">Beihang</a>),
All Rights Reserved.</p>
</body>
</html>