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
/
charter.html
311 lines (294 loc) · 22 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
309
310
311
<?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>Permissions & Obligations 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:[email protected]">[email protected]</a>
[<a href="https://lists.w3.org/Archives/Public/public-ole-comment/">Archive</a>,
<a href="mailto:[email protected]?subject=subscribe">Subscribe</a>].</p>
</div>
<h1 id="title">Permissions & Obligations Expression Working Group Charter (Draft)</h1>
<p>The Web has provided the community with standardized mechanisms for numerous content-management services: publishing, distribution, consumption, describing, and sharing. However, the key area of permissions, obligations and licensing has not been addressed in Web standards to date. Content licenses, rights statements, permissions and obligations express the terms of usage for content. With a standard vocabulary, content owners can express terms and processing systems can determine what permissions and other terms are associated with a given resource or collection of resources.</p>
<p>A permissions and obligations expression system should provide a flexible and interoperable information model that supports transparent and innovative (re)use of digital content across all sectors and communities. The underlying model should support the business models of open, educational, government, and commercial communities through profiles that align with their specific requirements whilst retaining a common semantic layer for wider interoperability. The system should not, however, be the basis of legal compliance or enforcement mechanisms.</p>
<p>A permissions and obligations expression language is composed of detailed terms that are both machine-processable and expressible in a form for human-consumption. Allowable actions, constraints, and requirements are expressed at a level enabling complex and business-specific expressions to be created from a vocabulary with specific semantics. This accommodates a broad range of situations and addresses a different business/user need than systems such as <a href="http://creativecommons.org/">Creative Commons</a> that provide generic sharing licenses.</p>
<p class="mission">The <strong>mission</strong> of the <a href="">Permissions & Obligations Expression Working Group</a> is to define a semantic data model for expressing permissions and obligations statements for digital content, and to define the technical elements to make it deployable across browsers and content systems.</p>
<div class="noprint">
<p class="join">@@@Join the Permissions & Obligations 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">Ben Whittam Smith, Thomson Reuters<br />Renato Iannella, Knowledgeflux, TBC</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>
<div class="scope">
<h2 id="scope">Scope</h2>
<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 community requirements with wide scale adoption. Over the past few years the group transformed into 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 <a href="http://dev.iptc.org/RightsML-Work-in-Progress">IPTC has adopted ODRL</a> for licensing online news articles.</p>
<p>The Permissions & Obligations Expression Working Group will take into account 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 languages and initiatives will be considered in the final deliverables. For example, <a href="http://schema.theodi.org/odrs/"><abbr title="Open Data Rights Statements">ODRS</abbr></a> and <a href="https://www.useplus.com/">PLUS photo licensing</a>.</p>
<p>In order to address the needs of atomic rights and obligations expressions, this Working Group will produce deliverables that define an abstract information model that is then realized in a variety of mappings and serializations. This work will take the form of <a href="#deliverables">several specifications</a> as Recommendation Track documents and supporting Notes.</p>
</div>
<div class="scope">
<h2 id="noscope">Out of Scope</h2>
<p>The Permissions & Obligations Expression Working Group will <strong>not</strong> be considering:</p>
<ul>
<li>access control mechanisms;</li>
<li>digital rights management;</li>
<li>a rule language for combining statements (beyond simple set operations);</li>
<li>enforcement mechanisms;</li>
<li>legal jurisdiction issues.</li>
</ul>
</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 permissions and obligations information model (Recommendation)</li>
<li>A definition of the formal semantics of the information model (Note)</li>
<li>A vocabulary for machine-readable expression of permissions and obligations (Recommendation)</li>
<li>Mapping of the model and terms in XML (Recommendation)</li>
<li>Mapping of the model and terms in RDF/OWL (Recommendation)</li>
<li>Mapping of the model and terms in JSON (Recommendation)</li>
</ul>
<p>The working group will further consider publishing a Note describing a P & O expression of Creative Commons licenses.</p>
<div>
<h3>Inputs</h3>
<p>The Permissions & Obligations Expression Working Group will use the following W3C ODRL Community Group specifications as the starting position:</p>
<ul>
<li><a href="http://www.w3.org/community/odrl/model/2.1/" class="none">ODRL Version 2.1 Information 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>Other similar models, languages, and terms will also be considered by the Working Group based on an analysis of additional Use Cases and Requirements that the group will collect.</p>
</div>
<div>
<h3 id="secAndPriv">Security and Privacy Considerations</h3>
<p>Each specification should contain a section detailing any known security and privacy implications for implementers, Web authors, and end users.</p>
</div>
<div>
<h3>Success Criteria</h3>
<p>To advance the encoding specifications to Proposed Recommendation, evidence will be gathered of independent implementations of permissions & obligations expression systems (at least two per mapping).</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">Permissions & Obligations Expression - Information Model</th>
<td class="WD1" rowspan="1" colspan="1">May 2016</td>
<td class="CR" rowspan="1" colspan="1">April 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">Permissions & Obligations Expression - Vocabulary</th>
<td class="WD1" rowspan="1" colspan="1">May 2016</td>
<td class="CR" rowspan="1" colspan="1">April 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">Permissions & Obligations Expression - XML Mapping</th>
<td class="WD1" rowspan="1" colspan="1">May 2016</td>
<td class="CR" rowspan="1" colspan="1">April 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">Permissions & Obligations Expression - RDF/OWL Mapping</th>
<td class="WD1" rowspan="1" colspan="1">May 2016</td>
<td class="CR" rowspan="1" colspan="1">April 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">Permissions & Obligations Expression - JSON Mapping</th>
<td class="WD1" rowspan="1" colspan="1">May 2016</td>
<td class="CR" rowspan="1" colspan="1">April 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">Permissions & Obligations Expression - Use Cases & Requirements</th>
<td class="WD1" rowspan="1" colspan="1">May 2016</td>
<td class="LC" rowspan="1" colspan="1">November 2016</td>
</tr>
<tr>
<th rowspan="1" colspan="1">Permissions & Obligations Expression - Formal Semantics</th>
<td class="WD1" rowspan="1" colspan="1">May 2016</td>
<td class="LC" rowspan="1" colspan="1">November 2017</td>
</tr>
</tbody>
</table>
<div>
<h3 id="timeline">Timeline View Summary</h3>
<ul>
<li>February 2016: First teleconference</li>
<li>March 2016: First face-to-face meeting</li>
<li>May 2016: First publications, expected to be minoir modifications of existing ODRL documents</li>
<li>April 2017: Candidate Recommendation</li>
<li>October 2017: Proposed Recommendation</li>
<li>December 2017: Recommendation</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 Permissions & Obligations Expression work is highly relevant for the Publishing Community at large that this group represents within W3C</dd>
<dt><a href="/2013/dwbp/">Data on the Web Best Practices</a> and <a href="/2015/spatial/">Spatial Data on the Web</a> Working Groups.</dt>
<dd>Permissions and Obligations are highly relevant to the sharing of data on the Web.</dd>
<dt><a href="/International/" shape="rect">Internationalization Activity</a></dt>
<dd>Licensing 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>
<dt><a href="http://www.w3.org/Social/WG">Social Web WG</a>, <a href="https://www.w3.org/community/ldpnext/">LDP Next CG</a> and <a href="http://www.w3.org/Payments/IG/">Web Payments IG</a>.</dt>
<dd>Possible new use cases will be solicited from all three groups.</dd>
<dt><a href="/2001/sw/interest/">Semantic Web Interest Group</a> and its <a href="http://www.w3.org/2001/sw/interest/webschema.html">Web Schemas Task Force</a>.</dt>
<dd>Feedback on the vocabulary will be sought from the <abbr title="Semantic Web Interest Group">SWIG</abbr>'s <a href="https://lists.w3.org/Archives/Public/public-vocabs/">Public Vocabs</a> list.</dd>
<dt>The <a href="https://www.w3.org/community/odrl/">ODRL CG</a></dt>
<dd>Membership of the ODRL CG is wider than the WG and provides an important source of input and expertise.</dd>
</dl>
<div id="conformance">
<p>Furthermore, the P&am;OE 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 Permissions & Obligations Expression Working Group is expected to begin with 20 or more active participants and to sustain sufficient numbers to complete the multiple deliverables. 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 current 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-ole-comment/">public comment list</a>.</p>
<p>Information about the group (deliverables, participants, face-to-face meetings, teleconferences, etc.) is available from the P&OE 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.</p>
<p>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 id="licensing"><h2>Licensing</h2>
<p>This Working Group will use the <a href='http://www.w3.org/Consortium/Legal/copyright-software'>W3C Software and Document license</a> for all its deliverables.</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 Permissions & Obligations Expression Working Group has been created according to <a href="/2015/Process-20150901/#GroupsWG" shape="rect">section 5.2.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><a href="mailto:[email protected]">Phil Archer</a></address>
<p class="copyright"><a rel="Copyright" href="/Consortium/Legal/ipr-notice#Copyright" shape="rect">Copyright</a>
© 2016 <a href="/" shape="rect"><abbr title="World Wide Web Consortium">W3C</abbr></a> <sup>®</sup> (<a href="http://www.csail.mit.edu/" shape="rect"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.eu/" shape="rect"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></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>