Issue 16507: Property Inherence Hierarchy (sacm-rtf) Source: MITRE (Mr. Samuel Redwine, samredwine(at)verizon.net) Nature: Revision Severity: Significant Summary: A simple, natural and appropriate set of properties would have Property (abstract?) inheriting from Assertion (or less preferably ModelElement) and having ModelElementProperty, RepesentedObjectProperty, Event, and Timing inheriting from it (Property) and appropriately associated. Artifacts and DomainObjects would use RepesentedObjectProperty’s. The two classes of properties are needed to allow properties associated with a model element and those associated with what it represents to be distinguished. Likewise ModelElementEvent and RepesentedObjectEvent inherit from Event. What type of event timing an instance is relevant to will be clear from what it is associated with. CM events and properties for both model elements and what they represent could be treated within this approach. Alternately, a usable set of properties could have Property inheriting from ModelElement and having ModelElementProperty, ArtifactProperty, DomainObjectProperty, Event, and Timing inheriting from it and appropriately associated. The three classes of properties are needed to allow properties associated with a model element and what it represents to be distinguished. Likewise ModelElementEvent, ArtifactEvent, and DomainObjectEvent inherit from Event. What type of event timing is relevant to will be clear from what it is associated with. CM events and properties could be treated likewise. Resolution: Revised Text: Actions taken: August 25, 2011: received issue Discussion: Covered above by reconsideration of reintroducing property abstract class. This is a unification between ARM and SAEM that cannot be achieved at this stage - Defer to RTF Disposition: Deferred End of Annotations:===== m: webmaster@omg.org Date: 25 Aug 2011 13:11:23 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Samuel T. Redwine, Jr. Company: Sam Redwine Consulting mailFrom: samredwine@ieee.org Notification: Yes Specification: Argumentation Metamodel (ARM) Section: June Day 2 Diagram FormalNumber: ptc/2010-08-36 Version: FTF - Beta 1 RevisionDate: August 2010 Page: All Title: Property Inherence Hierarchy Nature: Revision Severity: Significant test: 3qw8 B1: Report Issue Description: A simple, natural and appropriate set of properties would have Property (abstract?) inheriting from Assertion (or less preferably ModelElement) and having ModelElementProperty, RepesentedObjectProperty, Event, and Timing inheriting from it (Property) and appropriately associated. Artifacts and DomainObjects would use RepesentedObjectProperty.s. The two classes of properties are needed to allow properties associated with a model element and those associated with what it represents to be distinguished. Likewise ModelElementEvent and RepesentedObjectEvent inherit from Event. What type of event timing an instance is relevant to will be clear from what it is associated with. CM events and properties for both model elements and what they represent could be treated within this approach. Alternately, a usable set of properties could have Property inheriting from ModelElement and having ModelElementProperty, ArtifactProperty, DomainObjectProperty, Event, and Timing inheriting from it and appropriately associated. The three classes of properties are needed to allow properties associated with a model element and what it represents to be distinguished. Likewise ModelElementEvent, ArtifactEvent, and DomainObjectEvent inherit from Event. What type of event timing is relevant to will be clear from what it is associated with. CM events and properties could be treated likewise.