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
There was a crucial discussion today in the Data Modeling call about how to handle negation on edges.
I have a vague recollection that we removed Edge.negation long ago with the idea that they would just be attributes.
But after today's discussion, I am wondering whether it would be better/safer to make negated a first class property of Edge?
Vaccine causes autism?
Vaccine NOT causes autism.
We should follow Data Modeling conclusion closely on this and be very clear how to express this in TRAPI.
The text was updated successfully, but these errors were encountered:
It would also be helpful for us to distinguish between 1) there is evidence that the edge is not true vs 2) there is insufficient evidence to support this edge
There was a crucial discussion today in the Data Modeling call about how to handle negation on edges.
I have a vague recollection that we removed Edge.negation long ago with the idea that they would just be attributes.
But after today's discussion, I am wondering whether it would be better/safer to make negated a first class property of Edge?
Vaccine causes autism?
Vaccine NOT causes autism.
We should follow Data Modeling conclusion closely on this and be very clear how to express this in TRAPI.
The text was updated successfully, but these errors were encountered: