Move S15 Observable Entity to CRM?

Slides:



Advertisements
Similar presentations
ARIADNE is funded by the European Commission's Seventh Framework Programme WP 14 Addressing Complexity Martin Doerr, Sorin Hermon, Gerald Hiebel, Athina.
Advertisements

A Brief Presentation of PRESS OO For the CIDOC CRM SIG and FRBR/CRM Harmonisation WG 21 October 2013.
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.
ISAAR (CPF) and a possible mapping to CIDOC CRM Based on and “State of.
Visualization of Thematic Units in KR Schemata Mina AKAISHI Meme Media Laboratory Hokkaido University, JAPAN.
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.
Object–Orientated Design. OOP Design Describe the following: a computer a university Usually the most natural way to describe a task is to list the entities.
Fundamentals, Design, and Implementation, 9/e Chapter 3 Entity-Relationship Data Modeling: Process and Examples Instructor: Dragomir R. Radev Fall 2005.
9-1 Chapter Nine MEASUREMENT SCALES. 9-2 Scaling and Consideration What is Scaling? –Scaling is assigning numbers to indicants of the properties of objects.
Methodology Logical Database Design for the Relational Model
6. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain how events can be used to identify use cases that define requirements.
Fundamentals, Design, and Implementation, 9/e COS 346 Day 3.
Object Oriented Concepts. Movement toward Objects Instead of data-oriented or process-oriented Analysis, many firms are now moving to object-oriented.
Systems Analysis and Design in a Changing World, Tuesday, Feb 27
CRMsci CRM sci : the Scientific Observation Model Center for Cultural Informatics, Institute of Computer Science Foundation for Research and Technology.
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.
Database Processing: Fundamentals, Design and Implementation, 9/e by David M. KroenkeChapter 3/1 Copyright © 2004 Please……. No Food Or Drink in the class.
How Wikidata helps power projects like Histropedia.
The CIDOC Conceptual Reference Model A core-ontology for information integration Karl H. Lampe, Zoologisches Forschungsmuseum Alexander Koenig (ZFMK) Bonn/Germany.
Unified Modeling Language © 2002 by Dietrich and Urban1 ADVANCED DATABASE CONCEPTS Unified Modeling Language Susan D. Urban and Suzanne W. Dietrich Department.
1 Exploring time and space in the annotation of museum catalogues: The Sloane virtual exhibition experience Stephen Stead Vienna November 2014 University.
Chapter 11 & 12 Entity-Relationship (E-R) Model Characteristics of E-R Model Components of E-R Model Example of E-R Model Enhanced E-R Model.
What is Object-Oriented?  Organization of software as a collection of discreet objects that incorporate both data structure and behavior.
1 Chapter 17 Methodology - Local Logical Database Design.
Out and About with the CIDOC CRM: The Lessons and Results of the CRM Dissemination and Training programme Stephen Stead, Paveprime Ltd.
Fact Table The fact table stores business events. The attributes explain the conditions of the entity at the time the business event happened.
Ch 9 – Properties and Attributes of Functions 9.4 – Operations with Functions.
Invited report Digital Presentation and Preservation of Cultural and Scientific Heritage (DiPP2012) Conference 18 Sep 2012, Veliko Tarnovo, Bulgaria Types.
ICS-FORTH September, The CIDOC CRM Format Martin Doerr Washington, Sept. 22, 1999 Foundation for Research and Technology - Hellas Institute of Computer.
A CRM-based Ontology for Narratives 1 Carlo Meghini, Valentina Bartalesi.
1 Database Design Entity-Relationship Modeling N. Ilayaraja PSG Tech.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
CRMsci: the Scientific Observation Model
Harmonized EDM-CRM-FRBRoo
Relational Database Design by ER- and EER-to- Relational Mapping
Business System Development
DATA REQIREMENT ANALYSIS
The Movement To Objects
CRMsci: the Scientific Observation Model
Harmonized EDM-CRM-FRBRoo-CRMdig
©CIDOC 2013 Event oriented analysis and modeling in documentation CIDOC CRM and FRBRoo This module provides an introduction to the CIDOC Conceptual Reference.
From FRBR to FRBROO through CIDOC CRM…
CRMsci: the Scientific Observation Model
Harmonized EDM-CRM-FRBRoo
Domain Model Refinement
Harmonized EDM-CRM-FRBRoo
FRBRoo and performing arts
ASSIGNMENT NO.-2.
Shapley Value Regression
Tips Need to Consider When Organizing a College Event
UML UML Data Modeling.
CRMarchaeo Modelling Context, Stratigraphic Unit, Excavated Matter
Chapter 3 The Relational Model.
Domain Class Diagram Chapter 4 Part 2 pp
פחת ורווח הון סוגיות מיוחדות תהילה ששון עו"ד (רו"ח) ספטמבר 2015
Issue 326 Temporal entities
ماجستير إدارة المعارض من بريطانيا
RDA and practical linked open data
Harmonized EDM-CRM-FRBRoo
Move S15 Observable Entity to CRM?
Systems Analysis – ITEC 3155 Modeling System Requirements – Part 2
CRMarchaeo Issues Updates
The new RDA: resource description in libraries and beyond
Symbols Classes Relationships Name
ER Example Expressed as IMM Core Instance Specifications
Modeling Properties of Properties in the CIDOC CRM RDF encoding
Ontology Lezz. 4-6.
The CIDOC CRM Recent Developments
Chapter 3 The Relational Model
Chapter 20 Object-Oriented Concepts and Principles
Presentation transcript:

Move S15 Observable Entity to CRM? Some possible simplifications of CRMSci Issue 293: Dimension to be discussed at the 38th CIDOC CRM and 31th FRBR CRM meeting Christian-Emil Ore

E13 Attribute Assignment Current S15 Observable Entity – CRM and CRMSci P39 measured E7 Activity P140 assigned attribute to E13 Attribute Assignment P141 assigned E1 CRM Entity O16 observed value E16 Measurement S4 Observation O8 observed O9 observed property type S15 Observable Entity S9 Property Type E55 Type S19 Encounter Event O19 has found object P40 observed dimension O21 has found at E18 Physical Thing E70 Thing E53 Place O24 measured S21 Measurement O12 has dimension ? E54 Dimension P43 has dimension

E13 Attribute Assignment New Exx Observable Entity in CRM moved from CRMSci P39 measured E7 Activity P140 assigned attribute to E13 Attribute Assignment P141 assigned E1 CRM Entity O16 observed value E16 Measurement S4 Observation O8 observed O9 observed property type Exx Observable Entity S9 Property Type E55 Type S19 Encounter Event O19 has found object P40 observed dimension O21 has found at E18 Physical Thing E2 Temporal Entity E53 Place O24 measured S21 Measurement E77 Persistent Item Pxx has dimension ? P43 has dimension E70 Thing E54 Dimension

E13 Attribute Assignment New Exx Observable Entity – CRMSci simplification E7 Activity P140 assigned attribute to E13 Attribute Assignment P141 assigned E1 CRM Entity O16 observed value E16 Measurement S4 Observation O8 observed O9 observed property type Exx Observable Entity S9 Property Type E55 Type S19 Encounter Event O19 has found object P40 observed dimension O21 has found at E18 Physical Thing E2 Temporal Entity E53 Place P39 measured E77 Persistent Item Pxx has dimension ? P43 has dimension E70 Thing E54 Dimension

E13 Attribute Assignment New Exx Observable Entity – CRM adjustment alternative 1 (not recommended) E7 Activity P140 assigned attribute to E13 Attribute Assignment P141 assigned E1 CRM Entity O16 observed value E16 Measurement S4 Observation O8 observed O9 observed property type Exx Observable Entity S9 Property Type E55 Type S19 Encounter Event O19 has found object P40 observed dimension O21 has found at E18 Physical Thing E2 Temporal Entity E53 Place P39 measured E77 Persistent Item Pxx has dimension E70 Thing E54 Dimension

E13 Attribute Assignment New Exx Observable Entity – CRM adjustment alternative 2 (preferred) E7 Activity P140 assigned attribute to E13 Attribute Assignment P141 assigned E1 CRM Entity O16 observed value S4 Observation E16 Measurement O8 observed O9 observed property type Exx Observable Entity S9 Property Type E55 Type S19 Encounter Event O19 has found object P40 observed dimension O21 has found at E18 Physical Thing E2 Temporal Entity E53 Place P39 measured E77 Persistent Item Pxx has dimension E70 Thing E54 Dimension

E13 Attribute Assignment New Exx Observable Entity – CRM only E7 Activity P140 assigned attribute to E13 Attribute Assignment P141 assigned E1 CRM Entity E16 Measurement Exx Observable Entity P40 observed dimension E2 Temporal Entity P39 measured E77 Persistent Item P43 has dimension E70 Thing E54 Dimension

New Exx Observable Entity – Summing up Delete S4 Observable Entity from CRMSci Introduce new Exx Observable Entity in CRM Subclass of E1 CRM Entity Superclass of E2 Temporal Entity, E77 Persistent Item New domain for P43 has dimension, was E70 Thing, should be Exx Observable Entity Delete S21 Measurement and O24 measured It is currently a subclass of S4 Observation and E16 Measurement With the new class Exx Observable Entity and the adjusted domain for P43 has dimensions, it little new in S21 Measurement compared with the superclass E16 Measurement Where to place E16 Measurement? A measurement is an observation, therefore E16 Measurement should be a subclass of S4 Observation in CRMSci. When CRMSci is generalized to CRM: instances of S4 Observation will be “ordinary” instances of E13 Attribute Assignment. O16 observed value will be P141 assigned O8 observed P140 assigned attribute to