SV-EC Meeting Minutes
7 July 2003   11:00 am. Monday

Voting Members (3/4 or > 75%)
(r)
(a) Arturo Salz (Synopsys)
(-) Brad Pierce (Synopsys)
(a) David Smith (Synopsys)
(-) Francoise Martinolle (Cadence)
(a) Jay Lawrence (Cadence)
(-) Jeff Freedman (ModelTech)
(a) Michael Burns (Motorola)
(-) Mehdi Mohtashemi (Synopsys)
(a) Neil Korpusik (Sun)

Non-Voting Members (attendance based)
(-) Chris Spear (Synopsys)
(-) Dennis Brophy (ModelTech)
(a) Dave Rich (Synopsys)

Guests (non-voting)
(-) Cliff Cummings (IEEE 1364)
(-) Stefen Boyd (IEEE 1364)
(-) Stu Sutherland (IEEE 1364)
(-) Kevin Cameron (National)

Inactive Members (Missed last 4 meetings)

r => Regular meeting
x => Extra meeting (Presence counts for attendance, absence does not)

a => Attended
p => Attended by proxy
- => Missed


Action Items: 
    [identified with AI (#) in this text, # refers to AI number]
    David: Talk with Karen about EXT-5 disposition within SV-BC.
    David: Fix A.a under donations and change Issues to Errata on site.
    All members: Review Operating Guidelines
    All members: Review list and provide prioritization
    	(1-3: 1 - strong, 2 - don't care, 3 - not important)

Minutes 7/7/03 taken by David Smith

1. Review of Operating Guidelines
    Mission/Goals/Objectives
    	Mike Burns:
		Is the DVCON the real issue? Can we avoid the mad rush at the end that we had for 3.1.
	David: 
		The real date is Feb 24.
	Jay:
		Does not incorporate feedback from experts or users. Suggest was adding users to
		Goal A.
    Process
    Donation/Proposal
	Neil:
		A.a - what does the sentance mean?
	David:
		Typo. Should be "Does it address the topic". Will be fixed.
    Errata
    	David:
		Use of RT for errata if available.
	Jay:
		The role of champion appears to be a veto. Role did not exist. 
	Neil:
		Agree with Jay. What is the role of this?
	Mike:
		I would also agree with concern. Normally handled through persuasion. This issue
		only happens when time comes up.
	Jay:
		If the expert makes his concerns known then they generally get their way.
    Voting Structure/Rules
    	David:
		The 75% does not carry over but the 3/4 does for 3.1a. Essentially the individuals
		that had voting rights at the end of 3.1 will have voting rights at the start of
		3.1a and are granfathered in for the first 3 meetings of 3.1a.
    Milestones
    Deliverables

    David:
    	Members are on the web site without email addresses. If anyone objects then they need to
	notify me.

2. Review and prioritization of 3.1a Enhancements/Extensions
    David:
    	Any missing or suprising items?
    Jay:
    	What are RandCase or Stream Generation?
    Arturo:
    	RandCase is a simple extension for random selection of case items. The Stream generation
	provides a grammer for randomly generating valid token streams.
    Jay:
    	Optional ordering was closed in SV-BC. Need to talk with Karen.
    David:
    	Please review the items in the Extensions and send prioritization to the reflector before
	the next meeting.

    Discussion of what is errata and what is enhancement/extension. Concern was raised that since
    enhancements require implementation and the guidelines do not specifically indicate that multiple
    proposals can be made that acceptance of a proposal could occur before multiple proposals are
    known to be available.

    David: Clearly the implementation and submission guidelines are for enhancements/extensions. The
	errata follow a somewhat different process since they are related to fixes of the 3.1 LRM
	while submissions are for technology that is not present in the 3.1 LRM. It is unlikely that
	we would accept a submission at the same time it is submitted - we have to at least review
	the submission to accept. This will occur after the committment to submit is made. If there
	is another submission that is intended to be made on the same topic the submitter should
	notify the committee as soon as the original submission is comitteed.

3. Discussion of outstanding issues and issue gathering
    Mike:
    	Please change Open Issues to Errata
    Mike:
    	Would like to wait for the update the guidelines and get the feedback from chairs before
	voting.
    Jay:
    	Would like to make first order of business voting on guidelines at next meeting.

4. Next meeting: 21 July 2003 at 11:00am

5. Close of meeting