Open coret opened 6 months ago
Agreed. Note that the DKG currently discovers this property, exposing it as void:vocabulary
, but on the level of the dataset, not the distribution. In other words, this implies supporting different vocabularies per distribution.
In the example that Europeana shared with an identifier for the EDM was used including its definition:
<http://www.europeana.eu/schemas/edm/>
a dct:Standard .
Should we consider using a blank node for dct:conformsTo to include also the definition or do we assume this value to always be of type dct:Standard?
According to the spec, dct:conformsTo includes instead of has range dct:Standard, so adding it explicitly would add meaning.
Note that the DKG currently discovers this property, exposing it as void:vocabulary,
I think dct:conformsTo / schema:publishingPrinciples is broader than vocabulary (which can only be applied to linked data).
For the Aggregating Linked Data in Europeana MVP we need to be able to specify on which standard/model/ontology a distribution is based (eg. https://www.europeana.eu/schemas/edm/EDM.xsd). This property differs from
dct:format
/schema:encodingFormat
where you specify the format likeapplication/rdf+xml
.A suitable DCAT property would be dct:conformsTo. As mentioned in DCAT-AP to Schema.org Mapping, the property schema:publishingPrinciples would be the
nearest
Schema.org property.We need to include this property in the requirements (recommended, cardinality 0..n), adjust the SHACL and adapt the crawler (conversion & storing).