Issue 10778: Mismatch between Superstructure ptc/06-04-02 and XML Schema ptc/06-04-05 (uml2-rtf) Source: MID GmbH (Mr. Detlef Peters, d.peters(at)mid.de) Nature: Uncategorized Issue Severity: Summary: Possible Mismatch between Superstructure ptc/06-04-02 and XML Schema ptc/06-04-05 Please clarify the effects of the merge increments of 'Class' on its descendants, esp. on the 'Behavior' subtypes. IMHO the fact that 'behavior' inherits from 'Class (from Kernel)' implies that in turn it does NOT inherit features from 'BehavioredClassifier' or 'EncapsulatedClassifier' even on Compliance level L1. This would mean that e.g. an interaction may not have ownedPorts or ownedBehaviors, but nestedClassifier. If this is not the case, please clarify the precedence between the merge and inheritance constructs. Example: L1 (as seen in Fig. 2.2) merges Kernel, BasicBehaviors and InternalStructures and thus provides the 'Class', 'BehavioredClassifier' and 'EncapsulatedClassifier' constructs simultanously. - If inheritance comes before merging (which is what the diagrams suggest), 'Behavior' will have neither ownedPorts nor ownedBehaviors. - If merging comes before inheritance (which is what the XSD suggests), 'Behavior' will both have ownedPorts and ownedBehaviors. In the second case, the question arises that if even in L1 the three constructs mentioned above are provided, why does 'Behavior' not simply inherit from 'Class (from StructuredClasses)', directly being an EncapsulatedClassifier? Resolution: Revised Text: Actions taken: February 16, 2007: received issue Discussion: End of Annotations:===== te: Fri, 16 Feb 2007 09:45:26 +0100 From: Detlef Peters Organization: MID GmbH User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) To: issues@omg.org Cc: omg@mid.de Subject: Issue on UML 2.1 Superstructure X-Spam-Score: X-Spam-Report: X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at omg.org Possible Mismatch between Superstructure ptc/06-04-02 and XML Schema ptc/06-04-05 Please clarify the effects of the merge increments of 'Class' on its descendants, esp. on the 'Behavior' subtypes. IMHO the fact that 'behavior' inherits from 'Class (from Kernel)' implies that in turn it does NOT inherit features from 'BehavioredClassifier' or 'EncapsulatedClassifier' even on Compliance level L1. This would mean that e.g. an interaction may not have ownedPorts or ownedBehaviors, but nestedClassifier. If this is not the case, please clarify the precedence between the merge and inheritance constructs. Example: L1 (as seen in Fig. 2.2) merges Kernel, BasicBehaviors and InternalStructures and thus provides the 'Class', 'BehavioredClassifier' and 'EncapsulatedClassifier' constructs simultanously. - If inheritance comes before merging (which is what the diagrams suggest), 'Behavior' will have neither ownedPorts nor ownedBehaviors. - If merging comes before inheritance (which is what the XSD suggests), 'Behavior' will both have ownedPorts and ownedBehaviors. In the second case, the question arises that if even in L1 the three constructs mentioned above are provided, why does 'Behavior' not simply inherit from 'Class (from StructuredClasses)', directly being an EncapsulatedClassifier? Best regards, Detlef Peters -- MID Enterprise Software Solutions GmbH Dipl.-Inf.(Univ.) Detlef Peters Senior Software Engineer Eibacher Hauptstr. 141 90451 Nürnberg Telefon: +49 911-968 36-19 Fax : +49 911-968 36-10 E-Mail : d.peters@mid.de WWW : http://www.mid.de _________________________________________________________________________ Diese E-Mail (ggf. nebst Anhang) enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail (and any attachment/s) contains confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden. _________________________________________________________________________