VOCAB-DCAT-2 implementation evidence

	A	B
1
2	This spreadsheet has been created to collect implementation evidence of VOCAB-DCAT-2, to be eventually fed into the VOCAB-DCAT-2 Implementation Report
3
4	The latest implementation evidence is recorded in tab "Summary (consolidated)"
5
6	Gray	Class/property already included in DCAT 2014
7	Red	New class/property
8	Bold	Class/property recommended in DCAT-2
9	Normal	Properties inherited from dcat:Resource
10	Italic	Properties inherited from a parent class different from dcat:Resource
11	(YES)	Denotes the use of a class/property equivalent to the corresponding one in VOCAB-DCAT-2, because not supported in the original version of DCAT, and which may lead to the adoption of VOCAB-DCAT-2 solution
12		Classes/properties marked as features at risk in DCAT CR
13
14	NOTE	Implementation evidence has not been collected for class dcat:Resource and the corresponding properties, as dcat:Resource is an abstract class that is not supposed to be used directly, as explained in Section 5.1 of VOCAB-DCAT-2. Quoting:
15
16		dcat:Resource represents a dataset, a data service or any other resource that may be described by a metadata record in a catalog. This class is not intended to be used directly, but is the parent class of dcat:Dataset, dcat:DataService and dcat:Catalog. Member items in a catalog should be members of one of the sub-classes, or of a sub-class of these, or of a sub-class of dcat:Resource defined in a DCAT profile or other DCAT application. dcat:Resource is effectively an extension point for defining a catalog of any kind of resource. dcat:Dataset and dcat:DataService can be used for datasets and services which are not documented in any catalog.
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