BACM11 — OWL TTL does not represent composition properly

The MOF XMI owns_0 association is translated to an owl:ObjectProperty that is used with appropriate cardinalities in object property restriction axioms. But there is nothing that indicates that the association and its object property restrictions should have the cascading delete semantics. In the MOF2RDF specification, this is indicated by marking the object property as a subproperty of a "well-known" object property named "hasPart". The OWL version of BACM should follow this pattern.

Declare the owns_o object property as a subproperty of MOFSupport:hasPart

The OMG MOF2RDF ontology defines a sub-ontology MOFSupport which defines hasPart as an owl:ObjectProperty indicating that individuals in the range of this object property are existence-dependent on an individual in the domain. OWL 2 lacks a proper notion of existence dependency and reasoners cannot execute or validate this requirement, but a query or a subsumption reasoner can identity sub-properties of this property and drive an external agent to maintain the constraint.