I think there are some elements of the XMP it is trying to make sense of, and perhaps failing. Or possibly the XMP-reading code is in production but none of the

I think there are some elements of the XMP it is trying to make sense of, and perhaps failing. Or possibly the XMP-reading code is in production but none of the decoding is yet. Or maybe it will get keywords from XMP but nothing else? Not sure. The thing is, XMP is not any kind of independent standard; it's largely a set of instructions specific to Adobe Camera Raw and Photoshop. I do think we should expect them ultimately to be able to interpret most of it, and I half expect them to support XMP in their eventual DAM product as one sidecar type, (which is why I think there is probably code in Photo that is ready to read it) but they don't commit to it yet. I must say that if I process a raw file in one package then open it up in a competitor's raw processing package, I expect the second to ignore the work of the first The main thing that the suite really can't do is a Bridge-type function, though.