Thanks Pete,
The DC-Lib definition for Location is:
"Identifies the organization holding the resource or from which access
is obtained"
The DC-Lib Comment is:
"Use for a physical location that allows the user to retrieve the item
when a URI is not appropriate (e.g. for physical items not available
electronically). This also facilitates access if the URI doesn't
retrieve anything or only a poor substitute. Can also contain further
identification within a location such as call number, accession
number."
The term seems to be included for physical access reasons and we
therefore *do* want to talk about the place/repository as defined in
the Heaney model. The distinction between the organisation and the
location does become blurred because the value for the term could be the
name and address of the holding organisation or an organisation code
with other details recorded in the metadata related to the code.
Robina
-----Original Message-----
From: DC-Libraries Working Group [mailto:[log in to unmask]] On
Behalf Of Pete Johnston
Sent: 26 April 2006 17:41
To: [log in to unmask]
Subject: Re: Progressing DC-Lib and MODS
Clayphan, Robina wrote:
> If we are to look for an alternative there are three terms to make
> some decisions about: dateCaptured, edition and location. The most
> obvious alternative solution is to try and identify the terms we
> require from other namespaces that share the same model. As a
> starting point Ann has suggested using the term "isLocatedAt",
proposed by the Collection
> Description WG [4], instead of "location". This term refines
> dc:relation and the definition given in the CDAP is "A location of the
> resource".
Which even if I say so myself is, umm, a bit thin on the detail ;-)
> This does not seem to conflict with the requirement of DC-Lib, which
> is to identify the organization holding the resource [5].
Actually, I think an organisation and a location are quite different
things!
The use of isLocatedAt in the DC CD AP is based on the Is-Located-In
relation in Mike Heaney's Analytical Model of Collections and their
Catalogues [1] where he notes very clearly
===
The place (identified physically or electronically) where a Collection
is held.
Note: It is important to distinguish between the place and the
institution responsible for the place; the latter is represented in this
model by the term Administrator.
===
So the value of the proposed isLocatedAt property is intended to be a
"place", not an organisation (an Agent).
In general conversation we tend to blur the distinction between, say,
the University of Bath Library as the organisation (Agent) and the
University of Bath Library as place/repository/building (Location). And
in some application data models too, the distinction may not be worth
making, but in the Heaney model it is made, and the DC CD AP is intended
to reflect that.
Of course, it may be that in DC-Lib, you really _do_ want to talk about
the "place"/repository etc, rather than the organisation, in which case
the property would (probably) become a candidate for your requirements.
But, N.B., the DC CD property is currently only a suggested term (and as
you highlight, not a terribly well documented one!)
Pete
--
Pete Johnston
Research Officer (Interoperability)
UKOLN, University of Bath, Bath BA2 7AY, UK
tel: +44 (0)1225 383619 fax: +44 (0)1225 386838
mailto:[log in to unmask]
http://www.ukoln.ac.uk/ukoln/staff/p.johnston/
**************************************************************************
Experience the British Library online at www.bl.uk
Help the British Library conserve the world's knowledge. Adopt a Book. www.bl.uk/adoptabook
The Library's St Pancras site is WiFi - enabled
**************************************************************************
The information contained in this e-mail is confidential and may be legally privileged. It is intended for the addressee(s) only. If you are not the intended recipient, please delete this e-mail and notify the [log in to unmask] : The contents of this e-mail must not be disclosed or copied without the sender's consent.
The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of the British Library. The British Library does not take any responsibility for the views of the author.
**************************************************************************
|