- From: Karen Coyle via GitHub <sysbot+gh@w3.org>
- Date: Sat, 02 Nov 2019 15:25:30 +0000
- To: public-dxwg-wg@w3.org
@riccardoAlbertoni The DQV standard says that the "conforms to" statement relates to the metadata, not to the resource which the metadata describes: >The following example illustrates how a (DCAT) catalog record can be said to be conformant with the GeoDCAT-AP standard itself. ``` :myDatasetRecord a dcat:CatalogRecord ; foaf:primaryTopic :myDataset ; dcterms:conformsTo :geoDCAT-AP . ``` Given that the GeoDCAT-AP is a standard for metadata, not for the resources that are pointed to from a DCAT catalog, then I think this says the opposite of what @makxdekkers and @smrgeoinfo were saying. That DQV statement is consistent with the definition quoted by @bertvannuffelen, which is: >catalog record: This property SHOULD be used to indicate the model, schema, ontology, view or profile that the catalog record metadata conforms to. Note that it says "that the catalog record *metadata* conforms to", not "that the cataloged resource conforms to." So I think that the DCAT definitions are consistent with what is in DQV, but it seems that the interpretation that the three of you are making is different. I honestly don't care which interpretation is given the final approval, but we do need to eliminate the inconsistencies we've surfaced here. Also, as I pointed out above, if the meaning of: ``` ex:catrec1 dct:conformsTo ex:standard1 ex:catrec1 foaf:primaryTopic ex:dcatResource ``` is that `ex:catrec1 dct:conformsTo ex:standard1` means that the `ex:dcatResource` conforms to `ex:standard1` then there does seem to be a redundancy because there are two places where the `ex:dcatResource dct:conformsTo` is stated, in graph for the Catalog Record and in the graph for the Resource: ``` ex:catrec1 dct:conformsTo ex:standard1 ex:catrec1 foaf:primaryTopic ex:dcatResource ex:dcatResource rdf:type dcat:Resource ex:dcatResource dct:conformsTo ex:standard1 ``` and one wonders if that redundancy is intentional. -- GitHub Notification of comment by kcoyle Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1130#issuecomment-549053693 using your GitHub account
Received on Saturday, 2 November 2019 15:25:33 UTC