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? -- 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. -- If we do make 588 a duplicate of 572, we will have to update the proposal for 572 to include the additional section. -- 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. -- 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? -- I don't see how 589 is really a duplicate of 572. It seems like an unrelated issue. 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.Received on Wed Oct 24 06:39:58 2007
This archive was generated by hypermail 2.1.8 : Wed Oct 24 2007 - 06:40:13 PDT