On Mon, 5 Sep 2005, Andrew Wilson wrote:
> But dcterms:valid is for the temporal validity of the resource, not the
> content ("Date (often a range) of validity of a resource."),
But I don't understand how 'temporal validity of the resource' can mean
anything other than "temporal validity of the content of the resource"?
I.e. a bus timetable is valid for a certain period because its content is
only correct for that period.
Can you give me an example where 'date valid' doesn't hasve something to
do with the content of the resource?
A bus ticket perhaps?
> even though its
> possible that in some cases the same date could be valid for dcterms:valid
> and dcterms:temporal. But that doesn't mean the semantics overlap, or that
> the properties are related. I'm not sure why you say that the temporal scope
> of the content includes the temporal validity of the resource (the current
> definition of dcterms:temporal says: "Temporal characteristics of the
> intellectual content of the resource.")? The content is *not* the resource.
The definition of dcterms:temporal does limit it to the content of the
resource, I agree. Unfortunately, the definition of coverage (as it
currently stands) is not so specific.
Andy
--
Distributed Systems, UKOLN, University of Bath, Bath, BA2 7AY, UK
http://www.ukoln.ac.uk/ukoln/staff/a.powell
tel: +44 1225 383933 msn: [log in to unmask]
Resource Discovery Network http://www.rdn.ac.uk/
|