On Thu, Dec 12, 2013 at 6:18 PM, Largo84 <[email protected]> wrote: > The convention is that the file name is the same between the sidecar file > and the raw image file.
A big difference between images-with-side-car files and text files, like program code for example, is that images and .xmp mostly have a one-to-one relationship while arbitrary text files often won't. For a metaphor, think what it would be like managing the files if every frame in video had it's own .xmp side car, e.g. a single .leo file with multiple @file nodes. In the GIS world, which has many data formats utilizing multiple files to represent a single data-set (e.g. shapefile), we often struggle re-piecing data together because somewhere along the line someone dropped a side-car that didn't immediately make the data-set unusable. For example a .shp file without an accompanying coordinate system description (.prj) will work just fine for years in it's originating office, but hand it off to a colleague and they start complaining about stuff being in the wrong country and hemisphere. Anyway, side-cars *do* work. The aforementioned shapefile for example is still the defacto interchange format for spatial data decades after it's inception in spite of it's many limitations, the side-car nature being one of them. It's just that there are side effects to consider. -matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
