🚀 go-pugleaf

From:  Donn Terry <donn@hpfcrn.fc.hp.com>

The IEEE does not allow general access to the machine readable of any
of its standards.  The key reason is that there have actually been cases
where someone gets it, modifies it slightly for their own benefit, and
then prints it claiming it's the standard.  Since that happened, the IEEE
has been very careful about protecting its copyright and the machine
readable.

However, they do realize the world is changing, and that there is a need
to have machine-readable for legitimate reasons.  They are looking into
it (but slowly, as befits a bureaucracy).  (Someone at IEEE will kill me
for saying that :-) ).

They're defintely going to protect it somehow when it does become 
available; anonymous ftp doesn't seem real likely.

Donn Terry
Speaking only for myself, of course.

Volume-Number: Volume 21, Number 53

From:  khb@Eng.Sun.COM (Keith Bierman - SPD Advanced Languages)

In article <452@usenix.ORG> donn@hpfcrn.fc.hp.com (Donn Terry) writes:

...
   The IEEE does not allow general access to the machine readable of any
   of its standards.  The key reason is that there have actually been cases
   where someone gets it, modifies it slightly for their own benefit, and
   then prints it claiming it's the standard.  ...

Sounds like an excuse, not a reason. It would not be hard to publish
checksums. 

In the X3 world the reason is painfully clear, money. X3 relies on the
revenues generated by selling copies of the standard to finance its
operations (this information is a fallout of numerous arguments
between x3j3 members and x3; I cannot vouch that it is true, but it
was/is certainly the reason copies of the x3j3 draft are ftpable)
--
----------------------------------------------------------------
Keith H. Bierman    kbierman@Eng.Sun.COM | khb@chiba.Eng.Sun.COM
SMI 2550 Garcia 12-33			 | (415 336 2648)   
    Mountain View, CA 94043

Volume-Number: Volume 21, Number 56

From:  Chuck.Phillips@FtCollins.NCR.COM (Chuck.Phillips)

> On 24 Aug 90 05:49:57 GMT, khb@Eng.Sun.COM (Keith Bierman - SPD Advanced Languages) said:
Keith> In the X3 world the reason is painfully clear, money. X3 relies on the
Keith> revenues generated by selling copies of the standard to finance its
Keith> operations (this information is a fallout of numerous arguments
Keith> between x3j3 members and x3; I cannot vouch that it is true, but it
Keith> was/is certainly the reason copies of the x3j3 draft are ftpable)

Then how about making periodic releases of all ANSI (IEEE, etc.) standards
and current drafts on CD ROMs?  Of couse, then we'd have to create a new
committee to define the cross index and search/retrieval data interface.  ;^)

Seriously, this would allow us to create platform independent CD ROMs.
Machine dependent retrieval software often is included on CD ROMS due to
lack of said standards.

	Cheers,
--
Chuck Phillips  MS440
NCR Microelectronics 			Chuck.Phillips%FtCollins.NCR.com
2001 Danfield Ct.
Ft. Collins, CO.  80525   		uunet!ncrlnk!ncr-mpd!bach!chuckp

Volume-Number: Volume 21, Number 60

From:  jsdy@hadron.COM (Joseph S. D. Yao)

In article <462@usenix.ORG> Chuck.Phillips@FtCollins.NCR.COM (Chuck.Phillips) writes:
>and current drafts on CD ROMs?  Of couse, then we'd have to create a new
>committee to define the cross index and search/retrieval data interface.  ;^)

I believe the latest issue of ;login: referenced standard-in-progress
ANSI X3B11, or some such.  Check the hardcopy for the true reference.
(Well, this talked about WORM's: can't it apply?)

[ The snitch report on X3B11.1 by Andrew Hume was also posted to comp.std.unix
in Volume 20, Number 4, 19 May 1990.  That entire report set is available
by anonymous FTP from uunet.uu.net as
	~ftp/comp.std.unix/reports/1990.06.Z
and that specific report is currently available as
	~ftp/comp.std.unix/v20/repdir/x3b11.1
from the same machine.  For those with UUCP connections to UUNET, ~ftp is
the same directory as ~uucp, so just substitute and use uucp.  Get the file
	~ftp/comp.std.unix/README
or
	~uucp/comp.std.unix/README
for further details.  -mod]

	Joe Yao				jsdy@hadron.COM
	( jsdy%hadron.COM@{uunet.UU.NET,decuac.DEC.COM} )
	arc,arinc,att,avatar,blkcat,cos,decuac,\
	dtix,ecogong,grebyn,inco,insight,kcwc,  \
	lepton,lsw,netex,netxcom,phw5,research,  >!hadron!jsdy
	rlgvax,seismo,sms,smsdpg,sundc,telenet, /
	uunet				       /
(Last I counted ...)

Volume-Number: Volume 21, Number 73