TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Proportional Font
Show HTML Part by Default
Condense Mail Headers

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

Print Reply
Content-Transfer-Encoding:
7bit
Sender:
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Subject:
From:
Michael Feldman <[log in to unmask]>
Date:
Fri, 14 Jul 2000 21:03:44 -0400
Content-Type:
text/plain; charset=us-ascii
MIME-Version:
1.0
Reply-To:
Michael Feldman <[log in to unmask]>
Parts/Attachments:
text/plain (32 lines)
Rick et al,

My Prentice-Hall Dictionary of Computing says (1998, p.627):

"STANDARDS.

Clearly defined and agreed-upon conventions for programming
intefaces. Standards may be (bullets mine)

- proprietary (used only within the environment provided by a single
  computer vendor),

- public (widely used across a variety of vendor equipment), or

- formal (developed by a standards organization such as ANSI or ISO)."

This is not the greatest definition, but it's the best I can find
just now in the literature, and it'll do.

Obviously Ada is both formal and public, and Visual Basic is
proprietary (at least if we take 'single computer vendor' to mean
'the Wintel family').

Rick, let's avoid confusion. I'll agree to use the terms "formal standard"
or "public standard" if you'll agree -- at least in Ada circles -- to
preface your references to Microsoft standards with "proprietary". That
qualification will resolve the overloading of  the term "standard",
and will make clear that Microsoft fans understand fully that
Microsoft's use of the term is very different from (say) Ada's.

Mike Feldman

ATOM RSS1 RSS2