inScheme v. OWL set semantics

If you create a concept scheme with concepts and make it public, you
wouldn't want anyone to arbitrarly assert:
<http://myconcept> <skos:inScheme> <http://publishedScheme> .

But theres no way in SKOS to describe a class (a skos:ConceptScheme),
completly specified with an enumeration of it's members (skos:Concept). 

An enumerated class in OWL seems to be a better way to say that these
concepts belongs to this vocabulary. This would obsolete the <skos:inScheme>
property and give a catalog the knowledge of scheme and concepts clearly
defined in one place -- in the schema and not among the instances.

- Jason