Closed FranckCo closed 12 years ago
skos:member can be used to express the link between an level and a more detailed level, this is consistent with the SKOS model since ClassificationLevel is a subclass of skos:Collection (cf. § 9.6.3 of the SKOS reference, http://www.w3.org/TR/skos-reference/#L3588).
Similarly, skos:inScheme can be used to express the relation a level and the classification it belongs to (§ 4.6.5, http://www.w3.org/TR/skos-reference/#L2805).
So now the question is rather : do we have operational needs that would necessitate more than that (eg. easily go from one level to the level above) ?
I close the issue for now, usage will show if we need other navigational properties.
There is a containsClassificationLevel property in the UML model, but I think we said that skos:member could do the job for relations between levels, and skos:inScheme for attachement of levels to a classification (ConceptScheme)