1 / 8

Overview of HADOC Model: Integrating CIDOC-CRM Concepts

The HADOC program, introduced by the French Ministry of Culture in 2008, aims to standardize cultural data and enhance interoperability. The HADOC Conceptual Model, released in 2013, aligns with CIDOC-CRM principles but presents some distinct features. While not an extension, HADOC is compatible with CIDOC-CRM, ensuring harmonious data integration for cultural objects at a national level.

sieteiglesias
Download Presentation

Overview of HADOC Model: Integrating CIDOC-CRM Concepts

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An example of "CIDOC-CRM-aware" modelling: the HADOC model 33rdjoined meeting of the CIDOC CRM SIG and 26thFRBR - CIDOC CRM Harmonization meeting, 19-22 May 2015 Patrick Le Boeuf, National Library of France

  2. What is HADOC? • HADOC = Harmonisation de la production des données culturelles • HADOC = name of both a programme and a conceptual model • HADOC = a French Ministry of Culture initiative, led by Katell Briatte (member of the AFNOR WG who translated ISO 21127 into French)

  3. The HADOC Programme • Since 2008 • Goals:  Fight current heterogeneity in data produced by the Ministry and affiliated bodies  Facilitate interoperability  Facilitate access to and exploitation of data  On the long term, provide a national reference database for the identification of "cultural objects"

  4. The HADOC Conceptual Model • Version 1 released in 2013 • Represented in UML • Initial intention to be interoperable with:  CIDOC CRM  EDM  LIDO

  5. Some easy basics, to start with Dimension E54 Dimension E71 Man-Made- Thing Bien Culturel E16 Mesure Measurement Acteur E39 Actor Événement E5 Event Identifiant E42 Identifier

  6. Some trickier equivalences HADOC • Appellation CIDOC CRM / FRBROO • not E41 Appellation but F35 Nomen Use Statement • Activité • not E7 Activity but F51 Pursuit • Datation • E13 Attribute Assignment  Periode  not just E4 Period but E13 P141 E4  Laps de Temps  not just E52 Time-Span but E13 P141 E52  Date  not just E50 Date but E13 P141 E50 • Localisation • not just E53 Place but E13 P141 E53

  7. Trickier and trickier • Localisation Periode "an abstract class enabling one to define a Period through a Time-Span with regard to a given Place" aPourLocalisation Localisation aPourPeriode Periode estTemporellementEgalA Laps de Temps ?=? • E92 Spacetime Volume P161 has temporal projection E53 Place ["P158i was occupied by"] E4 Period P160 has spatial projection E52 Time-Span

  8. Conclusions • HADOC is "CIDOC CRM aware", although not entirely "CIDOC CRM inspired" • However, some important differences in formalism • HADOC-to-CIDOC CRM mapping not quite straightforward, but not unfeasible (also using some FRBROOfeatures) • HADOC definitely not an extension of CIDOC CRM, but on the whole compatible with it • French HADOC modelled data will predictably play nicely with CIDOC CRM modelled data

More Related