Issue 12249: MARTE name prefixes (marte-ftf) Source: Carleton University (Dr. Murray Woodside, cmw(at)sce.carleton.ca) Nature: Uncategorized Issue Severity: Summary: There is no consistent convention followed in the beta document for naming of stereotypes and their attributes, and this has been pointed out in other issues. Some chapters use a prefix for the chapter, such as Pa or pa for performance analysis, Grm or grm for General Resource Model, etc. MOst do not. From the point of view of precision, fully qualified names are sufficient, but from the point of view of usability, the prefixes are very helpful, especially as MARTE is such a big profile and realtime is a cross-cutting concern. THat is (unlike sysml) the profile does not redefine UML or restrict it to the domain of realtime, but adds realtime info to a functional design. MARTE may be used with other profiles, possibly several at once. The usability issues are to identify the realtime stereotypes and attributes, and also to avoid cluttering the namespace. A stereotype attribute may become a property of an object and its name might conflict with a functional property. Users might avoid MARTE just to avoid the risk of this happening. Issue: Consistency in prefixes is desirable, either all stereotypes with prefix, or none. Usability is affected. Realtime concerns are pervasive and crosscutting in software, so flooding of the namespace could be a problem, including conflict with other profiles and with functional property names. Proposed resolution: Apply two or three prefixes to all stereotypes and attributes: mm for MARTE Modeling ma for MARTE Analysis possibly mc for MARTE Core. Where a stereotype is specialized from another one, a third letter could be used. Alternative proposal: Apply prefixes only to the analysis chapters, because these are more likely to be used outside the embedded system domain (e.g. for enterprise system QoS) and thus to be used with other stereotypes. For instance to specify requirements on delay. Resolution: In order to decide when we need to prefix the name of element, we propose to apply the following algorithm as much as possible: - When we define a stereotype which name may conflict with the UML2 metaclass the stereotype is extending. In this case, we prefix with the name of the sub-profile wherein the stereotype is defined. - When we define a stereotype generalizing an already defined stereotype of MARTE. In this case, we should use the name of the profile wherein the stereotype is defined to prefix this latter. - Finally, we should not use "_" between the prefix and the name of the prefix. This rule should apply also for the name of the concepts of the domain model. However, there is an exception to this rule: we will not rename the predefined NFP type (the one define in the MARTE library such as NFP-Real) because they are used all along the specification and the change will need too much work w.r.t. to the global interest to do it. Let's note that, we consider that that as an editorial issue and we will not provide the complete revised text for the resolution because it would be too big. The editor of the specification (Sebastien Gerard) will do the required modifications directly in the specification when integrating all other resolutions voted within this FTF2 Revised Text: Actions taken: February 28, 2008: received issue October 16, 2009: closed issue Discussion: End of Annotations:===== te: Thu, 28 Feb 2008 09:36:31 -0500 (EST) From: Murray Woodside Reply-To: cmw@sce.carleton.ca To: issues@omg.org Subject: MARTE name prefixes There is no consistent convention followed in the beta document for naming of stereotypes and their attributes, and this has been pointed out in other issues. Some chapters use a prefix for the chapter, such as Pa or pa for performance analysis, Grm or grm for General Resource Model, etc. MOst do not. From the point of view of precision, fully qualified names are sufficient, but from the point of view of usability, the prefixes are very helpful, especially as MARTE is such a big profile and realtime is a cross-cutting concern. THat is (unlike sysml) the profile does not redefine UML or restrict it to the domain of realtime, but adds realtime info to a functional design. MARTE may be used with other profiles, possibly several at once. The usability issues are to identify the realtime stereotypes and attributes, and also to avoid cluttering the namespace. A stereotype attribute may become a property of an object and its name might conflict with a functional property. Users might avoid MARTE just to avoid the risk of this happening. Issue: Consistency in prefixes is desirable, either all stereotypes with prefix, or none. Usability is affected. Realtime concerns are pervasive and crosscutting in software, so flooding of the namespace could be a problem, including conflict with other profiles and with functional property names. Proposed resolution: Apply two or three prefixes to all stereotypes and attributes: mm for MARTE Modeling ma for MARTE Analysis possibly mc for MARTE Core. Where a stereotype is specialized from another one, a third letter could be used. Alternative proposal: Apply prefixes only to the analysis chapters, because these are more likely to be used outside the embedded system domain (e.g. for enterprise system QoS) and thus to be used with other stereotypes. For instance to specify requirements on delay. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) Subject: RE: prefixes on stereotypes Date: Thu, 28 Feb 2008 10:34:26 +0100 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: prefixes on stereotypes thread-index: Ach30JLxEfnWt6cQRKWqFeTzyoGN7QCHGlZQ From: "GERARD Sebastien 166342" To: Cc: X-OriginalArrivalTime: 28 Feb 2008 09:34:27.0352 (UTC) FILETIME=[1C90C980:01C879ED] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id m1S9a88t008484 Hi Murray, There is no policy for prefixing the stereotype in MARTE. Do you have any suggestion? Séb -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : lundi 25 février 2008 18:05 À : GERARD Sebastien 166342 Objet : prefixes on stereotypes Sebastien, do we have a policy on prefixes? Some chapters were written assuming there was... If all prefixes need to be changed, the text changes can just be edits but the figures will need to be modified in detail. there is an issue already. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) Date: Thu, 28 Feb 2008 09:23:23 -0500 (EST) From: Murray Woodside Reply-To: cmw@sce.carleton.ca To: GERARD Sebastien 166342 Cc: marte-ftf@omg.org Subject: RE: prefixes on stereotypes I am not sure about prefixes on stereotypes. I thought at one time we had a policy, but clearly I was wrong about that. Apparently there is no OMG policy... the SPT prefixes were decided by the group tht defined the profile (e.g. Bran and Alan among others). They had the advantage of clearly identifying the realtime concerns. As more and more profiles are created, I expect that real-time will be a cross-cutting concern that will show up in many areas... robotics, telecom, corba, QoS for enterprise and workflow and business engineering. In some cases just for specifying delay requirements, at least to start with. Then the usability of the profile could be negatively affected by names of stereotypes but more particularly of attributes... it could generate naming conflicts against functional property names, in designs, and make people wary of using it. After all we have hundreds and maybe even thousands of stereotypes and attributes defined in MARTE. If someone loads the whole profile their stereotype and attribute menus will be swamped. A prefix per chapter is probably too much. We might consider two prefixes: mm for Marte Modeling ma for Marte Analysis (possibly also mc for MARTE Core?) And where one chapter specializes a stereotype from another, the specialized one might have a third letter, eg. map for specializing Step from GQAM to PAM. I know the editing implications are considerable, but the usability concerns are also serious. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) On Thu, 28 Feb 2008, GERARD Sebastien 166342 wrote: Hi Murray, There is no policy for prefixing the stereotype in MARTE. Do you have any suggestion? Séb -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : lundi 25 février 2008 18:05 À : GERARD Sebastien 166342 Objet : prefixes on stereotypes Sebastien, do we have a policy on prefixes? Some chapters were written assuming there was... If all prefixes need to be changed, the text changes can just be edits but the figures will need to be modified in detail. there is an issue already. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) Subject: RE: prefixes on stereotypes Date: Thu, 28 Feb 2008 15:33:43 +0100 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: prefixes on stereotypes thread-index: Ach6FX8M5pg5EnvQR2amAxWW5j4pAQAAUogQ From: "GERARD Sebastien 166342" To: Cc: X-OriginalArrivalTime: 28 Feb 2008 14:33:44.0305 (UTC) FILETIME=[EBBE5E10:01C87A16] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id m1SEZY88019925 FOR ALL: Please react to the Murray proposal, because we need a solid discussion on that and to agree on the result, because at the end it seems it is me that will have to edit all the involved changes... -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : jeudi 28 février 2008 15:23 À : GERARD Sebastien 166342 Cc : marte-ftf@omg.org Objet : RE: prefixes on stereotypes I am not sure about prefixes on stereotypes. I thought at one time we had a policy, but clearly I was wrong about that. Apparently there is no OMG policy... the SPT prefixes were decided by the group tht defined the profile (e.g. Bran and Alan among others). They had the advantage of clearly identifying the realtime concerns. As more and more profiles are created, I expect that real-time will be a cross-cutting concern that will show up in many areas... robotics, telecom, corba, QoS for enterprise and workflow and business engineering. In some cases just for specifying delay requirements, at least to start with. Then the usability of the profile could be negatively affected by names of stereotypes but more particularly of attributes... it could generate naming conflicts against functional property names, in designs, and make people wary of using it. After all we have hundreds and maybe even thousands of stereotypes and attributes defined in MARTE. If someone loads the whole profile their stereotype and attribute menus will be swamped. A prefix per chapter is probably too much. We might consider two prefixes: mm for Marte Modeling ma for Marte Analysis (possibly also mc for MARTE Core?) And where one chapter specializes a stereotype from another, the specialized one might have a third letter, eg. map for specializing Step from GQAM to PAM. I know the editing implications are considerable, but the usability concerns are also serious. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) On Thu, 28 Feb 2008, GERARD Sebastien 166342 wrote: > Hi Murray, > > There is no policy for prefixing the stereotype in MARTE. Do you have any suggestion? > > > Séb > > -----Message d'origine----- > De : Murray Woodside [mailto:cmw@sce.carleton.ca] > Envoyé : lundi 25 février 2008 18:05 > À : GERARD Sebastien 166342 > Objet : prefixes on stereotypes > > Sebastien, do we have a policy on prefixes? Some chapters were written > assuming there was... > > If all prefixes need to be changed, the text changes can just be edits but > the figures will need to be modified in detail. there is an issue already. > > Murray Woodside > > Distinguished Research Professor > Dept of Systems and Computer Engineering, > Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. > (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca > (http://www.sce.carleton.ca/faculty/woodside.html) > Date: Thu, 28 Feb 2008 09:36:31 -0500 (EST) From: Murray Woodside Reply-To: cmw@sce.carleton.ca To: issues@omg.org Subject: MARTE name prefixes There is no consistent convention followed in the beta document for naming of stereotypes and their attributes, and this has been pointed out in other issues. Some chapters use a prefix for the chapter, such as Pa or pa for performance analysis, Grm or grm for General Resource Model, etc. MOst do not. From the point of view of precision, fully qualified names are sufficient, but from the point of view of usability, the prefixes are very helpful, especially as MARTE is such a big profile and realtime is a cross-cutting concern. THat is (unlike sysml) the profile does not redefine UML or restrict it to the domain of realtime, but adds realtime info to a functional design. MARTE may be used with other profiles, possibly several at once. The usability issues are to identify the realtime stereotypes and attributes, and also to avoid cluttering the namespace. A stereotype attribute may become a property of an object and its name might conflict with a functional property. Users might avoid MARTE just to avoid the risk of this happening. Issue: Consistency in prefixes is desirable, either all stereotypes with prefix, or none. Usability is affected. Realtime concerns are pervasive and crosscutting in software, so flooding of the namespace could be a problem, including conflict with other profiles and with functional property names. Proposed resolution: Apply two or three prefixes to all stereotypes and attributes: mm for MARTE Modeling ma for MARTE Analysis possibly mc for MARTE Core. Where a stereotype is specialized from another one, a third letter could be used. Alternative proposal: Apply prefixes only to the analysis chapters, because these are more likely to be used outside the embedded system domain (e.g. for enterprise system QoS) and thus to be used with other stereotypes. For instance to specify requirements on delay. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) Subject: RE: prefixes on stereotypes Date: Thu, 28 Feb 2008 15:50:53 +0100 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: prefixes on stereotypes thread-index: Ach6FX8M5pg5EnvQR2amAxWW5j4pAQAAUogQAABTw2A= From: "ESPINOZA Huascar 218344" To: "GERARD Sebastien 166342" , Cc: X-OriginalArrivalTime: 28 Feb 2008 14:50:54.0538 (UTC) FILETIME=[51CF72A0:01C87A19] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id m1SEsAYv024289 I think that the current prefixes are ok (where used): sw = SRM hw = HWM ga= GQAM sa = SAM pa = PAM we should define others for the remining chapters: gr = GRM ap? = RTEMoCC tm = Time ... and probably modify/align others: nf (instead of nfp) = NFP I think that there is no benefits in adding an additional letter (m/a) for Modeling and Analysis. Regards, Huascar -----Message d'origine----- De : GERARD Sebastien 166342 Envoyé : jeudi 28 février 2008 15:34 À : marte-ftf@omg.org Cc : cmw@sce.carleton.ca Objet : RE: prefixes on stereotypes FOR ALL: Please react to the Murray proposal, because we need a solid discussion on that and to agree on the result, because at the end it seems it is me that will have to edit all the involved changes... -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : jeudi 28 février 2008 15:23 À : GERARD Sebastien 166342 Cc : marte-ftf@omg.org Objet : RE: prefixes on stereotypes I am not sure about prefixes on stereotypes. I thought at one time we had a policy, but clearly I was wrong about that. Apparently there is no OMG policy... the SPT prefixes were decided by the group tht defined the profile (e.g. Bran and Alan among others). They had the advantage of clearly identifying the realtime concerns. As more and more profiles are created, I expect that real-time will be a cross-cutting concern that will show up in many areas... robotics, telecom, corba, QoS for enterprise and workflow and business engineering. In some cases just for specifying delay requirements, at least to start with. Then the usability of the profile could be negatively affected by names of stereotypes but more particularly of attributes... it could generate naming conflicts against functional property names, in designs, and make people wary of using it. After all we have hundreds and maybe even thousands of stereotypes and attributes defined in MARTE. If someone loads the whole profile their stereotype and attribute menus will be swamped. A prefix per chapter is probably too much. We might consider two prefixes: mm for Marte Modeling ma for Marte Analysis (possibly also mc for MARTE Core?) And where one chapter specializes a stereotype from another, the specialized one might have a third letter, eg. map for specializing Step from GQAM to PAM. I know the editing implications are considerable, but the usability concerns are also serious. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) On Thu, 28 Feb 2008, GERARD Sebastien 166342 wrote: > Hi Murray, > > There is no policy for prefixing the stereotype in MARTE. Do you have any suggestion? > > > Séb > > -----Message d'origine----- > De : Murray Woodside [mailto:cmw@sce.carleton.ca] > Envoyé : lundi 25 février 2008 18:05 > À : GERARD Sebastien 166342 > Objet : prefixes on stereotypes > > Sebastien, do we have a policy on prefixes? Some chapters were written > assuming there was... > > If all prefixes need to be changed, the text changes can just be edits but > the figures will need to be modified in detail. there is an issue already. > > Murray Woodside > > Distinguished Research Professor > Dept of Systems and Computer Engineering, > Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. > (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca > (http://www.sce.carleton.ca/faculty/woodside.html) > Date: Thu, 28 Feb 2008 10:08:08 -0500 (EST) From: Murray Woodside Reply-To: cmw@sce.carleton.ca To: ESPINOZA Huascar 218344 Cc: GERARD Sebastien 166342 , marte-ftf@omg.org Subject: RE: prefixes on stereotypes In answer to Huascar, I take it that you do not feel that consistnecy in use of prefixes is so important. I was thinking of having only two or three different prefixes, instead of so many... but many is also a solution. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) On Thu, 28 Feb 2008, ESPINOZA Huascar 218344 wrote: I think that the current prefixes are ok (where used): sw = SRM hw = HWM ga= GQAM sa = SAM pa = PAM we should define others for the remining chapters: gr = GRM ap? = RTEMoCC tm = Time ... and probably modify/align others: nf (instead of nfp) = NFP I think that there is no benefits in adding an additional letter (m/a) for Modeling and Analysis. Regards, Huascar -----Message d'origine----- De : GERARD Sebastien 166342 Envoyé : jeudi 28 février 2008 15:34 À : marte-ftf@omg.org Cc : cmw@sce.carleton.ca Objet : RE: prefixes on stereotypes FOR ALL: Please react to the Murray proposal, because we need a solid discussion on that and to agree on the result, because at the end it seems it is me that will have to edit all the involved changes... -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : jeudi 28 février 2008 15:23 À : GERARD Sebastien 166342 Cc : marte-ftf@omg.org Objet : RE: prefixes on stereotypes I am not sure about prefixes on stereotypes. I thought at one time we had a policy, but clearly I was wrong about that. Apparently there is no OMG policy... the SPT prefixes were decided by the group tht defined the profile (e.g. Bran and Alan among others). They had the advantage of clearly identifying the realtime concerns. As more and more profiles are created, I expect that real-time will be a cross-cutting concern that will show up in many areas... robotics, telecom, corba, QoS for enterprise and workflow and business engineering. In some cases just for specifying delay requirements, at least to start with. Then the usability of the profile could be negatively affected by names of stereotypes but more particularly of attributes... it could generate naming conflicts against functional property names, in designs, and make people wary of using it. After all we have hundreds and maybe even thousands of stereotypes and attributes defined in MARTE. If someone loads the whole profile their stereotype and attribute menus will be swamped. A prefix per chapter is probably too much. We might consider two prefixes: mm for Marte Modeling ma for Marte Analysis (possibly also mc for MARTE Core?) And where one chapter specializes a stereotype from another, the specialized one might have a third letter, eg. map for specializing Step from GQAM to PAM. I know the editing implications are considerable, but the usability concerns are also serious. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) On Thu, 28 Feb 2008, GERARD Sebastien 166342 wrote: Hi Murray, There is no policy for prefixing the stereotype in MARTE. Do you have any suggestion? Séb -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : lundi 25 février 2008 18:05 À : GERARD Sebastien 166342 Objet : prefixes on stereotypes Sebastien, do we have a policy on prefixes? Some chapters were written assuming there was... If all prefixes need to be changed, the text changes can just be edits but the figures will need to be modified in detail. there is an issue already. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) X-IronPort-AV: E=Sophos;i="4.25,419,1199660400"; d="scan'208";a="23169725" Date: Thu, 28 Feb 2008 17:11:17 +0100 From: Frederic Mallet User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) To: ESPINOZA Huascar 218344 Cc: marte-ftf@omg.org, cmw@sce.carleton.ca Subject: Re: prefixes on stereotypes Some sterotypes are already very long and it is already very heavy to use them. Adding yet another prefix will not make things easier. Moreover, how are we suppose to deal with cross-cuttings with other profiles (with SysML for instance). We have taken some of their stereotypes, we have kept their names to be compliant even though they did not seem to be the most appropriate names. That will ask a tremendous amount of work from Sébastien and it may be faster to rewrite another profile. To conclude, I am not in favor of a general rule for that matter. Frederic. ESPINOZA Huascar 218344 a écrit : I think that the current prefixes are ok (where used): sw = SRM hw = HWM ga= GQAM sa = SAM pa = PAM we should define others for the remining chapters: gr = GRM ap? = RTEMoCC tm = Time ... and probably modify/align others: nf (instead of nfp) = NFP I think that there is no benefits in adding an additional letter (m/a) for Modeling and Analysis. Regards, Huascar -----Message d'origine----- De : GERARD Sebastien 166342 Envoyé : jeudi 28 février 2008 15:34 À : marte-ftf@omg.org Cc : cmw@sce.carleton.ca Objet : RE: prefixes on stereotypes FOR ALL: Please react to the Murray proposal, because we need a solid discussion on that and to agree on the result, because at the end it seems it is me that will have to edit all the involved changes... -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : jeudi 28 février 2008 15:23 À : GERARD Sebastien 166342 Cc : marte-ftf@omg.org Objet : RE: prefixes on stereotypes I am not sure about prefixes on stereotypes. I thought at one time we had a policy, but clearly I was wrong about that. Apparently there is no OMG policy... the SPT prefixes were decided by the group tht defined the profile (e.g. Bran and Alan among others). They had the advantage of clearly identifying the realtime concerns. As more and more profiles are created, I expect that real-time will be a cross-cutting concern that will show up in many areas... robotics, telecom, corba, QoS for enterprise and workflow and business engineering. In some cases just for specifying delay requirements, at least to start with. Then the usability of the profile could be negatively affected by names of stereotypes but more particularly of attributes... it could generate naming conflicts against functional property names, in designs, and make people wary of using it. After all we have hundreds and maybe even thousands of stereotypes and attributes defined in MARTE. If someone loads the whole profile their stereotype and attribute menus will be swamped. A prefix per chapter is probably too much. We might consider two prefixes: mm for Marte Modeling ma for Marte Analysis (possibly also mc for MARTE Core?) And where one chapter specializes a stereotype from another, the specialized one might have a third letter, eg. map for specializing Step from GQAM to PAM. I know the editing implications are considerable, but the usability concerns are also serious. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) On Thu, 28 Feb 2008, GERARD Sebastien 166342 wrote: Hi Murray, There is no policy for prefixing the stereotype in MARTE. Do you have any suggestion? Séb -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : lundi 25 février 2008 18:05 À : GERARD Sebastien 166342 Objet : prefixes on stereotypes Sebastien, do we have a policy on prefixes? Some chapters were written assuming there was... If all prefixes need to be changed, the text changes can just be edits but the figures will need to be modified in detail. there is an issue already. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) Subject: RE: prefixes on stereotypes Date: Thu, 28 Feb 2008 17:29:27 -0000 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: prefixes on stereotypes Thread-Index: Ach6FX8M5pg5EnvQR2amAxWW5j4pAQAAUogQAAXt0tA= From: "VanZandt, Lonnie" To: "GERARD Sebastien 166342" , Cc: Just as large-scale software systems forced the use of namespacing in (more primitive) languages such as C++ and in ad hoc ways in (totally unmodular) C, the lack of a required namespace convention for UML profiles will soon become an impediment to progress. That is, this assuredly is not an issue limited to MARTE and is an issue that affects all UML profiles. Do I want to have to refer to MARTE stereotypes with pervasive "mm" (or "marte", "gqam_", etc.) prefixes? Absolutely, not. I do want to somehow be able to contextually say "import MARTE", "with MARTE", etc. and to then be able to use unqualified identifiers when the context disambiguates the references and to be able to namespace qualify identifiers when the context is ambiguous. Lonnie VanZandt Field Applications Engineer Denver, CO Artisan Software Tools mobile: 720 201-1349 desk: 303 482-2943 lonnie.vanzandt@artisansw.com -------------------------------------------------------------------------------- From: GERARD Sebastien 166342 [mailto:Sebastien.GERARD@cea.fr] Sent: Thu 2/28/2008 7:33 AM To: marte-ftf@omg.org Cc: cmw@sce.carleton.ca Subject: RE: prefixes on stereotypes FOR ALL: Please react to the Murray proposal, because we need a solid discussion on that and to agree on the result, because at the end it seems it is me that will have to edit all the involved changes... -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : jeudi 28 février 2008 15:23 À : GERARD Sebastien 166342 Cc : marte-ftf@omg.org Objet : RE: prefixes on stereotypes I am not sure about prefixes on stereotypes. I thought at one time we had a policy, but clearly I was wrong about that. Apparently there is no OMG policy... the SPT prefixes were decided by the group tht defined the profile (e.g. Bran and Alan among others). They had the advantage of clearly identifying the realtime concerns. As more and more profiles are created, I expect that real-time will be a cross-cutting concern that will show up in many areas... robotics, telecom, corba, QoS for enterprise and workflow and business engineering. In some cases just for specifying delay requirements, at least to start with. Then the usability of the profile could be negatively affected by names of stereotypes but more particularly of attributes... it could generate naming conflicts against functional property names, in designs, and make people wary of using it. After all we have hundreds and maybe even thousands of stereotypes and attributes defined in MARTE. If someone loads the whole profile their stereotype and attribute menus will be swamped. A prefix per chapter is probably too much. We might consider two prefixes: mm for Marte Modeling ma for Marte Analysis (possibly also mc for MARTE Core?) And where one chapter specializes a stereotype from another, the specialized one might have a third letter, eg. map for specializing Step from GQAM to PAM. I know the editing implications are considerable, but the usability concerns are also serious. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) On Thu, 28 Feb 2008, GERARD Sebastien 166342 wrote: > Hi Murray, > > There is no policy for prefixing the stereotype in MARTE. Do you have any suggestion? > > > Séb > > -----Message d'origine----- > De : Murray Woodside [mailto:cmw@sce.carleton.ca] > Envoyé : lundi 25 février 2008 18:05 > À : GERARD Sebastien 166342 > Objet : prefixes on stereotypes > > Sebastien, do we have a policy on prefixes? Some chapters were written > assuming there was... > > If all prefixes need to be changed, the text changes can just be edits but > the figures will need to be modified in detail. there is an issue already. > > Murray Woodside > > Distinguished Research Professor > Dept of Systems and Computer Engineering, > Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. > (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca > (http://www.sce.carleton.ca/faculty/woodside.html) > Date: Thu, 28 Feb 2008 12:58:33 -0500 (EST) From: Murray Woodside Reply-To: cmw@sce.carleton.ca To: "VanZandt, Lonnie" Cc: GERARD Sebastien 166342 , marte-ftf@omg.org Subject: RE: prefixes on stereotypes Your viewpoint is clear, Lonnie, but there is no separate context for MARTE, separated from the functional context... that is the trouble with a pervasive non-functional apect like realtime. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) On Thu, 28 Feb 2008, VanZandt, Lonnie wrote: Just as large-scale software systems forced the use of namespacing in (more primitive) languages such as C++ and in ad hoc ways in (totally unmodular) C, the lack of a required namespace convention for UML profiles will soon become an impediment to progress. That is, this assuredly is not an issue limited to MARTE and is an issue that affects all UML profiles. Do I want to have to refer to MARTE stereotypes with pervasive "mm" (or "marte", "gqam_", etc.) prefixes? Absolutely, not. I do want to somehow be able to contextually say "import MARTE", "with MARTE", etc. and to then be able to use unqualified identifiers when the context disambiguates the references and to be able to namespace qualify identifiers when the context is ambiguous. Lonnie VanZandt Field Applications Engineer Denver, CO Artisan Software Tools mobile: 720 201-1349 desk: 303 482-2943 lonnie.vanzandt@artisansw.com ________________________________ From: GERARD Sebastien 166342 [mailto:Sebastien.GERARD@cea.fr] Sent: Thu 2/28/2008 7:33 AM To: marte-ftf@omg.org Cc: cmw@sce.carleton.ca Subject: RE: prefixes on stereotypes FOR ALL: Please react to the Murray proposal, because we need a solid discussion on that and to agree on the result, because at the end it seems it is me that will have to edit all the involved changes... -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : jeudi 28 février 2008 15:23 Ã. : GERARD Sebastien 166342 Cc : marte-ftf@omg.org Objet : RE: prefixes on stereotypes I am not sure about prefixes on stereotypes. I thought at one time we had a policy, but clearly I was wrong about that. Apparently there is no OMG policy... the SPT prefixes were decided by the group tht defined the profile (e.g. Bran and Alan among others). They had the advantage of clearly identifying the realtime concerns. As more and more profiles are created, I expect that real-time will be a cross-cutting concern that will show up in many areas... robotics, telecom, corba, QoS for enterprise and workflow and business engineering. In some cases just for specifying delay requirements, at least to start with. Then the usability of the profile could be negatively affected by names of stereotypes but more particularly of attributes... it could generate naming conflicts against functional property names, in designs, and make people wary of using it. After all we have hundreds and maybe even thousands of stereotypes and attributes defined in MARTE. If someone loads the whole profile their stereotype and attribute menus will be swamped. A prefix per chapter is probably too much. We might consider two prefixes: mm for Marte Modeling ma for Marte Analysis (possibly also mc for MARTE Core?) And where one chapter specializes a stereotype from another, the specialized one might have a third letter, eg. map for specializing Step from GQAM to PAM. I know the editing implications are considerable, but the usability concerns are also serious. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) On Thu, 28 Feb 2008, GERARD Sebastien 166342 wrote: Hi Murray, There is no policy for prefixing the stereotype in MARTE. Do you have any suggestion? Séb -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : lundi 25 février 2008 18:05 Ã. : GERARD Sebastien 166342 Objet : prefixes on stereotypes Sebastien, do we have a policy on prefixes? Some chapters were written assuming there was... If all prefixes need to be changed, the text changes can just be edits but the figures will need to be modified in detail. there is an issue already. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) Date: Thu, 18 Sep 2008 17:27:45 +0200 From: S.©bastien Demathieu Organization: Thales Research & Technology User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) To: marte-ftf Cc: GERARD Sebastien 166342 Subject: Discussion on issue 12249 (was: Re: MARTE meeting in Orlando) Hi all, The issue 12249 calls for consistent conventions in the stereotype and stereotype attributes names. http://www.omg.org/issues/issue12249.txt I think that, by default, we should not use any prefix in the names we define. That way, we can keep stereotypes and stereotype attributes names as short as possible (as long as they are understandable) In the case of a stereotype defined in a subprofile then specialised in another subprofile then the specialised stereotypes may carry a prefix. A prefix should be unique for a given package. For instance, QGAM::Step (currently GQAM::GaStep) would be specialised by PAM::PaStep and SAM::SaStep. In a similar fashion, GRM::Device would be specialised by HRM:HwDevice. If a MARTE concept is really close to the UML metaclass it extends (e.g. NFP::NFPConstraint, extends UML::Constraint) then using a prefix may make sense too. Also, I think we should systematically avoid using underscores in the name we define. This character is used in parts of SRM and HRM. It would be interesting to hear back from you on this topic. Thanks, Sébastien GERARD Sebastien 166342 a écrit : Hi all, Here are two open issues that needs to be handle in priority because their resolutions may impact firstly lot of work in editing the spec, and secondly because it may have significant (editorial) impact on the resolution of other issues: http://www.omg.org/issues/issue12231.txt http://www.omg.org/issues/issue12249.txt So if may agree on preliminary resolution for both issues, we could finalize/continue the resolution within the Toulouse Meeting. Cheers, Sébastien. -----Message d'origine----- De : Irv Badr [mailto:ibadr@us.ibm.com] Envoyé : lundi 15 septembre 2008 16:53 À : Julio Medina Cc : GERARD Sebastien 166342; VanZandt, Lonnie; Frederic Mallet; marte-ftf Objet : Re: MARTE meeting in Orlando We are confirmed for Tuesday, 1300-1700, the room will be published in the OMG meeting program Irv ----------------- Sent from my BlackBerry Handheld. ----- Original Message ----- From: Julio Medina [julio.medina@unican.es] Sent: 09/15/2008 11:11 AM ZE2 To: Irv Badr Cc: GERARD Sebastien 166342 ; "VanZandt, Lonnie" ; Frederic Mallet ; marte-ftf Subject: Re: MARTE meeting in Orlando Irv, I guess you as chair may be better entitled to ask for the room to Kevin. (Also I happen to be traveling all this week so I wont probably have fluent access to my email). If Fred is OK with tuesday I think you may do the reservation. If necessary thursday afternoon is also ok for me. Thanks, Julio Irv Badr wrote: Julio, Tuesday is fine, especially after lunch. So are Wednesday or Thursday It would be nice to add tool vendor concern to the present agenda. Please let me know if you need help with room reservation Irv ----------------- Sent from my BlackBerry Handheld. ----- Original Message ----- From: Julio Medina [julio.medina@unican.es] Sent: 09/15/2008 10:49 AM ZE2 To: Irv Badr Cc: GERARD Sebastien 166342 ; "VanZandt, Lonnie" ; Frederic Mallet ; marte-ftf Subject: MARTE meeting in Orlando Hi All, Irv, Could we agree in a day, so that we may have a room reserved for it? I would suggest tuesday... (as usual) As for the agenda, we may probably take a look at the current list/category of issues we have now, and also it would be interesting to see about the expectations of tool vendors to implement the compliance cases proposed by MARTE. Of course these might be just initial points of discussion that might be continued in Toulouse. (Unfortunately I wont be able to attend the meeting in Toulouse) Cheers, Julio Irv Badr wrote: All, I will be glad to chair the meeting at Orlando, provided i can have a short con call with Lonnie and Sebastian sometime next week to sync up our agendas Irv ----------------- Sent from my BlackBerry Handheld. ------------------------------------------------------------------------ ----- Original Message ----- From: "GERARD Sebastien 166342" [Sebastien.GERARD@cea.fr] Sent: 09/12/2008 04:10 PM ZE2 To: "VanZandt, Lonnie" ; "Frederic Mallet" ; Subject: RE: MARTE meeting in Toulouse. Me too. I will also be in Toulouse. ------------------------------------------------------------------------ De : VanZandt, Lonnie [mailto:lonnie.vanzandt@artisansoftwaretools.com] EnvoyÃ.© : vendredi 12 septembre 2008 15:57 Ã.â.¬ : Frederic Mallet; marte-ftf@omg.org Objet : RE: MARTE meeting in Toulouse. Actually, I lost the vote for holding the meeting in Toulouse and I recall that Irv wrote he would be in Orlando to manage the chair duties there. I plan to call into any teleconference set up for the Orlando meeting. I will be in Toulouse at Models 2008 and I can meet with any fellow MARTE folk there and we could call in to Orlando together. Lonnie VanZandt Principal Engineer T: 303 482-2943 M: 720 201-1349 Lonnie.VanZandt@ArtisanSoftwareTools.com www.ArtisanSoftwareTools.com CONFIDENTIAL: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Thank you ------------------------------------------------------------------------ From: Frederic Mallet [mailto:Frederic.Mallet@sophia.inria.fr] Sent: Fri 9/12/2008 7:01 AM To: marte-ftf@omg.org Subject: MARTE meeting in Toulouse. hi all, I may be able to attend the meeting in Toulouse during MoDELs eventually. Did you choose a day ? Do you have a room number ? Regards, FrÃ.©dÃ.©ric. p.s.: I should also be at the Orlando meeting but it seems that I will be alone with Julio ? sebastien.demathieu1.vcf Subject: RE: Discussion on issue 12249 (was: Re: MARTE meeting in Orlando) Date: Thu, 18 Sep 2008 17:52:55 +0200 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Discussion on issue 12249 (was: Re: MARTE meeting in Orlando) thread-index: AckZo6vixALpdAt7TKWasV6H/tdIJQAAE+Rg From: "ESPINOZA Huascar 218344" To: S.©bastien Demathieu , "marte-ftf" Cc: "GERARD Sebastien 166342" X-OriginalArrivalTime: 18 Sep 2008 15:52:57.0059 (UTC) FILETIME=[9E765330:01C919A6] Hi Sébastien, Those rules are indeed used in MARTE already. For the underscore, it is not used (or .should be. if there are no mistakes) in Profiles. However, that is not the case in domain models. I.m not saying that it is ok. It would be great to have the feedback from users of MARTE. From my experience, having a prefix for all the stereotypes of the same Chapter makes easier the application of stereotypes. Regards, Huascar -------------------------------------------------------------------------------- De : Sébastien Demathieu [mailto:sebastien.demathieu@thalesgroup.com] Envoyé : jeudi 18 septembre 2008 17:28 À : marte-ftf Cc : GERARD Sebastien 166342 Objet : Discussion on issue 12249 (was: Re: MARTE meeting in Orlando) Hi all, The issue 12249 calls for consistent conventions in the stereotype and stereotype attributes names. http://www.omg.org/issues/issue12249.txt I think that, by default, we should not use any prefix in the names we define. That way, we can keep stereotypes and stereotype attributes names as short as possible (as long as they are understandable) In the case of a stereotype defined in a subprofile then specialised in another subprofile then the specialised stereotypes may carry a prefix. A prefix should be unique for a given package. For instance, QGAM::Step (currently GQAM::GaStep) would be specialised by PAM::PaStep and SAM::SaStep. In a similar fashion, GRM::Device would be specialised by HRM:HwDevice. If a MARTE concept is really close to the UML metaclass it extends (e.g. NFP::NFPConstraint, extends UML::Constraint) then using a prefix may make sense too. Also, I think we should systematically avoid using underscores in the name we define. This character is used in parts of SRM and HRM. It would be interesting to hear back from you on this topic. Thanks, Sébastien GERARD Sebastien 166342 a écrit : Hi all, Here are two open issues that needs to be handle in priority because their resolutions may impact firstly lot of work in editing the spec, and secondly because it may have significant (editorial) impact on the resolution of other issues: http://www.omg.org/issues/issue12231.txt http://www.omg.org/issues/issue12249.txt So if may agree on preliminary resolution for both issues, we could finalize/continue the resolution within the Toulouse Meeting. Cheers, Sébastien. -----Message d'origine----- De : Irv Badr [mailto:ibadr@us.ibm.com] Envoyé : lundi 15 septembre 2008 16:53 À : Julio Medina Cc : GERARD Sebastien 166342; VanZandt, Lonnie; Frederic Mallet; marte-ftf Objet : Re: MARTE meeting in Orlando We are confirmed for Tuesday, 1300-1700, the room will be published in the OMG meeting program Irv ----------------- Sent from my BlackBerry Handheld. ----- Original Message ----- From: Julio Medina [julio.medina@unican.es] Sent: 09/15/2008 11:11 AM ZE2 To: Irv Badr Cc: GERARD Sebastien 166342 ; "VanZandt, Lonnie" ; Frederic Mallet ; marte-ftf Subject: Re: MARTE meeting in Orlando Irv, I guess you as chair may be better entitled to ask for the room to Kevin. (Also I happen to be traveling all this week so I wont probably have fluent access to my email). If Fred is OK with tuesday I think you may do the reservation. If necessary thursday afternoon is also ok for me. Thanks, Julio Irv Badr wrote: Julio, Tuesday is fine, especially after lunch. So are Wednesday or Thursday It would be nice to add tool vendor concern to the present agenda. Please let me know if you need help with room reservation Irv ----------------- Sent from my BlackBerry Handheld. ----- Original Message ----- From: Julio Medina [julio.medina@unican.es] Sent: 09/15/2008 10:49 AM ZE2 To: Irv Badr Cc: GERARD Sebastien 166342 ; "VanZandt, Lonnie" ; Frederic Mallet ; marte-ftf Subject: MARTE meeting in Orlando Hi All, Irv, Could we agree in a day, so that we may have a room reserved for it? I would suggest tuesday... (as usual) As for the agenda, we may probably take a look at the current list/category of issues we have now, and also it would be interesting to see about the expectations of tool vendors to implement the compliance cases proposed by MARTE. Of course these might be just initial points of discussion that might be continued in Toulouse. (Unfortunately I wont be able to attend the meeting in Toulouse) Cheers, Julio Irv Badr wrote: All, I will be glad to chair the meeting at Orlando, provided i can have a short con call with Lonnie and Sebastian sometime next week to sync up our agendas Irv ----------------- Sent from my BlackBerry Handheld. ------------------------------------------------------------------------ ----- Original Message ----- From: "GERARD Sebastien 166342" [Sebastien.GERARD@cea.fr] Sent: 09/12/2008 04:10 PM ZE2 To: "VanZandt, Lonnie" ; "Frederic Mallet" ; Subject: RE: MARTE meeting in Toulouse. Me too. I will also be in Toulouse. ------------------------------------------------------------------------ De : VanZandt, Lonnie [mailto:lonnie.vanzandt@artisansoftwaretools.com] EnvoyÃ.© : vendredi 12 septembre 2008 15:57 Ã.â.¬ : Frederic Mallet; marte-ftf@omg.org Objet : RE: MARTE meeting in Toulouse. Actually, I lost the vote for holding the meeting in Toulouse and I recall that Irv wrote he would be in Orlando to manage the chair duties there. I plan to call into any teleconference set up for the Orlando meeting. I will be in Toulouse at Models 2008 and I can meet with any fellow MARTE folk there and we could call in to Orlando together. Lonnie VanZandt Principal Engineer T: 303 482-2943 M: 720 201-1349 Lonnie.VanZandt@ArtisanSoftwareTools.com www.ArtisanSoftwareTools.com CONFIDENTIAL: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Thank you ------------------------------------------------------------------------ From: Frederic Mallet [mailto:Frederic.Mallet@sophia.inria.fr] Sent: Fri 9/12/2008 7:01 AM To: marte-ftf@omg.org Subject: MARTE meeting in Toulouse. hi all, I may be able to attend the meeting in Toulouse during MoDELs eventually. Did you choose a day ? Do you have a room number ? Regards, FrÃ.©dÃ.©ric. p.s.: I should also be at the Orlando meeting but it seems that I will be alone with Julio ? X-IronPort-AV: E=Sophos;i="4.32,428,1217800800"; d="scan'208";a="17486303" Date: Fri, 19 Sep 2008 10:25:10 +0200 From: Frederic Mallet User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) To: ESPINOZA Huascar 218344 Cc: Sébastien Demathieu , marte-ftf , GERARD Sebastien 166342 Subject: Re: Discussion on issue 12249 Hi all, You actually took examples that works. But there are plenty of examples that would be weird if your prefix rule did apply : TimedProcessing, TimedEvent, ClockConstraint, Allocate, Refinement. Do you suggest to use : TimeTimedProcessing, TimeTimedEvent, TimeClockConstraint, AllocAllocate, AllocRefinement ... ? In the end, it may work for chapters where an acronym can be used as prefix. What would be the acronyms for Time and Allocation (two randomly selected chapters :) ) Frederic. ESPINOZA Huascar 218344 a écrit : Hi Sébastien, Those rules are indeed used in MARTE already. For the underscore, it is not used (or â..should beâ. if there are no mistakes) in Profiles. However, that is not the case in domain models. Iâ..m not saying that it is ok. It would be great to have the feedback from users of MARTE. From my experience, having a prefix for all the stereotypes of the same Chapter makes easier the application of stereotypes. Regards, Huascar ------------------------------------------------------------------------ *De :* Sébastien Demathieu [mailto:sebastien.demathieu@thalesgroup.com] *Envoyé :* jeudi 18 septembre 2008 17:28 *Ã. :* marte-ftf *Cc :* GERARD Sebastien 166342 *Objet :* Discussion on issue 12249 (was: Re: MARTE meeting in Orlando) Hi all, The issue 12249 calls for consistent conventions in the stereotype and stereotype attributes names. http://www.omg.org/issues/issue12249.txt I think that, by default, we should not use any prefix in the names we define. That way, we can keep stereotypes and stereotype attributes names as short as possible (as long as they are understandable) In the case of a stereotype defined in a subprofile then specialised in another subprofile then the specialised stereotypes may carry a prefix. A prefix should be unique for a given package. For instance, QGAM::Step (currently GQAM::GaStep) would be specialised by PAM::PaStep and SAM::SaStep. In a similar fashion, GRM::Device would be specialised by HRM:HwDevice. If a MARTE concept is really close to the UML metaclass it extends (e.g. NFP::NFPConstraint, extends UML::Constraint) then using a prefix may make sense too. Also, I think we should systematically avoid using underscores in the name we define. This character is used in parts of SRM and HRM. It would be interesting to hear back from you on this topic. Thanks, Sébastien GERARD Sebastien 166342 a écrit : Hi all, Here are two open issues that needs to be handle in priority because their resolutions may impact firstly lot of work in editing the spec, and secondly because it may have significant (editorial) impact on the resolution of other issues: http://www.omg.org/issues/issue12231.txt http://www.omg.org/issues/issue12249.txt So if may agree on preliminary resolution for both issues, we could finalize/continue the resolution within the Toulouse Meeting. Cheers, Sébastien. -----Message d'origine----- De : Irv Badr [mailto:ibadr@us.ibm.com] Envoyé : lundi 15 septembre 2008 16:53 Ã. : Julio Medina Cc : GERARD Sebastien 166342; VanZandt, Lonnie; Frederic Mallet; marte-ftf Objet : Re: MARTE meeting in Orlando We are confirmed for Tuesday, 1300-1700, the room will be published in the OMG meeting program Irv ----------------- Sent from my BlackBerry Handheld. ----- Original Message ----- From: Julio Medina [julio.medina@unican.es ] Sent: 09/15/2008 11:11 AM ZE2 To: Irv Badr Cc: GERARD Sebastien 166342 ; "VanZandt, Lonnie" ; Frederic Mallet ; marte-ftf Subject: Re: MARTE meeting in Orlando Irv, I guess you as chair may be better entitled to ask for the room to Kevin. (Also I happen to be traveling all this week so I wont probably have fluent access to my email). If Fred is OK with tuesday I think you may do the reservation. If necessary thursday afternoon is also ok for me. Thanks, Julio Irv Badr wrote: Julio, Tuesday is fine, especially after lunch. So are Wednesday or Thursday It would be nice to add tool vendor concern to the present agenda. Please let me know if you need help with room reservation Irv ----------------- Sent from my BlackBerry Handheld. ----- Original Message ----- From: Julio Medina [julio.medina@unican.es ] Sent: 09/15/2008 10:49 AM ZE2 To: Irv Badr Cc: GERARD Sebastien 166342 ; "VanZandt, Lonnie" ; Frederic Mallet ; marte-ftf Subject: MARTE meeting in Orlando Hi All, Irv, Could we agree in a day, so that we may have a room reserved for it? I would suggest tuesday... (as usual) As for the agenda, we may probably take a look at the current list/category of issues we have now, and also it would be interesting to see about the expectations of tool vendors to implement the compliance cases proposed by MARTE. Of course these might be just initial points of discussion that might be continued in Toulouse. (Unfortunately I wont be able to attend the meeting in Toulouse) Cheers, Julio Irv Badr wrote: All, I will be glad to chair the meeting at Orlando, provided i can have a short con call with Lonnie and Sebastian sometime next week to sync up our agendas Irv ----------------- Sent from my BlackBerry Handheld. ------------------------------------------------------------------------ ----- Original Message ----- From: "GERARD Sebastien 166342" [Sebastien.GERARD@cea.fr ] Sent: 09/12/2008 04:10 PM ZE2 To: "VanZandt, Lonnie" ; "Frederic Mallet" ; Subject: RE: MARTE meeting in Toulouse. Me too. I will also be in Toulouse. ------------------------------------------------------------------------ De : VanZandt, Lonnie [mailto:lonnie.vanzandt@artisansoftwaretools.com] EnvoyÃ.Æ.Ã.© : vendredi 12 septembre 2008 15:57 Ã.Æ.â.¬ : Frederic Mallet; marte-ftf@omg.org >>> Objet : RE: MARTE meeting in Toulouse. Actually, I lost the vote for holding the meeting in Toulouse and I recall that Irv wrote he would be in Orlando to manage the chair duties there. I plan to call into any teleconference set up for the Orlando meeting. I will be in Toulouse at Models 2008 and I can meet with any fellow MARTE folk there and we could call in to Orlando together. Lonnie VanZandt Principal Engineer T: 303 482-2943 M: 720 201-1349 Lonnie.VanZandt@ArtisanSoftwareTools.com www.ArtisanSoftwareTools.com CONFIDENTIAL: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Thank you ------------------------------------------------------------------------ From: Frederic Mallet [mailto:Frederic.Mallet@sophia.inria.fr] Sent: Fri 9/12/2008 7:01 AM To: marte-ftf@omg.org Subject: MARTE meeting in Toulouse. hi all, I may be able to attend the meeting in Toulouse during MoDELs eventually. Did you choose a day ? Do you have a room number ? Regards, FrÃ.Æ.Ã.©dÃ.Æ.Ã.©ric. p.s.: I should also be at the Orlando meeting but it seems that I will be alone with Julio ? Subject: RE: Discussion on issue 12249 Date: Fri, 19 Sep 2008 10:38:32 +0200 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Discussion on issue 12249 thread-index: AckaMUCjnS9kO2NRQgKisptFqOsw/wAACeEg From: "ESPINOZA Huascar 218344" To: "Frederic Mallet" Cc: Sébastien Demathieu , "marte-ftf" , "GERARD Sebastien 166342" X-OriginalArrivalTime: 19 Sep 2008 08:38:33.0439 (UTC) FILETIME=[19BF46F0:01C91A33] X-MIME-Autoconverted: from base64 to 8bit by amethyst.omg.org id m8J8dE2l013641 Hi Frédéric, Nice counter example, but it is not really a problem. You can use shorter prefixes than the chapter acronyms (as currently done: GQAM -> ga). However, if we see a more optimist scenario, tools should manage this aspect, and let users to transparently deal with a common name when the concept is used by many chapters. This should be done either by actually using common names (without prefix) and filtering by Packages by users... or maybe a more advanced support for a kind of Merge, like for UML metaclasses. In any case, we should do a balance between practicality (usability), tool capabilities, and a scalable language. Huascar -----Message d'origine----- De : Frederic Mallet [mailto:Frederic.Mallet@sophia.inria.fr] Envoyé : vendredi 19 septembre 2008 10:25 Ã. : ESPINOZA Huascar 218344 Cc : Sébastien Demathieu; marte-ftf; GERARD Sebastien 166342 Objet : Re: Discussion on issue 12249 Hi all, You actually took examples that works. But there are plenty of examples that would be weird if your prefix rule did apply : TimedProcessing, TimedEvent, ClockConstraint, Allocate, Refinement. Do you suggest to use : TimeTimedProcessing, TimeTimedEvent, TimeClockConstraint, AllocAllocate, AllocRefinement ... ? In the end, it may work for chapters where an acronym can be used as prefix. What would be the acronyms for Time and Allocation (two randomly selected chapters :) ) Frederic. ESPINOZA Huascar 218344 a écrit : > > Hi Sébastien, > > > > Those rules are indeed used in MARTE already. For the underscore, it > is not used (or â..should beâ. if there are no mistakes) in Profiles. > However, that is not the case in domain models. > > > > Iâ..m not saying that it is ok. It would be great to have the feedback > from users of MARTE. From my experience, having a prefix for all the > stereotypes of the same Chapter makes easier the application of > stereotypes. > > > > Regards, > > > > Huascar > > > > ------------------------------------------------------------------------ > > *De :* Sébastien Demathieu [mailto:sebastien.demathieu@thalesgroup.com] > *Envoyé :* jeudi 18 septembre 2008 17:28 > *Ã. :* marte-ftf > *Cc :* GERARD Sebastien 166342 > *Objet :* Discussion on issue 12249 (was: Re: MARTE meeting in Orlando) > > > > Hi all, > > The issue 12249 calls for consistent conventions in the stereotype and > stereotype attributes names. > > http://www.omg.org/issues/issue12249.txt > > > I think that, by default, we should not use any prefix in the names we > define. That way, we can keep > stereotypes and stereotype attributes names as short as possible (as > long as they are understandable) > > In the case of a stereotype defined in a subprofile then specialised > in another subprofile then the > specialised stereotypes may carry a prefix. A prefix should be unique > for a given package. For > instance, QGAM::Step (currently GQAM::GaStep) would be specialised by > PAM::PaStep and > SAM::SaStep. In a similar fashion, GRM::Device would be specialised by > HRM:HwDevice. > > If a MARTE concept is really close to the UML metaclass it extends > (e.g. NFP::NFPConstraint, > extends UML::Constraint) then using a prefix may make sense too. > > Also, I think we should systematically avoid using underscores in the > name we define. This character > is used in parts of SRM and HRM. > > It would be interesting to hear back from you on this topic. > > Thanks, > > Sébastien > > > > > GERARD Sebastien 166342 a écrit : > > Hi all, > > Here are two open issues that needs to be handle in priority because their resolutions may impact firstly lot of work in editing the spec, and secondly because it may have significant (editorial) impact on the resolution of other issues: > > http://www.omg.org/issues/issue12231.txt > > http://www.omg.org/issues/issue12249.txt > > > So if may agree on preliminary resolution for both issues, we could finalize/continue the resolution within the Toulouse Meeting. > > Cheers, > Sébastien. > > > > > -----Message d'origine----- > De : Irv Badr [mailto:ibadr@us.ibm.com] > Envoyé : lundi 15 septembre 2008 16:53 > Ã. : Julio Medina > Cc : GERARD Sebastien 166342; VanZandt, Lonnie; Frederic Mallet; marte-ftf > Objet : Re: MARTE meeting in Orlando > > We are confirmed for Tuesday, 1300-1700, the room will be published in the OMG meeting program > > Irv > ----------------- > Sent from my BlackBerry Handheld. > > > ----- Original Message ----- > From: Julio Medina [julio.medina@unican.es ] > Sent: 09/15/2008 11:11 AM ZE2 > To: Irv Badr > Cc: GERARD Sebastien 166342 ; "VanZandt, Lonnie" ; Frederic Mallet ; marte-ftf > Subject: Re: MARTE meeting in Orlando > > > > Irv, > > I guess you as chair may be better entitled to ask for the room to > Kevin. (Also I happen to be traveling all this week so I wont probably > have fluent access to my email). > > If Fred is OK with tuesday I think you may do the reservation. If > necessary thursday afternoon is also ok for me. > > Thanks, > > Julio > > Irv Badr wrote: > >> Julio, >> >> Tuesday is fine, especially after lunch. So are Wednesday or Thursday >> >> It would be nice to add tool vendor concern to the present agenda. >> Please let me know if you need help with room reservation >> Irv >> ----------------- >> Sent from my BlackBerry Handheld. >> >> >> ----- Original Message ----- >> From: Julio Medina [julio.medina@unican.es ] >> Sent: 09/15/2008 10:49 AM ZE2 >> To: Irv Badr >> Cc: GERARD Sebastien 166342 ; "VanZandt, >> Lonnie" ; Frederic Mallet >> ; marte-ftf >> Subject: MARTE meeting in Orlando >> >> >> >> Hi All, Irv, >> >> Could we agree in a day, so that we may have a room reserved for it? >> >> I would suggest tuesday... (as usual) >> >> As for the agenda, we may probably take a look at the current >> list/category of issues we have now, and also it would be interesting to >> see about the expectations of tool vendors to implement the compliance >> cases proposed by MARTE. >> >> Of course these might be just initial points of discussion that might be >> continued in Toulouse. (Unfortunately I wont be able to attend the >> meeting in Toulouse) >> >> Cheers, >> >> Julio >> >> >> Irv Badr wrote: >> >> >>> All, >>> >>> I will be glad to chair the meeting at Orlando, provided i can have a >>> short con call with Lonnie and Sebastian sometime next week to sync up >>> our agendas >>> >>> Irv >>> ----------------- >>> Sent from my BlackBerry Handheld. >>> >>> ------------------------------------------------------------------------ >>> >>> ----- Original Message ----- >>> From: "GERARD Sebastien 166342" [Sebastien.GERARD@cea.fr ] >>> Sent: 09/12/2008 04:10 PM ZE2 >>> To: "VanZandt, Lonnie" ; >>> "Frederic Mallet" ; >>> Subject: RE: MARTE meeting in Toulouse. >>> >>> >>> Me too. I will also be in Toulouse. >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> De : VanZandt, Lonnie [mailto:lonnie.vanzandt@artisansoftwaretools.com] >>> EnvoyÃ.Æ.Ã.© : vendredi 12 septembre 2008 15:57 >>> Ã.Æ.â.¬ : Frederic Mallet; marte-ftf@omg.org >>> Objet : RE: MARTE meeting in Toulouse. >>> >>> >>> >>> Actually, I lost the vote for holding the meeting in Toulouse and I >>> recall that Irv wrote he would be in Orlando to manage the chair >>> duties there. >>> >>> >>> >>> I plan to call into any teleconference set up for the Orlando meeting. >>> I will be in Toulouse at Models 2008 and I can meet with any fellow >>> MARTE folk there and we could call in to Orlando together. >>> >>> >>> >>> Lonnie VanZandt >>> >>> Principal Engineer >>> T: 303 482-2943 M: 720 201-1349 >>> Lonnie.VanZandt@ArtisanSoftwareTools.com >>> >>> >>> www.ArtisanSoftwareTools.com >>> >>> >>> >>> CONFIDENTIAL: The information in this message is confidential and may >>> be legally privileged. It is intended solely for the addressee(s). >>> Access to this message by anyone else is unauthorised. If you are not >>> the intended recipient, any disclosure, copying, or distribution of >>> the message, or any action or omission taken by you in reliance on it, >>> is prohibited and may be unlawful. Please immediately contact the >>> sender if you have received this message in error. Thank you >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> From: Frederic Mallet [mailto:Frederic.Mallet@sophia.inria.fr] >>> Sent: Fri 9/12/2008 7:01 AM >>> To: marte-ftf@omg.org >>> Subject: MARTE meeting in Toulouse. >>> >>> hi all, >>> I may be able to attend the meeting in Toulouse during MoDELs eventually. >>> Did you choose a day ? Do you have a room number ? >>> >>> Regards, >>> FrÃ.Æ.Ã.©dÃ.Æ.Ã.©ric. >>> p.s.: I should also be at the Orlando meeting but it seems that I will >>> be alone with Julio ? >>> >>> > > Date: Fri, 19 Sep 2008 15:50:47 +0200 From: S.©bastien Demathieu Organization: Thales Research & Technology User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) To: ESPINOZA Huascar 218344 Cc: marte-ftf , GERARD Sebastien 166342 Subject: Re: Discussion on issue 12249 Hi Huascar, Those rules are used in MARTE in some places but not in a consistent way. As for the use of underscore character, it is used in some HRM datatypes for sure. Thanks, Sébastien ESPINOZA Huascar 218344 a écrit : Hi Sébastien, Those rules are indeed used in MARTE already. For the underscore, it is not used (or .should be. if there are no mistakes) in Profiles. However, that is not the case in domain models. I.m not saying that it is ok. It would be great to have the feedback from users of MARTE. From my experience, having a prefix for all the stereotypes of the same Chapter makes easier the application of stereotypes. Regards, Huascar -------------------------------------------------------------------------------- De : Sébastien Demathieu [mailto:sebastien.demathieu@thalesgroup.com] Envoyé : jeudi 18 septembre 2008 17:28 À : marte-ftf Cc : GERARD Sebastien 166342 Objet : Discussion on issue 12249 (was: Re: MARTE meeting in Orlando) Hi all, The issue 12249 calls for consistent conventions in the stereotype and stereotype attributes names. http://www.omg.org/issues/issue12249.txt I think that, by default, we should not use any prefix in the names we define. That way, we can keep stereotypes and stereotype attributes names as short as possible (as long as they are understandable) In the case of a stereotype defined in a subprofile then specialised in another subprofile then the specialised stereotypes may carry a prefix. A prefix should be unique for a given package. For instance, QGAM::Step (currently GQAM::GaStep) would be specialised by PAM::PaStep and SAM::SaStep. In a similar fashion, GRM::Device would be specialised by HRM:HwDevice. If a MARTE concept is really close to the UML metaclass it extends (e.g. NFP::NFPConstraint, extends UML::Constraint) then using a prefix may make sense too. Also, I think we should systematically avoid using underscores in the name we define. This character is used in parts of SRM and HRM. It would be interesting to hear back from you on this topic. Thanks, Sébastien GERARD Sebastien 166342 a écrit : Hi all, Here are two open issues that needs to be handle in priority because their resolutions may impact firstly lot of work in editing the spec, and secondly because it may have significant (editorial) impact on the resolution of other issues: http://www.omg.org/issues/issue12231.txt http://www.omg.org/issues/issue12249.txt So if may agree on preliminary resolution for both issues, we could finalize/continue the resolution within the Toulouse Meeting. Cheers, Sébastien. -----Message d'origine----- De : Irv Badr [mailto:ibadr@us.ibm.com] Envoyé : lundi 15 septembre 2008 16:53 À : Julio Medina Cc : GERARD Sebastien 166342; VanZandt, Lonnie; Frederic Mallet; marte-ftf Objet : Re: MARTE meeting in Orlando We are confirmed for Tuesday, 1300-1700, the room will be published in the OMG meeting program Irv ----------------- Sent from my BlackBerry Handheld. ----- Original Message ----- From: Julio Medina [julio.medina@unican.es] Sent: 09/15/2008 11:11 AM ZE2 To: Irv Badr Cc: GERARD Sebastien 166342 ; "VanZandt, Lonnie" ; Frederic Mallet ; marte-ftf Subject: Re: MARTE meeting in Orlando Irv, I guess you as chair may be better entitled to ask for the room to Kevin. (Also I happen to be traveling all this week so I wont probably have fluent access to my email). If Fred is OK with tuesday I think you may do the reservation. If necessary thursday afternoon is also ok for me. Thanks, Julio Irv Badr wrote: Julio, Tuesday is fine, especially after lunch. So are Wednesday or Thursday It would be nice to add tool vendor concern to the present agenda. Please let me know if you need help with room reservation Irv ----------------- Sent from my BlackBerry Handheld. ----- Original Message ----- From: Julio Medina [julio.medina@unican.es] Sent: 09/15/2008 10:49 AM ZE2 To: Irv Badr Cc: GERARD Sebastien 166342 ; "VanZandt, Lonnie" ; Frederic Mallet ; marte-ftf Subject: MARTE meeting in Orlando Hi All, Irv, Could we agree in a day, so that we may have a room reserved for it? I would suggest tuesday... (as usual) As for the agenda, we may probably take a look at the current list/category of issues we have now, and also it would be interesting to see about the expectations of tool vendors to implement the compliance cases proposed by MARTE. Of course these might be just initial points of discussion that might be continued in Toulouse. (Unfortunately I wont be able to attend the meeting in Toulouse) Cheers, Julio Irv Badr wrote: All, I will be glad to chair the meeting at Orlando, provided i can have a short con call with Lonnie and Sebastian sometime next week to sync up our agendas Irv ----------------- Sent from my BlackBerry Handheld. ------------------------------------------------------------------------ ----- Original Message ----- From: "GERARD Sebastien 166342" [Sebastien.GERARD@cea.fr] Sent: 09/12/2008 04:10 PM ZE2 To: "VanZandt, Lonnie" ; "Frederic Mallet" ; Subject: RE: MARTE meeting in Toulouse. Me too. I will also be in Toulouse. ------------------------------------------------------------------------ De : VanZandt, Lonnie [mailto:lonnie.vanzandt@artisansoftwaretools.com] EnvoyÃ.© : vendredi 12 septembre 2008 15:57 Ã.â.¬ : Frederic Mallet; marte-ftf@omg.org Objet : RE: MARTE meeting in Toulouse. Actually, I lost the vote for holding the meeting in Toulouse and I recall that Irv wrote he would be in Orlando to manage the chair duties there. I plan to call into any teleconference set up for the Orlando meeting. I will be in Toulouse at Models 2008 and I can meet with any fellow MARTE folk there and we could call in to Orlando together. Lonnie VanZandt Principal Engineer T: 303 482-2943 M: 720 201-1349 Lonnie.VanZandt@ArtisanSoftwareTools.com www.ArtisanSoftwareTools.com CONFIDENTIAL: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Thank you ------------------------------------------------------------------------ From: Frederic Mallet [mailto:Frederic.Mallet@sophia.inria.fr] Sent: Fri 9/12/2008 7:01 AM To: marte-ftf@omg.org Subject: MARTE meeting in Toulouse. hi all, I may be able to attend the meeting in Toulouse during MoDELs eventually. Did you choose a day ? Do you have a room number ? Regards, FrÃ.©dÃ.©ric. p.s.: I should also be at the Orlando meeting but it seems that I will be alone with Julio ? sebastien.demathieu2.vcf Subject: RE: Discussion on issue 12249 Date: Fri, 19 Sep 2008 15:52:59 +0200 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Discussion on issue 12249 thread-index: AckaXr4nV/cHb2u7Qj2626nzDoL+6gAACZ0g From: "GERARD Sebastien 166342" To: S.©bastien Demathieu , "ESPINOZA Huascar 218344" Cc: "marte-ftf" X-OriginalArrivalTime: 19 Sep 2008 13:53:00.0010 (UTC) FILETIME=[07198CA0:01C91A5F] For underscore, for sure it has to be corrected in the test of the resolution proposal for this issue. For other, I would suggest to have no prefix in all stereotypes defined in the foundations, and only prefixes for stereotypes which are redefined in either design, or analysis sub profiles. -------------------------------------------------------------------------------- De : Sébastien Demathieu [mailto:sebastien.demathieu@thalesgroup.com] Envoyé : vendredi 19 septembre 2008 15:51 À : ESPINOZA Huascar 218344 Cc : marte-ftf; GERARD Sebastien 166342 Objet : Re: Discussion on issue 12249 Hi Huascar, Those rules are used in MARTE in some places but not in a consistent way. As for the use of underscore character, it is used in some HRM datatypes for sure. Thanks, Sébastien ESPINOZA Huascar 218344 a écrit : Hi Sébastien, Those rules are indeed used in MARTE already. For the underscore, it is not used (or .should be. if there are no mistakes) in Profiles. However, that is not the case in domain models. I.m not saying that it is ok. It would be great to have the feedback from users of MARTE. From my experience, having a prefix for all the stereotypes of the same Chapter makes easier the application of stereotypes. Regards, Huascar -------------------------------------------------------------------------------- De : Sébastien Demathieu [mailto:sebastien.demathieu@thalesgroup.com] Envoyé : jeudi 18 septembre 2008 17:28 À : marte-ftf Cc : GERARD Sebastien 166342 Objet : Discussion on issue 12249 (was: Re: MARTE meeting in Orlando) Hi all, The issue 12249 calls for consistent conventions in the stereotype and stereotype attributes names. http://www.omg.org/issues/issue12249.txt I think that, by default, we should not use any prefix in the names we define. That way, we can keep stereotypes and stereotype attributes names as short as possible (as long as they are understandable) In the case of a stereotype defined in a subprofile then specialised in another subprofile then the specialised stereotypes may carry a prefix. A prefix should be unique for a given package. For instance, QGAM::Step (currently GQAM::GaStep) would be specialised by PAM::PaStep and SAM::SaStep. In a similar fashion, GRM::Device would be specialised by HRM:HwDevice. If a MARTE concept is really close to the UML metaclass it extends (e.g. NFP::NFPConstraint, extends UML::Constraint) then using a prefix may make sense too. Also, I think we should systematically avoid using underscores in the name we define. This character is used in parts of SRM and HRM. It would be interesting to hear back from you on this topic. Thanks, Sébastien GERARD Sebastien 166342 a écrit : Hi all, Here are two open issues that needs to be handle in priority because their resolutions may impact firstly lot of work in editing the spec, and secondly because it may have significant (editorial) impact on the resolution of other issues: http://www.omg.org/issues/issue12231.txt http://www.omg.org/issues/issue12249.txt So if may agree on preliminary resolution for both issues, we could finalize/continue the resolution within the Toulouse Meeting. Cheers, Sébastien. -----Message d'origine----- De : Irv Badr [mailto:ibadr@us.ibm.com] Envoyé : lundi 15 septembre 2008 16:53 À : Julio Medina Cc : GERARD Sebastien 166342; VanZandt, Lonnie; Frederic Mallet; marte-ftf Objet : Re: MARTE meeting in Orlando We are confirmed for Tuesday, 1300-1700, the room will be published in the OMG meeting program Irv ----------------- Sent from my BlackBerry Handheld. ----- Original Message ----- From: Julio Medina [julio.medina@unican.es] Sent: 09/15/2008 11:11 AM ZE2 To: Irv Badr Cc: GERARD Sebastien 166342 ; "VanZandt, Lonnie" ; Frederic Mallet ; marte-ftf Subject: Re: MARTE meeting in Orlando Irv, I guess you as chair may be better entitled to ask for the room to Kevin. (Also I happen to be traveling all this week so I wont probably have fluent access to my email). If Fred is OK with tuesday I think you may do the reservation. If necessary thursday afternoon is also ok for me. Thanks, Julio Irv Badr wrote: Julio, Tuesday is fine, especially after lunch. So are Wednesday or Thursday It would be nice to add tool vendor concern to the present agenda. Please let me know if you need help with room reservation Irv ----------------- Sent from my BlackBerry Handheld. ----- Original Message ----- From: Julio Medina [julio.medina@unican.es] Sent: 09/15/2008 10:49 AM ZE2 To: Irv Badr Cc: GERARD Sebastien 166342 ; "VanZandt, Lonnie" ; Frederic Mallet ; marte-ftf Subject: MARTE meeting in Orlando Hi All, Irv, Could we agree in a day, so that we may have a room reserved for it? I would suggest tuesday... (as usual) As for the agenda, we may probably take a look at the current list/category of issues we have now, and also it would be interesting to see about the expectations of tool vendors to implement the compliance cases proposed by MARTE. Of course these might be just initial points of discussion that might be continued in Toulouse. (Unfortunately I wont be able to attend the meeting in Toulouse) Cheers, Julio Irv Badr wrote: All, I will be glad to chair the meeting at Orlando, provided i can have a short con call with Lonnie and Sebastian sometime next week to sync up our agendas Irv ----------------- Sent from my BlackBerry Handheld. ------------------------------------------------------------------------ ----- Original Message ----- From: "GERARD Sebastien 166342" [Sebastien.GERARD@cea.fr] Sent: 09/12/2008 04:10 PM ZE2 To: "VanZandt, Lonnie" ; "Frederic Mallet" ; Subject: RE: MARTE meeting in Toulouse. Me too. I will also be in Toulouse. ------------------------------------------------------------------------ De : VanZandt, Lonnie [mailto:lonnie.vanzandt@artisansoftwaretools.com] EnvoyÃ.© : vendredi 12 septembre 2008 15:57 Ã.â.¬ : Frederic Mallet; marte-ftf@omg.org Objet : RE: MARTE meeting in Toulouse. Actually, I lost the vote for holding the meeting in Toulouse and I recall that Irv wrote he would be in Orlando to manage the chair duties there. I plan to call into any teleconference set up for the Orlando meeting. I will be in Toulouse at Models 2008 and I can meet with any fellow MARTE folk there and we could call in to Orlando together. Lonnie VanZandt Principal Engineer T: 303 482-2943 M: 720 201-1349 Lonnie.VanZandt@ArtisanSoftwareTools.com www.ArtisanSoftwareTools.com CONFIDENTIAL: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Thank you ------------------------------------------------------------------------ From: Frederic Mallet [mailto:Frederic.Mallet@sophia.inria.fr] Sent: Fri 9/12/2008 7:01 AM To: marte-ftf@omg.org Subject: MARTE meeting in Toulouse. hi all, I may be able to attend the meeting in Toulouse during MoDELs eventually. Did you choose a day ? Do you have a room number ? Regards, FrÃ.©dÃ.©ric. p.s.: I should also be at the Orlando meeting but it seems that I will be alone with Julio ? Date: Wed, 8 Oct 2008 15:45:38 -0400 (EDT) From: Murray Woodside Reply-To: cmw@sce.carleton.ca To: marte-ftf@omg.org Subject: Re:issue 12249, use of prefixes on stereotypes Hi everyone, I am out of hospital and gradually returning to normal life. ***************** I introduced this issue, and it is big one in terms of effort, so I will try to collect together the reasons for doing it. We should decide on the principle of prefixes before discussing how they could be formed. 1. We have introduced many hundreds of stereotypes in MARTE, no designer is going to be able to remember them all. 2. Prefixes help to recognize that a property is defined by a standard, with semantics defined by the standard, rather than an application-specific property with semantics defined in the application. 3. Quick recognition by an analyst who is mainly focussed on a class of properties, makes it practical to navigate the diagrams and recognize the significance of properties in context. We have lots of experience of this with performance properties in SPT. This could be satisfied by prefixes on analysis properties only, but I think the same applies to model concepts and properties. 4. Robust and simpler implementation of tools to extract properties from XMI generated by models. Mechanical tools can filter information using the prefixes, and simplify their implementation. This would apply to MDE transformation tools as well as analysis tools, I think, and could encourage the creation of tools. 5. Risk of name conflict. Suppose a design is created without MARTE, and uses some generic concept like a clock, and introduces an application property with a name conflict with MARTE. If it is then decided to exploit MARTE to elaborate or analyze the design, the confusion might be very difficult to untangle. (This is less of a problem if MARTE is used from the beginning as many tools will immediately identify the name as already defined). In turn, this could inhibit the use of MARTE on existing specifications, and require the decision to use it, to be made right at the start... which would make users shy away from MARTE. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca Date: Tue, 27 Jan 2009 15:15:13 -0500 (EST) From: Murray Woodside Reply-To: cmw@sce.carleton.ca To: GERARD Sebastien 166342 cc: marte-ftf@omg.org Subject: issue 12249 on prefixes Sebastien proposes to discuss this issue shortly. I begin herewith I dont think there has been any discussion on naming, so nothing to summarize. The silence suggests no one agrees or no one wants to. It could also be difficult in practice. What we have now is prefixes for the analysis chapters GQAM, SAM, PAM, and also for the NFP library and only a few elsewhere: Nfp in chapter 8, NFP in Annex D, GrService only in GRM. Prefixes for analysis makes sense because the purpose of analysis is separate from specification modeling, and it may help to group the stereotypes that are relevant. So keeping them can be justified, and also NFP along with them. Modelers will see the marte modeling stereotypes as just another set of stereotypes for specification, so prefixes may be alien to their needs. I note there are three chapters that are mandatory for compliance of all kinds: NFP, GRM, Time. If there is any argument for prefixing stereotypes it could be these three chapters, with perhaps a common prefix Ma. However my sense is no one wants to change the stereotype names at this point. If so I will withdraw the issue. Lets decide in principle in the first ballot, whether any action is needed. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) On Tue, 27 Jan 2009, GERARD Sebastien 166342 wrote: No pb. Next week, the telco is scheduled for 4 pm CET. In the meantime, I will try to summarize the discussions on the issues related naming convention, and we may have a email discussion on that topic. Cheers... Sébastien. -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : mardi 27 janvier 2009 18:07 À : GERARD Sebastien 166342 Objet : RE: telco Sorry, I had the wrong time, and I went away from my office for the good time and just saw this an hour too late. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) On Tue, 27 Jan 2009, GERARD Sebastien 166342 wrote: Hi Murray, Sorry but i just purt the telephone down from another telco... The telco was scheduled at 5 pm CET this week, so in 29 min from now. However, you are the only one who raised the hand to participate. Thanks. The phone number and access code are the good one. See you in some minutes... if you still agree séb -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : mardi 27 janvier 2009 16:09 À : GERARD Sebastien 166342 Objet : telco I called into 33-172-283-003 with code 308953#... the last info I have... and there was no one there. Do you plan to hold the meeting? Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) Subject: RE: issue 12249, use of prefixes on stereotypes Date: Sat, 14 Feb 2009 23:07:58 +0100 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: issue 12249, use of prefixes on stereotypes Thread-Index: AckpfrlIjEIZVJbyTNyxAamcNvMV6xlcR3AQ From: "GERARD Sebastien 166342" To: , X-OriginalArrivalTime: 14 Feb 2009 22:07:58.0368 (UTC) FILETIME=[B1D65A00:01C98EF0] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id n1EM7IpY000774 Hi all, About this issue, it seems we make no progress... My point of view on that subject is that we should not prefix a priori and just use prefixes when needed. By when needed, I think it is: - when we define a stereotype which name may conflict with the UML2 metaclass the stereotype is extending. In this case, we have two solution for the prefix: either the name of the sub-profile wherein the stereotype is defined, or MARTE itself. This latter case is may be too long. So the first solution seems to be better. - when we define a stereotype generalizing an already defined stereotype of MARTE. In this case, we should use the name of the profile wherein the stereotype is defined to prefix this latter. Finally, we should not use "_" between the prefux and the name of the prefix. This rule should apply also for the name of the concepts of the domain model. Comments/propositions? Cheers... Sébastien -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : mercredi 8 octobre 2008 21:46 À : marte-ftf@omg.org Objet : Re:issue 12249, use of prefixes on stereotypes Hi everyone, I am out of hospital and gradually returning to normal life. ***************** I introduced this issue, and it is big one in terms of effort, so I will try to collect together the reasons for doing it. We should decide on the principle of prefixes before discussing how they could be formed. 1. We have introduced many hundreds of stereotypes in MARTE, no designer is going to be able to remember them all. 2. Prefixes help to recognize that a property is defined by a standard, with semantics defined by the standard, rather than an application-specific property with semantics defined in the application. 3. Quick recognition by an analyst who is mainly focussed on a class of properties, makes it practical to navigate the diagrams and recognize the significance of properties in context. We have lots of experience of this with performance properties in SPT. This could be satisfied by prefixes on analysis properties only, but I think the same applies to model concepts and properties. 4. Robust and simpler implementation of tools to extract properties from XMI generated by models. Mechanical tools can filter information using the prefixes, and simplify their implementation. This would apply to MDE transformation tools as well as analysis tools, I think, and could encourage the creation of tools. 5. Risk of name conflict. Suppose a design is created without MARTE, and uses some generic concept like a clock, and introduces an application property with a name conflict with MARTE. If it is then decided to exploit MARTE to elaborate or analyze the design, the confusion might be very difficult to untangle. (This is less of a problem if MARTE is used from the beginning as many tools will immediately identify the name as already defined). In turn, this could inhibit the use of MARTE on existing specifications, and require the decision to use it, to be made right at the start... which would make users shy away from MARTE. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) Date: Mon, 16 Feb 2009 13:55:23 +0100 From: Sébastien Demathieu Organization: Thales Research & Technology User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) To: GERARD Sebastien 166342 CC: cmw@sce.carleton.ca, marte-ftf@omg.org Subject: Re: issue 12249, use of prefixes on stereotypes Hi Sébastien, Following the link below you will find my point of view on issue 12249: http://www.omg.org/archives/marte-ftf/msg00955.html Thanks, Sébastien GERARD Sebastien 166342 a écrit : Hi all, About this issue, it seems we make no progress... My point of view on that subject is that we should not prefix a priori and just use prefixes when needed. By when needed, I think it is: - when we define a stereotype which name may conflict with the UML2 metaclass the stereotype is extending. In this case, we have two solution for the prefix: either the name of the sub-profile wherein the stereotype is defined, or MARTE itself. This latter case is may be too long. So the first solution seems to be better. - when we define a stereotype generalizing an already defined stereotype of MARTE. In this case, we should use the name of the profile wherein the stereotype is defined to prefix this latter. Finally, we should not use "_" between the prefux and the name of the prefix. This rule should apply also for the name of the concepts of the domain model. Comments/propositions? Cheers... Sébastien -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : mercredi 8 octobre 2008 21:46 À : marte-ftf@omg.org Objet : Re:issue 12249, use of prefixes on stereotypes Hi everyone, I am out of hospital and gradually returning to normal life. ***************** I introduced this issue, and it is big one in terms of effort, so I will try to collect together the reasons for doing it. We should decide on the principle of prefixes before discussing how they could be formed. 1. We have introduced many hundreds of stereotypes in MARTE, no designer is going to be able to remember them all. 2. Prefixes help to recognize that a property is defined by a standard, with semantics defined by the standard, rather than an application-specific property with semantics defined in the application. 3. Quick recognition by an analyst who is mainly focussed on a class of properties, makes it practical to navigate the diagrams and recognize the significance of properties in context. We have lots of experience of this with performance properties in SPT. This could be satisfied by prefixes on analysis properties only, but I think the same applies to model concepts and properties. 4. Robust and simpler implementation of tools to extract properties from XMI generated by models. Mechanical tools can filter information using the prefixes, and simplify their implementation. This would apply to MDE transformation tools as well as analysis tools, I think, and could encourage the creation of tools. 5. Risk of name conflict. Suppose a design is created without MARTE, and uses some generic concept like a clock, and introduces an application property with a name conflict with MARTE. If it is then decided to exploit MARTE to elaborate or analyze the design, the confusion might be very difficult to untangle. (This is less of a problem if MARTE is used from the beginning as many tools will immediately identify the name as already defined). In turn, this could inhibit the use of MARTE on existing specifications, and require the decision to use it, to be made right at the start... which would make users shy away from MARTE. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) sebastien.demathieu.vcf Subject: RE: issue 12249, use of prefixes on stereotypes Date: Mon, 16 Feb 2009 14:26:41 +0100 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: issue 12249, use of prefixes on stereotypes Thread-Index: AcmQNdlw2XT+UqQhQaeFccoPnHRV7QAA/IxA From: "GERARD Sebastien 166342" To: Sébastien Demathieu Cc: , X-OriginalArrivalTime: 16 Feb 2009 13:26:42.0326 (UTC) FILETIME=[34B09360:01C9903A] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id n1GDQWTR020690 Thanks sébastien, So we are in line I guess In order to help so solve this issue (except if you do it ? , could you, and other by the way, send me what you think should be modify? Or we should distribute the work: in this case who is volunteer to help me and sebastien in this task to find all the required changes in the spec? Let's notice that it is me that will do the change finally! I just ask for help for finding in an exhaustive manner all the places where change is needed to respect the rule proposed by SebD and second by SebG (myself . Cheers... Sébastien. -----Message d'origine----- De : Sébastien Demathieu [mailto:sebastien.demathieu@thalesgroup.com] Envoyé : lundi 16 février 2009 13:55 À : GERARD Sebastien 166342 Cc : cmw@sce.carleton.ca; marte-ftf@omg.org Objet : Re: issue 12249, use of prefixes on stereotypes Hi Sébastien, Following the link below you will find my point of view on issue 12249: http://www.omg.org/archives/marte-ftf/msg00955.html Thanks, Sébastien GERARD Sebastien 166342 a écrit : > Hi all, > > About this issue, it seems we make no progress... > > My point of view on that subject is that we should not prefix a priori and just use prefixes when needed. > > By when needed, I think it is: > - when we define a stereotype which name may conflict with the UML2 metaclass the stereotype is extending. In this case, we have two solution for the prefix: either the name of the sub-profile wherein the stereotype is defined, or MARTE itself. This latter case is may be too long. So the first solution seems to be better. > - when we define a stereotype generalizing an already defined stereotype of MARTE. In this case, we should use the name of the profile wherein the stereotype is defined to prefix this latter. > > Finally, we should not use "_" between the prefux and the name of the prefix. This rule should apply also for the name of the concepts of the domain model. > > Comments/propositions? > > > Cheers... Sébastien > > > -----Message d'origine----- > De : Murray Woodside [mailto:cmw@sce.carleton.ca] > Envoyé : mercredi 8 octobre 2008 21:46 > À : marte-ftf@omg.org > Objet : Re:issue 12249, use of prefixes on stereotypes > > Hi everyone, I am out of hospital and gradually returning to normal life. > ***************** > > I introduced this issue, and it is big one in terms of effort, so I will > try to collect together the reasons for doing it. > > We should decide on the principle of prefixes before discussing how they > could be formed. > > 1. We have introduced many hundreds of stereotypes in MARTE, no > designer is going to be able to remember them all. > > 2. Prefixes help to recognize that a property is defined by a standard, > with semantics defined by the standard, rather than an > application-specific property with semantics defined in the application. > > 3. Quick recognition by an analyst who is mainly focussed on a class of > properties, makes it practical to navigate the diagrams and recognize the > significance of properties in context. We have lots of experience of this > with performance properties in SPT. > > This could be satisfied by prefixes on analysis properties only, but I > think the same applies to model concepts and properties. > > 4. Robust and simpler implementation of tools to extract properties from > XMI generated by models. Mechanical tools can filter information using the > prefixes, and simplify their implementation. > > This would apply to MDE transformation tools as well as analysis tools, I > think, and could encourage the creation of tools. > > 5. Risk of name conflict. Suppose a design is created without MARTE, and > uses some generic concept like a clock, and introduces an application property > with a name conflict with MARTE. > > If it is then decided to exploit MARTE to elaborate or analyze the design, > the confusion might be very difficult to untangle. (This is less of a > problem if MARTE is used from the beginning as many tools will immediately > identify the name as already defined). > > In turn, this could inhibit the use of MARTE on existing specifications, > and require the decision to use it, to be made right at the start... which > would make users shy away from MARTE. > > Murray Woodside > > Distinguished Research Professor > Dept of Systems and Computer Engineering, > Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. > (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca > (http://www.sce.carleton.ca/faculty/woodside.html) > > Date: Mon, 16 Feb 2009 14:31:28 +0100 From: Sébastien Demathieu Organization: Thales Research & Technology User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) To: GERARD Sebastien 166342 CC: cmw@sce.carleton.ca, marte-ftf@omg.org Subject: Re: issue 12249, use of prefixes on stereotypes Sébastien, I will have a look at the Excel sheet you guys provided at the beginning of the FTF : http://www.omgwiki.org/marte-ftf2/doku.php?id=general_wg:forum_12249 It gives an overview of all the stereotypes and stereotypes attributes. Based on that, I will make change proposals. Thanks, Sébastien GERARD Sebastien 166342 a écrit : Thanks sébastien, So we are in line I guess In order to help so solve this issue (except if you do it ? , could you, and other by the way, send me what you think should be modify? Or we should distribute the work: in this case who is volunteer to help me and sebastien in this task to find all the required changes in the spec? Let's notice that it is me that will do the change finally! I just ask for help for finding in an exhaustive manner all the places where change is needed to respect the rule proposed by SebD and second by SebG (myself . Cheers... Sébastien. -----Message d'origine----- De : Sébastien Demathieu [mailto:sebastien.demathieu@thalesgroup.com] Envoyé : lundi 16 février 2009 13:55 Ã. : GERARD Sebastien 166342 Cc : cmw@sce.carleton.ca; marte-ftf@omg.org Objet : Re: issue 12249, use of prefixes on stereotypes Hi Sébastien, Following the link below you will find my point of view on issue 12249: http://www.omg.org/archives/marte-ftf/msg00955.html Thanks, Sébastien GERARD Sebastien 166342 a écrit : Hi all, About this issue, it seems we make no progress... My point of view on that subject is that we should not prefix a priori and just use prefixes when needed. By when needed, I think it is: - when we define a stereotype which name may conflict with the UML2 metaclass the stereotype is extending. In this case, we have two solution for the prefix: either the name of the sub-profile wherein the stereotype is defined, or MARTE itself. This latter case is may be too long. So the first solution seems to be better. - when we define a stereotype generalizing an already defined stereotype of MARTE. In this case, we should use the name of the profile wherein the stereotype is defined to prefix this latter. Finally, we should not use "_" between the prefux and the name of the prefix. This rule should apply also for the name of the concepts of the domain model. Comments/propositions? Cheers... Sébastien -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : mercredi 8 octobre 2008 21:46 Ã. : marte-ftf@omg.org Objet : Re:issue 12249, use of prefixes on stereotypes Hi everyone, I am out of hospital and gradually returning to normal life. ***************** I introduced this issue, and it is big one in terms of effort, so I will try to collect together the reasons for doing it. We should decide on the principle of prefixes before discussing how they could be formed. 1. We have introduced many hundreds of stereotypes in MARTE, no designer is going to be able to remember them all. 2. Prefixes help to recognize that a property is defined by a standard, with semantics defined by the standard, rather than an application-specific property with semantics defined in the application. 3. Quick recognition by an analyst who is mainly focussed on a class of properties, makes it practical to navigate the diagrams and recognize the significance of properties in context. We have lots of experience of this with performance properties in SPT. This could be satisfied by prefixes on analysis properties only, but I think the same applies to model concepts and properties. 4. Robust and simpler implementation of tools to extract properties from XMI generated by models. Mechanical tools can filter information using the prefixes, and simplify their implementation. This would apply to MDE transformation tools as well as analysis tools, I think, and could encourage the creation of tools. 5. Risk of name conflict. Suppose a design is created without MARTE, and uses some generic concept like a clock, and introduces an application property with a name conflict with MARTE. If it is then decided to exploit MARTE to elaborate or analyze the design, the confusion might be very difficult to untangle. (This is less of a problem if MARTE is used from the beginning as many tools will immediately identify the name as already defined). In turn, this could inhibit the use of MARTE on existing specifications, and require the decision to use it, to be made right at the start... which would make users shy away from MARTE. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) sebastien.demathieu2.vcf Date: Tue, 17 Feb 2009 18:13:41 -0500 (EST) Subject: RE: issue 12249, use of prefixes on stereotypes From: cmw@sce.carleton.ca To: "GERARD Sebastien 166342" Cc: Sébastien Demathieu , cmw@sce.carleton.ca, marte-ftf@omg.org User-Agent: SquirrelMail/1.4.17 To Seb+Seb and all others... I think the analysis chapter naming is OK as it stands, it identifies all the defined stereotypes, and this is probably a good idea for analysts who are focussed on these rather than on the design. Also there will be additional subprofiles for other analyses (reliability is coming I know) and it is wise to identify where these are defined!! to help the analysts with the semantics. Also all these names conform to the no "_" rule mentioned, I think. If this is acceptable it will reduce the effort to make changes. Murray > Thanks sébastien, > > So we are in line I guess > > In order to help so solve this issue (except if you do it ? , could > you, and other by the way, send me what you think should be modify? > > Or we should distribute the work: in this case who is volunteer to help me > and sebastien in this task to find all the required changes in the spec? > > Let's notice that it is me that will do the change finally! I just ask for > help for finding in an exhaustive manner all the places where change is > needed to respect the rule proposed by SebD and second by SebG (myself > . > > Cheers... Sébastien. > > -----Message d'origine----- > De : Sébastien Demathieu [mailto:sebastien.demathieu@thalesgroup.com] > Envoyé : lundi 16 février 2009 13:55 > À : GERARD Sebastien 166342 > Cc : cmw@sce.carleton.ca; marte-ftf@omg.org > Objet : Re: issue 12249, use of prefixes on stereotypes > > Hi Sébastien, > > Following the link below you will find my point of view on issue 12249: > > http://www.omg.org/archives/marte-ftf/msg00955.html > > Thanks, > > Sébastien > > > > GERARD Sebastien 166342 a écrit : >> Hi all, >> >> About this issue, it seems we make no progress... >> >> My point of view on that subject is that we should not prefix a priori >> and just use prefixes when needed. >> >> By when needed, I think it is: >> - when we define a stereotype which name may conflict with the UML2 >> metaclass the stereotype is extending. In this case, we have two >> solution for the prefix: either the name of the sub-profile wherein the >> stereotype is defined, or MARTE itself. This latter case is may be too >> long. So the first solution seems to be better. >> - when we define a stereotype generalizing an already defined stereotype >> of MARTE. In this case, we should use the name of the profile wherein >> the stereotype is defined to prefix this latter. >> >> Finally, we should not use "_" between the prefux and the name of the >> prefix. This rule should apply also for the name of the concepts of the >> domain model. >> >> Comments/propositions? >> >> >> Cheers... Sébastien >> >> >> -----Message d'origine----- >> De : Murray Woodside [mailto:cmw@sce.carleton.ca] >> Envoyé : mercredi 8 octobre 2008 21:46 >> À : marte-ftf@omg.org >> Objet : Re:issue 12249, use of prefixes on stereotypes >> >> Hi everyone, I am out of hospital and gradually returning to normal >> life. >> ***************** >> >> I introduced this issue, and it is big one in terms of effort, so I will >> try to collect together the reasons for doing it. >> >> We should decide on the principle of prefixes before discussing how they >> could be formed. >> >> 1. We have introduced many hundreds of stereotypes in MARTE, no >> designer is going to be able to remember them all. >> >> 2. Prefixes help to recognize that a property is defined by a standard, >> with semantics defined by the standard, rather than an >> application-specific property with semantics defined in the application. >> >> 3. Quick recognition by an analyst who is mainly focussed on a class of >> properties, makes it practical to navigate the diagrams and recognize >> the >> significance of properties in context. We have lots of experience of >> this >> with performance properties in SPT. >> >> This could be satisfied by prefixes on analysis properties only, but I >> think the same applies to model concepts and properties. >> >> 4. Robust and simpler implementation of tools to extract properties from >> XMI generated by models. Mechanical tools can filter information using >> the >> prefixes, and simplify their implementation. >> >> This would apply to MDE transformation tools as well as analysis tools, >> I >> think, and could encourage the creation of tools. >> >> 5. Risk of name conflict. Suppose a design is created without MARTE, and >> uses some generic concept like a clock, and introduces an application >> property >> with a name conflict with MARTE. >> >> If it is then decided to exploit MARTE to elaborate or analyze the >> design, >> the confusion might be very difficult to untangle. (This is less of a >> problem if MARTE is used from the beginning as many tools will >> immediately >> identify the name as already defined). >> >> In turn, this could inhibit the use of MARTE on existing specifications, >> and require the decision to use it, to be made right at the start... >> which >> would make users shy away from MARTE. >> >> Murray Woodside >> >> Distinguished Research Professor >> Dept of Systems and Computer Engineering, >> Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. >> (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca >> (http://www.sce.carleton.ca/faculty/woodside.html) >> >> > Subject: RE: issue 12249, use of prefixes on stereotypes Date: Fri, 20 Feb 2009 12:30:25 +0100 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: issue 12249, use of prefixes on stereotypes Thread-Index: AcmRVWz+M5lC7UGLTwmtvTP3ThaXfAB7orAgAAKqDWA= From: "Medina Pasaje, Julio Luis" To: "GERARD Sebastien 166342" , , Sébastien Demathieu Cc: X-imss-version: 2.053 X-imss-result: Passed X-imss-scanInfo: M:P L:E SM:0 X-imss-tmaseResult: TT:0 TS:0.0000 TC:00 TRN:0 TV:5.6.1016(16474.006) X-imss-scores: Clean:85.21471 C:2 M:3 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:2 S:2 R:2 (0.0000 0.0000) X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id n1KBVSLe032216 I Agree. Julio ________________________________ De: GERARD Sebastien 166342 [mailto:Sebastien.GERARD@cea.fr] Enviado el: vie 20/02/2009 11:16 Para: cmw@sce.carleton.ca; Sébastien Demathieu CC: marte-ftf@omg.org Asunto: RE: issue 12249, use of prefixes on stereotypes About the rule no "_", there is a pb with all the NFP predefined types that widely used in the spec and that are not respecting this rule: NFP_Real,... So I believe it is not reasonable to rename all these NFP redefined type because they are used all along the spec every wehre in the text and in the figure. So I suggest we make exception for that case. Do you agree? Sébastien. -----Message d'origine----- De : cmw@sce.carleton.ca [mailto:cmw@sce.carleton.ca] Envoyé : mercredi 18 février 2009 00:14 À : GERARD Sebastien 166342 Cc : Sébastien Demathieu; cmw@sce.carleton.ca; marte-ftf@omg.org Objet : RE: issue 12249, use of prefixes on stereotypes To Seb+Seb and all others... I think the analysis chapter naming is OK as it stands, it identifies all the defined stereotypes, and this is probably a good idea for analysts who are focussed on these rather than on the design. Also there will be additional subprofiles for other analyses (reliability is coming I know) and it is wise to identify where these are defined!! to help the analysts with the semantics. Also all these names conform to the no "_" rule mentioned, I think. If this is acceptable it will reduce the effort to make changes. Murray > Thanks sébastien, > > So we are in line I guess > > In order to help so solve this issue (except if you do it ? , could > you, and other by the way, send me what you think should be modify? > > Or we should distribute the work: in this case who is volunteer to help me > and sebastien in this task to find all the required changes in the spec? > > Let's notice that it is me that will do the change finally! I just ask for > help for finding in an exhaustive manner all the places where change is > needed to respect the rule proposed by SebD and second by SebG (myself > . > > Cheers... Sébastien. > > -----Message d'origine----- > De : Sébastien Demathieu [mailto:sebastien.demathieu@thalesgroup.com] > Envoyé : lundi 16 février 2009 13:55 > À : GERARD Sebastien 166342 > Cc : cmw@sce.carleton.ca; marte-ftf@omg.org > Objet : Re: issue 12249, use of prefixes on stereotypes > > Hi Sébastien, > > Following the link below you will find my point of view on issue 12249: > > http://www.omg.org/archives/marte-ftf/msg00955.html > > Thanks, > > Sébastien > > > > GERARD Sebastien 166342 a écrit : >> Hi all, >> >> About this issue, it seems we make no progress... >> >> My point of view on that subject is that we should not prefix a priori >> and just use prefixes when needed. >> >> By when needed, I think it is: >> - when we define a stereotype which name may conflict with the UML2 >> metaclass the stereotype is extending. In this case, we have two >> solution for the prefix: either the name of the sub-profile wherein the >> stereotype is defined, or MARTE itself. This latter case is may be too >> long. So the first solution seems to be better. >> - when we define a stereotype generalizing an already defined stereotype >> of MARTE. In this case, we should use the name of the profile wherein >> the stereotype is defined to prefix this latter. >> >> Finally, we should not use "_" between the prefux and the name of the >> prefix. This rule should apply also for the name of the concepts of the >> domain model. >> >> Comments/propositions? >> >> >> Cheers... Sébastien >> >> >> -----Message d'origine----- >> De : Murray Woodside [mailto:cmw@sce.carleton.ca] >> Envoyé : mercredi 8 octobre 2008 21:46 >> À : marte-ftf@omg.org >> Objet : Re:issue 12249, use of prefixes on stereotypes >> >> Hi everyone, I am out of hospital and gradually returning to normal >> life. >> ***************** >> >> I introduced this issue, and it is big one in terms of effort, so I will >> try to collect together the reasons for doing it. >> >> We should decide on the principle of prefixes before discussing how they >> could be formed. >> >> 1. We have introduced many hundreds of stereotypes in MARTE, no >> designer is going to be able to remember them all. >> >> 2. Prefixes help to recognize that a property is defined by a standard, >> with semantics defined by the standard, rather than an >> application-specific property with semantics defined in the application. >> >> 3. Quick recognition by an analyst who is mainly focussed on a class of >> properties, makes it practical to navigate the diagrams and recognize >> the >> significance of properties in context. We have lots of experience of >> this >> with performance properties in SPT. >> >> This could be satisfied by prefixes on analysis properties only, but I >> think the same applies to model concepts and properties. >> >> 4. Robust and simpler implementation of tools to extract properties from >> XMI generated by models. Mechanical tools can filter information using >> the >> prefixes, and simplify their implementation. >> >> This would apply to MDE transformation tools as well as analysis tools, >> I >> think, and could encourage the creation of tools. >> >> 5. Risk of name conflict. Suppose a design is created without MARTE, and >> uses some generic concept like a clock, and introduces an application >> property >> with a name conflict with MARTE. >> >> If it is then decided to exploit MARTE to elaborate or analyze the >> design, >> the confusion might be very difficult to untangle. (This is less of a >> problem if MARTE is used from the beginning as many tools will >> immediately >> identify the name as already defined). >> >> In turn, this could inhibit the use of MARTE on existing specifications, >> and require the decision to use it, to be made right at the start... >> which >> would make users shy away from MARTE. >> >> Murray Woodside >> >> Distinguished Research Professor >> Dept of Systems and Computer Engineering, >> Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. >> (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca >> (http://www.sce.carleton.ca/faculty/woodside.html) >> >> Subject: RE: issue 12249, use of prefixes on stereotypes Date: Fri, 20 Feb 2009 11:16:06 +0100 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: issue 12249, use of prefixes on stereotypes Thread-Index: AcmRVWz+M5lC7UGLTwmtvTP3ThaXfAB7orAg From: "GERARD Sebastien 166342" To: , Sébastien Demathieu Cc: X-OriginalArrivalTime: 20 Feb 2009 10:16:07.0465 (UTC) FILETIME=[3EA24190:01C99344] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id n1KAFacd000912 About the rule no "_", there is a pb with all the NFP predefined types that widely used in the spec and that are not respecting this rule: NFP_Real,... So I believe it is not reasonable to rename all these NFP redefined type because they are used all along the spec every wehre in the text and in the figure. So I suggest we make exception for that case. Do you agree? Sébastien. -----Message d'origine----- De : cmw@sce.carleton.ca [mailto:cmw@sce.carleton.ca] Envoyé : mercredi 18 février 2009 00:14 À : GERARD Sebastien 166342 Cc : Sébastien Demathieu; cmw@sce.carleton.ca; marte-ftf@omg.org Objet : RE: issue 12249, use of prefixes on stereotypes To Seb+Seb and all others... I think the analysis chapter naming is OK as it stands, it identifies all the defined stereotypes, and this is probably a good idea for analysts who are focussed on these rather than on the design. Also there will be additional subprofiles for other analyses (reliability is coming I know) and it is wise to identify where these are defined!! to help the analysts with the semantics. Also all these names conform to the no "_" rule mentioned, I think. If this is acceptable it will reduce the effort to make changes. Murray > Thanks sébastien, > > So we are in line I guess > > In order to help so solve this issue (except if you do it ? , could > you, and other by the way, send me what you think should be modify? > > Or we should distribute the work: in this case who is volunteer to help me > and sebastien in this task to find all the required changes in the spec? > > Let's notice that it is me that will do the change finally! I just ask for > help for finding in an exhaustive manner all the places where change is > needed to respect the rule proposed by SebD and second by SebG (myself > . > > Cheers... Sébastien. > > -----Message d'origine----- > De : Sébastien Demathieu [mailto:sebastien.demathieu@thalesgroup.com] > Envoyé : lundi 16 février 2009 13:55 > À : GERARD Sebastien 166342 > Cc : cmw@sce.carleton.ca; marte-ftf@omg.org > Objet : Re: issue 12249, use of prefixes on stereotypes > > Hi Sébastien, > > Following the link below you will find my point of view on issue 12249: > > http://www.omg.org/archives/marte-ftf/msg00955.html > > Thanks, > > Sébastien > > > > GERARD Sebastien 166342 a écrit : >> Hi all, >> >> About this issue, it seems we make no progress... >> >> My point of view on that subject is that we should not prefix a priori >> and just use prefixes when needed. >> >> By when needed, I think it is: >> - when we define a stereotype which name may conflict with the UML2 >> metaclass the stereotype is extending. In this case, we have two >> solution for the prefix: either the name of the sub-profile wherein the >> stereotype is defined, or MARTE itself. This latter case is may be too >> long. So the first solution seems to be better. >> - when we define a stereotype generalizing an already defined stereotype >> of MARTE. In this case, we should use the name of the profile wherein >> the stereotype is defined to prefix this latter. >> >> Finally, we should not use "_" between the prefux and the name of the >> prefix. This rule should apply also for the name of the concepts of the >> domain model. >> >> Comments/propositions? >> >> >> Cheers... Sébastien >> >> >> -----Message d'origine----- >> De : Murray Woodside [mailto:cmw@sce.carleton.ca] >> Envoyé : mercredi 8 octobre 2008 21:46 >> À : marte-ftf@omg.org >> Objet : Re:issue 12249, use of prefixes on stereotypes >> >> Hi everyone, I am out of hospital and gradually returning to normal >> life. >> ***************** >> >> I introduced this issue, and it is big one in terms of effort, so I will >> try to collect together the reasons for doing it. >> >> We should decide on the principle of prefixes before discussing how they >> could be formed. >> >> 1. We have introduced many hundreds of stereotypes in MARTE, no >> designer is going to be able to remember them all. >> >> 2. Prefixes help to recognize that a property is defined by a standard, >> with semantics defined by the standard, rather than an >> application-specific property with semantics defined in the application. >> >> 3. Quick recognition by an analyst who is mainly focussed on a class of >> properties, makes it practical to navigate the diagrams and recognize >> the >> significance of properties in context. We have lots of experience of >> this >> with performance properties in SPT. >> >> This could be satisfied by prefixes on analysis properties only, but I >> think the same applies to model concepts and properties. >> >> 4. Robust and simpler implementation of tools to extract properties from >> XMI generated by models. Mechanical tools can filter information using >> the >> prefixes, and simplify their implementation. >> >> This would apply to MDE transformation tools as well as analysis tools, >> I >> think, and could encourage the creation of tools. >> >> 5. Risk of name conflict. Suppose a design is created without MARTE, and >> uses some generic concept like a clock, and introduces an application >> property >> with a name conflict with MARTE. >> >> If it is then decided to exploit MARTE to elaborate or analyze the >> design, >> the confusion might be very difficult to untangle. (This is less of a >> problem if MARTE is used from the beginning as many tools will >> immediately >> identify the name as already defined). >> >> In turn, this could inhibit the use of MARTE on existing specifications, >> and require the decision to use it, to be made right at the start... >> which >> would make users shy away from MARTE. >> >> Murray Woodside >> >> Distinguished Research Professor >> Dept of Systems and Computer Engineering, >> Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. >> (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca >> (http://www.sce.carleton.ca/faculty/woodside.html) >> >> >Date: Fri, 20 Feb 2009 11:26:18 +0100 From: Sébastien Demathieu Organization: Thales Research & Technology User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) To: GERARD Sebastien 166342 CC: cmw@sce.carleton.ca, marte-ftf@omg.org Subject: Re: issue 12249, use of prefixes on stereotypes Sounds good to me. Sébastien GERARD Sebastien 166342 a écrit : About the rule no "_", there is a pb with all the NFP predefined types that widely used in the spec and that are not respecting this rule: NFP_Real,... So I believe it is not reasonable to rename all these NFP redefined type because they are used all along the spec every wehre in the text and in the figure. So I suggest we make exception for that case. Do you agree? Sébastien. -----Message d'origine----- De : cmw@sce.carleton.ca [mailto:cmw@sce.carleton.ca] Envoyé : mercredi 18 février 2009 00:14 À : GERARD Sebastien 166342 Cc : Sébastien Demathieu; cmw@sce.carleton.ca; marte-ftf@omg.org Objet : RE: issue 12249, use of prefixes on stereotypes To Seb+Seb and all others... I think the analysis chapter naming is OK as it stands, it identifies all the defined stereotypes, and this is probably a good idea for analysts who are focussed on these rather than on the design. Also there will be additional subprofiles for other analyses (reliability is coming I know) and it is wise to identify where these are defined!! to help the analysts with the semantics. Also all these names conform to the no "_" rule mentioned, I think. If this is acceptable it will reduce the effort to make changes. Murray Thanks sébastien, So we are in line I guess In order to help so solve this issue (except if you do it ? , could you, and other by the way, send me what you think should be modify? Or we should distribute the work: in this case who is volunteer to help me and sebastien in this task to find all the required changes in the spec? Let's notice that it is me that will do the change finally! I just ask for help for finding in an exhaustive manner all the places where change is needed to respect the rule proposed by SebD and second by SebG (myself heers... Sébastien. -----Message d'origine----- De : Sébastien Demathieu [mailto:sebastien.demathieu@thalesgroup.com] Envoyé : lundi 16 février 2009 13:55 À : GERARD Sebastien 166342 Cc : cmw@sce.carleton.ca; marte-ftf@omg.org Objet : Re: issue 12249, use of prefixes on stereotypes Hi Sébastien, Following the link below you will find my point of view on issue 12249: http://www.omg.org/archives/marte-ftf/msg00955.html Thanks, Sébastien GERARD Sebastien 166342 a écrit : Hi all, About this issue, it seems we make no progress... My point of view on that subject is that we should not prefix a priori and just use prefixes when needed. By when needed, I think it is: - when we define a stereotype which name may conflict with the UML2 metaclass the stereotype is extending. In this case, we have two solution for the prefix: either the name of the sub-profile wherein the stereotype is defined, or MARTE itself. This latter case is may be too long. So the first solution seems to be better. - when we define a stereotype generalizing an already defined stereotype of MARTE. In this case, we should use the name of the profile wherein the stereotype is defined to prefix this latter. Finally, we should not use "_" between the prefux and the name of the prefix. This rule should apply also for the name of the concepts of the domain model. Comments/propositions? Cheers... Sébastien -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : mercredi 8 octobre 2008 21:46 À : marte-ftf@omg.org Objet : Re:issue 12249, use of prefixes on stereotypes Hi everyone, I am out of hospital and gradually returning to normal life. ***************** I introduced this issue, and it is big one in terms of effort, so I will try to collect together the reasons for doing it. We should decide on the principle of prefixes before discussing how they could be formed. 1. We have introduced many hundreds of stereotypes in MARTE, no designer is going to be able to remember them all. 2. Prefixes help to recognize that a property is defined by a standard, with semantics defined by the standard, rather than an application-specific property with semantics defined in the application. 3. Quick recognition by an analyst who is mainly focussed on a class of properties, makes it practical to navigate the diagrams and recognize the significance of properties in context. We have lots of experience of this with performance properties in SPT. This could be satisfied by prefixes on analysis properties only, but I think the same applies to model concepts and properties. 4. Robust and simpler implementation of tools to extract properties from XMI generated by models. Mechanical tools can filter information using the prefixes, and simplify their implementation. This would apply to MDE transformation tools as well as analysis tools, I think, and could encourage the creation of tools. 5. Risk of name conflict. Suppose a design is created without MARTE, and uses some generic concept like a clock, and introduces an application property with a name conflict with MARTE. If it is then decided to exploit MARTE to elaborate or analyze the design, the confusion might be very difficult to untangle. (This is less of a problem if MARTE is used from the beginning as many tools will immediately identify the name as already defined). In turn, this could inhibit the use of MARTE on existing specifications, and require the decision to use it, to be made right at the start... which would make users shy away from MARTE. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) sebastien.demathieu.vcf