On Thu, 30 Oct 1997, Dirk-Willem van Gulik wrote:
> NOT Keyword: water, artic, algea (three elements)
> NOT Date.1.min: 1997-01-01 (half element)
> NOT Date.1.max: 1997-01-04 (half element)
>
> but Keyword: water
> Keyword: artic
> Keyword: algea
> Date: 1997-01-01 1997-01-05
"Keywords" is firmly embedded in the webhead psyche as e.g.
"sex,drugs,violence" etc. The DC equivalent is I believe "Subject"
which can contain multiple keywords.
On balance, I agree with Andrew Layman. IMO, most new work is going to
have one date (at least on the 1:1 principle) and the creator will know
what it is. I would think that most people would put either the date they
started writing, or the date they stopped and "published" to the Web,
which may well be the same.
One thing I think's important with Date (and Coverage) is that one should
be able to do arithmnetic with the values. This is simpler if
the value of the element can be reduced to a single real number (e.g. Unix
time, or Julian day number). So I'd prefer DC.Date as a single ISO value,
with DC.Date.max (DC:DateMax), min as recognized subelements.
Andrew Daviel
|