- From: Phil Archer <phil@philarcher.org>
- Date: Fri, 05 Apr 2013 12:37:08 +0100
- To: Makx Dekkers <makx@makxdekkers.com>
- CC: 'Bill Roberts' <bill@swirrl.com>, public-gld-comments@w3.org
I followed the idea of using a property to point to a class with the capitalisation of the class name as the only difference in some recent vocab work - and got push back. I was told by non-Sem Web data modellers that the more general convention is that properties (data type properties) should be nouns and relationships (object type properties) should be verbs. Things like org:hasSite cf. org:classification fit in with this. Based on that, if we were starting from scratch I'd argue for dcat:hasDataset or dcat:includesDataset but it may be too late now. And actually, isn't dcterms:hasPart sufficient for what dcat:dataset does anyway? The definition is "A related resource that is included either physically or logically in the described resource" which sounds rather like a dataset in a catalogue to me. Phil. On 05/04/2013 11:52, Makx Dekkers wrote: > > > I'd like to point to a decision taken by the Dublin Core Metadata > Initiative and documented at > http://dublincore.org/documents/naming-policy/ : > > > > "No DCMI Term Names will be assigned that differ from other Names only > in regard to case." > > > > Can you refer to cases where vocabularies use the same name for a class > and a property with only difference in case? > > > > I looked at other vocabularies (FOAF, VOID, SKOS, GoodRelations, DOAP, > MO, RDFS) and none of them seem to do this. I found some examples where > they use class name Something and then have a property hasSomething > (e.g. GoodRelations). > > > > Data Cube is the only other example that I could find where the same > names are used with upper and lower case, but I haven't done a deep > investigation. > > > > I have no opinion either way but it may be good to listen to what > implementers say. > > > > Makx. > > > > > > > > From: Bill Roberts [mailto:bill@swirrl.com] > Sent: Friday, April 05, 2013 12:13 PM > To: public-gld-comments@w3.org > Subject: Re: dataset and Dataset > > > > I understand but disagree with Alasdair's point on potential confusion > between dataset and Dataset. The convention of lower case for predicate > and upper case for class (usually the range of the corresponding > predicate) is now quite well established and is quite easy for new > people to learn - because it is widely used. So sticking to this > approach seems fine to me. > > > > Bill > > > > > > B > > > > > > -- Phil Archer http://philarcher.org/ +44 (0)7887 767755 @philarcher1
Received on Friday, 5 April 2013 11:37:52 UTC