Issue 4902: Runtime Instance                                                                                                                                                                                        (action-semantics-ftf)
Source: International Business Machines (Mr. Sridhar Iyengar, siyengar@us.ibm.com)
Nature: Uncategorized Issue
Severity: 
Summary: [Sridhar Iyengar] 4. I was confused when trying to interpret
'runtimeinstance' data type - but after the explanation (from
Conrad/Steve/Jim) about the removal of the execution model (with the
associated ripple effect on change bars in most of the submission which
slowed my review), I realize that this will not cause any interchange or
interoperability problems.  I recommend that this usage be clarified in
the spec, so others dont get confused either.

30. ReclassifyObjectAction class.  The text specifies the Association
'input' to be of type 'RuntimeObject'.  This clearly cannot be right
because 'RuntimeObject' is not defined as a class in the metamodel.  The
type should be 'InputPin'.

Resolution: see below
Revised Text: In all chapters, replaced RuntimeInstance with "T where T is"
    followed by an English description from the well formedness rules
    constraining the type of the pin
Actions taken:
March 5, 2002: received issue
December 11, 2002: closed issue
Discussion: 
Replace RuntimeInstance with "t [<multiplicity>] where t is
constraint using dot notation.

End of Annotations:=====
Reply-To: <conrad.bock@kabira.com>
From: "Conrad Bock" <conrad.bock@kabira.com>
To: <issues@omg.org>
Subject: Action semantic FTF issues
Date: Tue, 5 Mar 2002 12:07:34 -0800
Message-ID: <NDBBJCCGLKIFNFMGDBHNMEPIDPAA.conrad.bock@kabira.com>
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.2314.1300
Content-Type: text/plain;
	      charset="iso-8859-1"
X-UIDL: f'm!!V?Oe9f?<!!8)ld9


Hi Juergen,

Here are the initial action semantics FTF issues, hope its alright to
send them all at once.  There should be 44 total.  What will the URL
for
the issues list be?

Conrad




********************************************************************
********************************************************************

Summary: Runtime Instance

Text: 

[Sridhar Iyengar] 4. I was confused when trying to interpret
'runtimeinstance' data type - but after the explanation (from
Conrad/Steve/Jim) about the removal of the execution model (with the
associated ripple effect on change bars in most of the submission
which
slowed my review), I realize that this will not cause any interchange
or
interoperability problems.  I recommend that this usage be clarified
in
the spec, so others dont get confused either.

30. ReclassifyObjectAction class.  The text specifies the Association
'input' to be of type 'RuntimeObject'.  This clearly cannot be right
because 'RuntimeObject' is not defined as a class in the metamodel.
The
type should be 'InputPin'.



From: Edwin Seidewitz <eseidewitz@intelidata.com>
To: "Action Semantics FTF (E-mail)" <action-semantics-ftf@omg.org>
Subject: Comments on the draft action FTF ballot
Date: Thu, 14 Mar 2002 11:46:53 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	      boundary="----_=_NextPart_001_01C1CB77.D8820170"
X-UIDL: *kJd9hR8!!bk8!!=<!!!


Some relatively minor points on the draft ballot: 

Issue 4902: Runtime Instance 

The discussion currently reads: 

    Replace RuntimeInstance with "t [<<multiplicity>>] where t is 
    <<constraint using dot notation>>". 

I would suggest the following slight modification: 

Replace RuntimeInstance and RuntimeObject with "T [<<multiplicity>>],
where T = <<constraint using OCL notation>>".