I think the intention was to use Coverage instead of Subject when a
geographic subject is used. I am not sure that this is the right approach,
but the problem is distinguishing between a geographic subject and spatial
coverage. When is a geographic name considered subject and when
coverage? Coverage is defined as:

Coverage
Definition: The extent or scope of the content of the resource.
Comment:     Coverage will typically include spatial location (a place
name or geographic coordinates), temporal period (a period label, date, or
date range) or jurisdiction (such as a named administrative entity).
Recommended best practice is to select a value from a controlled vocabulary (for example, the Thesaurus of
Geographic Names [TGN]) and that, where appropriate, named places or
time periods be used in preference to numeric identifiers such
as sets of coordinates or date ranges.

Coverage.Spatial is defined as:
Definition: Spatial characteristics of the intellectual content of the
resource.

We know we should use Coverage for coordinates, but what about a
geographic name? Does someone have a proposal? Subject is "the topic of
the content of the resource". I find it difficult to see when a geographic
name would be used in Coverage that is not the topic of the resource
without making such fine distinctions that they would be hard to apply.

So if we can come up with a distinction between when you use a geographic
name as Subject and when as Coverage we can explain it in DC-Lib AP. (And
then we will get another element done-- or at least partially!)

Rebecca


On Thu, 20 Dec 2001, Clayphan, Robina wrote:

> 3) Other comment.
> The comment about using Coverage for recording "a geographical aspect" does
> not seem to be sufficient to explain its usage.  It seems to suggest using
> Coverage instead of Subject which I don't think is the intention.  If I have
> understood the suggested use of Coverage correctly, perhaps the DC-Lib
> Comment could be extended to explain that a value in Coverage would probably
> be in addition to the value in Subject and contain a value from a coded
> scheme.
>
> Regards,
> Robina
>
>
>
>
>
> *********************************************************************
> 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.
> *********************************************************************
>