Re: Update comment

The SPARQL query spec only specifies an indirect relationship between
graph name and contents for FROM and FROM NAMED, right?. USING should
be the same thing -- I don't think I understand the problem?

Lee


On 3/23/11, Andy Seaborne <andy.seaborne@epimorphics.com> wrote:
> A Fuseki user found the text below and assumed
>
> INSERT
>    { <http://rdf.freebase.com/ns/en.miles_davis> ?p ?o }
>    USING <http://rdf.freebase.com/ns/en.miles_davis>
>    WHERE
>    { <http://rdf.freebase.com/ns/en.miles_davis> ?p ?o }
>
> was like
>
>
>    CONSTRUCT
>    { <http://rdf.freebase.com/ns/en.miles_davis> ?p ?o }
>    FROM <http://rdf.freebase.com/ns/en.miles_davis>
>    WHERE
>    { <http://rdf.freebase.com/ns/en.miles_davis> ?p ?o }
>
> which it isn't (I hope).
>
>
> 3.1.3 DELETE/INSERT
> """
> The USING <uri> and USING NAMED <uri> clauses affect the graphs and
> named graphs used in the WHERE clause. This is identical manner to how
> FROM <uri> and FROM NAMED <uri> clauses affect the graphs and named
> graphs in a SPARQL SELECT query.
> """
>
> In most systems (not all) FROM reads a graph from the web and makes it
> part of the default graph.  It's LOAD.
>
> (Yes, *a few* systems pick their FROM out of the dataset)
>
> Doesn't USING select one or more graphs out of the graph store and use
> that for default graph.  Reading from the web is not allowed (I hope).
>
> """
> The use of USING in this instance is to avoid possible ambiguity of
> where statements being DELETEd from. If a USING clause appears, then
> this will override any effect that WITH may have on the WHERE clause,
> and only the WHERE clause.
> """
>
> What's "this instance"?
>
> 	Andy
>
>

Received on Wednesday, 23 March 2011 21:54:05 UTC