Re: DASC Scope


Subject: Re: DASC Scope
From: Shalom Bresticker (Shalom.Bresticker@motorola.com)
Date: Thu Nov 13 2003 - 02:44:26 PST


Alex,

I believe that is exactly one of the benefits of IEEE standardization.
IEEE should not be, and in my experience is not, just a rubber stamp.
IEEE is a body which carefully examines what it is standardizing.

IEEE 1364, for example, did not just rubber stamp the Cadence or OVL
LRMs for Verilog. They were carefully examined, feature by feature,
and in some cases changes were made.

Shalom

Alex Zamfirescu wrote:

> Michael:
>
> All you write make good sense under two conditions, and those are
> good intention, and technical soundness of the company of coalition-produced-
> spec brought to the IEEE attention.
>
> Both conditions are hard to check.
>
> What could go wrong if conditions are not met:
>
> The IEEE group might think it came up with a standard when
> in fact it just put a stamp on the name of either an incomplete (no good
> intention)
> or incorrect (no technical soundness) specification.
>
> In other words an implementation has to be feasible using the
> standard alone and that implementation has to be able to handle
> code the same way as any other implementation based on the
> standard.
>
> If you wait too much to get support from tools and industry,
> there is always the problem that some vendors will try to
> take advantage by not providing all the needed "tricks" to the
> standard group, or that one dominant vendor will hold the golden
> implementation that is hardly reproducible directly from
> the standard.
>
> Wearing my philosopher hat again, I can even state that it is best
> to have a standard that has hidden "holes" because that will
> keep a "herd" of experts explaining how to code to major
> corporations, and it is probably that group that will be ready
> to step up and devise even more new standard "soufflé."
> There will also be a holder of the golden implementation
> who will be there to promote, support etc.
> Talking from the same skeptic perspective, a perfect,
> easy to learn, implement and use standard
> will apparently never provide for enough maintainers, and will be soon
> abandoned for use ("like Latin in some Churches") only when
> critical information has to be conveyed.
>
> So the only question is: "How hot is the soufflé?"
>
> Any comments?
>
> Enjoy the day,
>
> Alex Zamfirescu
> CTO ASC

--
Shalom Bresticker                           Shalom.Bresticker@motorola.com
Design & Reuse Methodology                             Tel: +972 9 9522268
Motorola Semiconductor Israel, Ltd.                    Fax: +972 9 9522890
POB 2208, Herzlia 46120, ISRAEL                       Cell: +972 50 441478



This archive was generated by hypermail 2b28 : Thu Nov 13 2003 - 02:46:01 PST