Issue 19538: Another UML 2.5 Beta 2 XMI invalidity (uml2-rtf) Source: Oracle (Mr. Dave Hawkins, dave.hawkins(at)oracle.com) Nature: Uncategorized Issue Severity: Summary: For constraint specifications that "Cannot be expressed in OCL", there is an invalid language attribute in the XMI. For example: <specification xmi:type="uml:OpaqueExpression" xmi:id="ObjectFlow-same_upper_bounds-_specification" language=""/> language is a multivalued property with primitive type and these can only be represented as elements. (In 2.4.1 such unexpressable constraints were represented as (OCL,true), it's not clear the above change is intentional.) Resolution: Revised Text: Actions taken: July 22, 2014: received issue Discussion: End of Annotations:===== te: Tue, 22 Jul 2014 18:09:36 +0100 From: Dave Hawkins User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 To: OMG Issues , "uml2-rtf@omg.org" Subject: Another UML 2.5 Beta 2 XMI invalidity X-Source-IP: ucsinet22.oracle.com [156.151.31.94] X-Virus-Scanned: amavisd-new at omg.org For constraint specifications that "Cannot be expressed in OCL", there is an invalid language attribute in the XMI. For example: language is a multivalued property with primitive type and these can only be represented as elements. (In 2.4.1 such unexpressable constraints were represented as (OCL,true), it's not clear the above change is intentional.) Cheers, Dave -- 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. X-CM-Score: 0.00 X-CNFS-Analysis: v=2.1 cv=aY3vnHYt c=1 sm=1 tr=0 a=fozlfgnt8AxaPxDmTtzwNQ==:117 a=fozlfgnt8AxaPxDmTtzwNQ==:17 a=0Bzu9jTXAAAA:8 a=u9EReRu7m0cA:10 a=D9M0StDeE58A:10 a=8nJEP1OIZ-IA:10 a=YYzpnO7rAAAA:8 a=4Sg5CoXf9ohCdTCkr0sA:9 a=wPNLvfGTeEIA:10 X-AUTH: edwillink+ed:2500 Date: Tue, 22 Jul 2014 18:25:16 +0100 From: Ed Willink User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 To: OMG Issues , "uml2-rtf@omg.org" Subject: Re: Another UML 2.5 Beta 2 XMI invalidity X-Virus-Scanned: amavisd-new at omg.org Hi My OCL loading/checking has had to be a little enlightened. e.g. any excess languages are redundant. e.g. the first missing language is OCl. The WFRs are very vague where present. The variation in the UML 2.5 is mucgh less than it was. Ideally there should be a distinction between: cannot be expressed in IBM RSA: OCL 2.2 cannot be expresssed till OCL 2.5 provides reflection support cannot be sensibly expressed in OCL ever and there should be no constraints that are actually just waiting for a roundtuit. Regards Ed Willink On 22/07/2014 18:09, Dave Hawkins wrote: For constraint specifications that "Cannot be expressed in OCL", there is an invalid language attribute in the XMI. For example: language is a multivalued property with primitive type and these can only be represented as elements. (In 2.4.1 such unexpressable constraints were represented as (OCL,true), it's not clear the above change is intentional.) Cheers, Dave From: Ed Seidewitz To: "uml2-rtf@omg.org" Subject: Re: Another UML 2.5 Beta 2 XMI invalidity Thread-Topic: Another UML 2.5 Beta 2 XMI invalidity Thread-Index: AQHPpc/icCee3/4iOUKOrZIoPcC3yZusmzwA///TXwA= Date: Tue, 22 Jul 2014 18:45:33 +0000 Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [108.51.109.141] X-Mailprotector-Decision: deliver X-Mailprotector-Original-Sender: ed-s@modeldriven.com X-Mailprotector-Original-Recipients: uml2-rtf@omg.org X-Mailprotector-Redirect-To: ed-s@modeldriven.com X-Mailprotector-Connection: TLSv1|ec2-54-208-239-9.compute-1.amazonaws.com|54.208.239.9|CAS202.mailprotector.local|0.0|0.0|0|||0|0|0|0 X-Mailprotector-Results: clean X-Mailprotector-Score: 0 X-Mailprotector-IP-Analysis: 0, 54.208.239.9, Ugly c=0 p=0 Source New X-Mailprotector-Scan-Diagnostics: 0-0-0-5439-c X-Mailprotector-ID: d3748ccd-c3db-4bc8-b491-1af6da8f3fd1 X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id s6MIjvvH001834 All UML constraints that we felt were expressible in OCL should be expressed in OCL in the UML 2.5 specification. There were still some that we felt could not be expressed in OCL (at least as of OCL 2.4 ‹ we did not speculate on expressibility in OCL 2.5). Since a Constraint is required to have a specification, we decided that if we could not express the constraint in OCL, we would just have the specification be an OpaqueExpression with no body (which is legal). The document generation process then inserts the text ³Cannot be expressed in OCL² into the spec document for such constraints. Dave is right that it is not proper to have a XMI attribute for the XMI for OpaqueExpression::language, and an OpaqueExpression with no body elements should not have any language elements either. This seems to be an error in both the Beta 1 and Beta 2 XMI (but while not proper XMI, at least it is legal XML!). ‹ Ed On 7/22/14, 1:25 PM, "Ed Willink" wrote: >Hi > >My OCL loading/checking has had to be a little enlightened. > >e.g. any excess languages are redundant. >e.g. the first missing language is OCl. > >The WFRs are very vague where present. > >The variation in the UML 2.5 is mucgh less than it was. > >Ideally there should be a distinction between: > >cannot be expressed in IBM RSA: OCL 2.2 >cannot be expresssed till OCL 2.5 provides reflection support >cannot be sensibly expressed in OCL ever > >and there should be no constraints that are actually just waiting for a >roundtuit. > > Regards > > Ed Willink > > >On 22/07/2014 18:09, Dave Hawkins wrote: >> For constraint specifications that "Cannot be expressed in OCL", >> there is an invalid language attribute in the XMI. For example: >> >> > xmi:id="ObjectFlow-same_upper_bounds-_specification" language=""/> >> >> language is a multivalued property with primitive type and these >> can only be represented as elements. >> >> (In 2.4.1 such unexpressable constraints were represented as >> (OCL,true), it's not clear the above change is intentional.) >> >> Cheers, >> >> Dave >> >