Thanks, Andy. It made good sense. Cheers, Frank
________________________________ From: Andy Seaborne <[email protected]> To: [email protected] Sent: Wednesday, September 26, 2012 11:31 AM Subject: Re: Remote named graph On 26/09/12 01:06, Frank Lee wrote: > Thanks for that, Andy. > > So, we can't use any existing API (for we've already grabbed the handle of > the namedGraph model) to duplicate it, SPARQL/update is the only way to do it. Mu suggestions were made so as to avoid copying everything onto the local machine, and copying it back out again. Using COPY, only a copy within the remote machine is done. Is that what you are trying to do? Andy > > > > ________________________________ > From: Andy Seaborne <[email protected]> > To: [email protected] > Sent: Tuesday, September 25, 2012 2:34 PM > Subject: Re: Remote named graph > > On 25/09/12 00:33, Frank Lee wrote: >> Hi, Andy, >> >> What will be better way to duplicate existing named graph remotely? >> Or duplicated many with different URIs. Is there any simple API to >> use for it? Thanks. >> >> Cheers Frank > > SPARQL Update: > > something like > > COPY <g1> To <g2> > > for a one to one copy: > > or > > INSERT { GRAPH <g> { ?s ?p ?o } } > WHERE { GRAPH ?g { ?s ?p ?o } FILTER ( ?g IN ( <g1>, <g2>, <g3> ) ) } > > for many > > (untested) > > Andy >
