RE: [sv-ec] email ballot: response due by 11:00am PDT Friday May 1 2009

 I vote yes on most proposals except for id 19 and 183 for which I would
like a different resolution.
 
Francoise
      '

	id 48  allow for future enhancement

	      ___ X __ YES   _____ No

	 

	id 54  allow for future enhancement

	      ___ X __ YES   _____ No

	 

	id 16, 17

	   sv-ec agrees with sv-cc resolution to keep these regions for
future use. 

	   Reject svdb 2632 statement. 

	   __ X ___ YES   _____ No

	 

	id 19  No action required

	    _____ YES   ___ X __ No   I would add the bubble with
preponed for showing the PLI region, at least it shows consistency. 

	 

	id 20    svdb 2634  (svbc issue)

	    sv-ec votes as well to accept the proposal as well.

	   __ X ___ YES   _____ No 

	http://www.eda.org/svdb/view.php?id=2634  

	 

	id 105 (id 110 is duplicate of 105)

	     No action required

	    ___ X __ YES   _____ No

	 

	id 115  No action required

	    ___ X __ YES   _____ No

	 

	 

	id 35, svdb 2705    __ X ___ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2705 

	 

	 

	ids 36,37,38,39,40

	svdb 2700    __ X ___ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2700  

	 

	 

	id 41, svdb 2681    __ X ___ YES   _____ No

	[both svbc and svec will vote on this]

	http://www.eda.org/svdb/view.php?id=2681  

	 

	 

	id 42, svdb 2682    __ X ___ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2682 

	 

	 

	id 43 and id 45, 

	svdb 2430    __ X ___ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2430   

	 

	 

	id 44, svdb 2701    __ X ___ YES   _____ No

	[both svbc and svec will vote on this]

	http://www.eda.org/svdb/view.php?id=2701  

	 

	 

	id 46, svdb 2706    ___ X __ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2706 

	 

	id 47, svdb 2713    __ X ___ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2713  

	 

	id 57, svdb 2698    ___ X __ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2698 

	 

	id 65, svdb 2723    ___ X __ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2723 

	 

	id 67, svdb 2358    ___ X __ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2358 

	 

	id 80, svdb 2596    __ X ___ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2596 

	 

	id 102, svdb 2718    __ X ___ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2718 

	 

	id 106, svdb 2710    ___ X __ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2710 

	 

	id 107, svdb 2711    ___ X __ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2711  

	 

	id 181, svdb 2514    ___ X __ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2035 

	 

	id 182, svdb 2514    __ X ___ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2514 

	 

	id 183, svdb 2510    _____ YES   __ X ___ No  It is not clear
what is allowed as a clocking signal and why the text in 6.21 applies to
clocking signals. I think the text should be present or at least a
reference to a particular paragraph of section 6.21 

	http://www.eda.org/svdb/view.php?id=2510 

	 

	id 184, svdb 2473 

	CLOSE 2473,  id 184 requires no further action:

	[ Draft8 says

	  An associative array type or class shall be illegal as a 

	  destination type. So this has already been made illegal.]

	   ___ X __ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2473 

	 

	id 185, svdb 2342    _ X ____ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2342 

	 

	id 186, svdb 2288    ___ X __ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2288 

	 

	id 192, svdb 1256     __ X ___ YES   _____ No

	http://www.eda.org/svdb/view.php?id=1256  

	 

	 

	svdb 2719 for the following  ids

	id  58  ___ X __ YES   _____ No

	id  60  ___ X __ YES   _____ No

	id  61  ___ X __ YES   _____ No

	id 104  ___ X __ YES   _____ No

	id 108  ___ X __ YES   _____ No

	id 112  ___ X __ YES   _____ No

	id 117  ___ X __ YES   _____ No

	id 118  ___ X __ YES   _____ No

	id 119  ___ X __ YES   _____ No

	id 122  ___ X __ YES   _____ No

	id 137  ___ X __ YES   _____ No

	http://www.eda.org/svdb/view.php?id=2719 

	 

	 

	 


	-- 
	This message has been scanned for viruses and 
	dangerous content by MailScanner <http://www.mailscanner.info/>
, and is 
	believed to be clean. 


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.