Re: TIFF-FX: technical changes since RFC 2301

Hiroshi Tamura <[email protected]> Tue, 24 Dec 2002 13:01:22 +0900 (JST)
Newsgroups gmane.ietf.fax
Message-ID <[email protected]>
> > ned> What we have here is two MIME types: image/tiff and image/tiff-fx. The  former
> > ned> is defined for use with two profiles of TIFF, S and F.
> > ...
> > ned> I therefore think it is entirely appropriate to say that image/tiff-fx SHOULD
> > ned> NOT be used to describe material that is known to conform to the more
> > ned> specific image/tiff type.
> 
> > ahh.  overlapping coverage.  yes.  always a problem.  (sorry I missed that
> > this was the point.)
> 
> > Forgive another bit of confusion: I've lost track of where this
> > recommendation is going to be put.
> 
> Well, one way to handle it would be to put the relevant text in the
> revised tiff-fx registration document and eliminate the text from the
> tiff/tiff-fx specification document entirely. Another would be to have
> it in both places. I don't especially care which way this is done.

I like to have the text only in the revised tiff-fx registration document.
The tiff-fx document is for file format.

Any comments from the editors?

Regards,
--
Hiroshi Tamura, Ricoh Company, LTD.
E-mail: [email protected]