RE: [sv-cc] mantis 2226 action completed

Thanks, Chuck.  I agree.  I especially like the rewording
suggested in your point 3.
 
Regards,
Jim Vellenga

---------------------------------------------------------
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 Chuck Berking
	Sent: Wednesday, October 01, 2008 10:05 AM
	To: Shields, John
	Cc: sv-cc@eda.org
	Subject: RE: [sv-cc] mantis 2226 action completed
	
	
	John-
	I second Jim's assessment- nice work.  Here are my correction
inputs to Parts 1 -> 3 (minor  & word-smithing only):
	 
	In "38.36.1 Simulation event callbacks" :
	 
	    1) Change in first sentence starts with:   "such as values
changes"    "values" should be "value" (singular).
	 
	    2) Paragraph describing cb_data_p->obj has a sentence
containing:
	             ... "assigned a handle to class typespec object."
	        Please insert "a" so it reads:
	             ... "assigned a handle to a class typespec object."
	 
	    3) In paragraph beginning "For a cbReclainObj", the final
sentence:
	            "Navigation using this handle as a reference or
registration of callbacks associated with this handle is undefined."
	 
	        ... should be worded better for clarity. I would
suggest:
	            "Using this handle as a reference for purposes of
navigation or registering callbacks is undefined."
	 
	Regards,
	Chuck


________________________________

		From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org]
On Behalf Of Shields, John
		Sent: Monday, September 29, 2008 2:07 PM
		To: sv-cc@eda.org
		Cc: sv-champions@eda.org; Neil.Korpusik@sun.com; Karen
Pieper; Bresticker, Shalom; stuart@sutherland-hdl.com
		Subject: [sv-cc] mantis 2226 action completed
		
		

		Hi Everyone,

		 

		I have completed my action on 2226.  I changed it to
review so that I could revise files.  I've removed all the draft6
revisions and added the changes baselined to draft7.   All the champion
and reviewer feedback has been incorporated. The Champions and the
Working Group have entrusted SV-CC to to this composition work and you
have entrusted that all to me.  In a perfect world, I would ask Charlie
to close 2226 and he in turn would ask Neil to remark it approved and
turn it over to Stu.  I think it would be helpful to have a quick review
for composition errors and to allow the friendly amendments to be seen
in context.  I leave the next action to Charlie to ask for review or
close the item.

		 

		Because of the number of files, I have packaged them in
3 zip files.  fm-clauses-mantis2226.zip contain full framemaker files
for each clause (except annex C).  This is what Stu asked for to
minimize his effort.  My notes on that are:

		 

		1) Some diagrams I could show deletions, others the real
estate for the deletion was reused and one sees only the addition.

		2) The annexes need normal editor work.  I did not have
Annex C from Stu at all, but the edit is trivial.  The other 2 annexes
require some minor numbering.

		 

		 

		fm-changes-only-mantis2226.zip contains framemaker files
representing only what has changed in a minimal fashion suitable for
efficient review. pdf-changes-only-mantis2226.zip contains pdfs of
those.  The framemaker change only versions were necessary(to me) for
composition and I used them to create the complete clauses.  Normally,
Stu would start with them.  It is his option to look at them and
validate that the edits to the full clauses were made accurately.  I
used paragraph tags properly in the full clauses, but the change-only
requires tag mods to insure that the numbering matched the document.

		
		Regards, John


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