by 
0
0
Issues With CIDOC Mapping – CIDOC’s Lack of Namespace URIs
One issue I’ve noticed in trying to map data to CIDOC is that CIDOC doesn’t seem to provide individual namespace URIs for its different classes and properties. Instead, these terms are all stored in a single namespace file: (http://www.cidoc-crm.org/sites/default/files/cidoc_crm_v5.0.4_official_release.rdfs.xml)
Because of this issue, the Smithsonian’s links to CIDOC-CRM term resources come up dead (http://edan.si.edu/saam/id/object/1997.70/acquisition), while the British Museum uses an OWL-based CIDOC mapping that just downloads the entire ontology as a single RDF namespace file rather than linking to individual term URIs. This poses a problem, as creating triples that can’t be properly referenced to a URI would violate basic linked data principles.
One solution to this issue would be to map terms from terms from one or more external vocabularies onto the CIDOC structure. Prof. Pattuelli suggested Linked Open Vocabularies as a resource to research some of these: https://lov.okfn.org/dataset/lov/
It looks like there was an attempt to map CIDOC to Dublin Core back in 2000 (http://www.cidoc-crm.org/sites/default/files/dc_to_crm_mapping.pdf), but that mapping doesn’t seem to address CIDOC Event entities at all. Dublin Core does have an Event class, however (http://purl.org/dc/dcmitype/Event), so it seems like it wouldn’t be impossible to map Dublin Core terms onto CIDOC’s event-based structure.
