tag:blogger.com,1999:blog-21058102.post-86186000589734191452007-09-24T15:29:00.000-07:002007-09-24T15:35:56.380-07:00I have been doing research on what options I have for supporting XMP. It is a priority for me but with the image meta data standards being so ambiguous it seems like a lot of work to take on.<br /><br />So where should I store an images description: XMP, IPTC or EXIF. All three blocks I guess. What happens if when scanning an image the multiple results for a description are different, do I take the IPTC or XMP value?<br /><br />In the XMP schema, I have even more options with the different schemas available. For example the Author property can potentially be stored in the following locations:<br /><br />The Creator tag in the XMP Dublin Core schema:<br />/ifd/xmp/purl.org/dc/elements/1.1/dc:creator<br /><br />The Artist tag in the EXIF schema:<br />/ifd/{ushort=315}<br /><br />The Artist tag in the EXIF schema embedded in an XMP block:<br />/ifd/xmp/ns.adobe.com/tiff/1.0/tiff:artist<br /><br />So I guess one option is just to reverse engineer what Windows Vista does but even the Microsoft APIs scare me: just read <a href="http://bloggingabout.net/blogs/erwyn/archive/2007/03/18/diving-into-c-for-flickr-metadata-synchr-v0-6-0-0.aspx">this!</a><br /><br />I am currently working on a .NET version of ImageWalker (v3.0) and what I would like to do is focus on that after this release. The problem is I am not sure how long before the .NET version is releasable. Bit of a dilemma really, if the .NET version comes along quickly I will add XMP to that; if it is slow I will add it to next release of V2.3x.<br /><br />Being a one man part time project makes everything slow...need to work faster!ImageWalkerGuyhttp://www.blogger.com/profile/02126781094912283684noreply@blogger.com