Re: HTML Metadata for other Web objects

Andrew's idea seems like a pretty reasonable bird in the hand,
though I haven't looked at it in detail.  Pics-se and pics-ng
may be birds in the bush worth catching.  After all, DC is
meant to be expressible in a variety of syntaxes.


Date: Tue, 22 Apr 1997 17:19:01 -0700 (PDT)
From: Andrew Daviel <>
Subject: HTML Metadata for other Web objects

We need a consensus on how to specify metadata for non-HTML Web objects, 

The "search engine" META tags are in widespread use, and most people 
know how to use them, viz.
<meta name="description" content="object description here"> 
<meta name="keywords" content="various keywords here">

The Dublin Core set ( 
defines a set of standard media-independant elements which may
be applied to HTML documents, and the simple elements "Author" and 
"Copyright" are also in common use.

These all apply to the document that they are embedded in.

There is a need to index non-HTML objects which have no
well-defined metadata facility, and also non-text 
objects. These  include audio and video files, PostScript or PDF 
documents, executable binaries, and data sets.

It might be possible to include metadata in HTTP headers, but people seem 
reluctant to bulk the headers doing this, and much of the linking ability 
is lost.
suggests a META relationship for the LINK tag, as in 
<LINK REL=META HREF="metadata.html"> for a forward relationship and
<LINK REV=META HREF="blossom.gif"> for a reverse relationship.

The Dublin Core element IDENTIFIER may also be used, perhaps in the form
<meta name="dc.identifier" scheme=URL 
 content="">, though it may be used for other 
purposes, such as ISBN, ISSN, UPC etc. and has no concept of relative URLs

I propose:

  That the reverse META relationship in an HTML header be used to indicate
  that metainformation in the current document
  applies to the referenced object, not the current document itself.

  That the forward META relationship in HTTP (RFC 2068- be 
  optionally used to indicate the existance of metainformation 
  pertaining to a non-text object.

  That the reverse META relationship in HTTP be optionally used 
  in an identical fashion to the reverse META relationship in HTML.

Example - the metadata:

  HTTP/1.0 200 OK
  Content-type: text/html
  Link: <>; rev="meta"

  <html><head><title>Apple Blossoms</title>
  <LINK REV=META HREF="blossom.gif">
  <meta name="dc.title" content="Apple Blossoms">
  <meta name="dc.description" content="Apple Blossoms in Springtime">
  <meta name="dc.creator" content="Ann Photog">
  <meta name="dc.identifier" scheme="url" 
  <meta name="copyright" content="Ann Photog, 1997">
  (<a href="blossom.gif">here's the photo</a>)

and the object:

  HTTP/1.0 200 OK
  Content-type: image/gif
  Link: <>; rel="meta"

  GIF89a etc. etc.

This would require that discovery agents such as Web robots and spiders 
associate the metainformation with the correct object, listing e.g.

  <a href="">Apple Blossoms</a>
  &quot;Apple Blossoms in Springtime&quot;; Creator: Ann Photog

rather than

  <a href="">Apple Blossoms</a>

and optionally follow the HTTP Link header to discover metainformation
when traversing the original object (blossom.gif).

Perhaps an empty HREF field 
  <LINK REV=META HREF=""> could be used to signify that the metadata 
pertains to an offline object, such as a book or statue  (which may 
have a valid non-URL DC.IDENTIFIER element) ...

Andrew Daviel 
TRIUMF & Vancouver Webpages

Received on Wednesday, 23 April 1997 09:31:17 UTC