On 8/30/10 12:32 PM, Kyle wrote:
I considered it. But again, the ability to define the local graph name
was important, and well as being able to do the configuration without
interacting with the conductor site.
The Sponger is being updated to allow you designate Graph IRIs.
Virtuoso is act
I considered it. But again, the ability to define the local graph name
was important, and well as being able to do the configuration without
interacting with the conductor site. Virtuoso is acting as a backend
for another website, and that site defines which pages need to be
imported, and the XSLTs
Hi Kyle,
Have you considered using the Sponger RDF proxy Service (Rest style web
service) which exposes the Virtuoso sponger functionality via a web service
endpoint, as detailed at:
http://docs.openlinksw.com/virtuoso/rdfsparqlintegrationmiddleware.html#rdfspongerprogrammerguide
Using DB.DBA.SYS_HTTP_SPONGE_UP directly solves a few different
problems, namely it allows me to define the local name of the graph
URI manually.
Also by engaging SYS_HTTP_SPONGE_UP directly, I can write replacements
for RDF_LOAD_HTTP_RESPONSE. For example I have one called
RDF_XSLT_LOAD_HTTP_RESP
Hi Kyle,
The DB.DBA.SYS_HTTP_SPONGE_UP procedure is for internal use only. The Virtuoso
"sparql define get:soft ..." method would be the way to sponge remote pages as
detailed at:
http://virtuoso.openlinksw.com/presentations/SPARQL_Tutorials/SPARQL_Tutorials_Part_7/SPARQL_Tutorials_Par
I'm trying to build up a sparql database by manually calling
DB.DBA.SYS_HTTP_SPONGE_UP through the JDCB interface. Some of the
pages I want to grab require authentication to get. How can I pass
authentication information so virtuoso will download these pages?
Kyle
