Issue 15219: OCL 2.2 Clarity of qualified path names (ocl2-rtf)
Source: Nomos Software (Dr. Edward Willink, ed(at)willink.me.uk)
Nature: 
Severity: 
Summary: At the end of Section 7.4.6 OCL 2.2 says


"For clarity, the qualified form may only be used with an explicit source
expression."


thereby requiring "self.Person::age()" rather than just "Person::age()".


This 'clarity' is surely just a stylistic issue.


An organisation may advocate an OCL-style guide that discourages the use of
implicit-self.
That is a free choice made by that organisation.


It does not seem appropriate for one corner of the OCL specification to
prohibit implicit-self
where consistency would imply that it should be present.


This is not a 'clarity', it is a confusion.


Suggest allow implicit-self before qualified path names (unless there is a
different
strong technical reason.)
Resolution: 
Revised Text: 
Actions taken:
April 22, 2010: received issue
Discussion: 

End of Annotations:=====

m: "Willink, Ed" <Ed.Willink@thalesgroup.com>
To: "'issues@omg.org'" <issues@omg.org>
Subject: OCL 2.2 Clarity of qualified path names
Date: Thu, 22 Apr 2010 14:31:05 +0100
X-Mailer: Internet Mail Service (5.5.2657.72)


Hi


[Juergen: Please use: "Issue xyzzy: OCL 2.2 - Clarity of qualified path
names"
rather than just "Issue xyzzy - OCL 2.2 Issue" as the moderated email
title.]


At the end of Section 7.4.6 OCL 2.2 says


"For clarity, the qualified form may only be used with an explicit source
expression."


thereby requiring "self.Person::age()" rather than just "Person::age()".


This 'clarity' is surely just a stylistic issue.


An organisation may advocate an OCL-style guide that discourages the use of
implicit-self.
That is a free choice made by that organisation.


It does not seem appropriate for one corner of the OCL specification to
prohibit implicit-self
where consistency would imply that it should be present.


This is not a 'clarity', it is a confusion.


Suggest allow implicit-self before qualified path names (unless there is a
different
strong technical reason.)


        Regards
                        
                Ed Willink


****************************************************************************
Please consider the environment before printing this email.
Thales Research and Technology (UK) Limited DISCLAIMER:  The information
contained in this e-mail is confidential.  It may also be legally
privileged.  It is intended only for the stated addressee(s) and access to
it by any other person is unauthorised.  If you are not an addressee, you
must not disclose, copy, circulate or in any other way use or rely on the
information contained herein.  Such unauthorised use may be unlawful.  We
may monitor all e-mail communications through our networks.  If you have
received this e-mail in error, please inform us immediately on +44 (0)1293
575987 and delete it and all copies from your system.  We accept no
responsibility for changes to any e-mail which occur after it has been sent.
Attachments to this e-mail may contain software viruses which could damage
your system.  We therefore recommend you virus-check all attachments before
opening.  The registered office of Thales Research and Technology (UK)
Limited is at: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone,
Weybridge, Surrey KT15 2NX.  Registered in England No. 774298.
****************************************************************************