ISO/IEC TR 14252:1996

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

• Status: Withdrawn
• Publication Date: 11-Dec-1996
• Withdrawal Date: 11-Dec-1996
• ICS: 35.060 - Languages used in information technology
• Technical Committee: ISO/IEC JTC 1/SC 22 - Programming languages, their environments and system software interfaces
• Drafting Committee: ISO/IEC JTC 1/SC 22 - Programming languages, their environments and system software interfaces
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 23-Jan-2007
• Completion Date: 30-Oct-2025

Relations

• Consolidated By: ISO 13850:2006 - Safety of machinery - Emergency stop - Principles for design
• Effective Date: 06-Jun-2022

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
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.

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
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

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; [phone]. Permission to photocopy portions of any individual standard for
educational classroom use can also be obtained through the Copyright Clearance Center.

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
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 . . . .
. 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
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
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
Figure 3-5 - Distributed Application Platform Implementation . . .
Figure 3-6 - Service Components and Interfaces . . . . . . . . .
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 -
Figure 4-4 - POSIX OSE Communication Standards . . . . . . .
Figure 4-5 - Traditional Database Model . . . . . . . . . . . 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 -
Model . . . . . . . . . . . . . . . . . . . . . . .
POSIX OSE User Command Interface Services Reference
Figure 4-10 -
Model . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-ll- POSIX OSE Character-Based User Interface Services Reference
Model . . . . . . . . . . . . . . . . . . . . . . .
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
. . .
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
Mapping of Service Categories to Section 4 Clauses . . .
Table 4-1 -
5 1
Language Standards . . . . . . . . . . . . . .
Table 4-2 -
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 -
Table 4-6 - Communication Standards - APIs . . . . . . . . .
Table 4-7 - Communication Standards - EEIs . . . . . . . . .
Communication Standards - Services at the EEI . . . .
Table 4-8 -
Communication Standard Language Bindings . . . . . 76
Table 4-9 -
Database Standards . . . . . . . . . . . . . . 90
Table 4-10 -
Table 4-11 - Database Standard Language Bindings . . . . . . .
Table 4-12 - Data Interchange Standards . . . . . . . . . . . 98
Table 4-13 - Transaction Processing Standards . . . . . . . . .
Table 4-14 - Transaction Processing Standard Language Bindings . .
User Command Interface Processing Standards . . . .
Table 4-15 -
. 116
User Command Interface Processing Language Bindings
Table 4-16 -
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 -
Table 4-20 - Windowing Graphical Standard Language’Bindings . . .
Table 4-21 - POSIX OSE Graphics Services Reference Model Standards
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
Table 5-l - Interhationalfzation Standards. . . . . . . . . . .
System Security Standards . . . . . . . . . . . 180
Table 5-2 -
Table 5-3 - System Security Standard Language Bindings . . . . .
Table 5-4 - System Management Standards . . . . . . . . . .
Table 5-5 - Systems Management Standard Language Bindings . . .
POSIX SPs in Progress . . . . . . . . . . . . .
Table 7-1 - - - _-_~~ -
V
1v
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
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
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
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:
Application Program Interface (API) Standards
46 These standards govern how application software interacts with the
47 computer system. These standards affect application portability.
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.
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
To allow for movement of source code and data to a variety of applica-
tion platforms
70 System Interoperability
71 To allow application software and application platform interoperability
User Portability
To allow people to use a wide range of application platforms without
retraining
75 Accommodation of Standards
76 To provide users and vendors with information about key interface
77 specifications related to OSE objectives
vi Introduction
78 Accommodation of New Information System Technology
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
types
84 Distributed System Scalability
85 To assure that related standards do not inappropriately limit the
86 growth of distributed systems
Implementation Transparency
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
92 To allow clear statement of user needs and provide context for identify-
ing related standards
94 Benefits
95 The following items are some of the benefits derived from the use of POSIX OSE.
Integration of Components From Multiple Vendors
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.
Eficient Development and Implementation
Normally, systems users and providers have development and imple-
mentation activities that utilize personnel possessing skills in a specific
computer environment. As a result of this specialization, a change in
the target computer environment for a developer requires significant
retraining expense. As standards for application portability, system
interoperability, and system integration are developed, computer per-
sonnel will begin to develop skills in working with these standards.
This will allow a company to hire personnel with existing skills that can
be put to use in their operation. In addition, within a company,
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
environment to another is widely known. The porting of an application
that uses -standards-based interfaces to another system that provides
the same standards-based interfaces is considerably simpler than ports
involving completely different systems. The amount of system tailoring
vii
Benefits
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.
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 .
PlOO3.5 Ada Bindings 41 .
P1003.5b Ada Realtime Binding (formerly P1003.20) 41 .
Fortran Bindings 41 .
142 PlOO3.9
P1003.10 Supercomputing Profile 72 .
PlOO3.13 Realtime Profile 72 .
145 P1003.14 Multiprocessing Profile 72 .
P1003.18 POSIX Platform Profile 72 .
PlOO3.21 Realtime Distributed Systems Communications 43 .
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 .
Pl224.1 OS1 API - X.400 Electronic Mail/Messaging 43 .
P1224.2 OS1 API - X.500 Directory Services (formerly PlOO3.17) 43 .
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
20036-1903,USA; Telephone: [phone]-OlOl;FAX:[phone].
. . .
Vlll Introduction
Pr0.j ect Standards/Profile
Section
P2003. n Test Methods (formerly P 1003.3. n)
Most these efforts are in the areas of API standards and standardized profiles,
Extensions are approved as
“amendments” or “revisions” to this document, following IEEE
and ISO/IEC procedures.
Approved amendments are published separately until the full document is reprinted
and such amendments are incorporated in their proper positions.
If you have an interest in participating in the PASC working groups addressing these
issues, please send your name, address, and phone number to the Secretary, IEEE
Standards Board, Institute of Electrical and Electronics Engineers, Inc., P.O. Box 133 1,
445 Hoes Lane, Piscataway, NJ 08855433 1, USA, and ask to have this forwarded to the
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
Chair: Lowell Johnson
182 Vice-Chairs: Jay Ashford
183 Andrew Josey
Barry Needham
185 Charles Severance
Jon Spencer
187 Secretary: Charles Severance
188 Treasurer: Peter Smith
P1003.0 Working Group Officials
Allen Hankinson (1987- 1993)
Chair:
Kevin Lewis (1993- 1995)
Vice-Chairs: Kevin Lewis (1987-1993)
193 Fritz Schulz (19934995)
Fritz Schulz
194 Technical Editor:
Production Editors: Anthony Cincotta ( ISO/IEC Standard)
196 Hal Jespersen (IEEE Standard)
Charles Severance
197 Secretary:
Working Group
199 Michael Aaby Bob Gambrel Per Pedersen
Daniel Green
200 Michelle Aden Arnie Powell
Bill Allcorn Quin Hahn Dave Pruett
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
Rick Barbour Terry Humphrey Darryl Roberts
207 Jeff Hustad
Ralph Barker Mark Ruddock
208 Tony Barrese E. Lee Hutchins Nobuo Saito
Jon Becker Jim Isaak Greg Sawyer

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
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
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.
Introduction
241 The following persons were members of the balloting group:
242 Nick Stoughton EurOpen Institutional Representative
243 Robert Boucher Uniforum Institutional Representative
244 Norman Aaronson Joe Gwinn
Wendy Rauch
245 Michelle Aden
Allen L. Hankinson Robert Sarr
Lynda Allen
246 Barry Hedquist Andrew M. Schoka
247 Bengt Asker Hans H. Heilborn Fritz Schulz
248 Ralph Barker John L. Hill Richard L. Scott
249 Richard M. Bergman James C.M. Ho Peter Smith
250 Andy R. Bihain Andrew R. Huber Jeff Stevenson
251 Robert Bismuth Richard Hughes-Rowlands Sandra Swearingen
252 Keith Brophy Jim Isaak James G. Tanner
253 Dawn Burnett Petr Janecek Ravi Tavakley
254 George S. Carson Hal Jespersen Donn S. Terry
255 Stephan M. Chan Derek Kaufman Andrew T. Twigger
256 Kilnam Chon Judy Kerner Mark-Rem5 Uchida
257 William Corwin Lorraine C. Kevra Martial Van Neste
258 Fred D. Crowner Martin J. Kirk Andrew Walker
259 Dave Decot Greger Leijonhufvud Stephen R. Walli
260 Shane Deichman Kevin Lewis Paul Wanish
261 Stephen L. Diamond Lee W. Lucas Bruce Weiner
262 Ron Elliott Roger Martin Andrew E. Wheeler
263 Richard W. Elwood Roland McGrath Alex White
264 Philip H. Enslow Pete Meier John R. Williams
265 Donna K. Fisher Gary W. Miller Peter Wishart
266 Donald Folland John S. Morris Charles R. Young
267 Bob Gambrel Alok C. Nigam Oren Yuen
268 Michel Gien Patricia Oberndorf John J. Zenor
269 Michael Gonzalez A. W. Powell George R. Zerdian
270 Scott E. Preece
xi
271 The final conditions for approval of this standard were met on May 2, 1995. This
standard was conditionally approved by the IEEE Standards Board on March 16,
273 1995, with the following membership:
274 E. G. Wl” Kiener, Chair
Donald C. Loughry, Vice Chair
275 Andrew G. Salem, Secretary
276 Gilles A. Baril Richard J. Holleman Marco W. Migliaro
277 Clyde R. Camp Jim Isaak Mary Lou Padgett
278 Joseph A. Cannatelli Ben C. Johnson John W. Pope
279 Stephen L. Diamond Sonny Kasturi Arthur K. Reilly
280 Harold E. Epstein Lorraine C. Kevra Gary S. Robinson
281 Donald C. Fleckenstein Ivor N. Knight Ingo Rusch
282 Jay Forster* Joseph L. Koepfinger* Chee Kiow Tan
283 Donald N. Heirman D. N. “Jim” Logothetis Leonard L. Tripp
284 L. Bruce McClung
285 *Member Emeritus
286 Also included are the following nonvoting IEEE Standards Board liaisons:
287 Satish K. Aggarwal
288 Richard B. Engelman
289 Robert E. Hebner
290 Chester C. Taylor
291 Mary Lynne Nielsen
292 IEEE Standards Project Editor
293 Apple and Macintosh are trademarks of Apple Computer, Inc., regist,esed in the U.S. and atIler
294 countries.
Microsoft and Windows are registered trademarks of Microsoft Corporation.
Open Software Foundation, OSF, the OSF logo, and Motif are registered trademarks of the 0pen
Software Foundation, Inc.
298 OS/2 is a trademark of International Business Machines Corporation.
POSIX@ is a registered certification mark of the Institute of Electrical and Electronics Engineers, Inc.
UNIX@ is a registered trademark in the United States and other countries, licensed exclusively
301 through X/Open Company Limited.
302 X/Open and the X device are trademarks of X/Open Company Ltd.
xii Introduction
ISO/IEC TR 14252: 1996(E)
TECHNICAL REPORT
Information technology - Guide to the POSIX Open System
Environment (OSE)
Section 1: General
1 1.1 Scope
2 This guide provides
3 (1) Definitions of the concepts of application portability, application intero-
perability, data portability, and user portability
5 (2) Descri p t ions of services needed in the areas of application portability,
6 application interoperability, data portability, and user portability
7 (3) A survey of existing standards that address these objectives
8 (4) Identifi ca t ion of those areas where formal standards do not exist and disa-
9 cussion of near-term strategies for filling these gaps
10 (5) Guidance on assembling these standards into profiles
11 This guide includes no mandatory requirements.
12 1.2 Normative References
13 The following standards contain provisions that, through references in this text,
14 constitute provisions of this guide. At the time of publication, the editions indi-
15 cated were valid. All standards are subject to revision, and parties to agreements
16 based on these standards are encouraged to investigate the possibility of applying
17 the most recent editions of the standards listed below. Members of IEC and IS0
18 maintain registers of currently valid International Standards.
1.2 Normative References
ISO/LEC TR 14252:1996(E)
ANSI/IEEE Std 1003.0-1995 GUIDE TO THE POSIX@
19 NOTE: All formal international, regional, and national standards cited in this guide are listed in
20 this clause. Only those JTC 1 standards that have achieved DIS or ITU-T Recommendation status are
21 listed. Only those national body standards that have completed the process of adoption are listed,
22 and only when there is no international or regional standard covering the same area. All other
23 specifications or references cited in this guide are given as bibliographic entries in Annex A.
ISO/IEC 646: 1991,l) Information processing-IS0 g-bit coded character set
(11
25 for information interchange.
26 ISO/IEC 1539: 1991, Information technology-Programming languages-
27 Fortran.
28 IS0 1989: 1985 [ANSI X3.23-1985 (Reaff. 1991>], Programming languages-
(3)
29 COBOL.
30 IS0 2014: 1976, Information processing- Writing of calendar dates in all-
(4)
31 numeric form. ‘)
32 ISO/IEC 2022: 1994, Information technology-Character code structure and
(5)
33 extension techniques.
IS0 3307: 1975, Information processing-Representation of time of the day.‘)
35 IS0 4031: 1987, Information processing-Representation of local time
(71
36 differentials.‘)
37 IS0 4217: 1990, Codes for the representation of currencies and funds.
~~~
IS0 4873: 1991, Information technology-IS0 &bit code for information
19)
interchange-Structure and rules for implementation.
40 (10) IS0 6093: 1985, Information processing-Representation of numerical values
in character strings for information interchange.
42 IS0 6160: 1979 [ANSI X3.53-1976 (Reaff. 1993)], Programming languages-
43 PLII.
ISO/IEC 6429: 1992, Information technology-Control functions for coded
45 character sets.
ISO/IEC 6522: 1992 [ANSI X3.74-1987 (Reaff. Programming
46 19Wl)
languages-Information technology--P1 I I general purpose subset.
IS0 6936: 1988, Information processing-Conversion between the two coded
character sets of IS0 646 and IS0 6937-2 and the CCITT international tele-
graph alphabet No. 2 @TM).
(15) ISO/IEC 6937: 1994, Information technology-Coded graphic character set
52 for text communication-Latin alphabet.
53 (16) ISO/IEC 7185: 1990, Information technology-Programming languages-
54 Pascal.
55 1) IS0 and ISO/IEC documents can be obtained from the IS0 office, 1, rue de Varembe, Case Postale
56, CH-1211, Geneve 20, SwitzerlandDuisse.
2) Please note that this standard is currently withdrawn.
1 General
ISOLIEC TR 14252: 1996(E)
OPEN SYSTEM ENVIRONMENT (OSE) ANSYIEEE Std 1003.0- 1995
58 (17) ISO/IEC 7350: 1991, Information technology-Registration of repertoires of
59 graphic characters from IS0 10367.
60 (18) ISO/IEC 7498: 1994, Information processing systems-Open Systems Inter-
61 connection-Basic Reference Model: The Basic Model.
62 (19) IS0 7498-2: 1989, Information processing systems-Open Systems Inter-
63 connection-Basic Reference Model-Part 2: Security Architecture.
{ZO) IS0 7942: 1985, Information processing systems-computer graphics-
65 Graphical Kernel System (GKS) functional description.
(21) ISOIIEC 8072: 1994, Information processing systems-Open Systems Inter-
connection-Transport service definition.
68 ISO/IEC 8073: 1992, Information technology-Telecommunications and
69 information exchange between systems- Open Systems Interconnection-
Protocol for providing the connection-mode transport service.
71 IS0 8327: 1987, Information processing systems-Open Systems Inter-
72 connection-Basic connection oriented session protocol specification.
(24) IS0 8485: 1989, Programming languages-APL.
12s) IS0 8571, Information processing systems-Open Systems Inter-
75 connection-File Transfer, Access and Management.
76 IS0 8601: 1988, Data elements and interchange formats-Information
(26
77 interchange-Representation of dates and times.
78 IS0 8602: 1987, Information processing systems-Open Systems Inter-
79 connection-Protocol or providing the connectionless-mode transport
f
80 servzce.
(28) IS0 8613, Information processing-Text and office systems-Ofice Docu-
ment Architecture (ODA) and interchange format.
83 (29) ISO/IEC 8632: 1992, Information technology-Computer graphics-Metafile
for the storage and transfer of picture description information.
85 (30) IS0 8649: 1988, Information processing systems-Open Systems Inter-
86 connection-Service definition for the Association Control Service Element.
87 (31) IS0 8650: 1988, Information processing systems-Open Systems Inter-
88 connection-Protocol specification for the Association Control Service
89 Element.
90 } IS0 8651, Information processing systems-Computer graphics-Graphical
91 Kernel System (GKS) language bindings.
) IS0 8652: 1987 (ANSI/MIL 1815A-1983), Programming languages-Ada.
93 (34) ISO/IEC 8802-3: 1993 (ANSI/IEEE Std 802.3, 1993 Edition), Information
94 technology-Local and metropolitan area networks-Part 3: Carrier sense
multiple access with collision detection (CSMA/CD) access method and phy-
sical layer specifications.
1.2 Normative References
ISOlIEX TR 14252: 1996(E)
ANSI/IEEE Std 1003.0-1995
GUIDE TO THE POSM@
97 ISO/IEC 8802.4:1990 (ANIS/IEEE Std 802.4~1990), Information processing
(35)
systems-Local area networks-Part 4: Token-passing bus access method
99 and physical layer specifications.
100 ISO/IEC 8802-5: 1995
(ANSI/IEEE Std 802.5-1995), Information
(361
101 technology-Telecommunications and information exchange between
102 systems-Local and metropolitan area networks-Specific requirements-
103 Part 5: Token ring access method and physical layer specifications.
104 IS0 8805: 1988, Information processing systems-Computer graphics-
Graphical Kernel System for Three Dimensions (GKS-3D) functional
106 description.
ISO/IEC 8806-1: . . . ,3) Information
138 processing sys terns-Comp u ter
108 graphics-Graphical Kernel System for Three Dimensions (GKS-3D)
109 language bindings-Part 1: FORTM.
110 ISO/IEC 8806-4: 1991, technology-Computer
Information graphics-
111 Graphical Kernel System for Three Dimensions (GKS-3D) language
112 bindings-Part 4: C.
113 ISO/IEC 8823-l: 1994, Information technology-Open Systems Inter-
(40)
114 connection-Connection-oriented presentation protocol: Protocol
115 specification.
116 ISO/IEC 8824: 1990, Information technology-Open Systems Inter-
(41)
117 connection-Specification of Abstract Syntax Notation One (ASN.1).
118 ISO/IEC 8825: 1990, Information technology-Open
WI Systems Inter-
119 connection-Specification of Basic Encoding Rules for Abstract Syntax
120 Notation One (AsN.1).
121 IS0 8859-1: 1987, Information processing-g-bit single-byte coded graphic
(43)
122 character sets-Part 1: Latin alphabet No. 1.
IS0 8879: 1986, Information processing-Text and office systems-Standard
(44)
124 Generalized Markup Language (SGMLJ.
IS0 9040: 1990, Information technology-Open Systems Interconnection-
126 Virtual Terminal Basic Class Service.
IS0 9041, Information technology-Open Systems Inter~~o~.ancction.---.-Virtual
127 (46
Terminal Basic Class Protocol.
129 IS0 9069: 1988, Information processing-SGML support facilities---SGML
Document Interchange Format (SDIF).
ISOIIEC 9075: 1992 (ANSI X3.135-1992), Information technology-Database
132 languages-SQL.
IS0 9241, Ergonomic requirements for oflce work with visual display termi-
(49)
134 nals WDTS).
135 3) Presently at the state of Draft International Standard.
1 General
OPEN SYSTEM ENVIRONMENT (OSE) ANSI/IEEE Std 1003.0- 1995
136 ISO/IEC 9314, Information technology-Fibre Distributed Data Interface
(50)
137 (FDN).
138 IS0 9316: 1989, Information processing systems-Small Computer System
(511
139 Interface (SCSI).
ISO/IEC 9541, Information technology-Font information interchange.
(52)
ISO/IEC 9548-J.: . . . ,3) Information processing systems-Open Systems Inter-
(531
142 connection-Session connectionless protocol to provide the connectionless-
143 mode session service.
144 ISO/IEC 9576: 1991, Information technology-Open
(541 Systems Inter-
145 connection-Connectionless presentation protocol specification.
146 ISO/IEC 9579, Information technology-Open Systems Interconnection-
(551
147 Remote Database Access.
148 ISOIIEC 9592, Information processing systems-Computer graphics-
(561
149 Programmer’s Hierarchical Interactive Graphics System (PRIGS).
ISO/IEC 9593, Information processing systems-Computer graphics-
150 1571
151 Programmer’s Hierarchical Interactive Graphics System (PHIGS) language
152 bindings.
153 ISO/IEC 9594-l: 1990, Information technology-Open Systems Inter-
68)
connection-The Directory-Part 1: Overview of concepts, models and
155 services.
156 ISO/IEC 9594-8: 1990, Information technology-Open Systems Inter-
157 connection-The Directory-Part 8: Au then tica tion frame work.
158 ISO/IEC 9596-l: 1991, Information technology-Open Systems Inter-
159 connection--Common management information protocol-Part 1:
160 Specification.
161 ISO/IEC 9636: 1991, Information
(61) technol ogy-Comp u ter graphics-
162 Interfacing techniques for dialogues with graphical devices (CGI)-
163 Functional specification.
ISO/IEC 9637-2: 1992, Information technology-Computer
164 1621 graphics-
165 Interfacing techniques for dialogues with graphical devices (CGI)-Data
166 stream binding-Part 2: Binary encoding.
167 ISO/IEC 9638-3: 1994, Information technology-Computer Graphics-
(63)
168 Interfacing techniques for dialogues with graphical devices (CGI)-
169 Language bindings-Part 3: Ada.
170 IS0 9735: 1988, Electronic data interchange for administration, commerce
171 and transport (EDIFACT)-Application level syntax rules (Amended and
3.72 reprinted 1990).
3) Presently at the state of Draft International Standard.
1.2 Normative References
...