This ontology has the following classes and properties.
GFO-light contains some simplifications compared to the full version of General Formal Ontology (GFO) and is designed as a framework for the efficient development and foundation of domain/application ontologies.
IRI: https://w3id.org/gfo-light/CohesiveProcess
A treatment of a patient in a hospital
Football match
The course of an illness
The first half of the match
IRI: https://w3id.org/gfo-light/CohesiveSituation
A cohesive situation is a causally and temporally connected situation.
A risk situation when treating a patient in hospital if his laboratory values (qualities) are in the critical range over a certain period of time
The situation after the wedding of John and Mary (i.e., the situation in which they are married containing the marriage relator with a husband and a wife role)
The situation at the end of a football match containing players' qualities (e.g., number of goals or assists), teams' qualities (e.g., number of goals or ball possession) and a winner-loser relator with one team playing the winner role and the other team playing the loser role
IRI: https://w3id.org/gfo-light/InformationObject
Information objects are symbolic entities that denote/designate, describe, specify or represent other entities.
Computer programme
Description
Diagram
Model
Title
IRI: https://w3id.org/gfo-light/Line
Lines are not necessarily straight. They can be, for example, curves or broken lines that pass through various points and form a corner, a triangle or a polygon.
A line is a 1-dimensional object boundary.
Boundary line of the football field
Longitudinal axis of the human skeleton
IRI: https://w3id.org/gfo-light/Object
Objects are social or material entities that can exist independently of each other.
Bone
Chopstick
Computer
Person
IRI: https://w3id.org/gfo-light/ObjectAggregate
Object aggregates are groups of objects that together form a unit.
Research group
Sports team
IRI: https://w3id.org/gfo-light/ObjectBoundary
Object boundaries are 0-, 1-, or 2-dimensional (visible or imaginary) entities (i.e., points, lines and surfaces) that border objects (natural boundaries) or are located inside them (inner boundaries).
IRI: https://w3id.org/gfo-light/ObjectPart
Object parts are material entities that cannot exist independently of the corresponding whole object.
Part of a bone
Part of a chopstick
IRI: https://w3id.org/gfo-light/Point
A point is a 0-dimensional object boundary.
Gonion
Penalty spot
IRI: https://w3id.org/gfo-light/ProcessAggregate
A process aggregate is a process that consists of other contextually but not necessarily temporally interconnected processes.
A football league season, consisting of all matches
A series of lectures in a semester
IRI: https://w3id.org/gfo-light/Quality
Qualities can possess values.
Qualities are attributives that typically inhere in its bearer.
Observable or measurable characteristics of single objects, e.g., persons, (such as weight and height, laboratory parameters or symptoms)
Qualities of object groups (e.g., goals scored by a football team in a match)
Qualities of processes (e.g., the number of spectators as quality of a football match)
IRI: https://w3id.org/gfo-light/Relator
A relator represents an individual relation instance.
Relators are attributives that connect other entities (role players) by relational roles (played by role players).
A relator describing the relative location of an object (playing the target object role) in relation to another object (playing the reference object role), e.g., the location of a person relative to the city centre or the location of an anatomical structure relative to the longitudinal axis
A winner-loser relator connecting a winner and a loser team by a winner and a loser role
The marriage (relator) of John and Mary (in which Mary plays the wife role and John the husband role)
IRI: https://w3id.org/gfo-light/Role
An object part can play a (e.g., functional) role in the whole object (e.g., the processor is part of the computer and has the task/function/role to process commands). A member (object) of a social group (object aggregate) can play a social role in that group (e.g., John is member of the football team and plays the role of midfielder). Objects can play processual or situational roles in processes (e.g., team A plays the home team role and team B plays the visiting team role in a football match) or situations (e.g., scorer and assistant role in a goal situation or roles played by a doctor and a patient in a risk/adverse situation in hospital) in which they participate. Objects can play relational roles in a relation/relator (e.g., wife role and husband role of the marriage relator).
A role is a relational entity that links a continuant (role player) with some context (object, object aggregate, processual entity, situational entity, relator), in which the continuant plays that role.
John is member of the football team and plays the role of midfielder.
Roles played by a doctor and a patient in a risk/adverse situation in hospital
Target object role and reference object role of a relative location relator (describes the relative location of an object playing the target object role in relation to another object playing the reference object role)
Team A plays the home team role and team B plays the visiting team role in a football match.
The processor is part of the computer and has the task/function/role to process commands.
Wife role and husband role of the marriage relator
Winner team role and loser team role of the winner-loser relator
IRI: https://w3id.org/gfo-light/SituationAggregate
A situation aggregate is a situation that consists of other contextually but not necessarily temporally interconnected situations.
A situation of increased temperature during the course of an illness, consisting of all not necessarily temporally connected phases
IRI: https://w3id.org/gfo-light/Surface
A surface is a 2-dimensional object boundary.
Frontal plane of the human skeleton
Surface of the football field
IRI: https://w3id.org/gfo-light/boundaryOf
IRI: https://w3id.org/gfo-light/containsRole
IRI: https://w3id.org/gfo-light/hasBoundary
IRI: https://w3id.org/gfo-light/hasInnerBoundary
IRI: https://w3id.org/gfo-light/hasMember
IRI: https://w3id.org/gfo-light/hasNaturalBoundary
IRI: https://w3id.org/gfo-light/hasOwner
IRI: https://w3id.org/gfo-light/hasQuality
IRI: https://w3id.org/gfo-light/innerBoundaryOf
IRI: https://w3id.org/gfo-light/locatedIn
Material objects can be located in other material objects (locatedIn, e.g., the driver is located in the car).
IRI: https://w3id.org/gfo-light/locationOf
IRI: https://w3id.org/gfo-light/memberOf
IRI: https://w3id.org/gfo-light/naturalBoundaryOf
IRI: https://w3id.org/gfo-light/ownerOf
IRI: https://w3id.org/gfo-light/playedBy
IRI: https://w3id.org/gfo-light/plays
IRI: https://w3id.org/gfo-light/qualityOf
IRI: https://w3id.org/gfo-light/relates
IRI: https://w3id.org/gfo-light/representedBy
IRI: https://w3id.org/gfo-light/represents
IRI: https://w3id.org/gfo-light/roleIn
IRI: https://w3id.org/gfo-light/spatiallyEndsOn
IRI: https://w3id.org/gfo-light/spatiallyPassesThrough
IRI: https://w3id.org/gfo-light/spatiallyStartsOn
IRI: http://www.w3.org/2004/02/skos/core#altLabel
IRI: http://www.w3.org/2000/01/rdf-schema#comment
IRI: http://purl.org/dc/elements/1.1/created
IRI: http://purl.org/dc/elements/1.1/creator
IRI: http://www.w3.org/2004/02/skos/core#definition
IRI: http://purl.org/dc/elements/1.1/description
IRI: http://purl.org/ontology/bibo/doi
IRI: http://www.w3.org/2004/02/skos/core#example
IRI: http://xmlns.com/foaf/0.1/homepage
IRI: http://purl.org/dc/terms/license
IRI: http://purl.org/dc/elements/1.1/modified
IRI: http://purl.org/vocab/vann/preferredNamespacePrefix
IRI: http://purl.org/vocab/vann/preferredNamespaceURI
IRI: http://usefulinc.com/ns/doap#repository
IRI: http://purl.org/dc/elements/1.1/title
IRI: http://www.w3.org/2002/07/owl#versionInfo
The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.
A cohesive process is a causally and temporally connected process.