TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Classic View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Date: Mon, 17 Jul 2000 17:41:35 -0600
Reply-To: Craig Spannring <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset=us-ascii
From: Craig Spannring <[log in to unmask]>
Parts/Attachments: text/plain (40 lines)
The Prentice-Hall Dictionary of Computing as a couple of errors in
it's definition of what a standard is.  It should read-


Clearly defined and agreed-upon conventions for programming
interfaces. Standards may be-

- proprietary  (Designed to benefit a single vendor, usually the
                dominant player in the field, for the sole benefit
                of that vendor)

- industry     (Designed to benefit multiple vendors
                in a given field, usually aimed at reducing
                the dominance of the lead player in the field)

- public       (Designed to benefit the public.)

- formal       (developed by a standards organization such as ANSI or
                ISO with the primary goal of benefiting the standards

Now that we have a definition of the four types of standards, could we
put this thread to rest?

For the humor and sarcasm impaired, add a :-) and a :-( to this post.

 Life is short.                  | Craig Spannring
      Bike hard, ski fast.       | [log in to unmask]
  When all you've got is Perl, everything feels like a smashed thumb