P: Include additional metadata in XMP (flags, collections, VC's, etc.)

It should work fine if you use a vector file: AI, PDF, or EPS.

In my case I've tried with a vector logo copy pasted to PS as a smart object without succeeding.

If a raster graphic is made into a smart object, and that smart object is scaled to 50%, then I put a prefix of "200%" in front of the smart object name, I would expect the generator feature to export a file that looks the same as the original raster graphic... but it doesn't.

But isn't it supposed to scale the smart object layer?
So how am I supposed to do it the right way, if it's supported?

Your logo.png is a raster file, it can't be scaled as a vector.

But it should be possible to do that without polluting the regular databases. Maybe have a separate database used for that purpose only, which is subject to cleanup of expired entries.

Mmmmmmm, that mixed mode was the kind of scenario I was wondering about, and possibly more likely to make the cut. Not a complete departure from the current setup, but extending the xmp spec to contain all (or at least more) information and improving the metadata synchronization with those xmp files to give a more intelligent sync, or something along those lines.

Photoshop CS? You mean that incredibly cheap software, almost for free?

Bridge is the file browser/organizer that comes with the Photoshop CS.

What is "Bridge" ?

I actually did not intend to view offline photos, but that's a good point. I'd actually see three different approaches how to deal with it, and I'd suggest to leave it to the user to choose between:

- No method to watch offline files
- Include a thumbnail in the xmp (which makes sense only if the xmp is still online, which I could not really imagine at the moment)
- Use a regular database as a underlying cache. If LR keeps its code really clean, that it is really simple to build an abstract storage engine consisting of two others, which writes always in both, and reads from the available if one is missing. Would make searching much faster than traversing the file system each time. Actually that's not too far from what LR does right now with file system synchronization against it's database.

So I'd prefer basically three modes of storage:

- Database only with manual writing of xmp (as it is just right now)
- xmp mode only
- mixed mode with xmp preference, but using a database as a cache and backup in the offline case (where offline and missing because of deleted are distinct things)

The more I think about it, the more I'd see the function of that mixed mode database in fast searching/caching than in offline reading. E.g. having 200,000 pictures in a large file system tree would really take time to find all pictures with a particular key word or maintain a collection.

I think having the choice between these three modes would be good.