[Proposal][SKOS-Core] handling top concepts

This is a proposal in relation to the requirement outlined in [1].

To support identification of top concepts in situations where concepts may
be members of more than one concept scheme, I suggest the following actions:

1. The skos:TopConcept class be deprecated. 
2. A new property skos:hasTopConcept be added, with domain
skos:ConceptScheme and range skos:Concept.

See also [2].

Al.

[1] http://lists.w3.org/Archives/Public/public-esw-thes/2004Aug/0001.html
[2] http://esw.w3.org/topic/SkosDev_2fSkosCore_2fTopConcepts

---
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

Received on Tuesday, 3 August 2004 12:31:59 UTC