[sv-bc] Resend: Agenda: January 17, 2011 SV-BC Meeting

SV-BC Meeting
Date: Monday, January 17, 2011
Time: 9:00am-11:00am PST

Toll Free Dial In Number in North America: 1-888-813-5316
Caller Paid Dial In Number: 1-650-584-6338
Meeting ID: 7839818

Agenda

+ Review IEEE patent policy
  http://standards.ieee.org/board/pat/pat-slideset.ppt
 
+ Previous Meeting Minutes
  http://www.eda.org/sv-bc/minutes/sv-bc_10_12_06.txt
  
Interface Discussion
  Consensus to-date includes:
    Support for parameterized interfaces
    No support for run-time compatibility checking
  Prevailing opinion is to not unify classes and interfaces

  A couple of informal meetings were held over the past few weeks.
  Brad posted a summary of the progress on the reflector:

  http://www.eda.org/sv-bc/hm/10769.html

  and follow-on discussion ensued. Plan to re-sync and identify next
  steps.
  
Follow-up on Issue 210
  Still looking for details to justify any language enhancement.

Mantis 2889 [http://www.eda.org/svdb/view.php?id=2889]

Shalom posted an updated proposal to the reflector:
http://www.eda.org/sv-bc/hm/10735.html

Progress/Discussion for Top 10

Looking for proposal sketches or discussion for any of these issues.

   696 - Complete
  2310(1084, 1201) - Participants: Eric, Tom, Shalom, Steven,
                     Wilson Snyder
  3053 - Participants: Francoise, Mark, Alex, Kaiming
  3055 - Participants: Gord, Mark
  2991 - Champion: Tom, Participants: Steven
  1566 - For future discussion
  2114 - Similar to 3053. Have same group look at it.
   210 - Participants: Shalom, Matt
  3056 - Champion: Shalom, Participants: Steven, Francoise

Action Items

Complete

Outstanding
  05/10/10 Matt create Master Issue for WG-approved SV-BC Top-25
  07/19/10 Matt follow-up about voting rules for technical sub-committee.
           Is there a limit on the number of reps from 1 entity?
  07/19/10 Dave to post request to reflectors for clarification of 2108
  07/19/10 Jonathan post some items for discussion related to 2114 to reflector.
  08/02/10 Brad give SV-BC feedback on Mantis 2992 to Mehdi
  08/02/10 Eric start reflector thread on Mantis 2310
  08/02/10 Gord meet F2F with Mark when in Bay Area
  08/16/10 Matt to rethink 210 in terms of configuration and alias.
  08/16/20 All send Shalom feedback about prioritizing the issues raised
           in port declaration issue summary:
           http://www.eda.org/sv-bc/hm/10498.html
  09/13/10 Jonathan show simple examples of virtual interfaces, sub-interfaces
           and base classes in modules to demonstrate different methods for
           connecting design and testbenches.
             09/27/10 Tom post updated proposal to 696.
  09/27/10 Review Shalom's list of interface issues and suggest issues to
           tackle now.

  05/10/10 Matt create Master Issue for WG-approved SV-BC Top-25
  07/19/10 Matt follow-up about voting rules for technical sub-committee.
           Is there a limit on the number of reps from 1 entity?
  07/19/10 Dave to post request to reflectors for clarification of 2108
  07/19/10 Jonathan post some items for discussion related to 2114 to reflector.
  08/02/10 Brad give SV-BC feedback on Mantis 2992 to Mehdi
  08/02/10 Eric start reflector thread on Mantis 2310
  08/02/10 Gord meet F2F with Mark when in Bay Area
  08/16/10 Matt to rethink 210 in terms of configuration and alias.
  08/16/20 All send Shalom feedback about prioritizing the issues raised
           in port declaration issue summary:
           http://www.eda.org/sv-bc/hm/10498.html
  09/13/10 Jonathan show simple examples of virtual interfaces, sub-interfaces
           and base classes in modules to demonstrate different methods for
           connecting design and testbenches.
             09/27/10 Tom post updated proposal to 696.
  09/27/10 Review Shalom's list of interface issues and suggest issues to
           tackle now.
  11/22/10 Brad to file Mantis item for upward passing of interfaces.
  12/06/10 Matt open new Mantis item covering determination of port kind
           for .named_port connection (23.2.2.3).

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