forked from w3c/dwbp
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathvocab-dqg.html
2940 lines (2685 loc) · 148 KB
/
vocab-dqg.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>
<head>
<title>Data on the Web Best Practices: Data Quality Vocabulary</title>
<meta charset='utf-8'>
<script src="https://www.w3.org/Tools/respec/respec-w3c-common"
class="remove">
</script>
<script class='remove'>
var respecConfig = {
// specification status (e.g. WD, LC, WG-NOTE, etc.). If in doubt use ED.
specStatus : "ED",
//specStatus: "CR",
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName : "vocab-dqv",
// if your specification has a subtitle that goes below the main
// formal title, define it here
// subtitle : "an excellent document",
// if you wish the publication date to be other than today, set this
publishDate : "2016-04-15",
// prEnd: "2014-01-12",
// lcEnd: "2013-11-26",
// crEnd: "2013-11-26",
// if the specification's copyright date is a range of years, specify
// the start date here:
//copyrightStart : "2014",
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
previousPublishDate : "2015-06-25",
//previousPublishDate: "2013-08-01",
previousMaturity : "FPWD",
//previousMaturity: "CR",
previousURI : "http://www.w3.org/TR/2015/WD-vocab-dqv-20150625/",
// if there a publicly available Editor's Draft, this is the link
edDraftURI : "http://w3c.github.io/dwbp/vocab-dqg.html",
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2013-09-06",
// if there is an earler version of this specification at the Recommendation level,
// set this to the shortname of that version. This is optional and not usually
// necessary.
// prevRecShortname: "rdf-concepts",
// editors, add as many as you like
// only "name" is required
editors : [ {
name : "Riccardo Albertoni",
url : "mailto:[email protected]",
company : "CNR - Consiglio Nazionale delle Ricerche, Italy",
companyURL : "http://www.cnr.it/"
}, {
name : "Antoine Isaac",
url : "mailto:[email protected]",
company : "VU University Amsterdam and Europeana, The Netherlands",
companyURL : "http://www.vu.nl/"
},
],
otherLinks : [ {
key : "Contributors",
data : [ {
value : "Jeremy Debattista"
}, {
value : "Makx Dekkers"
}, {
value : "Christophe Guéret"
},{
value : "Deirdre Lee"
}, {
value : "Nandana Mihindukulasooriya"
},
{
value : "Amrapali Zaveri"
}
]
}, {
key : "Other locations",
data : [ {
value : "We are on Github",
href : "https://github.com/w3c/dwbp"
}, {
value : "Wiki pages",
href : "https://www.w3.org/2013/dwbp/wiki/Data_quality_notes"
} ]
}, {
key : "Changes",
data : [ {
value : "Change History",
href : "#change-history"
}, {
value : "Diff to previous version",
href : "http://w3c.github.io/dwbp/diffs/dqvdiff-20151214.html"
} ]
} ],
// name of the WG
wg : "Data on the Web Best Practices Working Group",
// URI of the public WG page
wgURI : "http://www.w3.org/2013/dwbp/",
// name (WITHOUT the @w3.org) of the public mailing to which comments are due
wgPublicList : "public-dwbp-comments",
noRecTrack : true,
// URI of the patent status for this WG, for Rec-track documents
// !!!! IMPORTANT !!!!
// This is important for Rec-track documents, do not copy a patent URI from a random
// document unless you know what you're doing. If in doubt ask your friendly neighbourhood
// Team Contact.
wgPatentURI : "http://www.w3.org/2004/01/pp-impl/68239/status",
// if this parameter is set to true, ReSpec.js will embed various RDFa attributes
// throughout the generated specification. The triples generated use vocabulary items
// from the dcterms, foaf, and bibo. The parameter defaults to false.
doRDFa : "1.1",
//alternateFormats : [ {
// uri : "diff-20131105.html",
// label : "diff to previous version"
//} ],
// implementationReportURI: "http://www.w3.org/2011/gld/wiki/DCAT_Implementations",
maxTocLevel : 2,
localBiblio : {
"CC-VOCAB" : {
title : "Creative Commons Rights Expression Language",
href : "http://creativecommons.org/ns"
},
"DaQ" : {
title : "daQ, an Ontology for Dataset Quality Information",
authors : [ "Jeremy Debattista", "Christoph Lange",
"Sören Auer" ],
date : "2014",
status : "LDOW 2014",
href : "http://ceur-ws.org/Vol-1184/ldow2014_paper_09.pdf"
},
"DaQ-RDFCUBE" : {
title : "Representing dataset quality metadata using multi-dimensional views",
authors : [ "Jeremy Debattista", "Christoph Lange",
"Sören Auer" ],
date : "2014",
status : "SEMANTICS 2014",
href : "http://arxiv.org/abs/1408.2468"
},
"MultilingualImporting" : {
title : "A Linkset Quality Metric Measuring Multilingual Gain in SKOS Thesauri",
authors : [ "Riccardo Albertoni", "Monica De Martino",
"Paola Podestà" ],
date : "2015",
status : "LDQ@ESWC 2015",
href : "http://ceur-ws.org/Vol-1376/LDQ2015_paper_01.pdf"
},
"GeoDCAT-AP" : {
title : "GeoDCAT-AP: A geospatial extension for the DCAT application profile for data portals in Europe",
authors : [ "ISA Programme" ],
date : "23 December 2015",
status : "Version 1.0",
href : "https://joinup.ec.europa.eu/asset/dcat_application_profile/asset_release/geodcat-ap-v10"
},
"ZaveriEtAl" : {
title : "Quality assessment for Linked Data: A Survey",
authors : [ "Amrapalia Zaveri", "Anisa Rula", "Andrea Maurino",
"Ricardo Pietrobon", "Jens Lehmann", "Sören Auer" ],
status : "Semantic Web, vol. 7, no. 1, pp. 63-93, 2015",
href : "https://dx.doi.org/10.3233/SW-150175"
},
"ISOIEC25012" : {
title : "ISO/IEC 25012 - Data Quality model",
href : "http://iso25000.com/index.php/en/iso-25000-standards/iso-25012"
},
"qSKOS" : {
title : "Finding Quality Issues in SKOS Vocabularies",
authors : [ "Christian Mader", "Bernhard Haslhofer",
"Antoine Isaac" ],
status : "Theory and Practice of Digital Libraries, Lecture Notes in Computer Science, Vol. 7489, pp 222-233",
date : "2012",
href : "https://dx.doi.org/10.1007/978-3-642-33290-6_25"
},
"SHACL" : {
title : "Shapes Constraint Language (SHACL)",
authors : [ "Holger Knublauch", "Arthur Ryman" ],
date : "28 January 2016",
status : "W3C Working Draft",
href : "https://www.w3.org/TR/shacl/"
},
"ODRL" : {
title : "ODRL Version 2.1 Core Model",
authors : [ "Renato Iannella","Susanne Guth","Daniel Paehler","Andreas Kasten" ],
date : "5 March 2015",
status : "W3C Community Group Specification",
href : "https://www.w3.org/community/odrl/model/2.1/"
},
"RijgersbergEtAl": {
title: "Ontology of units of measure and related concepts",
authors: ["Hajo Rijgersberg", "Mark van Assem","Jan L. Top"],
status : "Semantic Web, vol. 4, no. 1, pp. 3-13, 2013",
href : "https://dx.doi.org/10.3233/SW-2012-0069"
},
"Vocab-Data-Cube": {
title: "The RDF Data Cube Vocabulary",
authors: ["Richard Cyganiak","Dave Reynolds"],
status : "W3C Recommendation 16 January 2014",
href : "https://www.w3.org/TR/vocab-data-cube/"
}
}
};
</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>
</head>
<body>
<section id="abstract">
<p>This document provides a framework in which the quality of a
dataset can be described, whether by the dataset publisher or by a
broader community of users. It does not provide a formal, complete
definition of quality, rather, it sets out a consistent means by
which information can be provided such that a potential user of a
dataset can make his/her own judgment about its fitness for purpose.
</p>
</section>
<section id="sotd">
<p>The model for the Data Quality Vocabulary is nearing maturity,
but the Working Group is seeking feedback on a number of specific
issues highlighted in the document below.</p>
</section>
<section id="toc"></section>
<section class="informative">
<h2 id="intro">Introduction</h2>
<p>
The Data on the Web Best Practices <a
href="http://www.w3.org/TR/dwbp/">Working Draft</a> has pointed out
the relevance of <a href="http://www.w3.org/TR/dwbp/#quality">publishing
information about the quality of data published on the Web</a>.
Accordingly, the <a href="http://www.w3.org/2013/dwbp/wiki/Main_Page">Data
on the Web Best Practices Working Group</a> has been chartered to create
a vocabulary for expressing data quality. The Data Quality Vocabulary
(DQV) presented in this document is foreseen as an extension to DCAT
[[vocab-dcat]] to cover the quality of the data, how frequently is it
updated, whether it accepts user corrections, persistence commitments
etc. When used by publishers, this vocabulary will foster trust in
the data amongst developers.
</p>
<p>This vocabulary does not seek to determine what
"quality" means. We believe that quality lies in the eye of
the beholder; that there is no objective, ideal definition of it.
Some datasets will be judged as low-quality resources by some data
consumers, while they will perfectly fit others' needs. In
accordance, we attach a lot of importance to allowing many actors to
assess the quality of datasets and publish their annotations,
certificates, opinions about a dataset. A dataset's publisher should
seek to publish metadata that helps data consumers determine whether
they can use the dataset to their benefit. However, publishers should
not be the only ones to have a say on the quality of data published
in an open environment like the Web. Certification agencies, data
aggregators, data consumers can make relevant quality assessments,
too.</p>
<p>We want to stimulate this by making it easier to publish,
exchange and consume quality metadata, for every step of a dataset's
lifecycle. This is why next to rather expected constructs like
quality measures, the Data Quality Vocabulary puts an emphasis
on feedback, annotation, agreements</p>
<p>Note that DQV elements can be applied not only to
express metadata on the quality of datasets; they can also be used to express
statements about the quality of that metadata itself. This is especially true when it
comes to representing the provenance of that metadata or its conformance with respect
to established metadata standards.</p>
</section>
<section id="namespaces">
<h2>Namespaces</h2>
<p>
The namespace for DQV is provisionally set as
<code>http://www.w3.org/ns/dqv#</code>
. DQV, however, seeks to re-use elements from other vocabularies,
notably <a href="http://www.w3.org/ns/dcat#">DCAT</a>, following the
<a href="http://www.w3.org/TR/dwbp/#dataVocabularies">best
practices for data vocabularies</a> identified by the Data on the Web
Best Practices Working Group.
</p>
<!-- <div class="note">
<p>A first RDF representation of DQV has been created and is temporarily accessible at <a href="http://w3c.github.io/dwbp/dqv.ttl">http://w3c.github.io/dwbp/dqv.ttl</a>.</p>
</div> -->
<p>The table below indicates the full list of namespaces and
prefixes used in this document.</p>
<table id="namespacesTable">
<thead>
<tr>
<th>Prefix</th>
<th>Namespace</th>
</tr>
</thead>
<tbody>
<tr>
<td>daq</td>
<td>http://purl.org/eis/vocab/daq#</td>
</tr>
<tr>
<td>dcat</td>
<td>http://www.w3.org/ns/dcat#</td>
</tr>
<tr>
<td>dcterms</td>
<td>http://purl.org/dc/terms/</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>oa</td>
<td>http://www.w3.org/ns/oa#</td>
</tr>
<tr>
<td>prov</td>
<td>http://www.w3.org/ns/prov#</td>
</tr>
<tr>
<td>sdmx-attribute</td>
<td>http://purl.org/linked-data/sdmx/2009/attribute#</td>
</tr>
<tr>
<td>skos</td>
<td>http://www.w3.org/2004/02/skos/core#</td>
</tr>
</tbody>
</table>
</section>
<section id="model">
<h2>Vocabulary Overview</h2>
<p>The following vocabulary is based on DCAT [[vocab-dcat]] that
it extends with a number of additional properties and classes
suitable for expressing the quality of a dataset.</p>
<p>
The quality of a given dataset of distribution is assessed via a
number of observed properties. For instance, one may consider a
dataset to be of high quality because it complies to a specific
standard while for other use-cases the quality of the data will
depend on its level of interlinking with other datasets. To express
these properties an instance of a <a
href="http://www.w3.org/TR/vocab-dcat/#Class:_Dataset">dcat:Dataset</a>
or <a href="http://www.w3.org/TR/vocab-dcat/#Class:_Distribution">dcat:Distribution</a>
can be related to four different types of quality information represented by the following classes:
</p>
<ul>
<li><a href="#dqv:QualityAnnotation">dqv:QualityAnnotation</a>
represents feedbacks and quality certificates given about the
dataset or its distribution.</li>
<li><a href="http://purl.org/dc/terms/Standard">dcterms:Standard</a>
represents a standard the dataset or its distribution conforms to.</li>
<li><a href="#dqv:QualityPolicy">dqv:QualityPolicy</a>
represents a policy or agreement that is chiefly governed by data quality concerns.</li>
<li><a href="#dqv:QualityMeasurement">dqv:QualityMeasurement</a>
represents a metric value providing quantitative or qualitative
information about the dataset or distribution.</li>
<li><a href="http://www.w3.org/ns/prov#Entity">prov:Entity</a>
represents an entity involved in the provenance of the dataset or
distribution.</li>
</ul>
<p>
DQV defines quality measures as specific instances of Quality Measurements, adapting the daQ quality framework [[DaQ]], [[DaQ-RDFCUBE]]. It relies on quality dimensions and quality metrics. </p>
<ul>
<li>A Quality Dimension (<a href="#dqv:Dimension">dqv:Dimension</a>) is a quality-related characteristic of a dataset
relevant to the consumer (e.g., the availability of a dataset).</li>
<li>A Quality Metric (<a href="#dqv:Metric">dqv:Metric</a>) gives a procedure for measuring a data quality dimension, which is abstract, by observing a concrete quality indicator. There are usually multiple metrics per dimension; e.g., availability can be indicated by the accessibility of a SPARQL endpoint, or that of an RDF dump. The value of a metric can be numeric (e.g., for the metric “human-readable labeling of classes, properties and entities”, the percentage of entities having an rdfs:label or rdfs:comment) or boolean (e.g. whether or not a SPARQL endpoint is accessible).</li>
</ul>
<!--p>For example, a dimension could be "multilinguality" and two metrics could be "ratio of literals with language tags" and "number
of different language tags".</p-->
<p>Besides quality measurements, DQV considers certificates, standards, and quality policies, which can also be organized according to dimensions. Quality metadata containers (<a href="#dqv:QualityMetadata">dqv:QualityMetadata</a>) can group together different quality statements, so that their provenance can be tracked jointly.</p>
<figure>
<a href="images/DataQuality0.2.9.svg"> <img
src="images/DataQuality0.2.9.svg" />
</a>
<figcaption>Data model showing the main relevant classes
and their relations.</figcaption>
</figure>
<p>
<em>
N.B.: "containment" refers to the inclusion of quality statements into "containers", which may or may not be treated as (RDF) graphs (see later <a href="#DocumentProvenanceQualityMetadata">example</a> and the usage note for the class <a href="#dqv:QualityMetadata">dqv:QualityMetadata</a>).
</em>
</p>
<p>
Quality information can be derived from other quality information. For example, a quality annotation can be derived from a standard or a quality measurement. Quality measurements can be derived from other measurements. Metrics can be derived from other metrics. A standard can be built on another standard or a (set of) metrics. DQV models such derivations through the property <a href="https://www.w3.org/TR/prov-o/#wasDerivedFrom">prov:wasDerivedFrom</a> as illustrated in the diagram below.
</p>
<figure>
<a href="images/wasDerivedFrom2.svg"> <img
src="images/wasDerivedFrom2.svg" />
</a>
<figcaption>Using the property <a href="https://www.w3.org/TR/prov-o/#wasDerivedFrom">prov:wasDerivedFrom</a> to interrelate quality metrics and other quality statements.</figcaption>
</figure>
</section>
<section id="VocabularySpecification">
<h2>Vocabulary specification</h2>
<div class="note">
<p>This section is work in progress. We will include later more
tables with specification of individual classes and properties.</p>
</div>
<section id="dqv:QualityMeasurement">
<h3>Class: Quality Measurement</h3>
<!--p>DQV defines quality measures as specific instances of DQV
observations, adapting the DAQ quality metrics framework [[DaQ]],
[[DaQ-RDFCUBE]]:</p>
<ul>
<li>A Quality Dimension is a characteristic of a dataset
relevant to the consumer (e.g., the availability of a dataset).</li>
<li>A Quality Metric gives a procedure for measuring a data
quality dimension, which is abstract, by observing a concrete
quality indicator. There are usually multiple metrics per
dimension; e.g., availability can be indicated by the accessibility
of a SPARQL endpoint, or of an RDF dump. The value of a metric can
be numeric (e.g., for the metric “human-readable labeling of
classes, properties and entities”, the percentage of entities
having an rdfs:label or rdfs:comment) or boolean (e.g. whether or
not a SPARQL endpoint is accessible).</li>
</ul>
<p>For example, a dimension could be "multilinguality" and two
metrics could be "ratio of literals with language tags" and "number
of different language tags".</p-->
<p>
The following properties should be used on this class: <a
href="#dqv:isMeasurementOf">dqv:isMeasurementOf</a>, <a href="#dqv:value">dqv:value</a>,
<a href="#qb:dataSet">qb:dataSet</a>.
</p>
<div class="issue">
<p>
Should (and if yes, how) DQV represent parameters for a metric
applied for computing a specific quality measurement (e.g.,a specific
setting of weights)? (<a
href="https://www.w3.org/2013/dwbp/track/issues/223">Issue-223</a>)
</p>
</div>
<table class="definition">
<thead>
<tr>
<th>RDF Class:</th>
<th><a href="#dqv:QualityMeasurement">dqv:QualityMeasurement</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition:</td>
<td>A quality measurement represents the evaluation of a given
dataset (or dataset distribution) against a specific quality
metric.</td>
</tr>
<tr>
<td class="prop">Subclass of:</td>
<td><a href="http://purl.org/linked-data/cube#Observation">qb:Observation</a></td>
</tr>
<tr>
<td class="prop">Equivalent class</td>
<td><a href="http://purl.org/eis/vocab/daq#Observation">daq:Observation</a></td>
</tr>
<tr><td class="prop">Usage note:</td><td>The unit of measure in quality measurement should be specified through the property <a href="purl.org/linked-data/sdmx/2009/attribute#unitMeasure">sdmx-attribute:unitMeasure</a> as recommended by RDF Data Cube [[Vocab-Data-Cube]].
The <a href="http://www.wurvoc.org/vocabularies/om-1.8/">Ontology of units of Measure (OM)</a> [[RijgersbergEtAl]] provides a list of HTTP dereferenceable unit of measures which can be exploited as values for <a href="purl.org/linked-data/sdmx/2009/attribute#unitMeasure">sdmx-attribute:unitMeasure</a>.</td></tr>
</tbody>
</table>
<section id="dqv:isMeasurementOf">
<h4>Property: isMeasurementOf</h4>
<table class="definition">
<thead>
<tr>
<th>RDF Property:</th>
<th><a href="#dqv:isMeasurementOf">dqv:isMeasurementOf</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition:</td>
<td>Indicates the metric being observed.</td>
</tr>
<tr>
<td class="prop">Instance of:</td>
<td><a
href="http://purl.org/linked-data/cube#DimensionProperty">qb:DimensionProperty</a>
</td>
</tr>
<tr>
<td class="prop">Domain:</td>
<td><a href="http://purl.org/linked-data/cube#Observation">qb:Observation</a></td>
</tr>
<tr>
<td class="prop">Range:</td>
<td><a href="#dqv:Metric">dqv:Metric</a></td>
</tr>
<!--tr><td class="prop">Minimum cardinality:</td><td>1</td></tr-->
<tr>
<td class="prop">Equivalent Property</td>
<td><a href="http://purl.org/eis/vocab/daq#metric">daq:metric</a></td>
</tr>
</tbody>
</table>
</section>
<section id="qb:dataSet">
<h4>Property: dataSet</h4>
<table class="definition">
<thead>
<tr>
<th>RDF Property:</th>
<th><a href="http://purl.org/linked-data/cube#dataSet">qb:dataSet</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition:</td>
<td>Indicates the dataset to a quality measurement (which is an
RDF Data Cube observation) belongs.</td>
</tr>
<tr>
<td class="prop">Domain:</td>
<td><a href="http://purl.org/linked-data/cube#Observation">qb:Observation</a></td>
</tr>
<tr>
<td class="prop">Range:</td>
<td><a href="http://purl.org/linked-data/cube#Observation">qb:DataSet</a></td>
</tr>
</tbody>
</table>
</section>
<section id="dqv:computedOn">
<h4>Property: computedOn</h4>
<table class="definition">
<thead>
<tr>
<th>RDF Property:</th>
<th><a href="#dqv:computedOn">dqv:computedOn</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition:</td>
<td>Refers to the resource (e.g., a dataset, a linkset, a
graph, a set of triples) on which the quality measurement is
performed. In the DQV context, this property is generally
expected to be used in statements in which objects are instances
of <a href="http://www.w3.org/TR/vocab-dcat/#class-dataset">dcat:Dataset</a>
and <a
href="http://www.w3.org/TR/vocab-dcat/#class-distribution">dcat:Distribution</a>.
</td>
</tr>
<tr>
<td class="prop">Instance of:</td>
<td><a
href="http://purl.org/linked-data/cube#DimensionProperty">qb:DimensionProperty</a>
</td>
</tr>
<tr>
<td class="prop">Domain:</td>
<td><a href="#dqv:QualityMeasurement">dqv:QualityMeasurement</a></td>
</tr>
<!--<tr><td class="prop">Range:</td><td><a href="http://www.w3.org/TR/vocab-dcat/#class-dataset">dcat:Dataset</a>, <a href="http://www.w3.org/TR/vocab-dcat/#class-distribution">dcat:Distribution</a></td></tr>-->
<tr>
<td class="prop">Equivalent property:</td>
<td><a href="http://purl.org/eis/vocab/daq#computedOn">daq:computedOn</a></td>
</tr>
<tr>
<td class="prop">Inverse property:</td>
<td><a href="#dqv:hasQualityMeasurement">dqv:hasQualityMeasurement</a></td>
</tr>
<!--tr><td class="prop">Minimum cardinality:</td><td>1</td></tr-->
<!--tr><td class="prop">Maximum cardinality:</td><td>1</td></tr-->
</tbody>
</table>
</section>
<section id="dqv:value">
<h4>Property: value</h4>
<table class="definition">
<thead>
<tr>
<th>RDF Property:</th>
<th><a href="#dqv:value">dqv:value</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition:</td>
<td>Refers to values computed by metric.</td>
</tr>
<tr>
<td class="prop">Instance of:</td>
<td><a
href="http://purl.org/linked-data/cube#MeasureProperty">qb:MeasureProperty</a>,
<a href="http://www.w3.org/2002/07/owl#DatatypeProperty">owl:DatatypeProperty</a>
</td>
</tr>
<tr>
<td class="prop">Domain:</td>
<td><a href="#dqv:QualityMeasurement">dqv:QualityMeasurement</a></td>
</tr>
<!--tr><td class="prop">Range:</td><td><a href="ttp://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a></td></tr-->
<tr>
<td class="prop">Equivalent property:</td>
<td><a href="http://purl.org/eis/vocab/daq#value">daq:value</a></td>
</tr>
<!--tr><td class="prop">Minimum cardinality:</td><td>1</td></tr>
<tr><td class="prop">Maximum cardinality:</td><td>1</td></tr-->
</tbody>
</table>
</section>
</section>
<section id="dqv:Metric">
<h3>Class: Metric</h3>
<p>
The following properties should be used on this class: <a
href="#dqv:inDimension">dqv:inDimension</a>.
</p>
<table class="definition">
<thead>
<tr>
<th>RDF Class:</th>
<th><a href="#dqv:Metric">dqv:Metric</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition:</td>
<td>A standard to measure a quality dimension. An observation
(instance of dqv:QualityMeasurement) assigns a value in a given unit
to a Metric. <!--Specific metrics are defined as subclasses of this abstract class.-->
</td>
</tr>
<!--<tr><td class="prop">Usage note:</td><td>@@TODO@@</td></tr>-->
<tr>
<td class="prop">Equivalent class</td>
<td><a href="http://purl.org/eis/vocab/daq#Metric">daq:Metric</a></td>
</tr>
</tbody>
</table>
<section id="dqv:expectedDataType">
<h4>Property: expectedDataType</h4>
<div class="issue">
<p>
In daQ, the property <a
href="http://purl.org/eis/vocab/daq#expectedDataType">daq:expectedDataType</a>
associates each metric to the expected data type for its observed
value. Data types for observed values are restricted to <a
href="http://www.w3.org/2001/XMLSchema#anySimpleType">xsd:anySimpleType</a>
(e.g. xsd:boolean, xsd:double etc…). Is the current practice of
using daq:expectedDataType in daQ appropriate? Isn't the
restriction to xsd:anySimpleType too narrow? (<a
href="https://www.w3.org/2013/dwbp/track/issues/224">Issue-224</a>)
</p>
</div>
<table class="definition">
<thead>
<tr>
<th>RDF Property:</th>
<th><a href="#dqv:expectedDataType">dqv:expectedDataType</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition:</td>
<td>Represents the expected data type for metric's observed value (e.g. xsd:boolean, xsd:double etc...) </td>
</tr>
<tr>
<td class="prop">Domain:</td>
<td><a href="#dqv:Metric">dqv:Metric</a></td>
</tr>
<tr>
<td class="prop">Range:</td>
<td> <a href="http://www.w3.org/2001/XMLSchema#anySimpleType">xsd:anySimpleType</a>
</td>
</tr>
<tr>
<td class="prop">Equivalent property</td>
<td><a href="http://purl.org/eis/vocab/daq#expectedDataType">daq:expectedDataType</a></td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="dqv:Dimension">
<h3>Class: Dimension</h3>
<p>
The following properties should be used on this class: <a
href="#dqv:inCategory">dqv:inCategory</a>.
</p>
<table class="definition">
<thead>
<tr>
<th>RDF Class:</th>
<th><a href="#dqv:Dimension">dqv:Dimension</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition:</td>
<td>Represents criteria relevant for assessing quality. Each
quality dimension must have one or more metric to measure it. <!-- Dimensions are provided as subclasses of this abstract class, which is not intended for direct usage.-->
A dimension is linked with a category using the dqv:inDimension
property.
</td>
</tr>
<tr>
<td class="prop">Subclass of:</td>
<td><a href="https://www.w3.org/TR/skos-reference/#concepts">skos:Concept</a></td>
</tr>
<!--<tr><td class="prop">Usage note:</td><td>@@TODO@@</td></tr>-->
<tr>
<td class="prop">Equivalent class</td>
<td><a href="http://purl.org/eis/vocab/daq#Dimension">daq:Dimension</a></td>
</tr>
</tbody>
</table>
<section id="dqv:inCategory">
<h4>Property: inCategory</h4>
<table class="definition">
<thead>
<tr>
<th>RDF Property:</th>
<th><a href="#dqv:inCategory">dqv:inCategory</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition:</td>
<td>Represents the category a dimension is grouped in.</td>
</tr>
<tr>
<td class="prop">Domain:</td>
<td><a href="#dqv:Dimension">dqv:Dimension</a></td>
</tr>
<tr>
<td class="prop">Range:</td>
<td><a href="#dqv:Category">dqv:Category</a></td>
</tr>
<tr>
<td class="prop">Inverse:</td>
<td><a href="http://purl.org/eis/vocab/daq#hasDimension">daq:hasDimension</a></td>
</tr>
<!--tr><td class="prop">Minimum cardinality:</td><td></td></tr>
<tr><td class="prop">Maximum cardinality:</td><td>1</td></tr-->
<tr>
<td class="prop">Usage note:</td>
<td>Categories are meant to systematically organize
dimensions. The Data Quality Vocabulary defines no specific
cardinality constraints for dqv:inCategory, since distinct
quality frameworks might have different perspectives over a
dimension. A dimension may therefore be associated to more than
one category. However, those who define new quality metrics
should try to avoid this as much as possible and assign only one
category to the dimensions they define.</td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="dqv:Category">
<h3>Class: Category</h3>
<table class="definition">
<thead>
<tr>
<th>RDF Class:</th>
<th><a href="#dqv:Category">dqv:Category</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition:</td>
<td>Represents a group of quality dimensions in which a
common type of information is used as quality indicator. <!--Categories are provided as subclasses of this abstract class, which is not intended for direct usage.-->
</td>
</tr>
<!--<tr><td class="prop">Usage note:</td><td>@@TODO@@</td></tr>-->
<tr>
<td class="prop">Subclass of:</td>
<td><a href="https://www.w3.org/TR/skos-reference/#concepts">skos:Concept</a></td>
</tr>
<tr>
<td class="prop">Equivalent class</td>
<td><a href="http://purl.org/eis/vocab/daq#Category">daq:Category</a></td>
</tr>
</tbody>
</table>
</section>
<div class="note">
<p>
Dimension and category are abstract entities. We represent instances dqv:Dimension and dqv:Category as instances of <code>skos:Concept</code>, which we think enable similar features as these for dimensions and categories in daQ. Our representation choice differs more significantly for metrics, however. daQ uses RDFS/OWL classes and subclasses to represent constraints on measurements (e.g., on the type of values). RDFS/OWL however make an 'open world' assumption that does not allow one to capture entirely all constraints. Additionally, languages are currently being defined to represent constraints in more appropriate ways (SHACL). We think it is therefore not appropriate now to recommend to treat specific metrics as subclasses of dqv:Metric, and we refer implementers to future progress on SHACL and related technology.
</p>
</div>
<section id="dqv:QualityMeasurementDataset">
<h3>Class: Quality Measurement Dataset</h3>
<table class="definition">
<thead>
<tr>
<th>RDF Class:</th>
<th><a href="#dqv:QualityMeasurementDataset">dqv:QualityMeasurementDataset</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition:</td>
<td>Represents a dataset of quality measurements, evaluations of
a given dataset (or dataset distribution) against a specific
quality metric.</td>
</tr>
<tr>
<td class="prop">Subclass of:</td>
<td><a
href="http://www.w3.org/TR/vocab-data-cube/#ref_qb_DataSet">qb:DataSet</a></td>
</tr>
<!--<tr><td class="prop">Usage note:</td><td>@@TODO@@</td></tr>-->
<tr>
<td class="prop">Equivalent class</td>
<td><a href="http://purl.org/eis/vocab/daq#QualityGraph">daq:QualityGraph</a></td>
</tr>
</tbody>
</table>
</section>
<section id="dqv:QualityPolicy">
<h3>Class: Quality Policy</h3>
<table class="definition">
<thead>
<tr>
<th>RDF Class:</th>
<th><a href="#dqv:QualityPolicy">dqv:QualityPolicy</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition:</td>
<td>Represents a policy or agreement that is chiefly governed by data quality concerns.</td>
</tr>
</tbody>
</table>
</section>
<section id="dqv:QualityAnnotation">
<h3>Class: Quality Annotation</h3>
<table class="definition">
<thead>
<tr>
<th>RDF Class:</th>
<th><a href="#dqv:QualityAnnotation">dqv:QualityAnnotation</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition:</td>
<td>Represents quality annotations, including rating, quality
certificate, feedback that can be associated to datasets or
distributions. Quality annotations must have one oa:motivatedBy
statement with an instance of oa:Motivation (and skos:Concept),
which reflects a quality assessment purpose. We define this
instance as dqv:qualityAssessment.</td>
</tr>
<tr>
<td class="prop">Subclass of:</td>
<td><a href="http://www.w3.org/ns/oa#d4e434">oa:Annotation</a></td>
</tr>
<!--<tr><td class="prop">Usage note:</td><td>@@TODO@@</td></tr>-->
<tr>
<td class="prop">Equivalent class</td>
<td><pre class="highlight">
EquivalentClasses(
dqv:QualityAnnotation
ObjectHasValue( oa:motivatedBy dqv:qualityAssessment )
)</pre></td>
</tr>
</tbody>
</table>
<div class="note">
<p>To make the document more self-contained we might consider to
describe some properties of oa:Annotation, such as hasBody,
hasTarget.</p>
</div>
</section>
<section id="dqv:QualityCertificate">
<h3>Class: Quality Certificate</h3>
<table class="definition">
<thead>
<tr>
<th>RDF Class:</th>
<th><a href="#dqv:UserQualityFeedback">dqv:QualityCertificate</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition:</td>
<td>Represents annotations that associate datasets or distributions to quality certificate.</td>
</tr>
<tr>
<td class="prop">Subclass of:</td>
<td><a href="#dqv:QualityAnnotation">dqv:QualityAnnotation</a> </td>
</tr>
</tbody>
</table>
</section>
<section id="dqv:UserQualityFeedback">
<h3>Class: User Quality Feedback</h3>
<table class="definition">
<thead>
<tr>
<th>RDF Class:</th>
<th><a href="#dqv:UserQualityFeedback">dqv:UserQualityFeedback</a></th>
</tr>
</thead>
<tbody>
<tr>
<td class="prop">Definition:</td>