Month: March 2012

Sovereign-source vs. administrative identity

You know who you are. So does the IRS, the DMV, and every Website you’ve ever made up a login and a password for — so it could “know” you.

But none of those entities really knows you. What they know is what the techies call a namespace. What they have isn’t your identity, but an identifier. What they call your identity is an administrative construction. It’s something that had to be made up so that bureaucracies and technical systems could do what they do.

Who you are isn’t just how you appear in the namespaces of administrative entities. Who you are isn’t even the name your parents gave you. It’s your single, unitary and sovereign self, which remains fixed at the source, no matter what you’re called.

While the names that matter most to you are the ones you were given at birth, and the ones you choose to be called by, neither is fixed. You can change your names without changing who you are.

Walt Whitman, the great author of Song of Myself, did not call himself Walter.

Yes, some names come about socially, but the choice to use them for ourselves is personal. Take my own example. The name my parents gave me was David. Many friends and relatives still call me David or Dave. Many more, however, call me Doc. That name is what remains of Doctor Dave, which is what I was called on the radio and in a humor column in North Carolina in the late ’70s. (That image above was how I appeared in the column. I was around 30 then. I actually look like that now.)

The nickname Doc came along after I started a company with two other guys, one of whom was named David. He and the other guy (the late great Ray Simone, who also drew the Doctor Dave image) called me Doctor Dave around the office, and with clients and suppliers. After awhile three syllables seemed too many, and they all just called me Doc.

But the nickname then was still context-dependent. People who knew me through business called me Doc. Everybody else called me David or Dave.

Then our company opened an office in Silicon Valley and I went out there prospecting, in the Fall of ’85. I knew almost nobody there, other than a few business contacts who called me Doc. But I wasn’t sure about keeping Doc as a nickname, since in a way I was starting over in a new palce. So, when I went to the Comdex conference in October of that year in Las Vegas, I had two badges made. One said David Searls and the other said Doc Searls. I was there four days and alternated between the two badges. Afterwards everybody remembered Doc and nobody remembered David. So I decided not to dump the nickname, and it stuck.

My point is that I still had control over what I chose to be called. I had sovereign source authority over that.

The problem I’m trying to surface here is that we need full respect for sovereign source identities, and identifiers, before we can solve the problem of highly fractured and incompatible administrative identifiers — a problem that has only become worse with the growth of the Web, where by design we are always the submissive and dependent party: calves to administrative cows.

MoxyTongue puts it this way:

You are a social ID-slave by default today.

I want a Human ID; a personal data construct with sovereign source authority.

Society uses a social construct to give me an Administrative ID.

The difference is origin.

I do not participate in Society primarily as an AdminID.

I am a Human ID by sovereign source authority, backed by American Rights that I know how to wield administratively and matriculate accordingly.

Structure yields results. Therefore, if we get the origin of ID correct, we can get the data administration framework oriented right.

A Human ID -led Society with embedded structural Rights and empowerments is the socio-economic game changer.

That is my NSTIC proposal. That’s my open proposal: a new data administration framework for identity.

Deployed across Society by opt-in opportunity structure.

Deployable across a global ecosystem by data design.

I see an ID as a door. The existence of the door is a social construct… a decision…

But once that decision is made, it is Human executed in every regard.

ID-slavery is what we have by administrative structure today. Our managerial intent in servicing it is flawed by design.

A Human ID comes with #vrm baked in. Such is the bi-directional transactional authority, multi-role nature of it.

And most important… we all approach the door on equal Terms… one door…infinite possibilities.

Self-driven socio-economic structure.

Call it whatever you want…it starts with your identity being structured right.

VRM for me grew out of two things:

  1. The unfinished work of Cluetrain. The ‘one clue to get’ there said “our reach exceeds your grasp.” But it didn’t, and it still doesn’t. Much of the grasp is administrative, and it has to do with defining, for us, who we are. That’s a bug, not a feature.
  2. The unfinished work of the digital identity development community, which I believe will remain unfinished as long as we try to solve one symptom with another one. The symptom we’re trying to solve is regarding administrative IDs as independent variables, rather than as dependent ones. Until we recognize that the only true independent variable is the soul of the independent self, we’ll continue to seek administrative solutions to the problem of administrative identity slavery.

Have you ever noticed that when somebody says “That’s a good question?” it’s usually because they don’t yet have an answer? That applies here. To the question of how we make sovereign-source identity the independent variable, I don’t have an answer. But I do want to work on it.

I’ll be doing that tomorrow at a meeting on identity in Silicon Valley. On May 1-3 in Mountain View we’ll be holding the Internet Identity Workshop again. It’s our fourteenth, and it’s a terrific unconference. If you care about this stuff, you should come. Your sovereign self would like that.

Your actual wallet vs./+ Google’s and Apple’s

Now comes news that Apple has been granted a patent for the iWallet. Here’s one image among many at that last link:

iwallet

Note the use of the term “rules.” Keep that word in mind. It is a Good Word.

Now look at this diagram from Phil Windley‘s Event Channels post:

event channels

Another term for personal event network is personal cloud. Phil visits this in An Operating System for Your Personal Cloud, where he says, “In contrast a personal event network is like an OS for your personal cloud. You can install apps to customize it for your purpose, it canstore and manage your personal data, and it provides generalized services through APIsthat any app can take advantage of.” One of Phil’s inventions is the Kinetic Rules Language, or KRL, and the rules engine for executing those rules, in real time. Both are open source. Using KRL you (or a programmer working for you, perhaps at a fourth party working on your behalf, can write the logic for connecting many different kinds of events on the Live Web, as Phil describes here).

What matters here is that you write your own rules. It’s your life, your relationships and your data. Yes, there are many relationships, but you’re in charge of your own stuff, and your own ends of those relationships. And you operate as  free, independent and sovereign human being. Not as a “user” inside a walled garden, where the closest thing you can get to a free market is “your choice of captor.”

Underneath your personal cloud is your personal data store (MyDex, et. al.), service (Higgins), locker (Locker Project / Singly), or vault (Personal.com). Doesn’t matter what you call it, as long as it’s yours, and you can move the data from one of these things into another, if you like, compliant with the principles Joe Andrieu lays out in his posts on data portability, transparency, self-hosting and service endpoint portability.

Into that personal cloud you should also be able to pull in, say, fitness data from Digifit and social data from any number of services, as Singly demonstrates in its App Gallery. One of those is Excessive Mapper, which pulls together checkins with Foursquare, Facebook and Twitter. I only check in with Foursquare, which gives me this (for the U.S. at least):

Excessive Mapper

The thing is, your personal cloud should be yours, not somebody else’s. It should contain your data assets. The valuable nature of personal data is what got the World Economic Forum to consider personal data an asset class of its own. To help manage this asset class (which has enormous use value, and not just sale value), a number of us (listed by Tony Fish in his post on the matter) spec’d out the Digital Asset Grid, or DAG…

DAG

… which was developed with Peter Vander Auwera and other good folks at SWIFT (and continues to evolve).

There are more pieces than that, but I want to bring this back around to where your wallet lives, in your purse or your back pocket.

Wallets are personal. They are yours. They are not Apple’s or Google’s or Microsoft’s, or any other company’s, although they contain rectangles representing relationships with various companies and organizations:

Still, the container you carry them in — your wallet — is yours. It isn’t somebody else’s.

But it’s clear, from Apple’s iWallet patent, that they want to own a thing called a wallet that lives in your phone. Does Google Wallet intend to be the same kind of thing? One might say yes, but it’s not yet clear. When Google Wallet appeared on the development horizon last May, I wrote Google Wallet and VRM. In August, when flames rose around “real names” and Google +, I wrote Circling Around Your Wallet, expanding on some of the same points.

What I still hope is that Google will want its wallet to be as open as Android, and to differentiate their wallet from Apple’s through simple openness.  But, as Dave Winer said a few days ago

Big tech companies don’t trust users, small tech companies have no choice. This is why smaller companies, like Dropbox, tend to be forces against lock-in, and big tech companies try to lock users in.

Yet that wasn’t the idea behind Android, which is why I have a degree of hope for Google Wallet. I don’t know enough yet about Apple’s iWallet; but I think it’s a safe bet that Apple’s context will be calf-cow, the architecture I wrote about here and here. (In that architecture, you’re the calf, and Apple’s the cow.) Could also be that you will have multiple wallets and a way to unify them. In fact, that’s probably the way to bet.

So, in the meantime, we should continue working on writing our own rules for our own digital assets, building constructive infrastructure that will prove out in ways that require the digital wallet-makers to adapt rather than to control.

I also invite VRM and VRooMy developers to feed me other pieces that fit in the digital assets picture, and I’ll add them to this post.

© 2014 ProjectVRM

Theme by Anders NorenUp ↑