Download presentation
Presentation is loading. Please wait.
Published byAlice Freeman Modified over 9 years ago
1
Heraklion, April 2, 2002 1 Mapping a Data Structure to the CIDOC Conceptual Reference Model Martin Doerr (ICS-FORTH, Crete, Greece) Heraklion, Crete, April 2, 2002
2
Heraklion, April 2, 2002 2 What Means Mapping of One Schema to Another Defining an (automated) transformation of each instance of schema 1 into an instance of schema 2 with the same meaning. CRM Approach: u Interpretation of schema 1 as semantic model (nodes and links), u mapping each element of that to an equivalent CIDOC CRM path, u such that each instance of an element of the semantic model 1 can be converted into a valid instance of the CIDOC CRM with the same meaning. This is the most simple theory. Works for good structures
3
Heraklion, April 2, 2002 3 Interpreting a Schema as Semantic Model 1. Interpreting tables, columns as entities 2. Interpreting records as entity instances 3. Interpreting fieldnames as relationships and entities 4. Interpreting field contents as entity instances Each field is interpreted as entity-relationship-entity (e-r-e) The whole schema is decomposed into e-r-e’s Each e-r-e is mapped individually to the CRM.
4
Heraklion, April 2, 2002 4 Interpreting a Schema as Semantic Model, Example ID1975-7309 CategoryNRM - Railway furniture DescriptionArmchair, Upholstered in blue moquette with curved, buttoned back & scroll arms. Wooden legs Item name(s)armchairs (AAT Hierarchy: Furnishings) PartAspectTerm(AAT Hierarchy) overallphysical descriptor upholsteringProcesses & techniques overallmaterialmoquetteMaterials overallcolourblueColor legsmaterialwoodMaterials backphysical descriptor buttoningProcesses & techniques backshapecurvedPhysical attributes armsshapescrolled armsComponents The whole record corresponds to one entity: It stands for one object which is not referred to The field name stands for a relationship and the kind of contents Object 1975-7309 The field contents stand for an entity instance : 1975-7309 has ID: (data example from the Science Museum of London)
5
Heraklion, April 2, 2002 5 Mapping the First Element: Creating an Equivalent Proposition Object 1975-7309 Whole Record ID “has ID ” Source Schema interpretation Instance, valid for both schemata Man-Made Object Identifier is identified by CRM Schema maps to: Possible Mapping Annotation: Whole Record= E22 Man-Made Object ID = E42 Object identifier Whole Record->ID = P47 is identified by Possible CRM instance Annotation: Object 1975-7309 (E22: Man-Made_Object) is_identified_by 1975-7309 (E42 Object_Identifier)
6
Heraklion, April 2, 2002 6 Mapping the Interpreted Schema to the CRM Each Entity-link-entity can be instantiated as self-explanatory, context independent proposition The mapping allows to create sets of propositions equivalent to the meaning of each source document, but in terms of the CIDOC CRM. As the CRM-compatible propositions are self-explanatory, they can be merged into huge knowledge pools and the document boundaries can be ignored. buzz words: Data warehouses, Semantic Web
7
Heraklion, April 2, 2002 7 Interpreting a Schema: Advanced Stuff: Value Dependency ID1975-7309 CategoryNRM - Railway furniture DescriptionArmchair, Upholstered in blue moquette with curved, buttoned back & scroll arms. Wooden legs Item name(s)armchairs (AAT Hierarchy: Furnishings) PartAspectTerm(AAT Hierarchy) overallphysical descriptor upholsteringProcesses & techniques overallmaterialmoquetteMaterials overallcolourblueColor legsmaterialwoodMaterials backphysical descriptor buttoningProcesses & techniques backshapecurvedPhysical attributes armsshapescrolled armsComponents The whole row corresponds to one entity: It stands for one part The first field name stands for a relationship and the kind of contents Object 1975-7309 The field contents stands for an entity instance : legs of obj. 1975-7309 has part: If part = overall, it stands for the whole Mapping condition:
8
Heraklion, April 2, 2002 8 Mapping under condition: Creating an equivalent statement Object 1975-7309 legs of obj. 1975-7309 Whole Record Row “Part” “has Part ” Source Schema interpretation Instance, valid for both schemata Man-Made Object Man-Made Object is composed of CRM Schema maps to: Possible Mapping Annotation: Whole Record= E22 Man-Made Object Row “Part” = E22 Man-Made Object If (in Row “Part”, Part /= “overall”) then Whole Record-> Row “Part” = P46 is composed of Possible CRM instance Annotation: Object 1975-7309 (E22: Man-Made_Object) is_composed_of legs of 1975-7309 (E22: Man-Made_Object) If Part /= “overall”
9
Heraklion, April 2, 2002 9 Interpreting a Schema: Advanced Stuff: Values as Properties ID1975-7309 CategoryNRM - Railway furniture DescriptionArmchair, Upholstered in blue moquette with curved, buttoned back & scroll arms. Wooden legs Item name(s)armchairs (AAT Hierarchy: Furnishings) PartAspectTerm(AAT Hierarchy) overallphysical descriptor upholsteringProcesses & techniques overallmaterialmoquetteMaterials overallcolourblueColor legsmaterialwoodMaterials backphysical descriptor buttoningProcesses & techniques backshapecurvedPhysical attributes armsshapescrolled armsComponents The field “Aspect” contents state a relationship Object 1975-7309 The field contents stands for an entity instance : moquette has material: If part = overall, AND Aspect = material Value based mapping
10
Heraklion, April 2, 2002 10 Interpreting a Schema: Advanced Stuff: Mapping to Paths ID1975-7309 CategoryNRM - Railway furniture DescriptionArmchair, Upholstered in blue moquette with curved, buttoned back & scroll arms. Wooden legs Item name(s)armchairs (AAT Hierarchy: Furnishings) PartAspectTerm(AAT Hierarchy) overallphysical descriptor upholsteringProcesses & techniques overallmaterialmoquetteMaterials overallcolourblueColor legsmaterialwoodMaterials backphysical descriptor buttoningProcesses & techniques backshapecurvedPhysical attributes armsshapescrolled armsComponents The field “Aspect” contents state a relationship Object 1975-7309 The field contents stands for an entity instance : upholstering has physical descriptor: If part = overall, AND Aspect = physical descriptor Value based mapping
11
Heraklion, April 2, 2002 11 Mapping to Paths: Introducing an intermediate node Object 1975-7309 upholstering Whole Record Term “has physical descriptor ” Source Schema interpretation Instance of source Man-Made Object was produced by CRM Schema maps to: Possible Mapping Annotation: Whole Record= E22 Man-Made Object Term = E55 Type If Part = “overall” & Aspect= physical descriptor Whole Record-> Term = P108 was produced by – E12 Production - P32 used general technique Possible CRM instance Annotation: Object 1975-7309 (E22: Man-Made_Object) was_produced_by Obj. 1975-7309 Production (E12: Production) used general technique upholstering (E55 Type) Production Type If Part = “overall” & Aspect= physical descriptor used general technique Object 1975-7309 upholstering Obj. 1975-7309 Production Instance of target
12
Heraklion, April 2, 2002 12 Interpreting a Schema: Advanced Stuff: Nested Structures ID1975-7309 CategoryNRM - Railway furniture DescriptionArmchair, Upholstered in blue moquette with curved, buttoned back & scroll arms. Wooden legs Item name(s)armchairs (AAT Hierarchy: Furnishings) PartAspectTerm(AAT Hierarchy) overallphysical descriptor upholsteringProcesses & techniques overallmaterialmoquetteMaterials overallcolourblueColor legsmaterialwoodMaterials backphysical descriptor buttoningProcesses & techniques backshapecurvedPhysical attributes armsshapescrolled armsComponents The whole row corresponds to one entity: If part /= overall it stands for one part The field contents stands for an entity instance : legs of obj. 1975-7309 has material: If Aspect = material wood The contents of field “Aspect” state a relationship Value based mapping
13
Heraklion, April 2, 2002 13 Mapping Nested Structures : Continuing on a Range Entity wood legs of obj. 1975-7309 Row “Part” Term “has material ” Source Schema interpretation Instance, valid for both schemata Man-Made Object Material consists of CRM Schema maps to: Possible Mapping Annotation: Row “Part” = E22 Man-Made Object If Aspect= “material” Term = E57 Material Row “Part” -> Term = P45 consists of Possible CRM instance Annotation: Object 1975-7309 (E22: Man-Made_Object) is_composed_of legs of 1975-7309 (E22: Man-Made_Object) consists_of wood (E57 Material) If Part /= “overall” & Aspect = “material” Object 1975-7309
14
Heraklion, April 2, 2002 14 Other Forms of Maps: Cases of Heterogeneity A B “a ” Source Schema interpretation D c CRM Schema E C “b ” F d A B “a ” Source Schema interpretation D c CRM Schema E C “b ” F d G e Parallel to nested: Parallel to intermediate- parallel: (frequent with events!)
15
Heraklion, April 2, 2002 15 Other Mapping Forms: Cases of Heterogeneity A B “a ” Source Schema interpretation B,C,D are parts of an identifier for one real-life thing D d CRM Schema E C “b ” Compound contraction: (frequent with addresses, species names etc!) D “c ”
16
Heraklion, April 2, 2002 16 Mapping to the CRM: Conclusions Mapping to the CRM can serve just as guide for good- practice data structures. It can be used to create a Semantic Web of cultural knowledge. It can be used to preserve data in a neutral form. Even though mapping can become weird, good data structures transform easily, and there are commercial tools. No tool can guess all the experts intention in a data structure: Domain experts must assist the mapping.
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.