RE: [sv-bc] Next SV-BC Meeting: Monday, Mar 13th

Regarding Mantis 949, see also 
http://www.eda.org/sv-bc/hm/3845.html.

Shalom

> -----Original Message-----
> From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On
> Behalf Of Maidment, Matthew R
> Sent: Monday, March 06, 2006 9:22 AM
> To: sv-bc@eda.org
> Subject: [sv-bc] Next SV-BC Meeting: Monday, Mar 13th
> 
> SV-BC Errata Committee Meeting
> Date: Monday, March 13, 2006
> Time: 09:00am-11:00am PST
> 
> 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_02_06.txt
> 
> + E-mail ballot review
> 
> An e-mail ballot was sent January 30th:
> 
> http://www.eda.org/sv-bc/hm/3802.html
> 
> Review the results including any issues receiving 'no' votes
> 
> 
> Pass:
> 871,881,908,912,932,941,942,944,945,952,961,984,1092,1159,1253,
> 1260,1261
> ,1298
> 
> Fail:
> http://www.eda.org/svdb/bug_view_page.php?bug_id=0000882
> Cliff: http://www.eda.org/sv-bc/hm/3853.html
> 
> http://www.eda.org/svdb/bug_view_page.php?bug_id=0000911
> Cliff: http://www.eda.org/sv-bc/hm/3853.html
> Stu: http://www.eda.org/sv-bc/hm/3871.html  (supports Cliff's
> proposal)
> 
> http://www.eda.org/svdb/bug_view_page.php?bug_id=0000919
> Cliff: http://www.eda.org/sv-bc/hm/3853.html
> Francoise: http://www.eda.org/sv-bc/hm/3826.html
> Shalom: http://www.eda.org/sv-bc/hm/3828.html
> 
> http://www.eda.org/svdb/bug_view_page.php?bug_id=0000946
> Cliff: http://www.eda.org/sv-bc/hm/3853.html
> 
> http://www.eda.org/svdb/bug_view_page.php?bug_id=0000949
> Cliff: http://www.eda.org/sv-bc/hm/3853.html
> Mark: http://www.eda.org/sv-bc/hm/3834.html
> Francoise: http://www.eda.org/sv-bc/hm/3826.html
> 
> http://www.eda.org/svdb/bug_view_page.php?bug_id=0000962
> Cliff: http://www.eda.org/sv-bc/hm/3853.html
> Shalom: http://www.eda.org/sv-bc/hm/3858.html
> 
> http://www.eda.org/svdb/bug_view_page.php?bug_id=0001138
> Shalom: http://www.eda.org/sv-bc/hm/3812.html
> 
> http://www.eda.org/svdb/bug_view_page.php?bug_id=0001255
> Shalom: http://www.eda.org/sv-bc/hm/3812.html
> Cliff: http://www.eda.org/sv-bc/hm/3853.html
> Steven: http://www.eda.org/sv-bc/hm/3863.html
> 
> http://www.eda.org/svdb/bug_view_page.php?bug_id=0001297
> Stu: http://www.eda.org/sv-bc/hm/3871.html
> Shalom: http://www.eda.org/sv-bc/hm/3872.html
> 
> 
> Brad has provided analysis here:
>   http://www.eda.org/sv-bc/hm/4069.html
> 
> + Review Mantis #966
> 
> The SV-AC has requested that the SV-BC provide feedback on the
> proposal for issue 966:
> 
> http://www.eda.org/sv-ac/hm/2004.html
> 
> http://www.eda.org/svdb/bug_view_page.php?bug_id=0000966
> 
> Shalom has provided some initial feedback here:
> http://www.eda.org/sv-bc/hm/4142.html
> 
> + Top-N Issues Appropriate for SV-BC
> 
>  Process:
>  Identify -=N=- 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.
> 
>  Please identify issues that meet the above guidelines and send
> them to
> the  reflector so we can continue to make progress.
> 
> + Proposed Next Meeting Date: March 13th
> 
> Action Items
> 
> Completed
> 02/06/2006 Matt close on committee agreed feedback for next PAR
> by Feb
> 17
> 
> Pending
> 
> 12/05/2005 Steven Ask Jay if issue 1127 is resolved in P1800?
> 01/09/2006 Shalom add example for issue 1254 describing
> situation for
> rule 3
> 01/09/2006 Matt assemble issue list for future work
> 01/09/2006 Matt find owners for future work issues
>