mirror of
https://github.com/Decentralized-ID/decentralized-id.github.io.git
synced 2024-12-16 19:14:33 -05:00
add links
This commit is contained in:
Infominer
parent
761cc2d569
commit
2530a8b697
@ -10,6 +10,16 @@ tags: ["Blockpass","Ontology","Blockstack","Handshake","Democracy Earth"]
|
||||
last_modified_at: 2019-04-11
|
||||
---
|
||||
|
||||
## Blockchain
|
||||
|
||||
[**_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
|
||||
> Identity management systems (IDMSs) are widely used to provision user identities while managing authentication, authorization, and data sharing both within organizations as well as on the Internet more broadly. Traditional identity systems typically suffer from single points of failure, lack of interoperability, and privacy issues such as encouraging mass data collection and user tracking. Blockchain technology has the potential to support novel data ownership and governance models with built-in control and consent mechanisms, which may benefit both users and businesses by alleviating these concerns; as a result, blockchain-based IDMSs are beginning to proliferate. This work categorizes these systems into a taxonomy based on differences in architecture, governance models, and other salient features. We provide context for the taxonomy by describing related terms, emerging standards, and use cases, while highlighting relevant security and privacy considerations.
|
||||
[Identity Management with Blockchain: The Definitive Guide (2019)](https://tykn.tech/identity-management-blockchain/)
|
||||
> Learn everything about how Blockchain is used for Identity Management. This Definitive Guide to Identity Management with Blockchain has the answers.
|
||||
[Phil Windley (@windley)](https://twitter.com/windley/status/1071469217650638848)
|
||||
> If ledger isn’t used, then every issuer of a credential has to maintain infrastructure or contract service provider to respond to DID resolution & revocation requests. And, credential issuers would know when the credential was used, impacting privacy.
|
||||
|
||||
|
||||
## Blockpass
|
||||
|
||||
|
||||
@ -87,7 +87,9 @@ Phil [Zimmerman creates PGP](https://www.philzimmermann.com/EN/essays/WhyIWroteP
|
||||
> Shared repositories for #RebootingWebOfTrust Design Workshops - Web of Trust Info
|
||||
* [The Evolution of Internet Identity](https://www.slideshare.net/prabathsiriwardena/the-evolution-of-internet-identity)
|
||||
* [A Brief History of Digital Identity](https://medium.com/humanizing-the-singularity/a-brief-history-of-digital-identity-9d6a773bf9f5)
|
||||
> On April 10th, Mattereum hosted the third Internet of Agreements® (IoA) conference at the Google Campus in London, dedicated to the topic…
|
||||
> Many histories of digital identity start at the advent of the Internet, but the construction of name spaces is much older.
|
||||
>
|
||||
> Identity in our social systems is less concerned with encapsulating the human and more about the act of naming. As Silicon Valley’s Jared Dunn says in a moment of sad wisdom, “a name is just a sound that somebody makes when they need you.” The purpose of these names (or numbers) is to prove the uniqueness of a particular individual, to ensure accountability, and to establish some trust between individuals and institutions, to provide points of reference for the framework of laws and other social contracts that run our society.
|
||||
* [Identity Management OSS Map](http://web.archive.org/web/20110207095948/docs.safehaus.org/display/HAUS/Id+OSS+Map) - web.archive.org
|
||||
* [Vendor List](http://identityaccessmanagement.blogspot.com/2005/05/vendor-list.html) - identityaccessmanagement.blogspot.com
|
||||
> Updated: November 12 2006 I am trying to come up with the list of vendors and associated products in the Identity and Access Management ar...
|
||||
|
||||
@ -41,24 +41,8 @@ I will begin with a listing of standards bodies, organizations and open processe
|
||||
>
|
||||
> If you’re willing to put up with a lot of work for incremental improvements then step up and join a standard. Whether that is a (relatively) fast moving standard group like OASIS (www.oasis-open.org) or a slower but more international group like ISO you will learn. You’ll also benefit from working with experts. These experts donate their time and are more than happy to provide ideas, guidance, and leadership.
|
||||
|
||||
## XDI
|
||||
|
||||
* [**XDI**](xdi.html) **>>**
|
||||
|
||||
The XNS Public Trust Organization was founded in July 2000, shortly after International Planetwork Conference. -[xdi.org - History](http://xdi.org/?page_id=13)
|
||||
> to promote the concept of individuals owning their own digital identity and data based on a nascent technology being produced by two Technical Committees at OASIS: XRI (Extensible Resource Identifier) and XDI (Extensible Data Interchange).
|
||||
* [tutorial.xdi2.org](https://tutorial.xdi2.org)
|
||||
> XDI is a technology for modeling, storing, and manipulating data.
|
||||
>
|
||||
> It fits into a similar category of technologies as JSON, XML and RDF, but also has a number of properties that distinguishes it.
|
||||
>
|
||||
> XDI is a graph-based data model. This means that all data is expressed using nodes and arcs in a graph. At a minimum, a graph consists of a single node, called the common root node.
|
||||
|
||||
### OASIS XDI Tech Committee on Github
|
||||
* <a href="https://github.com/OASIS-XDI-Technical-Committee/xdi-spec-docbook">/OASIS-XDI-Technical-Committee/xdi-spec-docbook</a> - XDI Specifications (Docbook)
|
||||
* <a href="https://github.com/OASIS-XDI-Technical-Committee/xdi-developers-guide">/OASIS-XDI-Technical-Committee/xdi-developers-guide</a> - XDI Developer's Guide
|
||||
* <a href="https://github.com/OASIS-XDI-Technical-Committee/xdi-spec-openoffice">/OASIS-XDI-Technical-Committee/xdi-spec-openoffice</a> - XDI Specifications (Open Office)
|
||||
* <a href="https://github.com/OASIS-XDI-Technical-Committee/xdi-spec-dita">/OASIS-XDI-Technical-Committee/xdi-spec-dita</a> - XDI Specifications (DITA)
|
||||
[Who Are the Identerati? | ForgeRock](https://www.forgerock.com/blog/who-are-the-identerati)
|
||||
> You’re familiar with digital identity standards like OpenID Connect, OAuth, and User-Managed Access, fundamental elements of privacy and security on the internet. But have you ever wondered how they came to be? A lot of work on these protocols went on (and goes on) behind t...
|
||||
|
||||
|
||||
## W3C
|
||||
|
||||
@ -1,6 +1,13 @@
|
||||
---
|
||||
date: 2019-03-15
|
||||
title: XDI
|
||||
excerpt: >
|
||||
XDI is a technology for modeling, storing, and manipulating data.
|
||||
|
||||
It fits into a similar category of technologies as JSON, XML and RDF, but also has a number of properties that distinguishes it.
|
||||
|
||||
XDI is a graph-based data model. This means that all data is expressed using nodes and arcs in a graph. At a minimum, a graph consists of a single node, called the common root node.
|
||||
description: "XDI is a graph-based data model. This means that all data is expressed using nodes and arcs in a graph. At a minimum, a graph consists of a single node, called the common root node."
|
||||
layout: single
|
||||
permalink: /specs-standards/xdi/
|
||||
canonical_url: 'https://decentralized-id.com/specs-standards/xdi/'
|
||||
@ -19,28 +26,16 @@ last_modified_at: 2019-03-15
|
||||
>
|
||||
> XDI is a graph-based data model. This means that all data is expressed using nodes and arcs in a graph. At a minimum, a graph consists of a single node, called the common root node.
|
||||
|
||||
## Contents
|
||||
|
||||
* [Intro](#intro)
|
||||
* [RWoT Papers](#rwot-papers)
|
||||
* [Project Danube](#project-danube)
|
||||
* [Github Repos](#github-repos)
|
||||
* [OASIS XDI TC Technical Committee](#oasis-xdi-tc-technical-committee)
|
||||
* [Danube Github](#danube-github)
|
||||
* [XDI - Various Integrations](#xdi---various-integrations)
|
||||
* [XDI Configurations](#xdi-configurations)
|
||||
* [XDI Examples](#xdi-examples)
|
||||
* [XDI Plugins](#xdi-plugins)
|
||||
* [Aeternam](#aeternam)
|
||||
* [XDI Cloud](#xdi-cloud)
|
||||
* [XDI Server Deployed Via](#xdi-server-deployed-via)
|
||||
* [Services](#services)
|
||||
|
||||
## Intro
|
||||
|
||||
The XNS Public Trust Organization was founded in July 2000, shortly after International Planetwork Conference. -[xdi.org - History](http://xdi.org/?page_id=13)
|
||||
> to promote the concept of individuals owning their own digital identity and data based on a nascent technology being produced by two Technical Committees at OASIS: XRI (Extensible Resource Identifier) and XDI (Extensible Data Interchange).
|
||||
* [xdi.org](http://xdi.org/) is a non-profit public trust organization whose purpose is to provide public infrastructure for digital identity, security, and privacy using the open standard XDI semantic data interchange protocol developed by the OASIS XDI Technical Committee.
|
||||
* [tutorial.xdi2.org](https://tutorial.xdi2.org)
|
||||
> XDI is a technology for modeling, storing, and manipulating data.
|
||||
>
|
||||
> It fits into a similar category of technologies as JSON, XML and RDF, but also has a number of properties that distinguishes it.
|
||||
>
|
||||
> XDI is a graph-based data model. This means that all data is expressed using nodes and arcs in a graph. At a minimum, a graph consists of a single node, called the common root node.
|
||||
|
||||
|
||||
## RWoT Papers
|
||||
@ -76,8 +71,6 @@ The XNS Public Trust Organization was founded in July 2000, shortly after Intern
|
||||
> * A discovery function - enables looking up a registered DID in the blockchain
|
||||
> * A master key recovery function
|
||||
|
||||
|
||||
|
||||
## Project Danube
|
||||
|
||||
Markus Sabadello began working on Project Danube [around 2010](https://web.archive.org/web/20101221105543/http://projectdanube.org/)
|
||||
|
||||
@ -3,7 +3,7 @@ title: Verifiable Credentials
|
||||
permalink: /specs-standards/verifiable-credentials/
|
||||
tags: ["W3C", "CCG","VC-WG"]
|
||||
categories: ["Specs-Standards"]
|
||||
last_modified_at: 2020-01-09
|
||||
last_modified_at: 2020-01-10
|
||||
---
|
||||
|
||||
[](https://docs.google.com/presentation/d/1GMQy4rI093c_9zojwLRgp2r-fTscpDUSfX-wqwBk4j4/edit#slide=id.g3605fe1474_2_0)
|
||||
@ -37,24 +37,30 @@ Not all verifiable credentials are created the same. This post examines the cate
|
||||
> Verifiable Credential Authentication with OpenID Connect (VC-AuthN OIDC)
|
||||
* [Full-text Search for Verifiable Credential Metadata on Distributed Ledgers](https://arxiv.org/abs/1909.02895)
|
||||
* [Blockstack and Verifiable Credentials - Paris P2P Festival](https://p2p.paris/gen/attADzQJ92rNIv6B3-Blockstack_and_Verifiable_Credentials_-_Paris_P2P_Festival_.pdf)
|
||||
* [Open Badges are Verifable Credentials](https://nbviewer.jupyter.org/github/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/open-badges-are-verifiable-credentials.pdf)
|
||||
> The Open Badges Specifcation is a vocabulary and set of protocols that describes credentials. The vocabulary can describe any achievement in terms of a common set of attributes and is most often used for educational or occupational credentials. At present in version 2.0, Open Badges defnes two verifcation methods: HostedBadge (requiring resources hosted on HTTP in specifc locations) and SignedBadge (using a JSON Web Signature, which references hosted Issuer Profle and CryptographicKey information).
|
||||
>
|
||||
> The Blockcerts Open Badges Draft Extension introduced a verifcation method based on those used by Verifable Credentials for the specifc use case of blockchain-anchored credentials. This paper expands that work and proposes a new option that can reside alongside existing Open Badges verifcation methods.
|
||||
* [OPEN BADGES ON THE BLOCKCHAIN](https://draftin.com/documents/1138961?token=hQ5q0mCHizZum8-pkDFYUZr4YFYOWMN01BPT-5uX00hAaGxYOAlgAlhyenat76hjNpTCs-CMWPI38KWn_omp0Oc)
|
||||
> This document gives an overview of the status, interesting companies and people regarding Verifiable Open Badges on the Blockchain.
|
||||
* [Enabling Decentralised Identifiers and Verifiable Credentials for Constrained IoT Devices using OAuth-based Delegation](https://www.ndss-symposium.org/wp-content/uploads/diss2019_05_Lagutin_paper.pdf)
|
||||
> Abstract—Decentralised identifiers (DIDs) and verifiable credentials (VCs) are upcoming standards for self-sovereign privacypreserving identifiers and authorisation, respectively. This focus on privacy can help improve many services and open up new business models, but using DIDs and VCs directly on constrained IoT devices can be problematic due to the management and resource overhead. This paper presents an OAuth-based method to delegate the processing and access policy management to the Authorisation Server thus allowing also systems with constrained IoT devices to benefit from DIDs and VCs.
|
||||
* [W3C Verifiable Credentials - Kent Branch](https://www.bcs.org/events/2019/october/w3c-verifiable-credentials-kent-branch/) - [pdf](https://cdn.bcs.org/bcs-org-media/4653/kent-w3c-verifiable-credentials-031019.pdf)
|
||||
> The speaker will introduce the W3C Verifiable Credentials Data Model, which was published as a Proposed Recommendation in September 2019. Verifiable Credentials are the latest development in identity management and are fundamentally different from today's federated identity management systems such as SAML and OpenID Connect.
|
||||
>
|
||||
> David will describe the VC ecosystem and data model. He will then describe the prototype implementation which was built with colleagues from the University of Toulouse. They built a prototype system, which uses Fast Identity Online (FIDO) for user authentication, meaning that usernames and passwords are no longer needed. A pilot application was tested with a small sample of NHS patients and the speaker will present the results of this trial.
|
||||
* [Workday Credentials & WayTo™ By Workday](https://credentials.workday.com/docs/overview/)
|
||||
> An issuer is any entity that wishes to relinqiush and publicly attest to the veracity of data pertaining to a user. Public attestation comes in the form of a digital signature. When an issuer offers a credential to a user, Workday Credentials cryptographically signs the data in each credential with the issuer's private key before offering it to the user. The signing key's corresponding public key is written to a public ledger and is declared as belonging to the issuer, so that anyone can use that public key to verify the signature embedded in a user's digital credentials and establish trust in a credential's authenticity.
|
||||
* [IBM Verify Credentials](https://docs.info.verify-creds.com)
|
||||
> With IBM Verify Credentials and our alpha components, you can begin your journey of exploring the benefits of decentralized identity. We have provided an interactive experience centered around the challenge of proving your identity while opening a financial account. Additionally, we will walk you through the development of your first end-to-end decentralized identity solution.
|
||||
* [Verifiable credentials and libp2p](https://discuss.libp2p.io/t/verifiable-credentials-and-libp2p/206)
|
||||
> Hi - we’re looking into libp2p as a network stack for our application and exploring how we could integrate verifiable credentials (https://w3c.github.io/vc-data-model/ 2) infrastructure. A basic use case is that of a node being challenged to provide some specific credential to join the network. The bootstrap node handling the incoming connection should verify the credential with the issuer and complete the connection/bootstrap or terminate it.
|
||||
* [Open Badges are Verifable Credentials](https://nbviewer.jupyter.org/github/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/open-badges-are-verifiable-credentials.pdf)
|
||||
> The Open Badges Specifcation is a vocabulary and set of protocols that describes credentials. The vocabulary can describe any achievement in terms of a common set of attributes and is most often used for educational or occupational credentials. At present in version 2.0, Open Badges defnes two verifcation methods: HostedBadge (requiring resources hosted on HTTP in specifc locations) and SignedBadge (using a JSON Web Signature, which references hosted Issuer Profle and CryptographicKey information).
|
||||
>
|
||||
> The Blockcerts Open Badges Draft Extension introduced a verifcation method based on those used by Verifable Credentials for the specifc use case of blockchain-anchored credentials. This paper expands that work and proposes a new option that can reside alongside existing Open Badges verifcation methods.
|
||||
* [OPEN BADGES ON THE BLOCKCHAIN](https://draftin.com/documents/1138961?token=hQ5q0mCHizZum8-pkDFYUZr4YFYOWMN01BPT-5uX00hAaGxYOAlgAlhyenat76hjNpTCs-CMWPI38KWn_omp0Oc)
|
||||
> This document gives an overview of the status, interesting companies and people regarding Verifiable Open Badges on the Blockchain.
|
||||
* [Addition of Proof Request/Response to a formal Verifiable Credentials specification](https://github.com/WebOfTrustInfo/rwot9-prague/blob/master/topics-and-advance-readings/verifiable-credentials-proof-request.md)
|
||||
> The W3C Verifiable Credentials (hereafter VC) specification does not currently outline how credential data should be requested by a Verifier. This document outlines the approach taken at Workday and proposes it as an addition or companion to the VC spec.
|
||||
>
|
||||
> At RWoT we wish to present our approach in order to get community feedback and consensus. Workday recently announced our credentialing platform and will shortly begin to issue credentials within our market verticals. We fully intend to support the community standards around credentialing and therefore wish to drive consensus in the community on a simple, standard approach for requesting and sharing VCs between a holder and verifier.
|
||||
* [Workday Credentials & WayTo™ By Workday](https://credentials.workday.com/docs/overview/)
|
||||
> An issuer is any entity that wishes to relinqiush and publicly attest to the veracity of data pertaining to a user. Public attestation comes in the form of a digital signature. When an issuer offers a credential to a user, Workday Credentials cryptographically signs the data in each credential with the issuer's private key before offering it to the user. The signing key's corresponding public key is written to a public ledger and is declared as belonging to the issuer, so that anyone can use that public key to verify the signature embedded in a user's digital credentials and establish trust in a credential's authenticity.
|
||||
|
||||
|
||||
|
||||
## Code
|
||||
|
||||
@ -62,6 +68,10 @@ Not all verifiable credentials are created the same. This post examines the cate
|
||||
> This Javascript Library provides functionality around Verifiable Credentials (VC), a W3C standard. Enables Validators to issue, Credential Wallets to verify, filter and Requesters to verify credentials.
|
||||
* [EDCI-Data-Model](https://github.com/european-commission-europass/EDCI-Data-Model)
|
||||
> The European Commission is developing the Europass Digital Credentials Infrastructure (EDCI) – a set of tools, services and software to support the issuance of authentic, tamper-proof digital credentials (such as qualifications and other learning achievements) across Europe. The EDCI is being developed as part of ongoing work to implement the new Europass Framework for supporting transparency of skills and qualifications in Europe.
|
||||
* [gautamdhameja/substrate-verifiable-credentials](https://github.com/gautamdhameja/substrate-verifiable-credentials)
|
||||
> A minimal Substrate runtime for verifiable credentials' issuance and verification.
|
||||
* [bcgov/TheOrgBook](https://github.com/bcgov/TheOrgBook)
|
||||
> A public repository of verifiable claims about organizations. A key component of the Verifiable Organization Network.
|
||||
|
||||
## CCG
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user