[OAI-implementers] Qualified Dublin Core

[Simeon Warner]

I think the problem with "standard elements in any wrapper" approach is
that a harvester has no easy way to know up-front what it might be getting
if it harvests records in a particular format. Harvesting a metadata
format understood to be "only QDC elements" (nothing else, no funny
business) gives rather more assurance of intelligibility to a harvester
that understands QDC. A canonical schema seems the simplest way to
indicate this (notwithstanding versioning issues mentioned earlier by
Pete Johnston).

Cheers,
Simeon

On Mon, 9 Aug 2004, Timothy W. Cole wrote:
> Jeff-
>
> My take is that OAI shouldn't want to get back in business of hosting
> schemas or namespaces for metadata formats. We went to some trouble to get
> away from that when transitioning from 1.1 to 2.0. A blessed application
> namespaces for qualified DC should be left up to the DCMI.
>
> While DCMI decides how they want to handle things (and I know they won't be
> quick), solutions like the one at CCLRC (we've done much the same here for a
> couple of projects) and NSDL are fine. Any namespace-aware OAI application
> should ignore the locally created namespace and hone in on the dc, dcterms,
> and dcmitype namespaces and thereby be able to use those elements without
> any problems. If your OAI service provider respects namespaces, it shouldn't
> matter what namespace the container element is in -- that's why the XML
> Schemas posted on the DCMI Website were done that way.
>
> Isn't that good enough for harvesting purposes? Are am I missing a subtle
> consideration that requires a canonical namespace for the container element?
>
> Tim Cole
> University of Illinois at UC
>
> -----Original Message-----
> From: oai-implementers-bounces at openarchives.org
> [mailto:oai-implementers-bounces at openarchives.org] On Behalf Of Young,Jeff
> Sent: Monday, August 09, 2004 10:33 AM
> To: Mascord, M (Matthew) ; Young,Jeff;
> oai-implementers at oaisrv.nsdl.cornell.edu
> Cc: LeVan,Ralph; Hickey,Thom
> Subject: RE: [OAI-implementers] Qualified Dublin Core
>
> Yes, this is the problem. Now I have two to choose from. This one, and the
> one created by NSDL. I'm sure there are others out there. For the sake of
> interoperability, it seems to me that the OAI community should bless (and
> host?) such an "application profile" schema.
>
> Jeff
>
> > -----Original Message-----
> > From: Mascord, M (Matthew) [mailto:M.Mascord at rl.ac.uk]
> > Sent: Monday, August 09, 2004 11:21 AM
> > To: 'Young,Jeff'; oai-implementers at oaisrv.nsdl.cornell.edu
> > Cc: LeVan,Ralph; Hickey,Thom
> > Subject: RE: [OAI-implementers] Qualified Dublin Core
> >
> > Hi -
> >
> > I am the developer of an OAI compatible institutional repository for
> > the UK research council CCLRC.  The URL is http://epubs.cclrc.ac.uk.
> > We are attempting to capture & make publicly accessible any scientific
> > research that has benefitted from the use of CCLRC's facilities or
> > expertise.  We recently went live on the OAI repository network:
> > http://epubs.cclrc.ac.uk/oai?verb=Identify.
> >
> > We provide metadata in both Simple and Qualified Dublin Core but had
> > the same problem as you in finding an authoritative XML schema for
> > Qualified Dublin Core.  In the end we created our own that includes
> > the schema defined at
> > http://dublincore.org/schemas/xmls/qdc/2003/04/02/qualifieddc.xsd and
> > described in the Dublin Core Note at
> > http://dublincore.org/schemas/xmls/qdc/2003/04/02/notes/.  This
> > defines a container element into which elements from the dcterms and
> > dc namespaces may be placed.
> >
> > I'm not sure if this is the best approach so would appreciate any
> > feedback on this.  Our OAI implementation can be tested at
> > http://epubs.cclrc.ac.uk/oaitest.
> >
> > Kind Regards,
> > Matthew Mascord
> > e-Library Software Developer, CCLRC, UK
> >
> >
> > > -----Original Message-----
> > > From: oai-implementers-bounces at openarchives.org
> > > [mailto:oai-implementers-bounces at openarchives.org]On Behalf Of
> > > Young,Jeff
> > > Sent: 09 August 2004 16:03
> > > To: oai-implementers at oaisrv.nsdl.cornell.edu
> > > Cc: LeVan,Ralph; Hickey,Thom
> > > Subject: [OAI-implementers] Qualified Dublin Core
> > >
> > >
> > > I'm looking for an XML Schema for Qualified Dublin Core for use in
> > > OAI repositories. I poked around the UIUC OAI Registry, but all I
> > > found was a couple of ad hoc schemas used by repositories that
> > > appear to be defunct.
> > > Ideally, though, the existence and use of such a schema should be
> > > shared across a broad community and not ad hoc.
> > >
> > > Next, I searched in Google and OAForum but all I found was a
> > > reference to a preliminary effort to establish such a schema
> > > (http://www.ukoln.ac.uk/metadata/dcmi/xmlschema/). This particular
> > > document discusses a sample application schema for a DCQ container,
> > > but the implication is that the final schema must be decided by the
> > > specific application (e.g OAI?). Apparently, this has never been
> > > done.
> > >
> > > Can someone provide some guidance for doing this?
> > >
> > > Thanks.
> > >
> > > Jeff
> > >
> > > ---
> > > Jeffrey A. Young
> > > Software Architect
> > > Office of Research, Mail Code 710
> > > OCLC Online Computer Library Center, Inc.
> > > 6565 Frantz Rd.
> > > Dublin, OH 43017-3395
> > > www.oclc.org
> > >
> > > Voice: 614-764-4342
> > > Voice: 800-848-5878, ext. 4342
> > > Fax: 614-718-7477
> > > Email: jyoung at oclc.org
> > >
> > > _______________________________________________
> > > OAI-implementers mailing list
> > > List information, archives, preferences and to unsubscribe:
> > > http://openarchives.org/mailman/listinfo/oai-implementers
> > >
>
> _______________________________________________
> OAI-implementers mailing list
> List information, archives, preferences and to unsubscribe:
> http://openarchives.org/mailman/listinfo/oai-implementers
>
>
> _______________________________________________
> OAI-implementers mailing list
> List information, archives, preferences and to unsubscribe:
> http://openarchives.org/mailman/listinfo/oai-implementers
>