a ; "

COPY

\n\n

The COPY operation is a shortcut for inserting all data from an input graph into a destination graph. Data from the input graph is not affected, but data from the destination graph, if any, is removed before insertion.

\n
**COPY** ( **SILENT** )? ( ( **GRAPH** )? *[IRIref_from](../../../sparql11-query/grammar/#rIRIREF)* | **DEFAULT**) **TO** ( ( **GRAPH** )? *[IRIref_to](../../../sparql11-query/grammar/#rIRIREF)* | **DEFAULT** )\n
\n

is similar in operation to:

\n
**DROP** **SILENT** (**GRAPH** *[IRIref_to](../../../sparql11-query/grammar/#rIRIREF)* | **DEFAULT**);\n      **INSERT** { ( **GRAPH** *[IRIref_to](../../../sparql11-query/grammar/#rIRIREF)* )? **{ ?s ?p ?o } } WHERE** { ( **GRAPH** *[IRIref_from](../../../sparql11-query/grammar/#rIRIREF)* )? **{ ?s ?p ?o } }**\n
\n

The difference between COPY and the DROP/INSERT combination is that if COPY is used to copy a graph onto itself then no operation will be performed and the data will be left as it was. Using DROP/INSERT in this situation would result in an empty graph.

\n

If the destination graph does not exist, it will be created. By default, the service MAY return failure if the input graph does not exist. If SILENT is present, the result of the operation will always be success.

\n

Example 13:

\n

This example request copies all statements from the default graph to a named graph:

\n
COPY DEFAULT TO <http://example.org/named>\n
\n

Data before:

\n
**# Default graph**\n@prefix foaf:  <http://xmlns.com/foaf/0.1/> .\n\n<http://example/william> a foaf:Person .\n<http://example/william> foaf:givenName \"William\" .\n<http://example/william> foaf:mbox  <mailto:bill@example> .\n
\n
**# Graph http://example.org/named**\n<http://example/fred> a foaf:Person .\n<http://example/fred> foaf:givenName \"Fred\" .\n
\n

Data after:

\n
**# Default graph**\n@prefix foaf:  <http://xmlns.com/foaf/0.1/> .\n\n<http://example/william> a foaf:Person .\n<http://example/william> foaf:givenName \"William\" .\n<http://example/william> foaf:mbox  <mailto:bill@example> .\n
\n
**# Graph http://example.org/named**\n@prefix foaf:  <http://xmlns.com/foaf/0.1/> .\n\n<http://example/william> a foaf:Person .\n<http://example/william> foaf:givenName \"William\" .\n<http://example/william> foaf:mbox  <mailto:bill@example> .\n
\n

Note that the original content in http://example.org/named is lost by a COPY operation.

"^^ ; . a ; "

MOVE

\n\n

The MOVE operation is a shortcut for moving all data from an input graph into a destination graph. The input graph is removed after insertion and data from the destination graph, if any, is removed before insertion.

\n
**MOVE** (**SILENT**)? ( ( **GRAPH** )? *[IRIref_from](../../../sparql11-query/grammar/#rIRIREF)* | **DEFAULT**) **TO** ( ( **GRAPH** )? *[IRIref_to](../../../sparql11-query/grammar/#rIRIREF)* | **DEFAULT**)\n
\n

is similar in operation to:

\n
**DROP SILENT** (**GRAPH** *[IRIref_to](../../../sparql11-query/grammar/#rIRIREF)* | **DEFAULT**);\n      **INSERT** { ( **GRAPH** *[IRIref_to](../../../sparql11-query/grammar/#rIRIREF)* )? **{ ?s ?p ?o } } WHERE** { ( **GRAPH** *[IRIref_from](../../../sparql11-query/grammar/#rIRIREF)* )? **{ ?s ?p ?o } };\nDROP** ( **GRAPH** *[IRIref_from](../../../sparql11-query/grammar/#rIRIREF)* | **DEFAULT**)\n
\n

The difference between MOVE and the DROP/INSERT/DROP combination is that if MOVE is used to move a graph onto itself then no operation will be performed and the data will be left as it was. Using DROP/INSERT/DROP in this situation would result in the graph being removed.

\n

If the destination graph does not exist, it will be created. By default, the service MAY return failure if the input graph does not exist. If SILENT is present, the result of the operation will always be success.

\n

Example 14:

\n

This example request moves all statements from the default graph into a named graph:

\n
MOVE DEFAULT TO <http://example.org/named>\n
\n

Data before:

\n
**# Default graph**\n@prefix foaf:  <http://xmlns.com/foaf/0.1/> .\n\n<http://example/william> a foaf:Person .\n<http://example/william> foaf:givenName \"William\" .\n<http://example/william> foaf:mbox  <mailto:bill@example> .\n
\n
**# Graph http://example.org/named**\n@prefix foaf:  <http://xmlns.com/foaf/0.1/> .\n\n<http://example/fred> a foaf:Person .\n<http://example/fred> foaf:givenName \"Fred\" .\n
\n

Data after:

\n
**# Default graph**\n
\n
**# Graph http://example.org/named**\n@prefix foaf:  <http://xmlns.com/foaf/0.1/> .\n\n<http://example/william> a foaf:Person .\n<http://example/william> foaf:givenName \"William\" .\n<http://example/william> foaf:mbox  <mailto:bill@example> .\n
\n

Note that the original content in http://example.org/named is lost by a MOVE operation.

"^^ ; . a ; "

CREATE

\n\n

This operation creates a graph in the Graph Store:

\n
**CREATE** ( **SILENT** )? **GRAPH** *[IRIref](../../../sparql11-query/grammar/#rIRIREF)*\n
\n

For stores that record empty graphs, this will create a new empty graph in the store with a name specified by the IRI. If the graph already exists, then a failureSHOULD be returned, except when the SILENT keyword is used; in either case, the contents of already existing graphs remain unchanged. If the graph may not be created, then a failureMUST be returned, except when the SILENT keyword is used.

\n

Stores that do not record empty named graphs will always return success on creation of a non-existing graph.

"^^ ; . a , ; "

Graph Management

\n\n

Graph management operations allow creating, destroying, moving and copying named graphs in the Graph Store, or adding the contents of one graph to another. Operations for creation and destruction are not required to result in any actions, since Graph Stores are not required to record the existence of empty named graphs.

\n

The default graph in a Graph Store always exists.

\n

SPARQL 1.1 Update provides these graph management operations:

\n
    \n
  • The CREATE operation creates a new graph in stores that support empty graphs.
    • \n
  • The DROP operation removes a graph and all of its contents.
    • \n
  • The COPY operation modifies a graph to contain a copy of another.
    • \n
  • The MOVE operation moves all of the data from one graph into another.
    • \n
  • The ADD operation reproduces all data from one graph into another.
    • \n
"^^ ; ; "Graph Management" . a ; "

ADD

\n\n

The ADD operation is a shortcut for inserting all data from an input graph into a destination graph. Data from the input graph is not affected, and initial data from the destination graph, if any, is kept intact.

\n
**ADD** ( **SILENT** )? ( ( **GRAPH** )? *[IRIref_from](../../../sparql11-query/grammar/#rIRIREF)* | **DEFAULT**) **TO** ( ( **GRAPH** )? *[IRIref_to](../../../sparql11-query/grammar/#rIRIREF)* | **DEFAULT**)\n
\n

is equivalent to:

\n
**INSERT** { ( **GRAPH** *[IRIref_to](../../../sparql11-query/grammar/#rIRIREF)* )? **{ ?s ?p ?o } } WHERE** { ( **GRAPH** *[IRIref_from](../../../sparql11-query/grammar/#rIRIREF)* )? **{ ?s ?p ?o } }**\n
\n

If the destination graph does not exist, it will be created. By default, the service MAY return failure if the input graph does not exist. If SILENT is present, the result of the operation will always be success.

\n

Example 15:

\n

This example request adds all statements from the default graph to a named graph:

\n
ADD DEFAULT TO <http://example.org/named>\n
\n

Data before:

\n
**# Default graph**\n@prefix foaf:  <http://xmlns.com/foaf/0.1/> .\n\n<http://example/william> a foaf:Person .\n<http://example/william> foaf:givenName \"William\" .\n<http://example/william> foaf:mbox  <mailto:bill@example> .\n
\n
**# Graph http://example.org/named**\n@prefix foaf:  <http://xmlns.com/foaf/0.1/> .\n\n<http://example/fred> a foaf:Person .\n
\n

Data after:

\n
**# Default graph**\n@prefix foaf:  <http://xmlns.com/foaf/0.1/> .\n\n<http://example/william> a foaf:Person .\n<http://example/william> foaf:givenName \"William\" .\n<http://example/william> foaf:mbox  <mailto:bill@example> .\n
\n
**# Graph http://example.org/named**\n@prefix foaf:  <http://xmlns.com/foaf/0.1/> .\n\n<http://example/fred> a foaf:Person .\n\n<http://example/william> a foaf:Person .\n<http://example/william> foaf:givenName \"William\" .\n<http://example/william> foaf:mbox  <mailto:bill@example> .\n
"^^ ; . a ; "

DROP

\n\n
**DROP**  ( **SILENT** )? (**GRAPH** *[IRIref](../../../sparql11-query/grammar/#rIRIREF)* | **DEFAULT** | **NAMED** | **ALL** )\n
\n

The DROP operation removes the specified graph(s) from the Graph Store. The GRAPH keyword is used to remove a graph denoted by IRIref, the DEFAULT keyword is used to remove the default graph from the Graph Store, the NAMED keyword is used to remove all named graphs from the Graph Store, and the ALL keyword is used to remove all graphs from the Graph Store, i.e., resetting the store. After successful completion of this operation, the specified graphs are no longer available for further graph update operations. However, in case the DEFAULT graph of the Graph Store is dropped, implementations MUST restore it after it was removed, i.e., DROP DEFAULT is equivalent to CLEAR DEFAULT.

\n

If the store records the existence of empty graphs, then the SPARQL 1.1 Update service, by default, SHOULD return failure if the specified named graph does not exist. If SILENT is present, the result of the operation will always be success.

\n

Stores that do not record empty graphs will always return success.

"^^ ; . a ; ; ; ; ; ; ; "2023-07-10T16:13:28.199Z"^^ ; "Graph Management" ; ; ; .