Registration of media type image/vnd.radiance

[Mark Baker]

On Tue, Dec 30, 2008 at 11:34 PM, R Fritz <rfritz at u.washington.edu> wrote:
> Type name: image
>
> Subtype name: vnd.radiance

Vendor subtypes are structured as "vnd.<vendor>.<typename>", so if you
want to stick with it, perhaps "vnd.lbl.radiance" would be
appropriate.  If not, how about image/radiance?

>
> Required parameters: None
>
> Optional parameters: None
>
> Encoding considerations: Binary preferred.  This is a binary image
>  type with a text header; "binary" or "base64" are the only
>  reasonable choices.
>
> Security considerations: The Radiance HDR file format does not include
>  executable code or scripts; it is a graphics file with an ASCII
>  header. Compression is used, which could crash an image
>  viewer. There is no way to completely rule out the possibility of
>  malicious content, however HDR viewer applications do not usually
>  run with administrator privileges--they seem poor targets for such
>  attacks.
>
> Interoperability considerations: byte orders are spelled in the
>  published specification; we expect that Radiance HDR files will be
>  readable on all systems.
>
> Published specification: *Radiance File Formats*, available freely at
>  <http://radsite.lbl.gov/radiance/refer/> and also as part of Ch 18
>  of *Rendering With Radiance* (Booksurge/Amazon, ISBN 0974538108).
>
> Applications that use this media type: Adobe Photoshop, AHDRIA,
>  AHDRIC, CinePaint, FDRTools, hdrgen, HDR Shop, PFStools,
>  Photosphere, Qtpfsgui, RadDisplay, Radiance, Web HDR

So these tools currently use image/vnd.radiance?

Mark.