The question is IMO, what's the expected result?agree. Only an example: the SGILOGLUV encoding in the TIFF spec is XYZ. I simply like to handle these images as XYZ in floating point color space, and see them through the correct monitor profile on screen.
I think a property of a HDR image seems to be, that it rather has no implied whitepoint luminance (or other viewing conditions). It captures the scene colorimetrically with a very high dynamic range, and this gives the opportunity to compute the appearance of the recorded scene for various different viewing conditions at a later time. But this also implies, that in order to render a HDR image for viewing (e.g. on the screen or any other output device), one needs to supply the desired viewing conditions as additional input parameter for the rendering process, and then the HDR image can be rendered for these viewing conditions. In the simplest case, the viewing condition represents just the luminance of the adapted white point, i.e. you need to specify, which Y value in the HDR image you want to get mapped to monitor white (-> luminance scaling only), but of course more sophisticated appearance models could be used as well.
>From an HDR image editor I think I would for instance expect, that the display filter offers me a slider or scrollbar for each image editing window, such that I can "scroll" through the full luminance range of the HDR image, similar to spatial scrolling in x and y direction, if the image is larger than the editor window. With this "luminance scroll bar" I could tell the display filter my desired viewing conditions for the screen display, and the display filter can use this "viewing condition" to scale the image luminance, before applying the monitor profile and sending the result to the screen.
Best Regards,
Gerhard
