Awesome-Mirrors/decentralized-id.github.io
1
0
Fork 0
mirror of https://github.com/Decentralized-ID/decentralized-id.github.io.git synced 2024-10-01 01:05:54 -04:00
Code Issues Packages Projects Releases Wiki Activity

sort

Browse Source
This commit is contained in:
⧉ infominer 2023-08-13 00:48:55 -04:00
parent 4da7c49df2
commit 91ed3390c1
4 changed files with 28 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
unsorted/companies.md
View File

@ -2,6 +2,13 @@
published: false
---
* [Matching Identity Management Solutions to Self Sovereign Identity Solutions](https://www.slideshare.net/TommyKoens/matching-identity-management-solutions-to-selfsovereign-identity-principles)
5.2 The Short List
Following our knock-out assessment, there remain a total of nine identity man-agement solutions that match the three defined Self-Sovereign Identity Princi-ples. These are: — Blockauth — Cryptid — DIMS — Sovrin (Evernym) — IPv8 (Delft) — IRMA — Selfkey / KYC-chain — OpenID — uPort
6 Requirements short list
Having determined which identity management solutions fit the initial three requirement, we perform an in-depth assessment of the identity solutions on the short list. To do so, we create a new set of requirements, and match each solution to this new list of requirements.
# SSI Companies
Talao SSI wallet now available on Apple AppStore and Google Play https://medium.com/@talao_io/talao-ssi-wallet-now-available-on-apple-appstore-and-google-play-1435b4a01b1c
## Microsoft

16
unsorted/next/standards.md
View File

@ -85,3 +85,19 @@ DID Auth HTTP proxy.
* [Near-Final Second W3C WebAuthn and FIDO2 CTAP Specifications](https://self-issued.info/?p=2143)
> The [W3C WebAuthn](https://www.w3.org/blog/webauthn/) and [FIDO2](https://fidoalliance.org/fido2/) working groups have been busy this year preparing to finish second versions of the W3C Web Authentication (WebAuthn) and FIDO2 Client to Authenticator Protocol (CTAP) specifications
## RDF
* [Technical Report on the Universal RDF Dataset Normalization Algorithm](https://lists.w3.org/Archives/Public/public-credentials/2021Apr/att-0032/Mirabolic_Graph_Iso_Report_2020_10_19.pdf) 2020-10-19
> The goal of this technical report is to review the Universal RDF Dataset Normalization Algorithm (URDNA2015) for correctness and to provide satisfactory evidence that possible issues with URDNA2015 have been considered and dismissed. We do not lay out the algorithm in its considerable technical detail here, but refer the reader to the proposed technical specification 1 [Longley], a set of proofs by Rachel Arnold and Dave Longely [Arnold], and a reference implementation in Python [DigitalBazaar]
> - [Bill Bradley](https://lists.w3.org/Archives/Public/public-credentials/2021Apr/0032.html)
* [URDNA2015 Implementation Question](https://lists.w3.org/Archives/Public/public-credentials/2022Jul/0017.html) Daniel Petranek
> I've instrumented the rdf-canonicalize library so I can inspect the order of execution, and it appears that what differs between my implementation and the Javascript one is the order of the permutations. The spec doesn't say how the permutations should be ordered, and my intuition is that the order does indeed matter - though I'm happy to be corrected if I'm wrong.
So, here is my question(s):
* Does the order of the permutations matter?
* If so, what order should they be in?

2
unsorted/next/unsorted.md
View File

@ -2,6 +2,8 @@
published: false
---
# Infographic
https://twitter.com/DecentralizeID/timelines/1322735918386733057?ref_src=twsrc%5Etfw

3
unsorted/next/w3c.md
View File

@ -16,3 +16,6 @@ published: false
* [Block Joins W3C](https://twitter.com/brockm/status/1526723285102120960) [@brockm](https://twitter.com/brockm)
> Today, we became a member of the [@W3C](https://twitter.com/w3c), as part of our commitment to building open standards for an open web. We are committed to advancing and adopting decentralized and privacy-preserving standards for self-sovereign digital identity that benefits all. Not centralized platforms.
* [RDF Dataset Canonicalization and Hash Working Group](https://www.w3.org/groups/wg/rch/) 2024-07-20 W3C
> The goal of this group is to standardize the way many of us digitally sign Verifiable Credentials. This working group has been about decade in the making (some would say two decades) and is important for achieving things like BBS+ selective disclosure as well as standardizing the way we format Verifiable Credentials before they are digitally signed.