<div>Chris,</div><div> </div><div>There can be differences between a ROMM RGB profile and a ProPhotoRGB profile. E.g., a ROMM profile should be a lut profile. The ProPhoto profile I have seen is a matrix profile.</div><div> </div><div>This highlights the fact that that two profiles based on the same standard color space may behave differently the same, e.g., have a different perceptual rendering.</div><div> </div> <div>Best regards,</div> <div>Ann L McCarthy</div> <div><div>Imaging Systems Architect</div><div>Lexmark International, Inc.</div></div><br> <br><br><div class="gmail_quote">On Mon, May 7, 2012 at 5:39 PM, Chris Murphy <span dir="ltr"><<a href="mailto:lists@colorremedies.com" target="_blank">lists@colorremedies.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote"> <div class="im"><br> On May 6, 2012, at 1:45 AM, Richard Hughes wrote:<br> ><br> > STANDARD_space A standard space, where "srgb" -> sRGB; "adobe-rgb" -><br> > AdobeRGB; "prophoto-rgb" -> ProPhotoRGB<br> <br> </div>ProPhotoRGB is actually a renamed version of ROMM RGB. So it makes me wonder if that should be used as the base, with ProPhoto RGB as the alias, if aliasing can be supported.<br> <br> Likewise sRGB is derived from ITU-R BT.709 (or Rec. 709).<br> <br> Likewise "adobe rgb" does not exist, it's specifically "Adobe RGB (1998)" and for that matter I'd quibble with wikipedia for calling it "Adobe RGB color space" which is not strictly correct either.<br> <span class="HOEnZb"><font color="#888888"><br> Chris Murphy<br> </font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br> openicc mailing list<br> <a href="mailto:openicc@lists.freedesktop.org">openicc@lists.freedesktop.org</a><br> <a href="http://lists.freedesktop.org/mailman/listinfo/openicc" target="_blank">http://lists.freedesktop.org/mailman/listinfo/openicc</a><br> </div></div></blockquote></div><br>