One of the biggest impediments to the adoption of technology is
the cost burden typically associated with doing the right thing.
For instance, requirements for making the Linked Data Web (GGG) buzz
would include the following (paraphrasing TimBL's original
The list is nice, but actual execution can be challenging. For
instance, when writing a blog post, or constructing a
you have enough disposable time to go searching for these URIs? Or
would you compromise and continue to inject "Literal" values into
the Web, leaving it to the reasoning endowed human reader to
connect the dots?
Anyway, OpenLink Data
Spaces is now equipped with a Glossary system that
allows me to manage terms, meaning of terms, and hyper-linking of
phrases and words matching associated with my terms. The great
thing about all of this is that everything I do is scoped to
my Data Space
(my universe of discourse), I don't break or impede the other
meanings of these terms outside my Data Space. The Glossary system
can be shared with anyone I choose to share it with, and even
better, it makes my upstreaming (rules based replication) style of
blogging even more productive :-)
Remember, on the Linked Data Web, who you know doesn't matter as
much as what your are connected to, directly or indirectly.
Jason Kolb covers this
issue in his post: People as Data Connectors, and so
doesFrederick Giasson via a recent post titled: Networks are everywhere. For instance,
this blog post (or the entire Blog) is a bona fide RDF
Linked Data Source, you can use it as the Data Source of a SPARQL Query to find
things that aren't even mentioned in this post, since all you are
doing is beaming a query through my Data Space (a container of
Linked Data Graphs). On that note, let's re-watch Jon Udell's "On-Demand-Blogosphere" screencast from 2006
About this entry:
Author: Kingsley Uyi Idehen
Published: 03/27/2008 18:41 GMT-0500
Modified: 03/29/2008 00:50 GMT-0500
Tags: rdf , semanticweb , web30 , sparql , howto , screencast , openlink , DataSpace
Categories: Semantic Web
Comment Status: 1
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.