Rajeev,
As far as I understand, you've intended to find out subject with
property equal to an integer 1. But "1" and 1 are two different things,
1^^xsd:int is also differs in type and { ?x urn:prop1 1. } contains a
subtle error -- dot immediately after "1" become decimal point of double
precision constant (xsd:double), instead of indicating end of triple. A
space like in { ?x urn:prop1 1 . } will change the meaning.
The most interesting is why "1"^^xsd:integer. does not fork for you as
it should, but it works for last CVS checkout and maybe for last
published version. Anyway you know the fix now and there's no need to
upgrade before next VOS release that is scheduled for this weekend.
Best Regards,
Ivan Mikhailov.
OpenLink Software.
On Tue, 2008-01-22 at 14:29 +0530, Rajeev J Sebastian wrote:
> Hello Ivan,
>
> Thanks for your response.
>
> The reason I asked about it was that a particular query was not working for
> me.
>
> Sample graph:
>
> urn:foo1 urn:prop1 "1"^^xsd:integer.
> urn:foo2 rdf:label "bar".
>
>
> Queries:
>
> describe ?x where {?x rdf:label "bar". } <- works, returns all the
> triples with urn:foo2 as subject
> describe ?x where {?x ?p ?o.} <- works, returns the entire graph
>
> describe ?x where {?x urn:prop1 "1".} <- fails, returns empty graph
> describe ?x where {?x urn:prop1 "1"^^xsd:int.} <- fails, returns empty graph
> describe ?x where {?x urn:prop1 "1"^^xsd:integer.} <- fails, returns empty
> graph
> describe ?x where {?x urn:prop1 1.} <- fails, returns empty graph
> describe ?x where {?x ?p 1.} <-fails, returns empty graph
>
>
>
> Also, select fails
>
> select ?x where {?x urn:prop1 1.}
