Presentation is loading. Please wait.

Presentation is loading. Please wait.

IFORTH-ICS May 2014 CIDOC CRM Workshop Data Objects & Semantics Center for Cultural Informatics, Institute of Computer Science Foundation for Research.

Similar presentations


Presentation on theme: "IFORTH-ICS May 2014 CIDOC CRM Workshop Data Objects & Semantics Center for Cultural Informatics, Institute of Computer Science Foundation for Research."— Presentation transcript:

1 IFORTH-ICS May 2014 CIDOC CRM Workshop Data Objects & Semantics Center for Cultural Informatics, Institute of Computer Science Foundation for Research and Technology - Hellas Martin Doerr Prato, Tuscany, May 26-30, 2014

2 FORTH-ICS February 2014 CIDOC CRM Library, Archive, Museum Information The typical library contents: “The whole stories”, access widely solved!  Primary literature: Fiction.  Categorical: theories and hypotheses  Secondary literature (research results)  Facts brought into causal context The typical museum information: “Museum objects rarely talk”  Factual documentation of properties and context per object, references, classification  Highly heterogeneous,  About things taken out of original context, distributed over the world 2

3 FORTH-ICS February 2014 CIDOC CRM The typical archive contents: “The needle in the haystack”  Primary sources, “bits and pieces” (letters, legal documents, administration acts, images, scientific records)  Factual, kept in the contextual sequence of creation, as by the creator or responsible  Kept due to mandate related to functions.  Access indirectly through guessing: “who should have written about it?” Similarly, library content itself: “What is in the book?”  Parts of book content (citations!) are primary source of investigation  Current access forms: not much more than keyword search, if a digital form exists… Library, Archive, Museum Information 3

4 FORTH-ICS February 2014 CIDOC CRM Libraries Museums Archives illustrate, exemplify are about Books Objects, Sites primary Documents provide finding aids refer to document features & context provide finding aids contain narratives made from publish using SMRs Library, Archive, Museum Information document manage refer to exhibit pub lish 4

5 FORTH-ICS February 2014 CIDOC CRM Library, Archive, Museum Information Example: Museum Data are not “Metadata” 5

6 FORTH-ICS February 2014 CIDOC CRM Relevance of Cultural Objects By: Thomas Bewick 1753-1828, London In: “The figures of Bewick’s quadrupeds”, Edward Walker, Newcastle, 1824. 6

7 FORTH-ICS February 2014 CIDOC CRM The Scholarly Process discover collect aggregate update Search, correlate, integrate Refer interpret present Layer of “Latest Knowledge” “Evidence layer” Things Sources Collections Corpora Publications Stories exhibitions Ethiopia Johanson's Expedition Hadar Discovery of Lucy Lucy Cleveland Museum of Natural History Donald Johanson AL 288-1 Hypertext is wrong! 7

8 FORTH-ICS February 2014 CIDOC CRM Knowledge Representation How To Find The Global Schema ?? 8

9 FORTH-ICS February 2014 CIDOC CRM Knowledge Representation : Basic Notions What is “Knowledge Representation”: Representation of concepts, items (particulars) and their interrelation as perceived by humans and expressed in terms of a formal language, such as logic, conceptual graphs etc. The intended meaning (semantics) is the interpretation (identification) of used symbols as things and categories in the described universe (“domain”, “world”, “real world), and the interpretation of expressions, which use those symbols, as statements about their structure and interrelations (early Wittgenstein). A set of related knowledge representation expressions is called a model (of a domain). IT Jargon (due to limited scope):  “KNOWLEDGE” instead of model  “SEMANTICS” instead of expressions 9

10 FORTH-ICS February 2014 CIDOC CRM Knowledge Representation: Reservations Limitations: “Principles of equivalence”: Given a model accepted as correct by a human, logical (automatable) inferences from a model should conform with the expectations of a human. Only in this sense represents knowledge representation (KR) knowledge. KR is a means of communication. Expressions are rarely/never definitions, but partial constraints. (see also late Wittgenstein, Eleonore Rosch - George Lakoff). Formal languages fit only partially the way we think. Psychological Obstacles to create KR: The true structure of our thoughts is unconscious. Beware of compressions (Gilles Fauconnier, “The Way We Think”). Methodological questions reveal part of it (e.g. change of context). 10

11 FORTH-ICS February 2014 CIDOC CRM From Forms to Classes (a “decompression”) Patient Name String Weight Number Birth date Time Birth Place String Address String Attributes (sometimes called “part-of”) Table name Value types  What does that mean as statements about the world?  Is it correct, e.g., “Address” ? Relational Database Tables: - an abstraction from forms, - a model for (statistical) information processing 11

12 FORTH-ICS February 2014 CIDOC CRM ∞ ∞ Address table Patient Name String Weight Number Birth Date Time Birth Place String has Address:  Shared with others  Changes over time  Can be multiple  Independent entity What about Birth Date? From Forms to Classes (a “decompression”) 12

13 FORTH-ICS February 2014 CIDOC CRM ∞ ∞ Address table Patient Name String Weight Number has Birth Date, Birth Place  Shared with others  Birth shared with others (twins)!  Independent entity Birth Date Time Place String 1 ∞ From Forms to Classes (a “decompression”) 13

14 FORTH-ICS February 2014 CIDOC CRM ∞ ∞ Address Patient Name String has Knowledge Representation From Forms to Classes (a “decompression”) Weight:  Similar but not shared!  Multiple units, measurements  Dependent, but distinct entity What about the name? Birth Date Time Place String 1 ∞ Patient’s Weight 1 ∞ 14

15 FORTH-ICS February 2014 CIDOC CRM ∞ ∞ Address Patient has Knowledge Representation From Forms to Classes (a “decompression”) Name:  Shared  Context specific  Independent entity Who is the Patient then? Birth Date Time Place String 1 ∞ Patient’s Weight 1 ∞ Name String 15

16 FORTH-ICS February 2014 CIDOC CRM Summary:  In the end, no “private” attributes left over.  Widening/ change of context reveals them as hidden, distinct entities.  The “table” becomes a graph of related, but distinct entities, a MODEL  Things are only identified by unique keys – and the knowledge of the reality!  Do we describe a reality now? Are we closer to reality? Do we agree that this is correct? (“Ontological commitment”). For a database schema, a projection (birth!) of perceived reality can be sufficient and more efficient. For exchange of knowledge, it is misleading. For a database schema, it can hinder extension. Knowledge Representation From Forms to Classes (a “decompression”) 16

17 FORTH-ICS February 2014 CIDOC CRM In KR we call these distinct entities classes:  A class is a category of items that share one or more common traits serving as criteria to identify the items belonging to the class.  These properties need not be explicitly formulated in logical terms, but may be described in a text (here called a scope note) that refers to a common conceptualisation of domain experts.  The sum of these traits is called the intension of the class. A class may be the domain or range of none, one or more properties formally defined in a model.  The formally defined properties need not be part of the intension of their domains or ranges: such properties are optional. An item that belongs to a class is called an instance of this class.  The set of instances is called the extension. Knowledge Representation Classes and Instances 17

18 FORTH-ICS February 2014 CIDOC CRM DoctorPatient George 1 Costas 65 Weight Address Odos Evans 6. GR71500 Heraklion, Crete, Greece ? instance property Knowledge Representation Classes and Instances weighs dwells at In KR, instances are independent units of models, not a restricted to the records of one table. Identity is separated from description. We can do “multiple instantiation”.  What have doctors and patients in common? 85 Kg 18

19 FORTH-ICS February 2014 CIDOC CRM DoctorPatient George 1 Costas 65 Person Physical Object Weight Address dwells at weighs isA Knowledge Representation Generalization and Inheritance Odos Evans 6. GR71500 Heraklion, Crete, Greece 85 Kg subclass superclass An instance of a class is an instance of all its superclasses. A subclass inherits the properties of all superclasses. (properties “move up”) 19

20 FORTH-ICS February 2014 CIDOC CRM Knowledge Representation Ontology and Information Systems  An ontology is a logical theory accounting for the intended meaning of a formal vocabulary, i.e. its ontological commitment to a particular conceptualization of the world. The intended models* of a logical language using such a vocabulary are constrained by its ontological commitment. An ontology indirectly reflects this commitment (and the underlying conceptualization) by approximating these intended models. Nicola Guarino, Formal Ontology and Information Systems, 1998. * “models” are meant as models of possible states of affairs.  Ontologies pertains to a perceived truth: A model commits to a conceptualization, typically of a group, how we imagine things in the world are related.  An ontology can be implemented on a database, e.g, with RDF, OWL, but such a schema is no more a “pure” ontology. 20

21 FORTH-ICS February 2014 CIDOC CRM Terminology and Information Systems We define as terminology (vocabulary) as a system of named universals (classes) which is used in an information system as data i.e., their use does not depend or imply instance relationships that hold only between these the terms or their specializations. e.g., has_type : “car”, has_type : “wheel” is not used to say in which position of this car this wheel is mounted. Terminological systems are organized in KOS, typically with specialization/generalization hierarchies, and categorical relations (such as: cars –have parts – wheels) For us (FORTH-ISL, CRM-SIG), terminological systems are not ontologies! 21

22 FORTH-ICS February 2014 CIDOC CRM 22

23 FORTH-ICS February 2014 CIDOC CRM Challenge: Integrating Special and General… Access all data from any level by property generalization Dublin Core CDWA MIDAS Data Few concepts, high recall Special concepts, high precision automatic data export CIDOC Conceptual Reference Model (CRM) Thing Actor Event Acquisition was present at used object happened at 23

24 FORTH-ICS February 2014 CIDOC CRM But how to find the Global Schema? Foresight:  We started 1994-1996 with CIDOC/ICOM Documentation Standards Working Group  Convinced Group to use new technology => compatible to the later RDF/RDFS/OWL!  Addressed challenge: integrating poor and rich schemata to built the connection layer  Proactive, in order to be ahead of industrial solutions. Problem (2) to solve: What are the shared concepts? The simple idea of the CIDOC CRM:  Use existing schemata in use as evidence for underlying concepts and discourse restriction!!  Describe only facts, that are relevant across documents.  Deal with terminology as data!  Explaining data needs less words than a questionnaire.  The data in the collection layer are already checked for plausibility and completeness. 24

25 FORTH-ICS February 2014 CIDOC CRM Historical Archives… Type:Text Title: Protocol of Proceedings of Crimea Conference Title.Subtitle: II. Declaration of Liberated Europe Date: February 11, 1945 Creator:The Premier of the Union of Soviet Socialist Republics The Prime Minister of the United Kingdom The President of the United States of America Publisher:State Department Subject:Postwar division of Europe and Japan “ The following declaration has been approved: The Premier of the Union of Soviet Socialist Republics, the Prime Minister of the United Kingdom and the President of the United States of America have consulted with each other in the common interests of the people of their countries and those of liberated Europe. They jointly declare their mutual agreement to concert… ….and to ensure that Germany will never again be able to disturb the peace of the world…… “ Documents Metadata About… 25

26 FORTH-ICS February 2014 CIDOC CRM Images, non-verbose… Type:Image Title: Allied Leaders at Yalta Date: 1945 Publisher:United Press International (UPI) Source:The Bettmann Archive Copyright:Corbis References:Churchill, Roosevelt, Stalin Photos, Persons Metadata About… 26

27 FORTH-ICS February 2014 CIDOC CRM Places and Objects TGN Id: 7012124 Names: Yalta (C,V), Jalta (C,V) Types: inhabited place(C), city (C) Position: Lat: 44 30 N,Long: 034 10 E Hierarchy: Europe (continent) <– Ukrayina (nation) <– Krym (autonomous republic) Note: …Site of conference between Allied powers in WW II in 1945; …. Source: TGN, Thesaurus of Geographic Names Places, Objects About… Title: Yalta, Crimean Peninsula Publisher: Kurgan-Lisnet Source: Liaison Agency 27

28 FORTH-ICS February 2014 CIDOC CRM Explicit Events, Object Identity, Symmetry P14 performed P11 participated in P94 has created E31 Document “Yalta Agreement” E7 Activity “Crimea Conference” E65 Creation Event * E38 Image P86 falls within P7 took place at P67 is referred to by E52 Time-Span February 1945 P81 ongoing throughout P82 at some time within E39 Actor E53 Place 7012124 E52 Time-Span 1945-02-11 28

29 FORTH-ICS February 2014 CIDOC CRM Outcome s The CIDOC Conceptual Reference Model  A collaboration with the International Council of Museums  An ontology of 86 classes and 137 properties for culture and more  With the capacity to explain hundreds of (meta)data formats  Accepted by ISO TC46 in September 2000  International standard since 2006 - ISO 21127:2006  To be revised 2014 (minor extensions) Serving as:  intellectual guide to create schemata, formats, profiles  A language for analysis of existing sources for integration/ mediation “Identify elements with common meaning”  Transportation format for data integration / migration / Internet 29

30 FORTH-ICS February 2014 CIDOC CRM The Intellectual Role of the CRM Legacy systems Legacy systems Data bases World Phenomena ? Data structures & Presentation models Conceptualization abstracts from approximates explains, motivates organize refer to Data in various forms 30

31 FORTH-ICS February 2014 CIDOC CRM Encoding of the CIDOC CRM The CIDOC CRM is a formal ontology (defined in TELOS)  But CRM instances can be encoded in many forms: RDBMS, ooDBMS, XML, RDF(S)  Uses Multiple isA – to achieve uniqueness of properties in the schema  Uses multiple instantiation – to be able to combine not always valid combinations (e.g. destruction – activity)  Uses Multiple isA for properties to capture different abstraction of relationships Methodological aspects:  Entities are introduced as anchors of properties (and if structurally relevant)  Frequent joins (short-cuts) of complex data paths for data found in different degrees of detail are modeled explicitly 31

32 FORTH-ICS February 2014 CIDOC CRM Data example (RDF-like form) Epitaphios GE34604 (entity E22 Man-Made Object) P30 custody transferred through, P24 changed ownership through Transfer of Epitaphios GE34604 (entity E10 Transfer of Custody, E8 Acquisition Event) P28 custody surrendered by Metropolitan Church of the Greek Community of Ankara (entity E39 Actor) P23 transferred title from Metropolitan Church of the Greek Community of Ankara (entity E39 Actor) P29 custody received by Museum Benaki (entity E39 Actor) P22 transferred title to Exchangeable Fund of Refugees (entity E40 Legal Body) P2 has type national foundation (entity E55 Type) P14 carried out by Exchangeable Fund of Refugees (entity E39 Actor) P4 has time-span GE34604_transfer_time (entity E52 Time-Span) P82 at some time within 1923 – 1928 (entity E61 Time Primitive) P7 took place at Greece (entity E53 Place) P2 has type nation (entity E55 Type) republic (entity E55 Type) P89 falls within Europe (entity E53 Place) P2 has type continent (entity E55 Type) TGN data Multiple Instantiation 32

33 FORTH-ICS February 2014 CIDOC CRM Top-level classes useful for integration participate in E39 Actors E55 Types E28 Conceptual Objects E18 Physical Thing E2 Temporal Entities E41 Appellations affect or / refer to refer to / refine refer to / identify location at within E53 Places E52 Time-Spans 33

34 FORTH-ICS February 2014 CIDOC CRM The types of relationships  Identification of real world items by real world names  Observation and Classification of real world items  Part-decomposition and structural properties of Conceptual & Physical Objects, Periods, Actors, Places and Times  Participation of persistent items in temporal entities creates a notion of history: “world-lines” meeting in space-time  Location of periods in space-time and physical objects in space  Influence of objects on activities and products and vice-versa  Reference of information objects to any real-world item 34

35 FORTH-ICS February 2014 CIDOC CRM The E2 Temporal Entity Hierarchy E2 Temporal Entity E5 Event E63 Beginning of Existence E7 Activity E69 Death E6 Destruction E87 Curation Activity E83 Type Creation E13 Attribute Assignment E86 Leaving E80 Part Removal E 79 Part Addition Generalization E64 End of Existence E10 Transfer of Custody E15 Identifier Assignment E4 Period E3 Condition State E68 Dissolution E81 Transformation E67 Birth E66 Formation E65 Creation E11 Modification E9 Move E8 Acquisition E85 Joining E12 Production E17 Type Assignment E14 Condition Assessment E16 Measurement 35

36 FORTH-ICS February 2014 CIDOC CRM Scope note example: E2 Temporal Entity E2 Temporal Entity Scope Note: This class comprises all phenomena, such as the instances of E4 Periods, E5 Events and states, which happen over a limited extent in time. In some contexts, these are also called perdurants. This class is disjoint from E77 Persistent Item. This is an abstract class and has no direct instances. E2 Temporal Entity is specialized into E4 Period, which applies to a particular geographic area (defined with a greater or lesser degree of precision), and E3 Condition State, which applies to instances of E18 Physical Thing. Comments: E2 is limited in time, is the only link to time, but is not time itself spreads out over a place or object the core of a model of physical history, open for unlimited specialisation 36

37 FORTH-ICS February 2014 CIDOC CRM Temporal Entity-Main Properties  E2 Temporal Entity Properties: P4 has time-span (is time-span of): E52 Time-Span  E4 Period Properties: P7 took place at (witnessed): E53 Place P9 consists of (forms part of): E4 Period P10 falls within (contains): E4 Period  E5 Event Properties: P12 occurred in the presence of (was present at): E77 Persistent Item P11 had participant (participated in): E39 Actor  E7 Activity Properties: P14 carried out by (performed): E39 Actor P20 had specific purpose (was purpose of): E5 Event P21 had general purpose (was purpose of): E55 Type P16 used specific object (was used for): E70 Thing P125 used object of type (was type of object used in) E55 Type 37

38 FORTH-ICS February 2014 CIDOC CRM The Participation Properties P12 occurred in the presence of (was present at) P16 used specific object (was used for) P25 moved (moved by) P33 used specific technique (was used by) P142 used constituent (was used in) P143 joined (was joined by) P144 joined with (gained member by) P145 separated (left by) P124 transformed (was transformed by) P110 augmented (was augmented by) P112 diminished (was diminished by) P95 has formed (was formed by) P22 transferred title to (acquired title through) P23 transferred title from (surrendered title through) P135 created type (was created by) Generalization P31 has modified (was modified by) P146 separated from (lost member by) P28 custody surrendered by (surrendered custody through) P11 had participant (participated in) P93 took out of existence (was taken out of existence by) P92 brought into existence (was brought into existence by) P96 by mother (gave birth) P14 carried out by (performed) P99 dissolved (was dissolved by) P13 destroyed (was destroyed by) P100 was death of (died in) P108 has produced (was produced by) P123 resulted in (resulted from) P98 brought into life (was born) P94 has created (was created by) P29 custody received by (received custody through) 38

39 FORTH-ICS February 2014 CIDOC CRM Historical Events as Meetings S t Caesar’s mother Caesar Brutus Brutus’ dagger “coherence volume” of Caesar’s death “coherence volume” of Caesar’s birth was present at! ? Forum Romanum, Rome ? Forum Romanum, Rome 39

40 FORTH-ICS February 2014 CIDOC CRM Depositional events as meetings S t ancient ancientSantorinian house lava and ruins volcano coherence volume of volcano eruption coherence volume of house building Santorini - Akrotiti 40

41 FORTH-ICS February 2014 CIDOC CRM Exchanges of information as meetings t S runner 1 st Athenian coherence volume of first announcement coherence volume of the battle of Marathon Marathon otherSoldiers Athens 2 nd Athenian coherence volume of second announcement Victory!!! Victory!!! 41

42 FORTH-ICS February 2014 CIDOC CRM S t operator 1 st Computer coherence volume of mesh-creation coherence volume of acquisition Museum museumobject It-Lab 2 nd Computer coherence volume of rendering scan-data 3D model 3D Model Creation as Meetings scanner mesh-data 42

43 FORTH-ICS February 2014 CIDOC CRM Networks of Historical of Knowledge space time “LAOKOON” (copy) (in Vatican museum) Winkelmann “…noble simplicity, silent grandeur…” (in a library) Winkelmann’s birth Winkelmann’s death Winkelmann sees “Laokoon” Winkelmann writes…. Winkelmann’s mother unknown Roman copies “Laokoon” “LAOKOON” unknown Roman Greece RomeGermany (archive information?) Published Inference (in a library?) 1755 43

44 FORTH-ICS February 2014 CIDOC CRM Time Uncertainty, Certainty and Duration time before P82 at some time within P81 ongoing throughout after “ intensity ” Duration (P83,P84) 44

45 FORTH-ICS February 2014 CIDOC CRM E7 Activity and inherited properties E55 Type E1 CRM EntityE62 String E7 Activity P3 has note P2 has type (is type of) 0,10,n E5 Event E55 Type P3.1 has type E59 Primitive Value E39 Actor P14 carried out by (performed) 1,n0,n P14.1 in the role of E.g., “Field Collection” E55 Type E.g., “photographer” Generalization property Indirect Generalization 45

46 FORTH-ICS February 2014 CIDOC CRM Activities: E16 Measurement P140 assigned attribute to (was attribute by) E16 Measurement E13 Attribute Assignment E70 ThingE54 Dimension P43 has dimension (is dimension of) 0,n 1,1 1,n0,n1,10,n P39 measured (was measured by) P40 observed dimension (was observed in) 0,n P141 assigned (was assigned by) 0,n E1 CRM Entity 0,n E1 CRM Entity 0,n E58 Measurement Unit E60 Number P90 has value 1,1 0,n P91 has unit (is unit of) 1,1 0,n Shortcut Generalization property Indirect Generalization 46

47 FORTH-ICS February 2014 CIDOC CRM E53 Place  A place is an extent in space, determined diachronically with regard to a larger, persistent constellation of matter, often continents - by coordinates, geophysical features, artefacts, communities, political systems, objects - but not identical to  A “CRM Place” is not a landscape, not a seat - it is an abstraction from temporal changes - “the place where…”  A means to reason about the “where” in multiple reference systems.  Examples: figures from the bow of a ship African dinosaur foot-prints appearing in Portugal by continental drift where Nelson died 47

48 FORTH-ICS February 2014 CIDOC CRM Properties of E53 Place P59 has section (is located on or within) P53 has former or current location (is former or current location of ) P8 took place on or within (witnessed) E45 Address E48 Place Name E47 Spatial Coordinates E46 Section DefinitionE18 Physical Thing E44 Place Appellation E53 Place P88 consists of (forms part of) P58 has section definition (defines section) E9 Move P26 moved to (was destination of) P27 moved from (was origin of) P25 moved (moved by) E12 Production P108 has produced (was pro duced by) P7 took place at (witnessed) E24 Physical Man-Made Thing E19 Physical Object E4 Period 1,n 0,n 1,n 1,1 1,n 0,n 1,n 0,n 1,n 0,n 0,1 0,n 1,1 0,n P87 is identified by (identifies) 0,n P89 falls within (contains) 0,n Where was Lord Nelson’s ring when he died? 48

49 FORTH-ICS February 2014 CIDOC CRM 49 Activities: E9 Move P54 has current permanent location (is current permanent location of) E18 Physical Thing E7 Activity E9 Move E53 Place E19 Physical Object P53 has former or current location (is former or current location of) P55 has current location (currently holds) P26 moved to (was destination of) 1,n 0,n 1,n 0,1 0,n 1,n P27 moved from (was origin of) P25 moved (moved by) E55 Type P21 had general purpose (was purpose of) 0,n P20 had specific purpose (was purpose of) 0,n 0,1 E5 Period P7 took place at (witnessed) 1,n 0,n

50 FORTH-ICS February 2014 CIDOC CRM 50 An Instance of E9 Move P59B has section P26 moved to P27 moved from P25 moved P27 moved from E19 Physical Object Spanair EC-IYG E9 Move Flight JK126 E9 Move My walk 16-9-2006 13:45 P26 moved to E53 Place Madrid Airport E20 Person Martin Doerr E53 Place EC-IYG seat 4A E53 Place Frankfurt Airport-B10 How I came to Madrid…

51 FORTH-ICS February 2014 CIDOC CRM Activities: E11 Modification/E12 Production E57 MaterialE29 Design or Procedure E24 Physical Man-Made Thing E55 Type E18 Physical Thing E12 Production E11 Modification E7 Activity P68 usually employs (is usually employed by) 0,n P126 employed (was employed in) 0,n 1,n 0,n 1,n 0,n 1,n 1,1 P108 has produced (was produ ced by) P31 has modified (was mod ified by) P33 used specific technique (was used by) P45 co nsists of (is incor porated in) 0,n P69 is associated with 0,n P32 used general technique (was technique of) Things may be different from their plans Materials may be lost or altered P16 used specific object (was used for) E70 Thing P125 used object of type (was type of object used in) 51

52 FORTH-ICS February 2014 CIDOC CRM Ways of Changing Things E18 Physical Thing E11 Modification P111 added (was added by) E80 Part Removal P110 augmented (was augmented by) E24 Ph. M.-Made Thing P113 removed (was removed by) P112 diminished (was diminished by) E77 Persistent Item E81 Transformation E64 End of ExistenceE63 Beginning of Existence P124 transformed (was transformed by) P123 resulted in (resulted from) P92 brought into existence (was brought into existence by) P93 took out of existence (was taken o.o.e. by) P31 has modified (was modified by) E79 Part Addition 52

53 FORTH-ICS February 2014 CIDOC CRM E70 Thing E37 Mark E70 Thing E24 Physical M-M Thing E28 Conceptual Object E27 Site E25 Man-Made Feature E57 Material E21 Person E44 Place Appellation E32 Authority Document E46 Section Definition E38 Image E29 Design or Procedure E75 Conceptual Object Appellation E55 Type material immaterial E78 Collection E84 Information Carrier E73 Information Object E30 Right E50 Date E82 Actor Appellation Generalization E72 Legal Object E71 Man-Made Thing E18 Physical Thing E19Physical Object E26 Physical Feature E89 Propositional Object E90 Symbolic Object E42 Identifier E49 Time Appellation E51 Contact Point E31 Document E33 Linguistic Object E36 Visual Item E48 Place Name 47 Spatial Coordinates E45 Address E35 Title E20 Biological Object E22 Man-Made Object E58 Measurement Unit E56 Language E41 Appellation E34 Inscription 53

54 FORTH-ICS February 2014 CIDOC CRM Visual Content and Subject E24 Physical Man-Made Thing E55 Type E1 CRM Entity P62 depicts (is depicted by) P62.1 mode of depiction P65 shows visual item (is shown by) E36 Visual Item P138 represents (has representation) E73 Information Object E38 Image P67 refers to (is referred to by) E84 Information Carrier P128 carries (is carried by) P138.1 mode of depiction E37 Mark E34 Inscription 54

55 FORTH-ICS February 2014 CIDOC CRM Application: Mapping DC to the CRM (1) Example: DC Record about a Technical Report Type: text Title: Mapping of the Dublin Core Metadata Element Set to the CIDOC CRM Creator: Martin Doerr Publisher: ICS-FORTH Identifier: FORTH-ICS / TR 274 July 2000 Language: English 55

56 FORTH-ICS February 2014 CIDOC CRM Application: Mapping DC to the CRM (2) was created by is identified by E41 Appellation Name: Mapping of the Dublin Core Metadata Element Set to the CIDOC CRM E33 Linguistic Object Object: FORTH-ICS / TR-274 July 2000 E82 Actor Appellation Name: Martin Doerr E65 Creation Event: 0001 carried out by is identified by E82 Actor Appellation Name: ICS-FORTH E7 Activity Event: 0002 carried out by E55 Type Type: Publication has type was used for E75 Conceptual Object Appellation Name : FORTH-ICS / TR-274 July 2000 E55 Type Type: FORTH Identifier has type is identified by E56 Language Lang.: English has language E39 Actor Actor:0001 E39 Actor Actor:0002 is identified by (background knowledge not in the DC record) 56

57 FORTH-ICS February 2014 CIDOC CRM 57 Work (CRM Core). Category = E84 Information Carrier Classification =sculpture (visual work) Classification =plaster Identification =The Monument to Balzac (plaster) Description =Commissioned to honor one of France's greatest novelists, Rodin spent seven years preparing for Monument to Balzac. When the plaster original was exhibited in Paris in 1898, it was widely attacked. Rodin retired the plaster model to his home in the Paris suburbs. It was not cast in bronze until years after his death. Event Role in Event =P108B was produced by Identification= Rodin making Monument to Balzac in 1898 Event Type = E12 Production Participant Identification =Rodin, Auguste Identification =ID: 500016619 Participant Type = artists Participant Type = sculptors Date = 1898 Place = France (nation) Related event Role in Event =P134B was continued by Identification= Bronze casting Monument to Balzac in 1925 Event Role in Event =P16B was used for Identification= Bronze casting Monument to Balzac in 1925 Event Type = E12 Production Participant Identification =Rudier (Vve Alexis) et Fils Participant Type = companies Thing Present Identification =The Monument to Balzac (S.1296) Thing Present Type =bronze Thing Present Type =sculpture (visual work) Date = 1925 Related event Role in Event =P120B occurs after Identification= Rodin's death Relation To = Honore de Balzac Relation type refers to Artist (CRM Core). Category = E21 Person Classification = artists Classification = sculptors Identification =Rodin, Auguste Identification =ID: 500016619 Event Role in Event =P98B was born Identification= Rodin‘s birth Event Type = E67 Birth Date = 1840 Event Role in Event =P100B died in Identification= Rodin‘s death Event Type = E69_Death Date = 1917 Related event Role in Event =P120 occurs before Identification= Bronze casting Monument to Balzac in 1925 CRM Core Instances 57

58 FORTH-ICS February 2014 CIDOC CRM E52 Time-Span 1898 E53 Place France (nation) E21 Person Auguste Rodin E52 Time-Span 1840 E67 Birth Rodin’s birth E52 Time-Span 1917 P4 has time-span E69 Death Rodin’s death E12 Production Rodin making “Monument to Balzac” in 1898 E21 Person Honoré de Balzac E55 Type sculptors E84 Information Carrier The “Monument to Balzac” (plaster) E55 Type plaster E52 Time-Span 1925 E55 Type bronze E40 Legal Body Rudier (Vve Alexis) et Fils E12 Production Bronze casting “Monument to Balzac” in 1925 E55 Type companies E84 Information Carrier The “Monument to Balzac”(S1296) P108B was produced by P62 depicts P16B was used for P134 continued P2 has type P120B occurs after P4 has time-span P2 has type P100B died in P98B was born P4 has time -span P2 has type P14 carried out by P62 depicts P108B was produced by P2 has type P7 took place at P4 has time-span Merging metadata contents with CRM 58

59 FORTH-ICS February 2014 CIDOC CRM  Good ontologies can be extended without affecting interoperability.  Semantic interoperability in cultural heritage can be achieved with an “extensible ontology of relationships” and explicit event modeling  The CRM provides a shared explanation rather than the prescription of a common data structure.  The ontology is the language that S/W developers and museum experts can share. Therefore it needed interdisciplinary work. That is what CIDOC has provided. 59 Utility of the CIDOC CRM…

60 FORTH-ICS February 2014 CIDOC CRM Background 60 Integrated Argumentation Model:  explicitly represents factual argumentation  connects argumentation and facts expressed in a domain ontology (data in an information system)  distinguishes the logical order from the temporal one  distinguishes a proposition and the belief in it  allows for describing composite inferences

61 FORTH-ICS February 2014 CIDOC CRM Integrated Argumentation Model 61 IAM connects epistemological elements of argumentation with ontology P14 carried out by E52 Time-Span Belief has belief time E2 Temporal Entity E52 Time-Span P4 has time-span is believed by Argumentation resulted in or confirms Inference MakingBelief Adoption motivated State Observation Question is motivation of Proposition is Belief Value that (True, False, Unknown) E39 Actor P7 took place at E53 Place E7 Activity inherited property property IsA Subjective! Data Evaluation Simulation Here is the Information System and the Ontology! Here is the Researcher!

62 FORTH-ICS February 2014 CIDOC CRM Integrated Argumentation Model Epistemological considerations:  Material facts: history as meetings of people, things and information.  Material facts are supporting the discourse about possible pasts.  Material facts are the most objective information we have.  Material facts are carriers, evidence and constraints of the more vague and subjective social/intellectual processes and their interpretations we do not model! 62

63 FORTH-ICS February 2014 CIDOC CRM Proposed Epistemological Core Model of Sciences Categorical Models (terminologies) Possible Worlds and mechanisms of evolution Collective material behavior Actual world in data or mind Material world (CRM) Socio - Psychological world Factual world Observable world Non – discrete unlimited and unclassified material phenomena Reality inferred recognition Statistical reasoning Inductive reasoning Cognition models Innate or explicit Collective psychologica l behavior Collective world view Deductive reasoning Deductive reasoning Reasoning are also real world activities (CRM) !! 63

64 FORTH-ICS February 2014 CIDOC CRM CRMsci v1.2 http://www.ics.forth.gr/isl/CRMext/CRMsci.rdfs Inspired by INSPIRE, OBOE…. 64

65 FORTH-ICS February 2014 CIDOC CRM E13 Attribute Assignment S5 Inference Making S4 Observation S6 Data Evaluation S8 Categorical Hypothesis Building S7 Simulation or Prediction S1 Matter Removal S2 Sample Taking E7 Activity S19 Encounter Event 65 Scientific Events E80 Part Removal S3 Measurement by Sampling S21 Measurement E16 Measurement E5 Event S18 Alteration S17 Physical Genesis E12 Production E63 Beginning of Existence E11 Modification

66 FORTH-ICS February 2014 CIDOC CRM Observable Entity S10 Material Substantial S14 Fluid Body S11 Amount of Matter E70 Thing E18 Physical Thing S15 Observable Entity E2 Temporal Entity S13 Sample 66 S12 Amount of Fluid E77 Persistent Item E1 CRM Entity S15 Observable Entity Scope Note: This class comprises instances of E2 Temporal Entity or E77 Persistent Item, i.e. items or phenomena that can be observed, either directly by human sensory impression, or enhanced with tools and measurement devices, such as physical things, their behavior, states and interactions or events. S16 State E3 Condition State E55 Type S9 Property Type S20 / E26 Physical Feature E53 Place S22 Segment of MatterE27 SiteE25 Man-Made Feature

67 FORTH-ICS February 2014 CIDOC CRM Observable Entity S15 Observable Entity Scope Note (cont’d): Conceptual objects can be present in events by their carriers such as books, digital media, or even human memory. By virtue of this presence, properties of conceptual objects, such as number of words can be observed on their carriers. If the respective properties between carriers differ, either they carry different instances of conceptual objects or the difference can be attributed to accidental deficiencies in one of the carriers. In that sense even immaterial objects are observable. By this model we give credit to the fact that frequently, the actually observed carriers of conceptual objects are not explicitly identified in documentation, i.e., the actual carrier is assumed having existed but is unknown as an individual. 67

68 FORTH-ICS February 2014 CIDOC CRM Observable Entity E13 Attribute Assignment S5 Inference Making S4 Observation S6 Data Evaluation E7 Activity 68 E54 Dimension O9 observed property type S9 Property Type O10 assigned dimension S15 Observable Entity O12 has dimension O11 described E55 Type O16 observed value E1 CRM Entity E16 Measurement O24 measured E1 CRM Entity S19 Encounter Event P39 measured O8 observed S21 Measurement P140 assigned attribute to E53 Place E18 Physical Thing O21 has found at O19 has found object P141 assigned P40 observed dimension

69 FORTH-ICS February 2014 CIDOC CRM Encounter Event S4 Observation E7 Activity 69 E16 Measurement S19 Encounter Event S21 Measurement E53 Place E18 Physical Thing O21 has found at O19 has found object S20 / E26 Physical Feature E27 Site E25 Man-Made Feature S22 Segment of Matter O22 partly or completely contains E92 Spacetime Volume O23 is defined by S19 Encounter Event Scope Note: Activities of S4 Observation (substance) where an E39 Actor encounters an instance of E18 Physical Thing of a kind relevant for the mission of the observation or regarded as potentially relevant for some community (identity). This observation produces knowledge about the existence of the respective thing at a particular place in or on surrounding matter. This knowledge may be new to the group of people the actor belongs to. In that case we would talk about a discovery.

70 FORTH-ICS February 2014 CIDOC CRM Matter Removal S10 Material Substantial S14 Fluid Body S11 Amount of Matter E70 Thing E18 Physical Thing S19 Observable Entity S1 Matter Removal O5 removed S2 Sample Taking S13 Sample E7 Activity O3 sampled from O1 diminished S1 Matter Removal Scope Note: Activities that result in an instance of S10 Material Substantial being decreased by the removal of an amount of matter. O2 removed 70 E53 Place O4 sampled at E55 Type O20 sampled from type of part E2 Temporal Entity E77 Persistent Item O7 contains or confines O15 occupied P156 occupies

71 FORTH-ICS February 2014 CIDOC CRM Matter Removal S1 Matter Removal Scope Note (cont’d): Typical scenarios include the:  removal of a component or piece of a physical object  removal of an archaeological or geological layer  taking a tissue sample from a body or a sample of fluid from a body of water The removed matter may acquire a persistent identity of different nature beyond the act of its removal, such as becoming a physical object in the narrower sense. Such cases should be modeled by using multiple instantiation with adequate concepts of creating the respective items. 71

72 FORTH-ICS February 2014 CIDOC CRM Amount of Matter & Sample S11 Amount of Matter Scope Note: This class comprises fixed amounts of matter specified as some air, some water, some soil, etc., defined by the total and integrity of their material content. 72 S13 Sample Scope Note: This class comprises instances of S11 Amount of Matter taken from some instance of S10 Material Substantial with the intention to be representative for some material qualities of the instance of S10 Material Substantial or part of it it was taken from for further analysis. We typically regard a sample as ceasing to exist when the respective representative qualities become corrupted, such as the purity of a water sample or the layering of a bore core.

73 FORTH-ICS February 2014 CIDOC CRM Sample Taking S2 Sample Taking Scope Note: This class comprises the activity that results in taking an amount of matter as sample for further analysis from a material substantial such as a body of water, a geological formation or an archaeological object. The removed matter may acquire a persistent identity of different nature beyond the act of its removal, such as becoming a physical object in the narrower sense. The sample is typically removed from a physical feature which is used as a frame of reference, the place of sampling. In case of non-rigid Material Substantials, the source of sampling may regarded not to be modified by the activity of sample taking. 73

74 FORTH-ICS February 2014 CIDOC CRM Material Substantial S10 Material Substantial S14 Fluid BodyS11 Amount of MatterE18 Physical Thing S1 Matter Removal S2 Sample Taking E7 Activity O3 sampled from O1 diminished O2 removed 74 E53 Place O4 sampled at E55 Type O20 sampled from type of part O15 occupied P156 occupies P46 is composed of E3 Condition State E57 Material O7 contains or confines P44 has condition P45 consists of S12 Amount of Fluid O6 forms former or current part

75 FORTH-ICS February 2014 CIDOC CRM Material Substantial S10 Material Substantial Scope Note: This class comprises constellations of matter with a relative stability of any form sufficient to associate them with a persistent identity, such as being confined to certain extent, having a relative stability of form or structure, or containing a fixed amount of matter. In particular, it comprises physical things in the narrower sense and fluid bodies. It is an abstraction of physical substance for solid and non-solid things of matter. GH2: Should we add „at a specific time“? without the time I have troubles understanding the „relative stability of any form” 75

76 FORTH-ICS February 2014 CIDOC CRM Physical Genesis S18 Alteration E18 Physical Thing S17 Physical Genesis E63 Beginning of Existence S17 Physical Genesis Scope Note: Events or processes that result in (generate) physical things, man-made or natural, coming into being in the form by which they are later identified. The creation of a new physical item, at the same time, can be a result of an alteration (modification) – it can become a new thing due to an alteration activity. 76 E12 Production E5 Event E11 Modification O17 generated E24 Physical Man-Made Thing O18 altered P31 has modified O13 triggers S16 State O14 initializes

77 FORTH-ICS February 2014 CIDOC CRM Part of Scientific Observation Model E13 Attribute Assignment E55 Type S5 Inference Making S4 Observation S10 Material Substantial S14 Fluid Body S11 Amount of Matter E54 Dimension E18 Physical Thing P2 has type S9 Property Type O8 observed S6 Data Evaluation S8 Categorical Hypothesis Building S7 Simulation or Prediction S15 Observable Entity O11 described S1 Matter Removal O5 removed S2 Sample Taking S13 Sample E7 Activity S19 Encounter Event O19 has found object O10 assigned dimension O12 has dimension 77 O9 observed property type O16 observed value E1 CRM Entity E55 Type S21 Measurement E55 Type O20 sampled from type of part E53 Place O3 sampled from O2 removed O1 diminished O24 measured S12 Amount of Fluid O6 forms former or current part of O15 occupied O4 sampled at

78 FORTH-ICS February 2014 CIDOC CRM Applications Informed by the IAM model (argumentation) EU FP7 - PSP InGeoClouds o European Space Agency: satellite data EU FP7-INFRASTRUCTURES-2012-1 ARIADNE o Supermodel for CRMarchaeo EU - FP7 - CP & CSA iMarine o Informs and complements MarineTLO o Extended MarineTLO used in LifeWatch Greece, being promoted to LifeWatch 78

79 IFORTH-ICS May 2014 CRM archaeo : Modelling Context, Stratigraphic Unit, Excavated Matter CRMarchaeo Center for Cultural Informatics, Institute of Computer Science Foundation for Research and Technology - Hellas Martin Doerr Rethymnon, Crete February 17-28, 2014 RESTeCH I

80 FORTH-ICS February 2014 CIDOC CRM Excavation Process Unit A1 Excavation Process Unit E7 Activity S11 Amount of Matter E29 Design or Procedure P33 used specific technique P32 used general technique P17 was motivated by E73 Information Object P125 used object of type P32 used general technique E55 Type P13 destroyed E26 Physical Feature AP4 produced surface Substance: doing Identity: Actor, location, temporal coherence Unity: begin/end (maybe documented) Intentional, Declarative E55 Type P21 had general purpose SP2 Phenomenal Place AP3 excavated SP6 Declarative Place S11 Amount of Matter AP2 discarded intoAP1 produced “find Solomon’s Temple” “a heap”“a basket” preserved part or total of matter Q11 approximates P67 refers to A9 Segment of Matter A8 Stratigraphic Unit AP5 cut tools methodology technique research question S10 Material Substantial “surface” 3D excavated area planned area for drawings before excavating about where to excavate segment of Matter that happened to be at the excavated place AP21 occupied E55 Type 80 S40 Encounter Event P9 consists of A3 Stratigraphic Interface AP6 intended to approximate

81 FORTH-ICS February 2014 CIDOC CRM Excavation Process Unit A1 Excavation Process Unit Scope Note: This class comprises activities of excavating in the sense of archaeology which are documented as a coherent set of actions of progressively recording and removing matter from a pre-specified location under specific rules. Typically, an excavation process unit would be terminated if significant discontinuities of substance or finds come to light, or if the activity should be interrupted due to external factors, such as end of a working day. In other cases, the termination would be based on predefined physical specifications, such as the boundaries of a maximal volume of matter intended to be excavated in one unit of excavation. Depending on the methodology, an instance of A1 Excavation Process Unit may intend to remove matter only within the boundaries of a particular stratigraphic unit, or it may follow a pre-declared spatial extent such as a trench. It may only uncover, clean or expose a structure or parts of it. The process of excavation results in the production of a set of recorded (documentation) data that should be sufficient to provide researchers enough information regarding the consistence and spatial distribution of the excavated Segment of Matter and things and features embedded in it. Some parts or all of the removed physical material (S11 Amount of Matter) may be dispersed, whereas others may be kept in custody in the form of finds or samples, while others (such as parts of walls) may be left at the place of their discovery. The data produced by an instance of excavation process unit should pertain to the material state of matter at excavation time only and should well be distinguished from subsequent interpretation about the causes for this state of matter. 81

82 FORTH-ICS February 2014 CIDOC CRM Stratigraphic Genesis A1 Excavation Process Unit E7 Activity A8 Stratigraphic Unit A3 Stratigraphic Interface A4 Stratigraphic Genesis S10 Material Substantial S11 Amount of Matter AP1 produced AP7 produced AP9 took matter from 82 A5 Stratigraphic Modification Event S38 Physical Genesis E26 Physical Feature AP13 has stratigraphic relation AP8 disturbed A2 Stratigraphic Deposit Unit AP12 is confined by E63 Beginning of Existence S39 Alteration A9 Segment of Matter E18 Physical Thing AP24 is or contains remains of AP11 has physical relation AP10 is part of

83 FORTH-ICS February 2014 CIDOC CRM Stratigraphic Genesis A4 Stratigraphic Genesis Scope Note: A process resulting in the displacement of a limited amount of matter which has settled into a relatively stable form, often a deposition, consisting of homogeneous parts. Typology of processes. 83

84 FORTH-ICS February 2014 CIDOC CRM Embedding A7 Embedding E3 Condition State E18 Physical Thing E5 Event AP17 is found by “state, refinement of position” “reference space that is relative to the Context Stuff” “positioning” AP15 has found object “the Physical Object has a position at least up to the point of discovery” A1 Excavation Process Unit P9 consists of 84 S40 Encounter Event AP19 is embedding in AP20 is embedding atAP18 is embedding of A2 Stratigraphic Deposit Unit SP6 Declarative Place

85 FORTH-ICS February 2014 CIDOC CRM Embedding S40 Encounter Event Scope Note: This class compromises activities of S4 Observation (S) where an E39 Actor encounters an instance of E18 Physical Thing of a kind relevant for the mission of the observation or regarded as potentially relevant for some community (I). This observation produces knowledge about the existence of the respective thing at a particular place in or on surrounding matter. This knowledge may be new to the group of people the actor belongs to. In that case we would talk about a discovery. The observer may recognize or assign an individual identity of the thing encountered or regard only the type as noteworthy in the associated documentation or report. In archaeology there is a particular interest if an object is found “in situ”, i.e. if its embedding in the surrounding matter supports the assumption that the object was not moved since the archaeologically relevant deposition event. The surrounding matter with the relative position of the object in it as well as the absolute position and time of the observation may be recorded in order to enable inferences about the history of the E18 Physical Thing. 85

86 FORTH-ICS February 2014 CIDOC CRM Embedding A7 Embedding Scope Note: This class comprises the states of E18 Physical Things during their complete or partial embedding in one or more A2 Stratigraphic Deposit Units. The condition state can be documented directly through the property chain E18 Physical Thing ->AP18 is embedding of (is embedded) ->A7 Embedding -> AP19 is embedding in (contains embedding) -> A2 Stratigraphic Deposit Unit (surrounding matter) or positioning methods that document the position of an object within the surrounding matter at a specific time. 86

87 FORTH-ICS February 2014 CIDOC CRM Conclusions CRM Sci provides a comprehensive model for observation metadata regardless science and method. CRMArchaeo allows for a common representation of archaeological records and survey data, widely independent of local methodology. Still to be done: Specializations into analytical methods and reference data sets. Links: CRMarchaeo will be available soon at http://www.ics.forth.gr/isl/CRMext/CRMarchaeo.rdfs 87


Download ppt "IFORTH-ICS May 2014 CIDOC CRM Workshop Data Objects & Semantics Center for Cultural Informatics, Institute of Computer Science Foundation for Research."

Similar presentations


Ads by Google