BACM11 — OWL translates "generalizes_0" association incorrectly

BACM has this as an association prototype with semantics of inheritance between instances (that are also classes) to conform to MOF. RDFS already has the subClassOf and subPropertyOf predicates and generalizes_0 should be translated into one of these predicates.

The generalizes_0 association in MOF should not be translated into OWL

The OWL 2 ontology language already has generalization as a primitive, allowing both rdfs:subClassOf and rdfs:subPropertyOf as predicates in the language. Generalizes_0 is a meta-association whose instances would be used by modelers to represent generalization between two model elements. The BACM OWL ontology does not distinguish meta- and model levels and model instancing is effected by specializing meta-classes and meta-properties as model classes and model properties, using the existing RDFS predicates. Removing generalizes_0 from the set of meta-associations translated into OWL does not reduce the representation capabilities of the metamodel and its ontology. Translating it as an object property gives the wrong semantics. The Python program that generates the OWL ontology from the MOF XMI is changed to eliminate the translation of this association into OWL.