From: Don Organ
Sent: Tuesday, January 28, 2003 10:23
AM
To: STIL. 4 (E-mail)
Subject: stds-1450.4: Teleconference
meeting minutes 1/28/2003
Minutes of
1/28/2003
Dave
Dowding
Jim
O'Reilly
Don
Organ
Ernie
Wahl
Tom
Micek
Jim
Mosley
--------------------------------------------------
Multisite
A quick review of
the "blue" multisite syntax in the December 9 2002 pdf document.
Issues
raised:
- The port priority
is implicit by ordering in the syntax (perhaps could be overridden by further
syntax - such as via a strategy file).
- Glossary should
include FlowGroup, TestMethod, TestObject
Jim O'Reilly's Use
Case
Already has been
discussed in a couple of previous meetings. A summary of some of the
issues:
- if we agree that
the Measured field of the spec variable, then we need to identify the syntax
as to how the .Meas value is updated. Also, if we have global variables, how
are they updated.
- from a multsite
perspective, the values of a .Meas must be unique across each
site
- life-time
(persistence) of a .Meas value? How long does a value in the .Meas last (until
the end of the device? end of lot?) What is the syntax to flag that the value
is no longer valid. How does the value become invalidated after that
time? What happens if a reference is made to a value that has
"expired"?
- if we support
variables other than specs, than how are the other variables defined and
referenced?
Dave will have
translate the first use-case into syntax (by the weekend?).
Jim O'Reilly has
ideas for another use-case, he may pursue.
Regarding the syntax
- would like to have the order of Ins and Outs less restrictive - i.e. the
can be mixed in any order(on page 3, for example)
-DVO-
---------------------------------------------------------------------------------
Don
Organ
Inovys Corporation
---------------------------------------------------------------------------------