A term coined by Tim Berners-Lee that describes HTTP-based Data Access by Reference for the Web
A richer Linking mechanism for the Web that takes us from Hypertext Links (Document to Document) to Hyperdata Links (across things that documents are about)
Why is Linked Data Important?
It exposes the compound nature of Web Resources
Information Resources (Containers) are uniquely Identified & Referenceable
Entities within Containers are uniquely Identified & Referencable
It provides an Open Data Access & Connectivity mechanism for the Web
It delivers a powerful mechanism for meshing disparate and heterogeneous structured data sources
It offers an unobtrusive mechanism for unveiling the virtues of the broader Semantic Web vision.
Linked Data Tenets
Give Names to things you describe so that they become uniquely Identifiable Resources (Data Sources)
Incorporate HTTP into your naming scheme so that you expand data access scope across your internal and external networks
Use the RDF Data Model to describe your Resources
Use HTTP-based Resource Names (URIs) when creating RDF Data Model records (Triples).
Linked Data & ODBC Similarities
Linked Data & ODBC Differences
Open Database Connectivity Lacks:
Model Dexterity
(tightly bound to Relational Model)
Reference Granularity
(stops at Table/View level i.e. cannot reference individual data entities directly)
HTTP protocol component in Naming Scheme (vulnerable DBMS engine, Host OS, Network Protocol, and other infrastructural specificity / confinements).
What is the Linked Data Web?
A World Wide Web of Named Data Sources (Compound Documents and Entities are distinctly named)
A Giant Global Graph of Named Data Sources where Hyperdata Links provide the Link Tapestry
An evolution of the Web where the Description of anything is discernible via it's Data Source Name (URI).
The Linked Data Journey
Computer Network Infrastructure
Distributed Computing
Distributed Databases
Compound Documents
Distributed Objects
Network: Routers link Computers
Internet Layer: Cloud hides Routers
Internet: Computers Link to Documents
Web Layer: Docs hide Computers
Web: Hypertext Links between Documents
Linked Data Layer: Entities hide Documents
Linked Data: Hyperdata Links within Documents
Linked Data Web: Hyperdata Links across Data Spaces
Linked Data Web - Yet Another Abstraction Layer
Linked Data Web Materialization
Generated "on the fly" via RDF middleware from:
Existing Web Pages (POSH, Microformats, eRDF, RDFa, GRDDL)
Web 2.0 Data Spaces (Social Networks, Blogs, Wikis, Bookmarks, Online Discussions / Conversations etc)
DBpedia, Bio2RDF, and many other Linking Open Data projects
How Linked Data is Generated "on the fly"
Linked Data Generation from Existing Dynamic Web Content
Linked Data Generation from Existing Web Services
Linked Data Generation from Enterprise Data Sources
Linked Data Generation from Existing Web Content
Linked Data Generation via RDF Middleware (RDFizers)
How Do I Deploy Linked Data?
Obtain a Linked Data Server capable of:
Creating URL rewrite-rules for handling Content Negotiation requests
Associating URL rewrite-rules with RDF data store queries using SPARQL
Generating Information Resources "on the fly" that provide physical provenance to Resource Descriptions
Minting dereferenceable HTTP URIs (including wrapper/proxy URIs for non RDF Linked Data Source)
Incorporating RDFization for transforming non-RDF Data into RDF)
Linked Data Access Mechanics
Linked Data Publishing Tenets
When a "User Agent" requests (X)HTML, make a "best effort" to expose associated RDF data via any of the following:
Use the <head/> section's <link/> tag to expose RDF Data Source Names
Use simple RDFa or eRDF statements to embedded RDF Data Source Names within the (X)HTML via the <head/> section's <profile/> tag for eRDF or RDFa use declaration and <link/> tag to expose RDF Data Source Names
If XHTML, use GRDDL to glean RDF from the source document via a combination of the GRDDL use declaration in the <head/> section's <profile/> tag and an XSLT stylesheet exposed via the <link/> tag