Issue 6023: On page 140, the title for Parameter is "Parameter (Collaboration, as speci (uml2-superstructure-ftf) Source: (, ) Nature: Clarification Severity: Significant Summary: On page 140, the title for Parameter is "Parameter (Collaboration, as specialized)". This doesn't seem correct. The only prior definition of Parameter is on p 50, which is in the Kernel. The only way to "specialize" something appears to be when you want to add relationships to a concept that has been defined in a different package. I believe the more correct label should be "Parameter (from Kernel, as specialized)". Further, the abstract syntax diagram on page 128 should indicate that Parameter comes from the definition in the the Kernel. This may require deriving a new Parameter metaclass from the Kernel Parameter metaclass just so it can also be derived from ConnectableElement. Resolution: Revised Text: Actions taken: July 27, 2003: received issue March 9, 2005: closed issue Discussion: In this context, “specialized” means that the metaclass Collaboration::Parameter is specialized from an inherited metaclass Parameter, in this case, Kernel::Parameter. 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 End of Annotations:===== From: webmaster@omg.org Date: 27 Jul 2003 12:23:47 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Steve Hickman Company: self mailFrom: shickman@ieee.org Notification: Yes Specification: UML 2.0 Superstructure Section: Chapter 1 &3 FormalNumber: ad/03-04-01 Version: Third Revision RevisionDate: 4/1/03 Page: 50,140, 128 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 On page 140, the title for Parameter is "Parameter (Collaboration, as specialized)". This doesn't seem correct. The only prior definition of Parameter is on p 50, which is in the Kernel. The only way to "specialize" something appears to be when you want to add relationships to a concept that has been defined in a different package. I believe the more correct label should be "Parameter (from Kernel, as specialized)". Further, the abstract syntax diagram on page 128 should indicate that Parameter comes from the definition in the the Kernel. This may require deriving a new Parameter metaclass from the Kernel Parameter metaclass just so it can also be derived from ConnectableElement. Discussion: In this context, "specialized" means that the metaclass Collaboration::Parameter is specialized from an inherited metaclass Parameter, in this case, Kernel::Parameter. 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