tomaham
commented
1 month ago Done.
------ Original Message ------ From "David Zbíral" @.> To "DISSINET/InkVisitor" @.> Cc "tomas.hampejs" @.>; "Assign" @.> Date 5/31/2024 11:14:45 AM Subject [DISSINET/InkVisitor] BELONGS_TO should be HAS_STATEMENT, solve by optional postproduction query (Issue #2231)
For easy memorability, we switched to the has logic, very intuitive for everybody making properties, with Adam (I hope that at all levels). Now DDB2 has BELONGS_TO, i.e. bad relation and bad direction from the universalised DISSINET's has logic: statements have actants, but statements belong to depositions instead of depositions have statements.
But quite some queries are already built on BELONGS_TO. Thus, leave this already as the default option, but write an optional post-hoc query which will create "HAS_STATEMENT" and remove BELONGS_TO and will reverse the direction, i.e. from Territory to Statement.
— Reply to this email directly, view it on GitHub https://github.com/DISSINET/InkVisitor/issues/2231, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4Q7CJ2JWFYONUZWFVWVILZFA5QLAVCNFSM6AAAAABISN36HGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZDOMZTHE4TAOA. You are receiving this because you were assigned.Message ID: @.***>
With @adammertel, for easy memorability, we tried to universalise (I hope that at all levels) the "has" logic, and thus make the data model very intuitive for everybody making properties.
Now against this logic, DDB2 has BELONGS_TO, i.e. different relation and different direction from the universalised DISSINET's has logic: statements "have" actants, but statements "belong to" depositions instead of depositions "have" statements.
But I concede that quite some queries are already built on BELONGS_TO. Thus, leave this already as the default option, but write an optional post-hoc query which will create "HAS_STATEMENT" and remove BELONGS_TO and will reverse the direction, i.e. from Territory to Statement. The query could be called "rewrite S->T BELONGS_TO to T->S HAS_STATEMENT.