Discussion on Temporal Entities and Simultaneity in CIDOC CRM Meeting
Temporal entities and the modeling of simultaneity in CIDOC CRM are under discussion at the upcoming meeting. The current approach considers the cardinality of certain relations, aiming to streamline the representation of time-spans and spacetime volumes. The evolving perspectives on the spatial components of temporal entities are also being examined for alignment with existing classifications. The session aims to refine the conceptual understanding of how temporal entities are represented within the CIDOC CRM framework.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
Issue 326 Temporal entities Some comments Issue 326: Temporal entities, to be discussed at the 38th CIDOC CRM and 31th FRBR CRM meeting Christian-Emil Ore
CRM top hierarchy and space&time 1 E1 CRM Entity E2 Temporal Entity E52 Time-span E92 Spacetime Volume E53 Place Exx Observable Entity E54 Dimension P161 has spatial projection (1,n:1,1) P160 has temporal projection (1,1:1,1) P4 has time-span (1,1:1,n) E77 Persistent Item E4 Period E18 Physical Thing E3 Condition State I6 Belief The cardinality of P4 has time-span is (1,1:1,n), that is, two or more instances of E2 Temporal Entity can share an instance of E52 Time-span. This was introduced in an early stage to model simultaneity. This way of modeling simultaneity is considered obsolete and the cardinality of P4 should be (1,1:1,1)- E2 Temporal Entity and E52 Time-span in an one to one relation E2 Temporal Entity and E92 Spacetime Volume in an one to one relation.
CRM top hierarchy and space&time 2 E1 CRM Entity E2 Temporal Entity E52 Time-span E92 Spacetime Volume E53 Place Exx Observable Entity E54 Dimension P161 has spatial projection (1,n:1,1) P160 has temporal projection (1,1:1,1) P4 has time-span (1,1:1,1) E77 Persistent Item E4 Period E18 Physical Thing E3 Condition State I6 Belief The cardinality of P4 set to (1,1:1,1) has the following consequences E2 Temporal Entity and E52 Time-span in an one to one relation E2 Temporal Entity and E92 Spacetime Volume in an one to one relation. P4 (1,1:1,1) and P160(1,1:1,1) make E2 Temporal Entity, E52 Time-span and E92 Spacetime Volume isomorphic and they could be seen as one single class All instances of subclasses of E2 Temporal Entity have a spatial component.
CRM top hierarchy and space&time 3 E1 CRM Entity E2 Temporal Entity E52 Time-span E92 Spacetime Volume E53 Place Exx Observable Entity E54 Dimension P161 has spatial projection (1,n:1,1) P160 has temporal projection (1,1:1,1) P4 has time-span (1,1:1,1) E77 Persistent Item E4 Period E18 Physical Thing E3 Condition State I6 Belief Have all instances of possible subclasses of E2 Temporal Entity a spatial component? If yes then E4 Period equals E2 Temporal Entity If no then the cardinality of P160 has temporal projection should be adjusted to (1,1:0,1) It is doubtful that I2 Belief (CRMInf) has a spatial component. The function of an instance of I2 Belief is to express the temporal extent of the some actor s belief that an I4 Proposition Set has an I6 Belief Value.
Case: There exist instances of E4 Temporal Entity without spatial component E1 CRM Entity E2 Temporal Entity E52 Time-span E92 Spacetime Volume E53 Place Exx Observable Entity E54 Dimension P161 has spatial projection (1,n:1,1) P160 has temporal projection (1,1:0,1) E77 Persistent Item E4 Period E18 Physical Thing E3 Condition State I6 Belief Merge E2 Temporal Entity and E52 Time-span into one class All instances of E92 is connected to one and only one instance of this new class through P160 has temporal projection which is an injection. Thus E92 could have been a subclass of the new class. At least for pedagogical reasons this maynot be a good idea Is this a possible solution?
