Subject: Gate connection
From: Thomas Weigert (thomas.weigert#motorola.com)
Date: Fri Mar 08 2002 - 15:20:24 GMT
Andreas,
I am not confident that your explanation is correct.
Consider an agent type X with a gate G. Now consider another agent Y which
contains two instance sets of agents, y1:Y and y2:Y (both of type Y)
connected by a channel.
How do you differentiate, in the abstract representation of the system, the
instance of gate G on y1 and the instance of gate G on y2?
As far as I can see, the only representation of gates we have is in types.
But this does not allow us to distinguish the different instances of gates.
There must be, I think, something in the abstract syntax that would allow us
to say that, for example, the channel above is between the gate G of y1 and
the gate G of y2.
Thanks, Thomas.
> -----Original Message-----
> > From: Andreas Prinz <prinz#dagstuhl.de>
> > Date: Thu, 7 Mar 2002 15:52:21 +0100 (MET)
> >
> > Dear Rick,
> > as far as I understand, every channel gets connected
> > to a gate after several transformations. That is why
> > we do not have the state machine or agent there.
> > The gate should be unique here.
> >
> > The relevant portion of Z.100 does state:
> > If <gate> is specified, the channel is connected to that gate.
> > The gate and the channel must have at least one common element in their
> > signal lists in the same direction. If no <gate> is specified,
> the following
> > rules apply:
> > a) if the channel endpoint is an agent or state machine and
> that agent/state
> > contains a <channel to channel connection> for the channel,
> > the channel is connected to the implicit gate introduced by
> > the <channel to channel connection>;
> > b) if the channel endpoint is a state, the channel is connected to the
> > implicit gate of that state machine (see Annex F),
> > otherwise the channel introduces an implicit gate on the agent or state
> > mentioned in <channel endpoint>. This gate obtains the <signal list> of
> > the respective <channel path>s as its corresponding gate constraint.
> > The channel is connected to that gate.
> >
> > The same is specified in Z.100.F2, where first in
> > the transformations part a gate is generated everywhere
> > and afterwards the agent /state machine is ignored
> > in the mapping.
This archive was generated by hypermail 2a23 : Mon May 05 2008 - 20:30:55 GMT