Issue 15371: UML 2.3 Superstructure: Non-sensible text for modelLibrary stereotype (uml2-rtf) Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com) Nature: Uncategorized Issue Severity: Summary: The description for the stereotype in Annex C contains significant semantics which are not reflected anywhere else in the specification, nor as Constraints associated with the stereotype. Because this is a stereotype, not a keyword, these are not warranted. The full text is as follows: A package that contains model elements that are intended to be reused by other packages. Model libraries are frequently used in conjunction with applied profiles. This is expressed by defining a dependency between a profile and a model library package, or by defining a model library as contained in a profile package. The classes in a model library are not stereotypes and tagged definitions extending the metamodel. A model library is analogous to a class library in some programming languages. When a model library is defined as a part of a profile, it is imported or deleted with the application or removal of the profile. The profile is implicitly applied to its model library. In the other case, when the model library is defined as an external package imported by a profile, the profile requires that the model library be there in the model at the stage of the profile application. The application or the removal of the profile does not affect the presence of the model library elements Specifically the problems are: a) More specifics should be given for “This is expressed by for a dependency between a profile and a model library package” – such as the direction and name. b) Replace ‘tagged definitions’ by ‘properties’ or at least ‘tag definition’ c) The text ‘is imported or deleted’ is vague and goes beyond anything in Profile semantics (for example does it mean a PackageImport is implicitly created?) d) “The profile is implicitly applied to its model library” does not make sense except in the specific case that the model library is a set of stereotyped elements, regardless of whether the model library owned by the profile: if the model library is for use within or with the profile why would it be necessary to apply stereotypes to its elements? And it goes beyond Profile semantics as well as resulting in a circular dependency between library and profile. e) “In the other case, when the model library is defined as an external package imported by a profile,” is inconsistent with the earlier description of ‘the other case’ which is as defined via a Dependency (not an import). f) “the profile requires that the model library be there in the model at the stage of the profile application” is both vague (‘be there’) and beyond profile semantics. Proposed resolution Replace the paragraph with the following: A package that contains model elements that are intended to be reused by other packages. Though model libraries are frequently used in conjunction with applied profiles, the classes in a model library are not stereotypes extending the metamodel. A model library is analogous to a class library in some programming languages. Resolution: Revised Text: Actions taken: July 13, 2010: received issue Discussion: End of Annotations:===== s is issue # 15371 From: "Pete Rivett" UML 2.3 Superstructure: Non-sensible text for modelLibrary stereotype The description for the stereotype in Annex C contains significant semantics which are not reflected anywhere else in the specification, nor as Constraints associated with the stereotype. Because this is a stereotype, not a keyword, these are not warranted. The full text is as follows: A package that contains model elements that are intended to be reused by other packages. Model libraries are frequently used in conjunction with applied profiles. This is expressed by defining a dependency between a profile and a model library package, or by defining a model library as contained in a profile package. The classes in a model library are not stereotypes and tagged definitions extending the metamodel. A model library is analogous to a class library in some programming languages. When a model library is defined as a part of a profile, it is imported or deleted with the application or removal of the profile. The profile is implicitly applied to its model library. In the other case, when the model library is defined as an external package imported by a profile, the profile requires that the model library be there in the model at the stage of the profile application. The application or the removal of the profile does not affect the presence of the model library elements Specifically the problems are: a) More specifics should be given for .This is expressed by for a dependency between a profile and a model library package. . such as the direction and name. b) Replace .tagged definitions. by .properties. or at least .tag definition. c) The text .is imported or deleted. is vague and goes beyond anything in Profile semantics (for example does it mean a PackageImport is implicitly created?) d) .The profile is implicitly applied to its model library. does not make sense except in the specific case that the model library is a set of stereotyped elements, regardless of whether the model library owned by the profile: if the model library is for use within or with the profile why would it be necessary to apply stereotypes to its elements? And it goes beyond Profile semantics as well as resulting in a circular dependency between library and profile. e) .In the other case, when the model library is defined as an external package imported by a profile,. is inconsistent with the earlier description of .the other case. which is as defined via a Dependency (not an import). f) .the profile requires that the model library be there in the model at the stage of the profile application. is both vague (.be there.) and beyond profile semantics. Proposed resolution Replace the paragraph with the following: A package that contains model elements that are intended to be reused by other packages. Though model libraries are frequently used in conjunction with applied profiles, the classes in a model library are not stereotypes extending the metamodel. A model library is analogous to a class library in some programming languages. Date: Mon, 18 Mar 2013 17:48:50 +0000 From: Dave Hawkins User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 To: "Manfred R. Koethe" CC: "uml25-ftf@omg.org" Subject: [UML 2.5 FTF] Ballot 3 - Preview 3 - Issue 15371 X-Source-IP: userp1040.oracle.com [156.151.31.81] X-Virus-Scanned: amavisd-new at omg.org X-Brightmail-Tracker: AAAAAR0YqyA= X-Brightmail-Tracker: AAAAAA== The clause "the classes in a model library are not stereotypes extending the metamodel," seems like a rather odd way to say "they must not contain stereotypes." It's also not really complete as I think the intention is to prohibit model libraries from containing metamodel extension classes, ie Stereotype, Extension, ExtensionEnd and Profile. Dave On 16/03/13 21:03, Manfred R. Koethe wrote: Dear Colleagues, Here is Preview 3 of Ballot 3. Issue 8274 and 17933 are withdrawn from this ballot. Kind regards, Manfred --------------------------------------------------------------- Manfred R. Koethe 88solutions Corporation tel: +1 (617) 848 0525 fax: +1 (815) 550 2086 mailto: koethe@88solutions.com web: http://www.88solutions.com --------(Model-Driven Modeling Solutions)-------- -- Dave Hawkins | Principal Software Engineer | +44 118 924 0022 Oracle JDeveloper Development Oracle Corporation UK Ltd is a company incorporated in England & Wales. Company Reg. No. 1782505. Reg. office: Oracle Parkway, Thames Valley Park, Reading RG6 1RA. From: Steve Cook To: Dave Hawkins , "Manfred R. Koethe" CC: "uml25-ftf@omg.org" Subject: RE: [UML 2.5 FTF] Ballot 3 - Preview 3 - Issue 15371 Thread-Topic: [UML 2.5 FTF] Ballot 3 - Preview 3 - Issue 15371 Thread-Index: AQHOJAEEI4O8ox29rU+Cqz+TIe1+QZir0X2Q Date: Mon, 18 Mar 2013 19:27:19 +0000 Accept-Language: en-GB, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.166.18.103] X-Forefront-Antispam-Report: CIP:131.107.125.37;CTRY:US;IPV:CAL;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(51704002)(24454001)(71364001)(479174001)(199002)(189002)(13464002)(5403001)(5343655001)(76482001)(54356001)(51856001)(56816002)(15202345001)(74502001)(74662001)(54316002)(33656001)(16601075001)(44976002)(47446002)(31966008)(46406002)(47976001)(50466001)(47736001)(55846006)(16406001)(5343635001)(79102001)(69226001)(56776001)(53806001)(80022001)(77982001)(59766001)(65816001)(49866001)(20776003)(46102001)(4396001)(50986001)(47776003)(23726001)(63696002);DIR:OUT;SFP:;SCL:1;SRVR:BY2FFO11HUB036;H:TK5EX14HUBC107.redmond.corp.microsoft.com;RD:InfoDomainNonexistent;A:1;MX:1;LANG:en; X-OriginatorOrg: microsoft.onmicrosoft.com X-Forefront-PRVS: 07891BF289 X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id r2IJS0Ff021729 X-Brightmail-Tracker: AAAAAR0YqyA= X-Brightmail-Tracker: AAAAAA== How about "Though model libraries are frequently used in conjunction with applied profiles, elements in a model library may not include Stereotypes, or instances of the other metamodel extension metaclasses specified in clause 12.3 - Profiles"? -- Steve -----Original Message----- From: Dave Hawkins [mailto:dave.hawkins@oracle.com] Sent: 18 March 2013 17:49 To: Manfred R. Koethe Cc: uml25-ftf@omg.org Subject: [UML 2.5 FTF] Ballot 3 - Preview 3 - Issue 15371 The clause "the classes in a model library are not stereotypes extending the metamodel," seems like a rather odd way to say "they must not contain stereotypes." It's also not really complete as I think the intention is to prohibit model libraries from containing metamodel extension classes, ie Stereotype, Extension, ExtensionEnd and Profile. Dave On 16/03/13 21:03, Manfred R. Koethe wrote: > Dear Colleagues, > > Here is Preview 3 of Ballot 3. Issue 8274 and 17933 are withdrawn from this ballot. > > Kind regards, > > Manfred > > --------------------------------------------------------------- > Manfred R. Koethe 88solutions Corporation > tel: +1 (617) 848 0525 fax: +1 (815) 550 2086 > mailto: koethe@88solutions.com > web: http://www.88solutions.com > --------(Model-Driven Modeling Solutions)-------- > > > > > > > -- Dave Hawkins | Principal Software Engineer | +44 118 924 0022 Oracle JDeveloper Development Oracle Corporation UK Ltd is a company incorporated in England & Wales. Company Reg. No. 1782505. Reg. office: Oracle Parkway, Thames Valley Park, Reading RG6 1RA. Date: Tue, 19 Mar 2013 16:56:35 +0000 From: Dave Hawkins User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 To: Steve Cook CC: "Manfred R. Koethe" , "uml25-ftf@omg.org" Subject: Re: [UML 2.5 FTF] Ballot 3 - Preview 3 - Issue 15371 X-Source-IP: userp1040.oracle.com [156.151.31.81] X-Virus-Scanned: amavisd-new at omg.org X-Brightmail-Tracker: AAAAAR0YqyA= X-Brightmail-Tracker: AAAAAA== That's better, but I don't think the subordinate clause "Though model libraries..." really helps. Is the following an improvement? A package that contains model elements that are intended to be reused by other packages. It is analogous to a class library in some programming languages. The model library may not include instances of the metamodel extension metaclasses specified in Clause 12.3, such as Profiles and Stereotypes. However it may include ProfileApplications and stereotype applications, and a model library is often used in conjunction with an applied profile. Dave On 18/03/13 19:27, Steve Cook wrote: How about "Though model libraries are frequently used in conjunction with applied profiles, elements in a model library may not include Stereotypes, or instances of the other metamodel extension metaclasses specified in clause 12.3 - Profiles"? -- Steve -----Original Message----- From: Dave Hawkins [mailto:dave.hawkins@oracle.com] Sent: 18 March 2013 17:49 To: Manfred R. Koethe Cc: uml25-ftf@omg.org Subject: [UML 2.5 FTF] Ballot 3 - Preview 3 - Issue 15371 The clause "the classes in a model library are not stereotypes extending the metamodel," seems like a rather odd way to say "they must not contain stereotypes." It's also not really complete as I think the intention is to prohibit model libraries from containing metamodel extension classes, ie Stereotype, Extension, ExtensionEnd and Profile. Dave On 16/03/13 21:03, Manfred R. Koethe wrote: Dear Colleagues, Here is Preview 3 of Ballot 3. Issue 8274 and 17933 are withdrawn from this ballot. Kind regards, Manfred --------------------------------------------------------------- Manfred R. Koethe 88solutions Corporation tel: +1 (617) 848 0525 fax: +1 (815) 550 2086 mailto: koethe@88solutions.com web: http://www.88solutions.com --------(Model-Driven Modeling Solutions)-------- -- Dave Hawkins | Principal Software Engineer | +44 118 924 0022 Oracle JDeveloper Development Oracle Corporation UK Ltd is a company incorporated in England & Wales. Company Reg. No. 1782505. Reg. office: Oracle Parkway, Thames Valley Park, Reading RG6 1RA. -- Dave Hawkins | Principal Software Engineer | +44 118 924 0022 Oracle JDeveloper Development Oracle Corporation UK Ltd is a company incorporated in England & Wales. Company Reg. No. 1782505. Reg. office: Oracle Parkway, Thames Valley Park, Reading RG6 1RA.