[OAI-implementers] XSD file for qualified DC

Ann Apps ann.apps@man.ac.uk
Mon, 24 Jun 2002 13:52:34 GMT1BST

Carl, and All,

On Thu, 20 Jun 2002 Carl Lagoze wrote:

> Turning attention to the citation data issue, I will argue equally
> strongly that slotting these into the dc identifier element is
> inappropriate.  Citation data is implicitely structured whereas dc
> elements should be simply "appropriate literals" as defined by Tom
> Baker.  Playing a syntactic trick and serializing that data into an
> "appropriate literal" through the use of punctuation such as "Library
> and Information Science Research 22(3), 311-338 (2000)" as you suggest
> in http://epub.mimas.ac.uk/DC/citproposal.html, seems ill-advised with
> data that screams out for markup 
> Since this explicit structure is not currently allowed in DC (and I
> question whether it ever should be) and given the fact that OAI-PMH is
> quite happy expressing parallel structured form, it might be time to
> write the schema for such citation data and encourage people to expose
> it for harvesting, and not characterize it as "dublin core".
I think I'm about half way to agreeing with you. This approach does 
require a model which includes parallel metadata formats. So it 
would be OK for OAI, which is what we're talking about on this list.

So we could have a metadata format, say oai-cite (that's not a 
good name! - just something to work with). Then you could encode 
the metadata for a journal article something like as follows. I'm just 
considering the metadata for the article itself, not any references it 
may have - but probably a metadata format for those could be 
incorporated. (Doing this quickly, I've not included any schema 

<cite:atitle>Studying E-journal User Behavior Using Log 
<cite:jtitle>Library and Information Science Research</cite:jtitle>

But this is looking very similar to the OpenURL journal article 
metadata, which leads me to wonder if that can be used here as 
well. The main concern is that this is not a referent (or subject of a 
citation link) but rather an identification by citation metadata, 
unless it's seen as an introverted, self-referential link. Maybe this is 
an OpenURL context-object with a referring-entity but no referent?

To go back to the qualified Dublin Core case, from another email:

> <meta name="DC.Identifier.citation" 
> content="Library and Information Science Research 22(3), 311- 
338 (2000)">
> In that the entity Library and Information Science Research is 
being introduced that "has a" volume "22" and issue # "3". 

This is intended to be an "is a" relation where the entire content of 
this string 'is a' citation, and hence identifier of the article. There is 
no intention to say anything about the journal or issue outside of 
that exact citation. I think this is the same as an OpenURL citation 
where the complete set of metadata within the OpenURL identifies 
a particluar article by its citation. In fact, in OpenURL, different sets 
of metadata elements are used for journal articles (ja) and journal 
issues (ji). It is just coincidence that some of the constituents look 
the same to human readers. 

The document 'Guidelines for implementing Dublin Core in XML' 
http://www.ukoln.ac.uk/metadata/dcmi/dc-xml-guidelines/ includes 
examples of mixing DC metadata within other schemas. So I think 
one could include OpenURL jounal article metadata with a DC 
record (assuming it is alright to use the OpenURL journal article 
schema stand-alone).

For example:

<dc:title>Studying E-journal User Behavior Using Log 
<ja:jtitle>Library and Information Science Research</ja:jtitle>

Best wishes,

Mrs. Ann Apps. Senior Analyst - Research & Development, MIMAS,
     University of Manchester, Oxford Road, Manchester, M13 9PL, UK
Tel: +44 (0) 161 275 6039    Fax: +44 (0) 0161 275 6040
Email: ann.apps@man.ac.uk  WWW: http://epub.mimas.ac.uk/ann.html