Re: [Proposal][SKOS-Core] handling top concepts

If you did this would you risk losing any programming benefits of topconcept
for schmes that have several parallel hierarchies?
Doug

----- Original Message ----- 
From: "Miles, AJ (Alistair) " <A.J.Miles@rl.ac.uk>
To: "'Dan Brickley'" <danbri@w3.org>
Cc: <public-esw-thes@w3.org>
Sent: Wednesday, August 04, 2004 5:27 PM
Subject: RE: [Proposal][SKOS-Core] handling top concepts


>
> > Thanks, this identifies a discomfort I've had w/ interactions between
> > 'top concept' notion and thesaurus mixing. At heart you're saying
> > 'top concept' is a relation between a a scheme/dataset/thesaurus and
> > a concept. Makes sense to me.
> >
> > So would this be:
> >
> > <owl:FunctionalProperty
> > rdf:about="http:///....../skos/core#hasTopConcept"/>
> >
> > ie. anything that has a skos:hasTopConcept has only one such thing?
> >
>
> Thanks Dan.
>
> The original idea was that a scheme has several skos:hasTopConcept
> properties, pointing to the top level concepts for that scheme (i.e. so
not
> functional).
>
> If we made skos:hasTopConcept functional, each scheme would have to be
> defined with a single root concept ... do you think it's worth doing it
that
> way?
>
> Al.
>

Received on Wednesday, 4 August 2004 12:40:50 UTC