Transitivity of properties C-E Ore. Transitivity in a typed system Explicit – x:A, y:A, z:A P(x,y) & P(y,z) -> P(x,z) Implicit or constrained – Property.

Slides:



Advertisements
Similar presentations
Music Encoding Initiative (MEI) DTD and the OCVE
Advertisements

Information Modelling MOLES Metadata Objects for Linking Environmental Sciences S. Ventouras Rutherford Appleton Laboratory.
CRMarchaeo CRMarchaeo v1.2.1
F25 Performance Plan F1 Work F15 Complex Work F14 Individual Work F2 Expression F22 Self Contained Expression R1 is logical successor of (has successor)
8/3/20071 E65 Creation F30 Work Conception F1 Work F21 Complex Work Work F46 Individual Work R21 initiated (was initiated by) F2 Expression F20 Self Contained.
1 CIDOC CRM + FRBR ER = FRBR OO … an equation for a harmonised view of museum information and bibliographic information Martin Doerr First CASPAR Seminar.
RDF Schemata (with apologies to the W3C, the plural is not ‘schemas’) CSCI 7818 – Web Technologies 14 November 2001 Van Lepthien.
Bibliographic Relationships and Bibliographic Families.
Object-oriented modeling Class/Object Diagrams
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall A.1.
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
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.
ACQUISITION INFORMATION P52 has current owner (is current owner of) P51 has former or current owner (is former or current owner of) E55 TypeE1 CRM EntityE62.
Winter 2007SEG2101 Chapter 41 Chapter 4 SDL – Structure and Behavior.
IBM WebSphere survey Kristian Bisgaard Lassen. University of AarhusIBM WebSphere survey2 Tools  WebSphere Application Server Portal Studio Business Integration.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
7M822 UML Class Diagrams advanced concepts 15 September 2008.
PRJ566: PROJECT PLANNING AND MANAGEMENT Class Diagrams.
UML Class Diagrams: Basic Concepts. Objects –The purpose of class modeling is to describe objects. –An object is a concept, abstraction or thing that.
Chapter 4 The Enhanced Entity-Relationship (EER) Model
ICS – FORTH, August 31, 2000 Why do we need an “Object Oriented Model” ? Martin Doerr Atlanta, August 31, 2000 Foundation for Research and Technology -
Harmonising without Harm: towards an object-oriented formulation of FRBR aligned on the CIDOC CRM ontology Maja Žumer (University of Ljubljana) & Patrick.
Grant Number: IIS Institution of PI: Arizona State University PIs: Zoé Lacroix Title: Collaborative Research: Semantic Map of Biological Data.
INF 384 C, Spring 2009 Ontologies Knowledge representation to support computer reasoning.
Contributed Capital 12. Management Issues Related to Contributed Capital OBJECTIVE 1: Identify and explain the management issues related to contributed.
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.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Systems Analysis and Design in a Changing World, Fifth Edition
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
Object-Oriented Software Development F Software Development Process F Analyze Relationships Among Objects F Class Development F Class Design Guidelines.
CS3773 Software Engineering Lecture 04 UML Class Diagram.
1 Exploring time and space in the annotation of museum catalogues: The Sloane virtual exhibition experience Stephen Stead Vienna November 2014 University.
UML Class Diagram Trisha Cummings. What we will be covering What is a Class Diagram? Essential Elements of a UML Class Diagram UML Packages Logical Distribution.
9-1 © Prentice Hall, 2007 Chapter 9: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
What is Object-Oriented?  Organization of software as a collection of discreet objects that incorporate both data structure and behavior.
Object Oriented Analysis: Associations. 2 Object Oriented Modeling BUAD/American University Class Relationships u Classes have relationships between each.
Out and About with the CIDOC CRM: The Lessons and Results of the CRM Dissemination and Training programme Stephen Stead, Paveprime Ltd.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
7-1 © Prentice Hall, 2007 Topic 7: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
1 SWE Introduction to Software Engineering Lecture 14 – System Modeling.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
ICS-FORTH September, The CIDOC CRM Format Martin Doerr Washington, Sept. 22, 1999 Foundation for Research and Technology - Hellas Institute of Computer.
F25 Performance Plan F1 Work F15 Complex Work F14 Individual Work F2 Expression F22 Self Contained Expression R1 is logical successor of (has successor)
ICS-FORTH September 10, Modelling Intellectual Processes: The object-orient FRBR Model Martin Doerr Gothenburg, Sweden September 12, 2006 Corrections.
WELCOME TO OUR PRESENTATION UNIFIED MODELING LANGUAGE (UML)
DESIGN PROCESS AND CONCEPTS. Design process s/w design is an iterative process through which requirements are translated into a “blueprint” for constructing.
UML (Unified Modeling Language)
Harmonized EDM-CRM-FRBRoo
Harmonized EDM-CRM-FRBRoo-CRMdig
Harmonized EDM-CRM-FRBRoo
Harmonized EDM-CRM-FRBRoo
Harmonized EDM-CRM-FRBRoo
FRBRoo and performing arts
CRMinf: Argumentation and Scholarly Reading
RDA, linked data, and update on development
Appellations, Authorities, and Access
Ontology.
Chapter 20 Object-Oriented Analysis and Design
Harmonized EDM-CRM-FRBRoo
Appendix A Object-Oriented Analysis and Design
Harmonized EDM-CRM-FRBRoo
Database Design Hacettepe University
IENE – INTERCULTURAL EDUCATION OF NURSES AND MEDICAL STAFF IN EUROPE
The new RDA: resource description in libraries and beyond
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Appendix A Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Modeling Properties of Properties in the CIDOC CRM RDF encoding
Presentation transcript:

Transitivity of properties C-E Ore

Transitivity in a typed system Explicit – x:A, y:A, z:A P(x,y) & P(y,z) -> P(x,z) Implicit or constrained – Property P: A -> B & – C subclass of or equal to A & – C subclass of or equal to B & – x:C, y:C, z:C P(x,y) & P(y,z) -> P(x,z)

P5consists ofYESEXPE3E3 Condition StateE3E3 Condition State P9consists ofYESEXPE4E4 PeriodE4E4 Period P10falls withinYESEXPE4E4 PeriodE4E4 Period P134continuedNOEXPE7E7 ActivityE7E7 Activity P69has association withYESEXP E29E29 Design or Procedure E29E29 Design or Procedure P86falls withinYESEXPE52E52 Time-SpanE52E52 Time-Span P89falls withinYESEXPE53E53 PlaceE53E53 Place P106is composed ofYESEXPE90E90 Symbolic ObjectE90E90 Symbolic Object Explicit, possibly transitive properties 1

P114is equal in time toYESEXPE2E2 Temporal EntityE2E2 Temporal Entity P115finishesYESEXPE2E2 Temporal EntityE2E2 Temporal Entity P116startsYESEXPE2E2 Temporal EntityE2E2 Temporal Entity P117occurs duringYESEXPE2E2 Temporal EntityE2E2 Temporal Entity P118overlaps in time withNOEXPE2E2 Temporal EntityE2E2 Temporal Entity P119meets in time withNOEXPE2E2 Temporal EntityE2E2 Temporal Entity P120occurs beforeYESEXPE2E2 Temporal EntityE2E2 Temporal Entity P121overlaps withNOEXPE53E53 PlaceE53E53 Place P122borders withNOEXPE53E53 PlaceE53E53 Place Explicit, possibly transitive properties 2

P127has broader termYESEXPE55E55 TypeE55E55 Type P130shows features ofNOEXPE70E70 ThingE70E70 Thing P73is translation ofYESEXPE33E33 Linguistic ObjectE33E33 Linguistic Object P132overlaps withNOEXPE4E4 PeriodE4E4 Period P133is separated fromNOEXPE4E4 PeriodE4E4 Period P139has alternative formNOEXPE41E41 AppellationE41E41 Appellation P148has componentYESEXP E89E89Propositional Object E89E89 Propositional Object P150 defines typical parts of NOEXPE55E55 TypeE55E55 Type P152has parentNOEXPE21E21 PersonE21E21 Person Explicit, possibly transitive properties 3

P1is identified by NOIMPE1E1 CRM EntityE41E41 Appellation P48has preferred identifier NOIMPE1E1 CRM EntityE42E42 Identifier P102has title NOIMPE71E71 Man-Made ThingE35E35 Title P2has type NOIMPE1E1 CRM EntityE55E55 Type P137exemplifies NOIMPE1E1 CRM EntityE55E55 Type P15was influenced NOIMPE7E7 ActivityE1E1 CRM Entity P17was motivated NOIMPE7E7 ActivityE1E1 CRM Entity P136was based on NOIMPE83E83 Type CreationE1E1 CRM Entity P20had specific purposeNOIMPE7E7 ActivityE5E5 Event Implicit, possibly transitive properties 1

P62depicts NOIMP E24E24 Physical Man-Made Thing E1E1 CRM Entity P67refers to NOIMPE89E89 Propositional ObjectE1E1 CRM Entity P70documents NOIMPE31E31 DocumentE1E1 CRM Entity P71lists NOIMPE32E32 Authority DocumentE1E1 CRM Entity P129is about NOIMPE89E89 Propositional ObjectE1E1 CRM Entity P138represents NOIMPE36E36 Visual ItemE1E1 CRM Entity P101had as general use NOIMPE70E70 ThingE55E55 Type P103was intended for NOIMPE71E71 Man-Made ThingE55E55 Type P105right held byNOIMPE72E72 Legal ObjectE39E39 Actor Implicit, possibly transitive properties 2

P51 has former or current owner NOIMPE18E18 Physical ThingE39E39 Actor P165 incorporates YESIMPE73E73 Information ObjectE90E90 Symbolic Object P107 has current or former member NOIMPE74E74 GroupE39E39 Actor P140 assigned attribute to NOIMP E13E13 Attribute Assignment E1E1 CRM Entity P39measured NOIMPE16E16 MeasurementE1E1 CRM Entity P41classified NOIMPE17E17 Type AssignementE1E1 CRM Entity P141assigned NOIMP E13E13 Attribute Assignement E1E1 CRM Entity P155 has co-reference target NOIMP E91E91 Co-Reference Assignment E1E1 CRM Entity P52has current owner NOIMPE18E18 Physical ThingE39E39 Actor Implicit, possibly transitive properties 3

P134 continued (was continued by) Domain:E7 ActivityE7 Range:E7 ActivityE7 Subproperty of:E7 Activity. P15 was influenced by (influenced): E1 CRM EntityE7P15E1 Quantification:many to many (0,n:0,n) Scope note:This property associates two instances of E7 Activity, where the domain is considered as an intentional continuation of the range. A continuation of an activity may happen when the continued activity is still ongoing or after the continued activity has completely ended. The continuing activity may have started already before it decided to continue the other one. Continuation implies a coherence of intentions and outcomes of the involved activities. Examples: the construction of the Kölner Dom (Cologne Cathedral) (E7), abandoned in the 15th century, was continued by construction in the 19th century adapting the initial plans so as to preserve the intended appearance (E7)

P73 has translation (is translation of) Domain:E33 Linguistic ObjectE33 Range:E33 Linguistic ObjectE33 Subproperty of:E70 Thing. P130i features are also found on: E70 ThingE70P130E70 Quantification:one to many (0,n:0,1) Scope note:This property describes the source and target of instances of E33Linguistic Object involved in a translation. When a Linguistic Object is translated into a new language it becomes a new Linguistic Object, despite being conceptually similar to the source object. Examples: “Les Baigneurs” (E33) has translation “The Bathers” (E33) In First Order Logic: P73(x,y) ⊃ E33(x) P73(x,y) ⊃ E33(y) P73(x,y) ⊃ P130(y,x)

P139 has alternative form Domain:E41 AppellationE41 Range:E41 AppellationE41 Quantification:many to many (0,n:0,n) Scope note: This property establishes a relationship of equivalence between two instances of E41 Appellation independent from any item identified by them. It is a dynamic asymmetric relationship, where the range expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. The relationship is not transitive. The equivalence applies to all cases of use of an instance of E41 Appellation. Multiple names assigned to an object, which are not equivalent for all things identified with a specific instance of E41 Appellation, should be modelled as repeated values of P1 is identified by (identifies). P139.1 has type allows the type of derivation, such as “transliteration from Latin 1 to ASCII” be refined.. Examples: "Martin Doerr" (E41) has alternative form "Martin Dörr" (E41) has type Alternate spelling (E55) "Гончарова, Наталья Сергеевна" (E41) has alternative form "Gončarova, Natal´â Sergeevna" (E41) has type ISO 9:1995 transliteration (E55) “Αθήνα” has alternative form “Athina” has type transcription.

P148 has component (is component of) Domain:E89 Propositional ObjectE89 Range:E89 Propositional ObjectE89 Quantification:(0:n,0:n) Scope note:This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object. Examples: Dante’s “Divine Comedy” (E89) has component Dante’s “Hell” (E89) In First Order Logic: P148(x,y) ⊃ E89(x) P148(x,y) ⊃ E89(y)

P150 defines typical parts of (defines typical wholes for) Domain:E55 Type Range:E55 Type Quantification:many to many (0,n:0,n) Scope note:The property “broaderPartitive” associates an instance of E55 Type “A” with an instance of E55 Type “B”, when items of type “A” typically form part of items of type “B”, such as “car motors” and “cars”. It allows Types to be organised into hierarchies. This is the sense of "broader term partitive (BTP)" as defined in ISO 2788 and “broaderPartitive” in SKOS. Examples: Car motors (E55) defines typical parts of cars (E55) In First Order Logic: P150(x,y) ⊃ (E55 Type) P150(x,y) ⊃ E55(y) The scope note is not well formulated

P15 was influenced by (influenced) Domain:E7 ActivityE7 Range:E1 CRM EntityE1 Superproperty of:E7 Activity. P16 used specific object (was used for): E70 ThingE7P16E70 E7E7 Activity. P17 was motivated by (motivated): E1 CRM EntityP17E1 E7E7 Activity. P134 continued (was continued by): E7 ActivityP134E7 E83E83 Type Creation. P136 was based on (supported type creation): E1 CRM EntityP136E1 Quantification: many to many (0,n:0,n) Scope note:This is a high level property, which captures the relationship between an E7 Activity and anything that may have had some bearing upon it. The property has more specific sub properties. Examples: the designing of the Sydney Harbour Bridge (E7) was influenced by the Tyne bridge (E22) In First Order Logic: P15 (x,y) ⊃ E7(x) P15 (x,y) ⊃ E1(y)

P17 was motivated by (motivated) Domain:E7 ActivityE7 Range:E1 CRM EntityE1 Subproperty of: E7 Activity. P15 was influenced by (influenced): E1 CRM EntityE7P15E1 Quantification:many to many (0,n:0,n) Scope note:This property describes an item or items that are regarded as a reason for carrying out the E7 Activity. For example, the discovery of a large hoard of treasure may call for a celebration, an order from head quarters can start a military manoeuvre. Examples: the resignation of the chief executive (E7) was motivated by the collapse of SwissAir (E68). the coronation of Elizabeth II (E7) was motivated by the death of George VI (E69) In First Order Logic: P17(x,y) ⊃ E7(x) P17(x,y) ⊃ E1(y) P17 (x,y) ⊃ P15(x,y)

P136 was based on (supported type creation) Domain:E83 Type CreationE83 Range:E1 CRM EntityE1 Subproperty of:E7 Activity. P15 was influenced by (influenced): E1 CRM EntityE7P15E1 Quantification:many to many (0,n:0,n) Scope note:This property identifies one or more items that were used as evidence to declare a new E55 Type. The examination of these items is often the only objective way to understand the precise characteristics of a new Type. Such items should be deposited in a museum or similar institution for that reason. The taxonomic role renders the specific relationship of each item to the Type, such as "holotype" or "original element". Examples: the taxon creation of the plant species ‘Serratula glauca Linné, 1753.’ (E83) was based on Object BM of the Clayton Herbarium (E20) in the taxonomic role original element (E55) In First Order Logic: P136(x,y) ⊃ E83(x) P136(x,y) ⊃ E1(y) P136(x,y,z) ⊃ [P136(x,y) ∧ E55(z)] P136(x,y) ⊃ P15(x,y)

P105 right held by (has right on) Domain:E72 Legal ObjectE72 Range:E39 ActorE39 Superproperty of: E18 Physical Thing.P52 has current owner (is current owner of): E39 ActorE18P52E39 Quantification:many to many (0,n:0,n) Scope note:This property identifies the E39 Actor who holds the instances of E30 Right to an E72 Legal Object. It is a superproperty of P52 has current owner (is current owner of) because ownership is a right that is held on the owned object. P105 right held by (has right on) is a shortcut of the fully developed path from E72 Legal Object through P104 is subject to (applies to), E30 Right, P75 possesses (is possessed by) to E39 Actor. Examples: Beatles back catalogue (E73) right held by Michael Jackson (E21) In First Order Logic: P105(x,y) ⊃ E72(x) P105(x,y) ⊃ E39(y)

P51 has former or current owner (is former or current owner of) Domain:E18 Physical ThingE18 Range:E39 ActorE39 Superproperty of:E18 Physical Thing. P52 has current owner (is current owner of): E39 ActorE18P52E39 Quantification:many to many (0,n:0,n) Scope note:This property identifies the E39 Actor that is or has been the legal owner (i.e. title holder) of an instance of E18 Physical Thing at some time. The distinction with P52 has current owner (is current owner of) is that P51 has former or current owner (is former or current owner of) does not indicate whether the specified owners are current. P51 has former or current owner (is former or current owner of) is a shortcut for the more detailed path from E18 Physical Thing through P24 transferred title of (changed ownership through), E8 Acquisition, P23 transferred title from (surrendered title through), or P22 transferred title to (acquired title through) to E39 Actor. Examples: paintings from the Iveagh Bequest (E18) has former or current owner Lord Iveagh (E21) In First Order Logic: P51(x,y) ⊃ E18(x) P51(x,y) ⊃ E39(y)