Finally, there's TIFF. TIFF is not mentioned in the current MIME draft. I
don't know what, if any, parameters it would be appropriate for it to accept.
I believe that once again it is internally self-identifying, but I'm not sure
about this. In any case, it is a moot point since there's no standard for it
in MIME anyhow. If you want to argue about how TIFF is parameterized you can
either write a specification for it or go argue with the NETFAX folks, who are
using a specific profile of TIFF for their work.
TIFF is basically just a wrapper for various different types of image
representations. It contains a header, no that much unlike a mail header.
These fields are standardized, but since there are just so many different
possible combinations possible, there have been TIFF classes identified to
aid developers in producing output that can be used between applications.
This makes it possible for you to say that you can deal with a certain type
of TIFF class. The two that come to mind are class B and F. The later
class is the one that defines which combination of header fields are required
for dealing with FAX data.
Just a quick point: there is no need to go and write a specification, a
formal industry recognized standard exists. In addition, several classes
exist that define different types of conformance with the standard. My
recollection is that the NETFAX group was using class F, an existing
standard.
My personal feeling is that it would be nice to have some kind of mechanism
where not only TIFF but the conformance class could be indicated in MIME.
If however it would at all slow down the progress of MIME at this point, it
is not worth it - I assume it can be added at a later data through the IANA.
Best Regards,
Tim Kehres