Hi Richard,

On 6/2/2011 12:44 PM, Richard Cyganiak wrote:
> May I ask you to please keep the mailing list in CC at all times.
Of-course! :-)   Sorry about not including the list, I accidentally 
clicked the reply instead of the reply-all button.
> On 2 Jun 2011, at 17:30, Shahim Essaid wrote:
>> I would like to have a D2RQ model as the default graph in a Joseki Dataset.
> Why? D2R Server already is bundled with a pre-configured Joseki that has the 
> D2RQ model in the default graph. That's the service configured at 
> http://localhost:2020/sparql or wherever your D2R server is running.
>
I wasn't aware how the various APIs and servers are put together, and I 
wasn't aware of the SERVICE extension in SPARQL 1.1. I am starting to 
understand the various implementation components (and the SPARQL 1.1 
extensions) and how they are reused in each case.

However, it appears that my use-case needs more than one server in the 
current D2RQ Server implementation (the limit on named graphs in the 
D2RQ model).

Please allow me to briefly describe my use case:

I am developing a domain ontology and a D@RQ mapping to an existing 
database. The ontology (domain entities and relations) is independent of 
the database schema (application forms, and form properties and values). 
The mapping is complicated because the database is "application form" 
oriented but my ontology is "domain entity" oriented.

Now, I would like to issue SPARQL queries that are based on the domain 
entities and relations from the ontology and retrieve "domain data" (owl 
individuals and relations instances, rdf) from the database by 
extracting this data from "form data" in the database. To be able to do 
this, my query needs to retrieve some ontology information and bind the 
information to few SQPRQL variables before sending the query to the 
database (D2RQ Server).  I now see that the SERVICE approach is the way 
to do this unless there is a better way.

Here is my current setup:

Joseki  at (http://localhost:8080>
             Dataset: default: empty
<http:gieo>  gieo.owl OWL file
<http:gieoinf>  InfModel with Pellet and the OWL file

Joseki at <http://localhost:2020>  (the D2RQ Server)

         Dataset:   default D2RQ model with my mapping
                            No other graphs allowed.


SPARQL queries to <http://localhost:8080> with  SERVICE 
<http://localhost:2020> to access the data from the D2RQ server after 
binding variables from the named graphs at the <http://localhost:8080> 
service.

It looks like the above setup is working so far.

Thank you very much for the very helpful and quick answers. Many of 
these basic issues are not always clear for someone just getting started 
with these APIs and tools.

All the best,
Shahim

>> Can a D2RQ be a named graph in the Joseki Dataset or does it have to be a 
>> default graph?
> It has to be the default graph.
>
>> Can I add other named graphs to a Joseki Dataset if a D2RQ model is the 
>> default graph? ( the post above from 2009 says it is not possible)
> It's not possible.
>
>> If I can only load a D2RQ model as a default graph in Joseki with no other 
>> graphs, can this Joseki service be used in a FROM<some joseki service uri>  
>> sparql query to another Joseki sparql service that has named graphs in its 
>> dataset?
> As far as I know, you can only name the URI of an RDF file in a FROM clause. 
> You can't name the URI of a SPARQL endpoint. So to the best of my knowledge, 
> this is not possible, but that has nothing to do with D2RQ.
>
>> Which D2RQ libraries should I add to Joseki's classpath to include a D2RQ 
>> model in Joseki instead of using a FROM<http://localhost:2020/all>  in my 
>> Joseki queries?  I added all the jars in the D2RQ server lib folder to 
>> Joseki's classpath because I wasn't sure what is needed and what is not.
> Just use D2R Server. It comes with a bundled Joseki.
>
> Best,
> Richard
>


------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2 
_______________________________________________
d2rq-map-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/d2rq-map-devel

Reply via email to