On Tuesday 03 August 2010, Ivan Mikhailov wrote: > What should be added to existing extension API configurable via > "define input:grab-resolver ..." > and "define input:grab-loader ..." > as they're described in > http://docs.openlinksw.com/virtuoso/rdfiridereferencing.html#rdfinputgrab
Sorry, saw your email too late. Thanks for pointing met o input:grab-resolver, I think that's what I want... Is there a HowTo for writing such an own grab-resolver method if you would want all IRIs to be resolved to your local store if they exist, use them; if not, fetch them and store them locally; not refetching anything more often than weekly? (searched your docs, but nothing found when I enter "RDF_GRAB_RESOLVER_DEFAULT"?!?) Currently when calling the Proxy like this: http://localhost:8890/about/rdf/http/dbpedia.org/resource/Barack_Obama it won't use the local DBpedia dump, as the graphs aren't "materialized": I only have one graph from the DBpedia dump in the local store: "http://dbpedia.org";, all proxy-calls seem to introduce new graphs such as: "http://dbpedia.org/resource/Barack_Obama"; (and judging from the time they take it seems as if they don't use the local store) . The same counts for all SPARQL-Queries doing a IRI-deref. So would it be a good idea to substitute http://dbpedia.org with http://localhost:8890/ in the grab resolver? Can I perhaps also do this for the proxy in total? (i.e., rewriting http://localhost:8890/about/rdf/http://dbpedia.org/resource/Barack_Obama to http://localhost:8890/resource/Barack_Obama ) Cheers, Jörn
