Jonathan Vajda

I suggest that in addition to the reasons given above, the term 'person' could follow BFO design principles more closely. 'person' is defined as "an animal that is a member...

I don't think it is redundant if there is an important use case for has-process-part _as a subclass_ of has-occurrent-part. Absent that, it seems like it could be deprecated As...

> A function is the reason that something exists. I am not sure that capacity is the reason for a vehicle to exist. This just means that it is not...

> A possible objection: you can store supplies in a cave, but storage is not the cave's function. The pattern applies only to artifacts designed for storage. Bingo. There's a...

> I want to capture the 'quality' of how a function or disposition may be realized, not those abilities themselves. I want to capture something about the storage function, or...

It looks like "supervises" (and its inverse, "is supervised by") is the relevant CCO relation here. Definition: "A person p1 supervises a person p2 by virtue of p1 directing, managing,...

I have a few use cases, all fairly recently: "Who is working a shift during this time?" (Distinction between time and shift) "What people are working the majority of their...

>Draft definition: "An Odometer is an Information Bearing Artifact that is designed to bear some Information Content Entity that measures the distance an entity has traveled." Good enough, but "distance...

> The uses of the terms 'bear' and 'inhere' and their synonymity in BFO are not consistent with their natural language definitions. > > The term 'bear' has a common...

> If this is correct, then the definition of the inverse property (is site of) should read: > > "x is_site_of y iff x is an instance of _either_ Site...