Wanting to make a near complete switch from desktop to laptop for all of my work, I decided to wait for the faster and relatively cheaper machines to come out.

After buying and swapping a new hard drive, my machine now is a 15″ 2.66 Ghz i7/8gb RAM/7200 rpm (16mb cache) beauty that deals with virtualisation just fine while running every other application that I throw at it.

The project hasn’t been updated for nearly a year now. There are some forum posts on the subject: Bartek the developer has gone through a rough patch and has been unable to work on the project.

I don’t want to speculate much about the nature of his woes, but I have always wondered about the incredible speed of the updates & upgrades of the application. I deemed it unsustainable for a single person to update an application several times a month. Guess it all became too much for him.

Perhaps it is time to set the project free and allow others to take over? In any case, I wish you well Bartek. You’ve delivered wonderful free software, but it came at a price…

Some of the issues we encountered:

• data may or may not be present in Exif headers
• data may be present at different locations
• data may be present in different formats
• data may be present in different formats at different locations with different values

Terminology

For those among us who are new to image tagging, I’ll quickly explain some of the terminology used in this article.

• Exif: an outdated format mainly used for technical image data (aperture, date of capture, etc). This format has served us well up until this point, but it’s time for a replacement.
• IPTC: an outdated format used mainly for user description of the image (where was it taken? what keywords belong to the image? what copyright info?).
• XMP: a relatively new format developed by Adobe. This format could incorporate both Exif and IPTC data. XMP, being XML based, can be extended. For instance, unlike IPTC, it can deal with different character sets.

XMP & Industry Standards

I would really like to see speedy universal adoption of the XMP format. Standards are here for a reason: they generally make our lives more efficient, productive & enjoyable. XMP has the potential to become the imaging industry’s meta data standard. No more “Waiter, there’s a tag in my soup.“

It would be great if Apple would use XMP for tagging in their Aperture suite. As far as I know Adobe has released the XMP toolkit under a standard BSD license, so it allows other manufacturers to integrate it into their own proprietary applications.

Camera manufacturers for some time now have been adding their own “standards.” Enough already with the “Exif MakerFiles.” This is confusing and counter-productive for independent software developers. I venture to suggest it will be equally confusing for the developers employed by the camera manufacturers: “Which standards are we working with today boss?“

The Added Value Of Meta Data

In a time where meta data is becoming increasingly important, we really should pull together and set up & follow industry standards.

For instance, over 3,000 images were added to Flickr in the time it took me to write this sentence. Suppose that a mere 1 percent of these images were properly tagged (keywords/location/etc). That still equates to around 45,000 tagged images per day. This number is likely to increase when people become more aware of the benefits of tagging content and geo-tagging is more widely adopted (wireless meta data transfer between your camera and GPS enabled mobile phone?).

Tagged content has added value for its consumers and ensures it can be found in the first place. Tags could very well be the single most important reason behind the success of Flickr and YouTube. Enough said.

Further Reading

• XMP on Wikipedia
• Adobe on XMP
• ExifTool by Phil Harvey