Open phismith opened 6 years ago
Here are ones that I noticed so far. Am reaching out to others to collect more. cco:has_familial_relationship_to cco:prescribes Designates (IAO) Mentions (IAO) Is about (IAO) cco:has_ending_instant cco:has_starting_instant cco:occurs at
On Tue, Aug 28, 2018 at 1:12 PM cstoeckert notifications@github.com wrote:
Here are ones that I noticed so far. Am reaching out to others to collect more. cco:has_familial_relationship_to cco:prescribes Designates (IAO) Mentions (IAO) Is about (IAO) cco:has_ending_instant cco:has_starting_instant cco:occurs at
The last three are now part of BFO:
*2.1 *first instant of
Definition: *temporal instant t *first instant of temporal region t´ =Def. t precedes all temporal parts of t' other than t [210-ISO]
Domain*: *temporal instant
Range*: *temporal region
Example: an hour starting at midnight yesterday has first instant midnight yesterday.
*2.2 *has first instant
Definition: t has first instant t' =Def. t' has first instant t [214-ISO]
Domain*: *temporal region
Range*: *temporal instant
Example: the first hour of a year has first instant midnight December 31.
*2.3 *last instant of
Definition: *temporal instant t *last instant of temporal region t´ =Def. all temporal parts of t' other than t precede t [211-ISO]
Domain*: *temporal instant
Range*: *temporal region
Example: last midnight is the last instant of yesterday
*2.4 *has last instant
Definition: t has last instant t´ =Def. t´ *last instant of *t [215-ISO]
Domain*: *temporal region
Range*: *temporal instant
Example: the last hour of a year has last instant midnight
December 31.
These are also now part of BFO:
*2.1 *occurs in
Definition: *b *occurs in c =Def. b is a process or a process boundary and c is a material entity or immaterial entity
& there exists a spatiotemporal region r and b *occupies spatiotemporal region *r
& for all t, if b exists at t then c exists at t
& there exist *spatial *regions s and s' where
b spatially projects onto s *at* t
& c occupies spatial region s' at t
& s is a *continuant part of *s' at t [143-ISO]
Domain: process or process boundary
Range: material entity or immaterial entity but not spatial region
Example: a process of digestion occurs in the interior of an organism, a process of loading artillery rounds into a tank cannon occurs in the interior of the tank
*2.2 *environs
Definition: *b environs c =Def. c occurs in *b [211-ISO]
Domain: *material entity *or *immaterial entity *but
not spatial region
Range: process or process boundary
Example: mouth environs process of mastication, city environs traffic
—
You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/oborel/obo-relations/issues/252#issuecomment-416666873, or mute the thread https://github.com/notifications/unsubscribe-auth/AH6qNxSjChu3aPkUs2jhFXFjIPbPz4Gyks5uVXn2gaJpZM4WMdXL .
See also #254
See also #258. If we choose to have all (or most) relations housed in RO, then it will become even more important to have modules of RO that can be imported by those working in particularly domains.
Is this still needed?
There's been no activity here since 2018 -- can we close this issue?
In the RO discussion at the ICBO meeting we discussed the idea of extending RO-CORE by adding a collection of further general relations -- such as input, output, about -- which should be recommended for use by all RO users, but which are not part of RO Core since they are not part of the scope of BFO.
In this connection it was pointed out that the Common Core Ontologies (CCO) -- see here -- have already created such a set of general-purpose relations, which are available here
They are divided into 5 groups, first is the CCO equivalent of our RO Core, followed by:
Agent Ontology Geospatial Ontology Information Entity Ontology Time Ontology Extended Relation Ontology (mainly for relations pointing to entities in the future)
People are invited to examine these relations and identify those which they think will be of value for OBO purposes. BS