Hyperlinks are dumb. Literally dumb. They link one document to another – one little piece of text to another, but they don’t know how. They don’t know why. They don’t know diddly squat. The only real sense that search engines can make of their incoherent connections is that one page is more popular than another, probably, maybe. They’re dumb, first of all, because while they can relate two pieces of media on the Web, they don’t describe the nature of that relationship. At least – not in any way that computers can understand, which means therefore that we humans have to sort through the mess and – aint nobody got time for that. Second, they’re dumb because the only thing they know how to connect is media. They can link a page to a page or a page to a file, but they can’t link any real-world thing to any other real-world thing. They tell us all about the structure of websites, sure, but they don’t tell us anything meaningful about the real world. The link in Linked Data, however, changes all of that.
The link between two things in Linked Data is still very simple like a hyperlink, but much more powerful. When it relates one thing to another, it explicitly describes the nature of that relationship. By providing context to its connection, it creates knowledge. That’s right – the link itself is knowledge. And because Linked Data can connect URIs that identify real-world things, not just documents and media files, it can describe far more than the structure of a website. It can help us learn new things beyond the knowledge we explicitly programmed into our application. It’s connections make statements. And statements, together, tell stories. As vast graphs of information that span the globe, these stories can change the world again, much like the traditional hyperlink did over the last twenty-five years.
A link in Linked Data is, in fact, often referred to as a statement. It has the power, in and of itself, to make an assertion – to state a fact. It does so in very much the same way we humans do when we make a statement about something. We connect a subject to an object by way of some predicate.
This is the basic sentence structure we learned in grade school, remember? The subject of a sentence is the person, place, or thing that is performing the action. The predicate expresses the action or being. And the object indicates to whom or for whom the action is being done; it receives the action.
As simple as this statement is, a hyperlink would not commonly express the same underlying meaning. A blog post written by Jack might anchor to a blog post written by Jill, but that hyperlink relates the two documents, not the two people. It doesn’t say that Jill is a friend of Jack or Jack a friend of Jill. One could use the rel attribute introduced in HTML 4.01 along with a value from a microformat and that’s heading in the right direction, but still only a stop-gap solution. It introduces its own set of semantic issues that can be as perplexing to a search bot as random human keywords.
A link in Linked Data is an RDF statement, which has a subject, predicate, and an object.
The subject is a URI, which could resolve to some representation of a resource. What differentiates this from traditional linking on the Web is that the subject is assumed to represent any kind of thing, document or real-world. The URI is used more like an identifier than a locator. That’s why we use the term URI instead of URL. It’s kind of like a primary key for a record in a database, if you know how that works. Only this time, the database is your entire corporate intranet or the World Wide Web.
The predicate, the part that does the actual linking, is a property, which expresses the nature of the relationship. Though that property is also expressed with a URI, its URI represents some relational concept such as friend of, has sibling,or has mother. Such predicates (or properties) are often borrowed from well-established public vocabularies and as such, they express semantics or meaning that computers can be programmed to understand.
The object, the part that is linked to, is either some literal value (like a date, integer, string) or it is another resource with its own URI – some other real-world thing with a representation on the Web. And here’s the kicker. This object can be the subject of its own statements, with entirely new properties linking to entirely new objects. And that kind of linking creates a graph that has the power to grow far beyond what you and your little app can ever know alone. That’s awesome. That’s power.
OK, so maybe hyperlinks aren’t “dumb”. They got us this far, after all, didn’t they? They have been the glue for what today we call the World Wide Web. But if they can do all that, just imagine what the RDF triple, the link in Linked Data, can do.
Want to leverage the power of Linked Data in your next software solution?
Try Carbon LDP™ – a Linked Data application server that provides read/write access to RDF graph data over RESTful HTTP. Carbon provides a host of features for developing applications with Linked Data and for simplifying access to the enterprise knowledge graph. As such, it can act as the key system upon which you can build to capitalize on the benefits of Linked Data. It consolidates the Linked Data ecosystem within an enterprise into one common access point, or server, and exposes the knowledge graph as easily accessible web resources through an API. Carbon LDP makes it easier and faster for everyday web developers to build apps that process and manage data.