Issue 18275: Error in Dependency notation example (uml25-ftf) Source: Ivar Jacobson International AB (Mr. Ed Seidewitz, eseidewitz(at)ivarjacobson.com) Nature: Uncategorized Issue Severity: Summary: Specification: OMG Unified Modeling Language (OMG UML), Version 2.5 FTF – Beta 1 (ptc/2012-10-24) Subclause: 7.7.4 In Figure 7.18, the name within the guillemets should be a stereotype name, not the dependency name. The dependency name should be separate from the stereotype. Resolution: Revised Text: Actions taken: November 20, 2012: received issue Discussion: End of Annotations:===== m: Ed Seidewitz To: "issues@omg.org" Date: Tue, 20 Nov 2012 16:51:28 -0500 Subject: Error in Dependency notation example Thread-Topic: Error in Dependency notation example Thread-Index: Ac3HaTHwchpbc3apQkepR1l/o9KRhw== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-Mailprotector-Decision: deliver X-Mailprotector-Connection: TLSv1|[10.1.50.225]|10.1.50.225|outbound.mailprotector.net|0.0|0.0|0|||0|0|0|0 X-Mailprotector-Results: null_ptr clean X-Mailprotector-Score: 40 X-Mailprotector-IP-Analysis: 0, 10.1.50.225, Ugly c=0.779069 p=-0.958333 Source White X-Mailprotector-Scan-Diagnostics: 0-0-0-4658-c X-Mailprotector-ID: cbeb943d-2eac-4ff6-8a3a-d4ff2b4d03e5 Specification: OMG Unified Modeling Language (OMG UML), Version 2.5 FTF . Beta 1 (ptc/2012-10-24) Subclause: 7.7.4 In Figure 7.18, the name within the guillemets should be a stereotype name, not the dependency name. The dependency name should be separate from the stereotype.