Change how inverse roles are handle on the logic programming side

Seems like an easy way to convert inverse roles into atoms is to write
`R(y,x)` instead of `R^-(x,y)`.

This is still something we need to test and some additional rules that
use inverse roles in the naive way are still generated.

1 files changed, 2 insertions, 3 deletions

diff --git a/src/test/scala/uk/ac/ox/cs/rsacomb/converter/RDFoxConverterSpec.scala b/src/test/scala/uk/ac/ox/cs/rsacomb/converter/RDFoxConverterSpec.scala
index a401abf..12f71e8 100644
--- a/src/test/scala/uk/ac/ox/cs/rsacomb/converter/RDFoxConverterSpec.scala
+++ b/src/test/scala/uk/ac/ox/cs/rsacomb/converter/RDFoxConverterSpec.scala
@@ -86,12 +86,11 @@ class RDFoxConverterSpec
     }
   }
 
-  "The inverse of an object property" should "be converted into an atom with matching negated predicate" in {
+  "The inverse of an object property" should "be converted into an atom with inverted subject/object" in {
     val prop = factory.getOWLObjectProperty(iriString0)
     val inv = factory.getOWLObjectInverseOf(prop)
     for (sx <- Seq(Empty, Forward, Backward)) {
-      val atom =
-        TupleTableAtom.rdf(term0, IRI.create(iriString0 :: sx + Inverse), term1)
+      val atom = TupleTableAtom.rdf(term1, IRI.create(iriString0 :: sx), term0)
       convert(inv, term0, term1, sx) shouldEqual atom
     }
   }