- From: Phil Archer <phila@w3.org>
- Date: Thu, 27 Sep 2012 14:43:58 +0100
- To: Dave Reynolds <dave.e.reynolds@gmail.com>
- CC: public-gld-wg@w3.org
On 27/09/2012 14:27, Dave Reynolds wrote: [..] > OK. What about the other way round. Are all datasets semantic assets? > Well, again, it depends on the dataset. I can think of datasets that could be considered as semantic assets such as NAPTAN and the Companies House data. These are used as reference points within other datasets. But Suffolk County Council spending data for 2012 Q1... ? So we get to cost/benefit. If the cost of keeping dcat:Dataset and adms:Semantic Asset separate is greater than the benefit of making one a sub class of the other, then clearly we shouldn't keep them separated. My solution was to create a few super classes that I called RADion. If that imposes a useless burden on people well, then I'll happily read it the last rites - but that's not without some consequences. I did wonder about using the proposed extension to schema.org at http://www.w3.org/wiki/WebSchemas/Datasets#Related_vocabularies to fulfil the role foreseen for RADion but I'm not sure even that solves the problem. We still end up saying W3C Recs are datasets. Phil -- Phil Archer W3C eGovernment http://www.w3.org/egov/ http://philarcher.org +44 (0)7887 767755 @philarcher1
Received on Thursday, 27 September 2012 13:44:37 UTC