Re: [mdt-papyrus.dev] Standard Profile

["SCHNEKENBURGER Remi 211865" <Remi.SCHNEKENBURGER@xxxxxx>]

Hi,

I would prefer different names for the various elements:
- the plugin is a bundle that proposes some documentation profile. For me, 'org.eclipse.papyrus.uml.profile' sounds like a plugin that handles UML profiles for Papyrus. Why not '{oep}.documentation.profile' for example? Or perhaps your goal is to propose some other extensions to this profile, not related to documentation?
- the profile itself is a profile defining a language for documentation: Why not 'Documentation' instead of 'Papyrus'? 

Otherwise, I do agree with this idea ;-)

Regards,
Rémi

-----Message d'origine-----
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de GERARD Sebastien 166342
Envoyé : vendredi 3 décembre 2010 11:15
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Standard Profile

Hi Mathieu,

I second this idea. One question on the Papyrus Documentation Profile: about the properties of the Documentation stereotype, there is currently the author property. Do you think adding additional properties, such as affiliation, date, ... ?

Thanks,
Cheers... Sébastie,.




-----Message d'origine-----
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Mathieu Velten Envoyé : mercredi 1 décembre 2010 17:36 À : mdt-papyrus.dev@xxxxxxxxxxx Objet : [mdt-papyrus.dev] Standard Profile

Hello all,

I am currently working on a documentation mechanism similar to topcased one.
To embed the documentation in the meta-model, I wrote a generic mechanism with an extension point. The default implementation uses eAnnotation like in topcased (which can be used on notation Diagram for example), however the uml implementation uses a profile to store documentation in a stereotyped comment.

So I am suggesting to create a Papyrus standard profile to embed cleanly Papyrus-related informations into the uml model.

You can find attached a first version that I am currently using in the documentation code.

Mathieu