Re: Mac OS X 10.1 File Name Extension Guidelines
Re: Mac OS X 10.1 File Name Extension Guidelines
- Subject: Re: Mac OS X 10.1 File Name Extension Guidelines
- From: Lloyd Sargent <email@hidden>
- Date: Mon, 10 Sep 2001 18:56:40 -0500
On Tuesday, September 11, 2001, at 02:14 AM, j o a r wrote:
On Monday, September 10, 2001, at 02:21 , Ondra Cada wrote:
A particular example might be .tar.gz. It is more than just .gz; it
brings
not just the information "this can be decoded by gzip" as any other
.gz file,
but *also* it informs "it can be decoded by gnutar -z".
Why not be even more explicit while we're at it:
MyDocument.html.txt.tar.gz
Woho, types through file name extensions! The type is longer then the
file name! Don't forget to tell your mom that she can use long file
names, up to 255 characters, _provided_ that she uses the right file
type. Otherwise she'll need to remember to truncate the file name by
the length of the file name extension - got that mom?
On the other hand, if we* _accept_ that it's OK to use file system meta
data, we could easily add any number of extra tags - besides or instead
of T/C - for hierarchial types or whatever we think is reasonable. Why
not have a "backed up" flag as well? Or perhaps shoot for a general
purpose extensible xml field for whatever we might think of later?
*) hopefully "we" could be some standards organization with members
from the rest of the industry.
I prefer this embedding of meta-data over trying to explain to my wife
what MyDocument.html.txt.tar.gz is (or how to use it!).
Just my 2 cents...
Cheers,
Lloyd
--------
Canna Software Development
"No llamas used metadata or resorted to outlandishly long filenames in
the creation of this e-mail."