🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.std.unix
Article #823

Re: definitions

#823
From: Ralph Barker
Date: Sat, 27 Apr 1991 15:06
47 lines
2865 bytes
Submitted-by: ralph@svnet.UUCP (Ralph Barker)

In article <129555@uunet.UU.NET>, cazier@mbunix.mitre.org (Cazier) writes:
> Submitted-by: cazier@mbunix.mitre.org (Cazier)
> 
> What national or international groups have published definitions for the
> following:
> 
> 	standards, specifications, standards categories, profiles
> 	functional areas, functional area profiles, layers, framework
> 
> or does anyone have comments on the items listed above regarding definitions?
> 
Depending on the nature of the work for which the definitions are needded, the
level of care in use of the terms may vary.  For example, an article for the 
trade press might use the terms rather loosely, while work on a draft of a 
proposed standard or "official" specification would require greater
care.  

Within the standards work going on within IEEE, ANSI, ISO and other
standards bodies, a considerable effort goes into coordinating the
definitions of terms.  The direction of the coordination is usually
"up", i.e. toward coordination with ISO definitions.  Chairs of
working groups are encouraged (pronounced "required by duty or
professionalism") to coordinate with each other as work progresses, so
that variations in the use of terms can be avoided.  

In some cases, as with the term "profile", slight twists may be
unavoidable.  For example, within the work going on within the
P1003.0, "profile" is used to refer to a collection of standards and
functional standards used to specify the requirements for a particular
application environment.  At the international level, however,
"national profiles" commonly refers to a set of locale definition
specifications for i18n purposes.  

Considering the amount of standards work "in the pipeline", it is
advisable to check both the published dictionaries of standards bodies
and pending work to avoid conflicts.  

-- 
Ralph Barker:                SVNet, 640 So Winchester Blvd, San Jose,CA 95128
uucp: ...{pyramid, sun, uunet}!amdahl!aleph!svnet!ralph        
			uunet!usrgrp!svnet!ralph        
         or,     attmail!ralmar!ralph                   Voice: (408) 248-8649


Volume-Number: Volume 23, Number 48
Technical Details
Message-ID: <130888@uunet.UU.NET>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!uunet!uunet.UU.NET!sef
References: <129555@uunet.UU.NET> <129555@uunet.UU.NET>,

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!uunet!uunet.UU.NET!sef
From: ralph@svnet.UUCP (Ralph Barker)
Newsgroups: comp.std.unix
Subject: Re: definitions
Summary: Coordination with proposed Stds
Message-ID: <130888@uunet.UU.NET>
Date: 27 Apr 91 15:06:02 GMT
Article-I.D.: uunet.130888
References: <129555@uunet.UU.NET> <129555@uunet.UU.NET>,
Sender: usenet@uunet.UU.NET
Organization: SVNet, San Jose, CA 95128
Lines: 47
Approved: sef@uunet.uu.net (Moderator, Sean Eric Fagan - comp.std.unix)
Nntp-Posting-Host: uunet.uu.net
X-Submissions: std-unix@uunet.uu.net
Originator: sef@uunet.UU.NET