The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: ANSI (C) vs IEEE (POSIX) Standards Body Selection
Date: Wed, 26 Jun 2024 18:52:53 +0000	[thread overview]
Message-ID: <FmQhKshYk2ziuNXN2_Qgr3fnKq0twXAlPmXtnAiLkUAIj6uACwDhOJrMO2KoYRV0rNAKQRT-OZRos2BHMO-gmr6F7rpMqgffafDBMLSJRsU=@protonmail.com> (raw)
In-Reply-To: <CAO2qRdM3-W2AbBK88rpJjzCgc15BC8efuvkkqN92+ywvbCcc6w@mail.gmail.com>

On Wednesday, June 26th, 2024 at 11:43 AM, James Johnston <audioskeptic@gmail.com> wrote:

> ANSI accredits US standards committees and delegates, both to US and International Meetings.
> ANSI can vote to accept a standard. While I don't know the issue behind POSIX, it's entirely possible that ANSI accredited IEEE to standardize things. They have done this to many various groups for standards within their wheelhouse. Sometimes this has worked well, sometimes it has worked to the interest of some particular entity, speaking as someone who has spent one to many days hanging out in standards meetings as a "technical expert".
> 
> On Wed, Jun 26, 2024 at 11:35 AM Marc Rochkind <mrochkind@gmail.com> wrote:
> 
> > I think historically ANSI did languages.
> > But, I don't know specifically why IEEE became the standards body for POSIX. I did participate for a while in the IEEE standards process (not POSIX, but something else), and I knew it as a large, very active, well managed organization, always eager to take on new things (such as the thing that I was engaged in). So maybe that was one reason.
> > 
> > Maybe a greater reason is that the part of IEEE standards that did software was chaired by a person from DEC (forgot his name). I'm sure DEC had a strong interest in a UNIX-based standard, if only to make sure that it didn't go completely wild and negate DEC's huge head start in selling machines to run UNIX.
> > 
> > Marc
> > 
> > On Wed, Jun 26, 2024 at 12:22 PM segaloco via TUHS <tuhs@tuhs.org> wrote:
> > 
> > > Good morning, I was wondering if anyone has the scoop on the rationale behind the selection of standards bodies for the publication of UNIX and UNIX-adjacent standards. C was published via the ANSI route as X3.159, whereas POSIX was instead published by the IEEE route as 1003.1. Was there every any consideration of C through IEEE or POSIX through ANSI instead? Is there an appreciable difference suggested by the difference in publishers? In any case, both saw subsequent adoption by ISO/IEC, so the track to an international standard seems to lead to the same organizations.
> > > 
> > > - Matt G.
> > 
> > 
> > 
> > --
> > My new email address is mrochkind@gmail.com
> 
> 
> 
> --
> James D. (jj) Johnston
> 
> Chief Scientist, Immersion Networks

Well and that touches on one of the standards that adds some interest to this discussion: "An American National Standard IEEE Standard Pascal Computer Programming Language".  In this case, ANSI/IEEE 770 X3.97 is the Pascal standard as sponsored by both IEEE *and* ANSI.  The lines can certainly blur.  Another example of a language standard under IEEE is 1076, VHDL.  Could it be interpreted as such:

IEEE is one institute among many that may originate the creation and publication of standards in the field of electrical engineering and adjacent fields.  ANSI, in turn, is a national general standards body that publishes standards created by groups such as IEEE as well as those created relatively independently by their own committees such as X3.

In other words you're liable to have IEEE standards that get tracked as ANSI, but the likelihood of ANSI cooking something up in their own committees and then bouncing it out to IEEE is lower if present at all?

- Matt G.

P.S. If anyone wants a trial-use copy of POSIX, there's one sitting on eBay right now https://www.ebay.com/itm/145798619385

  reply	other threads:[~2024-06-26 18:53 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 17:56 [TUHS] " segaloco via TUHS
2024-06-26 18:32 ` [TUHS] " Ori Idan
2024-06-26 18:42   ` Marc Rochkind
2024-06-26 20:07   ` Aron Insinga
2024-06-26 23:28   ` Peter Yardley
2024-06-26 18:35 ` Marc Rochkind
2024-06-26 18:43   ` James Johnston
2024-06-26 18:52     ` segaloco via TUHS [this message]
2024-06-26 19:34       ` Heinz Lycklama
2024-06-26 20:01         ` Charles H Sauer (he/him)
2024-06-27  2:36           ` [TUHS] Re: arithmetic, " John Levine
2024-06-27  3:41             ` Charles H. Sauer
2024-06-26 20:29         ` [TUHS] " Marc Rochkind
2024-06-26 21:17           ` Rich Salz
2024-06-26 21:20           ` Alan Coopersmith via TUHS
2024-06-26 21:28             ` Warner Losh
2024-06-26 21:49               ` Rich Salz
2024-06-26 21:53               ` Steffen Nurpmeso
2024-06-27  0:44                 ` Clem Cole
2024-06-27  1:11                   ` [TUHS] Origin of the name POSIX (was: ANSI (C) vs IEEE (POSIX) Standards Body Selection) Greg 'groggy' Lehey
2024-06-27  2:12                     ` [TUHS] " Ron Natalie
2024-06-27  2:37                       ` Warner Losh
2024-06-27 14:19                       ` Steffen Nurpmeso
     [not found]                     ` <CAC20D2M+75ohjTPcTBmBkejeaWjQQjWCkf=4ZYrP4Bk0MCamKA@mail.gmail.com>
2024-06-27  3:02                       ` Clem Cole
2024-06-27  3:03                         ` Clem Cole
2024-06-27  3:08                         ` Clem Cole
2024-06-27  8:20                     ` Eric E. Bowles via TUHS
2024-06-27 11:56                       ` John S Quarterman
     [not found]                         ` <CAEoi9W4ZSVCVsJJ8pdBuBobeeXOkwsey0kM6DWBnPiuSd_7TQA@mail.gmail.com>
     [not found]                           ` <CANCZdfoghuf4n=HDgRJXDJ5VqZ=rCtmq_0WadaR6kj8QmcoVQQ@mail.gmail.com>
2024-06-27 13:42                             ` John S Quarterman
2024-06-27 11:58                     ` Dan Cross
2024-06-27 14:34                       ` Clem Cole
2024-06-27 15:05                         ` [TUHS] Re: Origin of the name POSIX Heinz Lycklama
2024-06-27 13:57                   ` [TUHS] Re: ANSI (C) vs IEEE (POSIX) Standards Body Selection Steffen Nurpmeso
2024-06-27 14:22                   ` Chet Ramey via TUHS
2024-06-27 14:29                     ` Andy Kosela
2024-06-27 14:59                       ` Clem Cole
2024-06-27  4:12             ` Wesley Parish
2024-06-27  4:52             ` G. Branden Robinson
2024-06-26 19:47     ` Aron Insinga
2024-06-27  5:02       ` Nevin Liber
2024-06-26 20:36   ` Stuff Received
2024-06-26 22:33     ` James Johnston
2024-06-26 20:32 ` Clem Cole
2024-06-26 22:04   ` Heinz Lycklama

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='FmQhKshYk2ziuNXN2_Qgr3fnKq0twXAlPmXtnAiLkUAIj6uACwDhOJrMO2KoYRV0rNAKQRT-OZRos2BHMO-gmr6F7rpMqgffafDBMLSJRsU=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).