Motivation for this post arose from a series of Twitter
exchanges between Tony Hirst and I, in relation to his
blog post titled: So What Is It About Linked Data that Makes it
Linked Data™ ?
At the end of the marathon session, it was clear to me that a blog post was required for future
reference, at the very least :-)
"Data Access by Reference" mechanism for Data
Objects (or Entities) on HTTP networks. It enables you to Identify
a Data Object and Access its structured Data Representation via a
single Generic HTTP scheme based Identifier (HTTP URI). Data Object representation formats may
vary; but in all cases, they are hypermedia oriented, fully structured, and
negotiable within the context of a client-server message
Information makes the world tick!
Information doesn't exist without data to contextualize.
Information is inaccessible without a projection (presentation)
All information (without exception, when produced by humans) is
subjective. Thus, to truly maximize the innate heterogeneity of
collective human intelligence, loose coupling of our information
and associated data sources is imperative.
Linked Data is exposed to HTTP networks (e.g. World Wide Web) via hypermedia resources
bearing structured representations of data object descriptions.
Remember, you have a single Identifier abstraction (generic HTTP
URI) that embodies: Data Object Name and Data Representation
Location (aka URL).
A structured representation of data exists when an Entity (Datum), its Attributes, and its
Attribute Values are clearly discernible. In the case of a Linked
Data Object, structured descriptions take the form of a hypermedia
based Entity-Attribute-Value (EAV) graph pictorial
-- where each Entity, its Attributes, and its Attribute Values
(optionally) are identified using Generic HTTP URIs.
Examples of structured data representation formats (content
types) associated with Linked Data Objects include:
You markup resources by expressing distinct
entity-attribute-value statements (basically these a 3-tuple
records) using a variety of notations:
You can achieve this task using any of the following
Our data access middleware heritage (which spans 16+ years) has
enabled us to assemble a rich portfolio of coherently integrated
products that enable cost-effective evaluation and utilization of
Linked Data, without writing a single line of code, or exposing you
to the hidden, but extensive admin and configuration costs. Post
installation, the benefits of Linked Data simply materialize (along
the lines described above).
Our main Linked Data oriented products include:
About this entry:
Author: Kingsley Uyi Idehen
Published: 03/04/2010 10:16 GMT-0500
Modified: 03/08/2010 09:59 GMT-0500
Tags: webservices , web2.0 , web20 , atom , rdf , xml , linked_data , semanticweb , virtuoso , ods , openlink , DataSpace
Categories: Demos , Virtual Database , SQL , Semantic Web , Web Services (Web 2.0) , Content Syndication
Comment Status: 0
This document is empty and basically useless. It is generated by a web service that can make some statements in HTML+Microdata format.
This time the service made zero such statements, sorry.