Re: needed for IBIS V3.1

Text item:

Steve,

Regarding the issue of "basic" and "luxury" items in IBIS, a very simple way to
determine what is basic is to look at the criteria whether the item is required
or not. You will find that most items are optional.

Arpad
===============================================================================

Mini-topic for the upcoming IBIS Summit meeting at DAC:

I believe it's important for V3.1 of the specification to include several
simple, clear example files, e.g., a simple IC using a minimum of
constructs, a more-complex IC using a few "extra" features like waveform
tables, a network-packaged passive device, and a bus switch.

Why? Because lacking these, the specification is so intimidating to
newcomers that many are being scared off, to the detriment of the entire
standard. Remember V1.x? It was a relatively quick, easily comprehended
"read." What we have now is richer and more powerful, but also exponentially
more confusing. Some of us on the committee are probably "velocitized" to
the point where we're not aware of the problem's gravity.

From recent conversations with IBIS "newbies" (and this includes
semiconductor-vendor personnel, unfortunately), I think it works like this:

1. Reads IBIS spec (or part of it).
2. Wants to kill self.
3. Hears about Spice-to-IBIS, and thinks "that's my only hope!"
4. Then the real trouble begins...

Personally, I'd like to see the opening page of the spec state clearly that
about 85% of modeling applications can use about 25% of the specification's
constructs, and point straight to the example models. Also good would be a
designation of some kind delineating between "basic" and "luxury" constructs.

I'd be interested in hearing opinions about this at the Summit...

Regards,

Steve Kaufer,
HyperLynx

Text item: External Message Header

The following mail header is for administrative use
and may be ignored unless there are problems.

***IF THERE ARE PROBLEMS SAVE THESE HEADERS***.

Subject: needed for IBIS V3.1
From: Steve Kaufer <stevek@hyperlynx.com>
To: ibis@vhdl.org
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0
X-Mailer: Windows Eudora Pro Version 2.1.2
X-Sender: stevek@mail.nwlink.com
Message-Id: <199706060141.SAA23593@montana.nwlink.com>
Date: Thu, 5 Jun 1997 18:41:07 -0700 (PDT)
Received: from steve.nwlink.com ([209.20.148.68])
     by montana.nwlink.com (8.8.5/8.8.5) with SMTP id SAA23593
     for <ibis@vhdl.org>; Thu, 5 Jun 1997 18:41:07 -0700 (PDT)
Received: from montana.nwlink.com (root@montana.nwlink.com [199.242.23.13]) by s
erver.vhdl.org (8.8.5/8.8.3) with ESMTP id SAA05227 for <ibis@vhdl.org>; Thu, 5
Jun 1997 18:41:58 -0700 (PDT)
Received: from server.vhdl.org (server.vhdl.org [198.31.14.3])
          by mailbag.jf.intel.com (8.8.5/8.8.4) with ESMTP
       id SAA27462; Thu, 5 Jun 1997 18:54:11 -0700 (PDT)
Received: from mailbag.jf.intel.com by relay.hf.intel.com with smtp
     (Smail3.1.28.1 #2) id m0wZoDG-000qDQC; Thu, 5 Jun 97 18:53 PDT
 
Received on Fri Jun 6 07:58:30 1997