Hi Cliff and Ann,
Just an idea, but you could consider DCMES as a starting point. You needn't
limit yourself to DCMES elements. However, I think DCMES is clear about
creating complex data structures with DCMES names: you shouldn't because it
will not be interoperable.
For example, DCMES does not really support a full address, which would
denote hemisphere. FWIW, the hemisphere thing isn're really a big deal in
this case as it relates more to an issue of a journal than the weather.
E.g. Publisher_Address.Street = 45 Letters Row
Publisher_Address.City = London
Publisher_Address.Country = UK
Publisher_Address.PostalCode = 123 HK2
Periodical.Date = 20000319
Periodical.Volume = 1
Periodical.Issue = 2
Periodical.Season = 21
Also, to settle the issue, you may find it helpful to consider how the data
will be used. Is the season a likely search parameter? Or, is it useful
information about a resource once the catalog record is located? DCMES
conformance is more important for search elements - as the single most
important area of interoperability. Every application will have much more
complex data requirements than DCMES supports. I have noticed DCMES is a
bit lacking for tagging periodicals and other serial publications. If MARC
has season codes, perhaps it has other periodical data items as well.
thinking out loud,
Charles Reitzel
-----Original Message-----
From: Ann Apps [mailto:[log in to unmask]]
Sent: Thursday, December 21, 2000 4:50 AM
To: [log in to unmask]
Subject: Publisher location
>
> Alex Satrapa <[log in to unmask]> wrote:
>
> Some indication of the publisher's geographic location would be
> necessary. This could possibly be done using the meta data record
> describing the publisher (though how you locate this given the sparse
> information in the DC.Publisher field, I'll leave as an excercise for
> the reader :)
>
Strangely I was looking at this very problem yesterday. The country
of publication is supplied in the source data I'm working on as a
separate record field from the the publisher name. I'm trying to write
an XML DTD for this data using Dublin Core for the elements. My
solution was to create a structured value within dc:publisher within
a local namespace (zetoc). So I have:
<dc:publisher>
<zetoc:pnm>My Publishing Co</zetoc:pnm>
<zetoc:country>England</zetoc:country>
</dc:publisher>
This probably indicates which side of the structuralist/minimalist
fence I sit on! This may also break the dumb-down rule, but
because I'm using a local namespace I think I can expect that both
sub-elements would be read together. I can also define within this
local namespace (application profile?) that the country is optional
but the publisher name is mandatory (at least in theory - in practice
real data is never so clean).
As ever, I am taking a pragmatic approach because I have to make
a decision quickly because we are building a real application.
Best wishes,
Ann
--------------------------------------------------------------------------
Mrs. Ann Apps. Electronic Publishing @ MIMAS. Manchester Computing,
University of Manchester, Oxford Road, Manchester, M13 9PL, UK
Tel: +44 (0) 161 275 6039 Fax: +44 (0) 0161 275 6040
Email: [log in to unmask] WWW: http://epub.mimas.ac.uk/ann.html
--------------------------------------------------------------------------
|