forked from w3c/rdf-star-wg-charter
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
602 lines (509 loc) · 37 KB
/
index.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
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8">
<title>RDF-star Working Group Charter</title>
<link rel="stylesheet" href="https://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/OldGuide/pubrules-style.css">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css">
<style>
main {
max-width: 60em;
margin: 0 auto;
}
ul#navbar {
font-size: small;
}
dt.spec {
font-weight: bold;
}
dt.spec new {
background: yellow;
}
ul.out-of-scope > li {
font-weight: bold;
}
ul.out-of-scope > li > ul > li{
font-weight: normal;
}
.issue {
background: plum;
font-style: italic;
}
.todo {
color: #900;
}
footer {
font-size: small;
}
body {
background-image: url("data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 150 100' width='100%' height='50%' opacity='.06'> <g transform='translate(73,45) rotate(-40)'> <rect fill='none' stroke='red' stroke-width='2' width='120' x='-60' y='3' height='20' rx='10' ry='10'/> <text x='0' y='20' font-family='sans-serif' font-size='18' fill='red' text-anchor='middle'>Draft</text> </g> </svg>");
background-position: top center;
background-repeat: repeat;
}
</style>
</head>
<body>
<header id="header">
<aside>
<ul id="navbar">
<li><a href="#background">Background</a></li>
<li><a href="#scope">Scope</a></li>
<li><a href="#deliverables">Deliverables</a></li>
<li><a href="#success-criteria">Success Criteria</a></li>
<li><a href="#coordination">Coordination</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="#licensing">Licensing</a></li>
<li><a href="#about">About this Charter</a></li>
</ul>
</aside>
<p>
<a href="https://www.w3.org/"><img alt="W3C" height="48" src="https://www.w3.org/Icons/w3c_home" width="72"></a>
</p>
</header>
<main>
<h1 id="title">RDF-star Working Group Charter</h1>
<!-- delete PROPOSED after AC review completed -->
<div style="border: 1px solid darkred">
<p><strong>DRAFT</strong></p>
<p>This is a <em>draft</em> text, under development by the community. The goal is to, eventually, submit this draft charter proposal to an official W3C AC review.</p>
<p>Any text rendered like <span class=issue>this</span> refers to content that must be finalized before the charter is sent to AC review.</p>
<p>Any text rendered like <span class=todo>this</span> refers to content that must be updated when the final charter is published at the latest (e.g., adjusting hyperlinks).</p>
</div>
<p class="mission">The <strong>mission</strong> of the <a href=""><i>RDF-star</i> Working Group</a> is to <span class="issue">extend a set of RDF and SPARQL related recommendations, with the ability to concisely represent and query statements about statements.</span></p>
<div class="noprint">
<p class="join"><a href="https://www.w3.org/2004/01/pp-impl/XXXTODOXXX/join">Join the <i>RDF-star</i> Working Group.</a></p>
</div>
<p style="padding: 0.5ex; border: 1px solid green"> This proposed charter is available
on <a href="https://github.com/w3c/rdf-star-wg-charter">GitHub</a>.
Feel free to raise <a href="https://github.com/w3c/rdf-star-wg-charter/issues">issues</a>.
</p>
<div id="details">
<table class="summary-table">
<tr id="Duration">
<th>
Start date
</th>
<td>
<i class="todo">[dd monthname yyyy] (date of the "Call for Participation", when the charter is approved)</i>
</td>
</tr>
<tr id="CharterEnd">
<th>
End date
</th>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
<i class="todo">[chair name] (affiliation)</i>
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<span class="todo"><a href="mailto:[email protected]">Pierre-Antoine Champin</a></span> (0.1 <abbr title="Full-Time Equivalent">FTE</abbr>)
</td>
</tr>
<tr>
<th>
Meeting Schedule
</th>
<td>
<strong>Teleconferences:</strong> 1 hour calls to be held weekly; extra topic-specific calls may also be held
<br>
<strong>Face-to-face:</strong> face-to-face meetings may be scheduled by consent of the participants, usually no more than 3 per year.
</td>
</tr>
</table>
</div>
<section id="background" class="background issue">
<p>RDF-star (initially spelled RDF*) is an extension of RDF that was initially proposed by Olaf Hartig and Bryan Thompson in 2014, providing a concise way to make statements about statements.It has become quite popular, especially as a mean to provide interoperability between RDF and Property Graphs, and has been already implemented to various extent by <a href="https://w3c.github.io/rdf-star/implementations.html">a number of vendors and open-source libraries</a>. A <a href="https://w3c.github.io/rdf-star/">subgroup</a> of the <a href="https://www.w3.org/community/rdf-dev/">RDF-DEV Community Group</a> then formed to gather feedback, <a href="https://w3c.github.io/rdf-star/UCR/rdf-star-ucr.html">use-cases</a>, and explore the possibility of <a href="https://w3c.github.io/rdf-star/cg-spec/editors_draft.html">integrating RDF-star</a> into the existing RDF standards.</p>
</section>
<section id="scope" class="scope">
<h2>Scope</h2>
<p class="issue">The scope of this Working Group is to extend RDF 1.1 and SPARQL 1.1 with the features introduced by RDF-star. More precisely, RDF-star introduces the notion of <em>embedded triple</em> to express statements about statements. The abstract and concrete syntaxes of RDF and SPARQL are extended to support this new feature, as well as their respective semantics.</p>
<p class="issue">The community group has identified, in its <a href="https://w3c.github.io/rdf-star/cg-spec/">report</a>, which recommendations should be updated, and a possible path for updating them. The Working Group may however reconsider this and proceed differently from the Community Group. For every recommendation updated by this Working Group, the pending errata will also be addressed. The Working Group will also consider <a href="https://www.w3.org/2020/Process-20200915/#allow-new-features">allowing new features</a> in these recommendations, according to <a href="https://www.w3.org/2020/Process-20200915/#revised-rec-features">Section 6.2.11.4 of the W3C process</a>, in order to render future evolutions easier.</p>
<section id="section-out-of-scope">
<h3 id="out-of-scope">Out of Scope</h3>
<p>The following features are out of scope, and will not be addressed by this Working group.</p>
<ul class="out-of-scope">
<li>Adding other improvements or extendions to RDF or SPARQL. Given the number of recommendations that this Working Group needs to update, it is important to keep its scope very focused.</li>
</ul>
</section>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<p>Updated document status is available on the <a class="issue" href="https://www.w3.org/groups/wg/rdf-star/publications">group publication status page</a>.</p>
<p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval. <i>Reference</i> is to a (draft) specification used as an additional input to the work. <i>Expected completion</i> indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.</p>
<section id="normative">
<h3>
Normative Specifications
</h3>
<p>
The Working Group will deliver the following W3C normative specifications:
</p>
<section>
<h4>RDF family of specifications</h4>
<dl>
<dt id="rdf11-concepts" class="spec">RDF <span class="issue">1.2</span> Concepts and Abstract Syntax</dt>
<dd>
<p>This specification defines an abstract syntax (a data model) which serves to link all RDF-based languages and specifications. The abstract syntax has two key data structures: RDF graphs are sets of subject-predicate-object triples, where the elements may be IRIs, blank nodes, or datatyped literals. They are used to express descriptions of resources. RDF datasets are used to organize collections of RDF graphs, and comprise a default graph and zero or more named graphs. RDF 1.1 Concepts and Abstract Syntax also introduces key concepts and terminology, and discusses datatyping and the handling of fragment identifiers in IRIs within RDF graphs.</p>
<p class="draft-status"><b>Draft state:</b> Adopted from the <a href="https://www.w3.org/2011/rdf-wg/wiki/Main_Page">RDF WG</a></p>
<p><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2014/REC-rdf11-concepts-20140225/">RDF 1.1 Concepts and Abstract Syntax</a>, eds. Richard Cyganiak, David Wood, Markus Lanthaler, W3C Recommendation.</p>
<p class="draft-status"><b>Reference:</b> <a href="https://w3c.github.io/rdf-star/cg-spec/#concepts"><i class="todo">Section 2</i> of RDF-star and SPARQL-star</a>, eds. Olaf Hartig, Pierre-Antoine Champin, Gregg Kellogg, Andy Seaborne, W3C Draft Community Group Report, 2020. </p>
<p class="milestone"><b>Expected completion:</b> <i class="todo">WG-START + X months</i></p>
</dd>
<dt id="n-quads" class="spec">RDF <span class="issue">1.2</span> N-Quads</dt>
<dd>
<p>This specification defines a line-based, plain text format for encoding an RDF dataset.</p>
<p class="draft-status"><b>Draft state:</b> Adopted from the <a href="https://www.w3.org/2011/rdf-wg/wiki/Main_Page">RDF WG</a></p>
<p><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2014/REC-n-quads-20140225/">RDF 1.1 N-Quads</a>, ed. Gavin Carothers, W3C Recommendation.</p>
<p class="draft-status"><b>Reference:</b> <a href="https://w3c.github.io/rdf-star/cg-spec/#n-quads-star"><i class="todo">Section 3.4</i> of RDF-star and SPARQL-star</a>, eds. Olaf Hartig, Pierre-Antoine Champin, Gregg Kellogg, Andy Seaborne, W3C Draft Community Group Report, 2020. </p>
<p class="milestone"><b>Expected completion:</b> <i class="todo">WG-START + X months</i></p>
</dd>
<dt id="n-triples" class="spec">RDF <span class="issue">1.2</span> N-Triples</dt>
<dd>
<p>This specification defines a line-based, plain text format for encoding an RDF graph.</p>
<p class="draft-status"><b>Draft state:</b> Adopted from the <a href="https://www.w3.org/2011/rdf-wg/wiki/Main_Page">RDF WG</a></p>
<p><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2014/REC-n-triples-20140225/">RDF 1.1 N-Triples</a>, eds. Gavin Carothers, Andy Seaborne, W3C Recommendation.</p>
<p class="draft-status"><b>Reference:</b> <a href="https://w3c.github.io/rdf-star/cg-spec/#n-triples-star"><i class="todo">Section 3.3</i> of RDF-star and SPARQL-star</a>, eds. Olaf Hartig, Pierre-Antoine Champin, Gregg Kellogg, Andy Seaborne, W3C Draft Community Group Report, 2020. </p>
<p class="milestone"><b>Expected completion:</b> <i class="todo">WG-START + X months</i></p>
</dd>
<dt id="rdf11-mt" class="spec">RDF <span class="issue">1.2</span> Semantics</dt>
<dd>
<p>This specification defines a precise semantics for the Resource Description Framework and RDF Schema. It defines a number of distinct entailment regimes and corresponding patterns of entailment.</p>
<p class="draft-status"><b>Draft state:</b> Adopted from the <a href="https://www.w3.org/2011/rdf-wg/wiki/Main_Page">RDF WG</a></p>
<p><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2014/REC-rdf11-mt-20140225/">RDF 1.1 Semantics</a>, eds. Patrick J. Hayes, Peter F. Patel-Schneider, W3C Recommendation.</p>
<p class="draft-status"><b>Reference:</b> <a href="https://w3c.github.io/rdf-star/cg-spec/#rdf-star-semantics"><i class="todo">Section 6</i> of RDF-star and SPARQL-star</a>, eds. Olaf Hartig, Pierre-Antoine Champin, Gregg Kellogg, Andy Seaborne, W3C Draft Community Group Report, 2020. </p>
<p class="milestone"><b>Expected completion:</b> <i class="todo">WG-START + X months</i></p>
</dd>
<dt id="trig" class="spec">RDF <span class="issue">1.2</span> TriG</dt>
<dd>
<p>This specification defines a textual syntax for RDF called TriG that allows an RDF dataset to be completely written in a compact and natural text form, with abbreviations for common usage patterns and datatypes. TriG is an extension of the Turtle format.</p>
<p class="draft-status"><b>Draft state:</b> Adopted from the <a href="https://www.w3.org/2011/rdf-wg/wiki/Main_Page">RDF WG</a></p>
<p><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2014/REC-trig-20140225/">RDF 1.1 TriG</a>, eds. Gavin Carothers, Andy Seaborne, W3C Recommendation.</p>
<p class="draft-status"><b>Reference:</b> <a href="https://w3c.github.io/rdf-star/cg-spec/#trig-star"><i class="todo">Section 3.2</i> of RDF-star and SPARQL-star</a>, eds. Olaf Hartig, Pierre-Antoine Champin, Gregg Kellogg, Andy Seaborne, W3C Draft Community Group Report, 2020. </p>
<p class="milestone"><b>Expected completion:</b> <i class="todo">WG-START + X months</i></p>
</dd>
<dt id="turtle" class="spec">RDF <span class="issue">1.2</span> Turtle</dt>
<dd>
<p>This specification defines a textual syntax for RDF called Turtle that allows an RDF graph to be completely written in a compact and natural text form, with abbreviations for common usage patterns and datatypes. Turtle provides levels of compatibility with the N-Triples format as well as the triple pattern syntax of the SPARQL W3C Recommendation.</p>
<p class="draft-status"><b>Draft state:</b> Adopted from the <a href="https://www.w3.org/2011/rdf-wg/wiki/Main_Page">RDF WG</a></p>
<p><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2014/REC-turtle-20140225/">RDF 1.1 Turtle</a>, eds. Eric Prud'hommeaux, Gavin Carothers, W3C Recommendation.</p>
<p class="draft-status"><b>Reference:</b> <a href="https://w3c.github.io/rdf-star/cg-spec/#turtle-star"><i class="todo">Section 3.1</i> of RDF-star and SPARQL-star</a>, eds. Olaf Hartig, Pierre-Antoine Champin, Gregg Kellogg, Andy Seaborne, W3C Draft Community Group Report, 2020. </p>
<p class="milestone"><b>Expected completion:</b> <i class="todo">WG-START + X months</i></p>
</dd>
<dt id="rdf-syntax-grammar" class="spec">RDF <span class="issue">1.2</span> XML Syntax</dt>
<dd>
<p>This specification defines an XML syntax for RDF called RDF/XML in terms of Namespaces in XML, the XML Information Set and XML Base.</p>
<p class="draft-status"><b>Draft state:</b> Adopted from the <a href="https://www.w3.org/2011/rdf-wg/wiki/Main_Page">RDF WG</a></p>
<p><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2014/REC-rdf-syntax-grammar-20140225/">RDF 1.1 XML Syntax</a>, eds. Fabien Gandon, Guus Schreiber, W3C Recommendation.</p>
<p class="milestone"><b>Expected completion:</b> <i class="todo">WG-START + X months</i></p>
</dd>
<dt id="rdf-schema" class="spec">RDF Schema <span class="issue">1.2</span></dt>
<dd>
<p>This specification describes how to use RDF to describe RDF vocabularies. This specification defines a vocabulary for this purpose and defines other built-in RDF vocabulary initially specified in the RDF Model and Syntax Specification.</p>
<p class="draft-status"><b>Draft state:</b> Adopted from the <a href="https://www.w3.org/2011/rdf-wg/wiki/Main_Page">RDF WG</a></p>
<p><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2014/REC-rdf-schema-20140225/">RDF Schema 1.1</a>, eds. Dan Brickley, R.V. Guha, W3C Recommendation.</p>
<p class="draft-status"><b>Reference:</b> <a href="https://w3c.github.io/rdf-star/cg-spec/#rdf-star-vocabulary"><i class="todo">Section 7</i> of RDF-star and SPARQL-star</a>, eds. Olaf Hartig, Pierre-Antoine Champin, Gregg Kellogg, Andy Seaborne, W3C Draft Community Group Report, 2020. </p>
<p class="milestone"><b>Expected completion:</b> <i class="todo">WG-START + X months</i></p>
</dd>
</dl>
</section>
<section>
<h4>SPARQL family of specifications</h4>
<dl>
<dt id="sparql11-query" class="spec">SPARQL <span class="issue">1.2</span> Query Language</dt>
<dd>
<p>This specification defines the syntax and semantics of the SPARQL query language for RDF. SPARQL can be used to express queries across diverse data sources, whether the data is stored natively as RDF or viewed as RDF via middleware. SPARQL contains capabilities for querying required and optional graph patterns along with their conjunctions and disjunctions. SPARQL also supports aggregation, subqueries, negation, creating values by expressions, extensible value testing, and constraining queries by source RDF graph. The results of SPARQL queries can be result sets or RDF graphs.</p>
<p class="draft-status"><b>Draft state:</b> Adopted from the <a href="https://www.w3.org/2009/sparql/wiki/Main_Page">SPARQL (1.1) WG</a></p>
<p><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2013/REC-sparql11-query-20130321/">SPARQL 1.1 Query Language</a>, eds. Steve Harris, Andy Seaborne, W3C Recommendation.</p>
<p class="draft-status"><b>Reference:</b> <a href="https://w3c.github.io/rdf-star/cg-spec/#sparql-star"><i class="todo">Section 4</i> of RDF-star and SPARQL-star</a>, eds. Olaf Hartig, Pierre-Antoine Champin, Gregg Kellogg, Andy Seaborne, W3C Draft Community Group Report, 2020. </p>
<p class="milestone"><b>Expected completion:</b> <i class="todo">WG-START + X months</i></p>
</dd>
<dt id="sparql11-update" class="spec">SPARQL <span class="issue">1.2</span> Update</dt>
<dd>
<p>This specification defines an update language for RDF graphs. It uses a syntax derived from the SPARQL Query Language for RDF. Update operations are performed on a collection of graphs in a Graph Store. Operations are provided to update, create, and remove RDF graphs in a Graph Store.</p>
<p class="draft-status"><b>Draft state:</b> Adopted from the <a href="https://www.w3.org/2009/sparql/wiki/Main_Page">SPARQL (1.1) WG</a></p>
<p><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2013/REC-sparql11-update-20130321/">SPARQL 1.1 Update</a>, eds. Paula Gearon, Alexandre Passant, Axel Polleres, W3C Recommendation.</p>
<p class="draft-status"><b>Reference:</b> <a href="https://w3c.github.io/rdf-star/cg-spec/#sparql-star-update"><i class="todo">Section 5</i> of RDF-star and SPARQL-star</a>, eds. Olaf Hartig, Pierre-Antoine Champin, Gregg Kellogg, Andy Seaborne, W3C Draft Community Group Report, 2020. </p>
<p class="milestone"><b>Expected completion:</b> <i class="todo">WG-START + X months</i></p>
</dd>
<dt id="sparql11-results-json" class="spec">SPARQL <span class="issue">1.2</span> Query Results JSON Format</dt>
<dd>
<p>This specification defines a JSON format for the variable binding and boolean results formats provided by the SPARQL query language for RDF.</p>
<p class="draft-status"><b>Draft state:</b> Adopted from the <a href="https://www.w3.org/2009/sparql/wiki/Main_Page">SPARQL (1.1) WG</a></p>
<p><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2013/REC-sparql11-results-json-20130321/">SPARQL 1.1 Query Results JSON Format</a>, ed. Andy Seaborne, W3C Recommendation.</p>
<p class="draft-status"><b>Reference:</b> <a href="https://w3c.github.io/rdf-star/cg-spec/#sparql-star-query-results-json-format"><i class="todo">Section 4.7.1</i> of RDF-star and SPARQL-star</a>, eds. Olaf Hartig, Pierre-Antoine Champin, Gregg Kellogg, Andy Seaborne, W3C Draft Community Group Report, 2020. </p>
<p class="milestone"><b>Expected completion:</b> <i class="todo">WG-START + X months</i></p>
</dd>
<dt id="sparql11-results-xml" class="spec">SPARQL <span class="issue">1.2</span> Query Results XML Format</dt>
<dd>
<p>This specification defines an XML format for the variable binding and boolean results formats provided by the SPARQL query language for RDF.</p>
<p class="draft-status"><b>Draft state:</b> Adopted from the <a href="https://www.w3.org/2009/sparql/wiki/Main_Page">SPARQL (1.1) WG</a></p>
<p><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2013/REC-rdf-sparql-XMLres-20130321/">SPARQL Query Results XML Format (Second Edition)</a>, ed. Sandro Hawke, W3C Recommendation.</p>
<p class="draft-status"><b>Reference:</b> <a href="https://w3c.github.io/rdf-star/cg-spec/#sparql-star-query-results-xml-format"><i class="todo">Section 4.7.2</i> of RDF-star and SPARQL-star</a>, eds. Olaf Hartig, Pierre-Antoine Champin, Gregg Kellogg, Andy Seaborne, W3C Draft Community Group Report, 2020. </p>
<p class="milestone"><b>Expected completion:</b> <i class="todo">WG-START + X months</i></p>
</dd>
</dl>
</section>
</section>
<section id="ig-other-deliverables">
<h3>
Other Deliverables
</h3>
<p>
Other non-normative documents may be created such as:
</p>
<ul>
<li>Use case and requirement documents;</li>
<li>Test suite and implementation report for the specification;</li>
<li>Primer or Best Practice documents to support web developers when designing applications.</li>
</ul>
</section>
<section id="timeline">
<h3>Timeline</h3>
<p class="todo">Put here a timeline view of all deliverables.</p>
<ul class="todo">
<li>Month YYYY: First teleconference</li>
<li>Month YYYY: Requirements and Use Cases for FooML</li>
<li>Month YYYY: FPWD for FooML</li>
<li>Month YYYY: Requirements and Use Cases for BarML</li>
<li>Month YYYY: FPWD FooML Primer</li>
</ul>
</section>
</section>
<section id="success-criteria">
<h2>Success Criteria</h2>
<p>In order to advance to <a href="https://www.w3.org/Consortium/Process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, each normative specification is expected to have <a href="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent implementations</a> of every feature defined in the specification.</p>
<p>Each specification should contain separate sections detailing all known security and privacy implications for implementers, Web authors, and end users.</p>
<p>There should be testing plans for each specification, starting from the earliest drafts.</p>
<p>To promote interoperability, all changes made to specifications should have <a href='https://www.w3.org/2019/02/testing-policy.html'>tests</a>.</p>
</section>
<section id="coordination">
<h2>Coordination</h2>
<p>For all specifications, this Working Group will seek <a href="https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review">horizontal review</a> for
accessibility, internationalization, performance, privacy, and security with the relevant Working and
Interest Groups, and with the <a href="https://www.w3.org/2001/tag/" title="Technical Architecture Group">TAG</a>.
Invitation for review must be issued during each major standards-track document transition, including
<a href="https://www.w3.org/Consortium/Process/#RecsWD" title="First Public Working Draft">FPWD</a>. The
Working Group is encouraged to engage collaboratively with the horizontal review groups throughout development of
each specification. The Working Group is advised to seek a review at least 3 months before first entering
<a href="https://www.w3.org/Consortium/Process/#RecsCR" title="Candidate Recommendation">CR</a> and is encouraged
to proactively notify the horizontal review groups when major changes occur in a specification following a review.</p>
<p>Additional technical coordination with the following Groups will be made, per the <a href="https://www.w3.org/Consortium/Process/#WGCharter">W3C Process Document</a>:</p>
<section>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="https://www.w3.org/2017/dxwg/wiki/Main_Page">Data Exchange Working Group</a> (DXWG)</dt>
<dd>The work of the DXWG on Content Negociation by Profile has been identified as a way to improve interoperability between RDF-star-aware applications and legacy application that do not support its new features.</dd>
<dt><a href="https://www.w3.org/2018/json-ld-wg/">JSON-LD Working Group</a></dt>
<dd>As a concrete syntax for RDF datasets, JSON-LD may also be updated to support RDF-star. <a href="https://json-ld.github.io/json-ld-star/">A proposal</a> from the JSON-LD Community Group is already available.</dd>
</dl>
<p class="issue"><b>Note:</b> Do not list horizontal groups here, only specific WGs relevant to your work.</p>
<p class="issue"><b>Note:</b> Do not bury normative text inside the liaison section.
Instead, put it in the scope section.</p>
</section>
<section>
<h3 id="external-coordination">External Organizations</h3>
<dl>
<dt><a href=""><i class="todo">[other name]</i> Working Group</a></dt>
<dd><i class="todo">[specific nature of liaison]</i></dd>
</dl>
</section>
</section>
<section class="participation">
<h2 id="participation">
Participation
</h2>
<p>
To be successful, this Working Group is expected to have 6 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a working day per week towards the Working Group. There is no minimum requirement for other Participants.
</p>
<p>
The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in <a href='#communication'>Communication</a>.
</p>
<p>
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a>.
</p>
<p>Participants in the group are required (by the <a href="https://www.w3.org/Consortium/Process/#ParticipationCriteria">W3C Process</a>) to follow the
W3C <a href="https://www.w3.org/Consortium/cepc/">Code of Ethics and Professional Conduct</a>.</p>
</section>
<section id="communication">
<h2>
Communication
</h2>
<p id="public">
Technical discussions for this Working Group are conducted in <a href="https://www.w3.org/Consortium/Process/#confidentiality-levels">public</a>: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution requests.
The meetings themselves are not open to public participation, however.
</p>
<p>
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href=""><i>RDF-star</i> Working Group home page.</a>
</p>
<p>
Most <i>RDF-star</i> Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
</p>
<p>
This group primarily conducts its technical work on <a class="todo" id="public-github" href="https://github.com/w3c/rdf-star/">GitHub issues</a> or on the public mailing list <a id="public-name" href="mailto:[email protected]">[email protected]</a> (<a class="todo" href="https://lists.w3.org/Archives/Public/public-rdf-star/">archive</a>).
The public is invited to review, discuss and contribute to this work.
</p>
<p>
The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.
</p>
</section>
<section id="decisions">
<h2>
Decision Policy
</h2>
<p>
This group will seek to make decisions through consensus and due process, per the <a href="https://www.w3.org/Consortium/Process/#Consensus"> W3C Process Document (section 3.3</a>). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.</p>
<p>
However, if a decision is necessary for timely progress and consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote and record a decision along with any objections.
</p>
<p>
To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional.
A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based survey), with a response period from one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue.
If no objections are raised by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group.
</p>
<p>
All decisions made by the group should be considered resolved unless and until new information becomes available or unless reopened at the discretion of the Chairs or the Director.
</p>
<p>
This charter is written in accordance with the <a href="https://www.w3.org/Consortium/Process/#Votes">W3C Process Document (Section 3.4, Votes)</a> and includes no voting procedures beyond what the Process Document requires.
</p>
</section>
<section id="patentpolicy">
<h2>
Patent Policy
</h2>
<p>
This Working Group operates under the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a> (Version of 15 September 2020). To promote the widest adoption of Web standards, W3C seeks to issue Web specifications that can be implemented, according to this policy, on a Royalty-Free basis.
For more information about disclosure obligations for this group, please see the <a href="https://www.w3.org/2004/01/pp-impl/">W3C Patent Policy Implementation</a>.
</p>
</section>
<section id="licensing">
<h2>Licensing</h2>
<p>This Working Group will use the <a href="https://www.w3.org/Consortium/Legal/copyright-software">W3C Software and Document license</a> for all its deliverables.</p>
</section>
<section id="about">
<h2>
About this Charter
</h2>
<p>
This charter has been created according to <a href="https://www.w3.org/Consortium/Process/#WG-and-IG">section 5.2</a> of the <a href="https://www.w3.org/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>
<section id="history">
<h3>
Charter History
</h3>
<p>The following table lists details of all changes from the initial charter, per the <a href="https://www.w3.org/Consortium/Process/#CharterReview">W3C Process Document (section 5.2.3)</a>:</p>
<table class="history">
<tbody>
<tr>
<th>
Charter Period
</th>
<th>
Start Date
</th>
<th>
End Date
</th>
<th>
Changes
</th>
</tr>
<tr>
<th>
<a href="">Initial Charter</a>
</th>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<i>N/A</i>
</td>
</tr>
<!--
<tr>
<th>
<a class="todo" href="">Charter Extension</a>
</th>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<i class="todo">none</i>
</td>
</tr>
<tr>
<th>
<a class="todo" href="">Rechartered</a>
</th>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<p class="todo">[description of change to charter, with link to new deliverable item in charter] <b>Note:</b> use the class <code>new</code> for all new deliverables, for ease of recognition.</p>
</td>
</tr>
-->
</tbody>
</table>
</section>
<section id="changelog">
<h3>Change log</h3>
<!-- Use this section for changes _after_ the charter was approved by the Director. -->
<p>Changes to this document are documented in this section.</p>
<!--
<dl id='changes'>
<dt>YYYY-MM-DD</dt>
<dd>[changes]]</dd>
</dl>
-->
</section>
</section>
</main>
<hr>
<footer>
<address>
<a href="mailto:[email protected]">Pierre-Antoine Champin</a>
</address>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
2021
<a href="https://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
(
<a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
<a href="https://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="https://www.keio.ac.jp/">Keio</a>,
<a href="https://ev.buaa.edu.cn/">Beihang</a>
), All Rights Reserved.
<abbr title="World Wide Web Consortium">W3C</abbr> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
</p>
<hr>
<p><a href="https://github.com/w3c/rdf-star-wg-charter">Yes, it's on GitHub!</a>.</p>
</footer>
</body>
</html>