Named graphs are a key concept of Semantic Web architecture in which a set of Resource Description Framework statements (a graph) are identified using a URI, allowing descriptions to be made of that set of statements such as context, provenance information or other such metadata. Named graphs are a simple extension of the RDF data model through which graphs can be created but the model lacks an effective means of distinguishing between them once published on the Web at large. Named graphs and HTTP One conceptualization of the Web is as a graph of document nodes identified with URIs and connected by hyperlink arcs which are expressed within the HTML documents. By doing an HTTP GET on a URI (usually via a Web browser), a somehow-related document may be retrieved. This "follow your nose" approach also applies to RDF documents on the Web in the form of Linked Data, where typically an RDF syntax is used to express data as a series of statements, and URIs within the RDF point to other resources. This Web of data has been described by Tim Berners-Lee as the "Giant Global Graph". Named graphs are a formalization of the intuitive idea that the contents of an RDF document (a graph) on the Web can be considered to be named by the URI of the document. This considerably simplifies techniques for managing chains of provenance for pieces of data and enabling fine-grained access control to the source data. Additionally, trust can be managed through the publisher applying a digital signature to the data in the named graph. (Support for these facilities was originally intended to come from RDF reification, however, that approach proved problematic.) Named graphs and RDF stores While named graphs may appear on the Web as simple linked documents (i.e. Linked Data), they are also very useful for managing sets of RDF data within an RDF store. In particular, the scope of a SPARQL query may be limited to a specific set of named graphs. Example Assume the following (Turtle) RDF document has been placed in a SPARQL-capable store with the name . @prefix foaf: <http://xmlns.com/foaf/0.1/> . <http://example.org/joe#me> a foaf:Person . <http://example.org/joe#me> foaf:homepage <http://example.org/joe/index.html> . <http://example.org/joe#me> foaf:mbox <mailto:joe@example.org> . <http://example.org/joe#me> foaf:name "Joe Lambda" . This data has been written in a more verbose form than necessary to show the triple structures The homepage of the person with the email address can be obtained