Hello all,
After spending many frustrating hours trying to fix the below attached
problems, finally I figured out from the DAWG test cases that I should
be doing something like
describe ?s where {?s urn:prop1 ?o . FILTER(?o = 1). }
However. that *still* didnt work, though the test cases were working ....
So, I went through my application again, and I found the problem:
Unlike what I had mentioned regarding the sample data, I was inserting
urn:foo1 urn:prop1 "1"^^xsd:int.
rather than xsd:integer
After changing python's rdflib to use xsd:integer for python int-s
instead, now the describe and select works correctly.
(I wrote the above just for the mailing list archive.)
Thanks to all
Regards
Rajeev J Sebastian
On Jan 22, 2008 2:29 PM, Rajeev J Sebastian <rajeev.sebast...@gmail.com> 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.}
>
>
> Perhaps it is my lack of knowledge on Sparql querying ... but is there
> some special syntax to indicate an integer in the "object" position in
> the graph pattern ? I think with simple literals, the describe is
> working correctly for me, but not for these kind of literals (but I
> have not tested extensively).
>
> Any help in this regard would be really appreciated ...
>
> Regards
> Rajeev J Sebastian
>
>
>
> On Jan 22, 2008 11:28 AM, Ivan Mikhailov <imikhai...@openlinksw.com> wrote:
> > Hello Rajeev,
> >
> > Yes, Virtuoso supports DESCRIBE for everything that can be SELECTed.
> > Internally, DESCRIBE, CONSTRUCT, INSERT, DELETE and MODIFY are
> > implemented as user-defined aggregates applied to the output of
> > appropriate SELECT statement so they do not bring any additional
> > restrictions to SELECT functionality.
> >
> > Best Regards,
> > Ivan Mikhailov,
> > OpenLink Software.
> >
> >
> > On Tue, 2008-01-22 at 05:32 +0530, Rajeev J Sebastian wrote:
> > > Hello all,
> > >
> > > Does Virtuoso 5.0.3 support queries of the form:
> > >
> > > describe ?x where { ?x foaf:name "foo" }
> > >
> > > ?
> > >
> > > Regards
> > > Rajeev J Sebastian
> > >
> > > -------------------------------------------------------------------------
> > > This SF.net email is sponsored by: Microsoft
> > > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > _______________________________________________
> > > Virtuoso-users mailing list
> > > Virtuoso-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/virtuoso-users
> >
> >
>
