[news.eclipse.modeling.mdt.uml2] Re: Creating Stereotype extending Assoc

["Kenn Hussey" <Kenn.Hussey@xxxxxxxxxxxxxxx>]

Vlad,

James and I already wrote an article on this topic - see 
http://www.eclipse.org/modeling/mdt/uml2/docs/articles/Customizing_UML2_Which_Technique_is_Right_For_You/article.html. 
In it, we refer to the use of keywords as "featherweight" extensions. Take a 
look and let us know your thoughts.

Kenn

"Vlad Varnica" <varnica@xxxxxxxxxx> wrote in message 
news:ab1dcbf4dc417c2f6686e513ee3f2c30$1@xxxxxxxxxxxxxxxxxx
> Kenn,
>
> If you look the property view or inside the xmi then you can certainly see 
> the difference but at Profile metaclass and UML graphical icon design 
> there is no difference between property and association ends.
> This is what I was trying to explain.
> The use of "association ends" keyword or stereotype was just an example 
> because the user wanted to add a stereotype on the association ends. 
> Adding the name "association ends" as stereotype or keyword is I agree 
> stupid :-)
>
> The interesting question could be: When to use stereotype or Keywords in a 
> project ?
> What difference do you see between them ?
> Should a stereotype be always related to a profile ?
> Is-it recommended to use stereotypes or keywords in a project ?
>
> This newsgroup is about EMF therefore I suggest we start a new talk on the 
> UML2 newsgroup.
> Thanks,
>
> Vlad,
>
>