Issue 6014: OpaqueExpression in CommonBehaviors (uml2-superstructure-ftf) Source: Honeywell (Mr. Steve Hickman, steve.hickman(at)honeywell.com) Nature: Clarification Severity: Significant Summary: OpaqueExpression in CommonBehaviors is titled "OpaqueExpression (from BasicBehaviors, specialized)". What does "specialized" mean in this context? There is no indication of inheritance from any other definition of OpaqueExpression. NOTE: the word "specialized" is used in the title of a number of concepts - in some cases the concepts are derived from other concepts of the same name from other package. This isn't always the case though. Resolution: Revised Text: Actions taken: July 24, 2003: received issue March 9, 2005: closed issue Discussion: In this context, “specialized” means that the metaclass BasicBehaviors::OpaqueExpression is specialized from an inherited metaclass OpaqueExpression, in this case, Kernel:: OpaqueExpression. While the text gives no indication from where a metaclass is specialized, this is done so throughout the document. Disposition: Closed, no change End of Annotations:===== From: webmaster@omg.org Date: 24 Jul 2003 11:51:32 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Steve Hickman Company: self mailFrom: shickman@ieee.org Notification: Yes Specification: UML 2.0 Superstructure Section: Chapter 7.3 FormalNumber: ad/03-04-01 Version: Third Revision RevisionDate: 4/1/03 Page: 354 Nature: Clarification Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; T312461; Guidant IE5 09302001 Win2000 Distribution; .NET CLR 1.0.3705) Description OpaqueExpression in CommonBehaviors is titled "OpaqueExpression (from BasicBehaviors, specialized)". What does "specialized" mean in this context? There is no indication of inheritance from any other definition of OpaqueExpression. NOTE: the word "specialized" is used in the title of a number of concepts - in some cases the concepts are derived from other concepts of the same name from other package. This isn't always the case though. Subject: RE: issue 6014 --UML 2.0 Superstructure FTF issues Date: Sat, 2 Aug 2003 09:52:08 -0400 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: issue 6014 --UML 2.0 Superstructure FTF issues Thread-Index: AcNV8RSXCBRMGvAsQs6SRVg0zYtDvgDC/Oig From: "Karl Frank" To: Cc: Steve is right about this. Origin: This is a defect that originated in the way the model was modified in the last round of reconciliation, at the request of Borland's Anders Ivnar, to recognize the difference between parsable OCL expressions and opague expressions. The UML 2 Superstructure metamodel was prior to that request, without such a distinction, and was altered, without removing the term "specialized". Prior to that change, the expression had indeed been specialized, but it was no longer such after it became "opaque" expression. Proposed resolution: The phrase "as specialized" should be removed here. A global search for similar defects of similar origin is recommended. - Karl Frank -----Original Message----- From: Juergen Boldt [mailto:juergen@omg.org] Sent: Tuesday, July 29, 2003 12:51 PM To: issues@omg.org; uml2-superstructure-ftf@omg.org Subject: issue 6014 --UML 2.0 Superstructure FTF issues From: webmaster@omg.org Date: 24 Jul 2003 11:51:32 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Steve Hickman Company: self mailFrom: shickman@ieee.org Notification: Yes Specification: UML 2.0 Superstructure Section: Chapter 7.3 FormalNumber: ad/03-04-01 Version: Third Revision RevisionDate: 4/1/03 Page: 354 Nature: Clarification Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; T312461; Guidant IE5 09302001 Win2000 Distribution; .NET CLR 1.0.3705) Description OpaqueExpression in CommonBehaviors is titled "OpaqueExpression (from BasicBehaviors, specialized)". What does "specialized" mean in this context? There is no indication of inheritance from any other definition of OpaqueExpression. NOTE: the word "specialized" is used in the title of a number of concepts - in some cases the concepts are derived from other concepts of the same name from other package. This isn't always the case though. ================================= Jürgen Boldt Director, Member Services Object Management Group 250 First Avenue, Suite 100 Needham, MA 02494 Tel. +1 781 444 0404 ext. 132 Fax: +1 781 444 0320 email: juergen@omg.org www www.omg.org ================================ :wq  Discussion: In this context, "specialized" means that the metaclass BasicBehaviors::OpaqueExpression is specialized from an inherited metaclass OpaqueExpression, in this case, Kernel::OpaqueExpression. While the text gives no indication from where a metaclass is specialized, this is done so throughout the document. A glance at the mdl file would also reveal the superclass. Disposition: Closed, no change OMG Issue No: 6014 Title: OpaqueExpression in CommonBehaviors Source: Honeywell (Mr. Steven Hickman, steve.hickman@honeywell.com) Summary: OpaqueExpression in CommonBehaviors is titled "OpaqueExpression (from BasicBehaviors, specialized)". What does "specialized" mean in this context? There is no indication of inheritance from any other definition of OpaqueExpression. NOTE: the word "specialized" is used in the title of a number of concepts - in some cases the concepts are derived from other concepts of the same name from other package. This isn't always the case though. Discussion: In this context, "specialized" means that the metaclass BasicBehaviors::OpaqueExpression is specialized from an inherited metaclass OpaqueExpression, in this case, Kernel::OpaqueExpression. While the text gives no indication from where a metaclass is specialized, this is done so throughout the document. A glance at the mdl file would also reveal the superclass. [Conrad: I guess this should be filed as a general issue. In activities, the superclasses are explicitly shown in the abstract syntax. Otherwise, there are on the package dependency diagrams to disambiguate, and in these won't work if two version of the same metaclass are specialized in the same package.] Disposition: Closed, no change