Hi Neil,
On Fri, Apr 17, 2009 at 07:29:43PM +0800, Neil Godfrey wrote:
> I had always understood pure OAI_DC (as per OAI-PMH implementation
> guidelines) to refer specifically to any of the 15 properties from
> http://purl.org/dc/elements/1.1/ and
> http://www.openarchives.org/OAI/2.0/oai_dc.xsd
>
> How is OAI_DC affected by the relegation of the dc: namespace to legacy, and
> its preferred replacement for rdf purposes by dcterms and its related 55
> properties?
Thank you for the questions!
The /elements/1.1/ elements are called "legacy" because they came
first, but they have not been "deprecated" and are indeed still
widely used.
OAI_DC is an XML schema. The difference between elements from
/elements/1.1/ and elements from http://purl.org/dc/terms/
becomes relevant only if OAI_DC metadata is translated into RDF.
The latter are sub-properties of the former, and a DC-aware
application can handle both.
> Related, if an application profile avoids the use of "date" and uses only
> "modified", "issued" etc, then how does that impact OAI_DC?
The protocol OAI-PMH can be used to exchange not only OAI_DC
metadata, but metadata created with application profiles.
If metadata based on the (more precise) application profile
translated into the (simpler) OAI_DC form, there would be some
loss of precision as the "issued" and "modified" dates were
merged into one generic "date".
Tom
--
Thomas Baker <[log in to unmask]>
|