COMMONS13 — StructuredCollections ontology misnamed

It's counterintuitive that the class StructuredCollection is not in the ontology StructuredCollections. It breaks the naming pattern that an ontology is named after its principle class.

StructuredCollections ontology misnamed

The issue states that there is a requirement that an ontology in Commons must include a class that has the same name as the ontology, and that as a consequence, this ontology is misnamed.

There are other cases where we have expanded on a concept and created a subordinate ontology that does not include the class of the same name, and we should be able to continue doing this without the constraint. If, for example, a particular community needs an expansion on some concept, we would add that new ontology expanding on the higher level, but not necessarily move the concept to the lower level. There are cases where people may need the notion of a structured collection but not the library of kinds of structured collections that might be useful for some use case.

Ontology renaming is quite disruptive, in fact, for people already using it, and should be avoided to the degree possible. The same is true for naming of concepts, although one can argue for doing that if it is appropriate for modularization or to create a higher-level concept on which multiple lower level concepts depend for interoperability. This is not that case, howevere.