- From: Alistair Miles <alistair.miles@zoo.ox.ac.uk>
- Date: Wed, 1 Oct 2008 17:10:53 +0100
- To: "Houghton,Andrew" <houghtoa@oclc.org>
- Cc: Antoine Isaac <aisaac@few.vu.nl>, public-swd-wg@w3.org
> Actually I wasn't suggesting a new class for TopConcept, but a mechanism for specifying that a skos:Concept is a top concept. Something like: > > <skos:Concept rdf:about="concept URI"> > <skos:isTopConcept rdf:resource="in-scheme URI" /> > </skos:Concept> > > skos:isTopConcept could be an inverse of skos:hasTopConcept in the skos:ConceptScheme. This way you could specify a top concept where it makes the most sense. Yes, this is what skos:topConceptOf is intended for, e.g. <skos:Concept rdf:about="MyConcept"> <skos:topConceptOf rdf:resource="MyScheme" /> </skos:Concept> Does this work for you? Cheers, Alistair. -- Alistair Miles Senior Computing Officer Image Bioinformatics Research Group Department of Zoology The Tinbergen Building University of Oxford South Parks Road Oxford OX1 3PS United Kingdom Web: http://purl.org/net/aliman Email: alistair.miles@zoo.ox.ac.uk Tel: +44 (0)1865 281993
Received on Wednesday, 1 October 2008 16:11:33 UTC