diff options
Diffstat (limited to 'posix-compliance/standards.rst')
| -rw-r--r-- | posix-compliance/standards.rst | 40 |
1 files changed, 28 insertions, 12 deletions
diff --git a/posix-compliance/standards.rst b/posix-compliance/standards.rst index ea86b94..5f47d39 100644 --- a/posix-compliance/standards.rst +++ b/posix-compliance/standards.rst @@ -22,11 +22,21 @@ independent of any standard and represents a union of multiple standards. For example, RTEMS supports BSD derived methods that are not in POSIX. -The IEEE Standard 1003.1 is the POSIX standard. Specifically, IEEE -Standard 1003.1-2008 is the 2003 edition of the POSIX standard and IEEE -Standard 1003.1-2008 is the 2008 edition. The 2008 is is an update from -the 2003 edition. Each edition of the POSIX standard tends to add some -methods, deprecate some methods, and obsolete (e.g. remove) other methods. +The IEEE Standard 1003.1 is the POSIX standard which is maintained by The +Open Group. Specifically, IEEE Standard 1003.1-2003 is the 2003 edition +of the POSIX standard which is referred to by The Open Group as Issue 6. +IEEE Standard 1003.1-2008 is the 2003 Edition of the standard with two +Technical Corrigenda applied. It does not have an issue number associated +with it. IEEE Standard 1003.1-2017 is also known as Issue 7. Each edition +of the POSIX standard tends to add some methods, deprecate some methods, +and obsolete (e.g. remove) other methods. + +API differences between Issue 5 and Issue 6 are documented at +https://pubs.opengroup.org/onlinepubs/009695399/xrat/xsh_chap01.html. +There is not a summary for the changes between Issue 6 as published +and what was released as 1003.1-2008. However, there is a summary +of API changes from Issue 6 to Issue 7 (POSIX 1003.1-2017) at +https://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xsh_chap01.html. PSE51 through PSE54 are Open Group defined profiles of the 2003 edition of the POSIX standard. These profiles are: @@ -69,21 +79,27 @@ and 2.1.1. In these editions, the profiles are as follows: * General Purpose - 812 APIs, multi-process, much more -FACE Technical Standard Edition 3.0 adds the requirement for an +FACE Technical Standard, Edition 3.0 adds the requirement for an operating system to support ``clock_nanosleep()`` in all profiles and defines one additional subcommand for the ``posix_devctl()`` methods. +FACE Technical Standard, Edition 3.1 has a number of minor changes +to the profiles. Most of these were to improve alignment with the +Software Communications Architecture (SCA) profiles. Additionally, +some inconsistencies in the profiles were noticed and addressed while +doing the alignment review. + RTEMS provides all of the methods required by the FACE Safety BASE profile and all of the methods in the Safety Extended profile which do not require multiple processes. Similarly, RTEMS provides most of the methods in the General Purpose profile which do not require multiple processes. -The Software Communications Architecture (SCA) specification targets the -requirements for software-defined radios. This specification was originally -developed in support of the Joint Tactical Radio System (JTRS) program -in conjunction with the Object Management Group (OMG). This standard is -now maintained by the Wireless Innovation Forum with support from the -U.S. Navy Joint Tactical Network Center (JTNC). Some URLs of interest: +The SCA specification targets the requirements for software-defined +radios. This specification was originally developed in support of the +Joint Tactical Radio System (JTRS) program in conjunction with the Object +Management Group (OMG). This standard is now maintained by the Wireless +Innovation Forum with support from the U.S. Navy Joint Tactical Network +Center (JTNC). Some URLs of interest: * SCA at Wireless Innovation Forum - http://www.wirelessinnovation.org/sca-based-standards-library |