- From: Michael Steidl via GitHub <sysbot+gh@w3.org>
- Date: Sun, 14 May 2017 08:51:08 +0000
- To: public-poe-archives@w3.org
re uses of SKOS My background: I'm maintaining the about 200 IPTC controlled vocabularies = concept schemes and IPTC has adopted SKOS. From that point of view: The ODRL ontology used both skos:Collection-s and skos:ConceptsScheme-s. I have to say frankly it is hard to make a clear distinction between both, I feel collections are closer to what an enumeration is in the programming context (a list of terms dedicated to a very specific use) and the concept scheme is a container of concepts - they may be used for specific purposes, but they don't have to. Actions by the WG: * It would be great if POE/ODRL could define for what purposes skos:Collection and skos:ConceptScheme should be used. * And: I'm not aware of any limitation of having a Concept only in a skos:Collection or skos:ConceptScheme - I think all Concepts should be contained by an ODRL Concept Scheme - and ODRL my have some. * ODRL defines a single skosConceptScheme "actions" and claims in free text that many actions - from anonymize to compensate - are included. But there not a single skos:inScheme - which is the corresponding definition by SKOS. And using skos:isTopConcept/skos:hasTopConcept is also of great help to clarify the hierarchy. (This was already pointed at by Antoine) -- GitHub Notification of comment by nitmws Please view or discuss this issue at https://github.com/w3c/poe/issues/164#issuecomment-301299155 using your GitHub account
Received on Sunday, 14 May 2017 08:51:14 UTC