mirror of
https://github.com/Decentralized-ID/decentralized-id.github.io.git
synced 2025-01-11 23:29:28 -05:00
identosphere updates
This commit is contained in:
⧉ infominer
parent
9d5b9e4211
commit
c4aa32d5dd
@ -1,5 +1,4 @@
|
||||
---
|
||||
date: 2020-11-26
|
||||
title: (DID) Authentication Working Group - DIF
|
||||
description: design, recommend, and implement authentication and authorization protocols that rely upon open standards and cryptographic protocols using DIDs and DID Documents.
|
||||
excerpt: >
|
||||
@ -9,19 +8,17 @@ canonical_url: https://decentralized-id.com/organizations/decentralized-identity
|
||||
redirect_from:
|
||||
- organizations/identity-foundation/wg/secure-data-storage/
|
||||
categories: ["Open Source Projects"]
|
||||
tags: ["DIDAuth WG","DIDAuth","DIF","DID","SOIP","Aries","Verifiable Credentials","W3C","DIDComm"]
|
||||
tags: ["DIDAuth WG","DIDAuth","DIF","DID","SOIP","Aries","Verifiable Credentials","W3C","DIDComm","BCGov"]
|
||||
header:
|
||||
image: /images/didauth-wg-head.webp
|
||||
teaser: /images/didauth-wg-teaser.webp
|
||||
last_modified_at: 2020-11-26
|
||||
last_modified_at: 2023-06-11
|
||||
---
|
||||
|
||||
[Webpage](https://identity.foundation/working-groups/authentication.html) - [GitHub](https://github.com/decentralized-identity/authentication-wg)
|
||||
|
||||
> Join this group to contribute to standards and technology that designs and implements authentication protocols that rely upon open standards and cryptographic protocols, including DIDs and DID Documents. This group develops specifications, protocols, and formats for data structures used for authentication.
|
||||
|
||||
* [Mailing list](https://dif.groups.io/g/didauth-wg) - The purpose of this working group is to design, recommend, and implement authentication and authorization protocols that rely upon open standards and cryptographic protocols using DIDs and DID Documents.
|
||||
* [DIDAuth WG Charter](https://github.com/decentralized-identity/org/blob/master/Org%20documents/WG%20documents/DIF_DIDAuth_WG_charter_v1.pdf)
|
||||
* [DID Authentication Working Group](https://identity.foundation/working-groups/authentication.html) - [GitHub](https://github.com/decentralized-identity/authentication-wg)
|
||||
> Join this group to contribute to standards and technology that designs and implements authentication protocols that rely upon open standards and cryptographic protocols, including DIDs and DID Documents. This group develops specifications, protocols, and formats for data structures used for authentication.
|
||||
* [Mailing list](https://dif.groups.io/g/didauth-wg)
|
||||
* [Charter](https://github.com/decentralized-identity/org/blob/master/Org%20documents/WG%20documents/DIF_DIDAuth_WG_charter_v1.pdf)
|
||||
> The purpose of this working group is to design, recommend and implement authentication and authorization protocols that rely upon open standards and cryptographic protocols using DIDs and DID Documents. Recommendations and development of specifications, protocols, and formats for data structures used for authentication and authorization. The Working Group’s areas of activity may include, but are not limited to, the following:
|
||||
> - Define the formats and protocols necessary for authentication and authorization using DIDs, DID Documents, and verifiable credentials which we intend to recognize as formally DIF-approved.
|
||||
> - Implement DIF-approved DID Auth proposals.
|
||||
@ -55,9 +52,16 @@ A shared effort with the HL Aries project to create a standardized means of auth
|
||||
|
||||
|
||||
|
||||
* [DID Auth and the Little I-am-Me](https://medium.com/@markus.sabadello/did-auth-and-the-little-i-am-me-ec14d757ff09)
|
||||
* [Introduction to DID Auth](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/did-auth.md) [[**ϟ**](http://ssimeetup.org/introduction-did-auth-markus-sabadello-webinar-10/)]
|
||||
<iframe src="//www.slideshare.net/slideshow/embed_code/key/CtcPSLkrTg5z2c" width="595" height="485" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;" allowfullscreen> </iframe>
|
||||
|
||||
<a href="http://ssimeetup.org/introduction-did-auth-markus-sabadello-webinar-10/"><img src="https://i.imgur.com/YNlk8RY.png"/></a>\
|
||||
http://ssimeetup.org/introduction-did-auth-markus-sabadello-webinar-10
|
||||
* [Introduction to DID Auth for SSI with Markus Sabadello](https://www.slideshare.net/SSIMeetup/introduction-to-did-auth-with-markus-sabadello) 2018-07-04 [SSI-Meetup](https://ssimeetup.org/introduction-did-auth-markus-sabadello-webinar-10/)
|
||||
> Markus Sabadello, CEO of Danube Tech, will talk about DID Auth, an emerging building block in the SSI ecosystem. Although the technical details of DID Auth are not well-defined at this point, its general concept is clear: With self-sovereign identity infrastructure, the most trivial and straightforward functionality for identity owners should be the ability to authenticate, i.e. to prove control of a DID in some relationship or during a transaction. This could take place using a number of different data formats, protocols, and flows. DID Auth includes the ability to authenticate to web sites and applications, and to establish mutually authenticated communication channels. In this webinar, we will discuss the current state of the DID Auth concept, and how it relates to other efforts such as Verifiable Credentials and agent protocols.
|
||||
* [DID Auth and the Little I-am-Me](https://medium.com/@markus.sabadello/did-auth-and-the-little-i-am-me-ec14d757ff09) 2018-09-04
|
||||
> We recently published a report on “DID Auth” ([PDF](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/raw/master/final-documents/did-auth.pdf), [MD](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/did-auth.md)), which summarizes ideas and possible architectures that allow you to prove that you control a certain Decentralized Identifier (DID). This report originated at the sixth Rebooting-the-Web-of-Trust workshop and is the result of a collaborative effort by several authors and contributors. There is also a webinar.
|
||||
* [Introduction to DID Auth](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/did-auth.md)
|
||||
> The term DID Auth has been used in different ways and is currently not well-defined. We define DID Auth as a ceremony where an identity owner, with the help of various components such as web browsers, mobile devices, and other agents, proves to a relying party that they are in control of a DID. This means demonstrating control of the DID using the mechanism specified in the DID Document's "authentication" object. This could take place using a number of different data formats, protocols, and flows. DID Auth includes the ability to establish mutually authenticated communication channels and to authenticate to web sites and applications. Authorization, Verifiable Credentials, and Capabilities are built on top of DID Auth and are out of scope for this document. This paper gives on overview of the scope of DID Auth, supported protocols and flows, and the use of components of the DID Documents that are relevant to authentication, as well as formats for challenges and responses.
|
||||
|
||||
### BCGov - GitHub
|
||||
* [DID Auth HTTP proxy](https://github.com/bcgov/http-did-auth-proxy) 2022-01-19
|
||||
> This is a DID Auth HTTP proxy that uses [HTTP Signatures](https://www.ietf.org/id/draft-cavage-http-signatures-09.txt) based on [Decentralized Identifiers](https://w3c-ccg.github.io/did-spec/) for authenticated HTTP requests.
|
||||
* [DID Auth browser extension](https://github.com/bcgov/did-auth-extension) 2021-12-29
|
||||
|
||||
@ -10,17 +10,15 @@ redirect_from:
|
||||
- organizations/identity-foundation/wg/identifiers-and-discovery/
|
||||
canonical_url: https://decentralized-id.com/organizations/identity-foundation/wg/identifiers-and-discovery/
|
||||
categories: ["Open Source Projects"]
|
||||
tags: ["Identifiers and Discovery WG","DID","DIF","Universal Resolver","Universal Registrar","KERI","Verifiable Credentials","JSON-LD","Ethereum","ION","BTCR","DID:PEER","ERC725","Linked Data"]
|
||||
tags: ["Identifiers and Discovery WG","DID","DIF","Universal Resolver","Universal Registrar","Verifiable Credentials","JSON-LD","Ethereum","ION","BTCR","DID:PEER","ERC725","Linked Data"]
|
||||
header:
|
||||
image: /images/identifiers-discovery-head.webp
|
||||
teaser: /images/identifiers-discovery-teaser.webp
|
||||
last_modified_at: 2020-11-26
|
||||
last_modified_at: 2023-06-11
|
||||
---
|
||||
|
||||
[Webpage](https://identity.foundation/working-groups/identifiers-discovery.html) - [GitHub](https://github.com/decentralized-identity/identifiers-discovery) - [Slack](https://difdn.slack.com/messages/C4WED8JSH)
|
||||
|
||||
> Members of the Working Group are engaged in development of protocols and systems that enable creation, resolution, and discovery of decentralized identifiers and names across underlying decentralized systems, like blockchains and distributed ledgers.
|
||||
|
||||
* [Identifiers and Discovery Working Group](https://identity.foundation/working-groups/identifiers-discovery.html) - [GitHub](https://github.com/decentralized-identity/identifiers-discovery)
|
||||
> Members of the Working Group are engaged in development of protocols and systems that enable creation, resolution, and discovery of decentralized identifiers and names across underlying decentralized systems, like blockchains and distributed ledgers.
|
||||
* [I&D WG Charter](https://github.com/decentralized-identity/org/blob/master/Org%20documents/WG%20documents/DIF_ID_WG_charter_v1.pdf)
|
||||
- Specifications, implementations, test suites, etc. related to creation, derivation, resolution, management, use of all forms of decentralized identifiers (i.e. including, but not limited to W3C DIDs)
|
||||
- Relationship between identifier systems (e.g. DID and domain names)
|
||||
@ -49,6 +47,26 @@ Spec and implementation of a driver-based framework that enables resolution of D
|
||||
* [decentralized-identity/universal-resolver-java](https://github.com/decentralized-identity/universal-resolver-java)
|
||||
* [decentralized-identity/universal-resolver-python](https://github.com/decentralized-identity/universal-resolver-python)
|
||||
|
||||
#### Related
|
||||
|
||||
* [Universal Resolver - resolve practically any DID](https://blog.identity.foundation/uni-resolver/) 2022-09-01 Identity Foundation
|
||||
> The Universal Resolver can now resolve 45 DID methods, and more are being added regularly. Visit [https://dev.uniresolver.io/](https://dev.uniresolver.io/) to see the full list of supported methods, and visit [this github page](https://github.com/decentralized-identity/universal-resolver/blob/main/docs/driver-development.md) to contribute a driver for a DID method.
|
||||
* [jolocom/ddoresolver-rs](https://github.com/jolocom/ddoresolver-rs) 2022-05-13 Jolocom
|
||||
> Universal, multy-method, feature gated DID Document resolver
|
||||
* [Mission Accomplished: Universal Resolver Calls coming to an end](https://blog.identity.foundation/universal-resolver-calls-wrapup/) 2021-11-04 Identity Foundation
|
||||
> Considering that the group has accomplished these goals, there is currently no more need for dedicated calls. Work on the Universal Resolver work item will continue on Github (under the [Universal Resolver](https://github.com/decentralized-identity/universal-resolver) and [Identifiers &Discovery](https://github.com/decentralized-identity/identifiers-discovery/) and on DIF Slack in the Identifiers & Discovery Working Group channel, #wg-id.
|
||||
* [DID Resolution: Given a DID how do I retrieve its document? – Markus Sabadello](https://www.slideshare.net/SSIMeetup/did-resolution-given-a-did-how-do-i-retrieve-its-document-markus-sabadello) 2018-11-27 [SSI-Meetup](http://ssimeetup.org/did-resolution-given-did-how-do-retrieve-document-markus-sabadello-webinar-13/)
|
||||
> Markus Sabadello, CEO of Danube Tech, will talk about DID Resolution and how to retrieve a DID document. As we know, Decentralized Identifiers (DIDs) are a key component in SSI architecture. They are used as building blocks for verifiable credentials, wallets, agents, and data exchange protocols. To make all this work, we need to be able to “resolve” DIDs to their associated DID Documents. This process fulfills a similar purpose as DNS does in the classic web. And while DID Resolution is not a very complicated topic, it is still important to understand how it works and how it relates to other topics. In this webinar, we will give a general introduction to DID Resolution, discuss a few in-depth topics, and also demo concrete tools that are available today.
|
||||
>
|
||||
> Most DID Resolution implementations envision an architecture where a common base component invokes a set of “drivers” or “plugins” or “modules” to implement method-specific functionality, e.g. see the DIF Universal Resolver, Digital Bazaar’s did-client, or the uPort JavaScript DID Resolver. We envision such “DID Resolver” tools to become as central to SSI infrastructure as DNS is for the web today.
|
||||
* [A Universal Resolver for self-sovereign identifiers](https://medium.com/decentralized-identity/a-universal-resolver-for-self-sovereign-identifiers-48e6b4a5cc3c)
|
||||
2017-11-01 (Markus Sabadello)
|
||||
> This is a first step in fulfilling DIF’s mission to help individuals and organizations to control their digital identity, without being dependent on any intermediary party.
|
||||
>
|
||||
> This tool fulfills a similar purpose as Bind does in the DNS system: resolution of identifiers. However, instead of working with domain names, we work with self-sovereign identifiers that can be created and registered directly by the entities they refer to.
|
||||
|
||||
<iframe src="//www.slideshare.net/slideshow/embed_code/key/wvgU7Gl8ORUGLI" width="595" height="485" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;" allowfullscreen> </iframe>
|
||||
|
||||
#### Resolver Drivers
|
||||
|
||||
* [decentralized-identity/uni-resolver-driver-did-erc725](https://github.com/decentralized-identity/uni-resolver-driver-did-erc725) - A Universal Resolver driver for did:erc725 identifiers.
|
||||
@ -81,6 +99,8 @@ Spec and implementation of a driver-based framework that enables creation/update
|
||||
### .well-known DID configuration
|
||||
Spec, docs, and implementations for discovering DIDs from .well-known HTTP(S) URIs.
|
||||
|
||||
* [Link your domain to your Decentralized Identifier (DID) (preview)](https://docs.microsoft.com/en-us/azure/active-directory/verifiable-credentials/how-to-dnsbind)
|
||||
> We make a link between a domain and a DID by implementing an open standard written by the Decentralized Identity Foundation called [Well-Known DID configuration](https://identity.foundation/.well-known/resources/did-configuration/). The verifiable credentials service in Azure Active Directory (Azure AD) helps your organization make the link between the DID and domain by including the domain information that you provided in your DID, and generating the well-known config file:
|
||||
* [decentralized-identity/.well-known/](https://github.com/decentralized-identity/.well-known/)
|
||||
* [Repo Webpage](https://identity.foundation/.well-known/)
|
||||
> Making it possible to connect existing systems and Decentralized Identifiers (DIDs) is an important undertaking that can aid in bootstrapping adoption and usefulness of DIDs. One such form of connection is the ability of a DID controller to prove they are the same entity that controls an origin.
|
||||
@ -92,17 +112,6 @@ Spec, docs, and implementations for discovering DIDs from .well-known HTTP(S) UR
|
||||
> The DID Configuration resource provides proof of a bi-directional relationship between the controller of an Internet domain and a DID via cryptographically verifiable signatures that are linked to a DID's key material. This document describes the data format of the resource and the resource location at which Internet domain controllers can publish their DID Configuration.
|
||||
>
|
||||
> Due to the location of the DID Configuration resource, discovery of associated Decentralized Identifiers against a domain is trivial. However, the inverse (i.e given a DID-URI discover the associated domains) is deemed out of scope.
|
||||
|
||||
|
||||
### KERI - Key Event Receipt InfrastructureSpec and implementation of an identifier and key
|
||||
rotation technology, where your primary root of trust is entropy, not
|
||||
any particular ledger.
|
||||
|
||||
* [decentralized-identity/keri](https://github.com/decentralized-identity/keri) - Key Event Receipt Infrastructure - the spec and implementation of the KERI protocol
|
||||
* [decentralized-identity/kerigo](https://github.com/decentralized-identity/kerigo) - Go implementation of KERI (Key Event Receipt Infrastructure)
|
||||
* [decentralized-identity/kerijs](https://github.com/decentralized-identity/kerijs) - JavaScript (nodes) Implementation of the KERI core library.
|
||||
* [decentralized-identity/keriox](https://github.com/decentralized-identity/keriox) - Rust Implementation of the KERI Core Library
|
||||
* [decentralized-identity/keripy](https://github.com/decentralized-identity/keripy) - Python Implementation of the KERI Core Libraries
|
||||
|
||||
### Peer DID Method Specification
|
||||
|
||||
@ -133,4 +142,4 @@ Extension parameters, properties, and values for the DID spec registries.
|
||||
* [decentralized-identity/fuzzy-encryption](https://github.com/decentralized-identity/fuzzy-encryption) - A variant of a Fuzzy Vault cryptographic scheme designed for encrypting data with better human recovery features.
|
||||
* [decentralized-identity/jsonld-common-java](https://github.com/decentralized-identity/jsonld-common-java) - Shared JSON-LD Java library.
|
||||
* [jsonld-document-loader](https://github.com/decentralized-identity/jsonld-document-loader)
|
||||
> Document loaders enable decentralized security, interoperability and extensibility while gaurding against vendor lock in.
|
||||
> Document loaders enable decentralized security, interoperability and extensibility while gaurding against vendor lock in.
|
||||
@ -13,53 +13,26 @@ tags: ["Storage and Compute WG","DIF","Secure Data Storage","Data Hubs","W3C","E
|
||||
header:
|
||||
image: /images/secure-data-storage-head.webp
|
||||
teaser: /images/secure-data-storage-teaser.webp
|
||||
last_modified_at: 2020-11-26
|
||||
last_modified_at: 2023-06-11
|
||||
---
|
||||
|
||||
[Webpage](https://identity.foundation/working-groups/storage-compute.html) - [Wiki](https://dif.groups.io/g/sds-wg/wiki) - [GitHub](https://github.com/decentralized-identity/confidential-storage/)
|
||||
|
||||
> Secure, encrypted, privacy-preserving storage and computation of data is a critical component of decentralized identity systems. As with identifiers and names must be self-sovereign to the owning entity, a user's identity data must remain private, only accessible to the entities they allow. DIF members are actively developing specs and reference implementations for provider-agnostic, run-anywhere solutions that provides these features.
|
||||
|
||||
- [Mailing List](https://dif.groups.io/g/sds-wg/wiki/home)
|
||||
- [Working Group Wiki](https://lists.identity.foundation/g/sds-wg/wiki)
|
||||
> Create one or more specifications to establish a foundational layer for secure data storage (including personal data), specifically data models for storage and transport, syntax, data at rest protection, CRUD HTTP API, access control, synchronization, and a minimum viable HTTP-based interface compatible with W3C DIDs/VCs.
|
||||
- [Secure Data Storage Working Group Charter](https://drive.google.com/file/d/1vf2CsD9QZstzrd6CJ4WFVHw0WKwwNLHf/view)
|
||||
> - Create one or more specifications to establish a foundational layer for secure data storage (including personal data), specifically data models for storage and transport, syntax, data at rest protection, CRUD API, access control, synchronization, and at least a minimum viable HTTP-based interface compatible with W3C DIDs/VCs.
|
||||
> - The [Identity Hubs](https://github.com/decentralized-identity/identity-hub/blob/master/explainer.md) and [Encrypted Data Vaults](https://digitalbazaar.github.io/encrypted-data-vaults/) documents will be used as a use case, requirements, and technical input for the collaborative effort.
|
||||
|
||||
* [Secure Data Storage and Compute Working Group](https://identity.foundation/working-groups/secure-data-storage.html)
|
||||
> Create one or more specifications to establish a foundational layer for secure data storage (including personal data), specifically data models for storage and transport, syntax, data at rest protection, CRUD API, access control, synchronization, and at least a minimum viable HTTP-based interface compatible with W3C DIDs/VCs.
|
||||
- [Wiki](https://dif.groups.io/g/sds-wg/wiki)
|
||||
- [GitHub](https://github.com/decentralized-identity?q=wg-sds)
|
||||
- [Mailing List](https://dif.groups.io/g/sds-wg/wiki/home)
|
||||
- [Charter](https://github.com/decentralized-identity/org/blob/master/Org%20documents/WG%20documents/DIF_SDS_WG_charter_v1.pdf)
|
||||
|
||||
## Specs & Projects
|
||||
### Decentralized Web Node
|
||||
* [Decentralized Web Node (DWN)](https://identity.foundation/decentralized-web-node/spec) - [GitHub](https://github.com/decentralized-identity/decentralized-web-node)
|
||||
> Formerly known as the Identity Hub, this initiative is to develop a data storage and message relay mechanism that entities can use to locate public or private permissioned data related to a given Decentralized Identifier (DID).
|
||||
|
||||
The active work items that are underway in the DIF Storage and Compute Working Group
|
||||
|
||||
### Confidential Storage
|
||||
|
||||
- [decentralized-identity/confidential-storage/](https://github.com/decentralized-identity/confidential-storage/)
|
||||
- [Latest Editors Draft](https://identity.foundation/confidential-storage/)
|
||||
> We store a significant amount of sensitive data online, such as personally identifying information (PII), trade secrets, family pictures, and customer information. The data that we store is often not protected in an appropriate manner.
|
||||
>
|
||||
### Encrypted Data Vaults
|
||||
* [Encrypted Data Vaults](https://identity.foundation/edv-spec/) - [GitHub](https://github.com/decentralized-identity/edv-spec/)
|
||||
> This specification describes a privacy-respecting mechanism for storing, indexing, and retrieving encrypted data at a storage provider. It is often useful when an individual or organization wants to protect data in a way that the storage provider cannot view, analyze, aggregate, or resell the data. This approach also ensures that application data is portable and protected from storage provider data breaches.
|
||||
* [DIF SDS/CS WG: CS Refactoring Proposal 0.2](https://hyperonomy.com/2021/03/28/cs-refactoring-proposal/) Hyperonomy
|
||||
> 1. Latest Version of the Proposal (0.2 – March 24, 2021)
|
||||
> 2. Agent-Hub-EDV Architecture Reference Model (AHE-ARM) 0.1
|
||||
> 3. Transcription of Selected Parts of the DIF SDS/CS March 11, 2021 Zoom Call
|
||||
> 4. OSI Stack Proposal for Confidential Storage Specification
|
||||
>
|
||||
> Based on the March 11 Zoom discussion where we worked hard to discern the differences between Agents, Hubs, and EDVs (and I believe were largely successful IMO), I’ve like to propose to the SDS/CS WG that we refactor the current Confidential Storage specification into 3 separable parts/specifications. I also present a high-level roadmap (simple ordering) for how the WG might proceed if this refactoring is accepted (or at least, if the first part/first new specification is accepted).
|
||||
|
||||
### Identity Hubs (Archived)
|
||||
## Background
|
||||
|
||||
Encrypted personal datastore for identity interactions and decentralized apps.
|
||||
|
||||
* [Identity Hubs](https://github.com/decentralized-identity/identity-hub/)
|
||||
* [Explainer](https://github.com/decentralized-identity/identity-hub/blob/master/explainer.md)
|
||||
> Hubs let you securely store and share data. A Hub is a datastore containing semantic data objects at well-known locations. Each object in a Hub is signed by an identity and accessible via a globally recognized API format that explicitly maps to semantic data objects. Hubs are addressable via unique identifiers maintained in a global namespace.
|
||||
* [System Diagram](https://raw.githubusercontent.com/decentralized-identity/hubs/master/diagrams/full-system.png)
|
||||
|
||||
[](https://raw.githubusercontent.com/decentralized-identity/hubs/master/diagrams/full-system.png)
|
||||
|
||||
### Encrypted Data Vaults (Archived)
|
||||
|
||||
* [Encrypted Data Vaults](https://digitalbazaar.github.io/encrypted-data-vaults/)
|
||||
> We store a significant amount of sensitive data online, such as personally identifying information (PII), trade secrets, family pictures, and customer information. The data that we store is often not protected in an appropriate manner.
|
||||
>
|
||||
> Legislation, such as the General Data Protection Regulation (GDPR), incentivizes service providers to better preserve individuals' privacy, primarily through making the providers liable in the event of a data breach. This liability pressure has revealed a technological gap, whereby providers are often not equipped with technology that can suitably protect their customers. Encrypted Data Vaults fill this gap and provide a variety of other benefits.
|
||||
* [Selected Parts of the DIF SDS/CS Hub and EDV Discussion featuring Daniel Buchner’s Description of a Hub](https://hyperonomy.com/2021/03/24/transcription-of-selected-parts-of-the-dif-sds-cs-march-11-2021-zoom-call-hub-and-edv-discussion-featuring-daniel-buchners-description-of-a-hub/) Michael Herman 2021-03-24
|
||||
> This is a transcription of selected parts of the EDV-Hub conversation during the DIF SDS/CS Thursday weekly Zoom call on March 11, 2021. This is the call where Daniel Buchner described (verbally) several aspects about what is and what is not a Hub. 2021-03-24
|
||||
|
||||
@ -1,25 +0,0 @@
|
||||
---
|
||||
published: false
|
||||
---
|
||||
# Sidetree
|
||||
* [Decoding the Sidetree Protocol](https://academy.affinidi.com/decoding-the-sidetree-protocol-18d8bfa39257) Affinidi
|
||||
> Sidetree protocols are layer 2 protocols that anchor to the underlying decentralized ledger system. That said, it is ledger agnostic and its primary role is to anchor batches of signed JSON operations to the network.
|
||||
* [Sidetree Protocol reaches V1](https://blog.identity.foundation/sidetree-protocol-reaches-v1/) DIF
|
||||
> This week, the DIF Steering Committee officially approved the first major release of the Sidetree Protocol specification, "v1" so to speak. This protocol has already been implemented, and four of its implementers have been collaborating intensively for over a year on expanding and extending this specification together.
|
||||
* [@csuwildcat](https://twitter.com/csuwildcat) shares
|
||||
> As of Friday, we believe v1 of ION is functionally code complete, and the Sidetree Working Group at DIF (@DecentralizedID) should have a v1 spec candidate ready for the underlying protocol by Jan 21st. Public v1 launch of the ION network on Bitcoin mainnet is just weeks away.
|
||||
|
||||
* [ION – We Have Liftoff!](https://techcommunity.microsoft.com/t5/identity-standards-blog/ion-we-have-liftoff/ba-p/1441555)
|
||||
> We are excited to share that v1 of [ION](https://identity.foundation/ion/) is complete and has been launched on Bitcoin mainnet. We have deployed an ION node to our production infrastructure and are working together with other companies and organizations to do so as well. ION does not rely on centralized entities, trusted validators, or special protocol tokens – ION answers to no one but you, the community. Because ION is an open, permissionless system, anyone can run an ION node, in fact the more nodes in operation, the stronger the network becomes. Development of ION, and the Sidetree standard ION is based on, takes place in the [Decentralized Identity Foundation](https://identity.foundation/) (DIF). Read on to learn how you can integrate ION, DIDs, and Verifiable Credentials in your applications and services.
|
||||
|
||||
|
||||
### Well Known
|
||||
* [Link your domain to your Decentralized Identifier (DID) (preview)](https://docs.microsoft.com/en-us/azure/active-directory/verifiable-credentials/how-to-dnsbind)
|
||||
> We make a link between a domain and a DID by implementing an open standard written by the Decentralized Identity Foundation called [Well-Known DID configuration](https://identity.foundation/.well-known/resources/did-configuration/). The verifiable credentials service in Azure Active Directory (Azure AD) helps your organization make the link between the DID and domain by including the domain information that you provided in your DID, and generating the well-known config file:
|
||||
|
||||
|
||||
## Hub
|
||||
* [Selected Parts of the DIF SDS/CS Hub and EDV Discussion featuring Daniel Buchner’s Description of a Hub](https://hyperonomy.com/2021/03/24/transcription-of-selected-parts-of-the-dif-sds-cs-march-11-2021-zoom-call-hub-and-edv-discussion-featuring-daniel-buchners-description-of-a-hub/) Michael Herman 2021-03-24
|
||||
> This is a [transcription of selected parts of the EDV-Hub conversation](https://hyperonomy.com/2021/03/24/transcription-of-selected-parts-of-the-dif-sds-cs-march-11-2021-zoom-call-hub-and-edv-discussion-featuring-daniel-buchners-description-of-a-hub/) during the DIF SDS/CS Thursday weekly Zoom call on March 11, 2021. This is the call where Daniel Buchner described (verbally) several aspects about what is and what is not a Hub. 2021-03-24
|
||||
* [PROPOSAL: Confidential Storage Specification Refactoring 0.2 – March 24, 2021](https://lists.w3.org/Archives/Public/public-credentials/2021Mar/0245.html)
|
||||
> Based on the March 11 Zoom discussion where we worked hard to discern the differences between Agents, Hubs, and EDVs (and I believe were largely successful IMO), I’ve like to propose to the SDS/CS WG that we refactor the current Confidential Storage specification into 3 separable parts/specifications.
|
||||
@ -1,20 +0,0 @@
|
||||
---
|
||||
published: false
|
||||
---
|
||||
# Universal Resolver
|
||||
|
||||
* [Universal Resolver - resolve practically any DID](https://blog.identity.foundation/uni-resolver/) Identity Foundation
|
||||
> The Universal Resolver can now resolve 45 DID methods, and more are being added regularly. Visit [https://dev.uniresolver.io/](https://dev.uniresolver.io/) to see the full list of supported methods, and visit [this github page](https://github.com/decentralized-identity/universal-resolver/blob/main/docs/driver-development.md) to contribute a driver for a DID method.
|
||||
- [DID DIF Universal Resolver](https://dev.uniresolver.io/)
|
||||
* [Universal Resolver Driver Policy Discussion](https://iiw.idcommons.net/21P/_Universal_Resolver_Driver_Policy_Discussion) by Bernhard Fuchs, Markus Sabadello
|
||||
> The project has some guidelines for contributing new DID method drivers:[https://github.com/decentralized-identity/universal-resolver/blob/master/docs/driver-development.md](https://github.com/decentralized-identity/universal-resolver/blob/master/docs/driver-development.md)
|
||||
* [A Universal Resolver for self-sovereign identifiers](https://medium.com/decentralized-identity/a-universal-resolver-for-self-sovereign-identifiers-48e6b4a5cc3c)
|
||||
* [On any blockchain or other decentralized system](https://medium.com/decentralized-identity/a-universal-resolver-for-self-sovereign-identifiers-48e6b4a5cc3c) (Markus Sabadello)
|
||||
> This is a first step in fulfilling DIF’s mission to help individuals and organizations to control their digital identity, without being dependent on any intermediary party.
|
||||
>
|
||||
> This tool fulfills a similar purpose as Bind does in the DNS system: resolution of identifiers. However, instead of working with domain names, we work with self-sovereign identifiers that can be created and registered directly by the entities they refer to.
|
||||
* [Mission Accomplished: Universal Resolver Calls coming to an end](https://blog.identity.foundation/universal-resolver-calls-wrapup/) Identity Foundation
|
||||
> Considering that the group has accomplished these goals, there is currently no more need for dedicated calls. Work on the Universal Resolver work item will continue on Github (under the [Universal Resolver](https://github.com/decentralized-identity/universal-resolver) and [Identifiers &Discovery](https://github.com/decentralized-identity/identifiers-discovery/) and on DIF Slack in the Identifiers & Discovery Working Group channel, #wg-id.
|
||||
|
||||
- [jolocom/ddoresolver-rs](https://github.com/jolocom/ddoresolver-rs) github
|
||||
|
||||
@ -1,73 +0,0 @@
|
||||
---
|
||||
date: 2019-07-20
|
||||
title: SSI-Meetup on Open Standards and Implementations
|
||||
layout: single
|
||||
permalink: organizations/ssi-meetup/open-standards/
|
||||
canonical_url: 'https://decentralized-id.com/organizations/ssi-meetup/open-standards/'
|
||||
redirect_from:
|
||||
- organizations/ssi-meetup/open-specs/
|
||||
categories: ["Web Standards","Media"]
|
||||
tags: ["SSI-Meetup","DID","BTCR","Verifiable Credentials","DKMS","W3C","Ethereum","Bitcoin","ION","Microsoft","Media"]
|
||||
last_modified_at: 2019-07-20
|
||||
toc_sticky: false
|
||||
published: false
|
||||
---
|
||||
|
||||
|
||||
>[SSI Meetup](https://ssimeetup.org) is an open, collaborative community to help SSI evangelists around the world, independent of company interests or standards. Our main mission is to help you connect with other SSI enthusiasts and create a dynamic, local, yet globally connected community.
|
||||
|
||||
...[Monthly webinars](https://ssimeetup.org/blog/), the [presentations](https://www.slideshare.net/SSIMeetup) and [video](https://www.youtube.com/channel/UCSqSTlKdbbCM1muGOhDa3Og) of which are invaluable resources.
|
||||
|
||||
|
||||
### DIDs the Fundamental Building block of SSI
|
||||
|
||||
Decentralized Identifiers (DIDs): The Fundamental Building Block of Self-Sovereign Identity (SSI) Drummond Reed, Chief Trust Officer at Evernym, will explain in our second Webinar "Decentralized Identifiers (DIDs) - Building Block of Self-Sovereign Identity (SSI)" giving us the background on how DIDs work, where they come from and why they are important for Blockchain based Digital Identity. https://www.slideshare.net/SSIMeetup/decentralized-identifiers-dids-the-fundamental-building-block-of-selfsovereign-identity-ssi 2018-05-09
|
||||
|
||||
|
||||
### DIDs and BTCR
|
||||
|
||||
* [Decentralized Identifiers DIDs and W3C with Manu Sporny and Drummond Reed](https://www.slideshare.net/SSIMeetup/decentralized-identifiers-dids-and-w3c-with-manu-sporny-and-drummond-reed)
|
||||
<iframe src="//www.slideshare.net/slideshow/embed_code/key/DddAXKYTd9YBLL" width="595" height="485" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;" allowfullscreen> </iframe>
|
||||
|
||||
|
||||
|
||||
### Schema Definitions and Overlay - Paul Knowles
|
||||
|
||||
<iframe src="//www.slideshare.net/slideshow/embed_code/key/BAN42ZJAuafQoj" width="595" height="485" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;" allowfullscreen> </iframe>
|
||||
|
||||
[Schema Definitions and Overlays for Self-Sovereign Identity (SSI) - Paul Knowles](https://www.slideshare.net/SSIMeetup/schema-definitions-and-overlays-for-selfsovereign-identity-ssi-paul-knowles)
|
||||
|
||||
|
||||
### DID Resolution - Markus Sabadello
|
||||
|
||||
<iframe src="//www.slideshare.net/slideshow/embed_code/key/wvgU7Gl8ORUGLI" width="595" height="485" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;" allowfullscreen> </iframe>
|
||||
|
||||
[DID Resolution: Given a DID how do I retrieve its document? – Markus Sabadello](https://www.slideshare.net/SSIMeetup/did-resolution-given-a-did-how-do-i-retrieve-its-document-markus-sabadello)
|
||||
|
||||
|
||||
### Verifiable Credentials 101 - Tyler Ruff
|
||||
|
||||
<iframe src="//www.slideshare.net/slideshow/embed_code/key/2FQiXCaqgTJvrQ" width="595" height="485" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;" allowfullscreen> </iframe>
|
||||
|
||||
[Verifiable Credentials 101 for SSI and Decentralized Digital Identity - Tyler Ruff](https://www.slideshare.net/SSIMeetup/verifiable-credentials-101-for-ssi-and-decentralized-digital-identity-tyler-ruff)
|
||||
|
||||
|
||||
### DID Auth - Markus Sabadello
|
||||
|
||||
<iframe src="//www.slideshare.net/slideshow/embed_code/key/CtcPSLkrTg5z2c" width="595" height="485" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;" allowfullscreen> </iframe>
|
||||
|
||||
[Introduction to DID Auth for SSI with Markus Sabadello](https://www.slideshare.net/SSIMeetup/introduction-to-did-auth-with-markus-sabadello)
|
||||
|
||||
|
||||
### Element DID Method - Orie Steele
|
||||
|
||||
<iframe src="//www.slideshare.net/slideshow/embed_code/key/2ct2imQLUnzp1j" width="595" height="485" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;" allowfullscreen> </iframe>
|
||||
|
||||
[The Element DID Method: Sidetree, Ethereum & IPFS – Orie Steele](https://www.slideshare.net/SSIMeetup/the-element-did-method-sidetree-ethereum-ipfs-orie-steele)
|
||||
|
||||
|
||||
### ION - Bitcoin DIDs with Microsoft - Daniel Buchner
|
||||
|
||||
<iframe src="//www.slideshare.net/slideshow/embed_code/key/e4v6fZdFL5fdu3" width="595" height="485" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;" allowfullscreen> </iframe>
|
||||
|
||||
[Introduction to Ion – a layer 2 network for Decentralized Identifiers with Bitcoin - Daniel Buchner](https://www.slideshare.net/SSIMeetup/introduction-to-ion-a-layer-2-network-for-decentralized-identifiers-with-bitcoin-daniel-buchner)
|
||||
Loading…
Reference in New Issue
Block a user