Hello
I noticed a strange effect happening when I issue the following query:
SELECT DISTINCT *
WHERE
{
SERVICE <http://0.0.0.0:2020/sparql> { ?document
<http://www.cipe.accamargo.org.br/ontologias/h2tc.owl#documentType>
"exam request" . }
SERVICE <http://0.0.0.0:2020/sparql> { ?document
<http://www.cipe.accamargo.org.br/ontologias/h2tc.owl#documentAuthor>
?author . }
}
0.0.0.0:2020/sparql points to a d2r-server instance. This query was issued
not directly to this instance, but rather by a command line ARQ over an
empty graph.
This query is part of a bigger query that refers to several d2r-server
instances, and I know that I could join both of them in one SERVICE only
for optimization, but that's not the point.
The point is, instead of getting proper URIs for ?author, I'm getting those
huge hex data, like
<687474703A2F2F7777772E636970652E616363616D6172676F2E6F72672E62722F6F6E746F6C6F676961732F683274632E6F776C237573657273554E495636363837353234353636>
Interestingly enough, converting consecutive pairs of those bytes to chars,
it turns into a URI!
http://www.cipe.accamargo.org.br/ontologias/h2tc.owl#usersUNIV6687524566
Which is a valid answer to ?author.
I have verified that a query without those SERVICE keywords works
perfectly, when issued directly to D2R-server.
I'm not really sure whose fault is this, ARQ or D2R.
Any help in order to get things straight will be appreciated.
Thanks,
--
diogo patrão
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
d2rq-map-devel mailing list
d2rq-map-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/d2rq-map-devel
