Skip to content

Commit 8e3735b

Browse files
committed
Add Perdurant as parent of Event and Action
Perdurant was originally proposed in Issue 544 with a sibling class. Issue 651 introduces Perdurant independently due to timelining needs. No effects were observed on Make-managed files. References: * #544 * #651 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
1 parent 633074a commit 8e3735b

2 files changed

Lines changed: 13 additions & 2 deletions

File tree

ontology/uco/action/action.ttl

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ action:Action
3737
owl:Class ,
3838
sh:NodeShape
3939
;
40-
rdfs:subClassOf core:UcoObject ;
40+
rdfs:subClassOf core:Perdurant ;
4141
rdfs:label "Action"@en ;
4242
rdfs:comment "An action is something that may be done or performed."@en ;
4343
owl:disjointWith core:Event ;

ontology/uco/core/core.ttl

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -181,7 +181,7 @@ core:Event
181181
owl:Class ,
182182
sh:NodeShape
183183
;
184-
rdfs:subClassOf core:UcoObject ;
184+
rdfs:subClassOf core:Perdurant ;
185185
rdfs:label "Event"@en ;
186186
rdfs:comment "An Event is a noteworthy occurrence (something that happens or might happen)."@en ;
187187
owl:disjointWith action:Action ;
@@ -330,6 +330,17 @@ core:ObjectStatusVocab
330330
] ;
331331
.
332332

333+
core:Perdurant
334+
a owl:Class ;
335+
rdfs:subClassOf core:UcoObject ;
336+
rdfs:label "Perdurant"@en ;
337+
rdfs:comment "Perdurants \"are individuals composed of temporal parts,\" or the start or end of such an individual. \"They happen in time in the sense that they extend in time accumulating temporal parts.\" In any instant where a non-instantaneous perdurant exists, \"it is not the case that all its temporal parts are present.\" Also known as \"Occurrents\" in some models [e.g., BFO concept 3]. [Definition quoted and adapted from Section 2 of Guizzardi et al., \"Towards Ontological Foundations for the Conceptual Modeling of Events,\" 2013; and, the BFO-2020 definition of \"occurrent\".] Taking for example a human: the human *is not* a perdurant; but, the human's life *is* a perdurant. Taking for example a computer process, as in the operating system object in which a piece of software is executed: The process *is not* a perdurant, because if time is frozen such as in a virtual machine snapshot, everything about the process exists; but, the process's execution taking place *is* a perdurant, as is the instant in which the process terminates."@en ;
338+
rdfs:seeAlso
339+
<http://purl.obolibrary.org/obo/BFO_0000003> ,
340+
<https://doi.org/10.1007/978-3-642-41924-9_27>
341+
;
342+
.
343+
333344
core:Relationship
334345
a
335346
owl:Class ,

0 commit comments

Comments
 (0)