This is a diff between 1.1 and 1.2 revisions:

64a67
< * [[http://docs.openlinksw.com/virtuoso/rdfsparql.html][SPARQL]]
\ No newline at end of file
63d67
> * [[http://docs.openlinksw.com/virtuoso/rdfsparql.html][SPARQL]]
60a64
<
< ---+++Related
59d64
> ---++ Related
56a60
< 1. Use <b><nowiki>SYS_SPARQL_HOST</b></nowiki> table as described [[http://docs.openlinksw.com/virtuoso/rdfsparql.html#rdfdefaultgraph][here]] and set <b><nowiki>SH_DEFINES</b></nowiki> so it contains your favorite define input:storage
55d60
> * Use <b><code><nowiki>SYS_SPARQL_HOST</nowiki></code></b> table as [[http://docs.openlinksw.com/virtuoso/rdfsparql.html#rdfdefaultgraph][described here]], and set <b><code><nowiki>SH_DEFINES</nowiki></code></b> so it contains your favorite <code>define input:storage</code>.
50a56
< There are two ways of using the Linked Data View from above in SPARQL endpoint without <b>define input:storage</b>:
< 1. Create Linked Data View right in <b>virtrdf:DefaultQuadStorage</b> or add the view in other storage and then copy it from there to <b>virtrdf:DefaultQuadStorage</b>.
< * In any of these two variants, use:
49d54
> There are two ways of using one of these Linked Data Views in SPARQL endpoint without making a <code>define input:storage</code> declaration.
> * Create a Linked Data View right in <b><code><nowiki>virtrdf:DefaultQuadStorage</nowiki></code></b>; or add the view in other storage, and then
> copy it from there to <b><code><nowiki>virtrdf:DefaultQuadStorage</nowiki></code></b>. In either case, use:
46a52
< 1 <b>virtrdf:DefaultQuadStorage</b> is what's in use if no input:storage specified.
< 1 <b>virtrdf:DefaultServiceStorage</b> will be used for SPARQL federation.
< 1 <b>virtrdf:SyncToQuads</b> is to keep the list of Linked Data Views that are translated into RDB2RDF triggers.
45d50
> * <b><code><nowiki>virtrdf:DefaultQuadStorage</nowiki></code></b> is used if no <code>input:storage</code> is specified.
> * <b><code><nowiki>virtrdf:DefaultServiceStorage</nowiki></code></b> is used for SPARQL Federation.
> * <b><code><nowiki>virtrdf:SyncToQuads</nowiki></code></b> is used to keep the list of Linked Data Views that are translated into RDB2RDF triggers.
30a35
< All metadata about all RDF storages are kept in "system" graph &lt;http://www.openlinksw.com/schemas/virtrdf#&gt; ( namespace prefix
< <b>virtrdf:</b> ). Subjects of type <b>virtrdf:QuadStorage</b> are RDF storages. There are three of them by default:
29d33
> All metadata about all RDF storages are kept in "system" graph <code><nowiki>&lt;http://www.openlinksw.com/schemas/virtrdf#&gt;</nowiki></code>
> (with built-in, predefined namespace prefix, <b><code>virtrdf:</code></b>). Subjects of type <b><code><nowiki>virtrdf:QuadStorage</nowiki></code></b>
> are RDF storages. There are three of them by default:
26a29
< http://localhost:8890/sparql?query=select * where { ?s ?p ?o }&default-graph-uri=NULL&named-graph-uri=NULL
25d29
> http://localhost:8890/sparql?qtxt=SELECT%20*%20WHERE%20%7B%20%3Fs%20%3Fp%20%3Fo%20%7D&default-graph-uri=NULL&named-graph-uri=NULL
23a26
< Now one could ask is there a way to define internally (once) that the quad storage should be included in queries to the SPARQL endpoint? So that the user does not have to define the <b>input:storage</b> explicitly in each query, like this:
22d25
> One might ask, is there a way to tell Virtuoso (once) that the quad storage should always be included in all queries to the
> SPARQL endpoint, such that the user does not have to define the <b>input:storage</b> explicitly in each query?
15a17
< define input:storage <http://localhost:8890/rdfv_demo/quad_storage/default>
14d17
> DEFINE input:storage <http://localhost:8890/rdfv_demo/quad_storage/default>
12a14
< Also the RDF is accessible over the SPARQL endpoint with the following query:
11d14
> The RDF is also accessible through the SPARQL endpoint with a query like --
6a8
< Let's take for example a [[http://virtuoso.openlinksw.com/whitepapers/relational%20rdf%20views%20mapping.html][created RDF view from relational data in Virtuoso]]. The RDF output therefor should have two graphs which reside in a quad storage named for ex.:
5d6
> Let's take for example a
> [[http://virtuoso.openlinksw.com/whitepapers/relational%20rdf%20views%20mapping.html][Linked Data (RDF) View created from relational data in Virtuoso]].
> The RDF output should have two graphs which reside in a quad storage named, for example --
3a3
< ---++How can I see which quad storages exist and in which quad storage a graph resides?
2d3
> ---+ How can I see which quad storages exist and in which quad storage a graph resides?