You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The inverse of permanent generic part of is not permanent generic has part. This is easy to see in that, in general the left hand side of this relation is a single entity, whereas the right hand side in general is either a type, or at least a number of individuals.
That would follow the pattern that the RO class level relations are not inverses of each other.
Only the -at-a-time instance-of relation are (sort of) inverse.
Also note that permanent generic part hood doesn't make sense for occurrents.
Therefore the suggestion that the atemporal relations are simpler and don't require as many variants as the temporalized relations is false. There would need to be, at least, a distinction between occurrents and continuants is needed (because generic parthood only makes sense for continuants) and separate inverses are needed (since the part-of relation inverse is not has-part).
This would suggest that a strategy that defined "ro2005-ish" atemporal relations, would not seem to be a simpler solution than that which is offered with the temporal relations.
IIRC the TQC version I proposed used the temporalized relations to good effect. If the TQC interpretation means that during any TCQ there is only one rhs for each lhs, can you say why you need something different than those? I hadn't previously heard it offered that the atemporal has-part relation would operate only on TCQs in the case that there was permanent generic parthood. If so, how would you actually express permanent generic parthood?
From [email protected] on May 07, 2013 13:19:10
The inverse of permanent generic part of is not permanent generic has part. This is easy to see in that, in general the left hand side of this relation is a single entity, whereas the right hand side in general is either a type, or at least a number of individuals.
That would follow the pattern that the RO class level relations are not inverses of each other.
Only the -at-a-time instance-of relation are (sort of) inverse.
Also note that permanent generic part hood doesn't make sense for occurrents.
Therefore the suggestion that the atemporal relations are simpler and don't require as many variants as the temporalized relations is false. There would need to be, at least, a distinction between occurrents and continuants is needed (because generic parthood only makes sense for continuants) and separate inverses are needed (since the part-of relation inverse is not has-part).
This would suggest that a strategy that defined "ro2005-ish" atemporal relations, would not seem to be a simpler solution than that which is offered with the temporal relations.
Original issue: http://code.google.com/p/bfo/issues/detail?id=169
The text was updated successfully, but these errors were encountered: