Mapping JERM to Dublin Core Terms

[stain]

Partial fix for #2

http://dublincore.org/documents/dcmi-terms/
http://purl.org/dc/terms/

I've included rdfs:isDefinedBy http://purl.org/dc/terms/ annotations for each of the cited terms - avoiding an OWL import of the full http://purl.org/dc/terms/

Property equivalence

• jerm:title == dcterms:title
• jerm:description == dcterms:description
• jerm:identifier == dcterms:identifier
• jerm:hasPart == dcterms:hasPart
• jerm:isPartOf == dcterms:isPartOf

(The above would make SEEK's output using dcterms conform to the JERM ontology)

Subproperties

Typically because the JERM properties have more specific domains/ranges:

• jerm:hasCreator < dcterms:creator
• jerm:hasContributor < dcterms:contributor
• jerm:hasFormat < dcterms:format

Disjoint properties

Some similarly named properties which are not compatible are marked as such:

• jerm:hasFormat != dcterms:hasFormat
• jerm:isFormatOf != dcterms:isFormatOf

(See http://dublincore.org/documents/dcmi-terms/#terms-hasFormat - both of these point to "A related resource that is substantially the same as the pre-existing described resource, but in another format." rather than the class-like "file format" resource)

Date properties

These date properties are subproperties of dct:date

• jerm:dateOfDeath
• jerm:donationDate
• jerm:samplingDate

Subclasses

DC Terms does not have many relevant classes as it focuses on the bibliography aspects, but I've mapped:

• jerm:Person < dct:Agent
• jerm:Protocol < dct:MethodOfInstruction
• jerm:Format < dct:FileFormat (might be equivalent?)
• jerm:Material_entity < dct:PhysicalResource (might be equivalent?)

Questions

Note that from JERM we already have the confusing jerm:Software < jerm:Equipment < jerm:Material_entity which then now would also become a dct:PhysicalResource - but the software might not be on a floppy! :)