[OAI-implementers] rdf

[Tim Brody]

On Mon, 30 Apr 2001, Eric Lease Morgan wrote:

> <?xml version="1.0"?>
> <GetRecord xmlns="http://www.openarchives.org/OAI/1.0/OAI_GetRecord"
>  xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
>  xsi:schemaLocation="http://www.openarchives.org/OAI/1.0/OAI_GetRecord
>  http://www.openarchives.org/OAI/1.0/OAI_GetRecord.xsd">
>  <responseDate>2001-04-30T07:24:56-7:00</responseDate>
>  <requestURL>http://www.infomotio...30-44</requestURL>
>  <record>
>   <header>
>    <identifier>twain-30-44</identifier>
>    <datestamp>1999</datestamp>
>   </header>
>   <metadata>
>    <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>     xmlns:dc="http://purl.org/dc/elements/1.1/"
>     xmlns:alex="http://bliss.lib.ncsu.edu/xml/rdf/alex-01-rdf-ns#">
>     <rdf:Description rdf:about="http://www....erature/am...44.txt">
>      <dc:identifier>twain-30-44</dc:identifier>
>      <dc:creator>Twain, Mark</dc:creator>
>      <dc:title>$30,000 Bequest And Other Stories, The</dc:title>
>      <dc:source rdf:resource="gopher://.../Classic/bequest.mt" />
>      <dc:format>text/plain</dc:format>
>      <dc:publisher>Project Gutenburg</dc:publisher>
>      <dc:type>text</dc:type>
>      <dc:language>en-US</dc:language>
>      <dc:rights>This document in the the Public Domain.</dc:rights>
>      <alex:hasIndex rdf:resource="http://ww...sDatabase=twain-30-44" />
>      <alex:hasConcordance rdf:resource="ht..nce&amp;bookcode=twain-30-44" />
>      <alex:makeEbook rdf:resource="http://www.info...andle=twain-30-44" />
>      <alex:makePDF rdf:resource="h...cgi-bin/pdf.pl?handle=twain-30-44" />
>      <dc:relation rdf:resource="http://www.infomotions.com/alex/" />
>     </rdf:Description>
>    </rdf:RDF>
>   </metadata>
>  </record>
> </GetRecord>

Not an answer to your question but a query, I believe DC describes
"identifier" as an unambiguous reference to the article, for example a
URL. With service-provider hat on I would rather be provided with a
complete URL (which I can then pass onto users), than something that must
be derived.

With that in mind couldn't rdf:resource* be put in dc:identifier, and
those particular fields dropped?

(I don't know whether "hasIndex" and other fields could be encapsulated
within a DC attribute?)

I have come to the conclusion that anything can be represented by DC
somewhere, its just a question of how much context you're prepared to
loose!

All the best,
Tim Brody