Issue 4212: Production by Package Extent Example in 00-12-05                                                                                                                                                        (xmi-rtf)
Source: University of Ireland (Mr. Ronan Conlon, )
Nature: Uncategorized Issue
Severity: 
Summary: I was reading document 00-11-02, i.e. the XMI 1.1 specs, and I was a bit confused with the example of production by Package Extent on page 5-12.

Should the line which says, "Similarly, the second Node in the NodeClass extent..." actually say, "...the second Net in the NetClass extent... "???

There is no reference to PDT, one of the XMI.field values of the second Net object. Also, there seems to be no reference to NodeZ in the same XML, although NodeW is referenced again.

Are these typos??? Sorry for nitpicking :)

Resolution: 
Revised Text: 
Actions taken:
February 22, 2001: received issue
October 3, 2001: XMI 1.2 RTF deferred this issue to a later RTF
Discussion: 

End of Annotations:=====
From: Andris Vignaga <avignaga@fing.edu.uy>
To: <issues@omg.org>
Subject: OCL issue
Date: Fri, 8 Dec 2000 12:25:48 -0300
Message-ID: <NEBBJBONILHNJIMFCPMLKECOCAAA.avignaga@fing.edu.uy>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Type: text/plain;
	      charset="iso-8859-1"
X-UIDL: bf9!!@,0!!gn=e9D@$"!

Descriptor: OCL: Created and Destroyed instances
Source: Andres Vignaga, Universidad de la Republica (Uruguay)
Reference: OCL
Nature: Enhancement
Severity: Medium
Summary:

Usually, the behaviour of an operation is described by pre and
postconditions, and then shown in a collaboration diagram. In turn, in
a
collaboration diagram one can model (via the standard stereotypes
create and
destroy) the creation and destroying of instances, but this is not in
the
case in OCL. It would be useful to be able to explicitly model in a
postcondition that an instance ocurring in the expression was created
during
the execution of the operation being specified. Since introducing a
command
is not possible, this feature could be achieved by just 'declaring' in
the
postcondition that the instance 'was created'.

For example:

    context X::operation()
    post: self.attr = self.attr@pre->including(created p)

this declares that p was created during the execution of operation,
and it
was not taken from elsewhere.