Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 +MMDF+2.11; site ukc.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!mcvax!ukc!msp
From: msp@ukc.UUCP (M.S.Parsons)
Newsgroups: net.ai
Subject: Re: An Image Format Standard
Message-ID: <182@ukc.UUCP>
Date: Sat, 20-Jul-85 13:29:14 EDT
Article-I.D.: ukc.182
Posted: Sat Jul 20 13:29:14 1985
Date-Received: Mon, 22-Jul-85 03:58:08 EDT
References: <1187@pucc-k> <1130@vax135.UUCP>
Reply-To: msp@eagle.UUCP (Mike Parsons. )
Organization: U of Kent at Canterbury, Canterbury, UK
Lines: 29
Keywords: Raster, Quadtree, Run-Length

In article <1130@vax135.UUCP> miles@vax135.UUCP (Miles Murdocca) writes:
>How about this idea:  subscribers to the net informally create a standard 
>that fills their needs as well as the needs of anyone else they can think 
>of. For starters, I suggest this: every image will start with a fixed size 
>header that gives information on the rest of the image(s).
>Such information could be X dimension (in pixels), Y dimension, type
>of data (graphic or raster), number of bits per pixel, number of images,
>etc.  Color maps and data would then follow.  Ideas or comments, anyone?

Good idea. I would love to trade images round the net. I think the header
needs to be somewhat more flexible though: What about run-length, quadtree,
octree and other 3-D data? To keep size to a minimum, every image could be
put through compress. We'll need uuencode/decode too. What about the HIPS
system? Reference in bib format:

%A Michael S. Landy
%A Yoav Cohen
%A George Sperling
%D 1984
%I Academic Press Inc.
%J Computer Vision, Graphics and Image Processing
%K HIPS, UNIX, Image Processing, filters, Headers
%P 331-347
%T HIPS: A UNIX-Based Image Processing System
%V 25

--------------------------------------------------------------------------------
Mike Parsons           UUCP: ..!seismo!mcvax!ukc!msp  ARPA: MSP%UKC@UCL-CS.ARPA
JANET: MSP%UKC@UCL-CS  MAIL: Computing Lab, Univ. of Kent, Canterbury, Kent, UK.