Graph Concepts: You Are Your URL

Posted by Luigi Montanez
on Sunday, April 27

As the next wave of communications technology evolves from the Net (network of computers) to the Web (web of documents) to the Graph (directed graph of people, places, and things), it’s important to keep in mind the big ideas that are driving the innovations. In this series of blog posts, I’ll go over four (and maybe more) concepts:

  1. You Are Your URL
  2. You Control Your Data
  3. Collective Intelligence Wins Over Artificial Intelligence
  4. Attention is a Scarce Commodity

Let’s begin with the first concept: that a URL is the best identifier for a person.

The OpenID Endpoint

The promise of OpenID is single sign-on to any supporting website. But what makes OpenID more special than any other previous single sign-on system is that it uses a URL (or if you want to be semantically correct, a URI) as the identifier. So, luigimontanez.com is my personal website as well as my OpenID. A URL is much more powerful as an identifier because it can act as a publicly accessible endpoint. An endpoint can contain things like links to that individuals other profiles around the Web, links to friends and contacts, marked-up HTML code that provides contact information, pointers to other services, and so much more.

Other Forms of Identification

As OpenID adoption grows, the notion of a URL acting as an identifier (instead of user name or email address) will become mainstream. When this happens, the URL will be the person. Today, if I say the name “Barack Obama”, you immediately know who I mean. A picture pops into your head of him, maybe his voice, maybe what has been recently said about him in the news. You associate the two words “Barack Obama” with the presidential candidate, even though it’s likely that there are at least a few more Barack Obama’s in the world. So the name, “Barack Obama”, is in fact not a unique identifier, even though it’s a pretty good one.

Conversely, if I were to show you this picture:

You would immediately think “Barack Obama”, and just as before, you may hear his voice in your mind or recent news items about him might be conjured up. The picture is a better identifier in the sense that it really, truly means I’m talking about that Barack Obama. It is, then, a unique identifier. But, and this is a big but, one has to know what Barack Obama looks like in order for the identifier to be useful. While most Americans and probably most Westerners know what Obama looks like, chances are many in the developing world have no idea. More importantly for the Graph, a website or service won’t be able to identify a person via photograph either (barring advanced face recognition technologies).

So we need an identifier that is truly unique yet in a form that all computers can recognize. An email address certainly fits the bill, and has been the standard identifier since the beginning of the Web. But, because of some very good privacy and spam concerns, personal email addresses aren’t generally made public. So while I use my email address to identify myself to Facebook, others in Facebook identify me via my name. Also, email addresses are uni-taskers when it comes to actual functionality. There’s only one thing you can do with an email address: send an email to it.

Arriving to the URL as the Solution

How about the URL as an identifier?

  • It’s unique. No one will have the same URL as you.
  • It’s universally accessible. Through the magic of DNS, any person or computer hooked up to the Internet can access the URL and its content.
  • It’s a multi-tasker. The page living at the URL can be configured to accept and output just about any kind of data.

Here’s a simple but powerful example. Let’s say that you and I are in the same city, and you’re wondering if I’m free for lunch today. You have a myriad of options:

  • Call me. But you’d have to know my highly arbitrary phone number.
  • Text me. See above.
  • Email me. Obviously, you’d need to know my email address.
  • IM me. You’d need to know my screen name and be on the same service I use.
  • Tweet me. Send me a direct message or an @ message via Twitter. We’d have to be following each other on Twitter for this to work.

But there are many points of failure here. If you call or text me and my cell phone is dead, you’re out of luck. If I’m out and about for the day and not online, the last three options don’t work. But what if you had a simple interface for sending me a message via my URL, easily discoverable via a quick Google search? Imagine a magic application window that lives on your computer or your cell phone where you could type:

@luigimontanez.com Want to meet for lunch?

On my end, my luigimontanez.com endpoint is set to receive messages and forward them to me as I see fit. Maybe I’m at my computer all day so I want to get messages via Jabber, or I’m a vain nerd and want them forwarded to my #luigirocks IRC chatroom on Freenode. Maybe the text-based message gets converted to a Stephen Hawking-like voice and I get a call from some VOIP service I’ve set up. Maybe I want messages from people I know to hit me in several ways, while messages from strangers are just dropped in my email inbox.

You don’t have to worry about how I get the message, you simply have to identify who I am (via my URL) and provide a message. Great, isn’t it?

That’s the power of what’s possible when You Are Your URL.