I agree with many of the comments in Diane Hillman's message although I'm
not sure whether it is a good idea to eliminate leading articles from
titles.  This seems to me to be a global problem that needs to be addressed
at the application end, not by compromising the data.

With regard to holdings, Diane says:

> Including Holdings in here boggles my mind--how does this relate to the
> discovery of the resource, or any of the possible uses described in this
> document?  This seems so far outside the scope of the other elements that
> I
> question its presence at all.  Surely we are not trying to recreate
> bibliographic utilities with DC?
>
A key use for DC in library and related applications must be to enable the
delivery of hybrid library services : services that enable searching across
a range of collections for resources regardless of format.  One obvious area
of application for libraries and related systems is provided for in the
Cross Domain Functional Area of the Z39.50 Bath Profile. Conformance to this
functional area currently requires support for presentation of records in
unqualified DC.

Location is probably a more user-centric term than holding:  Information
providers hold resources;  information users locate them!  I would like to
recommend that Location be encoded in the Library Application Profile as a
qualifier of Identifier so that holdings information can flow through in an
unqualified DC record via, say, a Z39.50 transaction, as just another
identifier.

Judith Pearce
Director, Web Services
National Library of Australia
CANBERRA  ACT  2601
Australia

Phone:  +61 2 62621425
Fax:  +61 2 6273 3648
Email: [log in to unmask]
NLA Web Site:  http://www.nla.gov.au