Skip to content
This repository was archived by the owner on Jan 22, 2020. It is now read-only.

Update introduction-to-hyperledger-indy.md #159

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

Update introduction-to-hyperledger-indy.md #159

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions LFS171x/docs/introduction-to-hyperledger-indy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -531,9 +531,7 @@ The Sovrin Foundation provides the three foundational components of the Sovrin N

All three parts are necessary to enable a global, trusted system for identity. The need for Legal Agreements and a sound Technical foundation are fairly obvious, but what is a "Trust Framework"?

Trust Frameworks are common in the digital identities world, but are also used in other contexts (with other names, such as "operating regulations" and "operating policies"). In all cases, they define how to govern multi-party systems where participants desire the ability to engage in a common type of transaction with any of the other participants, and to do so in a consistent and predictable manner. A trust framework enables an organization to count on

the business and/or technical processes carried out by another organization. In many cases, Trust Frameworks have been able to work and most importantly, scale. Common examples include credit card systems, electronic payment systems and the internet domain name registration system, which all rely on a set of interdependent specifications, rules, and agreements.
Trust Frameworks are common in the digital identities world, but are also used in other contexts (with other names, such as "operating regulations" and "operating policies"). In all cases, they define how to govern multi-party systems where participants desire the ability to engage in a common type of transaction with any of the other participants, and to do so in a consistent and predictable manner. A trust framework enables an organization to count on the business and/or technical processes carried out by another organization. In many cases, Trust Frameworks have been able to work and most importantly, scale. Common examples include credit card systems, electronic payment systems and the internet domain name registration system, which all rely on a set of interdependent specifications, rules, and agreements.

An Identity Trust Framework defines the rules for interactions between organizations for handling identity, authentication (who you are), and authorization (what you are allowed to do). The Sovrin Trust Framework defines those rules for the organizations using the Sovrin Network.

Expand Down