HI Mohammed,
I'm Mohamed Morsey, I'm one of the DBpedia developers team of Leipzig
university, and I'm currently working in DBpedia live.
We divide the triples of DBpedia live into 2 separate parts, one part
for dynamic triples, i.e. the triples that should be updated upon live
extraction, in which we place in one graph.
And another part for static triples, that we place in another graph.
The problem now is SPARQL query the user should specify 2 FROM clauses
for each graph, and we want avoid that issue, may be by using
something
like a subgraph or making something like a relational database view
that
combine both of these graphs, and then use it in "Default Graph
URI", so
I'm asking if any of this features apply and if so, how can I
achieve this.
I am discussing various options with the developers here to see what
is the best way to do this.
We will do some experiments to verify these solutions and see which is
the most optimal to use.
I will contact you privately to get some more background information
and sample data for us to look at.
Patrick
