Issue 17338: ODM Metamodel takes a different approach to OWL restrictions from the Profile (and indeed from OWL): (odm-rtf) Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com) Nature: Uncategorized Issue Severity: Summary: The ODM Metamodel takes a different approach to OWL restrictions from the Profile (and indeed from OWL): the Profile has a single stereotype Restriction whereas the Metamodel has 6 different subclasses depending on the type of restriction: HasValueRestriction, AllValuesFromRestriction, CardinalityRestriction etc. It would be more consistent if the metamodel had only a single class, though this would necessitate constraints on the properties. Resolution: Revised Text: Actions taken: April 25, 2012: received issue Discussion: Significant changes to the ODM metamodel have occurred since version 1.0. These changes had a broader scope than restrictions, Subsequent analysis of the metamodel is anticipated to include restrictions. Resolutions against issue 17338 are deferred until RTF 1.2. Disposition: Deferred End of Annotations:===== ubject: Issue on ODM Date: Wed, 25 Apr 2012 09:37:31 -0700 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue on ODM Thread-Index: Ac0jAa9Qpu5WpOD6TNi7s1Bcn43wGw== From: "Pete Rivett" To: Cc: The ODM Metamodel takes a different approach to OWL restrictions from the Profile (and indeed from OWL): the Profile has a single stereotype Restriction whereas the Metamodel has 6 different subclasses depending on the type of restriction: HasValueRestriction, AllValuesFromRestriction, CardinalityRestriction etc. It would be more consistent if the metamodel had only a single class, though this would necessitate constraints on the properties. -- Pete Rivett (pete.rivett@adaptive.com) CTO, Adaptive Inc 65 Enterprise, Aliso Viejo, CA 92656 cell: +1 949 338 3794 Follow me on Twitter @rivettp or http://twitter.com/rivettp