From: "Mike Taylor" <mike miketaylor.org.uk>
> I can't _believe_ there isn't a The One Right Way to
do this very
> simple thing. Can it really be that this requirement
hasn't cropped
> up again and again and again?
I'd say it depends on how you frame the requirement. If
it's "include a link
to a thumbnail", then you're probably right, there
isn't a universal
solution. But I think "include a link to a
thumbnail" is too narrow a
requirement. I believe that a library/metadata perspective
would suggest
generalizing the requirement to "include an
indication of what a link
accesses", the "indication" being a term
from a controlled vocabulary (which
would include "thumbnail").
In other words, add an optional attribute to <link>,
for example, <link
access="thumbnail">.
This, I feel safe to say, would be the approach favored by
the digital
library/metadata community. It is the approach taken with
the MODS metadata
initiative (see http://www.loc.gov
/standards/mods/). MODS defines such an
attribute, "access", and there is a starter
vocabulary, not yet
well-developed, but the Library of Congress is committed to
supporting and
maintaining a controlled vocabulary for this purpose. So
you could say:
<link mods:access="thumbnail">
--Ray Denenberg
=== [ Opensearch.org Discuss mailing list ]
=========================
http:
//opensearch.org/mailman/listinfo/discuss/
Unsubscribe on the web page, or discuss-unsubscribe opensearch.org
Problems? Reach a human at mailman-admin opensearch.org
|