- From: Simon Cox via GitHub <sysbot+gh@w3.org>
- Date: Sun, 21 Jul 2019 01:44:43 +0000
- To: public-dxwg-wg@w3.org
>when DCAT says something about the global dcterms:issued, it should be something applicable in all contexts where dcterms:issued is used, and therefore, should not do it I disagree strongly. It is completely legitimate to add annotations to any class or property from any namespace, to indicate expectations _in a particular context_. The context here is DCAT. That is clear from the fact that this annotation appears in the RDF representation of DCAT, as packaged in an artefact called dcat.ttl and distributed by W3C. What is done with that information in a particular application context is up to the application developer, who should be careful to load the graph they need for the application they are building. There are many technical ways to achieve this, which are not the point here (named-graphs are just one possibility), The 'danger' is introduced by an application developer using a graph constructed for one application in a different context. It is the responsibility of the application builder to load the graphs that are needed for their application. Using an RDF property or class from someone else's namespace and adding some rules about how it should be used in a specific context is part of the RDF methodology. We have a lot of specific usage notes relating to dct, foaf, prov ... resources. I am happy for them to be all moved to `skos:scopeNote` raather than `skos:definition` (I think that is @kcoyle suggestion) but not to remove them altogether from the RDF representation _in the file called dcat.ttl_. -- GitHub Notification of comment by dr-shorthair Please view or discuss this issue at https://github.com/w3c/dxwg/issues/725#issuecomment-513512037 using your GitHub account
Received on Sunday, 21 July 2019 01:44:44 UTC