Issue 5954: MOF requires Associations to be Named (deployment-ftf) Source: Zuehlke Engineering (Mr. Frank Pilhofer, fpilhofer2008(at)gmail.com) Nature: Uncategorized Issue Severity: Summary: This is an editorial issue for the Deployment FTF: MOF requires that all associations and association ends be named. The model conventions section should mention default names even if they are suppressed in the diagrams. Proposed resolution: In section 3.3, "Model Diagram Conventions", rewrite paragraphs 4 ("Role names on association ends ..."), 5 ("Role names at the navigable end ..."), 6 ("If a role names is suppressed ...") and 7 ("If an association name is suppressed ...") to read Role names on associations are made explicit wherever they are expected to appear in generated code, e.g. as an interface's attribute name. Role names at the navigable end of a derived association are normally suppressed. Therefore, if the role name at the navigable end of an association is suppressed, the association is derived. If a role name is suppressed at the end of an association, the name of the type at the association end, starting with a lowercase character, is used as the role name. This is the same implicit rule as in OCL. Implicit association names are used throughout the model. For unidirectional associations, the name of the class at the source plus an underscore plus the name of the navigable end is used as the name of the association. For bidirectional associations, the concatenation of the class names at both ends, in alphabetical order, with an underscore inbetween, is used as the name of the association. Resolution: Revised Text: Actions taken: June 19, 2003: received issue Discussion: End of Annotations:===== Subject: MOF requires Associations to be Named Date: Thu, 19 Jun 2003 09:55:52 -0400 Thread-Topic: MOF requires Associations to be Named Thread-Index: AcM2an8jJYPRTohATCuhoKBh4fm28A== From: "Pilhofer, Frank" To: Cc: X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id h5JDtOkM002450 This is an editorial issue for the Deployment FTF: MOF requires that all associations and association ends be named. The model conventions section should mention default names even if they are suppressed in the diagrams. Proposed resolution: In section 3.3, "Model Diagram Conventions", rewrite paragraphs 4 ("Role names on association ends ..."), 5 ("Role names at the navigable end ..."), 6 ("If a role names is suppressed ...") and 7 ("If an association name is suppressed ...") to read Role names on associations are made explicit wherever they are expected to appear in generated code, e.g. as an interface's attribute name. Role names at the navigable end of a derived association are normally suppressed. Therefore, if the role name at the navigable end of an association is suppressed, the association is derived. If a role name is suppressed at the end of an association, the name of the type at the association end, starting with a lowercase character, is used as the role name. This is the same implicit rule as in OCL. Implicit association names are used throughout the model. For unidirectional associations, the name of the class at the source plus an underscore plus the name of the navigable end is used as the name of the association. For bidirectional associations, the concatenation of the class names at both ends, in alphabetical order, with an underscore inbetween, is used as the name of the association. Subject: Re: issue 5954 Date: Mon, 7 Jul 2003 13:53:43 -0400 Thread-Topic: issues 5953 - 5955 -- Deployment FTF issues Thread-Index: AcM7XESXAvHtUadGEdeMjQCgyTbmFwJU2daA From: "Pilhofer, Frank" To: Cc: X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id h67HqBkM024245 This is an updated proposed resolution for deployment-ftf issue 5954: In section 3.3, "Model Diagram Conventions", rewrite paragraphs 4 ("Role names on association ends ..."), 5 ("Role names at the navigable end ..."), 6 ("If a role names is suppressed ...") and 7 ("If an association name is suppressed ...") to read The name of an AssociationEnd is suppressed in a diagram if and only if the AssociationEnd is not a referencedEnd for any Reference. Therefore, if the name of an AssociationEnd is not suppressed, then the class at the otherEnd of the association contains a Reference with this AssociationEnd as its referencedEnd. If the name of an AssociationEnd is suppressed, the name of the AssociationEnd's type, but with a lowercase character, is used as the AssociationEnd's name. (This is the same implicit rule as in OCL.) Implicit association names are used throughout the model. For unidirectional associations (where exactly one AssociationEnd is navigable), the name of the class at the source (non-navigable) end plus an underscore plus the name of the navigable end is used as the name of the association. For bidirectional associations, the concatenation of the class names at both ends, in alphabetical order, with an underscore inbetween, is used as the name of the association. (The model does not contain associations with two non-navigable AssociationEnds.) Subject: Updated proposed resolution for issue 5954 Date: Wed, 23 Jul 2003 17:10:11 -0400 Thread-Topic: issue 5954 Thread-Index: AcNEsgFdNOq/JrCNEdeMjQCgyTbmFwMrD7sg From: "Pilhofer, Frank" To: X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id h6NL74kM007857 This is an update with the amendments made in today's telecon: The resolution for issue 5954 was accepted with some updates on the word smithing: "if the name of an AssociationEnd is not suppressed" is to be changed to "if the name of an AssociationEnd is present" to sound more positive. The sentence "Implicit association names are used throughout the model" was changed to "Association names are suppressed in diagrams, default names are used throughout the model." Original issue: MOF requires that all associations and association ends be named. The model conventions section should mention default names even if they are suppressed in the diagrams. Updated proposed resolution: In section 3.3, "Model Diagram Conventions", rewrite paragraphs 4 ("Role names on association ends ..."), 5 ("Role names at the navigable end ..."), 6 ("If a role names is suppressed ...") and 7 ("If an association name is suppressed ...") to read The name of an AssociationEnd is suppressed in a diagram if and only if the AssociationEnd is not a referencedEnd for any Reference. Therefore, if the name of an AssociationEnd is present, then the class at the otherEnd of the association contains a Reference with this AssociationEnd as its referencedEnd. If the name of an AssociationEnd is suppressed, the name of the AssociationEnd's type, but with a lowercase character, is used as the AssociationEnd's name. (This is the same implicit rule as in OCL.) Association names are suppressed in diagrams, default names are used throughout the model. For unidirectional associations (where exactly one AssociationEnd is navigable), the name of the class at the source (non-navigable) end plus an underscore plus the name of the navigable end is used as the name of the association. For bidirectional associations, the concatenation of the class names at both ends, in alphabetical order, with an underscore inbetween, is used as the name of the association. (The model does not contain associations with two non-navigable AssociationEnds.)