diff options
| author | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2020-06-14 00:10:55 +0100 |
|---|---|---|
| committer | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2020-06-14 00:30:19 +0100 |
| commit | b6d961cb91a71f803f12b8dd1a521e08d4e60174 (patch) | |
| tree | 33cb851bc66952fcac26f6ee99f94d06a0e3149b | |
| parent | be609403b4ba0d520a038b45daffa433e1c5ec5e (diff) | |
Corrected the relation of POSIX and IEEE
Until now, we were saying "POSIX is defined by the IEEE", but in issue #12,
Michael Crusoe pointed out that this is not accurate. It is actually
jointly developed and operated by the IEEE, The Open Group and ISO/IEC JTC
1/SC 22, which together form the Austin Group.
So the sentence was modified to say tha the IEEE (potential publisher of
this paper) is part of the Austin Group that develops the POSIX standard.
Thanks a lot for bringing this up Michael.
| -rw-r--r-- | paper.tex | 5 |
1 files changed, 3 insertions, 2 deletions
@@ -173,8 +173,8 @@ We argue and propose that workflows satisfying the following criteria can not on \textbf{Criterion 1: Completeness.} A project that is complete (self-contained) has the following properties. -(1) It has no dependency beyond the Portable Operating System Interface: POSIX. -IEEE defined POSIX (a minimal Unix-like environment) and many OSes have complied. +(1) It has no dependency beyond the Portable Operating System Interface: POSIX (a minimal Unix-like environment). +POSIX has been developed by the Austin Group (which includes IEEE) since 1988 and many OSes have complied. (2) ``No dependency'' requires that the project itself must be primarily stored in plain text, not needing specialized software to open, parse or execute. (3) It does not affect the host OS (its libraries, programs, or environment). (4) It does not require root or administrator privileges. @@ -473,6 +473,7 @@ Marjan Akbari, Alice Allen, Pedram Ashofteh Ardakani, Roland Bacon, +Michael R. Crusoe, Antonio D\'iaz D\'iaz, Surena Fatemi, Fabrizio Gagliardi, |