Mark and others - 
 > Meeting minutes from the 4/29/98 DC-WG teleconference
...
 >   The next meeting will be a teleconference on Wednesday, 5/13/98,
 >   from 9-11 PDT.  This overlaps with CICC, which affects Enrico but
 >   not the others in the group.
I apologize but I will be in San Jose at a meeting during that time.
Mark - I will try to contact after the meeting if I can catch you
for a quick debrief.
 > Action Items:
 >       Who         When            What
 >       ----------  --------------  --------
...
 >  2.   Steve       5/12            Send pointers to documentation on EXPRESS
 >                                   to the reflector.
I am getting this from a colleague at NIST and hope to have it posted
to you by Wednesday.
 > Details:
 > 
 >   1. Charter/scope discussion
 >      - Finalize position on deliverables
 >      - Update on other groups (SLDL, IEEE P1500)
 > 
 >      We talked about the set of deliverables, and there was
 >      general agreement on the proposal to include
 >        - A presentation on the conceptual model, combining
 >          ideas from the different point of views.
 >        - A constraint dictionary
 >        - A constraint command language
 > 
 >      Jin will write up an updated version of the charter/scope document.
 > 
 >      We talked about EXPRESS and EXPRESS/G.  Steve volunteered
 >      to work on an EXPRESS model, which would be useful in checking
 >      consistency as we define the command language.  We stopped short
 >      of including the EXPRESS model as a deliverable.
That scope is still OK with me...
 >   3. Constraint dictionary discussion
 > 
 >      We agreed that it would be useful to add a column on the
 >      verification strategy for each constraint (a short description
 >      of how the design should be checked to see if the constraint is
 >      satisfied or not).  For example, an area constraint can be checked
 >      to see whether the estimated/actual area lies within the min/max
 >      range of values defined by the constraint.
 > 
 >      The constraint dictionary will be used as the basis for refining
 >      the conceptual model.  We will use concrete examples of the
 >      constraints described in the dictionary to evaluate what kinds of
 >      common verification procedures and consistency checking would be
 >      possible and useful, as well as looking at other issues such as
 >      constraint transformations and logical/physical hierarchy.
Good...
 > -- 
 > Mark Hahn                                          phone: (408) 428-5399
 > Architect, Deep Submicron Business Unit            fax:   (408) 428-5959
 > Cadence Design Systems                             email: mhahn@cadence.com
 > 
--Boundary_(ID_cRYFDiAqRX52yo7e+5nj9Q)--