- From: Jakub Klímek via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Aug 2018 05:42:04 +0000
- To: public-dxwg-wg@w3.org
@lvdbrink I would advise against considering usage of `dc:type` instead of `dct:type` as the [whole dc elements namespace was deprecated](http://dublincore.org/documents/dces/) by dc terms for use in Linked Data. > IMHO there is a need to provide a specific example of the problem and why its a problem, and how to handle the use cases of soft-typing. @rob-metalinkage A specific example of a problem would be an inference enabled Linked Data visualizer (or repository such as RDF4J). A typical discovery query is asking for all `rdfs:Class` and `owl:Class` instances in a SPARQL endpoint to see what data is there. With inferencing enabled, all instances of `skos:Concept`s used in a DCAT-rev data catalog to categorize datasets using `dct:type` could be unintentionally returned as instances of `rdfs:Class` with no actual instances (those would use `rdf:type`) causing all kinds of confusions. I would say that in this case, using `dct:type` is not worth it just for the sake of reusing an existing property, due to these unintentional side effects. I would suggest either 1. Explicitly say that the dataset categories are `rdfs:Class`es, and they should be used as `rdf:type`s 2. Say that the dataset categories are not implicit `rdfs:Class`es, and use another property for their attachment, with no "concealed" side effects such ass OWL punning The fact that as of now, the group does not see an immediate problem does not mean that this will be OK in near future, where, e.g. automated inferencing could become more spread. IMHO better to be safe and unless the inference is intentional (which it is not in this case), I would steer clear of it. -- GitHub Notification of comment by jakubklimek Please view or discuss this issue at https://github.com/w3c/dxwg/issues/314#issuecomment-414202849 using your GitHub account
Received on Monday, 20 August 2018 05:42:05 UTC