ISO/IEC TR 14252:1996
(Main)Information technology — Guide to the POSIX Open System Environment (OSE)
Information technology — Guide to the POSIX Open System Environment (OSE)
Describes POSIX Open System Environment (POSIX OSE). It is intended to be used by anyone interested in using standards to construct an information processing system, including consumers, system integrators, application developers, system providers, and procurement agencies.
Technologies de l'information — Guide pour l'environnement de système ouvert (OSE) POSIX
General Information
Relations
Standards Content (Sample)
ISO/IEC
TECHNICAL
TR 14252
REPORT
ANSI/IEEE
Std 1003.0
First edition
1996-I 2-l 5
Information technology - Guide to the
POSIXQ Open System Environment (OSE)
Guide pour I’environnement de syst&me
Technologies de /‘information -
ouvert (OSE) POSlX@
Reference number
&O/I EC TR 14252: 1996(E)
ANSI/IEEE
Std 1003.0-I 995 edition
---------------------- Page: 1 ----------------------
ISBN 1-55937-692-9
Copyright 0 1996 by
The Institute of Electrical and Electronics Engineers, Inc.
345 East 47th Street, New York, NY 10017, USA
No part of this publication may be reproduced in any form,
in an electronic retrieval system or otherwise,
without the prior written permission of the publisher.
---------------------- Page: 2 ----------------------
ISO/IEC TR 14252:1996(E)
ANSI/IEEE Std 1003.0-1995
Information technology-
Guide to the POSIXB
Open System Environment (OSE)
Sponsor
Portable Applications Standards Committee
of the
IEEE Computer Society
Approved May 2,1995
IEEE Standards Board
Approved December 19, 1995
American National Standards Institute
Abstract: This guide presents an overview of open system concepts and their appli-
cations. Information is provided to persons evaluating systems based on the
existence of, and interrelationships among, application software standards, with the
objective of enabling application portability and system interoperability. A frame-
work is presented that identifies key information system interfaces involved in
application portability and system interoperability and describes the services
offered across these interfaces. Standards or standards activities associated with
the services are identified where they exist or are in progress. Gaps are identified
where POSIXB Open System Environment services are not currently being
addressed by formal standards. Finally, the concept of a profile is discussed with
examples from several application domains.
Keywords: application portability, application interoperability, open system
environments, profiles, POSIXB
Adopted as an International Standard by the
International Organization for Standardization
and by the
International Electrotechnical Commission
American National Standard
Published by
t
The Institute of Electrical and Electronics Engineers, Inc.
Y
0
---------------------- Page: 3 ----------------------
ISO/IEC TR 14252: 1996(E)
ANSI/IEEE Std 1003.0-1995
Foreword
IS0 (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form the specialized system for worldwide standardization.
IEC participate in the development of
National bodies that are members of IS0 or
International Standards through technical committees established by the respective
organization to deal with particular fields of technical activity. IS0 and IEC technical
committees collaborate in fields of mutual interest. Other international organizations,
governmental and non-governmental, in liaison with IS0 and IEC, also take part in the
work.
In the field of information technology, IS0 and IEC have established a joint technical
committee, ISO/IEC JTC 1.
The main task of technical committees is to prepare International Standards, but in
exceptional circumstances a technical committee may propose the publication of a
Technical Report of one of the following types:
- type 1, when the required support cannot be obtained for the publication of an
International Standard, despite repeated efforts;
- type 2, when the subject is still under technical
development or where for any other
reason there is the future but not immediate
possibility of an agreement on an
International Standard;
- type 3, when a technical committee has collected data of a different kind from that
which is normally published as an International Standard (“state of the art”, for
example).
Technical Reports of types 1 and 2 are subject to review within three years of publication,
to decide whether they can be transformed into International Standards. Technical Reports
of type 3 do not necessarily have to be reviewed until the data they provide are considered
to be no longer valid or useful.
ISO/IEC TR 14252, which is a Technical Report of type 3, was prepared by Technical
Committee ISO/IEC JTC 1, InfoWn technology.
International Organization for Standardization/International Electrotechnical Commission
Case postale 56 l CH-1211 Gen&ve 20 l Switzerland
---------------------- Page: 4 ----------------------
IEEE Standards documents are developed within the IEEE Societies and the Standards Coor-
dinating Committees of the IEEE Standards Board. Members of the committees serve voluntar-
ily and without compensation. They are not necessarily members of the Institute. The standards
developed within IEEE represent a consensus of the broad expertise on the subject within the
Institute as well as those activities outside of IEEE that have expressed an interest in partici-
pating in the development of the standard.
Use of an IEEE Standard is wholly voluntary. The existence of an IEEE Standard does not
imply that there are no other ways to produce, test, measure, purchase, market, or provide
other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint
expressed at the time a standard is approved and issued is subject to change brought about
through developments in the state of the art and comments received from users of the standard.
Every IEEE Standard is subjected to review at least every five years for revision or reaffirma-
tion. When a document is more than five years old and has not been reaffirmed, it is reasonable
to conclude that its contents, although still of some value, do not wholly reflect the present state
of the art. Users are cautioned to check to determine that they have the latest edition of any
IEEE Standard.
Comments for revision of IEEE Standards are welcome from any interested party, regardless of
membership affiliation with IEEE. Suggestions for changes in documents should be in the form
of a proposed change of text, together with appropriate supporting comments.
Interpretations: Occasionally questions may arise regarding the meaning of portions of stan-
dards as they relate to specific applications. When the need for interpretations is brought to the
attention of IEEE, the Institute will initiate action to prepare appropriate responses. Since
IEEE Standards represent a consensus of all concerned interests, it is important to ensure that
any interpretation has also received the concurrence of a balance of interests. For this reason,
IEEE and the members of its societies and Standards Coordinating Committees are not able to
provide an instant response to interpretation requests except in those cases where the matter
has previously received formal consideration.
Comments on standards and requests for interpretations should be addressed to:
Secretary, IEEE Standards Board
445 Hoes Lane
PO. Box 1331
Piscataway, NJ 08855-1331
USA
Note: Attention is called to the possibility that implementation of this standard may
require use of subject matter covered by patent rights. By publication of this standard,
no position is taken with respect to the existence or validity of any patent rights in
connection therewith. The IEEE shall not be responsible for identifying all patents
for which a license may be required by an IEEE standard or for conducting inquiries
into the legal validity or scope of those patents that are brought to its attention.
Authorization to photocopy portions of any individual standard for internal or personal use is
granted by the Institute of Electrical and Electronics Engineers, Inc., provided that the appro-
priate fee is paid to Copyright Clearance Center. To arrange for payment of licensing fee, please
contact Copyright Clearance Center, Customer Service, 222 Rosewood Drive, Danvers, MA
01923 USA; (508) 750-8400. Permission to photocopy portions of any individual standard for
educational classroom use can also be obtained through the Copyright Clearance Center.
---------------------- Page: 5 ----------------------
Contents
PAGE
. 4 . . . l 4 4 4 V
4 4 4 . 4 4 4
Introduction . . . . . .
l . 4 . 4 4 4 l 4 1
. 4 4 . 4
Section 1: General . . . .
4 4 4 . 4 4 4 . . l 1
4 4 4 4
1.1 Scope
1
4 4 4 4 4 . l 4 4 4 4 4
l 4
1.2 Normative Reference’s
l 4 4 4 4 4 4 4 4 . 4 . 10
. 4
1.3 Conformance . . .
4 . 4 4 l . 4 4 l 4 . 11
4 4 e
1.4 Test Methods . . .
4 4 . 4 . 4 4 4 . 4 4 13
4 4 4
Section 2: Terminology . .
4 4 4 4 . l l 4 4 . 4 13
4 4 4
2.1 Conventions . . .
l 4 4 4 l l 4 4 4 4 4 14
4 . .
2.2 Definitions . . . .
14
. 0 . . . 4 . 4 4 4 4
4 4 .
2.2.1 Terminology .
4 4 4 4 4 4 . 4 . 15
l . . . 4
2.2.2 General Terms
4 4 4 4 4 4 4 4 20
. 4 4 4 4 4
2.2.3 Abbreviations
4 4 . 4 . 23
4 . .
Section 3: POSIX Open System Environment (OSE)
4 . 4 4 . . . . 24
- General Objectives .
3.1 POSIX OSE
. . 4 . 4 4 . l 27
......
3.2 POSIX OSE Reference Model
4 4 . 4 4 l 4 . 36
........
3.3 POSIXOSE Services
. 4 4 4 . 4 4 l 37
........
3.4 POSIXOSE Standards
0 . l . . l . 4 39
..........
3.5 POSIX Profiles
. 4 . 4 4 . . . 40
..............
3.6 PIIs
l 4 4 4 4 4 4 4 43
........
Section 4: POSIXOSE Services
4 4 4 4 4 45
......... 4 4 4
4.1 Language Services
4 4 4 4 4 54
........ . 4 4
4.2 Core System Services
. 4 . 4 4 . 67
....... 4 4
4.3 Communication Services
. . . . l 4 4 4 83
.........
4.4 Database Services
4 . 4 4 4 4 . 4 94
......
4.5 Data Interchange Services
. 4 4 . 4 4 . 4 101
....
4.6 Transaction Processing Services
4 4 4 . 4 110
4 . . l
User Command Interface Services
4.7
4 l . l 118
. l 4 .
4.8 Character-Based User Interface Services. .
. l 4 4 124
...... 4 4 . 4
4.9 Windowing System Services
4 . 4 . 140
......... 4 4 l 4
4.10 Graphics Services
4 4 . 4 . 154
4.11 Application Software Development Support Services
l . 4 l 159
..... 4
Section 5: POSIX OSE Cross-Category Services
. 4 4 4 160
........ .
5.1 Internationalization Services
4 4 4 175
.......... . .
5.2 System Security Services
4 4 4 . 182
........ 4
5.3 Systems Management Services
. . 4 4 4 195
...............
Section 6: Profiles
4 4 4 4 195
................ 4
6.1 Scope
ii
---------------------- Page: 6 ----------------------
62 . Concepts Related to Profiles
.............. 196
63 . Guidance to Profile Developers
............. 197
64 . Types of Profiles
.................. 202
I
Section 7: POSIX SP Profiling Efforts
............. 203
Introduction
71 . . 203
Multiprocessing Systems Platform Profiles
72 . . 204
73 . POSIX Interactive Systems AEP . 206
74 . Supercomputing AEP . 206
75 . Realtime AEPs . 208
Annex A (informative) Bibliography . . . . . . . . . . . . . 211
Annex B (informative) Standards Organizations and Contact Information 217
B.1 Introduction . . . . . . . . . . . . . . . . . . . 217
B.2 The Formal Standards Groups . . . . . . . . . . . . . 218
B.3 Related Organizations . . . . . . . . . . . . . . . . 237
Alphabetic Topical Index . . . . . . . . . . . . . . . . . . 249
FIGURES
28
Figure 3-l - POSIX OSE Reference Model . . . . . . . . . . .
POSIX OSE Reference Model - Entities . . . . . . . 29
Figure 3-2 -
POSIX OSE Reference Model - Interfaces . . . . . . 31
Figure 3-3 -
. . 35
Figure 3-4 - POSIX OSE Reference Model - Distributed Systems
36
Figure 3-5 - Distributed Application Platform Implementation . . .
40
Figure 3-6 - Service Components and Interfaces . . . . . . . . .
47
Figure 4-l - POSIX OSE Language Services Reference Model . . . .
Figure 4-2 - POSIX OSE Core System Services Reference Model . . . 55
POSIX OSE Communication Services Reference Model . . 68
Figure 4-3 -
80
Figure 4-4 - POSIX OSE Communication Standards . . . . . . .
Figure 4-5 - Traditional Database Model . . . . . . . . . . . 84
84
Figure 4-6 - POSIX OSE Database Services Reference Model . . . .
. 95
Figure 4-7 - POSIX OSE Data Interchange Services Reference Model
so3
Figure 4-8 - Transaction Processing Model . . . . . . . . . .
POSIX OSE Transaction Processing Services Reference
Figure 4-9 -
105
Model . . . . . . . . . . . . . . . . . . . . . . .
POSIX OSE User Command Interface Services Reference
Figure 4-10 -
111
Model . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-ll- POSIX OSE Character-Based User Interface Services Reference
120
Model . . . . . . . . . . . . . . . . . . . . . . .
126
Figure 4-12 - POSIX OSE Windowing System Services Reference Model .
. . 142
Figure 4-13 - Computer Graphics Reference Model Level Structure
POSIX OSE Graphics Services Reference Model . . . . 143
Figure 4-14 -
POSIX OSE Application Software Development Services Reference
Figure 4-15 -
Model . . . . . . . . . . . . . . . . . . . . . . . 155
. . .
111
---------------------- Page: 7 ----------------------
Figure 5-l - POSIX OSE Reference Model for Systems Management . . 183
Selected Major Standards and Standards-Influencing Bodies 219
Figure B-l -
IEEE Standards Diagram . . . . . . . . . . . . 233
Figure B-2 -
TABLES
Table 2-l - Typographical Conventions . . . . . . . . . . . 13
43
Mapping of Service Categories to Section 4 Clauses . . .
Table 4-1 -
5 1
Language Standards . . . . . . . . . . . . . .
Table 4-2 -
62
Core System Services Standards . . . . . . . . . .
Table 4-3 -
Systems Services Standard Language Bindings . . . . 63
Table 4-4 -
Functionality of ISO/IEC 9945-l: 1990 . . . . . . . 64
Table 4-5 -
74
Table 4-6 - Communication Standards - APIs . . . . . . . . .
75
Table 4-7 - Communication Standards - EEIs . . . . . . . . .
76
Communication Standards - Services at the EEI . . . .
Table 4-8 -
Communication Standard Language Bindings . . . . . 76
Table 4-9 -
Database Standards . . . . . . . . . . . . . . 90
Table 4-10 -
91
Table 4-11 - Database Standard Language Bindings . . . . . . .
Table 4-12 - Data Interchange Standards . . . . . . . . . . . 98
108
Table 4-13 - Transaction Processing Standards . . . . . . . . .
109
Table 4-14 - Transaction Processing Standard Language Bindings . .
116
User Command Interface Processing Standards . . . .
Table 4-15 -
. 116
User Command Interface Processing Language Bindings
Table 4-16 -
122
Character-Based User Interface Standards . . . . . .
Table 4-17 -
Table 4-18 - Character-Based User Interface Standard Language
Bindings 4 4 4 4 4 4 4 4 4 4 4 4 4 4 123
Windowing Standards’ 4 4 4 136
Table 4-19 -
137
Table 4-20 - Windowing Graphical Standard Language’Bindings . . .
148
Table 4-21 - POSIX OSE Graphics Services Reference Model Standards
148
Table 4-22 - Graphics Standard Language Bindings . . . . . . .
Application Software Development Support Standards . . 157
Table 4-23 -
Application Software Development Support Services
Table 4-24 -
Bindings 4 4 4 4 4 4 4 4 a 4 4 157
170
Table 5-l - Interhationalfzation Standards. . . . . . . . . . .
System Security Standards . . . . . . . . . . . 180
Table 5-2 -
180
Table 5-3 - System Security Standard Language Bindings . . . . .
192
Table 5-4 - System Management Standards . . . . . . . . . .
192
Table 5-5 - Systems Management Standard Language Bindings . . .
204
POSIX SPs in Progress . . . . . . . . . . . . .
Table 7-1 - - - _-_~~ -
V
1v
---------------------- Page: 8 ----------------------
Introduction
(This introduction is not a normative part of IEEE Std 1003.0-1995 or of ISO/IEC TR 14252:1996.)
Purpose
This guide describes the POSIX Open System Environment (POSIX OSE). It is
intended to be used by anyone interested in using standards to construct an infor-
mation processing system, including consumers, systems integrators, application
developers, systems providers, and procurement agencies.
6 The scope of this guide is much broader than a single standard. This guide
7 identifies standards from many different areas produced by many different organ-
8 izations. The POSIX OSE is intended to be broad enough to cover the entire scope
9 of general-purpose information processing systems. While the intent of this guide
10 is to identify completely the user services for a general-purpose information pro-
11 cessing system, it is acknowledged that this will take some time, and this version
12 of the guide may be incomplete in areas that are still evolving.
13 It is important to note that this guide is not a base standard itself; it merely
14 identifies standards that might be used when constructing a complete information
15 processing system.
16 It is not appropriate to claim conformance to this guide because it contains no
17 mandatory requirements. This guide is intended to be used only as a source of
18 reference material.
19 Although this guide is a product of the IEEE POSIX standardization efforts, its
20 scope is much broader than those efforts. IEEE POSIX is currently developing
21 base standards and standardized profiles focused primarily on application pro-
22 gramming interfaces. At the end of the introduction is a cross-reference of the
23 POSIX standardization efforts and where they fit into the POSIX OSE. For a more
24 detailed discussion of POSIX profiling projects, see Section 7.
The process of selecting standards for a particular application domain is called
25
26 profiling. Recommendations for the production of different types of profiles are
27 included in this guide.
28 It may never be necessary to implement an information processing system that
29 provides an implementation of every standard in the POSIX OSE.
30 In addition to listing and categorizing existing standards efforts, this guide
31 identifies important services that standards have not yet addressed. In areas
32 where these services are not addressed, emerging standards efforts and existing
33 public specifications are described. These emerging standards and public
specifications are not part of the POSIX OSE. They are included in this guide to
34
35 identify some of the existing work that has been done in areas that are gaps in
36 the POSIX OSE. This guide does not promote the use of these specifications that
37 are outside the POSIX OSE. They are included for information purposes only.
38 User needs and standards to meet those services are continuously expanding. As
39 such, this guide will need regular revision to incorporate new user services and
V
Purpose
---------------------- Page: 9 ----------------------
40 the new standards that evolve to meet those user needs.
41 The POSIX OSE Reference Model
42 To describe the POSIX OSE, this guide develops a reference model used to classify
43 information processing standards. The reference model categorizes standards at
44 two types of interfaces:
45
Application Program Interface (API) Standards
46 These standards govern how application software interacts with the
47 computer system. These standards affect application portability.
48
External Environment Interface @El’) Standards
49 These standards affect how an information processing system interacts
50 with its external environment. These standards affect system interoper-
51 ability, user interface usability, and data portability.
52
These standards allow users to procure portions of their information processing
53 systems independently from multiple vendors according to the needs of each user.
54 The services provided at the interfaces are classified into four major categories:
55 - System services
56 Communication services
- Information services
57 .
58 - Human/Computer interaction services
59 Within these categories, service component areas are identified.
60 Using the reference model, a general set of services for each component area is
61 developed. For each of the services, existing or emerging standards are identified
62 that address each of the services. If a service is not completely addressed by an
63 existing or emerging standard, this gap in the standards is noted.
Goals
65 The POSIX OSE described in this guide should provide services to satisfy the fol-
66 lowing objectives, summarized from 3.1.
Application Portability at the Source Code Level
67
To allow for movement of source code and data to a variety of applica-
68
tion platforms
70 System Interoperability
71 To allow application software and application platform interoperability
User Portability
72
To allow people to use a wide range of application platforms without
73
retraining
74
75 Accommodation of Standards
76 To provide users and vendors with information about key interface
77 specifications related to OSE objectives
vi Introduction
---------------------- Page: 10 ----------------------
78 Accommodation of New Information System Technology
79
To allow for migration to new technologies and a variety of marketplace
80 solutions
81 Application Platform Scalability
82 To allow portability and software reuse across application platform
83
types
84 Distributed System Scalability
85 To assure that related standards do not inappropriately limit the
86 growth of distributed systems
Implementation Transparency
87
88 To allow the widest latitude in providing consistent and standard inter-
89 faces to the application, regardless of the underlying implementation
90 technology
Functional Requirements of the User
91
92 To allow clear statement of user needs and provide context for identify-
ing related standards
93
94 Benefits
95 The following items are some of the benefits derived from the use of POSIX OSE.
Integration of Components From Multiple Vendors
96
97 As the standards for system integration and system interoperability are
98 produced and implemented, users will have the choice of mixing
99 software and equipment from multiple vendors. This will allow users to
100 tailor their information processing system to their particular needs by
101 selecting hardware and software based on the needs of the application
102 rather than the ability of the hardware and software to interoperate
with the existing equipment.
103
Eficient Development and Implementation
104
Normally, systems users and providers have development and imple-
105
mentation activities that utilize personnel possessing skills in a specific
106
computer environment. As a result of this specialization, a change in
107
the target computer environment for a developer requires significant
108
retraining expense. As standards for application portability, system
109
interoperability, and system integration are developed, computer per-
110
sonnel will begin to develop skills in working with these standards.
111
This will allow a company to hire personnel with existing skills that can
112
be put to use in their operation. In addition, within a company,
113
114 resources can be redeployed between development efforts with a
115 minimum of retraining.
116 Eflicient Porting of Applications
The difficulty of moving an application from one hardware or software
117
environment to another is widely known. The porting of an application
118
that uses -standards-based interfaces to another system that provides
119
the same standards-based interfaces is considerably simpler than ports
120
involving completely different systems. The amount of system tailoring
121
vii
Benefits
---------------------- Page: 11 ----------------------
122 (i.e., changes to either the operating or application system required to
123 make them work well together) is greatly reduced.
124 Related Standards Activities
125 In addition to this guide, the Portable Applications Standards Committee (PAX)
126 has authorized other standards activities that are related to the content of this
127 guide.
128
The following table summarizes the current PASC standardization efforts’) and
129 how they relate to sections of this guide:
130 Project Standard/Profile Section
131 PlOO3.1, .la System Interfaces 42 .
132 P1003. lb, . Id Realtime (formerly P1003.4) 42 .
133 P1003.1c Threads (formerly P1003.4) 42 .
134 Pl003.le Security API (formerly PlOO3.6.1) 52 .
135 P1003.lf Transparent File Access (formerly P1003.8) 43 .
Protocol-Independent Network ApI (formerly P1003.12) 43 .
136 PlOO3. lg
Shell and Utilities 47 .
137 P1003.2, .2b
Security Utilities (formerly P1003.6.2) 52 .
138 P1003.2~
Pl003.2d Batch Queueing Extensions 47 .
139
PlOO3.5 Ada Bindings 41 .
140
P1003.5b Ada Realtime Binding (formerly P1003.20) 41 .
141
Fortran Bindings 41 .
142 PlOO3.9
P1003.10 Supercomputing Profile 72 .
143
PlOO3.13 Realtime Profile 72 .
144
145 P1003.14 Multiprocessing Profile 72 .
P1003.18 POSIX Platform Profile 72 .
146
PlOO3.21 Realtime Distributed Systems Communications 43 .
147
Guide to POSIX OSE Security Framework 52 .
148 P1003.22
Uniform ApI for Graphical User Interfaces 49 .
149 P1201.1
User Interface Drivability 49 .
150 P1201.2
P1224 OS1 API - Abstract Data Manipulation 43 .
151
Pl224.1 OS1 API - X.400 Electronic Mail/Messaging 43 .
152
P1224.2 OS1 API - X.500 Directory Services (formerly PlOO3.17) 43 .
153
OS1 API Common Support Functions 43 .
154 Pl238.0
OS1 ApI FTAM. Test Methods and C Binding 43 .
155 Pl238.1
OS1 ApI Abstract Data Manipulation - C Binding 43 .
156 P1327
OS1 API X.400 - C Binding 43 .
157 P1327.1
OS1 API X.500 - C Binding 43 .
158 P1327.2
System Administration (formerly P1003.7.n) 53 .
159 P1387.n
160 1) A Standards Status Report that lists all current IEEE Computer Society standards projects is
available from the IEEE Computer Society, 1730 Massachusetts Avenue NW, Washington, DC
161
20036-1903,USA; Telephone: +1202371-OlOl;FAX:+1202728-9614.
162
. . .
Vlll Introduction
---------------------- Page: 12 ----------------------
163
Pr0.j ect Standards/Profile
Section
164
P2003. n Test Methods (formerly P 1003.3. n)
165
Most these efforts are in the areas of API standards and standardized profiles,
166
Extensions are approved as
“amendments” or “revisions” to this document, following IEEE
167
and ISO/IEC procedures.
168
Approved amendments are published separately until the full document is reprinted
169
and such amendments are incorporated in their proper positions.
170
If you have an interest in participating in the PASC working groups addressing these
171
issues, please send your name, address, and phone number to the Secretary, IEEE
172
Standards Board, Institute of Electrical and Electronics Engineers, Inc., P.O. Box 133 1,
173
445 Hoes Lane, Piscataway, NJ 08855433 1, USA, and ask to have this forwarded to the
174
chairperson of the appropriate PASC working group. If you have an interest in
175 participating in this work at the international level, contact your ISO/IEC national body.
176 IEEE Std 1003. O-l 995 was prepared by the IEEE P1003 .O working group, sponsored
177 by the Portable Applications Standards Committee of the IEEE Computer Society. At
178 the time this standard was approved, the membership of the P1003.0 group was as
179 follows:
Portable Applications Standards Committee
180
Chair: Lowell Johnson
181
182 Vice-Chairs: Jay Ashford
183 Andrew Josey
Barry Needham
184
185 Charles Severance
Jon Spencer
186
187 Secretary: Charles Severance
188 Treasurer: Peter Smith
P1003.0 Working Group Officials
189
Allen Hankinson (1987- 1993)
Chair:
190
Kevin Lewis (1993- 1995)
191
Vice-Chairs: Kevin Lewis (1987-1993)
192
193 Fritz Schulz (19934995)
Fritz Schulz
194 Technical Editor:
Production Editors: Anthony Cincotta ( ISO/IEC Standard)
195
196 Hal Jespersen (IEEE Standard)
Charles Severance
197 Secretary:
Working Group
198
199 Michael Aaby Bob Gambrel Per Pedersen
Daniel Green
200 Michelle Aden Arnie Powell
Bill Allcorn Quin Hahn Dave Pruett
201
202 Gary Andrews Dale Harris Brian Purdy
John Hill
203 Bengt Asker Lynwood Randolph
204 Richard Holbert
Jeanne Baccash Wendy Rauch
205 Jayne Baker Michael Howard Brad Reed
206
Rick Barbour Terry Humphrey Darryl Roberts
207 Jeff Hustad
Ralph Barker Mark Ruddock
208 Tony Barrese E. Lee Hutchins Nobuo Saito
209
Jon Becker Jim Isaak Greg Sawyer
---------------------- Page: 13 ----------------------
210 Erwin R. Bender Clariest Iselt Norman Scherer
211 Rich Bergman Petr Janecek Carl Schmiedekamp
212 Andy Bihain Michael Jende Andy Schoka
Lorenzo Bonanni James Johnson Richard Scott
213
Lorraine Kevra
214 Kevin Brady Glen Seeds
Walter C. Keyser
215 Steve Brooks Ron Sellars
Michael Kjolsrud Lewis Shannon
216 Steve Carpenter
Bob Knighten Karen Sheaffer
217 Tim Carter
Bob Kruger Harry Singh
218 David Chinn
Mike Lambert Pete Smith
219 J. J. Cinecoe
220 Michel Colin Doris Lebovits Dukjoo Son
Vinnie Squitieri
221 Bud Conrad Kevin Leininger
W. Edward Ludt Keith Stobie
222 Art Corey
Heinz Lycklama Jong Sung Sunwoo
223 Jean-Michel Cornu
Sheila Mallela Sandra Swearingen
224 Joe Cote
Roger Martin Marti Szczur
225 Bernard Cox
Sunil Mehta Ravi Tavakley
226 Elizabeth Crouse
Pete Meier Eva Uristensson
227 Francis Deckelman
Gary Miller Martial Van Neste
228 Shane Deichman
Manuel Carbajo Monje Bob Voigt
229 Simion Diky
Kevin Murphy Andrew Walker
230 Dave Dodge
Yasushi Nakahara Gentry Watson
231 Dominic Dunlop
232 Mat Einseln Shigetatsu Nakao Alan Weaver
233 Dave Febrache Barry Needham James White
Suy Nguyen P,Tohn Wilber
234 Donna Fisher
Mary Lynne Nielsen John Williams
235 Don Folland
David Folsom Patricia Oberndorf Arnold Winkler
236
Jim Oblinger Wayne Yaddow
237 Kester Fong
238 Rick Forberg Peter Owens Charles Young
Ed Palmer George Zerdian
239 Thomas Ford
F. G. Patterson, Jr.
240
Introduction
---------------------- Page: 14 ----------------------
241 The following persons were membe
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.