[OAI-implementers] XML records and RDF

Thu, 7 Mar 2002 07:38:21 -0500

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1C5D4.F6F7AB08
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Alan,=20
=20
Mathew's response is pretty complete.  To restate in slightly different =
language: the OAI-PMH mandates a very simple and basic DC syntax for the =
purpose of a lingua franca amongst all data providers.  The protocol =
allows (and encourages, if a protocol can do such!) data providers to =
provide parallel forms of metadata that are more expressive than the =
required dc format.
=20
Carl
=20
Department of Computer Science
Cornell University
Ithaca, NY 14853 USA
Voice: +1-607-255-6046
FAX: +1-607-255-4428
EMail: lagoze@cs.cornell.edu
WWW: http://www.cs.cornell.edu/lagoze=20

-----Original Message-----
From: Paxinos, Mathew M [mailto:paxinos.mathew.m@edumail.vic.gov.au]
Sent: Wednesday, March 06, 2002 11:59 PM
To: 'Alan Kent'; OAI Implementors
Subject: RE: [OAI-implementers] XML records and RDF

Alan,=20

My interpretation of the schema was that you can provide the records in =
whatever format you wish, it could conform to the DC schema as outlined =
in the OAI 1.1 spec, or you could specify your own.  The OAI 1.1 only =
specified that you must provide an instance of your data using the DC =
schema.

Our system provides records in DC as per the schema for general =
consumption or using our own VEMS standard, which provides the same =
information but with more descriptive detail as to what things are.  The =
ListMetadataFormats verb provides a list of the schemas that the =
repository can provide the data in.

Regards,=20

Mathew Paxinos=20
System Developer=20
Victorian Education Channel=20
Department of Education & Training=20
Phone: (03) 9637 2256=20
www.education.vic.gov.au=20
 =20

-----Original Message-----=20
From: Alan Kent [ mailto:ajk@mds.rmit.edu.au]=20
Sent: Thursday, 7 March 2002 14:17=20
To: OAI Implementors=20
Subject: [OAI-implementers] XML records and RDF=20

I was looking at the feasibility of putting up a collection of=20
records using a scheme which is an extension of Dublin Core. However,=20
they have encoded the records using RDF rather than the simpler=20
OAI schema as used for Dublin Core records. (ie: lots of=20
<rdf:description> and <rdf:value> elements all over the place.)=20

The DC records included in appendex of the OAI 1.1 spec however=20
does not use RDF.=20

Just wondering if there was any reason for me not to return my=20
records using the RDF based schema? I could try and convert them=20
to the OAI DC schema as well (so available in both formats).=20
Just wondering if there was any wisdom here. (Eg: "we chose not=20
to use RDF based DC XML because...").=20

I am not an RDF expert by the way, so don't understand all the=20
subtlties that may be involved.=20

Alan=20
--=20
Alan Kent ( mailto:ajk@mds.rmit.edu.au, http://www.mds.rmit.edu.au)=20
Postal: Multimedia Database Systems, RMIT, GPO Box 2476V, Melbourne =
3001.=20
Where: RMIT MDS, Bld 91, Level 3, 110 Victoria St, Carlton 3053, VIC =
Australia.=20
Phone: +61 3 9925 4114  Reception: +61 3 9925 4099  Fax: +61 3 9925 4098 =

_______________________________________________=20
OAI-implementers mailing list=20
OAI-implementers@oaisrv.nsdl.cornell.edu=20
http://oaisrv.nsdl.cornell.edu/mailman/listinfo/oai-implementers=20

*************************************************************************=
******=20
Important - This email and any attachments may be confidential. If =
received in error, please contact us and delete all copies. Before =
opening or using attachments check them for viruses and defects. =
Regardless of any loss, damage or consequence, whether caused by the =
negligence of the sender or not, resulting directly or indirectly from =
the use of any attached files our liability is limited to resupplying =
any affected attachments. Any representations or opinions expressed are =
those of the individual sender, and not necessarily those of the =
Department of Education Employment and Training.

------_=_NextPart_001_01C1C5D4.F6F7AB08
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>RE: [OAI-implementers] XML records and RDF</TITLE>

<META content=3D"MSHTML 6.00.2713.1100" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D306333512-07032002><FONT color=3D#0000ff =
size=3D2>Alan,=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D306333512-07032002><FONT color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D306333512-07032002><FONT color=3D#0000ff =
size=3D2>Mathew's response=20
is pretty complete.&nbsp; To restate in slightly different language: the =
OAI-PMH=20
mandates a very simple and basic DC syntax for the purpose of a lingua =
franca=20
amongst all data providers.&nbsp; The protocol allows (and encourages, =
if a=20
protocol can do such!) data providers to provide parallel forms of =
metadata that=20
are more expressive than the required dc format.</FONT></SPAN></DIV>
<DIV><SPAN class=3D306333512-07032002><FONT color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D306333512-07032002><FONT color=3D#0000ff=20
size=3D2>Carl</FONT></SPAN></DIV>
<DIV><SPAN class=3D306333512-07032002><FONT color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D306333512-07032002>
<P><FONT size=3D2>Department of Computer Science<BR>Cornell =
University<BR>Ithaca,=20
NY 14853 USA<BR>Voice: +1-607-255-6046<BR>FAX: +1-607-255-4428<BR>EMail: =

lagoze@cs.cornell.edu<BR>WWW: <A =
href=3D"http://www.cs.cornell.edu/lagoze"=20
target=3D_blank>http://www.cs.cornell.edu/lagoze</A> =
</FONT></P></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Paxinos, Mathew M=20
  [mailto:paxinos.mathew.m@edumail.vic.gov.au]<BR><B>Sent:</B> =
Wednesday, March=20
  06, 2002 11:59 PM<BR><B>To:</B> 'Alan Kent'; OAI=20
  Implementors<BR><B>Subject:</B> RE: [OAI-implementers] XML records and =

RDF </DIV>
 Alan, 
 My interpretation of the schema was that you can =
provide the=20
 records in whatever format you wish, it could conform to the DC schema =
as=20
 outlined in the OAI 1.1 spec, or you could specify your own.&nbsp; The =
OAI 1.1=20
 only specified that you must provide an instance of your data using =
the DC=20
 schema.
 Our system provides records in DC as per the schema =
for=20
 general consumption or using our own VEMS standard, which provides the =
same=20
 information but with more descriptive detail as to what things =
are.&nbsp; The=20
 ListMetadataFormats verb provides a list of the schemas that the =
repository=20
 can provide the data in.
 Regards, 
 Mathew Paxinos System =
Developer=20
 Victorian Education Channel <FONT=20
 size=3D2>Department of Education &amp; Training Phone:=20
 (03) 9637 2256 www.education.vic.gov.au=20
 &nbsp; 
 -----Original Message----- From: Alan=20
 Kent [<A =
href=3D"mailto:ajk@mds.rmit.edu.au">mailto:ajk@mds.rmit.edu.au</A>]=20
 Sent: Thursday, 7 March 2002 14:17 =
 <FONT=20
 size=3D2>To: OAI Implementors Subject:=20
 [OAI-implementers] XML records and RDF 
 I was looking at the feasibility of putting up a =
collection=20
 of records using a scheme which is an =
extension of=20
 Dublin Core. However, they have encoded the =
records=20
 using RDF rather than the simpler OAI schema =
as used=20
 for Dublin Core records. (ie: lots of <FONT=20
 size=3D2>&lt;rdf:description&gt; and &lt;rdf:value&gt; elements all =
over the=20
 place.) 
 The DC records included in appendex of the OAI 1.1 =
spec=20
 however does not use RDF. 
 Just wondering if there was any reason for me not to =
return=20
 my records using the RDF based schema? I =
could try and=20
 convert them to the OAI DC schema as well =
(so=20
 available in both formats). Just wondering =
if there=20
 was any wisdom here. (Eg: "we chose not to =
use RDF=20
 based DC XML because..."). 
 I am not an RDF expert by the way, so don't =
understand all=20
 the subtlties that may be involved. =

 Alan -- Alan=20
 Kent (<A =
href=3D"mailto:ajk@mds.rmit.edu.au">mailto:ajk@mds.rmit.edu.au</A>, <A=20
 href=3D"http://www.mds.rmit.edu.au"=20
 target=3D_blank>http://www.mds.rmit.edu.au</A>) Postal:=20
 Multimedia Database Systems, RMIT, GPO Box 2476V, Melbourne =
3001.=20
 Where: RMIT MDS, Bld 91, Level 3, 110 Victoria St, =
Carlton=20
 3053, VIC Australia. Phone: +61 3 9925 =
4114&nbsp;=20
 Reception: +61 3 9925 4099&nbsp; Fax: +61 3 9925 4098 <FONT =

size=3D2>_______________________________________________ =
 <FONT=20
 size=3D2>OAI-implementers mailing list <FONT=20
 size=3D2>OAI-implementers@oaisrv.nsdl.cornell.edu <A=20
 =
href=3D"http://oaisrv.nsdl.cornell.edu/mailman/listinfo/oai-implementers"=
=20
 =
target=3D_blank>http://oaisrv.nsdl.cornell.edu/mailman/listinfo/oai-imple=
menters</A>=20
 
 <FONT=20
 =
size=3D2>****************************************************************=
***************=20
 Important - This email =
and any=20
 attachments may be confidential. If received in error, please contact =
us and=20
 delete all copies. Before opening or using attachments check them for =
viruses=20
 and defects. Regardless of any loss, damage or consequence, whether =
caused by=20
 the negligence of the sender or not, resulting directly or indirectly =
from the=20
 use of any attached files our liability is limited to resupplying any =
affected=20
 attachments. Any representations or opinions expressed are those of =
the=20
 individual sender, and not necessarily those of the Department of =
Education=20
 Employment and Training.</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1C5D4.F6F7AB08--