Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update self-sovereign-identity-primer.md #96

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

nsmolenski
Copy link

Hello WoT Group,

I have reviewed and revised the Primer on Self-Sovereign Identity.

Natalie

@jandrieu
Copy link
Contributor

There's much to appreciate in this revision, but it ignores the functional foundation that Chris, I, and others, are hoping to build upon. Defining self-sovereign identity as a container is explicitly counter to the functional perspective, undermining, in this article, the subsequent framing based on that.

If we are to build upon the functional definition of identity,

Identity is how we keep track of people and things, and in turn how they keep track of us

then self-sovereign identity emerges from negotiated boundaries of control over that tracking. This debate, this fight, is what establishing self-sovereign identity is about.

@matthewjosef @ChristopherA

@nsmolenski
Copy link
Author

nsmolenski commented Oct 22, 2017 via email

@jandrieu
Copy link
Contributor

jandrieu commented Oct 22, 2017

I would say the container is a common artifact used to track people across contexts, but it isn't the identity. Even with self-sovereign "identity containers", observers will continue to maintain their notion of our identity within the systems they can perceive. Whether its an internal unique key in a database and log files of my http requests or the ephemeral gist of experiential contact in the mind of another person, the identity is fundamentally in the minds-eye of the observer, independent of the artifacts used to track it. The goal of the tracking is not the container, but the subject.

The question of self-sovereign identity must include not just some sort of "identity container", but also negotiations over how people are tracked, how attributes are derived, how attributes are used, and how attributes are controlled. Framing self-sovereign identity in the core definition as a "container" suggests that managing the container addresses all the current challenges with the surveillance systems baked into our digital world. This connects to my longer rant on PII, which I'll spare you except to say that as a framing, PII evokes the wrong mental models in both engineers and regulators. I think containers do the same wrong.

Functionally, all identity systems are tracking systems, for which individuals deserve some control if we are to live in a free society. DIDs enable self-sovereign control over a root identifier. VCs offer the promise of authoritative attributes without ongoing dependence on those authorities, giving individuals control over the creation and sharing of identity information and the ability to participate as peer authorities.

What the self-sovereign conversation--as a whole, not just in this primer--is missing at this point is a solid framing for engaging the boundaries of the rest of the attribute-driven information tracking and sharing system. I contend that the problem with information sharing is... that you are sharing information. That, in fact, the most self-sovereign architecture minimizes sharing of attributes, not just gives users control over who gets what data.

It's key that our definition of self-sovereign identity advances the conversation towards addressing these more distributed, intertextual challenges. "Containers" feels like a framing that undermines that progression.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants