Hi Thomas,
I agree with all your remarks.
Though concerning the remark below (a top concept having a broader concept) though, I would like to nuance.
- SKOS though leaves this open as it allows to represent directed graphs where top concepts are just entry points.
(I do not know if there are useful applications for this.)
See: http://www.w3.org/TR/skos-reference/#L2446 <http://www.w3.org/TR/skos-reference/%23L2446>
- For common hierarchical schemes and thesauri (standard ISO 25964) indeed indicate that a top concept cannot be a narrower concept of any other concept.
(Validation rules may differ per application. Uniqueness preferred labels per language is another such characteristic.)
Kind Regards,
Johan De Smedt
Chief Technology Officer
mail: <mailto:johan.de-smedt@tenforce.com> johan.de-smedt@tenforce.com
mobile: +32 477 475934
mail-TenForce
From: Thomas Francart [mailto:thomas.francart@sparna.fr]
Sent: Tuesday, 03 September, 2013 19:51
To: oreste.signore@isti.cnr.it
Cc: SKOS
Subject: Re: skos:hasTopConcept mandatory?
Hello
[JDS:>] […cut…]
Is it acceptable that a TopConcept is narrower than another Concept/TopConcept?
Certainly not. If a top-level concept is moved down the hierarchy, its topConceptOf/hasTopConcept properties should be deleted.
[...cut…].
Thomas
[1] SKOS Play : http://labs.sparna.fr/skos-play/
--
Thomas Francart - Sparna
Consultant Indépendant
Data, Sémantique, Contenus, Connaissances
web : http://sparna.fr, blog : http://francart.fr
Tel : +33 (0)6.71.11.25.97
Fax : +33 (0)9.58.16.17.14
Skype : francartthomas
