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_RESPONSE, which does a XSLT transformation on the incoming data before loading it. And this can be done programatically, without having to interact with the conductor webtool.
Kyle On Fri, Aug 27, 2010 at 6:08 AM, Hugh Williams <[email protected]> wrote: > 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_Part_7.html#%2815%29 > > Although the "get:soft" pragma does not have an authentication paramter and > so cannot authenticate for you currently, although a request has been made > for an authentication parameter to be added which should be in the next > release ... >
