Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!amdahl!rtech!hoptoad!gnu
From: gnu@hoptoad.uucp (John Gilmore)
Newsgroups: comp.lang.c
Subject: Re:  copyrighting standards to avoid their modification
Message-ID: <3994@hoptoad.uucp>
Date: 2 Feb 88 12:24:06 GMT
References: <11140@brl-adm.ARPA> <6967@brl-smoke.ARPA> <23133@rebel.UUCP>, <1880@optilink.UUCP>
Organization: Nebula Consultants in San Francisco
Lines: 24

> There is also a specific problem with the release of machine-readable forms
> of standards:  the possibility of mutated versions without warnings of the
> mutations.  This is, unfortunately, *not* an imaginary problem; it really
> has happened.  At least some of the people involved in setting ANSI and
> IEEE policy on such things consider this the more important consideration,
> or so I am told.

There's an easy fix for this:  They just copyright the standard, release
the machine-readable forms, but only give permission to distribute
*unmodified* copies.

If somebody runs it through a document scanner and distributes perfect,
machine-readable copies (unlikely, given the current state of document
scanning), what are they going to do, sue the guy for copyright violation?
Gee, that's just what they would have to do to stop somebody who distributed
a *modified* machine readable copy, had they released one.

So that can't be the reason.  I still think it's pure profit motive, and
wonder that the committee of our peers who wrote it don't claim their
own copyright on it, permitting redistribution, and only allow ANSI to
distribute it if ANSI permits it to be redistributed.  Sort of like the
GNU copyright...
-- 
{pyramid,ptsfa,amdahl,sun,ihnp4}!hoptoad!gnu			  gnu@toad.com
		"Watch me change my world..." -- Liquid Theatre