There are several issues with the use of property redefinition to support restrictions in OWL. One of these involves the notion of property identity: OWL restrictions specify classes whose members have a restricted range of values for a particular property. In UML, property redefinition involves defining two distinct properties, potentially having the same name, one of which redefines the other, but that have unique identity and are related contextually via a constraint. Property identity is preserved in OWL, however there is only one uniquely defined property referenced in property restrictions.
In addition, the notation specified in the current ODM document (for all three kinds of restrictions existential and universal quantification as well as restricting the range of the property to a particular individual or data value) does not provide the ability to indicate whether property redefinition means that the restriction is necessary for class membership or necessary and sufficient for class membership. In OWL, restrictions are formed by creating an anonymous restriction class that limits the values possible for the range of a particular property, and then linking this restriction class to other class expressions, such as a named class, either through a generalization (rdfs:subClassOf), corresponding to necessary conditions for class membership, or equivalence relationship (owl:equivalentClass), corresponding to necessary and sufficient conditions. There should be a visible way for modellers to make this distinction in an ODM-compliant model. Such anonymous restrictions can be used with other class expressions to build up complex expressions useful for classification and identity reasoning (for example, does some individual x meet the criteria to be a member of y).
The proposed solution makes use of the «owlRestriction» stereotype, already available in the ODM specification, and augments that with a set of dependencies that connect the restriction to the property being restricted and to the class or individual/literal that provide the requisite source of value(s), as well as the use of either the «rdfsSubClassOf» stereotyped generalization or the «equivalentClass» stereotyped dependency or generalization that are already in the profile.
Per RTF discussion all of the stereotypes and notation for restrictions have been consolidated under a single heading, rather than distributing them across several sections. As a result, the recommendation, below, incorporates details for both object and data restrictions, for number as well as value restrictions, together in section 126.96.36.199, and eliminates sections 188.8.131.52 through 184.108.40.206.