On Thu, 24 Jul 1997, Jon Knight wrote:
[... sensible stuff snipped...]
> job with non-DLOs. That's why you don't see people pushing DC for
> describing people; people aren't DLOs and the metadata you want about
> people resources (ie white pages databases) is considerably different.
What about CVs though? For my sins I'm involved with a project
that will include a database of both CVs and job adverts for Social
Science researchers. On the face of it these are both classic DLOs, but
the former is also straying into white-pages territory.
Searching for document-like-objects of type 'curriculum vitae' or 'job
vacancy' seems, on the face of it, a reasonable thing to do. In the case
of the former, the CV, as a DLO, stands in proxy for the thing
ultimately being described and/or searched for (ie. the person).
DC -> CV -> person. This is OK but limited: the contents of the Dublin
Core record does not describe the person, it describes a description of
the person. So all the DC fields are about the CV not the person; in some
cases these will often intersect (eg. author, subject) which makes it
easy to forget that the DC is itself describing a description...
This is a specific case of a general problem: for more or less any
non-DLO (people, jobs, houses, museum artifacts, databases, whatever...)
it is often useful to have a DLO describing that resource. (eg. CVs,
job description, catalogue records, photographs of artifacts). And once
we've got a class of DLOs for talking about that kind of non-DLO, there's
a need to represent them in Dublin Core. Which is maybe why people
sometimes seem to be using DC for everything...
Dan
--
[log in to unmask] tel: +44(0)117 9288478
Biz/ed Technical Officer http://www.bized.ac.uk/
Institute for Learning and Research Technology http://www.ilrt.bris.ac.uk/
University of Bristol, Bristol BS8 1TN, UK. fax: +44(0)117 9288473
|