Stoyan:
Thanks for being so responsive. If you were not aware, there are many resources out there that allow one to manage the metadata in images. The problem has been that there are several places it can be stored, notably, in the
Exif,
IPTC-IIM, or
XMP containers. Making sure that all of the values are synchronized can be a bigger challenge. However, one group has stepped forward to take on this challenge. Dubbed the Metadata Working Group, representatives from Microsoft, Adobe, Apple, Canon and Nokia, have released a White paper called
Guidelines for Handling Metadata, that would be a good reference to check. Does Smushit have a metadata policy -- a set of acceptable practices and standards? If not, I would suggest looking this Metadata Working Groups white paper as a good place to start.
While I understand the need to make images smaller for the web (actually resizing the image rather than changing the image pixel attributes), I think that encouraging users to strip metadata wholesale creates a real issue. I know that for small web images, the amount of textual data within them can bloat, but this doesn't mean that you have to throw the baby out with the bath water. Even offering to remove all but the copyright notice, copyright URL, XMP rights (Rights Usage Terms) and Creator fields would still reduce the size of the image with causing it to become an Orphaned Work.
In using the tool, I see no attempt to warn users not to violate copyright, in fact, there doesn't even appear to even be an End User License Agreement anywhere on the site. It would be useful to at least have a warning to notify users that they must only run such a tool on their own images (these would be the only ones which they have the authority to modify). However, in looking at the Smushit tool, I don't even see a checkbox to acknowledge that these are the users property. In fact, the way it's set up, it seems to encourage the use of property other than one's own. This I find troubling, especially since when you launched, the tool removed metadata in the images, so if someone "borrowed" an image from another website, the version provided by Smushit was bereft of any information that might have helped the end user locate the original source at a later point in time. If this is to remain a fixture, I would recommend, that at minimum, the URL that is supplied for the original image be embedded into the image as a means to return to the original at some point in the future.
You mention using ImageMagick. This application does offer the ability to retain Image Metadata (at least IPTC Information Interchange Model types stored in a binary header). The other popular application GD does not have this feature, however, Laura Cotterman has provided a set of free functions that will work with GD and provide a means to preserve the metadata when resizing, watermarking, etc. You can find those on her
"Image Metadata" website if you are interested.
Hope that helps, and thanks for making the appropriate changes.
David
--
Stock Artists Alliance Photo Metadata Project leader
http://www.stockartistsalliance.org/photometadata-projectChairman, SAA Imaging Technology Standards Committee