RE: "Let the market decide" is a flawed concept
"Dan Wing" <[email protected]>
| Newsgroups | gmane.ietf.fax |
|---|---|
| Message-ID | <[email protected]> |
What do you suggest we do in this instance? Personally, I see no advantage to indicating "image/tiff-fx" if the TIFF attachment is only Profile F or S, which are defined as "image/tiff". In fact, I see only interoperational difficulties by sending a Profile F or S TIFF file marked with "image/tiff-fx" to receivers that are only capable of receiving "image/tiff". As to fragmentation, there is the additional issue of Adobe's IPR position regarding TIFF-FX as defined in the RFCs. This will create fragmentation as well, as some companies may decide to avoid TIFF-FX. -d > -----Original Message----- > From: Mac [mailto:[email protected]] > Sent: Friday, December 28, 2001 6:56 PM > To: Dan Wing; McIntyre, Lloyd; Hiroshi Tamura > Cc: [email protected]; [email protected]; [email protected]; > [email protected] > Subject: "Let the market decide" is a flawed concept > > > One lesson learned from rapporteurship of G3bis - you must anticipate what > the market > will adopt, do it together and do it right. Else you will fragment your > market and > it will form critical mass elsewhere. > --- Don > > > 05:21 PM 28/12/01 -0800, Dan Wing wrote: > > > > Yes, the above is true. > > > One could perceive a future where viewers of more efficient > > > encodings become > > > dominant and use the need to use two MIME content-types becomes > > > unnecessary. > > > >Sure. > > > > > > > If you you're only sending Profile S or F, I don't see a > > > > need to "scare" > > > > > a receiver into thinking you're sending a higher-complexity TIFF. > > > > > > > > > > So, I would recommend striking the last sentence above and > > > > replacing it > > > > > with: > > > > > > > > > > To achieve the highest amount of interworking with devices only > > > > > capable of rendering Profile S or F, "image/tiff-fx" SHOULD NOT > > > > > be used for Profile S or F; rather, "image/tiff" SHOULD be used. > > > I do not support striking the last sentence. > > > It may, however, be reasonable to add a note that captures the intent > > > without conveying a message that it is never appropriate to use > > > image/tiff-fx. > > > > > > To maximize interworking with devices that are only capable of > > > rendering Profile S or F, "image/tiff" SHOULD be used when > > > transporting Profile S or F. > > > >That wording sounds great. > > > >-d >