Received: by cthulhu.engr.sgi.com (941129.SGI.8.6.9/911001.SGI)
	for tiff-list id WAA11483; Fri, 16 Dec 1994 22:33:41 -0800
Return-Path: <owner-tiff>
Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (941129.SGI.8.6.9/911001.SGI)
	for <tiff-relay@cthulhu.engr.sgi.com> id WAA11478; Fri, 16 Dec 1994 22:33:34 -0800
Received: from Lilly.com by sgi.sgi.com via ESMTP (941129.SGI.8.6.9/910110.SGI)
	for <tiff@sgi.com> id WAA17448; Fri, 16 Dec 1994 22:33:32 -0800
Received: from mr.lilly.com by INET.D48.LILLY.COM (PMDF V4.3-10 #6224)
 id <01HKQDN1GWWW007WBV@INET.D48.LILLY.COM>; Sat,
 17 Dec 1994 01:33:28 -0500 (EST)
Received: with PMDF-MR; Sat, 17 Dec 1994 06:33:12 GMT
MR-Received: by mta CORP02; Relayed; Sat, 17 Dec 1994 06:33:12 +0000
MR-Received: by mta MCDEV1; Relayed; Sat, 17 Dec 1994 06:33:17 +0000
Alternate-recipient: prohibited
Disclose-recipients: prohibited
Date: Sat, 17 Dec 1994 06:24:12 +0000 (GMT)
From: BRADY CLARK D <BRADY_CLARK_D@Lilly.com>
Subject: Re: TIFF File Naming Conventions/Standards?
To: tiff@sgi.sgi.com
Cc: BRADY CLARK D <BRADY_CLARK_D@Lilly.com>
Message-id: <01HKQDN3JNVQ007WBV@mr.lilly.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Importance: normal
Priority: normal
X400-MTS-identifier: [;21336071214991/2349792@CRPVAX]
Hop-count: 2
Sender: owner-tiff@sgi.sgi.com
Precedence: bulk

Re: TIFF File Naming Conventions/Standards?
Any additional interest in the prior message about file name
standards for multiple TIFF files?

Thanks to Bill Davis for his comments.
] From an Object Oriented standpoint, a set of multiple
] single images should be a single entity.  If we consider
] other file formats, the

While I agree, there are still many systems today that produce multiple single
page images.  I was attempting to suggest that a set of standards could help
everyone deal with multiple files as if they were one.  From an OO perspective
it doesn't matter if the implementation is one directory with multiple files or
one file with multiple pages. I'd really like to be able to define a convient
set of methods for images and have all systems follow those
guidelines...However, establishing a set of naming conventions could also help
the implmentation details of such a defintion.

] Having a convention for the use of names in various
] operating systems is nice, but the same convention can be
] used to have a group of GIF files or a group of text files.

It wouldn't bother me that a standard could be used for more than one thing.
I'd be glad that the convention would be reused....I thought reuse was
fundamental to OO?

] Putting something that in a library causes so many OS
] dependencies that the extension and maintenance of the
] TIFF specific parts of the library would inevitably
] suffer.

I do agree that it would be difficult to have an efficient library that covers
many different operating systems. However, from some head aches that I've had
before I also think it would be worth it


Any body else got any ideas?

Know any businesses that have worked through this or are interested in
addressing this?

Clark Brady - Eli Lilly - 317-277-1769
brady_clark_d@lilly.com



