RE: [sv-ac] Re: [SV-AC] IMPLIES / OR / AND / VACUITY TABLE

Hi Ben:

I have attached a prettied up version of the notes I mentioned
yesterday. It should be noted that I have been thinking about this from
a theoretical perspective. One thing that should likely be considered
is which cases are of practical importance. I started thinking about
that a bit, but I haven't come to any strong conclusions. I will
continue thinking about it when I have some more time.

You sent an e-mail regarding the definition of vacuity earlier today. I
should likely give my perspective which may give some clue as to the
origin of the statements in the attached document. Property
success/failure (s/f) and vacuity/nonvacuity (v/nv) are separate
concepts. Each property will have a s/f and a v/nv result. The v/nv
result gives additional information about the "quality" of the s/f
result. The v/nv result should only be nv when all conditions required
for the s/f result are determined by nv results.

Oh, I haven't carefully checked these notes for correctness. Please let
me know if you find any errors.

Thanks,

Scott

From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of ben
cohen
Sent: Tuesday, October 05, 2010 12:18 PM
To: Korchemny, Dmitry; sv-ac@eda.org
Subject: [sv-ac] Re: [SV-AC] IMPLIES / OR / AND / VACUITY TABLE

On Tue, Oct 5, 2010 at 9:45 AM, ben cohen <hdlcohen@gmail.com> wrote:

See attached table.

It needs work, but it is something that I would like to have clarified.

Ben

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