Inactive-Reserved Standard

IEEE 1003.13-2003

IEEE Standard for Information Technology - Standardized Application Environment Profile (AEP) - POSIX(™) Realtime and Embedded Application Support™

This standard is part of the POSIX series of standardized profiles for open systems. It defines environment profiles for portable realtime and embedded applications.

Standard Committee
C/MSC - Microprocessor Standards Committee
Status
Inactive-Reserved Standard
PAR Approval
2002-06-13
Superseding
1003.13-1998
Board Approval
2003-12-10
History
ANSI Approved:
2004-04-26
Published:
2004-09-10
Reaffirmed:
2010-06-17
Inactivated Date:
2021-03-25

Working Group Details

Society
IEEE Computer Society
Standard Committee
C/MSC - Microprocessor Standards Committee
Working Group
POSIX_WG - System Services Realtime Working Group
IEEE Program Manager
Tom Thompson
Contact Tom Thompson
Working Group Chair
Joseph Gwinn

Other Activities From This Working Group

Current projects that have been authorized by the IEEE SA Standards Board to develop a standard.


No Active Projects

Standards approved by the IEEE SA Standards Board that are within the 10-year lifecycle.


No Active Standards

These standards have been replaced with a revised version of the standard, or by a compilation of the original active standard and all its existing amendments, corrigenda, and errata.


No Superseded Standards

These standards have been removed from active status through a ballot where the standard is made inactive as a consensus decision of a balloting group.


No Inactive-Withdrawn Standards

These standards are removed from active status through an administrative process for standards that have not undergone a revision process within 10 years.


1003.26-2003
IEEE Standard for Information Technology - Portable Operating System Interface (POSIX(TM)) - Part 26: Device Control Application Program Interface (API) [C Language]

This standard is part of the POSIX series of standards. It defines an application program interface for controlling device drivers. Although it is based on the widely used ioctl() system call, the interface is type-safe and has a fixed number of parameters.

Learn More About 1003.26-2003

Subscribe to our Newsletter

Sign up for our monthly newsletter to learn about new developments, including resources, insights and more.