FAIRDataTeam / FAIRDataPoint

https://www.fairdatapoint.org
MIT License
60 stars 37 forks source link

Usage of dct:conformsTo is not correct #533

Open CAVDgit opened 5 months ago

CAVDgit commented 5 months ago

Dear all,

I wish to address the use of dct:conformsTo for the Dataset class (and other classes) by the FDP.

As I understand it, the Fair Data Point (FDP) uses this property to indicate that metadata adheres to a specific schema. For example, the FDP reports that a Dataset metadata record conforms to the SHACL of the Dataset metadata schema of the FDP. This usage would be correct if the definition of dct:conformsTo were "An established standard to which the record conforms."

However, the correct definition of dct:conformsTo is "An established standard to which the DESCRIBED resource conforms," as detailed here.

Therefore, instead of specifying the standard that the record itself follows, it should specify the standard that the resource described by the record follows, which is a significant distinction.

The DCAT 3.0 documentation provides examples: DCAT 3.0 Example.

For instance:

ex:Dataset-1 a dcat:Dataset; dcterms:conformsTo http://data.europa.eu/eli/reg/2014/1312/oj .

"The use of dcterms:conformsTo and dcterms:Standard to represent conformance to a standard is well-established, as shown in Example 43 from SDW-BP (Example 51). This example declares a fictitious dcat:Dataset conformant to the EU INSPIRE Regulation on interoperability of spatial data sets and services ("Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services")."

I suggest you reconsider how the FDP annotates records to follow specific metadata schemas. Currently, the misuse of dct:conformsTo leads to confusion and difficulties in adhering to metadata standards such as DCAT and DCAT-AP.

Thank you very much.

dennisvang commented 2 months ago

related