RE: [sv-cc] SV-CC Data Read API meeting agenda for 02/06/2008

Hi Charles,

There were three participants in today's call on Data Read API, Jim,
Bassam and myself. Jim reported that you were not feeling well and not
able to join.

After waiting few minutes, we decided to cancel today's call.

Thanks,
/gjk

-----Original Message-----
From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On Behalf Of
Charlie Dawson
Sent: Tuesday, February 05, 2008 6:07 PM
To: sv-cc@eda.org
Subject: [sv-cc] SV-CC Data Read API meeting agenda for 02/06/2008

The first SV-CC Data Read API meeting agenda for 02/06/2008.

The call-in information for this meeting is as follows:

   U.S.               866-807-0627
   International      203-955-5179
   Passcode           399143

Meeting will start at 11:30am EST (4:30pm GMT), and last for 1.5 hours.

AGENDA

1.  Review Patent information

   Go to:
     http://standards.ieee.org/board/pat/pat-slideset.ppt

2.  Consent agenda Items

   - Declare Item 0587 a duplicate of Item 572
   - Declare Item 0588 a duplicate of Item 572
   - Declare Item 0589 a duplicate of Item 572
   - Close Item 0559 as Not a Bug - clarification added as NOTE
   - Close Item 0567 as Not a Bug - clarification added as NOTE
   - Close Item 0568 as Not a Bug - clarification added as NOTE
   - Close Item 0579 as Not a Bug - clarification added as NOTE
   - Close Item 0581 as Not a Bug - clarification added as NOTE
   - Close Item 0592 as Not a Bug - clarification added as NOTE
   - Close Item 2144 as Not a Bug - clarification added as NOTE
   - Close Item 2147 as Not a Bug - clarification added as NOTE


3.  Review Items with proposals:

   - Item 0555 31.1 Introduction not needed in context of the larger
document
   - Item 0556 31.2 Beginning of this section not needed in larger
context of spec
   - Item 0557 31.3.1 specific references to objects should be removed
   - Item 0558 31.3.3 rename section to "Access availability"
   - Item 0560 31.4.1 & 31.4.2.1 Overloading vpi_handle() is a bad idea
   - Item 0561 31.4.2 vpi_free_object() should be explicitly referenced
here
   - Item 0562 31.5 needless restriction on traverse object creation -
poor terminology
   - Item 0563 31.5 diagram in figure 31-18 needs to be redrawn
   - Item 0565 31.6 remove first paragraph of this section
   - Item 0570 31.8.1 Need prototype for vpi_load_extension()
   - Item 0571 31.8.1 unnecessary complication added for vpi_close()
   - Item 0572 31.8 make use of the term 'user'
   - Item 0580 31.8.4 section is not necessary and colloquial
   - Item 0583 31.8.4.2 terminology first defined in a footnote?
   - Item 0584 31.8.4.2 implies that vpi_goto() creates new handle
   - Item 0593 31.12 Routines should be in table format
   - Item 2146 Data read API description references wrong header file
   - Item 2148 Unclear statement about error handling after calling
vpi_unload()

4.  Review remaining Items:

   - Item 0573 -- No proposal, assign back to filer to list the issue
and suggest resolution
   - Item 0590 -- *postpone*

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


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