- From: Miles, AJ (Alistair) <A.J.Miles@rl.ac.uk>
- Date: Thu, 13 May 2004 19:06:01 +0100
- To: 'Bernard Vatant' <bernard.vatant@mondeca.com>, public-esw-thes@w3.org
Hi Bernard, Er ... oops! I always intended skos:TopConcept to be a sub-class of skos:Concept. I'm going to change that asap. Leonard - yes you are right, a top concept is just a concept without any broader concepts. I originally removed the TopConcept class from early versions of the SKOS-Core schema (we inherited it from the TIF schema that was the early basis for SKOS), for exactly this reason - I thought it was redundant. However it is convenient from a programming point of view to have a TopConcept class, so applications can locate the top concepts directly, and not have to discover the top concepts dynamically by examining all of the concepts. Al. --- Alistair Miles Research Associate CCLRC - Rutherford Appleton Laboratory Building R1 Room 1.60 Fermi Avenue Chilton Didcot Oxfordshire OX11 0QX United Kingdom Email: a.j.miles@rl.ac.uk Tel: +44 (0)1235 445440 > -----Original Message----- > From: public-esw-thes-request@w3.org > [mailto:public-esw-thes-request@w3.org]On Behalf Of Bernard Vatant > Sent: 13 May 2004 17:47 > To: public-esw-thes@w3.org > Subject: skos:TopConcept > > > > > skos:TopConcept is not defined as a subclass of skos:Concept > > Why is it so? > > Bernard Vatant > Senior Consultant > Knowledge Engineering > Mondeca - www.mondeca.com > bernard.vatant@mondeca.com > >
Received on Thursday, 13 May 2004 14:13:14 UTC