-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathvocab-du.html
2265 lines (2225 loc) · 85.5 KB
/
vocab-du.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
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html content="en" lang="en">
<head>
<meta content="text/html; charset=utf-8" http-equiv="content-type">
<title>Data on the Web Best Practices: Dataset Usage Vocabulary</title>
<meta name="description" content="A vocabulary to describe how datasets are used by humans and machines as well as to describe consumer feedback">
<script class="remove" src="http://www.w3.org/Tools/respec/respec-w3c-common">
</script>
<script class="remove">
var respecConfig = {
specStatus: "ED",
shortName: "vocab-duv",
//publishDate: "2016-08-30",
previousPublishDate: "2016-08-30",
previousMaturity: "WD",
previousURI: "http://www.w3.org/TR/2016/WD-vocab-duv-20160519/",
edDraftURI: "http://w3c.github.io/dwbp/vocab-du.html",
// lcEnd: "3000-01-01",
// crEnd: "3000-01-01",
editors: [{
name: "Bernadette Farias Lóscio",
company: "CIn - UFPE, Brazil",
companyURL: "http://www.cin.ufpe.br/"
},{
name: "Eric G. Stephan",
company: "Pacific Northwest National Laboratory",
companyURL: "http://www.pnnl.gov/"
}, {
name: "Sumit Purohit",
company: "Pacific Northwest National Laboratory",
companyURL: "http://www.pnnl.gov/"
}],
wg: "Data on the Web Working Group",
noRecTrack: true,
wgURI: "http://www.w3.org/2013/dwbp/",
wgPublicList: "public-dwbp-wg",
wgPatentURI: "https://www.w3.org/2004/01/pp-impl/68239/status",
otherLinks: [{
key: "Repository",
data: [{
value: "We are on Github",
href: "https://github.com/w3c/dwbp"
}]
}, {
key: "Changes",
data: [{
value: "Diff to previous version",
href: "diff-xxx.html"
}, {
value: "Commit history",
href: "https://github.com/w3c/dwbp/commits/gh-pages"
}]
}],
localBiblio: {
"BiRO" : {
title : "BiRO, the Bibliographic Reference Ontology",
href : " http://purl.org/spar/biro",
authors : ["David Shotton" , "Silvio Peroni"]
},
"CITO" : {
title : "CiTO, the Citation Typing Ontology",
href : " http://purl.org/spar/cito",
authors: ["David Shotton", "Silvio Peroni"]
},
"SPAR": {
title: " Semantic Publishing and Referencing (SPAR) Ontologies",
href: "http://www.sparontologies.net"
},
"FaBIO": {
title: "FaBiO, the FRBR-aligned Bibliographic Ontology",
href: "http://purl.org/spar/fabio",
authors: ["David Shotton", "Silvio Peroni"]
},
"MSUDataCite": {
title: "How to Cite Data: General Info",
href: "http://libguides.lib.msu.edu/citedata",
authors: ["Michigan State University"]
},
"BP": {
title: "Data on the Web Best Practices",
href: "https://www.w3.org/TR/dwbp/",
authors: ["Bernadette Farias Lóscio", "Caroline Burle", "Newton Calegari"]
},
"DWBP": {
title: "Data on the Web Best Practices",
href: "https://www.w3.org/2013/dwbp/wiki/Main_Page",
authors: ["W3C"]
},
"SCHEMA": {
title: "Schema.org",
href: "https://schema.org/",
authors: ["Dan Brickley"]
},
"REV": {
title: "RDF Review Vocabulary",
href: "http://vocab.org/review/terms.html"
},
"OKFN": {
title: "Open Knowledge Foundation (OKFN), Linked Open Vocabularies (LOV)",
href: "http://lov.okfn.org/dataset/lov/",
authors: ["Pierre-Yves Vandenbussche","Bernard Vatant"]
},
"FORCE11-Citation": {
title: "Data Citation Principles",
href: "https://www.force11.org/group/joint-declaration-data-citation-principles-final",
authors: ["Emory University"]
},
"OA": {
title: "Open Annotation Data Model",
href: "https://www.w3.org/ns/oa#",
authors: ["Herbert Van de Sompel", "Paolo Ciccarese", "Robert Sanderson"]
}
}
};
</script> <style type="text/css">
table {
border-collapse: collapse;
}
td, th {
border: 1px solid black;
padding: 1em;
}
table#namespaces td {
font-family: monospace;
}
table.definition {
width: 100%;
}
table.definition td.prop {
width: 10em;
}
/* .editorsnote::before {
content: "Editor's Note";
display: block;
width: 150px;
background: #F30023;
color: #fff;
margin: -1.5em 0 0.5em 0;
font-weight: bold;
border: 1px solid #cff6d9;
padding: 3px 1em;
}
.editorsnote {
margin: 1em 0em 1em 1em;
padding: 1em;
border: 2px solid #cff6d9;
} */
pre {
padding: 1em;
border: 1px dashed #2f6fab;
color: black;
background-color: #f9f9f9;
line-height: 1.1em;
}
pre red { color: red;
}
</style><!-- ttl to json-ld convertor begin -->
<style>
.todo {
color: red;
}
pre {
tab-size: 4;
}
th {
text-align: left;
}
.comment {
/* font-lock-comment-face */
color: #b22222;
}
.constant {
/* font-lock-constant-face */
color: #008b8b;
}
.function-name {
/* font-lock-function-name-face */
color: #0000ff;
}
.keyword {
/* font-lock-keyword-face */
color: #a020f0;
}
.string {
/* font-lock-string-face */
color: #8b2252;
}
.type {
/* font-lock-type-face */
color: #228b22;
}
.example {
display: inline-block;
}
.example.wrapper {
background-color: #fff;
}
.example.wrapper pre {
background-color: #fcfaee;
margin-left: 0;
line-height: 1.2;
}
.example.wrapper .fail {
background-color: #fceefa
}
.verticalDivider {
float: left;
width: .5em;
border:thin solid #fff; /* disappears without this */
}
.highlight1 { margin-left: -5px; margin-right: -5px; border-left: 5px solid rgba(176, 176, 0, .5); border-right: 5px solid rgba(176, 176, 0, .5); } /* font-weight: bold ; */
.highlight1.top { margin-top: -5px; border-top: 5px solid rgba(176, 176, 0, .5); } /* font-weight: bold ; */
.highlight1.bot { margin-bottom: -5px; border-bottom: 5px solid rgba(176, 176, 0, .5); } /* font-weight: bold ; */
.lowlight1 { margin-left: -5px; margin-right: -5px; border-left: 5px solid transparent; border-right: 5px solid transparent; } /* font-weight: normal; */
.lowlight1.top { margin-top: -5px; border-top: 5px solid transparent; } /* font-weight: normal; */
.lowlight1.bot { margin-bottom: -5px; border-bottom: 5px solid transparent; } /* font-weight: normal; */
.highlight2 { margin-left: -5px; margin-right: -5px; border-left: 5px solid rgba(176, 0, 176, .5); border-right: 5px solid rgba(176, 0, 176, .5); } /* font-weight: bold ; */
.highlight2.top { margin-top: -5px; border-top: 5px solid rgba(176, 0, 176, .5); } /* font-weight: bold ; */
.highlight2.bot { margin-bottom: -5px; border-bottom: 5px solid rgba(176, 0, 176, .5); } /* font-weight: bold ; */
.lowlight2 { margin-left: -5px; margin-right: -5px; border-left: 5px solid rgba(127, 127, 127, .07); border-right: 5px solid rgba(127, 127, 127, .07); } /* font-weight: normal; */
.lowlight2.top { margin-top: -5px; border-top: 5px solid rgba(127, 127, 127, .07); } /* font-weight: normal; */
.lowlight2.bot { margin-bottom: -5px; border-bottom: 5px solid rgba(127, 127, 127, .07); } /* font-weight: normal; */
.highlightBG1 { /* border: 5px solid transparent; */ background-color: #bb0; font-weight: bold; }
.lowlightBG1 { /* border: 5px solid transparent; */ font-weight: normal; }
.highlightBG2 { /* border: 5px solid transparent; */ background-color: #b00; font-weight: bold; }
.lowlightBG2 { /* border: 5px solid transparent; */ font-weight: normal; }
.new { font-weight: bold; }
.errorSite { color: red; }
</style>
<!--
<script src="http://www.w3.org/2013/ShEx/demobits/jquery.min.js" type= "text/javascript"></script> -->
<!-- That script libraray was causing a problem. Commenting it out seems to have fixed it. The T/J swicth still works ;-) -->
<!-- ttl to json-ld convertor end -->
</head>
<body>
<section id="abstract">
<p>Datasets published on the Web are accessed and experienced by consumers
in a variety of ways, but little information about these experiences is
typically conveyed. Dataset publishers many times lack feedback from
consumers about how datasets are used. Consumers lack an effective way
to discuss experiences with fellow collaborators and explore referencing
material citing the dataset. Datasets as defined by DCAT are a
collection of data, published or curated by a single agent, and
available for access or download in one or more formats. The Dataset
Usage Vocabulary (DUV) is used to describe consumer experiences,
citations, and feedback about the dataset from the human perspective. </p>
<p>By specifying a number of foundational concepts used to collect dataset
consumer feedback, experiences, and cite references associated with a
dataset, APIs can be written to support collaboration across the Web by
structurally publishing consumer opinions and experiences, and provide a
means for dataset consumers and producers advertise and search for
published open dataset usage. </p>
</section>
<section id="sotd">
<p>This is the fourth iteration of the vocabulary, developed following
extensive consultation among and outside the working group who now
regard it as nearing completion. Comment and feedback is sought before
the next iteration which is likely to be the final version for the
foreseeable future.</p>
</section>
<section id="intro" class="informative">
<h2> Introduction</h2>
<p> The Data on the Web Best Practices working group [[DWBP]] identified
Best Practices [[BP]] for citing published data, conveying feedback
between consumers and publishers, and providing descriptive metadata
that provides insights to the consumer about how published datasets can
be used. The dataset usage vocabulary is viewed as an extension to
the Data Catalog (DCAT) vocabulary version 1.0 [[VOCAB-DCAT]] to fill
current existing gaps required to adequately cite, describe usage, and
convey feedback on published datasets and
distributions. <br>
<br>
Broadly speaking the vocabulary is domain-independent and open. As
an open vocabulary the DUV encourages publishers to add descriptive
metadata tailored to meet each publisher’s domain-specific needs.
When publishers and consumers exchange, combine, and reuse published
data, the DUV metadata allows usage information to be clearly identified
and cross-referenced across datasets. Because the DUV heavily
relies on vocabulary reuse descriptive metadata in many cases can be
leveraged from original vocabulary. <br>
<br>
The DUV is modular consisting of four sub-models (DCAT, citation, usage,
feedback) to support different practitioner needs. As
a result the DUV can be used in part (DCAT+citation, DCAT+usage,
DCAT+feedback) or in its entirety depending on the practitioner’s
requirements. The DCAT+usage submodel is loosely defined to either
indicate usage from an informational perspective, or if descriptive
metadata is required, the usage submodel can indicate to find this
information. Additionally, the citation submodel describing basic
electronic citation elements, bibliographic references to dataset, and
citation rationale can be independently used.<br>
</p>
<!-- ttl to json-ld convertor begin -->
<form id="langOptions" action="#">View as: <label><input name="presLang"
value="turtle" checked="checked" type="radio">Turtle (press 't')</label>
<label><input name="presLang" value="json-ld" type="radio">JSON-LD
(press 'j')</label> . </form>
</section>
<section id="namespaces-1">
<h2> Namespaces</h2>
<p>The namespace for DUV is <code>http://www.w3.org/ns/duv#</code>. It
should be noted that DUV makes extensive use of terms from other
vocabularies which rely their own sets of namespaces. A full set of
namespaces and prefixes used in this document is shown in the table
below.</p>
<table id="namespaces">
<thead>
<tr>
<th>Prefix</th>
<th>Namespace</th>
</tr>
</thead>
<tbody>
<tr>
<td>biro</td>
<td>http://purl.org/spar/biro/</td>
</tr>
<tr>
<td>cito</td>
<td>http://purl.org/spar/cito/</td>
</tr>
<tr>
<td>dcat</td>
<td>http://www.w3.org/ns/dcat#</td>
</tr>
<tr>
<td>dct</td>
<td>http://purl.org/dc/terms/</td>
</tr>
<tr>
<td>disco</td>
<td>http://rdf-vocabulary.ddialliance.org/discovery#</td>
</tr>
<tr>
<td>dqv</td>
<td>http://www.w3.org/ns/dqv#</td>
</tr>
<tr>
<td>duv</td>
<td>http://www.w3.org/ns/duv#</td>
</tr>
<tr>
<td>fabio</td>
<td>http://purl.org/spar/fabio/</td>
</tr>
<tr>
<td>foaf</td>
<td>http://xmlns.com/foaf/0.1/</td>
</tr>
<tr>
<td>frbr</td>
<td>http://purl.org/vocab/frbr/core#</td>
</tr>
<tr>
<td>oa</td>
<td>http://www.w3.org/ns/oa#</td>
</tr>
<tr>
<td>pav</td>
<td> http://purl.org/pav/</td>
</tr>
<tr>
<td>rdf</td>
<td>http://www.w3.org/1999/02/22-rdf-syntax-ns#</td>
</tr>
<tr>
<td>rdfs</td>
<td>http://www.w3.org/2000/01/rdf-schema#</td>
</tr>
<tr>
<td>skos</td>
<td>http://www.w3.org/2004/02/skos/core#</td>
</tr>
<tr>
<td>vann</td>
<td>http://purl.org/vocab/vann/</td>
</tr>
<tr>
<td>xsd</td>
<td>http://www.w3.org/2001/XMLSchema#</td>
</tr>
</tbody>
</table>
</section>
<section id="audience">
<h2>Audience</h2>
<p>The <abbr title="Dataset Usage Vocabulary">DUV</abbr> is intended for
data producers and publishers interested in tracking, sharing, and
persisting consumer dataset usage. It is also intended for collaborators
who require an exchange medium to advertise and interactively convey
dataset usage. </p>
</section>
<section id="scope">
<h2>Scope</h2>
<p> The scope of the <abbr title="Dataset Usage Vocabulary">DUV</abbr>
is defined by the Data on the Web Best Practices (DWBP) Use Case
document [[DWBP-UCR]] based on the data usage requirements about
datasets. These requirements include: citing datasets on the Web,
tracking the usage of datasets, sharing feedback and rating datasets.
These requirements were derived from fourteen real world use cases
examples provided in the use case document. </p>
</section>
<section id="relationship_vocabularies">
<h2> Relationship to other Vocabularies</h2>
<h3>Vocabulary Reuse</h3>
<p>Based on DWBP the <abbr title="Dataset Usage Vocabulary">DUV</abbr>
heavily relies upon is vocabulary reuse to support citation, feedback,
and usage of datasets published on the Web. This section provides our
rationale and approach for vocabulary selection and reuse.</p>
<p>The core DUV begins with reusing the Data Catalog Vocabulary
[[VOCAB-DCAT]] <code>dcat:Dataset</code> and <code>dcat:Distribution</code>
classes and many of their related properties. In fact, the
DUV can be considered an extension of <code>the dcat:Dataset and </code><code>dcat:Distribution</code>
classes. </p>
<p>The Web Annotation Vocabulary [[OA]] is used to describe <code>duv:Feedback</code>
as a subclass inheriting the behavior of <code>oa:Annotation</code>.
The intent for the <code>duv:Feedback</code> is provided by the <code>oa:motivated_by</code>
property and <code>oa:Motivation</code> subclasses (for example: <code>oa:describing</code>,
<code>oa:questioning</code>, <code>oa:replying</code>). A subset of the
Motivation instances are important to describe feedback to data
publishers, and blogs between dataset consumers. In addition to
supporting <code>duv:Feedback</code>, because the Web Annotation
vocabulary provides a generic way of annotating any Web resource, it is
recommended that Web Annotation vocabulary be used to annotate the <code>dcat:Dataset</code>
for uses beyond the scope of the DUV. </p>
<p> The Semantic Publishing and Referencing [[SPAR]] Ontologies provides a
suite of vocabularies used to related entities to reference citations,
bibliographic records, and describe the publication process along with
other related activities. The DUV directly relies upon the FRBR-aligned
Bibliographic Ontology [[FaBIO]], and Dublin Core [[DC-TERMS]]
ontologies are used to describe citations and references between
datasets and cited sources. In addition to ontologies the research
community provided basic criteria for citing data on the Web
[[MSUDataCite]]. These resources helped scope the DUV citation model
into the minimal requirements for electronic dataset publication.
Finally, data citation principles being adopted [[FORCE11-Citation]] are
also being considered to ensure the DUV is consistent with guidelines
developed by other data citation communities.</p>
<h3>Alternative Vocabulary Considerations </h3>
<p>As discussed earlier, the intention of the DUV is to be thorough enough
to offer a starting point for describing dataset usage and yet be open
to using other alternative classes and properties as required by
developers. For example, duv:Feedback the subclass of
oa:Annotation reuses the object property oa:hasBody. While the [[OA]]
uses oa:TextualBody as a means to capture textual information, however
what if needed to capture feedback in alternative ways, it is highly
suggested spending time exploring resources such as the Open Knowledge
Foundation, Linked Open Vocabularies [[OKFN]] such as using the Review
vocabulary [[REV]]. This vocabulary features a very lightweight
way to specify ratings. <br>
<br>
While the focus of this document is mainly on representing the DUV using
semantic expressions, a very active effort Schema.org [[SCHEMA]]
provides lightweight data structures that can be used as markup that
commercial search engines recognize, aiding in discovery. Not only
do Schema.org and the DUV rely on many related concepts, efforts are
underway to extend the Schema.org to support additional data structures.</p>
</section>
<section id="Vocab_Overview">
<h2>Vocabulary Overview</h2>
<p>This section depicts the vocabulary in its entirety as a conceptual
model. Boxes are used to identify each class. Labeled open arrows
identify object and literal properties. White arrowheads depict class
inheritance with the parent class identified by the arrowhead.
Please note that while most of the properties are reused from other
vocabularies, they are included in the diagram to (1) reduce the
learning curve required by DUV implementers that would otherwise be
spent constantly referencing to third party vocabularies and (2) provide
a starting place to familiarize DUV implementers with the basics needed
to get them started. </p>
<a href="images/DUV_model.png"><img src="images/DUV_model.png" style="width:80%; vertical-align: bottom"
alt="The class diagram for DUV"></a>
<section id="Citation_Model">
<h3>Citation Model</h3>
<p>The citation model was motivated by the UCR requirement <a href="http://www.w3.org/TR/dwbp-ucr/#R-Citable">
R-Citable </a><em> It should be possible to cite data on the Web.</em>
The citation model is largely based on classes, properties, and
recommended approaches taken from the SPAR Ontologies.
<!--The remainder
of the model is composed from the Open Annotation vocabulary, Dublin Core, FOAF and by newly introduced DUV properties. --></p>
<p>The citation model seeks to meet the needs of:</p>
<ol>
<li>Data consumers who cite published <code>dcat:Dataset</code> and <code>dcat:Distribution</code>
<a href="#ex1">(See Example 1)</a> by using basic bibliographic
reference criteria provided by the data publisher. To do
this, DUV extensions are added to the DCAT model in two ways:
First because <code>dcat:Dataset</code> or <code>dcat:Distribution</code>
are forms of electronic media that can be potentially cited, both
use the same citation properties. Secondly, to fill any
information gaps, new properties were created or properties from
other vocabularies were added.
<p> </p>
<p> <a href="images/DUV_citation_submodel_part_1.png"><img src="images/DUV_citation_submodel_part_1.png"
style="width:50%; vertical-align: bottom" alt="The class diagram for the citation DUV"></a>
</p>
<p>The table below shows how a portion of the DUV properties can be
used to form a bibliographic reference. </p>
<table style="width: 70%;" border="2">
<tbody>
<tr>
<td><span style="font-weight: bold;">Bibliographic Field</span></td>
<td><span style="font-weight: bold;">Definition</span></td>
<td><span style="font-weight: bold;">Property used in DUV</span></td>
</tr>
<tr>
<td>Author(s)</td>
<td>An individual, a group of individuals, or an organization
responsible for creating the dataset or distribution.</td>
<td>dct:creator</td>
</tr>
<tr>
<td>Title</td>
<td>Name of the dataset or distribution or the name of the
activities that produced the data.</td>
<td>dct:title</td>
</tr>
<tr>
<td>Year</td>
<td>When data was produced.</td>
<td>dct:created</td>
</tr>
<tr>
<td>Publisher</td>
<td>This may be the name of the archive where it is housed or
the organization responsible for performing publication
services.</td>
<td>dct:publisher</td>
</tr>
<tr>
<td>Distributor (if used)</td>
<td>Organization that makes the dataset available for
downloading and use </td>
<td>duv:hasDistributor</td>
</tr>
<tr>
<td>Edition or version</td>
<td>Edition or version number associated with the dataset</td>
<td>pav:version </td>
</tr>
<tr>
<td>Access information (a URL or other persistent identifier).
</td>
<td>Web address of dataset or distribution, or persistent
identifier such as digital object identifier (DOI). </td>
<td>dct:identifier<br>
</td>
</tr>
</tbody>
</table>
<p><br>
Extracting metadata from the properties in <a href="#ex1">example
1</a>, it is possible to form the following example reference:</p>
<table>
<tbody>
<tr>
<td>
<p><span style="font-style: italic;">dct:creator + .
+ dct:title + pav:version </span>+ . + <span style="font-style: italic;">dct:publisher
</span>+ [. +<span style="font-style: italic;">
duv:hasDistributor</span> + ] . + <span style="font-style: italic;">dct:identifier</span></p>
<p>MyCity Bus Association. Bus stops of MyCity. 1.0 version.
Transport Agency, 2015 [publisher,distributor].
doi:10.0902/1975.16</p>
</td>
</tr>
</tbody>
</table>
<p> </p>
</li>
<li>Data publishers wanting to annotate <code>dcat:Dataset</code>/<code>dcat:Distribution</code>
with bibliographic references that provide data additional insights
to data consumers <a href="#ex2">(See Example 2)</a>. Data
publishers can also annotate a dataset or distribution with
bibliographic references provided by data consumers <a href="#ex2">(See
Example 3)</a>. For example, a researcher uses a dataset for
performing some experiments and then publishes a paper with the
experimentation's results. The dataset can be annotated with the
bibliographic reference of this paper. include: <code>dcat:Dataset</code>,
<code>dcat:Distribution</code>, <code>biro:BibliographicReference</code>,
<code>fabio:Expression</code>. Properties include: <code><code>frbr:part</code>,frbr:partOf</code>,
<code>biro:references</code>, <code>biro:isReferencedBy</code>.
<p> <a href="images/DUV_citation_submodel_part_2.png"><img src="images/DUV_citation_submodel_part_2.png"
style="width:25%; vertical-align: bottom" alt="The class diagram for the citation DUV"></a></p>
</li>
</ol>
<p>Note that while the DUV reuses a limited set of [[SPAR]] classes and
properties to support basic [[VOCAB-DCAT]] dataset and distribution
citation requirements, the [[SPAR]] ontologies have a richer set of
classes and properties for more advanced representations. For example
[[FaBIO]] <code>fabio:Expression</code> class has many subclasses
(e.g. <code>fabio:Policy</code>) that help characterize referenced
material. </p>
<ol>
</ol>
</section>
<section id="Usage_Model">
<h3>Usage Model</h3>
<p>The usage model was motivated by the UCR requirement <a href="http://www.w3.org/TR/dwbp-ucr/#R-Citable">
R-TrackDataUsage </a> <em>It should be possible to track the usage
of data.</em> Sharing and tracking dataset usage can help enhancing
the utility of the datasets by providing help describing how the
datasets can be used by a consumer <a href="#ex5">(See Example 5)</a>.
Usage could be considered as enabling <span style="font-style: italic;">descriptive</span>
information provided by the data publisher to help the consumer
community make use of datasets and distributions. Based on the use
cases, data usage can help provide guidance information about how to
use the dataset and tools <a href="#ex6">(See Example 6)</a> that
can be used with the dataset. As also stipulated by use cases is the
need to track usage metrics </p>
<p>The following classes constitute the Usage Model: <code>dcat:Dataset</code>,
<code>dcat:Distribution</code>, <code>duv:Usage</code>, <code>duv:UsageTool</code><code></code>.
Properties include: <code>duv:hasUsage</code>, <code>duv:hasUsageTool</code><code></code>,
<code>duv:refersTo</code>, <code>dct:identifier</code>, <code>dct:title</code>,
<code>dct:created</code>, <code>pav:version</code>, <code>dct:issued</code>,
and <code>dct:description</code>. </p>
<a href="images/DUV_usage_submodel.png"><img src="images/DUV_usage_submodel.png"
style="width:50%; vertical-align: bottom" alt="The class diagram for the DUV usage submodel"></a>
</section>
<section id="Feedback_Model">
<h3>Feedback Model</h3>
<p> The feedback model was motivated by UCR requirement <a href="http://www.w3.org/TR/dwbp-ucr/#R-UsageFeedback">R-UsageFeedback</a><em>
Data consumers should have a way of sharing feedback and rating data
<a href="#ex4">(See Example 4)</a> . </em>User feedback is
important to address data quality concerns about published dataset.
Different users may have different experiences with the same dataset
so it is important to capture the context in which data was used and
the profile of the user who uses it. <a href="http://www.w3.org/TR/dwbp-ucr/#R-UsageFeedback">R-UsageFeedback</a>
should also provide a way for consumers to communicate suggested
corrections or advice back to the dataset publisher. </p>
<a href="images/DUV_feedback_submodel.png"><img src="images/DUV_feedback_submodel.png"
style="width:50% ; vertical-align: bottom" alt="The class diagram for the DUV feedback submodel"></a>
<p>The following classes constitute the Feedback Model: <code>dcat:Dataset</code>,
<code>dcat:Distribution</code>, <code>oa:Annotation</code>, <code>oa:Motivation</code>,
<code>duv:UserFeedback</code>, <code>dqv:UserQualityFeedback</code>,
<code>duv:RatingFeedback</code>, <code>oa:TextualBody</code>.
Properties include: <code><code>duv:hasFeedback</code>, <code></code>duv:hasRating</code>,
<code>oa:hasTarget</code>, <code>oa:hasBody</code>,<code></code> <code>oa:motivatedBy</code><code></code>.
</p>
</section>
</section>
<!--<div class="note">This section will be non-normative and will contain links
back to the vocabularies we mention. </div> -->
<section id="vocabulary-specification">
<h2> Vocabulary Specification </h2>
<section id="class-ratingfeedback">
<h3> Class: RatingFeedback</h3>
<table class="definition">
<thead>
<tr>
<th>RDF Class:</th>
<th><a href="#class-ratingfeedback">duv:RatingFeedback</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition</td>
<td>Predefined criteria used to express a user opinion about a
dataset or distribution using a discrete range of values.</td>
</tr>
<tr>
<td class="prop">rdfs:isDefinedBy</td>
<td><a href="http://www.w3.org/ns/duv">http://www.w3.org/ns/duv</a></td>
</tr>
<tr>
<td>Label</td>
<td>rating feedback</td>
</tr>
<tr>
<td>rdfs:subClassOf</td>
<td><a href="#class-userFeedback">duv:UserFeedback</a></td>
</tr>
</tbody>
</table>
</section>
<section id="class-usage">
<h3>Class: Usage</h3>
<table class="definition">
<thead>
<tr>
<th>RDF Class:</th>
<th><a href="#class-usage">duv:Usage</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition</td>
<td>Actions that can be performed on a given dataset or
distribution.</td>
</tr>
<tr>
<td class="prop">rdfs:isDefinedBy</td>
<td><a href="http://www.w3.org/ns/duv">http://www.w3.org/ns/duv</a></td>
</tr>
<tr>
<td>Label</td>
<td>usage</td>
</tr>
</tbody>
</table>
</section>
<section id="class-usageTool">
<h3>Class: UsageTool</h3>
<table class="definition">
<thead>
<tr>
<th>RDF Class:</th>
<th><a href="#class-usageTool">duv:UsageTool</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition</td>
<td>A tool that can use a dataset or distribution.<br>
</td>
</tr>
<tr>
<td class="prop">rdfs:isDefinedBy</td>
<td><a href="http://www.w3.org/ns/duv">http://www.w3.org/ns/duv</a></td>
</tr>
<tr>
<td>Label</td>
<td>usage tool<br>
</td>
</tr>
</tbody>
</table>
</section>
<section id="class-userFeedback">
<h3>Class: UserFeedback</h3>
<table class="definition">
<thead>
<tr>
<th>RDF Class:</th>
<th><a href="#class-userFeedback">duv:UserFeedback</a> </th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition</td>
<td>User feedback on a dataset or distribution.</td>
</tr>
<tr>
<td>Label</td>
<td>user feedback</td>
</tr>
<tr>
<td>rdfs:subClassOf</td>
<td> <a href="http://www.w3.org/ns/oa#d4e434">oa:Annotation</a></td>
</tr>
</tbody>
</table>
</section>
<section id="Properties">
<h3>Properties</h3>
<!--<h4 aria-level="3" id="Property:chars">Property: chars</h4>
<table class="definition"> <thead> <tr> <th>RDF Property:</th> <th> <a href="#Property:chars">cnt:chars</a> </th> </tr> </thead> <tbody> <tr> <td class="prop">Definition</td> <td>Text content of an annotation body.</td> </tr> <tr> <td>vann:usageNote</td> <td>cnt:ContentAsText (subject) cnt:chars (predicate) rdfs:Literal (object)</td> </tr> <tr> <td>Label</td> <td>chars</td> </tr> </tbody> </table> -->
<h4 aria-level="3" id="Property:created">Property: created</h4>
<table class="definition">
<thead>
<tr>
<th>RDF Property:</th>
<th> <a href="#Property:created">dct:created</a> </th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition</td>
<td> <span style="font-family: Verdana,Arial,"Arial Unicode MS",Helvetica,sans-serif;"></span>Date
of creation of the resource</td>
</tr>
<tr>
<td>vann:usageNote</td>
<td>dcat:Dataset (subject) dct:created (predicate) rdfs:Literal
(object)<br>
dcat:Distribution (subject) dct:created (predicate) rdfs:Literal
(object)</td>
</tr>
<tr>
<td>Label</td>
<td>created</td>
</tr>
</tbody>
</table>
<h4 aria-level="3" id="Property:creator"> Property: creator </h4>
<table class="definition">
<thead>
<tr>
<th>RDF Property:</th>
<th><a href="#Property:creator">dct:creator</a> </th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition</td>
<td>An entity primarily responsible for making the resource.
</td>
</tr>
<tr>
<td>vann:usageNote</td>
<td>dcat:Dataset (subject) dct:creator (predicate) foaf:Agent
(object)<br>
dcat:Distribution (subject) dct:creator (predicate) foaf:Agent
(object)</td>
</tr>
<tr>
<td>Label</td>
<td>creator</td>
</tr>
</tbody>
</table>
<h4 aria-level="3" id="Property:description"> Property: description </h4>
<table class="definition">
<thead>
<tr>
<th>RDF Property:</th>
<th><a href="#Property:description">dct:description</a> </th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition</td>
<td>A free text account of the resource </td>
</tr>
<tr>
<td>vann:usageNote</td>
<td>duv:Usage (subject) dct:description (predicate) rdfs:Literal
(object)<br>
duv:UsageTool (subject) dct:description (predicate) rdfs:Literal
(object)</td>
</tr>
<tr>
<td>Label</td>
<td>description</td>
</tr>
</tbody>
</table>
<h4 aria-level="3" id="Property:fundedBy">Property: fundedBy</h4>
<table class="definition">
<thead>
<tr>
<th>RDF Property:</th>
<th><a href="http://rdf-vocabulary.ddialliance.org/discovery.html">disco:fundedBy</a>
</th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition</td>
<td>The agent (person, organization) responsible for sponsoring
the dataset/distribution research that made the creation of the
dataset possible, such as codifying and digitizing the data. </td>
</tr>
<tr>
<td>vann:usageNote</td>
<td><br>
dcat:Dataset (subject) disco:fundedBy (predicate) foaf:Agent
(object)<br>
dcat:Distribution (subject) fundedBy (predicate) foaf:Agent
(object)</td>
</tr>
<tr>
<td>Label</td>
<td>funded by</td>
</tr>
</tbody>
</table>
<h4 id="Property:hasbody">Property: oa:hasBody</h4>
<table class="definition">
<thead>
<tr>
<th>RDF Property:</th>
<th><a href="#Property:hasbody">oa:hasBody</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition</td>
<td>Body of the comment associated with user feedback.</td>
</tr>
<tr>
<td>vann:usageNote</td>
<td>duv:UserFeedback (subject) oa:hasBody (predicate)
(object)<br>
oa:Annotation (subject) oa:hasBody (predicate)
oa:TextualBody(object)</td>
</tr>
<tr>
<td>Label</td>
<td>has body</td>
</tr>
</tbody>
</table>
<h4 id="Property:hasDistributor" aria-level="3">Property:
hasDistributor</h4>
<table class="definition">
<thead>
<tr>
<th>RDF Property:</th>
<th><a href="#Property:hasDistributor">duv:hasDistributor</a> </th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition</td>
<td>The distributor is the organization that makes the dataset or
distribution available for downloading and use.</td>
</tr>
<tr>
<td>vann:usageNote</td>
<td>dcat:Dataset (subject) duv:hasDistributor (predicate)
foaf:Agent (object)<br>
dcat:Distribution (subject) duv:hasDistributor (predicate)
foaf:Agent (object) </td>
</tr>
<tr>
<td>Label</td>
<td>has distributor</td>
</tr>
</tbody>
</table>
<h4 id="Property:hasrating" aria-level="3">Property: hasRating</h4>
<table class="definition">
<thead>
<tr>
<th>RDF Property:</th>
<th><a href="#Property:hasrating">duv:hasRating</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition</td>
<td>RatingFeedback has rating opinion</td>
</tr>
<tr>
<td>vann:usageNote</td>
<td>duv:RatingFeedback (subject) duv:hasRating (predicate)
skos:Concept (object)</td>
</tr>
<tr>
<td>Label</td>
<td>has rating</td>
</tr>
</tbody>
</table>
<h4 id="Property:hastarget" aria-level="3">Property: oa:hasTarget</h4>
<table class="definition">
<thead>
<tr>
<th>RDF Property:</th>
<th><a href="#Property:hastarget">oa:hasTarget</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition</td>
<td>Dataset or distribution associated with UserFeedback. </td>
</tr>
<tr>
<td>vann:usageNote</td>
<td>duv:UserFeedback (subject) oa:hasTarget (predicate)
dcat:Dataset (object)<br>
duv:UserFeedback (subject) oa:hasTarget (predicate)
dcat:Distribution (object)</td>
</tr>
<tr>
<td>Label</td>
<td>has target</td>
</tr>
</tbody>
</table>
<br>
<h4 aria-level="3" id="Property:hasusage">Property: hasUsage</h4>
<table class="definition">
<thead>
<tr>
<th>RDF Property:</th>
<th><a href="#Property:hasusage">duv:hasUsage</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition</td>
<td>Dataset or distribution usage guidance/instructions. </td>
</tr>
<tr>
<td>vann:usageNote</td>
<td>dcat:Dataset (subject) oa:hasUsage(predicate) duv:Usage
(object)<br>