RE: [sv-cc] Read API

Hi Jim,
 
Thanks for the input. Some comments below but basically the spreadsheet
is meant as a starting point "guidance" -- yes all proposals need
updates, and yes all "Editor" entries mean a proposal on guidance (may
be more green than usual :)) is needed. 
 
Thx.
-Bassam.
 

________________________________

From: Jim Vellenga [mailto:vellenga@cadence.com] 
Sent: Wednesday, October 24, 2007 6:39 AM
To: Bassam Tabbara; sv-cc@eda-stds.org; SV-CC
Subject: RE: [sv-cc] Read API


Bassam and Ghassan, thank you for putting the list together.
 
A few thoughts:
 
-- I'm sure the champions aren't going to accept a resolution
of these issues unless the section numbers are updated.  It
would be helpful for the rest of us too.  Could you guys
do us the favor of updating the section numbers in the titles
and descriptions?
[Bassam Tabbara] Yes indeed proposals should be draft 4 -- I was not
able to edit the items, let's talk in meeting on how to accomplish (may
be update spreadsheet list and Charles can edit the items).
 
-- Although you list 572 as having a proposal posted (and
that is, strictly speaking, correct), the proposal needs
to be updated for Draft 4 and the section numbers and
bullet letters (rather than numbers) that Draft 4 uses.
[Bassam Tabbara] yes indeed. 
 
-- If we do make 588 a duplicate of 572, we will have to
update the proposal for 572 to include the additional section.
[Bassam Tabbara] yep. 
 
-- I am reluctant to move the new routine descriptions into
Clause 37, as you suggest in your proposed proposal for Item
593.  As far as I can tell, this is really a separate layer
of API built on top of the rest of VPI, and it would seem
clearer to keep its description separate. 
[Bassam Tabbara] Let's discuss this one on what's best. 
 
-- A couple of places your proposed proposal says "Editor
should ..." or "Ask editor to ...".  If you're saying we
don't need a concrete and detailed written proposal for
these, do you really think that will get past the Champions?
[Bassam Tabbara] I meant we have a proposal with more green. 
 
-- I don't see how 589 is really a duplicate of 572.  It seems
like an unrelated issue.
[Bassam Tabbara] I think item header is confusing -- user note answers
the question and then states it is similar to 572, Again SS starting
point, we'll target one by one ...
 
Regards,
Jim V.
 

---------------------------------------------------------
James H. Vellenga                            978-262-6381
Software Architect                              (FAX) 978-262-6636
Cadence Design Systems, Inc.         vellenga@cadence.com
270 Billerica Rd
Chelmsford, MA 01824-4179
"We all work with partial information."
---------------------------------------------------------- 

 


________________________________

	From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On Behalf
Of Bassam Tabbara
	Sent: Tuesday, October 23, 2007 10:56 PM
	To: sv-cc@eda-stds.org
	Subject: [sv-cc] Read API
	
	
	Hi All,
	 
	> Bassam and Ghassan to prioritize list of issues with Read API.
	 
	Attached please find the list with our notes. 
	 
	Thx.
	-Bassam.
	P.S. Attached can be viewed in IE.

	-- 
	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.