Endre Stølsvik , Feb 04, 2010; 10:54 a.m.
"sRGB is a standard RGB color space created cooperatively by HP and Microsoft in 1996 for use on monitors, printers, and the Internet."
It is a sort of "middle ground" that every device should be able to replicate. (And as we know, "common ground" and "largest common denominator" usually don't give the ultimate solution to any problem: sRGB on its hand has not got a very good color gamut: "sRGB is sometimes avoided by high-end print publishing professionals because its color gamut is not big enough, especially in the blue-green colors, to include all the colors that can be reproduced in CMYK printing.")
" The sRGB color space is well specified and is designed to match typical home and office viewing conditions, rather than the darker environment typically used for commercial color matching.
Nearly all software was and is designed with the assumption that an 8-bit-per-channel image file placed unchanged onto an 8-bit-per-channel display will appear much as the sRGB specification dictates. "
Several browsers don't know how to handle any other color space - they don't even read it out from the file, they just directly dump the pixels it decodes from the file to the video card, ignoring completely the color space you've saved with the file. The same goes for many simple image viewers. Then, the video card sends those bytes to the screen. And the screen is probably somewhat near sRGB too.
So my suggestion is to go with sRGB for files meant for "standard public consumption".
I am yet not expert on color spaces, though. However, the Wikipedia article also reads: "As the recommended color space for the Internet, sRGB should be used for editing and saving all images intended for publication to the WWW. Images intended for professional printing via a fully color-managed workflow, e.g. prepress output, sometimes use another color space such as Adobe RGB (1998), which allows for a wider gamut."