Methodological tips for mappings to CIDOC CRM Maria Theodoridou, George Bruseker, Maria Daskalaki, Martin Doerr FORTH - Institute of Computer Science {bruseker,

Slides:



Advertisements
Similar presentations
1 ICS-FORTH & Univ. of Crete SeLene November 15, 2002 A View Definition Language for the Semantic Web Maganaraki Aimilia.
Advertisements

CRMarchaeo CRMarchaeo v1.2.1
CRMarchaeo Modelling Context, Stratigraphic Unit, Excavated Matter
1 ICS –FORTH, Oct.30-Nov.4,2006, Cyprus Documenting Events in Metadata Martin Doerr, Athina Kritsotaki Center for Cultural Informatics Institute of Computer.
ICS-FORTH May 23, An Ontological Approach to Digital Preservation Metadata Martin Doerr Foundation for Research and Technology - Hellas Institute.
1 CIDOC CRM + FRBR ER = FRBR OO … an equation for a harmonised view of museum information and bibliographic information Martin Doerr First CASPAR Seminar.
Database Systems: Design, Implementation, and Management Tenth Edition
TEI, CIDOC-CRM and a Possible Interface between the Two Øyvind Eide & Christian-Emil Ore* Unit for Digital Documentation, University of Oslo, Norway (*ICOM.
Mapping Memory Manager Use Case: Mapping the dFMRÖ coin database to CIDOC-CRM Martin Doerr, Maria Theodoridou Foundation for Research and Technology –
Melbourne, October 13, Electronic Communication on Diverse Data - The Role of the oo CIDOC Reference Model - Martin Doerr (ICS-FORTH, Crete, Greece)
P12 occurred in the presence of (was present at) P11 had participant P16 used specific object P25 moved P31 has modified P92 brought into existence P33.
Heraklion, April 2, Mapping a Data Structure to the CIDOC Conceptual Reference Model Martin Doerr (ICS-FORTH, Crete, Greece) Heraklion, Crete, April.
Martin Doerr, Gerald Hiebel, Institute of Computer Science
Carlos Lamsfus. ISWDS 2005 Galway, November 7th 2005 CENTRO DE TECNOLOGÍAS DE INTERACCIÓN VISUAL Y COMUNICACIONES VISUAL INTERACTION AND COMMUNICATIONS.
ICS-FORTH May 25, The Utility of XML Martin Doerr Foundation for Research and Technology - Hellas Institute of Computer Science Heraklion, May.
ICS – FORTH, August 31, 2000 Why do we need an “Object Oriented Model” ? Martin Doerr Atlanta, August 31, 2000 Foundation for Research and Technology -
ICS-FORTH October 14, The CIDOC CRM, factor for the integration and presentation of cultural information Martin Doerr Foundation for Research and.
Harmonising without Harm: towards an object-oriented formulation of FRBR aligned on the CIDOC CRM ontology Maja Žumer (University of Ljubljana) & Patrick.
Using an ontology-driven system to integrate museum information and library information Paper presented on the occasion of the Symposium on Digital Semantic.
Metadata, the CARARE Aggregation service and 3D ICONS Kate Fernie, MDR Partners, UK.
P12 occurred in the presence of (was present at) P11 had participant P16 used specific object P25 moved P31 has modified P92 brought into existence P33.
A CIDOC CRM – compatible metadata model for digital preservation
Dimitrios Skoutas Alkis Simitsis
Smithsonian, March 26, International Symposium “Sharing the Knowledge” Martin Doerr Smithsonian, Washington DC March 26, 2003 FORTH, Greece Chair,
1 Relational Databases and SQL. Learning Objectives Understand techniques to model complex accounting phenomena in an E-R diagram Develop E-R diagrams.
Datasets on the GRID David Adams PPDG All Hands Meeting Catalogs and Datasets session June 11, 2003 BNL.
The CIDOC Conceptual Reference Model A core-ontology for information integration Karl H. Lampe, Zoologisches Forschungsmuseum Alexander Koenig (ZFMK) Bonn/Germany.
1 Exploring time and space in the annotation of museum catalogues: The Sloane virtual exhibition experience Stephen Stead Vienna November 2014 University.
Out and About with the CIDOC CRM: The Lessons and Results of the CRM Dissemination and Training programme Stephen Stead, Paveprime Ltd.
From FRBR to FRBR OO through CIDOC CRM… A Common Ontology for Cultural Heritage Information Patrick Le Bœuf, National Library of France International Symposium.
Digital Humanities Dr. Øyvind Eide TEI and neighbouring standards: CIDOC-CRM Øyvind Eide Universität Passau (with thanks to Christian-Emil.
44220: Database Design & Implementation Introduction to Module Ian Perry Room: C49 Ext.: 7287
Knowledge Technologies for Description of the Semantics of the Bulgarian Iconographical Artefacts Lilia Pavlova-Draganova Laboratory of Telemаtics – BAS,
Data Provision and Aggregation Mapping Culture Semantically with CIDOC-CRM & 3M CRM SIG Maria Theodoridou Foundation for Research and Technology – Hellas.
Temporal Primitives Institute of Computer Science Foundation for Research and Technology - Hellas Manos Papadakis & Martin Doerr Workshop: Extending, Mapping.
ICS-FORTH September, The CIDOC CRM Format Martin Doerr Washington, Sept. 22, 1999 Foundation for Research and Technology - Hellas Institute of Computer.
Data Models. 2 The Importance of Data Models Data models –Relatively simple representations, usually graphical, of complex real-world data structures.
Setting the stage: linked data concepts Moving-Away-From-MARC-a-thon.
Co-funded by the European Union under FP7-ICT Co-ordinated by aparsen.eu #APARSEN Provenance Interoperability and Reasoning Yannis Tzitzikas Assistant.
ER Diagrams and Relational Model CS 174a (Winter 2015)
COP Introduction to Database Structures
RSC Strategy Gordon Dunsire, Chair, RDA Steering Committee
Let try to identify the conectivity of these entity relationship
Logical Database Design and the Rational Model
Mapping Cultural Heritage Information to CIDOC-CRM*
Harmonized EDM-CRM-FRBRoo
Harmonized EDM-CRM-FRBRoo-CRMdig
From FRBR to FRBROO through CIDOC CRM…
Entity-Relationship Model
Harmonized EDM-CRM-FRBRoo
Annual report and current focus CIDOC CRM SIG
FRBRoo and performing arts
Chapter 12 Outline Overview of Object Database Concepts
RDA, linked data, and update on development
CRMarchaeo Modelling Context, Stratigraphic Unit, Excavated Matter
ISC321 Database Systems I Chapter 10: Object and Object-Relational Databases: Concepts, Models, Languages, and Standards Spring 2015 Dr. Abdullah Almutairi.
02 - The Relational Database Model
Ontology-Based Approaches to Data Integration
Introducing IFLA-LRM Gordon Dunsire, Chair, RSC
Metadata in Digital Preservation: Setting the Scene
Information Networks: State of the Art
RDA Community and linked data
The new RDA: resource description in libraries and beyond
Semantic Interoperability in Digital Library Systems
Entity/Data Representation in Different Contexts, Frames of Reference, and Context-Changing Events Hans W. Polzer March 21, 2018.
Modelling Intellectual Processes: The object-orient FRBR Model
Enhanced Entity-Relationship (EER) Modeling
Modelling Intellectual Processes: The object-orient FRBR Model
Modeling Properties of Properties in the CIDOC CRM RDF encoding
Entity-Relationship Modelling
Presentation transcript:

Methodological tips for mappings to CIDOC CRM Maria Theodoridou, George Bruseker, Maria Daskalaki, Martin Doerr FORTH - Institute of Computer Science {bruseker, martin,

OSLO CAA 2016, March 30, 2016 The CIDOC Conceptual Reference Model (ISO 21127:2006) has been chosen as the core model for use in several Cultural Heritage projects

OSLO CAA 2016, March 30, 2016 CIDOC CRM extension suite 3 Few concepts, high recall Special concepts, high precision CRMinfCRMsci FRBRoo CIDOC-CRM CRMarchaeo CRMdig CRMba Thing Actor Event was present at happened at PRESSoo CRMgeo

OSLO CAA 2016, March 30, Mapping one schema to another  Foundational activity Convert data stored in existing (source) schemata to an expression in a form (rdf) compatible with CIDOC CRM and its extensions (target schema) It’s not a matching exercise, it’s not matching of terms, but interpreting relations It is a consideration of the meaning of the source and a re-expression of that in the target Common point of reference in interpreting source and target as being descriptions of the same reality  Goal Preserve as much as possible the initial ‘meaning’ of the data Enable information exchange and integration between heterogeneous sources of cultural heritage information

OSLO CAA 2016, March 30, Target Range: Literal Target Domain: E22 Man-Made Object P43 has dimension Source Path: weights Source Domain: Coin Source Range: WEIGHT P90 has value Target Path: Intermediate Node: E54 Dimension Constant Node: E58 Measurement Unit P91 has unit P2 has type Constant Node: E55 Type weight gr Mapping one schema to another

OSLO CAA 2016, March 30, 2016 Mapping & Training Activities  Several mapping activities were initiated trying to convert existing schemata of Cultural heritage data to CIDOC CRM ARIADNE: diverse archaeological databases Research Space: British Museum and Rijksmuseum data  Training activities Research Space Workshops in Yale and in Oxford Universities ITN-DCH CIDOC CRM board game ARIADNE Summer Schools and Transnational Access 6

OSLO CAA 2016, March 30, 2016 General Mapping Principles & Approach 7

OSLO CAA 2016, March 30, 2016 Define primary domain Define primary domain - typically represents the focus of interest Identify the CIDOC CRM class that models it best  Is there a need for a new Class?  Do we need properties that are not available in CIDOC CRM? The introduction of a new class should comply with the “Minimality” modelling principle of CIDOC CRM (CIDOC CRM, 2015): “A class is not declared unless it is required as the domain or range of a property not appropriate to its superclass, or it is a key concept in the practical scope” 8

OSLO CAA 2016, March 30, 2016 Example: Two approaches for defining Coin  Introduce a specialization of E22 Man-Made Object: Exx Coin subclass of E22 Man-Made Object  Define the Type of E22 Man-Made Object: E22 Man-Made Object. P2 has type: E55 Type = “Coin” To choose we need to answer the question:  Does the new class Coin have new properties that are not available in E22? Create a new Class, work with it and if it comes out that it has no new properties, revert to its CRM superclass 9 Define primary domain

OSLO CAA 2016, March 30, 2016 Practical Mapping Tips 10

OSLO CAA 2016, March 30, 2016 We map local identifiers in relational database tables explicitly only if these identifiers are visible in the user interface and used in other documents as well. Alternatively, we use the local database identifiers only for generating URIs for the record instance, if the thing identified belongs to our holdings or was created/invented by us. Otherwise we better use a global authority.  Golden rules for identifiers:  they should be widely known for the item they identify  they should be related to those who can confirm the relation between the identifier and the identified (museum object identifiers) 11 Common database fields: Local identifiers

OSLO CAA 2016, March 30, 2016 only a local URI: or a local URI and an Identifier: 12 Common database fields: Local identifiers ……………….. E22 Man-Made Object E22 Man-Made Object E42 Identifier P1 is identified by

OSLO CAA 2016, March 30, 2016 Whenever possible use a global authority El Greco (Dominico Theotokopoulos) VIAF: or GETTY ULAN: 13 Common database fields: Local identifiers E39 Actor E39 Actor

OSLO CAA 2016, March 30, 2016  Label and Appellation are alternative implementations in rdf  For contemporary names (not historical) the use of rdfs:label + language attribute is sufficient  We use the E41 Appellation class only if there is need to assign some property to the Appellation 14 Common database fields: Appellations

OSLO CAA 2016, March 30, 2016 Yes/No fields of relational databases are typically mapped to types. Table name: Gefaesse (vessels) (E22 Man-Made Object) Field name: GefFragmen: yes/no field If value of field is yes then Gefaesse.GefFragment maps to E55 Type fragment 15 Common database fields: Yes/No fields E22 Man-Made Object Vessel 1 E55 Type fragment P2 has type

OSLO CAA 2016, March 30, 2016  All the hidden constants, the common context information of a db, can be added as constant node information at a suitable object type, typically in the domain node.  Quite often semantics are built into  the User Interface  the queries  values of the identifiers 16 Common database fields: Implicit and contextual information

OSLO CAA 2016, March 30, Target Range: Literal Target Domain: E22 Man-Made Object P43 has dimension Source Path: weights Source Domain: Coin Source Range: WEIGHT P90 has value Target Path: Intermediate Node: E54 Dimension Constant Node: E58 Measurement Unit P91 has unit P2 has type Constant Node: E55 Type weight gr Common database fields: Implicit and contextual information Constant Node: E40 Legal Body OEAW P50 has current keeper

OSLO CAA 2016, March 30, 2016  Need to separate categorical and factual data Inconsistent information:  Find spot -> for a specific coin  Historical facts -> for a category of coins 18 Common database fields: Categorical vs factual info

OSLO CAA 2016, March 30, 2016 Common database fields: Categorical vs factual info 19 P108i was produced by P137 exemplifies PC1 produced things of type  Need to extend the model in order to support categorical production (similar to FRBRoo R26 produced things of type) E12 Production production of coins AU E55 Type AU from Rome E22 Man-Made Object MyCoin

OSLO CAA 2016, March 30, 2016 Nationality can be modeled as:  membership in an E74 Group = citizenship, social participation an actor may join and/or leave the group (former, current member)  E67 Birth = provenance  E55 Type = behavior suitable for ambiguous, fuzzy characterizations 20 People: Groups, Nationality, Origins

OSLO CAA 2016, March 30, People: Groups, Nationality, Origins Art Institute Chicago, Photo M. Doerr, 2010 E55 Type Spanish E39 Actor P2 has type E74 Group Cretan P107i is current or former member of E67 Birth The birth of El Greco E53 Place Greece P7 took place at P98i was born

OSLO CAA 2016, March 30, 2016 Art Institute Chicago 22 People: Groups, Nationality, Origins

OSLO CAA 2016, March 30, 2016 Accidental roles are roles that do not characterize an actor independently from a particular context of activity. These roles are properties of the P14 carried out property but this cannot be represented in rdf. They should NOT be assigned to the actor 23 People: Accidental roles E39 Actor E55 Type E7 Activity P14 carried out by (performed)P14.1 in the role of

OSLO CAA 2016, March 30, 2016 Solution 1: Specializing P14 carried out by for each role suitable if we know a priory all the possible values P carried out by as researcherP carried out by as farmer People: Accidental roles E7 Activity E7 Activity E39 Actor

OSLO CAA 2016, March 30, 2016 Solution 2: Introducing class PC0 Typed CRM_Property and its subclass PC14 carried out by and properties P01 has domain and P02 has range PC14 carried out by PC14 carried out by E7 Activity klionCRM-SIGmeeting P01 has domain E55 Type E55 Type P14.1 in the role of E7 Activity MaladesPlantingOliveTrees E39 Actor P02 has range P01 has domain P02 has range PC0 Typed CRM Property E1 CRM Entity P01 has domain (P01i is domain of) P02 has range (P02i is range of) P14.1 in the role of People: Accidental roles

OSLO CAA 2016, March 30, 2016 Solution 2: equivalence with CIDOC CRM definition PC14 carried out by er E7 Activity klionCRM-SIGmeeting P01 has domain E55 Type P14.1 in the role of E39 Actor P02 has range P14 carried out by (performed) PC0 Typed CRM Property E7 Activity HeraklionCIDOC-CRM-SIGmeeting E39 Actor E55 Type equivalent to P14.1 in the role of People: Accidental roles

OSLO CAA 2016, March 30, 2016 Solution 3: Add a note to each Activity with the Person’s role does not require any extension of the model Literal The Activity was carried out by Doerr in the role of Researcher Literal The Activity was carried out by Doerr in the role of Farmer E7 Activity P2 has note E7 Activity E39 Actor P14 carried out by P2 has note People: Accidental roles

OSLO CAA 2016, March 30, 2016 Solution 4: Assign a type to each Activity does not require any extension of the model E55 Type E55 Type E7 Activity E7 Activity E39 Actor P14 carried out by People: Accidental roles P2 has type

OSLO CAA 2016, March 30, 2016 People: Accidental roles - Issuer 29 Target Range: E39 Actor Target Domain: E22 Man-Made Object P108i was produced by Source Path: ISSUER_ID == PR_ID Source Domain: //COIN Source Range: //ISSUER P14 carried out by E12 Production p1 "Issuer" is an accidental role, does not characterize an actor independently from particular contexts of activity. Therefore the Actor does not have the type "Issuer" but the activity only has the type "Issuing“ P17 was motivated by E7 Activity ia1 E55 Type Issuing “gave order”

OSLO CAA 2016, March 30, 2016 Political office is modeled as an E74 Group with one member an actor may join and/or leave the group (former, current member) Alexis Tsipras is the 185th and current Prime Minister of Greece, having been sworn in on 21 September He previously served as the 183rd Prime Minister of Greece from 26 January 2015 to 27 August E74 Group The Prime Minister of Greece P144i gained member by E85 Joining P143 joined E39 Actor Alexis Tsipras P4 has time-span E52 Time-Span 26 January 2015 P146i lost member by E86 Leaving P145 separated E39 Actor Alexis Tsipras P4 has time-span E52 Time-Span 27 August 2015 P144i gained member by E85 Joining P143 joined E39 Actor Alexis Tsipras P4 has time-span E52 Time-Span 21 September People: Political office

OSLO CAA 2016, March 30, 2016  Geopolitical units map to a Period with type “State”, etc.  Map them as Place but the id has the name of the country plus a date, when this name of country was assigned.  It is a snapshot that allows to be always in the right time space context.  always refer to a global authority e.g. TGN (falls within, overlaps, is identified by) 31 Places: Countries

OSLO CAA 2016, March 30, 2016 “Why hell is not a good place”  E53 Place represents always a real extent in space independent of time  An imaginary place can be represented as an E89 Propositional Object The ambiguity between real and imaginary is an ambiguity of the phrase and not an ambiguity in the mind of the author of the phrase (as long as he is sane) Alternatives should be made explicit: principle of recall over precision 32 Places: Imaginary Places

OSLO CAA 2016, March 30, 2016 How many interpretations of hell? 33 Places: Imaginary Places Taoist Hell Catholic Hell, Pisa 13 th century Byzantine-Orthodox Hell Crete

OSLO CAA 2016, March 30, 2016 William Blake's depiction of "The Vestibule of Hell and the Souls Mustering to Cross the Acheron" in his Illustrations to Dante's "Divine Comedy“ object 5 c The original for the work is held by the National Gallery of Victoria Example taken from 34 Places: Imaginary Places E73 Information Object The Vestibule of Hell and the Souls Mustering to Cross the Acheron E89 Propositional Object Hell P67 refers to E53 Place Acheron

OSLO CAA 2016, March 30, 2016 Now Italian archaeologists working at the Greco-Roman site of ancient Hierapolis (modern-day Pamukkale) in Turkey have uncovered that city's gate to the underworld. Example taken from underworld-archaeology-mount-olympus--greece/ 35 Places: Imaginary Places E89 Propositional Object Entrance to Hell P67 refers to E53 Place ancient Hierapolis E13 Attribute Assignement possibly refers to E73 Information Object P140 was attributed by P141 assigned Archaeologists Find a Classic Entrance to Hell

OSLO CAA 2016, March 30, 2016 Pieces of a broken object are mapped as products of an event that destroyed the object and not as part_of.  For provenance reasons  For semantic clarity As long as the object existed the respective pieces of matter were not distinct, had no identity 36 Objects: Pieces of a broken object E22 Man-Made Object Piece 1 E81 Transformation destruction of object E55 Type fragment E22 Man-Made Object broken object P124 transformed P2 has type P123 resulted in

OSLO CAA 2016, March 30, 2016 Pieces of a set are mapped as part of  Chess set has parts: Chess board and chess pieces Collective objects in the general sense, like a tomb full of gifts, a folder with stamps or a set of chessmen, should be documented as instances of E19 Physical Object, and not as instances of E78 Collection. This is because they form wholes either because they are physically bound together or because they are kept together for their functionality. 37 Objects: Pieces of a set E22 Man-Made Object Chess set E22 Man-Made Object Chess pieces E22 Man-Made Object Chess board P46 is composed of

OSLO CAA 2016, March 30, Conclusions Always consult the reference document Definition of the CIDOC Conceptual Reference Model Read carefully the scope note of the class and property that you intend to use. Learning to use a formal ontology requires understanding the basic principles expressed in its scope, classes and relations New site (available for testing)

OSLO CAA 2016, March 30, Conclusions IFASK!

OSLO CAA 2016, March 30, 2016 Thank you! Maria Theodoridou 40