In FileInfo view for an image, if I switch to the 'Raw Data' tab, it shows photoshop:ColorMode and photoshop:ICCProfile. However, when I check the actual XMP data of the image e.g. using exiftool or a text editor, these properties do not exist in the XMP data.
According to this thread: http://forums.adobe.com/message/5057589 these are both internal properties to PS / Bridge, which explains why they don't exist in the XMP. But why are they shown in the 'Raw' data view for the XMP then? Showing them here is just confusing as it makes it seem like they should exist in the XMP data.
I can't really see any point in including nonexistent tags in the Raw Data view. But if it is deemed necessary, how about highlighting them a different color, such as using a grey font instead of black? At least it would indicate that they were different to the real data.
P.S. This is with Bridge CS5, possibly the issue has been fixed in CS6?
They are part of the Photoshop schema. ExifTool does support them, see...
Yes, Exiftool does support those tags, but they must be written to the file for exiftool to be able to read them. The issue is that these tags are not written to the file by Bridge, but are included in the 'Raw Data' view of the XMP, which makes it look like they have been written to the file.
Since those tags are used internally by Bridge, and not actually written to the file, exiftool cannot extract the data from the nonexistent tags.
There is a lot of data that is held in the metadata for various reasons, you can even add your very own.
The tags you mentioned are used by Photoshop and various other applications so they can get the mode, profile of the document.
The issue is that the Bridge File Info panel is showing these tags in the XMP for the image, but if you check the XMP of the file, those tags aren't there.
As a side issue, Bridge File Info panel is also showing the XMP in a different structure to that which exists in the actual file. There are two issues here really
Although I would like the ColorMode tag added to the image, I don't think point 1 is a real issue, since the ICC profile is embedded okay. Point 2 does appear to be a bug (or at least it is confusing if it is intended behaviour).