On Wed, 1 Oct 1997, Andrew Prout wrote:
> The date element contains the [main] date of the resource, I am
> happy with this very loose definition of what the date of the
> resource is, but a rule of thumb would be that the resource being
> described is likely only to have one date or one range of dates. ie
> the date of the Empire State Building is 1929, the date of DC5 is Oct
> 1997, the date of this Email is 1 Oct 1997 etc etc. Date can only be
> qualified if the qualification does not change the definition above.
>
> The result of this for the searcher would be that a search on a date
> or range of dates would retrieve a relatively sensible result.
>
my $0.02:
In a search I would probably be interested in the date something was
written, or at least revised, rather than when it was reprinted,
translated, or had it's background colour changed. So if
I wanted to know about (recent) high-performance computers and said
"date >1996", I wouldn't want a recently-webified article about the
Colossus codebreaker (WWII). In HTML (well, HTTP) one can find out when
the background colour was changed (!) by looking at "Last-Modified" ...
Andrew
|