diff --git a/dcat/config.js b/dcat/config.js index 7ea2b7cc5..b22185713 100644 --- a/dcat/config.js +++ b/dcat/config.js @@ -122,8 +122,8 @@ var respecConfig = { title:"DBPedia ontology" }, "DCAT-AP-SE": { - title: "DCAT-AP-SE: Swedish recommendation for DCAT-AP1.1", - href: "https://lankadedata.se/spec/DCAT-AP-SE", + title: "DCAT-AP-SE: Clarifications, translations and explanations of DCAT-AP for Sweden", + href: "https://docs.dataportal.se/dcat/en/", authors: ["Matthias Palmér"], etAl: false }, diff --git a/dcat/index.html b/dcat/index.html index 1f00fabd4..c394037e6 100644 --- a/dcat/index.html +++ b/dcat/index.html @@ -210,6 +210,7 @@
pav
http://purl.org/pav/
sdmx-attribute
http://purl.org/linked-data/sdmx/2009/attribute#
sdo
https://schema.org/
xhv
http://www.w3.org/1999/xhtml/vocab#
w3cgeo
http://www.w3.org/2003/01/geo/wgs84_pos#
RDF Property: | +dcat:first | +
---|---|
Definition: | +The first resource in an ordered collection or series of resources, to which the current resource belongs. | +
Sub-property of: | +xhv:first |
+
Usage note: | +
+ In DCAT this property is used for resources belonging to a |
+
See also: | ++, +, +. + | +
RDF Property: | +dcat:last | +
---|---|
Definition: | +The last resource in an ordered collection or series of resources, to which the current resource belongs. | +
Sub-property of: | +xhv:last |
+
Usage note: | +
+ In DCAT this property is used for resources belonging to a |
+
See also: | ++, +, +. + | +
RDF Property: | +dcat:next | +
---|---|
Definition: | +The next resource (after the current one) in an ordered collection or series of resources. | +
Sub-property of: | +xhv:next |
+
Usage note: | +
+ In DCAT this property is used for resources belonging to a |
+
See also: | ++, +, +. + | +
RDF Property: | +dcat:prev | +
---|---|
Definition: | +The previous resource (before the current one) in an ordered collection or series of resources. | +
Sub-property of: | +xhv:prev |
+
Usage note: | +
+ In DCAT this property is used for resources belonging to a It is important to note that this property is different from |
+
See also: | ++, +, +. + | +
RDF Class: | dcat:DatasetSeries |
---|---|
Definition: | A collection of datasets that are published separately, but share some common characteristics that groups them. |
Sub-class of: | dcat:Dataset |
Usage note: | Dataset series can be also soft-typed via property dcterms:type as in the approach used in [[GeoDCAT-AP]], and adopted in [[DCAT-AP-IT]] and [[GeoDCAT-AP-IT]]). |
Usage note: | Dataset series can be also soft-typed via property dcterms:type as in the approach used in [[?GeoDCAT-AP]], and adopted in [[?DCAT-AP-IT]] and [[?GeoDCAT-AP-IT]]). |
Usage note: | Common scenarios for dataset series include: time series composed of periodically released subsets; map-series composed of items of the same type or theme but with differing spatial footprints. |
adms:last
is defined as A link to the current or latest version of the Asset, whereas in [[PAV]] the current and latest versions of a resource may be different, and link to by using different properties.
Moreover, although the definitions of the [[VOCAB-ADMS]] properties states explicitly that they are meant to be used for "versions", they are subproperties of the corresponding terms in [[XHTML-VOCAB]], where they are used to link resources in a collection (e.g., the set of pages of a Web site). E.g., the definition of xhv:last
reads as follows: last refers to the last resource in a collection of resources.
.
Based on that, in this draft, [[PAV]]-equivalent properties are used for versions, whereas the [[VOCAB-ADMS]] ones are used for dataset series (). Properties dcterms:hasVersion
/ dcterms:isVersionOf
are not used.
Based on that, in this draft, [[PAV]]-equivalent properties are used for versions, whereas the [[VOCAB-ADMS]] properties, and properties dcterms:hasVersion
/ dcterms:isVersionOf
are not used.
Property dcat:previousVersion
is used to build a version chain, that can be navigated backward from a given version to the first one. This reflects the most typical use case - i.e., linking different versions published as distinct resources in a catalog.
With "dataset series" we refer to data, somehow interrelated, that are published separately. An example is budget data split by year and/or country, instead of being made available in a single dataset.
@@ -4704,10 +4997,10 @@Dataset series may evolve over time, by acquiring new datasets. E.g., a dataset series about yearly budget data will acquire a new child dataset every year. In such cases, it might be important to link the yearly releases with relationships specifying the previous, next, and latest ones. In such scenario, DCAT makes use of the [[VOCAB-ADMS]] properties adms:prev
, adms:next
, and adms:last
, respectively.
Dataset series may evolve over time, by acquiring new datasets. E.g., a dataset series about yearly budget data will acquire a new child dataset every year. In such cases, it might be important to link the yearly releases with relationships specifying the first, previous, next, and latest ones. In such scenario, DCAT makes use of properties dcat:first
, dcat:prev
, dcat:next
, and dcat:last
, respectively.
Properties about dataset series can be classified into two groups.
-The first group is about properties describing the dataset series itself. For instance, this is the case of property dcterms:accrualPeriodicity
, whose value should correspond to the frequency upon which a new child dataset is added.
The first group is about properties describing the dataset series itself. For instance, this is the case of property dcterms:accrualPeriodicity
, whose value should correspond to the frequency upon which a new child dataset is added.
The second group is about properties reflecting the dimensions described in child dataset metadata, via upstream inheritance - i.e., property values of child datasets are inherited by their parent (the dataset series).
@@ -4774,8 +5067,8 @@Finally, some annotation properties of child datasets may need to be taken into account as well at the level of dataset series. In particular, properties concerning the creation / publication / update dates of child datasets may affect the corresponding ones in the series. For these properties, DCAT recommends the following approach:
dcterms:created
) of the dataset series should correspond to the earliest creation date of the child datasets.dcterms:issued
) of the dataset series should correspond to the earliest publication date of the child datasets.dcterms:modified
) of the dataset series should correspond to the latest publication or update date of the child datasets.dcterms:issued
) of the dataset series should correspond to the earliest publication date of the child datasets.dcterms:modified
) of the dataset series should correspond to the latest publication or update date of the child datasets.