owl:sameAs inference not working

[Maatary Okouya]

Hi, 

I would like to understand how Stardog handle owl:sameAs. 

I have the following ttl file produced with TopBraid:

(I precise TopBraid because to explain the spin:import, which actually should be ignore from what i understand of Stardog)

# baseURI: http://example.org/aProject

@prefix : <http://example.org/aProject#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix spin: <http://spinrdf.org/spin#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<http://example.org/aProject>
  rdf:type owl:Ontology ;
  spin:imports <http://topbraid.org/spin/owlrl-all> ;
  owl:versionInfo "Created with TopBraid Composer"^^xsd:string ;
.
:he
  rdf:type owl:NamedIndividual ;
  rdf:type owl:Thing ;
  :isRelatedTo :me ;
  rdfs:label "he"^^xsd:string ;
.
:isRelatedTo
  rdf:type owl:ObjectProperty ;
  rdfs:label "isRelatedTo"^^xsd:string ;
.
:me
  rdf:type owl:NamedIndividual ;
  rdf:type owl:Thing ;
  rdfs:label "me"^^xsd:string ;
.
:you
  rdf:type owl:NamedIndividual ;
  rdf:type owl:Thing ;
  rdfs:label "you"^^xsd:string ;
  owl:sameAs :me ;
.

Here is what is in Stardog after loading my dataset produce with TopBraid. 

<http://example.org/aProject> a <http://www.w3.org/2002/07/owl#Ontology> ;

<http://spinrdf.org/spin#imports> <http://topbraid.org/spin/owlrl-all> ;

<http://www.w3.org/2002/07/owl#versionInfo> "Created with TopBraid Composer"^^<http://www.w3.org/2001/XMLSchema#string> .



<http://example.org/aProject#he> a <http://www.w3.org/2002/07/owl#NamedIndividual> , <http://www.w3.org/2002/07/owl#Thing> ;

<http://example.org/aProject#isRelatedTo> <http://example.org/aProject#me> ;

<http://www.w3.org/2000/01/rdf-schema#label> "he"^^<http://www.w3.org/2001/XMLSchema#string> .



<http://example.org/aProject#isRelatedTo> a <http://www.w3.org/2002/07/owl#ObjectProperty> ;

<http://www.w3.org/2000/01/rdf-schema#label> "isRelatedTo"^^<http://www.w3.org/2001/XMLSchema#string> .



<http://example.org/aProject#me> a <http://www.w3.org/2002/07/owl#NamedIndividual> , <http://www.w3.org/2002/07/owl#Thing> ;

<http://www.w3.org/2000/01/rdf-schema#label> "me"^^<http://www.w3.org/2001/XMLSchema#string> .



<http://example.org/aProject#you> a <http://www.w3.org/2002/07/owl#NamedIndividual> , <http://www.w3.org/2002/07/owl#Thing> ;

<http://www.w3.org/2000/01/rdf-schema#label> "you"^^<http://www.w3.org/2001/XMLSchema#string> ;

<http://www.w3.org/2002/07/owl#sameAs> <http://example.org/aProject#me> .

When I run: ask {:you owl:sameAs :me}  I get true as a result

However when i run: ask {:me owl:sameAs :you}  I get false as a result

I have tested it with all reasoning level, and i keep on getting the same answer, am i doing something wrong ? Can anyone help.

I'm using the 2.2.2 version. I'm suspecting that the problem comes from it. I would like to try with the previous one, can i still download its community version ?

Many thanks for any help. 

[Evren Sirin]

As mentioned in [1] Stardog currently does not support sameAs
reasoning. We have this feature almost ready and will include it in
the next major release.

Best,
Evren

[1] http://docs.stardog.com/owl2/#sd-Known-Issues

> --
> -- --
> You received this message because you are subscribed to the C&P "Stardog"
> group.
> To post to this group, send email to sta...@clarkparsia.com
> To unsubscribe from this group, send email to
> stardog+u...@clarkparsia.com
> For more options, visit this group at
> http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en

[Maatary Okouya]

Thank you for re-minding me. 

If i may, i have 2 questions: 

in the context of linked-data, where this is pretty much important, what would be the workaround here ?

Also could you give me an idea of when the next release will come ?

I use it quite a lot to describe my data and reason with it within TopBraid. This is particularly useful when you have a resource A related to a Resource B that is the same as an involving set of other resource (Updated over time).

A gets automatically related to have evolving set. In any case that's a basic example. It is just that in the world of linked-data this is extremely used. 

How one can work around that ? If not please let me know.

[Maatary Okouya]

Could ICV constraint be of any help ?