[sv-bc] Agenda: December 4 SV-BC CC

SV-BC Committee Meeting
Date: Monday, December 4, 2006
Time: 09:00am-11:00am PDT

Toll Free Dial In Number: (888)635-9997
International Access/Caller Paid Dial In Number: (763)315-6815
PARTICIPANT CODE: 53904

Agenda

+ Review IEEE patent policy
  http://standards.ieee.org/board/pat/pat-slideset.ppt 
  
+ Review Minutes of Previous Meeting
  http://www.eda.org/sv-bc/minutes/sv-bc_06_10_23.txt

+ Call for additional agenda items

+ Resolve date of next SV-BC conference call
     Proposed Next Meeting Date: December 18, 2006

+ Review pending action items (see Appendix 1 below)

+ Status report from name resolution task force

+ Tentative P1800 schedule for 2007
  http://www.eda-stds.org/sv-bc/hm/5388.html

+ Straw poll on `begin_define -- `end_define
  http://www.eda-stds.org/sv-bc/hm/5316.html
  http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0001621

+ Issues for voting

  Update $display and other file I/O system tasks for aggregate data
types
  http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0000331

  generate_block_or_null is superfluous
  http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0001673

+ Adjourn
  

Appendix 1: Pending Action Items

Pending
01/09/2006 Shalom add example for issue 1254 describing situation for
rule 3
03/27/2006 Cliff post examples demonstrating the need for 0-1 wildcard 
           to justify further action on SVDB 99

           Other ideas: elsex, defaultx, ifx, alwaysx, initialx,
           Question: what about X expression in index of Vector or
           array expressions (a[i] where i === 'X).  Cliff to pursue
further
           action.

04/10/2006 Steven to create proposal for SVDB 1386
04/10/2006 Steven to create proposal for SVDB 1078
05/22/2006 Gord file issue regarding scoping & forward visibility in
$unit.
06/19/2006 Dave to draw up some guidelines about thread creation from 
           functions for SV-BC to vote/capture consensus and pass along
to 
           other committees.
06/19/2006 Gord raise the issue of support of dynamic data in vcd to
SV-EC.
06/19/2006 Francoise check with SV-CC regariding suitability of data
read API
           to address debugging of "dynamic data" in lieu of vcd
extensions.
07/10/2006 Steve add bugnote to 1043 about specifics for resolution
07/31/2006 Steve add bug note to 1481 with details for a clearer
proposal
08/14/2006 Matt to forward request for timely updates to 1800 standard
to 1800
           committee and offer Dave's name if seeking participants to
enable.
09/11/2006 Dave open new issue to address hierarchical references of
imported
           identifiers.  Copy Stu's bug note from 1323 to new issue.
09/25/2006 Matt add SVDB entry to request capability to packages: 
           import/export & non-exported (local) package declarations.
09/25/2006 Matt send feedback to sv-bc/sv-ac regarding SVDB 1601
10/09/2006 Gord/Dave: draft proposal to resolve SVDB 1484

10/09/2006 Brad: enhance 1554 proposal to prevent circularity of
expressions
           (address use or non-use of hierarchical references).
10/09/2006 Shalom: add an additional mantis to enable parameters with
dynamic
           data types


Appendix 2: Issue Review

 Process:
 Identify subset of issues to focus committee effort  Assign owners for
the issues  Owners bring issues to vote when draft of proposal complete
Rebuttal to issues should come in the form of specific changes to
proposal

 Guidelines for issues:
 - Group would prefer not to address issues that complicate merging of
the 
   LRMs or require edits to both specs.  Group would prefer to address
more
   isolated errata until next PAR is set.
 - Try to clarify intent of some issues even if no formal resolution.
This
   would be useful for keeping implementations consistent.
 - Major Severity will be used to identify issues that if not addressed
will
   lead to visibly different implementations.
 - Group will use severity to quantify impact of change.
   Issues will be addressed in order of severity.
 - Priority will indicate issue's development progress.  Increase in
priority
   indicates increased progress to proposal and vote.  'Immediate'
priority
   indicates issue is ready for a vote.
 - Individuals will indicate ownership of resolution by adding
themselves
   to the 'assigned to' field.  Karen will help anyone who cannot update
an 
   issue.
 - Individual members can increase the severity of an issue but the
group 
   must agree to decrease severity.
 - Status Filed: Assigned, Resolved & Closed are key states. 

 Issue Themes

 Namespaces
 Issues: 30, 1213, 1214, 1220
 Primary Owner: Francoise
 Participants: Gord, Francoise, Mark, cc: Shalom, cc: Karen
 
 I/O Errata/Clarification
 Issues: 672, 1078, 1386: Steven ; 988: Gord  Primary Owner: Steven
 Participants: Steven, Gord, Mark, Francoise
 
 Enumerated Types
 Issues: 916, 917, 1429
 Primary Owner: Matt
 
 Configurations
 Issues: 986 (see bugnote for related items)  Primary Owner: TBD
(proposed as Cliff but he was not present)

 Scheduling
 Issues: 1290, 219
 Primary Owner: TBD (Gord; after first round of issues are addressed)

 Compiler Directives
 Issues: 1052, 1053, 1084, 1119, 1202, 1292, 1333, 1338, 1339, 1341
Primary Owner: Shalom 

 Name Resolution
 Primary Owner: Gord
 Participants: Francoise, Steven, Mark, Shalom.