mirror of
https://github.com/Decentralized-ID/decentralized-id.github.io.git
synced 2024-07-08 20:01:53 +00:00
links
This commit is contained in:
⧉ infominer
parent
8ede57db03
commit
0d2beadb69
|
|
@ -31,7 +31,8 @@ last_modified_at: 2019-07-11
|
|||
> The components of SSI will be described in detail, evaluated, and visualized in a components architecture. These include standards like decentralized identifiers (DIDs), verifiable credentials (VCs), and verifiable presentations (VPs). Further, the concepts of a decentralized public key infrastructure (DPKI) and a decentralized key management system (DKMS) are introduced. Additionally, this thesis deals in detail with the trust infrastructure of SSI.
|
||||
>
|
||||
> Additionally, this thesis focuses on SSI systems and their underlying DID methods. To provide an overview of existing identity systems, the SSI ecosystem is analyzed on its currently existing DID methods. Based on the presented DID methods, representative DID methods are selected and examined for further analysis and evaluation of the system. To analyze the DID methods and their systems, criteria are defined to emphasize the differences of each DID method. The results from the analysis are then used for evaluating the DID methods.
|
||||
|
||||
* [Distributed Ledger Technology for eHealth Identity Privacy: State of The Art and Future Perspective](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7013398/)
|
||||
> In the decentralized trusted identity model, the identity provider still centralized and performs the user’s identity proofing based on trusted credentials like passports or driver licenses while uses the DLT to store the identity attestation for later validation by third parties services and trusted organizations as is shown in Figure 1b [46]. The decentralized trusted identity doesn’t use the concept of identity repository which is the slight difference from the SSI model, and the identity provider will provide the receiving entity a testimony on the validity of the data while all the credentials are encrypted and stored locally in the user phone.
|
||||
|
||||
## Reports
|
||||
* [EU BLOCKCHAIN OBSERVATORY AND FORUM — Workshop Report — e-Identity, Brussels, November 7, 2018](https://www.eublockchainforum.eu/sites/default/files/reports/workshop_5_report_-_e-identity.pdf)
|
||||
|
|
|
|||
|
|
@ -28,6 +28,8 @@ I've begun exploring and becoming more familiar with the decentralized nature of
|
|||
|
||||
## High Level Overview
|
||||
|
||||
* [*Overview of Decentralized Identity Standards*](https://medium.com/decentralized-identity/overview-of-decentralized-identity-standards-f82efd9ab6c7), Nader Helmy
|
||||
> A standard, open protocol for establishing unique, private and secure connections between multiple parties without requiring the assistance of an intermediary “connection broker,” like Google, WhatsApp, an email provider, or a phone carrier. Secure connections are created by two or more peers creating and exchanging decentralized identifiers or “DIDs.”
|
||||
|
||||
* [**_A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems_**](https://arxiv.org/pdf/1908.00929.pdf) NIST CYBERSECURITY WHITE PAPER (DRAFT) BLOCKCHAIN IDENTITY MANAGEMENT APPROACHES
|
||||
JULY 9, 2019
|
||||
|
|
@ -44,11 +46,6 @@ JULY 9, 2019
|
|||
## Standards Bodies
|
||||
**_and other orgs worth keeping an eye on_**
|
||||
|
||||
I will begin with a listing of standards bodies, organizations and open processes, to which I'm paying attention (in addition to those previously gathered). From there, integrate and expand, as able.
|
||||
|
||||
* [*Overview of Decentralized Identity Standards*](https://medium.com/decentralized-identity/overview-of-decentralized-identity-standards-f82efd9ab6c7), Nader Helmy
|
||||
> A standard, open protocol for establishing unique, private and secure connections between multiple parties without requiring the assistance of an intermediary “connection broker,” like Google, WhatsApp, an email provider, or a phone carrier. Secure connections are created by two or more peers creating and exchanging decentralized identifiers or “DIDs.”
|
||||
|
||||
* [ISSA (Information Systems Security Association)](https://www.issa.org/)
|
||||
* [ISAO Standards](https://www.isao.org/)
|
||||
* [IETF](https://datatracker.ietf.org/wg/)
|
||||
|
|
@ -56,7 +53,6 @@ I will begin with a listing of standards bodies, organizations and open processe
|
|||
* [ISO](https://www.iso.org/committee/6266604/x/catalogue/p/0/u/1/w/0/d/0)
|
||||
* [IEEE](https://standards.ieee.org/)
|
||||
* [DIF](https://identity.foundation/working-groups/) - [GitHub](https://github.com/decentralized-identity/)
|
||||
* [Self Sovereign Identity Stack](https://medium.com/decentralized-identity/the-self-sovereign-identity-stack-8a2cc95f2d45)
|
||||
* [Fido Alliance](https://fidoalliance.org/)
|
||||
* [Hyperledger](https://www.hyperledger.org/join-a-group) - [Wiki](https://wiki.hyperledger.org/display/HYP/Working+Groups)
|
||||
* [Kantara](https://kantarainitiative.org/groups/)
|
||||
|
|
@ -67,6 +63,10 @@ I will begin with a listing of standards bodies, organizations and open processe
|
|||
|
||||
{% include figure image_path="/images/1280px-Who-Runs-the-Internet-graphic.png" alt="https://es.wikipedia.org/wiki/Archivo:Who-Runs-the-Internet-graphic.png" caption="[*Internet Governance*](https://en.wikipedia.org/wiki/Internet_governance)" %}
|
||||
|
||||
## NIST
|
||||
|
||||
- [FIPS PUB 201-3 (DRAFT) Federal Information Processing Standards Publication](https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.201-3-draft.pdf) (Supersedes FIPS 201-2)
|
||||
> Personal Identity Verification (PIV) of Federal Employees and Contractors
|
||||
|
||||
## W3C
|
||||
|
||||
|
|
|
|||
|
|
@ -22,9 +22,10 @@ Not all verifiable credentials are created the same. This post examines the cate
|
|||
* [Verifiable Credential Exchange](https://www.windley.com/archives/2018/12/verifiable_credential_exchange.shtml)
|
||||
> Multi-source identity (MSI) depends on issuing, exchanging, and verifying digital credentials. The specification for verifiable credentials is being formulated by the World Wide Web Consortium’s Verifiable Credentials Working Group. Verifiable credentials provide a standard way to express credentials in a way that is cryptographically secure, privacy respecting, and automatically verifiable.
|
||||
* [Verifiable Claims Task Force Use Cases](https://opencreds.org/specs/source/use-cases/)
|
||||
* [2018 Texas Bitcoin Conference in Austin, Texas.](https://www.youtube.com/watch?v=uDqLYv379gI)
|
||||
> 13:14 what if I was would like to prove that I had a certain diploma man if the university would basically state that I have a certain diploma because I asked them to and if they put the proof basically the fingerprint of that claim onto the blockchain then I can prove I am I have that certain diploma but why would I trust that because if I would say I have the diploma but you still have the same problem as we had using a scan the reason why you can trust it is because it was actually the university signing off on the fact that I have a certain diploma and how does that work in the end you will need those decentralized identifiers I talked about earlier to make sure that every piece of information on the blockchain is you are able to validate those and you are able to retrieve if you'd like the underlying data off chain
|
||||
* [Intro to Verifiable Cliams by W3C VCWG Members -iiw.idcommons.net](http://web.archive.org/web/20171228060921/http://iiw.idcommons.net/2J/_Intro_to_Verifiable_Cliams_by_W3C_VCWG_Members)
|
||||
* [Verifiable Credentials 101 for SSI - Tyler Ruff - Webinar 11](http://ssimeetup.org/verifiable-credentials-101-ssi-tyler-ruff-webinar-11/)
|
||||
> Tyler Ruff, product manager at Evernym, will be our next guest to walk us through Verifiable Credentials in the context of Self-Sovereign Identity. He will cover how they are created, issued and shared, as well as cover some common technical questions.
|
||||
|
||||
|
||||
|
||||
|
||||
## Application
|
||||
|
|
@ -74,7 +75,7 @@ Not all verifiable credentials are created the same. This post examines the cate
|
|||
* [bcgov/TheOrgBook](https://github.com/bcgov/TheOrgBook)
|
||||
> A public repository of verifiable claims about organizations. A key component of the Verifiable Organization Network.
|
||||
|
||||
## CCG
|
||||
### CCG
|
||||
|
||||
* [Credentials Community Group](https://www.w3.org/community/credentials/) - [Website](https://w3c-ccg.github.io/) - [Mail archive](http://lists.w3.org/Archives/Public/public-credentials/)
|
||||
> The mission of the Credentials Community Group is to explore the creation, storage, presentation, verification, and user control of credentials. We focus on a verifiable credential (a set of claims) created by an issuer about a subject—a person, group, or thing—and seek solutions inclusive of approaches such as: self-sovereign identity; presentation of proofs by the bearer; data minimization; and centralized, federated, and decentralized registry and identity systems. Our tasks include drafting and incubating Internet specifications for further standardization and prototyping and testing reference implementations.
|
||||
|
|
@ -85,7 +86,7 @@ WORK ITEM: Drafts and Ideas of Educational and Occupational Verifiable Credentia
|
|||
* [w3c-ccg/vc-examples](https://github.com/w3c-ccg/vc-examples)
|
||||
WORK ITEM: Verifiable Credentials Examples.
|
||||
|
||||
## VC-WG
|
||||
### VC-WG
|
||||
|
||||
* [W3C Verifiable Claims Working Group](https://www.w3.org/2017/vc/WG/) - [Mail Archives](https://lists.w3.org/Archives/Public/public-vc-wg/) - Technical discussion and public announcements for the Verifiable Claims Working Group
|
||||
> The mission of the Verifiable Claims Working Group (VCWG) is to make expressing and exchanging credentials that have been verified by a third party easier and more secure on the Web.
|
||||
|
|
@ -103,12 +104,4 @@ Verifiable Claims WG Test Suite.
|
|||
* [w3c/vctf](https://github.com/w3c/vctf) **Archived**
|
||||
> The Web Payments Interest Group's Verifiable Claims Task Force
|
||||
|
||||
## Sovrin
|
||||
|
||||
|
||||
|
||||
* [https://drive.google.com/drive/u/0/folders/1UxLLugRQKuV8Mdvv_X9Y6ty4szSi5ZNU?ogsrc=32](https://drive.google.com/drive/u/0/folders/1UxLLugRQKuV8Mdvv_X9Y6ty4szSi5ZNU?ogsrc=32)
|
||||
|
||||
* [Verifiable Credentials 101 for SSI - Tyler Ruff - Webinar 11](http://ssimeetup.org/verifiable-credentials-101-ssi-tyler-ruff-webinar-11/)
|
||||
|
||||
Tyler Ruff, product manager at Evernym, will be our next guest to walk us through Verifiable Credentials in the context of Self-Sovereign Identity. He will cover how they are created, issued and shared, as well as cover some common technical questions.
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user