Code lists should be represented as skos:ConceptSchemes

[clange]

For better reusability and tool support (e.g., https://fcp.vse.cz/iga-hybrid/), our code lists should not only be implemented by having multiple individuals of the same class, but with a redundant SKOS structure. We hardly ever even make explicit use of SKOS – Frequency is the only example I could find. That is, in addition to

ids:Foo a owl:Class. 
ids:FOO a ids:Foo. 

it would be good to have

ids:Foo a owl:Class, skos:ConceptScheme .
 
ids:FOO a ids:Foo, skos:Concept ;
  skos:inScheme ids:Foo . 

[riannella]

I would strongly support this suggestion. Adding SKOS is important for vocab tool support.