update from csv

This commit is contained in:
⧉ infominer 2023-06-03 00:35:31 +05:30
parent 16c07a07f3
commit 6fe079c370
2 changed files with 70 additions and 92 deletions

View File

@ -5,11 +5,11 @@ Standards,WeAreOpen,,,Doug Belshaw,,,,,,Open standards should be developed openl
Standards,ContinuumLoop,,,Darrell O'Donnell,,,,,,Premature Standardization & Interoperability,Heres my premise we dont have standards nor interoperability at least not as people really need. We have been through a process that is powerful and good but what we have is what I call “premature standardization.” Its a great start but nowhere near where things will be.,Within the decentralized identity space its premature to think we have real Standardization & Interoperability,https://www.continuumloop.com/premature-standardization-interoperability/,,Post,,,Standardization,,,,,,,,2022-09-11,,,,,,,,,,,,,
Standards,Trinsic,,,Anna Johnson,,,,,,Trinsic Basics: What Are SSI Standards?,There are two kinds of standards that Trinsic implements to enable interoperability and avoid vendor lock-in: data model standards and protocol standards.,Our engineering team ensures that the Trinsic platform is always based on the most recent SSI standards and protocols.,https://trinsic.id/what-are-ssi-standards/,,page,,,Standardization,,,,,,,,2020-11-12,,,,,,,,,,,,,
Standards,Scripting.com,,,Dave Winer,,,,,,Manifesto: Rules for standards-makers,"I've used all kinds of formats and protocols in a long career as a software developer, even created a few. My new manifesto summarizes what I've learned about what works and what doesn't.",,http://scripting.com/2017/05/09/rulesForStandardsmakers.html,,Post,,,Standardization,,,,,,,,2017-05-08,,,,,,,,,,,,,
Standards,ContinuumLoop,,,Darrell O'Donnell,,,,,,Why Engage with Standards?,"too many people complain about problems but dont step to Fix It!. There are certainly a lot of flawed standards but they make interoperability possible not perfect but possible. If you havent used them then you have no right to complain that they are too complex, too simple (even in the same standard) or too domain specific or any of the other rants and raves that go on. <br><brIf youre 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. Youll also benefit from working with experts. These experts donate their time and are more than happy to provide ideas, guidance, and leadership.",,https://www.continuumloop.com/why-engage-with-standards/,,Post,,,Standardization,,,,,,,,2013-09-28,,,,,,,,,,,,,
Standards,ContinuumLoop,,,Darrell O'Donnell,,,,,,Why Engage with Standards?,"too many people complain about problems but dont step to Fix It!. There are certainly a lot of flawed standards but they make interoperability possible not perfect but possible. If you havent used them then you have no right to complain that they are too complex, too simple (even in the same standard) or too domain specific or any of the other rants and raves that go on. <br><br>If youre 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. Youll also benefit from working with experts. These experts donate their time and are more than happy to provide ideas, guidance, and leadership.",,https://www.continuumloop.com/why-engage-with-standards/,,Post,,,Standardization,,,,,,,,2013-09-28,,,,,,,,,,,,,
Standards,Forgerock,,,,,,,,,Who Are the Identerati? - ForgeRock,"Youre 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 the scenes at the Internet Identity Workshop (IIW), a bi-annual gathering of identity experts where we work on improving the identity systems that make the web run. Its a great event thats flown under the radar, so Im excited to share a new documentary on IIW, “Not Just Who They Say We Are: Claiming our identity on the Internet”. This short film shines a light on the stealth community of “Identerati” at IIW that are defining and refining digital identity.","Youre 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 the scenes at the Internet Identity Workshop (IIW), a bi-annual gathering of identity experts where we work on improving the identity systems that make the web run.",https://www.forgerock.com/blog/who-are-the-identerati,,Post,,,Standardization,,,,,,,,2017-03-22,,,,,,,,,,,,,
Standards,Wikipedia,,,,,,,,,Who Runs the Internet?,"NO ONE PERSON, COMPANY, ORGANIZATION OR GOVERNMENT RUNS THE INTERNET.<BR>The Internet itself is a globally distributed computer network comprised of many volantarily interconnected autonomous networks. Similarly, its overnance is conducte by a decentralized and international multi-stakeholder network of interconnected autonomous groups drawing from civil society, the private sector, governments, the academic and research communities, and national and international organizations. They work cooperatively from their respective roles to create shared policies and standards that mantian the Internet's global interoperability for the public good.",,https://es.wikipedia.org/wiki/Archivo:Who-Runs-the-Internet-graphic.png,https://upload.wikimedia.org/wikipedia/commons/thumb/e/ed/Who-Runs-the-Internet-graphic.png/1024px-Who-Runs-the-Internet-graphic.png,wiki entry,,,Standardization,,,,,,,,2013-01-31,,,,,,,,,,,,,
Standards,Wikipedia,,,,,,,,,Who Runs the Internet?,"NO ONE PERSON, COMPANY, ORGANIZATION OR GOVERNMENT RUNS THE INTERNET.<br>The Internet itself is a globally distributed computer network comprised of many volantarily interconnected autonomous networks. Similarly, its overnance is conducte by a decentralized and international multi-stakeholder network of interconnected autonomous groups drawing from civil society, the private sector, governments, the academic and research communities, and national and international organizations. They work cooperatively from their respective roles to create shared policies and standards that mantian the Internet's global interoperability for the public good.",,https://es.wikipedia.org/wiki/Archivo:Who-Runs-the-Internet-graphic.png,https://upload.wikimedia.org/wikipedia/commons/thumb/e/ed/Who-Runs-the-Internet-graphic.png/1024px-Who-Runs-the-Internet-graphic.png,wiki entry,,,Standardization,,,,,,,,2013-01-31,,,,,,,,,,,,,
Standards,Hyperledger,,,,,,,,,Identity Standards ,We hope to accumulate links here that talk to all Identity Standards work. Short updates form this will be used in the paper. Some are already input into the paper and need work polishing up.,,https://wiki.hyperledger.org/display/IWG/Identity+Standards,,wiki entry,,,Decentralized Identity Stack,,,,,,,Hyperledger Identity Working Group,2019-05-20,,,,,,,,,,,,,
Standards,CCG Mailing List,,,Manu Sporny,CCG,,,,,Roadmap: Verifiable Trust Standards,Green - General data format standards<br>Yellow - Vocabulary standards (I the mislabeled VC work)<brMagenta - Protocol standards (I mislabeled DID Resolution)<brRed - Low-level cryptographic primitives<brPurple - General crypto packaging/protocol standards<brOrange - Application layer standards,,https://lists.w3.org/Archives/Public/public-credentials/2021Mar/0014.html,https://lists.w3.org/Archives/Public/public-credentials/2021Mar/att-0014/VerifiableTrustStandards.png,Discussion,,,Decentralized Identity Stack,,,,,,,Credentials Community Group,2021-03-03,,,,,,,,,,,,,
Standards,CCG Mailing List,,,Manu Sporny,CCG,,,,,Roadmap: Verifiable Trust Standards,Green - General data format standards<br>Yellow - Vocabulary standards (I the mislabeled VC work)<br>Magenta - Protocol standards (I mislabeled DID Resolution)<br>Red - Low-level cryptographic primitives<br>Purple - General crypto packaging/protocol standards<br>Orange - Application layer standards,,https://lists.w3.org/Archives/Public/public-credentials/2021Mar/0014.html,https://lists.w3.org/Archives/Public/public-credentials/2021Mar/att-0014/VerifiableTrustStandards.png,Discussion,,,Decentralized Identity Stack,,,,,,,Credentials Community Group,2021-03-03,,,,,,,,,,,,,
Standards,CCG Mailing List,,https://lists.w3.org/Archives/Public/public-credentials/2021Feb/att-0134/2021-Linked-Data-Security.pdf,Manu Sporny,CCG,,,,,Linked Data Security,The attached slide deck provides a basic overview (with examples) of Linked Data Security as well as the specifications in that orbit. The W3C CCG is  actively developing a number of these specifications.,,https://lists.w3.org/Archives/Public/public-credentials/2021Feb/0134.html,,Discussion,,,Decentralized Identity Stack,,,,,,,Credentials Community Group,2021-02-29,,,,,,,,,,,,,
Standards,arxiv,,,,,,,,,A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems (NIST CYBERSECURITY WHITE PAPER),"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. JULY 9, 2019",,https://arxiv.org/pdf/1908.00929.pdf,,Paper,DRAFT,,Decentralized Identity Stack,,,,,,,,2020-01-14,,,,,,,,,,,,,
Standards,Personal,,,Tim Bouma,,,,,,Building Blocks for a New Architecture,"First, you will see the Issuer, Holder and Verifier. This is the archetypal pattern of the decentralized architecture. An issuer issues something to a holder, who then presents it to a verifier, who make a decision. A simple example: government(issuer) issues you a passport (holder), which you present to a border control officer (verifier) who lets you through the gate. When you look at all the use cases (described above), they all fall into this pattern. https://i.imgur.com/qGXEnW1.png","Note: These are my opinions only, and not that of my employer. All information used in developing this post is open and freely available. No statements should be considered as advice or representing…",https://medium.com/@trbouma/building-blocks-for-a-new-architecture-fda2238ac005,,Post,,,Decentralized Identity Stack,,,,,,,,2019-09-23,,,,,,,,,,,,,
@ -17,7 +17,7 @@ Standards,DIF,,,Oliver Terbu,,,,,,The Self-Sovereign Identity Stack,"<table><tr>
Standards,DIF,,https://gist.github.com/creatornader/c8a20c534d3cf8f65a9b34ce2ad81725,Nader Helmy,,,,,,Overview of Decentralized Identity Standards,"we can think of each specification as addressing one or more of the SSI “building blocks” that we described above. In some cases a standard may be a bridge between layers, enabling a closer link between connections, data, and keys, making the ecosystem more secure as a whole. What you will find below is a list of all relevant standards, links to every specification, the organizations they belong to, their relationship to the ecosystem, and their relative maturity as internet technologies.","There are a number of organizations working towards standardization of technologies that span across the web. Of these, there are a handful of umbrella organizations that are particularly important…",https://medium.com/decentralized-identity/overview-of-decentralized-identity-standards-f82efd9ab6c7,https://miro.medium.com/v2/resize:fit:1000/1*oDeFSKBXhWkltGqXZ82yDA.png,Post,,,Decentralized Identity Stack,,,,,,,,2020-03-02,,,,,,,,,,,,,
Standards,SSIMeetup.org ,,https://www.youtube.com/watch?v=RllH91rcFdE,Drummond Reed,Evernym,,,,,The Story of Open SSI Standards,"Drummond Reed, Chief Trust Officer at Evernym and Sovrin Foundation Trustee, features in our first Webinar “The Story of SSI Open Standards” by giving us the background on the foundation of Self Sovereign Identity. Drummond explains the technical and development aspects of DIDs, DKMS, DID Auth and Verifiable Credentials that will make Self Sovereign Identity possible.",,https://ssimeetup.org/story-open-ssi-standards-drummond-reed-evernym-webinar-1/,https://imgur.com/6MLNgXal.png,Presentation,,,Decentralized Identity Stack,,,,,,,,2018-04-27,,,,,,,,,,,,,
Standards,DIF,,,,,,,,,SSI Architectural Stack and Community Efforts Overview,"While a more thorough (and competitive) separation of concerns might slice todays and tomorrows identity systems into more modular and interchangeable parts at many more layers, the diagram used here organizes the space into just three broad divisions, which map roughly to the bottom three in the mapping dominant in the Aries & ToIP communities. For a more detailed and complex mapping, see the forthcoming map by the DIF interoperability working group.",,https://github.com/decentralized-identity/interoperability/blob/master/assets/ssi-architectural-stack--and--community-efforts-overview.pdf,,infographic,,,Decentralized Identity Stack,,,,,,,,2020-09-23,,,,,,,,,,,,,
"Verifiable Credentials,Standards",Personal,,,Kristina Yasuda,VC spec map,,,,,Distributed ID Learning Path,"There is a lot of information about decentralized IDs on the web. I struggled too. (I still do that lol)<BR><BR>There are many standards for decentralized identities, and they are interdependent and interrelated, as you can see from the diagram below.","Describes pre-requisite knowledge, including JSON, JSON-LD, JWT, JWS, JWK, JWA, and sometimes CBOR. She then goes on to break down knowledge areas beginning with the basics: DID-Core, DID-Resolution, DID-Spec, DID Use-Cases. Next, she covers Verifiable Credentials with VC-Data Model, VC Use-Cases, and VC-Implementors Guide, and also Transport, Credential Presentation, and Other Data Formats.",https://translate.google.com/translate?sl=auto&tl=en&u=https://kristinayasuda.com/posts/decentralized-identity-catch-up-path/,https://images.ctfassets.net/iifz0jg6o9rt/1frepoi3bOWvEZOIAKlWkC/de5013e3d77fc29ce3c19a3a532c603d/IBO_WebUI.JPG,Post,,,"Interoperability, Decentralized Identity Stack",,,,,,,,2020-12-09,,,,,,,,,,,,,
"Verifiable Credentials,Standards",Personal,,,Kristina Yasuda,VC spec map,,,,,Distributed ID Learning Path,"There is a lot of information about decentralized IDs on the web. I struggled too. (I still do that lol)<br><br>There are many standards for decentralized identities, and they are interdependent and interrelated, as you can see from the diagram below.","Describes pre-requisite knowledge, including JSON, JSON-LD, JWT, JWS, JWK, JWA, and sometimes CBOR. She then goes on to break down knowledge areas beginning with the basics: DID-Core, DID-Resolution, DID-Spec, DID Use-Cases. Next, she covers Verifiable Credentials with VC-Data Model, VC Use-Cases, and VC-Implementors Guide, and also Transport, Credential Presentation, and Other Data Formats.",https://translate.google.com/translate?sl=auto&tl=en&u=https://kristinayasuda.com/posts/decentralized-identity-catch-up-path/,https://images.ctfassets.net/iifz0jg6o9rt/1frepoi3bOWvEZOIAKlWkC/de5013e3d77fc29ce3c19a3a532c603d/IBO_WebUI.JPG,Post,,,"Interoperability, Decentralized Identity Stack",,,,,,,,2020-12-09,,,,,,,,,,,,,
Standards,WebOfTrustInfo,,,,,,,,RWoT,Recommendations for Decentralized Key Management Systems,"A decentralized key management system (DKMS) aims to solve how consumers can manage their own keys and certificates without relying on a third-party provider having access or controls over the keys.. This method helps to ensure that no third-party can compromise the integrity and security of the system as a whole. Entities can use the system to safely authenticate each other and validate keys and certificates. Centralized key management systems (CKMS) manage key and certificate creation, signing, and validity. Specific problems arise when these authorities become unavailable, or the data they control becomes corrupted or known. Central authorities often become choice targets for attackers. This document proposes to meet these requirements with a decentralized blockchain ledger for providing an oracle of trust and leave control over all keys with end users. The use of a blockchain permits globally readable identifiers and public data to be shared in a secure manner that is not vulnerable to the man-in-the-middle attack or system wide compromise and permits consumers to be self-sovereign. This leaves consumers with the task of key management and protection. This document covers various ideas for how users may create, recover, backup, and revoke keys and provides recommended suggestions.",,https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/topics-and-advance-readings/dkms-recommendations.md,,Paper,,,Decentralized Identity Stack,,,,,,,,2017-09-15,,,,,,,,,,,,,
Standards,SSIMeetup.org,,https://www.slideshare.net/SSIMeetup/decentralized-key-management-dkms-an-essential-missing-piece-of-the-ssi-puzzle-drummond-reed,Drummond Reed,,,,,,DKMS - An Essential Missing Piece of the SSI Puzzle,"DKMS inverts a core assumption of conventional PKI (public key infrastructure) architecture, namely that public key certificates will be issued by centralized or federated certificate authorities (CAs). With DKMS, the initial “root of trust” for all participants is any blockchain or distributed ledger that supports DIDs. This webinar will explain why we need DKMS, what a DKMS-compatible identity wallet looks like, how DKMS can solve some longstanding problems in wallet backup and recovery, and where DKMS is headed for standardization.","If you can't manage the keys for your DIDs (Decentralized Identifiers), then the SSI engine will never get started. That's why DKMS (Decentralized Key Management System) is one of the core open standards in the DID ""stack"".",http://ssimeetup.org/decentralized-key-management-dkms-essential-missing-piece-ssi-puzzle-drummond-reed-webinar-8/,https://i.imgur.com/5qc1qrG.png,Presentation,,,Decentralized Identity Stack,,,,,,,,2018-06-28,,,,,,,,,,,,,
Verifiable Credentials,Wikipedia,,,,,,,,,Verifiable Credentials - Wikipedia,"Verifiable credentials (VCs) are the electronic equivalent of the physical credentials that we all possess today, such as: plastic cards, passports, driving licences, qualifications and awards, etc. The data model for verifiable credentials is a World Wide Web Consortium Recommendation, ""Verifiable Credentials Data Model 1.0 - Expressing verifiable information on the Web"" published 19 November 2019.",,https://en.wikipedia.org/wiki/Verifiable_credentials,https://upload.wikimedia.org/wikipedia/commons/thumb/5/51/VC_triangle_of_Trust.svg/1200px-VC_triangle_of_Trust.svg.png,wiki entry,,,About,,,,,,,,2023-04-25,,,,,,,,,,,,,
@ -44,12 +44,12 @@ Verifiable Credentials,Affinidi,,,,,,,,,Compare and Contrast — IRMA vs Verifia
Verifiable Credentials,IDCommons,,,Grace Rachmany,,,,,IIW,Could an NFT be a VC?,"Case discussed: A group of villages in Africa using a cryptocurrency platform for alternative currencies. Different organizations issue the coins under different circumstances. When you accept a currency, you want to know who is the issuer. The Red Cross might be more or less trusted than the local leader or agricultural cooperative as the issuer of a currency that is supposedly equivalent to a shilling.<br><br>What types of tech could be used for this?<br><br>- Multiple currencies on the blockchains<br>- Certifications in the form of some kind of NFT issued by the issuer.<br>- Limited supply tokens or NFTs that are “expired” when you use them<br>- Open Credential Publisher framework was suggested<br>- VCs are generally authorizations associated with a person, so maybe a person could have the VC and show their credit rating in some way while they are making a transaction<br>- Similarly maybe the VC belongs to the organization that is issuing the coin, proving its reputation over time.",,https://iiw.idcommons.net/20I/_Could_an_NFT_be_a_VC%3F,,Session Notes,,,Comparisons,,,,,,,,2021-05-06,,,,,,,,,,,,,
Verifiable Credentials,Personal,,,Timothy Ruff,,,,,,How does VC Functional Stack compare to #ToIP Stack?,"1. ToIP Layers 2 & 3 compare to Functional Layer 2<br>2. ToIP Layer 4 compares to Functional Layers 3 & 4 (horizontal layer for VC Management, vertical layer for Applications)<br>3. Functional stack doesn't require #blockchain<br>4. Functional Stack doesn't detail steps for trust or verification; ToIP Stack doesn't separate management or storage<br>5. Functional Stack clarifies functions, roles, and potential business models; ToIP stack clarifies trust & security They are complementary, not contradictory.",,https://twitter.com/rufftimo/status/1301314001251438593,https://i.imgur.com/8zakrMQ.png,Thread,,,Comparisons,,,,,,,,2020-09-03,,,,,,,,,,,,,
Verifiable Credentials,CCG Mailing List,,,Michael Herman,CCG,,,,,What are VCs similar to?,"The chip in your e-passport is the analogy Ive been most successful with<br>An issuer gives it to you.<br>You carry it around and show to whom you choose<br>The verifier can check its integrity without contacting the issuer<br>“A VC is like the chip in your passport - bit for any document type”<br>So far the best analogy Ive found.  Policy makers say “ah, I see”",,https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0338.html,,Discussion,,,Comparisons,,,,,,,Credentials Community Group,2021-08-23,,,,,,,,,,,,,
Verifiable Credentials,fossandcrafts,,,,,,,,,Hygiene for a computing pandemic,"This episode of FOSS and Crafts features Christopher Lemmer Webber discussing the object capability security approach. Its a generalization not specific to VCs, continuing from the conversation on the CCG mailinglist, [Hygiene for a computing pandemic: separation of VCs and ocaps/zcaps](https://lists.w3.org/Archives/Public/public-credentials/2020Dec/0028.html), we shared last month.<br",The podcast *show-notes include an epic list of references* supporting the discussion.,https://fossandcrafts.org/episodes/20-hygiene-for-a-computing-pandemic.html,,Post,,,Comparisons,,,,,,,,2021-01-03,,,,,,,,,,,,,
Verifiable Credentials,Personal,,https://lists.w3.org/Archives/Public/public-credentials/2021Jun/0244.html,"Kyle Den Hartog, Manu Sporny",,,,,,Re: The dangers of using VCs as permission tokens (was: PROPOSALs for VC HTTP API call on 2021-06-22),"Agreed, when it comes to the number of checks that occur it's much greater<brbecause of the delegation. With that in mind, looking at the semantics only<brof the system VCs in my opinion weren't optimally designed for permission<brtokens. This difference between the two requires that an implementation<brthat wants to support both claims tokens and permissions tokens has to<brgrapple with the different mental model that arise when trying to stuff<brthese things together. This introduces additional complexity. Additionally<brit leads to weird statements that are being made where it's difficult to<brtell if the VC is behaving like a claims token or a permissions token.<br><br>Yes, exactly this. Exactly what Kyle states above is the reason why it's so complicated (and thus dangerous) to use VCs as permissions tokens.<br><br>This is one of the primary reasons that we separated out the Authorization Capabilities work from the Verifiable Credentials work. Things get really complicated when you start mixing authz/authn/claims/permissions into a Verifiable Credential. Just because you can do it doesn't mean you should",,https://kyledenhartog.com/example-authz-with-VCs/,,Post,,,Comparisons,,,,,,,,2021-06-24,,,,,,,,,,,,,
Verifiable Credentials,fossandcrafts,,,,,,,,,Hygiene for a computing pandemic,"This episode of FOSS and Crafts features Christopher Lemmer Webber discussing the object capability security approach. Its a generalization not specific to VCs, continuing from the conversation on the CCG mailinglist, [Hygiene for a computing pandemic: separation of VCs and ocaps/zcaps](https://lists.w3.org/Archives/Public/public-credentials/2020Dec/0028.html), we shared last month.<br>",The podcast *show-notes include an epic list of references* supporting the discussion.,https://fossandcrafts.org/episodes/20-hygiene-for-a-computing-pandemic.html,,Post,,,Comparisons,,,,,,,,2021-01-03,,,,,,,,,,,,,
Verifiable Credentials,Personal,,https://lists.w3.org/Archives/Public/public-credentials/2021Jun/0244.html,"Kyle Den Hartog, Manu Sporny",,,,,,Re: The dangers of using VCs as permission tokens (was: PROPOSALs for VC HTTP API call on 2021-06-22),"Agreed, when it comes to the number of checks that occur it's much greater<br>because of the delegation. With that in mind, looking at the semantics only<br>of the system VCs in my opinion weren't optimally designed for permission<br>tokens. This difference between the two requires that an implementation<br>that wants to support both claims tokens and permissions tokens has to<br>grapple with the different mental model that arise when trying to stuff<br>these things together. This introduces additional complexity. Additionally<br>it leads to weird statements that are being made where it's difficult to<br>tell if the VC is behaving like a claims token or a permissions token.<br><br>Yes, exactly this. Exactly what Kyle states above is the reason why it's so complicated (and thus dangerous) to use VCs as permissions tokens.<br><br>This is one of the primary reasons that we separated out the Authorization Capabilities work from the Verifiable Credentials work. Things get really complicated when you start mixing authz/authn/claims/permissions into a Verifiable Credential. Just because you can do it doesn't mean you should",,https://kyledenhartog.com/example-authz-with-VCs/,,Post,,,Comparisons,,,,,,,,2021-06-24,,,,,,,,,,,,,
Verifiable Credentials,Personal,,,Kyle Den Hartog,,,,,,Comparing VCs to ZCAP-LD,Why make the investment then to put the time and effort into ZCAPs when weve already got VCs? Simply put because security is hard and trying to push square pegs into round holes often times leads to bugs which are elevated to mission critical authentication/authorization bypass vulnerabilities. By designing around a fit for purpose data model with a well defined problem being solved it allows for us to be much more precise about where we believe extensibility is important versus where normative statements should be made to simplify the processing of the data models. By extension this leads to a simpler security model and likely a much more robust design with fewer vulnerabilities.,,https://kyledenhartog.com/comparing-VCs-with-zcaps/,,Post,,,Comparisons,,,,,,,,2021-09-25,,,,,,,,,,,,,
Verifiable Credentials,CCG Mailing List,,,Dave Longley,CCG,,,,,Re: VCs - zCaps / OCap a Discussion,"TL; DR: My current view is that the main confusion here may be over the difference between VCs and LD Proofs, not VCs and ZCAPs. VCs are not a generalized container for attaching a cryptographic proof to a document. That's what LD proofs (or JOSE style proofs) are for. VCs *use* LD proofs (or JOSE style proofs) to attach an assertion proof to a document that specifically models statements made by an issuer about some subject, which is therefore inherently about the identity of that subject",,https://lists.w3.org/Archives/Public/public-credentials/2020Dec/0027.html,,Discussion,,,Comparisons,,,,,,,Credentials Community Group,2020-12-05,,,,,,,,,,,,,
Verifiable Credentials,W3C,Verifiable Credentials Working Group,https://www.w3.org/2020/01/vc-wg-charter.html,,,,,,,Verifiable Credentials Working Group,The mission of the Verifiable Credentials (formerly known as 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.<br><br>The Chairs of the Working Group are Kristina Yasuda and Brent Zundel. The W3C Staff Contact for the Working Group is Ivan Herman.,,https://www.w3.org/2017/vc/WG/,,Working Group,,,Working Group,,,,,,,,2017-04-14,https://github.com/w3c/verifiable-claims,,,https://lists.w3.org/Archives/Public/public-vc-wg/,,,,,,https://lists.w3.org/Archives/Public/public-vc-wg/,,,
Verifiable Credentials,VCWG,,,Manu Sporny,,,,,,Verifiable Credentials Data Model v1.1 is an official W3C standard!,"It's official, the Verifiable Credentials Data Model v1.1 is a W3C standard!<br><br Verifiable Credentials Data Model v1.1<br https://www.w3.org/TR/2022/REC-vc-data-model-20220303/<br><br>This was largely a maintenance release of the specification. The list of (minor) revisions since the v1.0 release can be found here:https://www.w3.org/TR/2022/REC-vc-data-model-20220303/#revision-history",,https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0005.html,,Specificationification,,,Working Group,,,,,,,Credentials Community Group,2022-03-03,,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,Manu Sporny,,,,,,Verifiable Credentials Data Model v1.1 is an official W3C standard!,"It's official, the Verifiable Credentials Data Model v1.1 is a W3C standard!<br><br> Verifiable Credentials Data Model v1.1<br> https://www.w3.org/TR/2022/REC-vc-data-model-20220303/<br><br>This was largely a maintenance release of the specification. The list of (minor) revisions since the v1.0 release can be found here:https://www.w3.org/TR/2022/REC-vc-data-model-20220303/#revision-history",,https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0005.html,,Specificationification,,,Working Group,,,,,,,Credentials Community Group,2022-03-03,,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,Verifiable Credentials Data Model v1.1,"Credentials are a part of our daily lives; driver's licenses are used to assert that we are capable of operating a motor vehicle, university degrees can be used to assert our level of education, and government-issued passports enable us to travel between countries. This specification provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.","Driver's licenses are used to claim that we are capable of operating a motor vehicle, university degrees can be used to claim our education status, and government-issued passports enable holders to travel between countries. This specification provides a standard way to express these sorts of claims on the Web in a way that is cryptographically secure, privacy respecting, and automatically verifiable.",https://www.w3.org/TR/2022/REC-vc-data-model-20220303/,https://www.w3.org/TR/2022/REC-vc-data-model-20220303/diagrams/ecosystem.svg,Specificationification,RECOMMEND,,Working Group,,,,,,,Verifiable Credentials Working Group,2022-03-03,,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,Verifiable Credentials Data Model v2.0,- The components that constitute a [verifiable credential](https://www.w3.org/TR/2022/WD-vc-data-model-2.0-20220811/%23dfn-verifiable-credentials),"Credentials are a part of our daily lives; driver's licenses are used to assert that we are capable of operating a motor vehicle, university degrees can be used to assert our level of education, and government-issued passports enable us to travel between countries. This specification provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.",https://www.w3.org/TR/vc-data-model-2.0/,https://www.w3.org/TR/vc-data-model-2.0/diagrams/zkp-cred-pres.svg,Specificationification,DRAFT,,Working Group,,,,,,,Verifiable Credentials Working Group,2023-05-20,,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,Verifiable Credential Data Integrity 1.0,"This specification describes mechanisms for ensuring the authenticity and integrity of Verifiable Credentials and similar types of constrained digital documents using cryptography, especially through the use of digital signatures and related mathematical proofs.",,https://www.w3.org/TR/vc-data-integrity/,https://www.w3.org/TR/vc-data-integrity/diagrams/hiw-verification.svg,Specification,Working Draft,,Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-05-15,,,,,,,,,,,,,
@ -102,7 +102,7 @@ Verifiable Credentials,Evernym,,,Daniel Hardman,,,,,,Categorizing Verifiable Cre
Verifiable Credentials,DIF,,https://github.com/decentralized-identity/vc-spec-map/releases/tag/v1.2.0,Michael Ruminer,,,,,,Verifiable Credentials Specification Relationships,"diagrams and documentation on the relationship of verfiable credential specifications<br><br>The current release contains some of the most core specifications and their related specs in a diagram. It does not yet address some of the items especially under DIF work groups for secure data storage, SIOP, Sidetree etc.","""Good for anyone but especially useful when trying to jump in on the deep end. If you walk even this limited tree of specs you know a lot"" - @michaelruminer",https://github.com/decentralized-identity/vc-spec-map,http://decentralized-id.com/images/VC-spec-map.webp,infographic,,,Interoperability,,,,,,,,2021-05-27,,,,,,,,,,,,,
Verifiable Credentials,Evernym,,,Brent Zundel,,,,,,Why the Verifiable Credentials Community Should Converge on BBS+,"BBS+ LD-Proofs use JSON-LD schemas, so credentials that use them can have a rich, hierarchical set of attributes. Instead of the heavy-handed mechanism for the encoding and canonicalization of attributes values that wed imagined for Rich Schemas, they use RDF canonicalization and a hash function. Rather than expanding the credential definition, they discarded it, taking advantage of some properties of BBS+ keys which allow for deterministic expansion.",BBS+ ZKP signatures: The breakthrough the industry has been looking for to converge on a universal format for privacy-respecting VCs.,https://www.evernym.com/blog/bbs-verifiable-credentials/,,Post,,,Varieties,,,,,,,,2021-03-24,,,,,,,,,,,,,
Verifiable Credentials,Personal,,,Steve Lockstep,,,,,,The original #VerifiableCredentials were PKI-based SIM cards and EMV cards.,"These bind key pairs to individuals, and to signed assertions (account numbers) to deliver provenance, fidelity and proof of possession. [https://constellationr.com/blog-news/not-too-much-identity-technology-and-not-too-little](https://constellationr.com/blog-news/not-too-much-identity-technology-and-not-too-little)<br>$5",,https://twitter.com/Steve_Lockstep/status/1419935186188341249,https://i.imgur.com/ucAVxCX.png,tweet,,,Varieties,,,,,,,,2021-06-27,,,,,,,,,,,,,
Verifiable Credentials,CCG Mailing List,,,Anil John,CCG,,,,,FYI >> DHS W3C VC/DID Implementation Profile: Credential Data Model Representation Syntax & Proof Format,"We are walking this path step-by-step by documenting the results and lessons from the DHS sponsored multi-platform, multi-vendor interoperability plug-fests and other rigorous plug-fests with similar goals to develop a “DHS Implementation Profile of W3C Verifiable Credentials and W3C Decentralized Identifiers” to ensure the use of Security, Privacy and Interoperability implementation choices that are acceptable to the USG such that these capabilities can be deployed on and connect to USG networks and infrastructure.<br … please [find attached the DHS Implementation Profile](https://lists.w3.org/Archives/Public/public-credentials/2022Sep/att-0253/DHS.W3C.VC-DID.Implemenation.Profile-20220929-SHARE.pdf) of W3C VCs and W3C DIDs normative guidance on:<br - Credential Data Model Representation Syntax<br - Credential Data Model Proof Format",,https://lists.w3.org/Archives/Public/public-credentials/2022Sep/0253.html,,Discussion,,,Interoperability,,,,,,,Credentials Community Group,2022-09-29,,,,,,,,,,,,,
Verifiable Credentials,CCG Mailing List,,,Anil John,CCG,,,,,FYI >> DHS W3C VC/DID Implementation Profile: Credential Data Model Representation Syntax & Proof Format,"We are walking this path step-by-step by documenting the results and lessons from the DHS sponsored multi-platform, multi-vendor interoperability plug-fests and other rigorous plug-fests with similar goals to develop a “DHS Implementation Profile of W3C Verifiable Credentials and W3C Decentralized Identifiers” to ensure the use of Security, Privacy and Interoperability implementation choices that are acceptable to the USG such that these capabilities can be deployed on and connect to USG networks and infrastructure.<br> … please [find attached the DHS Implementation Profile](https://lists.w3.org/Archives/Public/public-credentials/2022Sep/att-0253/DHS.W3C.VC-DID.Implemenation.Profile-20220929-SHARE.pdf) of W3C VCs and W3C DIDs normative guidance on:<br> - Credential Data Model Representation Syntax<br> - Credential Data Model Proof Format",,https://lists.w3.org/Archives/Public/public-credentials/2022Sep/0253.html,,Discussion,,,Interoperability,,,,,,,Credentials Community Group,2022-09-29,,,,,,,,,,,,,
Verifiable Credentials,DIF,,,,,,,,,Interoperability Mapping Exercise,The archive and information hub for the cross-community interoperability project. Focus is on education and familiarity for various efforts across multiple groups for interoperable decentralized identity infrastructure.,,https://github.com/decentralized-identity/interoperability/blob/master/assets/interoperability-mapping-exercise-10-12-20.pdf,https://i.imgur.com/QvpMl6M.png,infographic,,,Interoperability,,,,,,,,2020-10-13,,,,,,,,,,,,,
Verifiable Credentials,Github,,,creatornader,,,,,,Decentralized Identity Standards.md,"Decentralized Identifiers (DIDs), Decentralized Identifier (DID) Resolution, DID Spec Registries, DID Use Cases, DID Rubric, DID Key, DID Web, WebCrypto, WebAuthn, WebKMS, Verifiable Credentials (VCs), VC Use Cases, VC JSON Schemas, Credential Revocation List, Credential Handler API (CHAPI), Verifiable Presentation Request, JSON Linked Data (JSON-LD), CBOR Linked Data (CBOR-LD), Authorization Capabilities (ZCAP-LD), Linked Data Security Vocab, Linked Data Citizenship Vocab, Linked Data Traceability Vocab, Linked Data Cryptographic Suite Registry, Linked Data Proofs, Linked Data Proofs BBS+ Signatures, Universal Wallet, Encrypted Data Vaults (EDVs), Data Privacy Vocabulary, Data Minimization, ActivityPub, Confidential Storage, DID Peer, DIDComm Messaging, Well Known DID Configuration, Self-Issued DID Profile for OpenID, Verifiable Presentation Exchange, Identity Hubs, Credential Manifest, Sidetree, Key Event Receipt Infrastructure (KERI), OAuth 2.0, Grant Negotiation Access Protocol (GNAP), JWA/JWK, JWT/JWS/JWE, JSON Web Message (JWM), HTTP Signatures, Hashlink, BBS+ Signatures Scheme, Biometric Service Providers (BSPs), Aries RFCs, Interop Test Suite, The Trust Over IP (ToIP) Stack, Rich Schemas, Chained Credentials, Data Overlays, Data Consent Lifecycle, Indirect Identity Control, Anoncreds, Machine-Readable Trust Frameworks, Decentralized Key Management System (DKMS), eXtensible Data Interchange (XDI), OpenID Connect (OIDC), OIDC Credential Provider, User-Managed Access (UMA) 2.0, Consent Receipts, Blinding Identity Taxonomy (BIT)",,https://gist.github.com/creatornader/c8a20c534d3cf8f65a9b34ce2ad81725,,gist,,,Interoperability,,,,,,,,2020-11-25,,,,,,,,,,,,,
Verifiable Credentials,Personal,,,Samuel Smith,,,,,,VC Spec Enhancement Proposal,"the VC standard appears to be an adoption vector for Linked Data, not the other way around. My overriding interest is that the concept of a VC as a securely attributable statement is a very powerful and attractive one and therefore should be widely adopted. We should therefore be picking the best technologies that best support broad VC adoption, not the other way around.",,https://github.com/SmithSamuelM/Papers/blob/master/whitepapers/VC_Enhancement_Strategy.md,,Paper,,,Literature,,,,,,,,2022-04-04,,,,,,,,,,,,,
@ -123,7 +123,7 @@ Verifiable Credentials,IDCommons,,,"Gena Morgan, Kevin Dean",IDCommons,,,,IIW,Ve
Verifiable Credentials,IDCommons,,,Mahmoud Alkhraishi,IDCommons,,,,IIW,Verifiable Credentials for Assets,General Framework on how to think of VCs for Assets including leveraging GS1 and other vocabularies in the traceability vocab.<br><br>Requirements and Opportunities that block adoption of VCs in Supply chains,,https://iiw.idcommons.net/21E/_Verifiable_Credentials_for_Assets_30_min,,Session Notes,,,Use Case,,,,,,,,2021-05-07,,,,,,,,,,,,,
Verifiable Credentials,Trusted Digital Web,,,,,,,,,Using Paper-based Structured Credentials to Humanize Verifiable Credentials,User Scenario: ABC Grocery wants to use the Trusted Digital Web to issue a Purchase Order for 10 cabbages from David's Cabbages. Michael Herman,User Scenario: ABC Grocery wants to use the Trusted Digital Web to issue a Purchase Order for 10 cabbages from David's Cabbages.This tutorial was inspired by...,https://www.youtube.com/watch?v=kM30pd3w8qE,,Video,Rough Cut,,User Experience,,,,,,,,2021-11-19,,,,,,,,,,,,,
Verifiable Credentials,WebofTrustInfo,,,Manu Sporny,,,,,RWoT,Rendering Verifiable Credentials,"This paper explores ways in which the Verifiable Credentials data model could be extended to support visual, audio, and physical renderings for Verifiable Credentials.",,https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/advance-readings/rendering-verifiable-credentials.md,,Paper,,,User Experience,,,,,,,,2022-07-17,,,,,,,,,,,,,
Verifiable Credentials,Personal,,,Pamela Dingle,,,,,,Thread: VCs need Threat Modeling,"Another pre-read recommendation for @identiverse: the @openid for Verifiable Credentials Whitepaper.<br>* [Firstyear Replying to @Erstejahre @pamelarosiedee and 4 others](https://twitter.com/Erstejahre/status/1537615778106658816) ""It also seems to lack any sections about threat modelling and possible risks, making it hard to trust since risks are not directly and clearly addressed.""<BR>* [Torsten Lodderstedt Replying to @Erstejahre @pamelarosiedee and 3 others](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics) ""I agree. We [threat] model while we are designing the protocol, we also need to add it to the spec. Please note: we build on existing work. There is an extensive thread model for OAuth and countermeasures that we built on ([datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics). Feel free to contribute.""",,https://twitter.com/pamelarosiedee/status/1537233243086327812?s%3D20%26t%3DWWt14_H4AXgtn09xb5-yew,,Thread,,,Critique,,,,,,,,2022-06-16,,,,,,,,,,,,,
Verifiable Credentials,Personal,,,Pamela Dingle,,,,,,Thread: VCs need Threat Modeling,"Another pre-read recommendation for @identiverse: the @openid for Verifiable Credentials Whitepaper.<br>* [Firstyear Replying to @Erstejahre @pamelarosiedee and 4 others](https://twitter.com/Erstejahre/status/1537615778106658816) ""It also seems to lack any sections about threat modelling and possible risks, making it hard to trust since risks are not directly and clearly addressed.""<br>* [Torsten Lodderstedt Replying to @Erstejahre @pamelarosiedee and 3 others](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics) ""I agree. We [threat] model while we are designing the protocol, we also need to add it to the spec. Please note: we build on existing work. There is an extensive thread model for OAuth and countermeasures that we built on ([datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics). Feel free to contribute.""",,https://twitter.com/pamelarosiedee/status/1537233243086327812?s%3D20%26t%3DWWt14_H4AXgtn09xb5-yew,,Thread,,,Critique,,,,,,,,2022-06-16,,,,,,,,,,,,,
Decentralized Identifiers,CCG,,,,,,,,,A Primer for Decentralized Identifiers,An introduction to self-administered identifiers for curious people,"A Decentralized Identifier (DID) is a new type of identifier that is globally unique, resolvable with high availability, and cryptographically verifiable. DIDs are typically associated with cryptographic material, such as public keys, and service endpoints, for establishing secure communication channels. DIDs are useful for any application that benefits from self-administered, cryptographically verifiable identifiers such as personal identifiers, organizational identifiers, and identifiers for Internet of Things scenarios. For example, current commercial deployments of W3C Verifiable Credentials heavily utilize Decentralized Identifiers to identify people, organizations, and things and to achieve a number of security and privacy-protecting guarantees. This document is an introduction to the concept of Decentralized Identifiers.",https://w3c-ccg.github.io/did-primer/,https://w3c-ccg.github.io/did-primer/did-primer-diagrams/urn-format.png,Report,,,Main,,,,,,,Credentials Community Group,2021-11-11,https://github.com/w3c-ccg/did-primer,,,,,,,,,,,,
Decentralized Identifiers,W3C,,,Markus Sabadello,"Danube Tech, Sovrin Foundation, OASIS XDI TC",Vienna,,,W3C Workshop on Privacy and Linked Data,Decentralized IDentifers (DIDs),"- Developed at Rebooting-the-Web-of-Trust workshop and W3C Credentials CG<br>- Persistent, dereference-able, cryptographically verifable identifers<br>- Registered in a blockchain or other decentralized network",,https://www.w3.org/2018/vocabws/presentations/Sabadello.pdf,https://i.imgur.com/7NRcJbq.png,Presentation,,,Main,,,,,,,,2018-04-17,,,,,,,,,,,,,
Decentralized Identifiers,Identity Foundation,,,,,,,,,Decentralized Identifiers (DID) 1.0 specification approved as W3C Recommendation,"Announcing the [Decentralized Identifiers (DID) v1.0 specification](https://www.w3.org/TR/did-core/) as an open web standard signals that it is technically sound, mature, and ready for widespread adoption. Having an established v1.0 specification allows work to continue with renewed energy and focus, not only at the many groups meeting at DIF, but across the digital identity community.",The W3C has approved the DIDCore V1.0 spec as an official Recommentdation; DIDs are now an open web standard ready for use and further development,https://blog.identity.foundation/w3cdidspec-2/,,Post,,,Main,,,,,,,,2022-06-22,,,,,,,,,,,,,
@ -160,10 +160,10 @@ Decentralized Identifiers,IDCommons,,"https://iiw.idcommons.net/13D/_We_evaluate
Decentralized Identifiers,IDCommons,,"https://iiw.idcommons.net/13D/_We_evaluated_7_DID_methods_with_the_W3C_DID_Rubric!_did:btcr,_did:sov,_did:ion,_did:web,_did:key,_did:peer,_did:ethr","Walid Fdhila, Markus Sabadello","did:btcr, did:sov, did:ion, did:web, did:key, did:peer, did:ethr, Decentralized Identifiers",,,,IIW,DID Methods Evaluation Report,This report evaluates a selection of DiD methods using the guidelines specified in the W3C DiD method Rubric V1.0 (draft 06 January 2021). The evaluation reflects the authors opinion based on documents and source code that are publicly available. The report mainly includes a comprehensive evaluation.,"Web word processing, spreadsheets and presentations",https://docs.google.com/document/d/1jP-76ul0FZ3H8dChqT2hMtlzvL6B3famQbseZQ0AGS8//,,Report,,,About DID Methods,,,,,,,,2021-04-04,,,,,,,,,,,,,
Decentralized Identifiers,IDCommons,,"https://iiw.idcommons.net/13D/_We_evaluated_7_DID_methods_with_the_W3C_DID_Rubric!_did:btcr,_did:sov,_did:ion,_did:web,_did:key,_did:peer,_did:ethr","Walid Fdhila, Markus Sabadello",Decentralized Identifiers,,,,IIW,Critera for DID Method Evaluation,The criteria selected for did evaluation are derived from (i) did rubric and (ii) principles of SSI.<br>(i) https://w3c.github.io/did-rubric/<br>(ii) https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/self-sovereign-identity-principles.md,,https://docs.google.com/document/d/1vAKtMrsrjO_tLQhah8tRoLaIS7HpOIE6xM38ZoBpgWU/,https://lh3.googleusercontent.com/docs/ADP-6oGo4pZN6hzrDT7Ac5x4QQp6fiOaI5VvfXK6lrPstUV7ugHLmwFd2--hUy7QXjnSqEA_uz6CCgQz71VrxM-DnIiJGz9wR0k4QnknbocdcTn4=w1200-h630-p,Guidance,,,About DID Methods,,,,,,,,2021-05,,,,,,,,,,,,,
Decentralized Identifiers,ArcBlock,did:abt:,,,,,,,,did:abt:,"One of our main goal is to protect users privacy. So people do not use the DID generated from their master key to talk to DAPPs, instead, the WALLET automatically generates an extended DID according to the users master DID and the DAPPs DID and use this extended DID to communicate with the DAPP.",ABT DID Protocol,https://arcblock.github.io/abt-did-spec/,,Specification,,ABT Network,The DID Methods,,,,,,,,2019-10-11,https://github.com/arcblock/abt-did-spec/,,,,,,,,,,,,
Decentralized Identifiers,CCG,did:btcr:,,"Christopher Allen, Ryan Grant, Kim Hamilton Duffy",,,,,,did:btcr:,"The Bitcoin Reference DID method (did:btcr) supports DIDs on the public Bitcoin blockchain. The Bitcoin Reference method has minimal design goals: a DID trust anchor based on the Bitcoin blockchain, updates publicly visible and auditable via Bitcoin transactions, and optionally, additional DID Document information referenced in the transaction OP_RETURN data field. No other Personal Identifiable Information (PII) would be placed on the immutable blockchain.<brA secondary intent of the BTCR method is to serve as a very conservative, very secure example and some best practices for creating a DID method. The use cases for BTCR are focused on anonymous and pseudo-anonymous identities, web-of-trust style webs of identity, and absolute mimimal personal information disclosure. Other DID methods will likely need to loosen these standards.<brSome aspects of the BTCR method will not be practical if inappropriately scaled — for instance, there is a transaction cost to update keys and DDO object, potential UTXO inflation (i.e. one additional unspent output for every BTCR-based identity), and even if segwit isnt used it could cause blockchain bloat. However, identities using the BTCR method can be a strong as Bitcoin itself -- currently securing billions of dollars of digital value.",,https://w3c-ccg.github.io/didm-btcr/,https://w3c-ccg.github.io/didm-btcr/diagrams/btcr-tx-ref.png,Specification,,Bitcoin,The DID Methods,,,,,,,,2019-08-08,,,,,,,,,,,,,
Decentralized Identifiers,CCG,did:btcr:,,"Christopher Allen, Ryan Grant, Kim Hamilton Duffy",,,,,,did:btcr:,"The Bitcoin Reference DID method (did:btcr) supports DIDs on the public Bitcoin blockchain. The Bitcoin Reference method has minimal design goals: a DID trust anchor based on the Bitcoin blockchain, updates publicly visible and auditable via Bitcoin transactions, and optionally, additional DID Document information referenced in the transaction OP_RETURN data field. No other Personal Identifiable Information (PII) would be placed on the immutable blockchain.<br>A secondary intent of the BTCR method is to serve as a very conservative, very secure example and some best practices for creating a DID method. The use cases for BTCR are focused on anonymous and pseudo-anonymous identities, web-of-trust style webs of identity, and absolute mimimal personal information disclosure. Other DID methods will likely need to loosen these standards.<br>Some aspects of the BTCR method will not be practical if inappropriately scaled — for instance, there is a transaction cost to update keys and DDO object, potential UTXO inflation (i.e. one additional unspent output for every BTCR-based identity), and even if segwit isnt used it could cause blockchain bloat. However, identities using the BTCR method can be a strong as Bitcoin itself -- currently securing billions of dollars of digital value.",,https://w3c-ccg.github.io/didm-btcr/,https://w3c-ccg.github.io/didm-btcr/diagrams/btcr-tx-ref.png,Specification,,Bitcoin,The DID Methods,,,,,,,,2019-08-08,,,,,,,,,,,,,
Decentralized Identifiers,Blockstack,did:stack:,,Jude Nelson,,,,,,did:stack:,"Blockstack's DID method is specified as part of its decentralized naming system. Each name in Blockstack has one or more corresponding DIDs, and each Blockstack DID corresponds to exactly one name -- even if the name was revoked by its owner, expired, or was re-registered to a different owner.<br>Blockstack is unique among decentralized identity systems in that it is not anchored to a specific blockchain or DLT implementation. The system is designed from the ground up to be portable, and has already been live-migrated from the Namecoin blockchain to the Bitcoin blockchain. The operational ethos of Blockstack is to leverage the must secure blockchain at all times -- that is, the one that is considered hardest to attack.<br>Blockstack's naming system and its DIDs transcend the underlying blockchain, and will continue to resolve to DID document objects (DDOs) even if the system migrates to a new blockchain in the future.",,https://github.com/blockstack/blockstack-core/blob/stacks-1.0/docs/blockstack-did-spec.md,,Specification,,"Bitcoin, Namecoin, Portable",The DID Methods,,,,,,,,2019-07-19,,,,,,,,,,,,,
Decentralized Identifiers,WebofTrustInfo,did:erc725:,,"Markus Sabadello, Fabian Vogelsteller, Peter Kolarov",,,,,rwot06,did:erc725:,"Decentralized Identifiers (DIDs, see [1]) are designed to be compatible with any distributed ledger or network (called the target system). In the Ethereum community, a pattern known as ERC725 (see [2]) utilizes smart contracts for standard key management functions. We propose a new DID method that allows ERC725 identities to be treated as valid DIDs. One advantage of this DID method over others appears to be the ability to use the full flexibility of Ethereum smart contracts for key management purposes.",,https://github.com/WebOfTrustInfo/rwot6-santabarbara/blob/master/topics-and-advance-readings/DID-Method-erc725.md,,Specification,,Ethereum,The DID Methods,,,,,,ERC725,,2018-02-21,,,,,,,,,,,,,
Decentralized Identifiers,DIDWG,did:example:,,,,,,,,did:example:,"A DID is a simple text string consisting of three parts, the:<br>- URI scheme identifier (did)<br>- Identifier for the DID method<br>- DID method-specific identifier.<br**EXAMPLE 1: A simple example of a decentralized identifier (DID)**<code>did:example:123456789abcdefghi</code><br>The example DID above resolves to a DID document. A DID document contains information associated with the DID, such as ways to cryptographically authenticate the DID controller, as well as services that can be used to interact with the DID subject.",,https://w3c.github.io/did-core/#a-simple-example,https://w3c.github.io/did-core/diagrams/did_detailed_architecture_overview.svg,Specification,,Portable,The DID Methods,,,,,,,Credentials Community Group,2022-07-19,,,,,,,,,,,,,
Decentralized Identifiers,DIDWG,did:example:,,,,,,,,did:example:,"A DID is a simple text string consisting of three parts, the:<br>- URI scheme identifier (did)<br>- Identifier for the DID method<br>- DID method-specific identifier.<br>**EXAMPLE 1: A simple example of a decentralized identifier (DID)**<code>did:example:123456789abcdefghi</code><br>The example DID above resolves to a DID document. A DID document contains information associated with the DID, such as ways to cryptographically authenticate the DID controller, as well as services that can be used to interact with the DID subject.",,https://w3c.github.io/did-core/#a-simple-example,https://w3c.github.io/did-core/diagrams/did_detailed_architecture_overview.svg,Specification,,Portable,The DID Methods,,,,,,,Credentials Community Group,2022-07-19,,,,,,,,,,,,,
Decentralized Identifiers,TranSendX,did:ipid:,,,,,,,,did:ipid:,"The Interplanetary Identifiers DID method (did:ipid:) supports DIDs on the public and private Interplanetary File System (IPFS) networks. IPFS is the distributed content addressable permanent web. More specifically, the IPID DID method utilizes the Interplanetary Linked Data (IPLD) suite of tools. The IPID DID method has minimal design goals: a DID trust anchor based on the IPFS and Libp2p protocol. In and of itself, this is not a blockchain solution. However, blockchains and other distributed ledger technologies could be utilized to anchor the artifacts of this DID methods for further enhanced security.",,https://did-ipid.github.io/ipid-did-method/,,Specification,,IPFS,The DID Methods,,,,,,,,2018-12-31,,,,,,,,,,,,,
Decentralized Identifiers,lifeID Foundation,did:life:,,lifeID,,,,,,did:life:,"lifeID is a decentralized, blockchain-based protocol that acts as an open identity provider. The protocol enables the creation and use of self-sovereign identities as well as the issuance of verifiable credentials to those identities. The blockchain-based components of the protocol include smart contracts for storage, revocation, and recovery of keys and credentials. These contracts may be run on any open, permissionless blockchain. The purpose of this protocol is to allow users to transact their identity in a way that minimizes data disclosure, is cryptographically secure, and enables censorship-resistant decentralized identity provisioning and recovery. The purpose of this specification is to describe how lifeID DIDs are created and the technical requirements to operate on the lifeID platform.",,https://lifeid.github.io/did-method-spec/,,Specification,,RChain,The DID Methods,,,,,,,,2019-08-13,,,,,,,,,,,,,
Decentralized Identifiers,Sovrin Foundation,did:sov:,,Mike Lodder,,,,,,did:sov:,"Sovrin is a public ledger designed specifically and only for privacy-preserving self-sovereign identity. The Sovrin Ledger is governed by the international non-profit Sovrin Foundation. As the only public ledger designed exclusively for self-sovereign identity, Sovrin is optimized for DIDs and DID Documents. DIDs are created, stored, and used with verifiable claims. This specification covers how these DIDs are managed. It also describes related features of Sovrin of particular interest to DID owners, guardians, and developers.",,https://sovrin-foundation.github.io/sovrin/spec/did-method-spec-template.html,,Specification,,Sovrin,The DID Methods,,,,,,,,2023-04-19,,,,,,,,,,,,,
@ -205,7 +205,7 @@ Decentralized Identifiers,"MOAC Blockchain Tech, Inc.",did:moac:,,David Ricardo
Decentralized Identifiers,OmniOne,did:omn:,,,,,,,,did:omn:,"OmniOne is a decentralized network system for Self-Sovereign identity and Verifiable Claims. It can replace a legacy centralized credential system that with trusted blockchain node. In the OmniOne system, several types of certificates are issued. DID(Decentralized Identifiers) is used as the unique identifier of the certificate. Also DID allows to obtain public key information for secure exchange of information between users.",,https://github.com/OmniOneID/did_method/blob/master/did_method.md,,Specification,,OmniOne,The DID Methods,,,,,,,,2019-05-30,,,,,,,,,,,,,
Decentralized Identifiers,"Workday, Inc.",did:work:,,,,,,,,did:work:,"Workday offers a decentralized Credentialing Platform with a Blockchain based trust layer. A key component of the platform is the WayTo by Workday mobile app which allows the user to store verifiable identity documents, encrypted using their own personal encryption key, which is managed in the Trusted Execution Environment (TEE) of their mobile device. The mobile app can hold official documents, training certifications, verified accomplishments and other credentials. The user can choose what to share, and with whom to share it with. Users of the Workday Credentialing Platform will have a DID and a corresponding DID Document on a permissioned ledger, which credential verifiers can use to validate users cryptographic signatures, included in their credentials.",,https://workday.github.io/work-did-method-spec/,"data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAYAAABzenr0AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAyRpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADw/eHBhY2tldCBiZWdpbj0i77u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlkIj8+IDx4OnhtcG1ldGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhNUCBDb3JlIDUuMy1jMDExIDY2LjE0NTY2MSwgMjAxMi8wMi8wNi0xNDo1NjoyNyAgICAgICAgIj4gPHJkZjpSREYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjIj4gPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIgeG1sbnM6eG1wPSJodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvIiB4bWxuczp4bXBNTT0iaHR0cDovL25zLmFkb2JlLmNvbS94YXAvMS4wL21tLyIgeG1sbnM6c3RSZWY9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC9zVHlwZS9SZXNvdXJjZVJlZiMiIHhtcDpDcmVhdG9yVG9vbD0iQWRvYmUgUGhvdG9zaG9wIENTNiAoTWFjaW50b3NoKSIgeG1wTU06SW5zdGFuY2VJRD0ieG1wLmlpZDpFMTZCRDY3REIzRjAxMUUyQUQzREIxQzRENUFFNUM5NiIgeG1wTU06RG9jdW1lbnRJRD0ieG1wLmRpZDpFMTZCRDY3RUIzRjAxMUUyQUQzREIxQzRENUFFNUM5NiI+IDx4bXBNTTpEZXJpdmVkRnJvbSBzdFJlZjppbnN0YW5jZUlEPSJ4bXAuaWlkOkUxNkJENjdCQjNGMDExRTJBRDNEQjFDNEQ1QUU1Qzk2IiBzdFJlZjpkb2N1bWVudElEPSJ4bXAuZGlkOkUxNkJENjdDQjNGMDExRTJBRDNEQjFDNEQ1QUU1Qzk2Ii8+IDwvcmRmOkRlc2NyaXB0aW9uPiA8L3JkZjpSREY+IDwveDp4bXBtZXRhPiA8P3hwYWNrZXQgZW5kPSJyIj8+SM9MCAAAA+5JREFUeNrEV11Ik1EY3s4+ddOp29Q5b0opCgKFsoKoi5Kg6CIhuwi6zLJLoYLopq4qsKKgi4i6CYIoU/q5iDAKs6syoS76IRWtyJ+p7cdt7sf1PGOD+e0c3dygAx/67ZzzPM95/877GYdHRg3ZjMXFxepQKNS6sLCwJxqNNuFpiMfjVs4ZjUa/pmmjeD6VlJS8NpvNT4QQ7mxwjSsJiEQim/1+/9lgMHgIr5ohuxG1WCw9Vqv1clFR0dCqBODElV6v90ogEDjGdYbVjXhpaendioqK07CIR7ZAqE49PT09BPL2PMgTByQGsYiZlQD4uMXtdr+JxWINhgINYhGT2MsKgMrm2dnZXgRXhaHAg5jEJodUAHxux4LudHJE9RdEdA+i3Juz7bGHe4mhE9FNrgwBCLirMFV9Okh5eflFh8PR5nK5nDabrR2BNJlKO0T35+Li4n4+/J+/JQCxhmu5h3uJoXNHPbmWZAHMshWB8l5/ipqammaAf0zPDDx1ONV3vurdidqwAQL+pEc8sLcAe1CCvQ3YHxIW8Pl85xSWNC1hADDIv0rIE/o4J0k3kww4xSlwIhcq3EFFOm7KN/hUGOQkt0CFa5WpNJlMvxBEz/IVQAxg/ZRZl9wiHA63yDYieM7DnLP5CiAGsC7I5sgtYKJGWe2A8seFqgFJrJjEPY1Cn3pJ8/9W1e5VWsFDTEmFrBcoDhZJEQkXuhICMyKpjhahqN21hRYATKfUOlDmkygrR4o4C0VOLGJKrOITKB4jijzdXygBKixyC5TDQdnk/Pz8qRw6oOWGlsTKGOQW6OH6FBWsyePxdOXLTgxiyebILZCjz+GLgMIKnXNzc49YMlcRdHXcSwxFVgTInQhC9G33UhNoJLuqq6t345p9y3eUy8OTk5PjAHuI9uo4b07FBaOhsu0A4Unc+T1TU1Nj3KsSSE5yJ65jqF2DDd8QqWYmAZrIM2VlZTdnZmb6AbpdV9V6ec9znf5Q7HjYumdRE0JOp3MjitO4SFa+cZz8Umqe3TCbSLvdfkR/kWDdNQl5InuTcysOcpFT35ZrbBxx4p3JAHlZVVW1D/634VRt+FvLBgK/v5LV9WS+10xMTEwtRw7XvqOL+e2Q8V3AYIOIAXQ26/heWVnZCVfcyKHg2CBgTpmPmjYM8l24GyaUHyaIh7XwfR9ErE8qHoDfn2LTNAVC0HX6MFcBIP8Bi+6F6cdW/DICkANRfx99fEYFQ7Nph5i/uQiA214gno7K+guhaiKg9gC62+M8eR7XsBsYJ4ilam60Fb7r7uAj8wFyuwM1oIOWgfmDy6RXEEQzJMPe23DXrVS7rtyD3Df8z/FPgAEAzWU5Ku59ZAUAAAAASUVORK5CYII=",Specification,dead,Hyperledger Fabric,The DID Methods,,,,,,,,2020-06-25,,,,,,,,,,,,,
Decentralized Identifiers,VP Inc.,did:vid:,,,,,,,,did:vid:,"The system aims to provide secure authentication and various payment services based on the DID and Verifiable Claims specificiatons published by the W3C and the Decentralised Identity Foundation. VP DID is a decentralized identifier devised to provide a way to uniquely identify a person, an organization. VP DID document contains information for providing various payment methods among network participants in a decentralized way. This specification defines how VP blockchain stores DIDs and DID documents, and how to do CRUD operations on DID documents.",,https://github.com/vpayment/did-method-spec/blob/master/vid.md,,Specification,,VP,The DID Methods,,,,,,,,2019-10-15,,,,,,,,,,,,,
Decentralized Identifiers,"Baidu, Inc.",did:ccp:,,,,,,,,did:ccp:,"Application scenarios:<br>- Digital identity<br>- Joint member key customer system<br>- Financial KYC<br>- Exchange<br>- Smart City<br>- IoT deviceless identity management<br><brProgram features:<brBuilding a decentralized ID system based on blockchain and consortium chains will have almost equal control over the system and enhance cooperation intentions.<br><br>Blockchain asymmetric encryption technology combines public and private keys to ensure the authenticity and reliability of ID and certification.<br><br>Form a richer user portrait, with multiple tags (VIP authentication, privilege authentication, asset authentication...) and one ID.",,https://did.baidu.com/did-spec/,https://did.baidu.com/images/did-login-pc.png,Specification,,Quorum,The DID Methods,,,,,,,,2016-02-08,,,,,,,,,,,,,
Decentralized Identifiers,"Baidu, Inc.",did:ccp:,,,,,,,,did:ccp:,"Application scenarios:<br>- Digital identity<br>- Joint member key customer system<br>- Financial KYC<br>- Exchange<br>- Smart City<br>- IoT deviceless identity management<br><br>Program features:<br>Building a decentralized ID system based on blockchain and consortium chains will have almost equal control over the system and enhance cooperation intentions.<br><br>Blockchain asymmetric encryption technology combines public and private keys to ensure the authenticity and reliability of ID and certification.<br><br>Form a richer user portrait, with multiple tags (VIP authentication, privilege authentication, asset authentication...) and one ID.",,https://did.baidu.com/did-spec/,https://did.baidu.com/images/did-login-pc.png,Specification,,Quorum,The DID Methods,,,,,,,,2016-02-08,,,,,,,,,,,,,
Decentralized Identifiers,Jnctn Limited,did:jnctn:,,,,,,,,did:jnctn:,"The system provides secure credential management services based on the DID and Verifiable Claims specifications published by the W3C and the Decentralised Identity Foundation. JNCTN DID method enables an interoperability bridge between the worlds of centralized, federated, and decentralized identifiers with self soverign identity services. JNCTN DID document contains information for accessing JNCTN DID network methods, how JNCTN stores DIDs and DID documents, and how to do CRUD operations on JNCTN DID documents.",,https://github.com/jnctn/did-method-spec/,,Specification,dead,Jnctn Network,The DID Methods,,,,,,,,,,,,,,,,,,,,,
Decentralized Identifiers,evan GmbH,did:evan:,,,,,,,,did:evan:,evan.network is a blockchain for digitalization and automation of business transactions. The network members create digital twins for their machines and products and develop standards for cross-company transactions. The open technology allows integration into existing business models. evan.network guarantees 100% reliable and permanently secured information.,,https://github.com/evannetwork/evan.network-DID-method-specification/blob/master/evan_did_method_spec.md,,Specification,,evan.network,The DID Methods,,,,,,,,2020-03-24,,,,,,,,,,,,,
Decentralized Identifiers,Elastos Foundation,did:elastos:,,,,,,,,did:elastos:,"DID is completely under the control of the DID subject, without reliance on any centralized registration body, commercial identity provider, or organization issuing certificates. The DID is described in the DID documents. Each DID document includes at least two items: encryption materials and verification methods. The encryption materials integrated with the verification methods provides a set of identify verification mechanisms (such as a public key, anonymous biological identification agreement, etc.), with other optional parts that can be used according to the needs of the application and of the user.",,https://github.com/elastos/Elastos.DID.Method/blob/master/DID/Elastos-DID-Method-Specification_en.md,,Specification,,Elastos ID Sidechain,The DID Methods,,,,,,,,2021-01-04,,,,,,,,,,,,,
@ -213,17 +213,17 @@ Decentralized Identifiers,BOTLabs GmbH,did:kilt:,,,,,,,,did:kilt:,"KILT DIDs are
Decentralized Identifiers,Transmute,did:elem:,,,,,,,,did:elem:,Element is an implementation of the Sidetree protocol that uses the Ethereum blockchain as the ledger layer and IPFS as the Content-addressable storage layer,,https://github.com/decentralized-identity/element/blob/master/docs/did-method-spec/spec.md,,Specification,,,The DID Methods,,,,,,Element DID,,2020-04-06,,,,,,,,,,,,,
Decentralized Identifiers,Transmute,did:github:,,,,,,,,did:github:,"The `github` method is meant to make working with DIDs very simple at the cost of trusting Github.com for assisting in resolving DID Documents.<br><br>Many developers are familar with Github, and its 2 supported public key cryptosystems, GPG and SSH.<br><br>Linked Data Signatures are difficult to work with when operating a server or running a local node of some distributed system / blockchain is a requirement.<br><br>The objective of GitHub DID is to encourage contribution to the DID Spec and Linked Data Signatures, and allow rapid development of extensions to these without requiring the use of slow, or complicated more trustless infrastructure, such as blockchains or other distributed systems.",,https://docs.github-did.com/did-method-spec/,,Specification,,Github,The DID Methods,,,,,,,,2020-05-08,,,,,,,,,,,,,
Decentralized Identifiers,teleinfo caict,did:bid:,,,,,,,,did:bid:,"BID provides distributed identifiers and blockchain-based digital identity services for people, enterprises, devices and digital objects. It aims to build a decentralized, data-secure, privacy-protected and flexible identifier system that addresses trusted connections among people, enterprises, devices and digital objectsenabling the vision of the Internet of Things and trust ingress with everything.",,https://github.com/teleinfo-bif/bid/tree/master/doc/en,,Specification,,bif,The DID Methods,,,,,,,,2022-11-03,,,,,,,,,,,,,
Decentralized Identifiers,PalletOne,did:ptn:,,,,,,,,did:ptn:,"Description of each field in the Base DID Document example (★ required fields, others are optional fields):<br><br>* ★ `context` A single value or an array, specifying the syntax standard that the DID Document format complies with.<br* `controller` Single value or array, other owners of DID Document. You can specify other DIDs to manage the file, and the permissions of other DIDs will be set in the corresponding operations authentication, updation, deletion, and recovery later. The default is controlled by the DID in the DID Document corresponding to the Base DID Document.<br>* ★ `publicKey` A single value or an array that controls the public key information corresponding to the private key of the DID Document.<br>* ★ `id` The ID of the public key, `#keys-<num>` expressed in a unified way, incremented `<num>` from the `1` beginning.<br>* ★ `type` The algorithm of public key generation is unified with the chain,<br * `controller` The owner of the public key `controller` corresponds to the one in the previous level. The format is `<DID>#keys-<num>`. The default situation is controlled by the document DID. `<DID>` The value on the stage controller, a `#keys-<num>` is `<DID>` a corresponding public key `id`.<br>* `publicKeyHex` Hexadecimal information of the public key. When the above controller is the default, this field is **required**.<br* ★ `authentication` Specify `publicKey` which fields can be used for authentication.<br>* `updation` Specify `publicKey` which fields can be used for DID Document **update** operations, such as updating information such as pubkey or service.<br* `deletion` Specify `publicKey` which fields can be used for DID Document **delete** operation.<br>* `recovery` Specify `publicKey` which fields can be used for DID Document **recovery** operations.",,https://github.com/palletone/palletone-DID/blob/master/docs/did-method/README.md,,Specification,,PalletOne,The DID Methods,,,,,,,,2020-02-29,,,,,,,,,,,,,
Decentralized Identifiers,PalletOne,did:ptn:,,,,,,,,did:ptn:,"Description of each field in the Base DID Document example (★ required fields, others are optional fields):<br><br>* ★ `context` A single value or an array, specifying the syntax standard that the DID Document format complies with.<br>* `controller` Single value or array, other owners of DID Document. You can specify other DIDs to manage the file, and the permissions of other DIDs will be set in the corresponding operations authentication, updation, deletion, and recovery later. The default is controlled by the DID in the DID Document corresponding to the Base DID Document.<br>* ★ `publicKey` A single value or an array that controls the public key information corresponding to the private key of the DID Document.<br>* ★ `id` The ID of the public key, `#keys-<num>` expressed in a unified way, incremented `<num>` from the `1` beginning.<br>* ★ `type` The algorithm of public key generation is unified with the chain,<br> * `controller` The owner of the public key `controller` corresponds to the one in the previous level. The format is `<DID>#keys-<num>`. The default situation is controlled by the document DID. `<DID>` The value on the stage controller, a `#keys-<num>` is `<DID>` a corresponding public key `id`.<br>* `publicKeyHex` Hexadecimal information of the public key. When the above controller is the default, this field is **required**.<br>* ★ `authentication` Specify `publicKey` which fields can be used for authentication.<br>* `updation` Specify `publicKey` which fields can be used for DID Document **update** operations, such as updating information such as pubkey or service.<br>* `deletion` Specify `publicKey` which fields can be used for DID Document **delete** operation.<br>* `recovery` Specify `publicKey` which fields can be used for DID Document **recovery** operations.",,https://github.com/palletone/palletone-DID/blob/master/docs/did-method/README.md,,Specification,,PalletOne,The DID Methods,,,,,,,,2020-02-29,,,,,,,,,,,,,
Decentralized Identifiers,Echo Technological Solutions LLC,did:echo:,,,,,,,,did:echo:,We propose a new DID method that allows special objects in ECHO network to be treated as valid DIDs.,,https://github.com/echoprotocol/uni-resolver-driver-did-echo/blob/master/echo_did_specifications.md,,Specification,,Echo,The DID Methods,,,,,,,,2022-10-11,,,,,,,,,,,,,
Decentralized Identifiers,SecureKey,did:trustbloc:,,,,,,,,did:trustbloc:,"The did:trustbloc DID method allows groups of independent entities to share custody of a DID registry consisting of a Sidetree implementation over a permissioned ledger. For more information on Sidetree, please refer to the Sidetree protocol specification.<br><br>Independent stakeholders wishing to transact with one another using DIDs can come together to form a consortium to manage their shared custody of a ledger.<br><br>This spec defines a discovery service. The discovery service provided by the TrustBloc DID Method allows a client to verify that a consortium is endorsed by its constituent stakeholders, verify that the configuration files of each stakeholder (which includes a list of Sidetree endpoints) are signed by the respective stakeholders, and use the provided Sidetree endpoints to perform Sidetree DID operations.",,https://github.com/trustbloc/trustbloc-did-method/blob/master/docs/spec/trustbloc-did-method.md,,Specification,,Hyperledger Fabric,The DID Methods,,,,,,,,2020-04-09,,,,,,,,,,,,,
Decentralized Identifiers,YLZ Inc.,did:san:,,,,,,,,did:san:,The system aims to provide secure authentication and various health services based on the SAN blockchain and DID & Verifiable Credential Specifications published by the W3C.,,https://github.com/Baasze/DID-method-specification,,Specification,,SAN Cloudchain,The DID Methods,,,,,,,,2020-04-17,,,,,,,,,,,,,
Decentralized Identifiers,Gataca,did:gatc:,,,,,,,,did:gatc:,"Gatacas platform is based on a mobile identity portfolio, a set of APIs, and controllers for multiple blockchain networks.<br<br>Gataca is agnostic to the blockchain network. We adapt our infrastructure to the third partys preferred ledger. Gataca currently supports the public network Ethereum and private networks based on Hyperledger Fabric, Hyperledger Besu or Quorum. Other networks may be added as requested.<br>This document provides the DID method specs for how our DID schema is implemented on the Ethereum network.<br><br>The simple structure links an object to a DID with states and public keys. Users do not need privileges to read the information on the blockchain but do need them to write. Gataca is the unique user that can modify the smart contract.",,https://github.com/gatacaid/gataca-did-method,,Specification,,"Ethereum, Hyperledger Fabric, Hyperledger Besu, Alastria",The DID Methods,,,,,,,,2020-05-05,,,,,,,,,,,,,
Decentralized Identifiers,Gataca,did:gatc:,,,,,,,,did:gatc:,"Gatacas platform is based on a mobile identity portfolio, a set of APIs, and controllers for multiple blockchain networks.<br><br>Gataca is agnostic to the blockchain network. We adapt our infrastructure to the third partys preferred ledger. Gataca currently supports the public network Ethereum and private networks based on Hyperledger Fabric, Hyperledger Besu or Quorum. Other networks may be added as requested.<br>This document provides the DID method specs for how our DID schema is implemented on the Ethereum network.<br><br>The simple structure links an object to a DID with states and public keys. Users do not need privileges to read the information on the blockchain but do need them to write. Gataca is the unique user that can modify the smart contract.",,https://github.com/gatacaid/gataca-did-method,,Specification,,"Ethereum, Hyperledger Fabric, Hyperledger Besu, Alastria",The DID Methods,,,,,,,,2020-05-05,,,,,,,,,,,,,
Decentralized Identifiers,"Sphereon, Factomatic, Factom Inc",did:factom:,,,,,,,,did:factom:,"This proposal contains the interoperability specifications for products creating, reading (resolving) updating and deactivating Decentralized Identifiers on top of the Factom Protocol. This specification is not about other products wanting to use DIDs for their specific purpose, like signing or voting. This document describes the low level data structures and rules for DIDs, DID documents, resolution and registration on Factom itself.",,https://github.com/factom-protocol/FIS/blob/master/FIS/DID.md,,Specification,,Factom,The DID Methods,,,,,,,,2019-11-02,,,,,,,,,,,,,
Decentralized Identifiers,Cryptonics Consulting,did:signor:,,,,,,,,did:signor:,"DIDs are registered in the DID Registry on-chain, and have a controller and a subject, expressed in the form of Ethereum addresses. The DID controller may or may not be the subject itself. Multiple controllers can be implemented through proxy smart contracts.",,https://github.com/cryptonicsconsulting/signor-did-contracts/blob/master/did-method-spec.md,,Specification,,"Ethereum, Hedera Hashgraph, Quorum, Hyperledger Besu",The DID Methods,,,,,,,,2020-11-16,,,,,,,,,,,,,
Decentralized Identifiers,"Hedera Hashgraph, Swisscom Blockchain AG",did:hedera:,,,,,,,,did:hedera:,"This document defines a binding of the Decentralized Identifier architecture to Hedera Hashgraph - specifically how to use the Hedera File Service to record membership in 'business application networks' (appnets) and how to use the Hedera Consensus Service (HCS) for CRUD mechanisms on DID documents stored in such business application network. An business application network is a network of computers that store some set of business data (such as DID Documents) in a shared state, and rely on the Hedera mainnet for timestamping and ordering the transactions that cause that business application network state to change. An business application network could be exclusively dedicated to managing DID Documents and other identity artifacts in its state, or it could itself be multi-purpose.",,https://github.com/hashgraph/did-method/blob/master/did-method-specification.md,,Specification,,Hedera Hashgraph,The DID Methods,,,,,,,,2020-05-14,,,,,,,,,,,,,
Decentralized Identifiers,"ProximaX Enterprise, Proximax Inc.",did:sirius:,,,,,,,,did:sirius:,The target system is the ProximaX Sirius Chain network. This can either be:<br>- Sirius Chain on Main Net<br>- Sirius Chain on Test Net<br>- Sirius Chain on Private Net,,https://gitlab.com/proximax-enterprise/siriusid/sirius-id-specs/-/blob/master/docs/did-method-spec.md,,Specification,,ProximaX Sirius Chain,The DID Methods,,,,,,,,2020-07-04,,,,,,,,,,,,,
Decentralized Identifiers,Dock,did:dock:,,,,,,,,did:dock:,"Currently, three public key and signing algorithms are supported for authentication.<br>- Schnorr signatures with Sr25519. The public key is 32 bytes and signature is 64 bytes in size. These are supported by Substrate and Polkadot.<br>- EdDSA signatures with Ed25519 curve. The public key is 32 bytes and signature is 64 bytes in size.<br><br>Dock is currently running as a proof of authority network but will evolve into a proof of stake chain. DIDs can be created by anyone holding Dock tokens but the creator of the DID is not necessarily the owner of the DID and thus cannot manage (update, remove) them. DIDs are managed using their corresponding private keys and these keys are independent of keys controlling the Dock tokens spent while creating the DID.<br><br>The chain does not store the full DID document but only the DID, the corresponding keys and controllers and block number for the last update and this block number changes with each update to the DID. This is needed for replay protection. Dock's client SDK retrieves those details and constructs the full DID document.",,https://github.com/docknetwork/dock-did-driver/blob/master/Dock%20DID%20method%20specification.md,,Specification,,Dock,The DID Methods,,,,,,,,2022-07-21,,,,,,,,,,,,,
Decentralized Identifiers,did-twit,did:twit:,,,,,,,,did:twit:,"Twitter is a highly used and influential social media network that lacks decentralization and higher levels of trust (i.e. signed messages). The `did:twit` specification makes an attempt to increase trust in Twitter interactions.<br><br>The method is similar to [did:key](https://w3c-ccg.github.io/did-method-key) in the sense that it is uses a `did` to wrap a single public key.<br<br>The objective of Twitter DID, similar to that of the [GitHub DID Method](https://github.com/decentralized-identity/github-did), is to encourage use of the [DID Spec](https://w3c-ccg.github.io/did-spec/), by lowering the barrier to entry for use of the technology, and promote higher trust interactions.",,https://github.com/did-twit/did-twit/blob/master/spec/index.md,,Specification,,Twitter,The DID Methods,,,,,,,,2020-07-29,,,,,,,,,,,,,
Decentralized Identifiers,did-twit,did:twit:,,,,,,,,did:twit:,"Twitter is a highly used and influential social media network that lacks decentralization and higher levels of trust (i.e. signed messages). The `did:twit` specification makes an attempt to increase trust in Twitter interactions.<br><br>The method is similar to [did:key](https://w3c-ccg.github.io/did-method-key) in the sense that it is uses a `did` to wrap a single public key.<br><br>The objective of Twitter DID, similar to that of the [GitHub DID Method](https://github.com/decentralized-identity/github-did), is to encourage use of the [DID Spec](https://w3c-ccg.github.io/did-spec/), by lowering the barrier to entry for use of the technology, and promote higher trust interactions.",,https://github.com/did-twit/did-twit/blob/master/spec/index.md,,Specification,,Twitter,The DID Methods,,,,,,,,2020-07-29,,,,,,,,,,,,,
Decentralized Identifiers,Ontology Foundation,did:near:,,,,,,,,did:near:,"NEAR uses readable account identifiers instead of a hash of a public key, and the accounts have some DID features, but not all. We have developed this specification to define a new DID method for hosting DIDs on the NEAR blockchain, also referred to as NEAR DID, and facilitate developers to work with related contracts.",,https://github.com/ontology-tech/DID-spec-near/blob/master/NEAR/DID-Method-NEAR.md,,Specification,,NEAR,The DID Methods,,,,,,,,2020-08-02,,,,,,,,,,,,,
Decentralized Identifiers,China Academy of Information and Communications Technology (CAICT),did:vaa:,,,,,,,,did:vaa:,"Blockchain Identifier Infrastructure (BIF) is a permissioned public blockchain aiming for creating a distributed trust management framework typical for internet ID service, and the [BIF blockchain](http://bidspace.cn/) is governed by China Academy of Information and Communications Technology (CAICT). CAICT is also the official issuing agency with Issuing Agency Code (IAC)——""VAA"", given by ISO/IEC 15459. The IAC indicates an authorized qualification of distributing identifiers with own allocation rules.",,https://github.com/caict-develop-zhangbo/vaa-method/blob/master/README.md,,Specification,,BIF,The DID Methods,,,,,,,,2020-08-05,,,,,,,,,,,,,
Decentralized Identifiers,Attila Aldemir,did:bba:,,,,,,,,did:bba:,"The `bba` DID method aims to enable the Ardor blockchain to act as a DPKI within the SSI ecosystem. It runs on the independent IGNIS child chain and utilizes Ardors Account Properties feature to manage DIDs and corresponding DID controllers. The Account Properties feature provides the possibility to tag an account with a small amount of data (160 characters). A DID controller is always represented in form of an Ardor account and is by default separated from the public keys (if present) embedded in a DID document. Think of a master key controlling the DID operations create, update and deactivate. A DID controller always corresponds to exactly one Ardor account, whereas one Ardor account can control multiple DIDs.<br><br>DID and DID document handling is decoupled so that multiple DID document storages can be defined and integrated to store DID document templates (DID documents without a DID reference). In its current state, the `bba` DID method defines only one storage type (Ardor Cloud Storage).<br>In the following, `bba` DID method compliant account properties are called DID attestations. An account property is `bba` DID method compliant if it aligns to the data model described in the DID Attestation Data Fields section and is self-set. A self-set account property is a property in which sender and receiver accounts are identical.",,https://github.com/blobaa/bba-did-method-specification/blob/master/docs/markdown/spec.md,,Specification,,Ardor,The DID Methods,,,,,,,,2020-08-31,,,,,,,,,,,,,
@ -235,7 +235,7 @@ Decentralized Identifiers,Ontology Foundation,did:klay:,,,,,,,,did:klay:,"Decent
Decentralized Identifiers,Ontology Foundation,did:trx:,,,,,,,,did:trx:,"This TRON DID method specification describes a new DID method, that is, TRON DID and defines how TRON blockchain stores TRON DIDs and their corresponding DID documents, and how to do CRUD operations on TRON DID documents.",,https://github.com/ontology-tech/DID-method-specs/blob/master/did-trx/DID-Method-trx.md,,Specification,,TRON,The DID Methods,,,,,,,,2020-08-14,,,,,,,,,,,,,
Decentralized Identifiers,GRGBanking Blockchain Express,did:grg:,,,,,,,,did:grg:,"GRG did document security authentication is based on the cryptography algorithm. A signature is used to verify that the claim is from a trusted did user. What should be noted is the authenticity verification of the issuer. An alliance blockchain maintained by an official organization is designed and used. In the alliance chain, the did document of the certification authority should be stored, and its did ID number should be displayed on the official website of the relevant organization. Therefore, the verifier can verify claims based on this information.",,https://github.com/GrgChain/DID-method-specs/blob/master/README.md,,Specification,,GrgChain,The DID Methods,,,,,,,,2020-08-01,,,,,,,,,,,,,
Decentralized Identifiers,51nodes GmbH,did:schema:,,,,,,,,did:schema:,The Schema Registry DID Method aims to provide unique and universal identification for schemas in multiple formats hosted on multiple storage mechanisms or networks.,,https://github.com/51nodes/schema-registry-did-method/blob/master/README.md,,Specification,,"Portable, IPFS, evan.network",The DID Methods,,,,,,,,2020-08-26,,,,,,,,,,,,,
Decentralized Identifiers,CCG,did:key,,"Rick Astley, Manu Sporny, Dmitri Zagidulin, Dave Longley, Orie Steele",,,,,,did:key,"Ledger independent DID method based on public/private key pairs.<BR><BR>While DLT-based DID Methods have great decentralization characteristics, and some of the more centralized DID Methods provide strong system control guarantees, the general approaches tend to be expensive to setup and operate. Some use cases requiring DIDs do not need the guarantees provided by these heavy-weight systems. For example, a DID that will only be used for a single, ephemeral interaction might not need to be registered, updated, or deactivated. It is for this class of use cases that the did:key method exists",,https://w3c-ccg.github.io/did-method-key/,,Specification,,"Portable, IPFS, evan.network",The DID Methods,,,,,,,,2022-09-02,,,,,,,,,,,,,
Decentralized Identifiers,CCG,did:key,,"Rick Astley, Manu Sporny, Dmitri Zagidulin, Dave Longley, Orie Steele",,,,,,did:key,"Ledger independent DID method based on public/private key pairs.<br><br>While DLT-based DID Methods have great decentralization characteristics, and some of the more centralized DID Methods provide strong system control guarantees, the general approaches tend to be expensive to setup and operate. Some use cases requiring DIDs do not need the guarantees provided by these heavy-weight systems. For example, a DID that will only be used for a single, ephemeral interaction might not need to be registered, updated, or deactivated. It is for this class of use cases that the did:key method exists",,https://w3c-ccg.github.io/did-method-key/,,Specification,,"Portable, IPFS, evan.network",The DID Methods,,,,,,,,2022-09-02,,,,,,,,,,,,,
Decentralized Identifiers,CCG,,,,did:key,,,,,did-key-creator published,"This has been tested to create did:keys from the P-256,P-384, and P-521 curves specified in https://github.com/w3c-ccg/did-method-key and https://w3c-ccg.github.io/did-method-key/","This is a library for converting public keys to the did:key format. Latest version: 1.2.0, last published: 7 months ago. Start using did-key-creator in your project by running `npm i did-key-creator`. There is 1 other project in the npm registry using did-key-creator.",https://www.npmjs.com/package/did-key-creator,,Code,,"Portable, IPFS, evan.network",The DID Methods,,,,,,,,2022-11-03,,,,,,,,,,,,,
Decentralized Identifiers,Crates,,,Tomislav Markovski,did:key,,,,,Rust implementation of the did:key method,"This crate is intended to provide basic support for did:key methods. It has no external dependencies and can be compiled for any target. It was originally designed for use with DIDComm Extension for gRPC, but we recognized it may be useful if this was an independent library",,https://crates.io/crates/did-key,,Code,,"Portable, IPFS, evan.network",The DID Methods,,,,,,,,2022-11-28,,,,,,,,,,,,,
Decentralized Identifiers,Tryon,did:tyron:,,"Julio, Cabrapan Duarte",,,,,,did:tyron:,"Tyronzil is the W3C Decentralized Identifier Method of the Tyron Self-Sovereign Identity Protocol. You can find it published at the W3C DID Specification Registries, and it is the first DID Method of the Zilliqa blockchain - funded by ZILHive Innovation grants.",,https://www.tyronzil.com/,,Specification,,Zilliqa,The DID Methods,,,,,,,,,,,,,,,,,,,,,
@ -245,11 +245,11 @@ Decentralized Identifiers,MediBloc,did:panacea:,,,,,,,,did:panacea:,"Panacea is
Decentralized Identifiers,Hyperledger Foundation,did:indy:,,,,,,,,did:indy:,"Indy is a public ledger designed specifically and only for privacy-preserving self-sovereign identity. A Hyperledger Indy ledger is designed specifically to enable the use of verifiable credentials, allowing credential issuers to publish data necessary for issuing verifiable credentials and constructing presentations from those verifiable credentials. This specification covers how DIDs on an Indy ledger are managed and the operations for creating, reading, updating, and deleting DIDs.",,https://github.com/hyperledger/indy-did-method,,Specification,,Hyperledger Indy,The DID Methods,,,,,,,,2023-02-23,,,,,,,,,,,,,
Decentralized Identifiers,IDCommons,,,Stephen Curran,did:indy:,,,,IIW,The did:indy DID Method - Future Indy Ledgers,Getting involved with this work:,,https://iiw.idcommons.net/4I/_The_did:indy_DID_Method_-_Future_Indy_Ledgers,,Session Notes,,Hyperledger Indy,The DID Methods,,,,,,,,2021-05-06,,,,,,,,,,,,,
Decentralized Identifiers,BCGov,,,Stephen Curran,did:indy:,,,,,did:indy Presentation,"- Namespaced DIDs useful across all Indy instances<br>- Indy network discovery<br>- Full DIDDoc support<br>- Namespaced identifiers for other Indy objects (schemas, etc.)<br>- Support for important resolution parameters<br>- E.g. version-id, version-time, resource<br><br>Nice to have (but not likely to be there):<br>- Cross-ledger registration of networks for discovery<br>- Support for KERI identifiers on Indy networks<br><br>Getting involved with this work:<br>- [HackMD Document](https://hackmd.io/@icZC4epNSnqBbYE0hJYseA/S1eUS2BQw) with current spec<br>- Home of future spec: [indy-did-method](https://github.com/hyperledger/indy-did-method)<br>- [Meeting Wiki](https://wiki.hyperledger.org/display/indy/Indy%2BDID%2BMethod%2BSpecification) and schedule<br>- Hyperledger [indy-did-method](https://chat.hyperledger.org/channel/indy-did-method) chat channel",,https://docs.google.com/presentation/d/1c5K7E5CRx9ANuwmVBIyFVG5hJ4lH0EyW-wkmraLivBI/edit?usp%3Dsharing,,Presentation,,Hyperledger Indy,The DID Methods,,,,,,,,2021-04-20,,,,,,,,,,,,,
Decentralized Identifiers,Blockchain Commons,did:onion:,,,,,,,,did:onion:,"🧅 part of the torgap technology family<brDIDs that target a distributed ledger face significant practical challenges in bootstrapping enough meaningful trusted data around identities to incentivize mass adoption. We propose using a new DID method that allows them to bootstrap trust using a Tor Hidden Service's existing reputation.<br><br>we'd like to review more with our community how close we want to keep did:onion to did:web, and if we want to incorporate some elements of did:peer or KERI or to leverage services like Open Time Stamps.",,http://htmlpreview.github.io/?https://raw.githubusercontent.com/BlockchainCommons/did-method-onion/main/index.html,,Specification,,Tor,The DID Methods,,,,,,,,2021-08-06,,,,,,,,,,,,,
Decentralized Identifiers,Blockchain Commons,did:onion:,,,,,,,,did:onion:,"🧅 part of the torgap technology family<br>DIDs that target a distributed ledger face significant practical challenges in bootstrapping enough meaningful trusted data around identities to incentivize mass adoption. We propose using a new DID method that allows them to bootstrap trust using a Tor Hidden Service's existing reputation.<br><br>we'd like to review more with our community how close we want to keep did:onion to did:web, and if we want to incorporate some elements of did:peer or KERI or to leverage services like Open Time Stamps.",,http://htmlpreview.github.io/?https://raw.githubusercontent.com/BlockchainCommons/did-method-onion/main/index.html,,Specification,,Tor,The DID Methods,,,,,,,,2021-08-06,,,,,,,,,,,,,
Decentralized Identifiers,Ceramic,did:nft:,,,,,,,,did:nft:,"The NFT DID Method converts any non-fungible token on any blockchain into a decentralized identifier where the owner of the NFT is the controller of the DID. This is achieved by using the Chain Agnostic Improvement Proposals to describe NFT assets and blockchain accounts, as well as the Ceramic network to find the DID associated with the owner of the NFT.",,https://github.com/ceramicnetwork/CIPs/blob/main/CIPs/cip-94.md,,Specification,,Ethereum,The DID Methods,,,,,,,,2021-02-12,,,,,,,,,,,,,
Decentralized Identifiers,Gimly,did:eos:,,,,,,,,did:eos:,"1. Identity - the management of accessible public key infrastructure and identifies. Decentralized Identifiers is the W3C standard that allows this. Compliance with this standard allows application layers to interoperate without a need to understand the base layer decentralised protocols that power identities.<br>2. Application - use of the identity layer to interact and provide meaningful, secure and verifiable data communications and interaction. The Verifiable Credentials W3C standard is the most prominent and adopted standard here which is a data structure and message protocol allowing people and organisations to securely and in a verifiable way send and verify information about themselves ""credentials"" to each other. DIDComm is another important application layer that uses DID methods to communicate between SSI identities.",,https://github.com/Gimly-Blockchain/eosio-did-spec,,Specification,,EOS,The DID Methods,,,,,,,,2021-06-30,,,,,,,,,,,,,
Decentralized Identifiers,Gimly,,,,did:eos:,,,,,The EOSIO DID method specification,"We have been working with the [Decentralised Identity Foundation](https://identity.foundation) to shape this specification, and also want to thank the [W3C Credentials Community Group](https://www.w3.org/community/credentials/) for their support in the creation of the [Verifiable Condition](https://github.com/Gimly-Blockchain/verifiable-conditions) type, a necessary component to create the EOSIO DID document to represent EOSIO account permissions.",Gimly has built a full draft of the EOSIO Decentralised Identifier (DID) method specification. This specification guides the implementation of DIDs on EOSIO powered blockchains.,https://www.gimly.io/blog/the-eosio-did-method-specification,,Post,,EOS,The DID Methods,,,,,,,,2021-04-02,,,,,,,,,,,,,
Decentralized Identifiers,SpruceID,did:did:,https://lists.w3.org/Archives/Public/public-credentials/2021Apr/0026.html,,,,,,,did:did:,"DID Identity DID (DID) DID method<BR><BR>Spruce announces did:did, a DID method based on Decentralized Identifiers (DIDs). We hope the community will find this useful to help increase adoption and interoperability of Decentralized Identity technology.",,https://github.com/spruceid/did-did/,,Specification,,humor,The DID Methods,,,,,,,,2021-04-01,,,,,,,,,,,,,
Decentralized Identifiers,SpruceID,did:did:,https://lists.w3.org/Archives/Public/public-credentials/2021Apr/0026.html,,,,,,,did:did:,"DID Identity DID (DID) DID method<br><br>Spruce announces did:did, a DID method based on Decentralized Identifiers (DIDs). We hope the community will find this useful to help increase adoption and interoperability of Decentralized Identity technology.",,https://github.com/spruceid/did-did/,,Specification,,humor,The DID Methods,,,,,,,,2021-04-01,,,,,,,,,,,,,
Decentralized Identifiers,SpruceID,did:undid:,,,,,,,,did:undid:,"did:un-did is a DID method that enables using any valid Decentralized Identifier (DID) as a did:un-did DID, but more importantly it un-does the did that did:did did method performs.<br><br>*Clarification, a few week ago we shared about the [DID:DID](https://did-did.spruceid.com/) method. [April Fools Joke](https://en.wikipedia.org/wiki/April_Fools%2527_Day_RFC)!!! Heres yet another DID method in the series.*",,https://did-undid.github.io/did-undid/,,Specification,,humor,The DID Methods,,,,,,,,2021-04-01,,,,,,,,,,,,,
Decentralized Identifiers,SpruceID,did:doge:,,,,,,,,did:doge:,"We draw heavily from prior work by Christopher Allen and Kim Hamilton Duffy within the W3C Credentials Community Group on the BTCR DID Method due to strong architectural similarities between the Bitcoin and Dogecoin blockchains.<br><br>However, there are some key differences that enable new privacy-preserving benefits. Namely, the did:doge method-specific identifier is the Base58Check-encoded Dogecoin address itself, allowing for DID usage even in the absence of any public transaction histories and only relying upon them for rotation events for verification methods and service endpoints.",,https://spruceid.github.io/did-doge/index.html,,Specification,,Dogecoin,The DID Methods,,,,,,,,2023-05-04,https://github.com/spruceid/did-doge,,,,,,,,,,,,
Decentralized Identifiers,"SpruceID, TQ Tezos",did:tz:,,,,,,,,did:tz:,"did:tz is a multi-modal DID method design with many offchain, on-chain, and side-chain/L2 use cases in mind. A valid Tezos address (controlled by a private key from any of 3 supported curves) can control an ""implicit"" DID document (generatively created from the address like a did:key), an ""onchain"" DID document (published via smart contract on any Tezos ledger), or have ""patches"" applied to it that are published and governed by a closed network or authority (including, for example, a sidetree network). In particular, this third option has not been specified in any detail, and we would be particularly curious to hear from implementers of such systems before further specifying it.",,https://github.com/w3c-ccg/did-tz,,Specification,,Tezos,The DID Methods,,,,,,,,2022-01-13,,,,,,,,,,,,,
@ -273,14 +273,14 @@ Decentralized Identifiers,Personal,,https://eu01web.zoom.us/rec/play/4_ZLV8uot0h
Decentralized Identifiers,IDCommons,,,Dave Huseby,,,,,IIW,"Dont use DIDs, DIDs, nor DIDs: Change My Mind (a.k.a. Oh no he DIDnt)",This session was to talk about the topics I put in a recent article that created a huge fire in our community where I lay out the case for completely abandoning the W3C DID standards.,,"https://iiw.idcommons.net/10A/_Don%27t_use_DIDs,_DIDs,_nor_DIDs:_Change_My_Mind_(a.k.a._Oh_no_he_DIDn%27t)",,Session Notes,,,Critique,,,,,,,,2021-05-07,,,,,,,,,,,,,
Decentralized Identifiers,cardossier CH,,https://iiw.idcommons.net/21D/_The_world_between_public_and_private_DIDs_-_Or_how_to_make_use_of_SSI_without_the_subjects,This Loepfe,,,,,,The world between public and private DIDs - Or how to make use of SSI without the subjects,"- It was very hard for me to explain the problem Im searching a solution for and equally for the proposed solution ideas.<br>- We discussed a lot of more philosophical questions and if peer-dids are a good thing or not and if it is worth trying to minimize correlation when any involved party anyway stores the personal data of the related persons. I think we should make it as hard as possible to correlate data, even if we can not completely prevent it.<br>- We also discussed the potential complexity of such a solution and if it is worth it. The conclusion was to minimize the number of personas one should (be forced) to hold, such that it is still easy to maintain.",,https://cardossier.ch/wp-content/uploads/2021/05/iiw-between-public-and-private.pdf,,Presentation,,,Discussion,,,,Public vs Private,,,,05-2021,,,,,,,,,,,,,
Decentralized Identifiers,CCG Mailing List,,,Steve Capell,CCG,,,,,DID methods as W3C standards - a happy compromise?,can't we pick just a small number of un-controversial methods to standardise?  even if it's just did:key and did:web to start with.,,https://lists.w3.org/Archives/Public/public-credentials/2022Feb/0117.html,,Discussion,,,Discussion,,,,Methods as Standards,,,,2022-02-22,,,,,,,,,,,,,
Decentralized Identifiers,CCG Mailing List,,,Manu Sporny,CCG,,,,,Re: CCG Community opinions needed to define CCG scope (specifically re: did methods as work items),"Heather Vescent wrote:<br1. What are the *pros* of including did methods as work items in the CCG?<brCommunity vetting and approval of particular DID Methods.<br><br>Basically, broader and deeper review of DID Methods that we expect to be of great use to the world. I expect there will be DID Methods that the community wants to eventually propose as DID Methods for standardization (did:key and<br><br>did:web feel like two ones where we could get consensus on doing so).",,https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0376.html,,Discussion,,,Discussion,,,,Methods as Standards,,,,2021-08-26,,,,,,,,,,,,,
Decentralized Identifiers,CCG Mailing List,,,Manu Sporny,CCG,,,,,Re: CCG Community opinions needed to define CCG scope (specifically re: did methods as work items),"Heather Vescent wrote:<br>1. What are the *pros* of including did methods as work items in the CCG?<br>Community vetting and approval of particular DID Methods.<br><br>Basically, broader and deeper review of DID Methods that we expect to be of great use to the world. I expect there will be DID Methods that the community wants to eventually propose as DID Methods for standardization (did:key and<br><br>did:web feel like two ones where we could get consensus on doing so).",,https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0376.html,,Discussion,,,Discussion,,,,Methods as Standards,,,,2021-08-26,,,,,,,,,,,,,
Decentralized Identifiers,GoDiddy,,https://iiw.idcommons.net/2C/_godiddy.com_-_Universal_DID_Services,Markus Sabadello,,,,,,godiddy.com - Universal DID Services,"Basic functions are creating, resolving, updating, and deactivating DIDs across multiple DID methods and networks. Advanced functions include key management, search, transfer of DIDs, lookup of historical DID document versions, notification of DID-related events, and more.",,https://godiddy.com,,site,,,Tools and Utilities,,,,,,,,2021-05-06,,,,,,,,,https://docs.godiddy.com/,https://api.godiddy.com/,,,
Decentralized Identifiers,IDCommons,,,Markus Sabadello,,,,,,Standard Interfaces for DID Create/Update/Deactivate,"- There is an attempt to specify abstract interfaces if you want to Create/Update/Deactivate a did that could be implemented for all did methods.<br>- The idea of this specification is to provide a standard with the same assumptions as with resolution. It should be in an abstract level, meaning it should specify the inputs and outputs of creating/updating/deactivating a did but not how it should be implemented.",,https://iiw.idcommons.net/3C/_Standard_Interfaces_for_DID_Create/Update/Deactivate,,Session Notes,,,Tools and Utilities,,,,,,,,2021-07-17,,,,,,,,,,,,,
Decentralized Identifiers,W3C,,,,,,,,,DID test suite,"DID test suite is not for runtime, but the Universal Resolver could do a few simple checks on a driver's responses. But there's also a philosophical question: Should the Universal Resolver be ""allowed"" to check and potentially transform driver responses, or should it just ""pass through"" everything that comes from a driver?",,https://github.com/w3c/did-test-suite,,Code,,,Tools and Utilities,,,,,,,,2023-01-17,,,,,,,,,,,,,
Decentralized Identifiers,Personal,,,Micheal Herman,,,,,,BlueToque Tools Toolkit,"BlueToque Tools is a collection of software tools for working with DID Method Namespaces, DID Identifiers, DID Documents, DID Agent Service Endpoints, DID Agent Servers, DID Agent Clusters, and DID Objects (the 7 DIDs). The flagship tool is didlang, a language for interactively working with the 7 DIDs.",,https://github.com/mwherman2000/BlueToqueTools,,Code,,,Tools and Utilities,,,,,,,,2022-12-06,,,,,,,,,,,,,
Decentralized Identifiers,W3C,,,,,,,,,Objections overruled by W3C director approving the DIDCore specification as a W3C Recommendation,"In its next chartered period the Working Group should address and deliver proposed standard DID method(s) and demonstrate interoperable implementations.  The community and Member review of such proposed methods is the natural place to evaluate the questions raised by the objectors and other Member reviewers regarding decentralization, fitness for purpose, and sustainable resource utilization. -Ralph Swick, for Tim Berners-Lee",,https://www.w3.org/2022/06/DIDRecommendationDecision.html,,Post,,,W3C Recommendation,,,,,,,,2022-06-30,,,,,,,,,,,,,
Decentralized Identifiers,DIF,,,,,,,,,Decentralized Identifiers (DID) 1.0 specification approved as W3C Recommendation,"Announcing the [Decentralized Identifiers (DID) v1.0 specification](https://www.w3.org/TR/did-core/) as an open web standard signals that it is technically sound, mature, and ready for widespread adoption. Having an established v1.0 specification allows work to continue with renewed energy and focus, not only at the many groups meeting at DIF, but across the digital identity community.",The W3C has approved the DIDCore V1.0 spec as an official Recommentdation; DIDs are now an open web standard ready for use and further development,https://blog.identity.foundation/w3cdidspec-2/,,Post,,,W3C Recommendation,,,,,,,,2022-06-30,,,,,,,,,,,,,
Decentralized Identifiers,TOIP,,,,,,,,,A DIF & TOIP Joint Statement of Support for the Decentralized Identifiers (DIDS) V1.0 Specification Becoming A W3C Specification,"DIDs are a critical part of a technical foundation for the products and activities of many of our members. Many of the implementations in the [DID Working Groups implementation report](https://w3c.github.io/did-test-suite/%23report-by-methods) were developed by engineers and companies who collaborate openly at DIF on points of technical interoperability, and at ToIP on points of policy and governance.<brWhy would you have 75 logins when you could have 1?",,https://trustoverip.org/blog/2021/10/29/a-dif-toip-joint-statement-of-support-for-the-decentralized-identifiers-dids-v1-0-specification-becoming-a-w3c-standard/,,Post,,,W3C Recommendation,,,,,,,,2021-10-29,,,,,,,,,,,,,
Decentralized Identifiers,TOIP,,,,,,,,,A DIF & TOIP Joint Statement of Support for the Decentralized Identifiers (DIDS) V1.0 Specification Becoming A W3C Specification,"DIDs are a critical part of a technical foundation for the products and activities of many of our members. Many of the implementations in the [DID Working Groups implementation report](https://w3c.github.io/did-test-suite/%23report-by-methods) were developed by engineers and companies who collaborate openly at DIF on points of technical interoperability, and at ToIP on points of policy and governance.<br>Why would you have 75 logins when you could have 1?",,https://trustoverip.org/blog/2021/10/29/a-dif-toip-joint-statement-of-support-for-the-decentralized-identifiers-dids-v1-0-specification-becoming-a-w3c-standard/,,Post,,,W3C Recommendation,,,,,,,,2021-10-29,,,,,,,,,,,,,
Decentralized Identifiers,Indicio,,,Sam Curren,,,,,,Indicios support for the W3C DID Specification and its path to standardization,"The position of Indicio is that the DID Specification is of signal importance to creating a better digital world. We recognize that, as with any specification, improvements can and will be made in the future; but we back its recommendations and its approval.",The W3Cs DID Specification is critical to building a better digital world.,https://indicio.tech/indicios-support-for-the-w3c-did-specification-and-its-path-to-standardization/,,Post,,,W3C Recommendation,,,,,,,,2022-07-01,,,,,,,,,,,,,
Decentralized Identifiers,The Register,,,,,,,,,"W3C overrules objections by Google, Mozilla to decentralized identifier spec","The [DID specification](https://www.w3.org/TR/did-core/%23introduction) describes a way to deploy a globally unique identifier without a centralized authority (eg, Apple [for Sign in with Apple](https://developer.apple.com/sign-in-with-apple/) as a verifying entity.",,https://www.theregister.com/2022/07/01/w3c_overrules_objections/,,Post,,,W3C Recommendation,,,,,,,,2022-07-01,,,,,,,,,,,,,
Decentralized Identifiers,IOHK,,,,,,,,,Advancing digital identity through DID core specification,The recent DID core specification approval at the World Wide Web Consortium (W3C) provided clearer and stronger foundations for identity platforms building decentralized identifiers.,"Good to see Cardano jumping on the bandwagon, looks like they will bring DID\VC to Atla Prism.",https://iohk.io/en/blog/posts/2022/09/08/advancing-digital-identity-through-did-core-specification/,,Post,,,W3C Recommendation,,,,,,,,2022-09-08,,,,,,,,,,,,,
@ -435,15 +435,15 @@ Blockcerts,Learning Machine,,,,,,,,,Digital Identity,A framework for organizing
Blockcerts,Learning Machine,,,,,,,,,Learning Machine,Get a complete system to issue digital credentials in a blockchain-secured format that is easily shareable and instantly verifiable anywhere in the world.,,https://www.learningmachine.com/,https://www.learningmachine.com/wp-content/uploads/2019/06/mobile-cert-min.png,company,,,Learning Machine,,,,,,,,2016,,,,,,,,,,,,,
Blockcerts,Personal,,,Natalie Smolenski,,,,,,"Natalie Smolenski - Author, Speaker","Natalie Smolenski is an anthropologist leading business development for blockchain technology firm Learning Machine. She writes and speaks about identity, tech, and government.",,https://www.nataliesmolenski.com/,,blog,,,Learning Machine,,,,,,,,,,,,,,,,,,,,,
Blockcerts,Learning Machine,,,,,,,,,Academic Credentialing and the Blockchain,"Hello everyone. My name is Chris Jagers. Im the CEO of Learning Machine, the software company that has been working with MIT over the last year to develop an open standard for blockchain certificates. Ill be giving a short presentation about blockchain-based academic credentials, followed by a discussion with our panel and with all of you.",,https://www.learningmachine.com/academic-credentialing-blockchain/,,page,,,Learning Machine,,,,,,,,2016-10-28,,,,,,,,,,,,,
Blockcerts,Hyland Credentials,,,,,,,,,Future Proof,"Learning Machine is proud to announce that we have won Phase-1 funding for our response to the open call “Preventing Forgery & Counterfeiting of Certificates and Licenses through the use of Blockchain and Distributed Ledger Technology.” [...] The open-source reference implementation, targeted for 2020, will include:<br- Updating the Blockcerts schema to a Verifiable Credentials-based format<br- Updating the Blockcerts signature/verification scheme to conform to the latest JSON-LD signature suite format<br- Updating Blockcerts credential issuance and verification<br- Incorporating a cost-efficient DID method for issuers",,https://www.hylandcredentials.com/future-proof,https://www.learningmachine.com/wp-content/uploads/2019/07/vc.png,page,,,Learning Machine,,,,,,,,2017-07,,,,,,,,,,,,,
Blockcerts,Hyland Credentials,,,,,,,,,Future Proof,"Learning Machine is proud to announce that we have won Phase-1 funding for our response to the open call “Preventing Forgery & Counterfeiting of Certificates and Licenses through the use of Blockchain and Distributed Ledger Technology.” [...] The open-source reference implementation, targeted for 2020, will include:<br>- Updating the Blockcerts schema to a Verifiable Credentials-based format<br>- Updating the Blockcerts signature/verification scheme to conform to the latest JSON-LD signature suite format<br>- Updating Blockcerts credential issuance and verification<br>- Incorporating a cost-efficient DID method for issuers",,https://www.hylandcredentials.com/future-proof,https://www.learningmachine.com/wp-content/uploads/2019/07/vc.png,page,,,Learning Machine,,,,,,,,2017-07,,,,,,,,,,,,,
Blockcerts,Blockcerts,Blockcerts,,,,,,,,Blockcerts,"open standard for issuing and verifying blockchain-based official records; The project offers open-source libraries, tools, and mobile apps. MIT has [issued](https://www.insidehighered.com/news/2017/10/19/mit-introduces-digital-diplomas) digital certificates based on this standard.","Build apps that issue and verify blockchain-based credentials for academic credentials, professional certifications, workforce development, and civic records.",https://www.blockcerts.org/,,project,,,Blockcerts,,,,,,,,2016,https://github.com/blockchain-certificates,https://twitter.com/blockcerts,,,,,,,,,,,http://community.blockcerts.org/
Blockcerts,Blockcerts,,,,,,,,,Introduction,"Blockcerts is an open standard for building apps that issue and verify blockchain-based official records. These may include certificates for civic records, academic credentials, professional licenses, workforce development, and more.<br><brBlockcerts consists of open-source libraries, tools, and mobile apps enabling a decentralized, standards-based, recipient-centric ecosystem, enabling trustless verification through blockchain technologies.<br><br>Blockcerts uses and encourages consolidation on open standards. Blockcerts is committed to self-sovereign identity of all participants, and enabling recipient control of their claims through easy-to-use tools such as the certificate wallet (mobile app). Blockcerts is also committed to availability of credentials, without single points of failure.","Build apps that issue and verify blockchain-based credentials for academic credentials, professional certifications, workforce development, and civic records.",https://www.blockcerts.org/guide/,https://www.blockcerts.org/assets/img/pictures/blockcerts.png,page,,,Blockcerts,,,,,,,,,,,,,,,,,,,,,
Blockcerts,Blockcerts,,,,,,,,,Introduction,"Blockcerts is an open standard for building apps that issue and verify blockchain-based official records. These may include certificates for civic records, academic credentials, professional licenses, workforce development, and more.<br><br>Blockcerts consists of open-source libraries, tools, and mobile apps enabling a decentralized, standards-based, recipient-centric ecosystem, enabling trustless verification through blockchain technologies.<br><br>Blockcerts uses and encourages consolidation on open standards. Blockcerts is committed to self-sovereign identity of all participants, and enabling recipient control of their claims through easy-to-use tools such as the certificate wallet (mobile app). Blockcerts is also committed to availability of credentials, without single points of failure.","Build apps that issue and verify blockchain-based credentials for academic credentials, professional certifications, workforce development, and civic records.",https://www.blockcerts.org/guide/,https://www.blockcerts.org/assets/img/pictures/blockcerts.png,page,,,Blockcerts,,,,,,,,,,,,,,,,,,,,,
Blockcerts,MIT Media Lab,,,,,,,,,Blockcerts — An Open Infrastructure for Academic Credentials on the Blockchain,"What would an academic degree look like if it was designed today? Or a professional certificate? These are questions we have been working on over the last year, and we are excited to announce the…",,https://medium.com/mit-media-lab/blockcerts-an-open-infrastructure-for-academic-credentials-on-the-blockchain-899a6b880b2f,https://miro.medium.com/v2/resize:fit:1200/1*zrTpMx8dQKK_XAJLtLdOGg.png,Post,,,Blockcerts,,,,,,,,2016-10-25,,,,,,,,,,,,,
Blockcerts,Learning Machine,,,Natalie Smolenski,,,,,,Top 10 Reasons to Use Blockcerts,The open standard for issuing blockchain-based records is your easiest bet for creating records that remain verifiable for a lifetime.,"With more blockchain credentialing solutions popping up every week, it can be difficult to navigate the landscape of offerings. How do you decide which blockchain credentialing framework to use? One…",https://medium.com/learning-machine-blog/top-10-reasons-to-use-blockcerts-ec7d29f2712c,,Post,,,Blockcerts,,,,,,,,2018-05-19,,,,,,,,,,,,,
Blockcerts,SSIMeetup,,https://www.slideshare.net/SSIMeetup/blockcerts-the-open-standard-for-blockchain-credentials,,,,,,,Blockcerts: The Open Standard for Blockchain Credentials,"<center><iframe src=""//www.slideshare.net/slideshow/embed_code/key/rVC25i8FzeTPiw"" 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</center>","Anthony Ronning, an engineer behind Blockcerts and backend dev at Learning Machine and Daniel Paramo, co-founder of swys and advisor at Xertify, explains how Blockcerts started, deep dive on how Blockcerts work, which institutions are implementing this solution and what companies have made a solution for the adoption of this standard. We will review the current Blockcerts roadmap and their pros and cons. What considerations do we need to take when developing a solution around Blockcerts?",https://ssimeetup.org/blockcerts-open-standard-blockchain-credentials-daniel-paramo-anthony-ronning-webinar-39/,,Presentation,,,Blockcerts,,,,,,,,2019-10-12,,,,,,,,,,,,,
Blockcerts,WebofTrustInfo,,,,,,,,rwot5-boston,A Decentralized Approach to Blockcerts Credential Revocation,"The initial release of the Blockcerts standard and reference implementation described only one revocation mechanism, the issuer-hosted revocation list approach also used by Open Badges. This has known limitations, including: centralization, single point of failure, and inability for a recipient to revoke. Other approaches to revocation were considered, but none were technically or economically feasible at the time given the project goals, including Bitcoin blockchain anchoring, low overhead, and minimal cost.",,https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/final-documents/blockcerts-revocation.md,,Paper,,,Blockcerts,,,,,,,,2018-02-09,,,,,,,,,,,,,
Blockcerts,WebofTrustInfo,,https://community.blockcerts.org/t/blockcerts-v3-proposal-verifiable-credentials-decentralized-identifiers/2221,,,,,,rwot9-prague,Blockcerts V3 Proposal - Verifiable Credentials & Decentralized Identifiers,"As the standards around Verifable Credentials are starting to take form, different favors of ""verifiable credentials-like"" data structures need to make necessary changes to leverage on the rulesets outlined and constantly reviewed by knowledgeable communities such as the W3C. The purpose of this paper is to identify all of the changes needed for Blockcerts to comply with the Verifiable Credentials (VCs) and Decentralized Identifers (DIDs) standards and to expand upon the additional benefits of using a blockchain in combination with Verifiable Credentials. This paper is meant to act as an explainer in which a formal specification can be created. This paper proposes multiple implementation options for several properties. The intention is that we can engage the Blockcerts / Verifiable Credential communities and see what fts best.","Some of you may already know and/or have been following along. Over the last few months, since Rebooting the Web of Trust 9, we have been coming up with drafts and proposals for Blockcerts V3 for the al&hellip;",https://nbviewer.jupyter.org/github/WebOfTrustInfo/rwot9-prague/blob/master/final-documents/BlockcertsV3.pdf,,Paper,,,Blockcerts,,,,,,,,2019-12-19,https://github.com/blockchain-certificates/cert-issuer/tree/v3,,,,,,,,,,,,https://community.blockcerts.org/t/blockcerts-v3-proposal-verifiable-credentials-decentralized-identifiers/2221
Blockcerts,Learning Machine,,,,,,,,,Badges and Blockcerts,"In education and workforce development, its important to understand the differences between digital credential formats and how to combine them for greatest impact [...]<br><br2011 saw the birth of Open Badges, which digitally and visually convey the achievement of a specific skill. Similar to the Scouts movement, which uses a small fabric symbol to represent specific achievements, digital badges were designed to convey a singular achievement through a digital image and a hosted set of data. Initially spearheaded by the Mozilla Foundation, the Open Badges standard is now maintained by the IMS Global Learning Consortium, ensuring interoperability between platforms. [...]<br><br>In response to the desire for high-stakes credentials in a digital format, the development of Blockcerts began in 2015 as part of a project by the MIT Media Lab.",,https://www.learningmachine.com/badges-and-blockcerts/,https://www.learningmachine.com/wp-content/uploads/2019/01/Screen-Shot-2019-01-29-at-9.54.40-AM.png,page,,,Open Badges,,,,,,,,2018-12-13,,,,,,,,,,,,,
Blockcerts,Learning Machine,,,,,,,,,Badges and Blockcerts,"In education and workforce development, its important to understand the differences between digital credential formats and how to combine them for greatest impact [...]<br><br>2011 saw the birth of Open Badges, which digitally and visually convey the achievement of a specific skill. Similar to the Scouts movement, which uses a small fabric symbol to represent specific achievements, digital badges were designed to convey a singular achievement through a digital image and a hosted set of data. Initially spearheaded by the Mozilla Foundation, the Open Badges standard is now maintained by the IMS Global Learning Consortium, ensuring interoperability between platforms. [...]<br><br>In response to the desire for high-stakes credentials in a digital format, the development of Blockcerts began in 2015 as part of a project by the MIT Media Lab.",,https://www.learningmachine.com/badges-and-blockcerts/,https://www.learningmachine.com/wp-content/uploads/2019/01/Screen-Shot-2019-01-29-at-9.54.40-AM.png,page,,,Open Badges,,,,,,,,2018-12-13,,,,,,,,,,,,,
Blockcerts,WebofTrustInfo,,,,Open Badges,,,,rwot6-santabarbera,Open Badges are Verifable Credentials,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.,,https://nbviewer.jupyter.org/github/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/open-badges-are-verifiable-credentials.pdf,,Paper,,,Open Badges,,,,,,,,2018-06-22,,,,,,,,,,,,,
Blockcerts,Draftin,,,,Open Badges,,,,,OPEN BADGES ON THE BLOCKCHAIN,"This document gives an overview of the status, interesting companies and people regarding Verifiable Open Badges on the Blockchain.",,https://draftin.com/documents/1138961?token=hQ5q0mCHizZum8-pkDFYUZr4YFYOWMN01BPT-5uX00hAaGxYOAlgAlhyenat76hjNpTCs-CMWPI38KWn_omp0Oc,,Paper,,,Open Badges,,,,,,,,2019-07-19,,,,,,,,,,,,,
Blockcerts,FSMB,,,,,,,,,"Healthcare and Digital Credentials: Technical, Legal, and Regulatory Considerations","Credentials expressed through a trusted identity framework can be accorded a higher value within a social interaction due to the underlying assumption that someone within the system is managing the creation and transfer of these credentials. Within any high functioning identity framework specifications, rules, and agreements based in both technological capacity and social need are necessary to ensure that the level of trustworthiness required by participants in the identity system and the community relying on the services offered by the identity system is met.",,https://www.fsmb.org/siteassets/digital-credentials/digital-credentials-report-june-2019.pdf,,Report,,,Literature,,,,,,,,2019-06,,,,,,,,,,,,,
@ -474,7 +474,7 @@ Blockcerts,Blockcerts,,,,,,,,,An Android app for Blockcerts.,Blockcerts Android
Blockcerts,Blockcerts,,,,,,,,,"An iOS wallet for viewing, validating, and sharing certs",This repository contains the core modules used to implement Blockcerts functionality in iOS.,,https://github.com/blockchain-certificates/BlockcertsFramework-iOS,,Code,,,Development; Apps,,,,,,,,2022-09-19,,,,,,,,,,,,,
Blockcerts,Blockcerts,,,,,,,,,An iOS wallet for Blockcerts.,Blockcerts mobile app for iOS to receive and share certificates that are verifiable via the blockchain,,https://github.com/blockchain-certificates/wallet-iOS,,Code,,,Development; Apps,,,,,,,,2022-02-17,,,,,,,,,,,,,
Linked Data,TwoBitHistory,,,,,,,,,Whatever Happened to the Semantic Web?,"In 2001, Tim Berners-Lee, inventor of the World Wide Web, published an article in Scientific American. Berners-Lee, along with two other researchers, Ora Lassila and James Hendler, wanted to give the world a preview of the revolutionary new changes they saw coming to the web. Since its introduction only a decade before, the web had fast become the worlds best means for sharing documents with other people. Now, the authors promised, the web would evolve to encompass not just documents but every kind of data one could imagine",,https://twobithistory.org/2018/05/27/semantic-web.html,,Post,,,Getting Started,,,,,,,,2018-05-27,,,,,,,,,,,,,
Linked Data,W3C,,,,,,,,,LinkedData - W3C Wiki,"The idea behind these principles is on the one hand side, to use standards for the representation and the access to data on the Web. On the other hand, the principles propagate to set hyperlinks between data from different sources. These hyperlinks connect all Linked Data into a single global data graph, similar as the hyperlinks on the classic Web connect all HTML documents into a single global information space. Thus, LinkedData is to spreadsheets and databases what the Web of hypertext documents is to word processor files. The Linked Open Data cloud diagramms give an overview of the linked data sets that are available on the Web.",,https://www.w3.org/wiki/LinkedData,https://www.w3.org/wiki/resources/assets/poweredby_mediawiki_88x31.png,entry,,,Getting Started,,,,,,,,2016-08-01,,,,,,,,,,,,,
Linked Data,W3C,,,,,,,,,LinkedData - W3C Wiki,"The idea behind these principles is on the one hand side, to use standards for the representation and the access to data on the Web. On the other hand, the principles propagate to set hyperlinks between data from different sources. These hyperlinks connect all Linked Data into a single global data graph, similar as the hyperlinks on the classic Web connect all HTML documents into a single global information space. Thus, LinkedData is to spreadsheets and databases what the Web of hypertext documents is to word processor files. The Linked Open Data cloud diagramms give an overview of the linked data sets that are available on the Web.",,https://www.w3.org/wiki/LinkedData,,entry,,,Getting Started,,,,,,,,2016-08-01,,,,,,,,,,,,,
Linked Data,W3C,,,Tim Berners Lee,,,,,,Linked Data - Design Issues,"The Semantic Web isn't just about putting data on the web. It is about making links, so that a person or machine can explore the web of data. With linked data, when you have some of it, you can find other, related, data.<br>Like the web of hypertext, the web of data is constructed with documents on the web. However, unlike the web of hypertext, where links are relationships anchors in hypertext documents written in HTML, for data they links between arbitrary things described by RDF,. The URIs identify any kind of object or concept. But for HTML or RDF, the same expectations apply to make the web grow:<br>- Use URIs as names for things<br>- Use HTTP URIs so that people can look up those names.<br>- When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL)<br>- Include links to other URIs. so that they can discover more things.",,https://www.w3.org/DesignIssues/LinkedData,https://www.w3.org/DesignIssues/diagrams/lod/597992118v2_350x350_Back.jpg,page,,,Getting Started,,,,,,,,2006-07-27,,,,,,,,,,,,,
Linked Data,Semantalytics,,,,,,,,,Awesome Semantic Web,A curated list of various semantic web and linked data resources.,,https://github.com/semantalytics/awesome-semantic-web,,list,,,Getting Started,,,,,,,,2023-04-26,,,,,,,,,,,,,
Linked Data,Nandana Mihindukulasooriya,,,,,,,,,Awesome Linked Data,A list of tools for publishing and consuming Linked Data.,,https://github.com/nandana/awesome-linkeddata,,list,,,Getting Started,,,,,,,,2017-03-07,,,,,,,,,,,,,
@ -484,11 +484,11 @@ Linked Data,Personal,,,Kerstin Forsberg,,,,,,Linked Data for Enterprises,Keeping
Linked Data,Read-Write Linked Data,,,,,,,,,Examples in the Wild << Pretty Awesome List,"dokieli is a decentralised article authoring, annotation, and social notification tool which works from Web browsers. It is built with the following principles in mind: freedom of expression, decentralisation, interoperability, and accessibility.",,https://github.com/linkeddata/dokieli/wiki,,wiki,,,Getting Started,,,,,,,,2019-07-03,,,,,,,,,,,,,
Linked Data,Solid,,,,,,,,,Understanding Linked Data slide deck (in Remark.js format),A slide deck introduction to Linked Data aimed at developers.,,https://github.com/solid/understanding-linked-data,,Presentation,,,Getting Started,,,,,,,,2019-10-03,,,,,,,,,,,,,
Linked Data,LinkedDataTools,,,,,,,,,Introducing Linked Data And The Semantic Web,"What is Linked Data and the Semantic Web and what is all the hype about? Principally, the Semantic Web is a Web 3.0 web technology - a way of linking data between systems or entities that allows for rich, self-describing interrelations of data available across the globe on the web.",,http://www.linkeddatatools.com/semantic-web-basics,https://2mye7d.n3cdn1.secureserver.net/wp-content/uploads/2023/02/semantic-web-learning-curve.png,page,,,Getting Started,,,,,,,,2011-06-12,,,,,,,,,,,,,
Linked Data,Personal,,,Ruben Verborgh,,,,,,Designing a Linked Data developer experience,"Making decentralized Web app development fun<br>While the Semantic Web community was fighting its own internal battles, we failed to gain traction with the people who build apps that are actually used: front-end developers. Ironically, Semantic Web enthusiasts have failed to...",,https://ruben.verborgh.org/blog/2018/12/28/designing-a-linked-data-developer-experience/,https://ruben.verborgh.org/images/blog/front-end-devs.jpg,Post,,,Main,,,,,,,,2018-12-28,,,,,,,,,,,,,
Linked Data,Personal,,,Ruben Verborgh,,,,,,Designing a Linked Data developer experience,"Making decentralized Web app development fun<br>While the Semantic Web community was fighting its own internal battles, we failed to gain traction with the people who build apps that are actually used: front-end developers. Ironically, Semantic Web enthusiasts have failed to...",,https://ruben.verborgh.org/blog/2018/12/28/designing-a-linked-data-developer-experience/,,Post,,,Main,,,,,,,,2018-12-28,,,,,,,,,,,,,
Linked Data,WebofTrustInfo,,,"Christopher Lemmer Webber, Mark S. Miller",,,,,rwot05-boston,Linked Data Capabilities,"Linked Data Signatures enable a method of asserting the integrity of linked data documents that are passed throughout the web. The object capability model is a powerful system for ensuring the security of computing systems. In this paper, we explore layering an object capability model on top of Linked Data Signatures via chains of signed proclamations. fn:1 We call this system ""Linked Data Capabilities"", or ""ld-ocap"" for short.",,https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/final-documents/lds-ocap.md,,Paper,,,Main,,,,,,,,2022-12-28,,,,,,,,,,,,,
Linked Data,WebofTrustInfo,,,,,,,,rwot3-sf,Identity as Linked Data on Immutable Ledgers,"Content creators on the Web are getting a raw deal. They get a fraction of a cent for an ad played on YouTube, and nothing on Facebook, for filling these sites with traffic-driving content. Its hard to make a living when youre a creative. Licensing is hard; the user experience is bad, so lawyers and middlemen extract the most value. In the music industry, more money flows into the pockets of distributors than creatives. Consumers are often happy to pay for their content. Instead, they're forced to sit through ads.",,https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/identity-as-linked-data-on-immutable-ledgers.md,,Paper,,,Main,,,,,,,,2016-10-17,,,,,,,,,,,,,
Linked Data,WebofTrustInfo,,,"Manu Sporny, Harlan Wood, Noah Thorp, Wayne Vaughn, Christopher Allen, Jason Bukowski, and Dave Longley",,,,,rwot3-sf,Blockchain Extensions for Linked Data Signatures,"The term Linked Data is used to describe a recommended best practice for exposing, sharing, and connecting information on the Web using standards, such as URLs, to identify things and their properties. When information is presented as Linked Data, other related information can be easily discovered and new information can be easily linked to it. Linked Data is extensible in a decentralized way, greatly reducing barriers to large scale integration.<br>With the increase in usage of Linked Data for a variety of applications, there is a need to be able to verify the authenticity and integrity of Linked Data documents. The Linked Data Signatures specification added authentication and integrity protection to linked data documents through the use of public/private key cryptography without sacrificing Linked Data features such as extensibility and composability.",,https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/blockchain-extensions-for-linked-data-signatures.md,,Paper,,,Main,,,,,,,,2016-10-30,,,,,,,,,,,,,
Linked Data,WebofTrustInfo,,,"Ganesh Annan, Kim Hamilton Duffy",,,,,rwot7-toronto,Resource Integrity Proofs,"Cryptographic linking provides discoverability, integrity, and scheme agility<brContributors: Manu Sporny, Dave Longley, David Lehn, and Bohdan Andriyiv<br>Currently, the Web provides a simple yet powerful mechanism for the dissemination of information via links. Unfortunately, there is no generalized mechanism that enables verifying that a fetched resource has been delivered without unexpected manipulation. Would it be possible to create an extensible and multipurpose cryptographic link that provides discoverability, integrity, and scheme agility?<br>Cryptographic linking solutions today have yet to provide a generalized mechanism for creating tamper-evident links. The Subresource Integrity standard limits this guarantee to script and link resources loaded on Web pages via the use of HTML attributes. IPFS provides a verification mechanism that is constrained to hash-based, content-addressable links, with no ability to complete content negotiation. RFC6920 proposes another mechanism that cannot be applied to existing links: it recommends the use of named information hashes and a resolution method that creates a content addressable URL [1]. Resource Integrity Proofs incorporates ideas from these standards and solutions to provide a new data format for cryptographic links that is fit for the open world.",,https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/resource-integrity-proofs.md,,Paper,,,Main,,,,,,,,2018-12-12,,,,,,,,,,,,,
Linked Data,WebofTrustInfo,,,"Ganesh Annan, Kim Hamilton Duffy",,,,,rwot7-toronto,Resource Integrity Proofs,"Cryptographic linking provides discoverability, integrity, and scheme agility<br>Contributors: Manu Sporny, Dave Longley, David Lehn, and Bohdan Andriyiv<br>Currently, the Web provides a simple yet powerful mechanism for the dissemination of information via links. Unfortunately, there is no generalized mechanism that enables verifying that a fetched resource has been delivered without unexpected manipulation. Would it be possible to create an extensible and multipurpose cryptographic link that provides discoverability, integrity, and scheme agility?<br>Cryptographic linking solutions today have yet to provide a generalized mechanism for creating tamper-evident links. The Subresource Integrity standard limits this guarantee to script and link resources loaded on Web pages via the use of HTML attributes. IPFS provides a verification mechanism that is constrained to hash-based, content-addressable links, with no ability to complete content negotiation. RFC6920 proposes another mechanism that cannot be applied to existing links: it recommends the use of named information hashes and a resolution method that creates a content addressable URL [1]. Resource Integrity Proofs incorporates ideas from these standards and solutions to provide a new data format for cryptographic links that is fit for the open world.",,https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/resource-integrity-proofs.md,,Paper,,,Main,,,,,,,,2018-12-12,,,,,,,,,,,,,
Linked Data,WebofTrustInfo,,,,,,,,rwot6-santabarbera,Recent happenings with Linked Data Capabilities,"Veres One's architecture has been adjusted to take full advantage of Linked Data Capabilities as its primary mechanism for granting authority to perform operations on the ledger as well as on DID Documents. permission to update key materials can be conditionally handed out to an entity (or entities) and later revoked if deemed appropriate using Linked Data Capabilities' design.<br>As for ledger updates, Accelerators also make use of Linked Data Capabilities. To prevent spamming the ledger, the costs of an update must somehow be accounted for. The traditional way to do this on a blockchain is to use proof of work, and this is also an option in Veres One, but for those use cases where expending time and energy on proof of work is less desirable users can use an ""accelerator"".<br>An accelerator is an entity that has been granted a capability to perform updates on the ledger more quickly. Accelerators may likewise take advantage of Linked Data Capabilities' support for delegation, with or without caveats.",,https://github.com/WebOfTrustInfo/rwot6-santabarbara/blob/master/topics-and-advance-readings/ld-ocap-recent-happenings.md,,Paper,,,Main,,,,,,,,2018-03-02,,,,,,,,,,,,,
Linked Data,WebofTrustInfo,,,,,,,,rwot4-paris,LD Signature Format Alignment,"The goal of the ""LD Signature Format Alignment"" Working Group at Rebooting the Web of Trust IV was to investigate the feasibility and impact of the proposed 2017 RSA Signature Suite spec, which brings JSON-LD signatures into alignment with the JOSE JSON Web Signature (JWS) standards.The 2017 RSA Signature Suite is based on RFC 7797, the JSON Web Signature (JWS) Unencoded Payload Option specifcation. This approach avoids past concerns about JWT raised in the LD signature adopters, including:•Increased space consumption associated withbase-64 encoding.•Difculty of nesting or chaining signatures, leading to data duplication.•Use of a format that is not a JSON object, preventing ability to rely exclusively on a JSON document-based storage engine (whilepreserving the signature)",,https://nbviewer.jupyter.org/github/WebOfTrustInfo/rwot4-paris/blob/master/final-documents/ld-signatures.pdf,,Paper,,,Main,,,,,,,,2017-08-18,,,,,,,,,,,,,
Linked Data,CCG,,,,,,,,,Authorization Capabilities for Linked Data v0.3,"Authorization Capabilities for Linked Data (ZCAP-LD for short) provides a secure way for linked data systems to grant and express authority utilizing the object capability model. Capabilities are represented as linked data objects which are signed with Linked Data Proofs. ZCAP-LD supports delegating authority to other entities on the network by chaining together capability documents. ""Caveats"" may be attached to capability documents which may be used to restrict the scope of their use, for example to restrict the actions which may be used or providing a mechanism by which the capability may be later revoked.",,https://w3c-ccg.github.io/zcap-spec/,,Specification,,,Main,,,,,,,Credentials Community Group,2023-01-22,https://github.com/w3c-ccg/zcap-spec,,,,,,,,,,,,
@ -497,26 +497,26 @@ Linked Data,WebofTrustInfo,,,,,,,,,JSON-LD Signatures with JSON Web Signatures,"
Linked Data,CCG,,,,,,,,,Linked Data Keys Registry,This repository contains the Linked Data Cryptographic Suite Registry which is a list of all known Linked Data cryptographic suites and their current level of maturity.,,https://github.com/w3c-ccg/ld-cryptosuite-registry,,registry,,,Implementation,,,,,,,Credentials Community Group,2020-12-29,,,,,,,,,,,,,
Linked Data,DigitalBazaar,,,,,,,,,Linked Data Capabilities reference implementation,JavaScript reference implementation for Authorization Capabilities.,,https://github.com/digitalbazaar/ocapld.js,,Code,,,Implementation,,,,,,,,2023-01-14,,,,,,,,,,,,,
Linked Data,W3C,,,,,,,,,RDF AND JSON-LD UseCases,This wiki page strive to address one of many question about use of RDF vs JSON-LD to store linked data. This page attempts to provide a general introduction of both the technologies and provide suitability analysis of various kind of applications to use either technology.,,https://www.w3.org/2013/dwbp/wiki/RDF_AND_JSON-LD_UseCases,https://www.w3.org/2013/dwbp/wiki/images/thumb/1/17/RDFSerialization-formats.png/800px-RDFSerialization-formats.png,page,,,RDF,,,,,,,,2014-09-15,,,,,,,,,,,,,
Linked Data,W3C,,,,,,,,,Comparison of RDFJS libraries,This is a comparison of JavaScript libraries for working with RDF.,,https://www.w3.org/community/rdfjs/wiki/Comparison_of_RDFJS_libraries,https://www.w3.org/community/rdfjs/wiki/resources/assets/poweredby_mediawiki_88x31.png,entry,,,RDF,,,,,,,,2019-01-18,,,,,,,,,,,,,
Linked Data,W3C,,,,,,,,,Comparison of RDFJS libraries,This is a comparison of JavaScript libraries for working with RDF.,,https://www.w3.org/community/rdfjs/wiki/Comparison_of_RDFJS_libraries,,entry,,,RDF,,,,,,,,2019-01-18,,,,,,,,,,,,,
Linked Data,W3C,,,,,,,,,RDF.js: The new RDF and Linked Data JavaScript library,"A diverse web requires decentralized data storage and maintenance. According to MITs Tim Berners-Lee, “it is about making links, so that a person or machine can explore the web of data. With Linked Data, when you have some of it, you can find other, related, data”.<br><br>Zazukos CTO Thomas Bergwinkl adds that “Linked Data is built on top of the web stack and the programming language of the web is JavaScript. It is crucial for Web Developers to have access to well-designed JavaScript libraries to work with RDF and Linked Data”.<br><br>The RDFJS W3C Community Group did a tremendous job in defining a standard to represent Linked Data in JavaScript. Several individuals and groups started to implement the RDFJS specification.",,https://www.w3.org/community/rdfjs/2018/04/23/rdf-js-the-new-rdf-and-linked-data-javascript-library/,,Post,,,RDF,,,,,,,,2018-04-23,,,,,,,,,,,,,
Linked Data,RCH Working Group,,,,CCG,,,,,RDF Dataset Canonicalization,"RDF [RDF-CONCEPTS] describes a graph-based data model for making claims about the world and provides the foundation for reasoning upon that graph of information. At times, it becomes necessary to compare the differences between sets of graphs, digitally sign them, or generate short identifiers for graphs via hashing algorithms. This document outlines an algorithm for normalizing RDF datasets such that these operations can be performed.",,https://w3c.github.io/rdf-canon/spec/,,Report,,,RDF,,,,,,,,2023-05-24,https://github.com/w3c/rdf-canon/,,,,,,,,,,,,
GS1,GS1,,,,,,,,,GS1 - How we got here,"Since 1973, we have opened offices in over 110 countries and amassed more than 2 million members using supply chain standards that make business easier. Learn about key dates in our history.<br- 1973: The barcode standard is agreed<br- 1974: The first barcode is scanned<br- 1977: The GS1 system is launched<br- 1983: Barcodes are used on wholesale multi-packs<br- 1989: GS1 moves beyond barcodes<br - With wide area networks making an impact on supply chains, we create our first international standard for electronic data interchange.<br- 1990: Responsibilities grow<br - The US and international arms of GS1 come together formally, creating a single organisation with a presence in 45 countries.<br- 1995: First healthcare standards created<br- 1999: The GS1 DataBar arrives<br- 2000: 90th local office opens<br - In just ten years, we double the number of countries in which we have a local presence.<br- 2002: Global standards forum launched<br - Our Global Standards Management Process is launched. This global forum gives GS1 members one place to discuss standards.<br- 2004: The first standard for RFID is created<br- 2007: GS1 enters the business-to-consumer world<br - As ecommerce grows, we begin to create open standards that give consumers direct access to key product information.<br- 2013: A 40-year celebration<br - With a presence in over 100 countries and more than a million members, we celebrate 40 years of the global language of business.",,https://www.gs1.org/about/how-we-got-here,https://gs1go2.azureedge.net/cdn/ff/72KV_kX-aZGtwUlmD5KjuSzFpY-TPv1WkMRH0_CHCVE/1675165342/public/2023-01/1973.png,page,,,Main,,,,,,,,2023-04-25,,,,,,,,,,,,,
GS1,GS1,,,,,,,,,Standards development,"A neutral participant, GS1 facilitates dialogue and the development of standards-based solutions among business and technical people from nearly sixty countries. Industries represented include retail and consumer goods, fresh foods, healthcare, transport and logistics, governments and many more.<br><br>The GSMP (Global Standards Management Process) is a community-based forum for businesses facing similar problems to work together and develop standards-based solutions. Standards created by industry, for industry.","The GSMP (Global Standards Management Process) is a community-based forum for businesses facing similar problems to work together and develop standards-based solutions. Standards created by industry, for industry.",https://www.gs1.org/standards/development,https://gs1go2.azureedge.net/cdn/ff/Vts5yHWR2YqcWFYp2bXZSKYgfHhlDZVDNC-giMBOFYs/1635150532/public/2021-06/thumb_video_standards_0.png,page,,,Main,,,,,,,,2023-04-25,,,,,,,,,,,,,
GS1,GS1,,,,,,,,,How we develop standards,Our standards development team guide the regular upgrading of our standards through a document development life cycle whose rules everyone agrees to. The Global Standards Management Process (GSMP) enables us to reach consensus around the creation and adoption of new standards smoothly and rapidly!,We develop our global supply chain standards in partnership with the industry experts and business teams who actually use them. Find out how we do it.,https://www.gs1.org/how-we-develop-standards,https://gs1go2.azureedge.net/cdn/ff/j98vq8ZwoGIDZaJf1YJMp_IQ0Vxr7IlpF5CWqXSrmGE/1639585169/public/2021-12/why-join-workgroup.png,page,,,Main,,,,,,,,2023-04-27,,,,,,,,,,,,,
GS1,GS1,,,,,,,,,GS1 - How we got here,"Since 1973, we have opened offices in over 110 countries and amassed more than 2 million members using supply chain standards that make business easier. Learn about key dates in our history.<br>- 1973: The barcode standard is agreed<br>- 1974: The first barcode is scanned<br>- 1977: The GS1 system is launched<br>- 1983: Barcodes are used on wholesale multi-packs<br>- 1989: GS1 moves beyond barcodes<br> - With wide area networks making an impact on supply chains, we create our first international standard for electronic data interchange.<br>- 1990: Responsibilities grow<br> - The US and international arms of GS1 come together formally, creating a single organisation with a presence in 45 countries.<br>- 1995: First healthcare standards created<br>- 1999: The GS1 DataBar arrives<br>- 2000: 90th local office opens<br> - In just ten years, we double the number of countries in which we have a local presence.<br>- 2002: Global standards forum launched<br> - Our Global Standards Management Process is launched. This global forum gives GS1 members one place to discuss standards.<br>- 2004: The first standard for RFID is created<br>- 2007: GS1 enters the business-to-consumer world<br> - As ecommerce grows, we begin to create open standards that give consumers direct access to key product information.<br>- 2013: A 40-year celebration<br> - With a presence in over 100 countries and more than a million members, we celebrate 40 years of the global language of business.",,https://www.gs1.org/about/how-we-got-here,,page,,,Main,,,,,,,,2023-04-25,,,,,,,,,,,,,
GS1,GS1,,,,,,,,,Standards development,"A neutral participant, GS1 facilitates dialogue and the development of standards-based solutions among business and technical people from nearly sixty countries. Industries represented include retail and consumer goods, fresh foods, healthcare, transport and logistics, governments and many more.<br><br>The GSMP (Global Standards Management Process) is a community-based forum for businesses facing similar problems to work together and develop standards-based solutions. Standards created by industry, for industry.","The GSMP (Global Standards Management Process) is a community-based forum for businesses facing similar problems to work together and develop standards-based solutions. Standards created by industry, for industry.",https://www.gs1.org/standards/development,,page,,,Main,,,,,,,,2023-04-25,,,,,,,,,,,,,
GS1,GS1,,,,,,,,,How we develop standards,Our standards development team guide the regular upgrading of our standards through a document development life cycle whose rules everyone agrees to. The Global Standards Management Process (GSMP) enables us to reach consensus around the creation and adoption of new standards smoothly and rapidly!,We develop our global supply chain standards in partnership with the industry experts and business teams who actually use them. Find out how we do it.,https://www.gs1.org/how-we-develop-standards,,page,,,Main,,,,,,,,2023-04-27,,,,,,,,,,,,,
GS1,IDCommons,,,,,,,,IIW30,GS1's decentralized approach to resolving identifiers over HTTPS,"Slides are at http://docs.google.com/presentation/d/1fLDETcghxxRfac7mDCTGpqktaVnn9bjl/edit# General principles paper is at http://gs1.github.io/DigitalLinkDocs/principles/<br><br>GS1 DIgital Link standard makes the standard product Identifier - the “UPC” code web resolvable. Making it do more than go beep at the check out.<br><br>SSI / DIDs “not central point of issuance, no single point of failure”...but we can meet those requirements with persistent identifiers with centralized federation… centralized + delegation can work.",,https://iiw.idcommons.net/GS1%27s_decentralized_approach_to_resolving_identifiers_over_HTTPS,,Session Notes,,,Main,,,,,,,,2009-06-18,,,,,,,,,,,,,
GS1,IDCommons,,https://gs1.github.io/DigitalLinkDocs/principles/,"Phil Archer, Mark Harrison, Henri Barthel",,,,,IIW30,Decentralized resolution of identifiers with HTTPS,11 Transferable Principles from GS1 Digital Link,,https://docs.google.com/presentation/d/1fLDETcghxxRfac7mDCTGpqktaVnn9bjl/edit#slide=id.p1,https://lh3.googleusercontent.com/docs/ADP-6oHa-ouWp6hpdtK-96YC0Ar-fwMZxk26EYXKOlxsExdj5_JUeW6Ee6R6qXgneyJetUEcnuab9B5Cy_d8gxyFxF9-P_AugQ=w1200-h630-p,Presentation,,,Main,,,,,,,,2020-04,,,,,,,,,,,,,
GS1,IDCommons,,https://gs1.github.io/DigitalLinkDocs/principles/,"Phil Archer, Mark Harrison, Henri Barthel",,,,,IIW30,Decentralized resolution of identifiers with HTTPS,11 Transferable Principles from GS1 Digital Link,,https://docs.google.com/presentation/d/1fLDETcghxxRfac7mDCTGpqktaVnn9bjl/edit#slide=id.p1,,Presentation,,,Main,,,,,,,,2020-04,,,,,,,,,,,,,
GS1,GS1,,,,,,,,,GSMP Manual,"The GSMP 4-Step Process is designed to ensure that business needs and requirements are understood before standards and guidelines are developed, and that supporting materials are created afterward. Each step culminates in the completion of one or more outputs, created through a consensus-based process within a working group and with larger consensus confirmed through community review and eBallot.",,https://www.gs1.org/docs/gsmp/GSMP_Manual.pdf,,docs,,,Global Standards Mapping Process,,,,,,,,2022-07,,,,,,,,,,,,,
GS1,GS1,,,,,,,,,Global Data Model (GDM) Governance Manual,"The retail landscape is changing at an unprecedented rate. In this connected world, consumers increasingly rely on product information for purchasing decisions. The purpose of the Global Data Model (GDM) is to simplify and harmonise the exchange of master data. The GDM will identify and define—in a globally consistent way—the set of foundational attributes needed to list/order, move, store and sell a product, both digitally and physically. By harmonising foundational data across the industry around the globe, it will enable an improved consumer experience and reduce complexity by delivering more reliable and complete product information to consumers.",,https://www.gs1.org/sites/default/files/docs/gsmp/gdm_manual_i1_a_2020-03-19.pdf,,docs,,,Global Standards Mapping Process,,,,,,,,2020-03-19,,,,,,,,,,,,,
GS1,GS1,,,,,,,,,GSMP Value Statement,"Are business challenges holding back your companys full potential and growth? You are not alone. Business is easier when you speak the same language as your customers, suppliers and partners. Though we all work in our own way, problems and differences become solutions when we all work together. Thats where GS1 can help.<br><br>The GSMP is a community-based forum for businesses facing similar problems to work together and develop standards-based solutions to address them. Standards created by industry, for industry.",,https://www.gs1.org/sites/default/files/docs/gsmp/gsmp_execsummary.pdf,,docs,,,Global Standards Mapping Process,,,,,,,,2015-10-02,,,,,,,,,,,,,
GS1,GS1,,https://www.gs1.org/standards/development-work-groups,,,,,,,GSMP Data Accuracy SMG,"This processes all maintenance Work Requests for the **[GS1 Package Measurement Rules Standard](https://www.gs1.org/docs/gdsn/3.1/GS1_Package_Measurement_Rules.pdf)** and the **[Package Measurement Rules Implementation Guideline](https://www.gs1.org/sites/default/files/docs/gdsn/GDSN_Pack_Measure_Rules_Implementation_Guide.pdf)**. This group acts as a pool of experts for all Data Accuracy SMG work requests and coordinate with associated Mission Specific groups as defined in the GSMP Manual. The work the Data Accuracy SMG allows our community to increase savings throughout the supply chain by synchronising accurate dimensions and weight data which enables better transportation, logistics and retail shelf planning.",,https://www.gs1.org/standards/development-work-groups#DA,https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png,Working Group,,,Working Groups,,,,,,,,2010-04-15,,,,,,,,,,,,,
GS1,GS1,,https://www.gs1.org/standards/development-work-groups,,,,,,,GSMP Electronic Data Interchange (EDI) SMG,This group maintains and improves [GS1 EDI (Electronic Data Interchange) standards](https://www.gs1.org/standards/edi). Examples of standards maintained in this group (but not limited to) are:<br>- EANCOM®<br>- GS1 XML<br>- GS1 UN/CEFACT XML,,https://www.gs1.org/standards/development-work-groups#EDI,https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png,Working Group,,,Working Groups,,,,,,,,2010-04-15,,,,,,,,,,,,,
GS1,GS1,,https://www.gs1.org/standards/development-work-groups,,,,,,,GSMP Global Master Data (GMD) SMG,"The group maintains and improves the GS1 Master Data standards. Examples of standards maintained in this group (but not limited to) are:<br- [Master Data Standards](https://www.gs1.org/standards/gs1-global-data-model)<br- GS1 Attributes, definitions, code lists, and guidance definitions<br- [GDSN solutions and GDSN Validation Rules](https://www.gs1.org/standards/gdsn)<br- GS1 Web Vocabulary<br- Global Data Model Standards and Attribute Definitions for Business",,https://www.gs1.org/standards/development-work-groups#GMD,https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png,Working Group,,,Working Groups,,,,,,,,2013-12-14,,,,,,,,,,,,,
GS1,GS1,,https://www.gs1.org/standards/development-work-groups,,,,,,,GSMP Global Product Classification (GPC) SMG,"The GPC Standards Maintenance Group maintains and improves the GS1 Global Product Classification (GPC) standard.<br><br>The [GS1 Global Product Classification (GPC) standard](https://www.gs1.org/standards/gpc) helps global trading partners to group products in the same way, everywhere in the world. The resulting common business language is clear and instantly understandable.",,https://www.gs1.org/standards/development-work-groups#GPC,https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png,Working Group,,,Working Groups,,,,,,,,2010-04-15,,,,,,,,,,,,,
GS1,GS1,,https://www.gs1.org/standards/development-work-groups,,,,,,,GSMP Identification SMG,"The ID Standards Maintenance Group maintains and improves the GS1 Automatic Identification and Data Capture (AIDC) standards including Identification Keys, Barcodes, Electronic Product Code, and Radio-Frequency Identification (RFID) standards.<br><br- The GS1 General Specification is the core foundational GS1 standard that defines how identification keys, data attributes and barcodes must be used in business applications<br- GS1 Identification Keys provides companies efficient ways to access and share information about items in their supply chains.<br- Barcodes are symbols that can be scanned electronically using laser or camera-based systems.<br- The Electronic Product Code™ (EPC) is syntax for unique identifiers assigned to physical objects, unit loads, locations, or other identifiable entity playing a role in business operations.<br- GS1's EPC Tag Data Standard (TDS) defines the Electronic Product Code (EPC), including its correspondence to GS1 keys and other existing codes. TDS also specifies data that is carried on Gen 2 RFID tags, including the EPC, User Memory data, control information, and tag manufacture information.",,https://www.gs1.org/standards/development-work-groups#ID,https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png,Working Group,,,Working Groups,,,,,,,,2010-04-15,,,,,,,,,,,,,
GS1,GS1,,,,,,,,,GSMP Traceability and Event Sharing Standards Maintenance Group SMG,"The SMG maintains updates to the GS1 EPCglobal standards that support physical event capture and sharing and the [Global Traceability Standard that supports tracking and tracing of goods](https://www.gs1.org/sites/default/files/docs/gsmp/call_to_action_gtc_h.pdf) and information about the goods. This includes all simple work requests indicated as impacting the event data sharing and traceability standards.<br><br>In addition, the group acts as a pool of experts for all Mission Specific Work Groups that are related to the SMG, as defined in the GSMP Manual in section 3.4. Work Groups.",,https://www.gs1.org/standards/development-work-groups#TRACE_EVENT,https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png,Working Group,,,Working Groups,,,,,,,,2011-05-26,,,,,,,,,,,,,
GS1,GS1,,,,,,,,,GSMP Digital Signature MSWG,"Provide a GS1 standard solution approach to digital signatures. Otherwise, there will be no open, brand owner determined digital signatures to set as an alternative to proprietary digital signature use in barcodes with GS1 standards.",Mission-specific Working Groups (MSWGs) develop new standards,https://www.gs1.org/standards/development-work-groups#DigitalSignature,https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png,Working Group,,,Working Groups,,,,,,,,2020-03-26,,,,,,,,,,,,,
GS1,GS1,,,,,,,,,GSMP EPCIS & CBV 2.0 MSWG,"Since its initial ratification as an EPCglobal standard in 2007 and its subsequent integration into the GS1 “Share” portfolio, EPCIS and its companion standard the Core Business Vocabulary (CBV) have been updated twice (2014 and 2016) and published by ISO (as ISO/IEC 19987 and 19988, respectively). In the meantime, EPCIS and the CBV have gained importance as visibility enablers in various industries. Updates are needed to ensure the relevance of these standards into the coming decades.",Mission-specific Working Groups (MSWGs) develop new standards,https://www.gs1.org/standards/development-work-groups#EPCISCBV,https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png,Working Group,,,Working Groups,,,,,,,,2018-02-19,,,,,,,,,,,,,
GS1,GS1,,,,,,,,,GSMP GLN Modernisation MSWG,"This work group will update the GLN Standards to be more clear and concise and provide guidance to enable industry partners to create, manage, share, and use the GLN to meet their party and location use cases needs in a scalable, standardised manner.",Mission-specific Working Groups (MSWGs) develop new standards,https://www.gs1.org/standards/development-work-groups#GLNM,https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png,Working Group,,,Working Groups,,,,,,,,2022-08-16,,,,,,,,,,,,,
GS1,GS1,,https://www.gs1.org/standards/development-work-groups,,,,,,,GSMP Data Accuracy SMG,"This processes all maintenance Work Requests for the **[GS1 Package Measurement Rules Standard](https://www.gs1.org/docs/gdsn/3.1/GS1_Package_Measurement_Rules.pdf)** and the **[Package Measurement Rules Implementation Guideline](https://www.gs1.org/sites/default/files/docs/gdsn/GDSN_Pack_Measure_Rules_Implementation_Guide.pdf)**. This group acts as a pool of experts for all Data Accuracy SMG work requests and coordinate with associated Mission Specific groups as defined in the GSMP Manual. The work the Data Accuracy SMG allows our community to increase savings throughout the supply chain by synchronising accurate dimensions and weight data which enables better transportation, logistics and retail shelf planning.",,https://www.gs1.org/standards/development-work-groups#DA,,Working Group,,,Working Groups,,,,,,,,2010-04-15,,,,,,,,,,,,,
GS1,GS1,,https://www.gs1.org/standards/development-work-groups,,,,,,,GSMP Electronic Data Interchange (EDI) SMG,This group maintains and improves [GS1 EDI (Electronic Data Interchange) standards](https://www.gs1.org/standards/edi). Examples of standards maintained in this group (but not limited to) are:<br>- EANCOM®<br>- GS1 XML<br>- GS1 UN/CEFACT XML,,https://www.gs1.org/standards/development-work-groups#EDI,,Working Group,,,Working Groups,,,,,,,,2010-04-15,,,,,,,,,,,,,
GS1,GS1,,https://www.gs1.org/standards/development-work-groups,,,,,,,GSMP Global Master Data (GMD) SMG,"The group maintains and improves the GS1 Master Data standards. Examples of standards maintained in this group (but not limited to) are:<br>- [Master Data Standards](https://www.gs1.org/standards/gs1-global-data-model)<br>- GS1 Attributes, definitions, code lists, and guidance definitions<br>- [GDSN solutions and GDSN Validation Rules](https://www.gs1.org/standards/gdsn)<br>- GS1 Web Vocabulary<br>- Global Data Model Standards and Attribute Definitions for Business",,https://www.gs1.org/standards/development-work-groups#GMD,,Working Group,,,Working Groups,,,,,,,,2013-12-14,,,,,,,,,,,,,
GS1,GS1,,https://www.gs1.org/standards/development-work-groups,,,,,,,GSMP Global Product Classification (GPC) SMG,"The GPC Standards Maintenance Group maintains and improves the GS1 Global Product Classification (GPC) standard.<br><br>The [GS1 Global Product Classification (GPC) standard](https://www.gs1.org/standards/gpc) helps global trading partners to group products in the same way, everywhere in the world. The resulting common business language is clear and instantly understandable.",,https://www.gs1.org/standards/development-work-groups#GPC,,Working Group,,,Working Groups,,,,,,,,2010-04-15,,,,,,,,,,,,,
GS1,GS1,,https://www.gs1.org/standards/development-work-groups,,,,,,,GSMP Identification SMG,"The ID Standards Maintenance Group maintains and improves the GS1 Automatic Identification and Data Capture (AIDC) standards including Identification Keys, Barcodes, Electronic Product Code, and Radio-Frequency Identification (RFID) standards.<br><br>- The GS1 General Specification is the core foundational GS1 standard that defines how identification keys, data attributes and barcodes must be used in business applications<br>- GS1 Identification Keys provides companies efficient ways to access and share information about items in their supply chains.<br>- Barcodes are symbols that can be scanned electronically using laser or camera-based systems.<br>- The Electronic Product Code™ (EPC) is syntax for unique identifiers assigned to physical objects, unit loads, locations, or other identifiable entity playing a role in business operations.<br>- GS1's EPC Tag Data Standard (TDS) defines the Electronic Product Code (EPC), including its correspondence to GS1 keys and other existing codes. TDS also specifies data that is carried on Gen 2 RFID tags, including the EPC, User Memory data, control information, and tag manufacture information.",,https://www.gs1.org/standards/development-work-groups#ID,,Working Group,,,Working Groups,,,,,,,,2010-04-15,,,,,,,,,,,,,
GS1,GS1,,,,,,,,,GSMP Traceability and Event Sharing Standards Maintenance Group SMG,"The SMG maintains updates to the GS1 EPCglobal standards that support physical event capture and sharing and the [Global Traceability Standard that supports tracking and tracing of goods](https://www.gs1.org/sites/default/files/docs/gsmp/call_to_action_gtc_h.pdf) and information about the goods. This includes all simple work requests indicated as impacting the event data sharing and traceability standards.<br><br>In addition, the group acts as a pool of experts for all Mission Specific Work Groups that are related to the SMG, as defined in the GSMP Manual in section 3.4. Work Groups.",,https://www.gs1.org/standards/development-work-groups#TRACE_EVENT,,Working Group,,,Working Groups,,,,,,,,2011-05-26,,,,,,,,,,,,,
GS1,GS1,,,,,,,,,GSMP Digital Signature MSWG,"Provide a GS1 standard solution approach to digital signatures. Otherwise, there will be no open, brand owner determined digital signatures to set as an alternative to proprietary digital signature use in barcodes with GS1 standards.",Mission-specific Working Groups (MSWGs) develop new standards,https://www.gs1.org/standards/development-work-groups#DigitalSignature,,Working Group,,,Working Groups,,,,,,,,2020-03-26,,,,,,,,,,,,,
GS1,GS1,,,,,,,,,GSMP EPCIS & CBV 2.0 MSWG,"Since its initial ratification as an EPCglobal standard in 2007 and its subsequent integration into the GS1 “Share” portfolio, EPCIS and its companion standard the Core Business Vocabulary (CBV) have been updated twice (2014 and 2016) and published by ISO (as ISO/IEC 19987 and 19988, respectively). In the meantime, EPCIS and the CBV have gained importance as visibility enablers in various industries. Updates are needed to ensure the relevance of these standards into the coming decades.",Mission-specific Working Groups (MSWGs) develop new standards,https://www.gs1.org/standards/development-work-groups#EPCISCBV,,Working Group,,,Working Groups,,,,,,,,2018-02-19,,,,,,,,,,,,,
GS1,GS1,,,,,,,,,GSMP GLN Modernisation MSWG,"This work group will update the GLN Standards to be more clear and concise and provide guidance to enable industry partners to create, manage, share, and use the GLN to meet their party and location use cases needs in a scalable, standardised manner.",Mission-specific Working Groups (MSWGs) develop new standards,https://www.gs1.org/standards/development-work-groups#GLNM,,Working Group,,,Working Groups,,,,,,,,2022-08-16,,,,,,,,,,,,,
Object Capabilities,Personal,,,Dan Connolly,,,,,,Awesome Object Capabilities and Capability-based Security,Capability-based security enables the concise composition of powerful [patterns](https://github.com/dckc/awesome-ocap/wiki) of cooperation without vulnerability. [What Are Capabilities?](http://habitatchronicles.com/2017/05/what-are-capabilities/) explains in detail.,,https://github.com/dckc/awesome-ocap,,list,,,Main,,,,,,,,2023-03-03,,,,,,,,,,,,,
Object Capabilities,Wikipedia,,,,,,,,,Object Capability Model,"Computer scientist E. Dean Tribble stated that in smart contracts, identity-based access control did not support well dynamically changing permissions, compared to the object-capability model. He analogized the ocap model with giving a valet the key to one's car, without handing over the right to car ownership.<br><br>The structural properties of object capability systems favor modularity in code design and ensure reliable encapsulation in code implementation.<br><br>These structural properties facilitate the analysis of some security properties of an object-capability program or operating system. Some of these in particular, information flow properties can be analyzed at the level of object references and connectivity, independent of any knowledge or analysis of the code that determines the behavior of the objects. As a consequence, these security properties can be established and maintained in the presence of new objects that contain unknown and possibly malicious code.",,https://en.wikipedia.org/wiki/Object-capability_model,,entry,,,Main,,,,,,,,2023-04-12,,,,,,,,,,,,,
Object Capabilities,eRights,,,Mark S. Miller,,,,,,Object Capabilities,"The capability model is, in a sense, the object model taken to its logical extreme. Where object programmers seek modularity -- a decrease in the dependencies between separately thought-out units -- capability programmers seek security, recognizing that required trust is a form of dependency. Object programmers wish to guard against bugs: a bug in module A should not propagate to module B. Capability programmers wish to guard against malice. However, if B is designed to be invulnerable to A's malice, it is likely also invulnerable to A's bugs.",E: Cryptographic Capabilities for Distributed Smart Contracting,http://erights.org/elib/capability/ode/ode-capabilities.html,http://erights.org/elib/capability/ode/images/money.png,page,,,Main,,,,,,,,1998-10-03,,,,,,,,,,,,,
@ -533,48 +533,51 @@ Object Capabilities,WebofTrustInfo,,,"Christopher Lemmer Webber, Mark S. Miller"
DIDComm,CCG Mailing List,,,Daniel Hardman,CCG,,,,,announcement: DIDComm user group,"Now that the [DIDComm v2 spec](https://identity.foundation/didcomm-messaging/spec/) is nearing completion, and there are [robust libraries in multiple programming languages](https://github.com/decentralized-identity/didcomm-messaging#implementations), we are starting a user group to share learnings as we put DIDComm into production. We will organize community resources, produce a handbook, foster application-level protocol creation, maintain the [didcomm.org website](https://didcomm.org) and [repo](https://github.com/decentralized-identity/didcomm.org), and recommend best practices.",,https://lists.w3.org/Archives/Public/public-credentials/2022Jan/0168.html,,Discussion,,,main,,,,,,,,2022-01-20,,,,,,,,,,,,,
DIDComm,CCG Mailing List,,https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0032.html,,CCG,,,,,DIDComm V2 Primer,"1. What it is<br>2. What it does and doesn't do<br>3. Relationship to WACI-DIDComm, CHAPI, OIDC-SIOP<br>4. Versions<br>5. Implementations",,https://lists.w3.org/Archives/Public/public-credentials/2022Apr/att-0032/DIDComm_v2_Primer.pdf,,Discussion,,,main,,,,,,,,2022-04,,,,,,,,,,,,,
DIDComm,didcomm.org,,,,,,,,,didcomm.org,"DIDComm lets people and software use [DIDs](https://www.w3.org/TR/did-core/) to communicate securely and privately over many channels: the web, email, mobile push notifications, QR codes, Bluetooth, message queues, sneakernet, and more.",,https://didcomm.org/,,site,,,main,,,,,,,,,,,,,,,,,,,,,
DIDComm,DIF,,,,,,,,,DIDComm Working Group,"Join this group to contribute to specs that embody a method for secure, private and authenticated message-based communication, where trust is rooted in DIDs and used over a wide variety of transports.",,https://identity.foundation/working-groups/did-comm.html,,Working Group,,,main,,,,,,,,2020-08-18,,,,,,,,,,,,,
DIDComm,DIF,,,"Sam Curren, Tobias Looker, Oliver Terbu, Kyle Den Hartog, Baha Shaaban, Drummond Reed, Steve McCown, Troy Ronda, George Aristy, Vyacheslav Gudkov, Alexander Shcherbakov, Alexander Martynov, Daniel Buchner, Devin Fisher, Orie Steele, Brian Richter, Juan Caballero, @liormargalit, Timo Glastra, Andrew Whitehead, Nader Helmy, Markus Sabadello, Patrick McClurg, Stephen Curran, Daniel Hardman, Moe Jangda","Indicio, TBD, SICPA, Danube Tech, MATTR, Animo, Aviary, Transmute, Centre, Microsoft, Evernym, DSR, SecureKey, ConsenSys, BCGov, Anonyome",,,,,DIDComm Messaging,"DIDComm Messaging enables higher-order protocols that inherit its security, privacy, decentralization, and transport independence. Examples include exchanging verifiable credentials, creating and maintaining relationships, buying and selling, scheduling events, negotiating contracts, voting, presenting tickets for travel, applying to employers or schools or banks, arranging healthcare, and playing games. Like web services atop HTTP, the possibilities are endless; unlike web services atop HTTP, many parties can participate without being clients of a central server, and they can use a mixture of connectivity models and technologies. And these protocols are composable into higher-order workflows without constantly reinventing the way trust and identity transfer across boundaries.",,https://identity.foundation/didcomm-messaging/spec/,https://identity.foundation/didcomm-messaging/collateral/problem-code-structure.png,Specification,,,Spec,,,,,,,DIDComm WG,2022-04-12,,,,,,,,,,,,,
DIDComm,IDCommons,,https://docs.google.com/presentation/d/16HTPyZV_-BtM6EifQpxjivRHKYUeVtOAReUD1eGUA9M/edit?usp=sharing,Sam Curren,,,,,IIW,2D/ Why the Internet Needs DIDComm - IIW,- Enables Verifiable Communication<br - Intelligence at the edge (like email)<br - Protocol Based (like email)<br - Supports HTTP(s) (like APIs) and others as a transport<br - Bluetooth enables Edge to Edge transport<br - Mobile / Offline Friendly (like email)<br - Supports rotating from one DID to another<br - Security independent of transport<br - Protocol development becomes easier and more robust (unlike email),,https://iiw.idcommons.net/2D/_Why_the_Internet_Needs_DIDComm,,Session Notes,,,Explainer,,,,,,,,2021-05-06,,,,,,,,,,,,,
DIDComm,IDCommons,,,Paul Knowles,,,,,IIW,2E/ Decentralized Semantics 101 - IIW,"A digital network must contain authenticable data entry and immutable data<br <br capture elements in order to maintain balance and integrity.<br <br Within the context of a decentralized network, these fundamentals enable a self-regulating system where ...<br <br (1) data inputs can be trusted as having come from an assured source under the control of a governing entity; and<br <br (2) semantic items ensure that the meaning and use of inputted data remains unaltered for all interacting actors.",,https://iiw.idcommons.net/2E/_Decentralized_Semantics_101,,Session Notes,,,Explainer,,,,,,,,2021-05-06,,,,,,,,,,,,,
DIDComm,DIF,DIDComm WG,https://github.com/decentralized-identity/org/blob/master/Org%20documents/WG%20documents/DIF_DIDcomm_WG_Charter_v1.pdf,,,,,,,DID Communications Working Group,"Join this group to contribute to specs that embody a method for secure, private and authenticated message-based communication, where trust is rooted in DIDs and used over a wide variety of transports.",,https://identity.foundation/working-groups/did-comm.html,,Working Group,,,Working Group,,,,,,,,2020-09-18,https://github.com/decentralized-identity/didcomm-messaging/,,,https://dif.groups.io/g/didcomm-wg,,,,,,,,,
DIDComm,DIF,,,,,,,,,DIDComm V2 reaches approved spec status!,"Following the approval of the Decentralized Identifiers (DID) Core Spec by the W3C as an official open web standard, the Decentralized Identity Foundation (DIF) announced the approval of the DIDComm v2 specification. Combined, this represents a major step forward in the acceptance of decentralized identity, one that opens the path to widespread adoption and further development especially with regard to the types of peer-to-peer communication now possible.<br><br>DIDComm defines how messages are composed into application-level protocols and workflows.","DIDComm v2 has now reached DIF Approved Status, joining SideTree as a complete and approved open-source specification.",https://blog.identity.foundation/didcomm-v2/,,Post,,,Working Group,,,,,,,DIDComm WG,2022-07-26,,,,,,,,,,,,,
DIDComm,DIDComm WG,,,"Sam Curren, Tobias Looker, Oliver Terbu, Kyle Den Hartog, Baha Shaaban, Drummond Reed, Steve McCown, Troy Ronda, George Aristy, Vyacheslav Gudkov, Alexander Shcherbakov, Alexander Martynov, Daniel Buchner, Devin Fisher, Orie Steele, Brian Richter, Juan Caballero, @liormargalit, Timo Glastra, Andrew Whitehead, Nader Helmy, Markus Sabadello, Patrick McClurg, Stephen Curran, Daniel Hardman, Moe Jangda","Indicio, TBD, SICPA, Danube Tech, MATTR, Animo, Aviary, Transmute, Centre, Microsoft, Evernym, DSR, SecureKey, ConsenSys, BCGov, Anonyome",,,,,DIDComm Messaging v2.1 Editors Draft,"DIDComm enables higher-order protocols that inherit its security, privacy, decentralization, and transport independence. Examples include exchanging verifiable credentials, creating and maintaining relationships, buying and selling, scheduling events, negotiating contracts, voting, presenting tickets for travel, applying to employers or schools or banks, arranging healthcare, and playing games. Like web services atop HTTP, the possibilities are endless; unlike web services atop HTTP, many parties can participate without being clients of a central server, and they can use a mixture of connectivity models and technologies.",,https://identity.foundation/didcomm-messaging/spec/,,Specification,,,Working Group,,,,,,,,2023-04-26,https://github.com/decentralized-identity/didcomm-messaging,,,,,,,,,,,,
DIDComm,DIDComm WG,,,,,,,,,DIDcomm WG Operating Addendum,We are designing communications protocols specifically for use with the decentralized identifier specification at W3C (https://www.w3.org/TR/did-core/). The DID Core specification and the surrounding family of DID specifications (e.g https://w3c-ccg.github.io/did-resolution/) represent the format for entity identification in our DIDComm efforts.,,https://github.com/decentralized-identity/org/blob/master/Org%20documents/WG%20documents/DIF_DIDcomm_WG_Operating_Addendum_v1.pdf,,Page,,,Working Group,,,,,,,,2020-09-18,,,,,,,,,,,,,
DIDComm,DIDComm WG,,,,,,,,,DIF starts DIDComm Working Group,"Over the past few months, the DIF and Hyperledger Aries community have come together and agreed to work on a common work item aimed at developing secure communication based on Decentralized Identifiers (DIDs) — hence the name DIDComm, which is short for DID Communication. Significant prior work in developing a messaging-based communication protocol using DIDs has been incubating in the HyperLedger (HL) Aries community, with the progress of this effort evident in the resulting [Aries RFCs](https://github.com/hyperledger/aries-rfcs). To address the requirements of a broader and more heterogeneous community we selected DIF as the place to pursue the next phase of work associated with this effort. Presenting the progress of DIDcomm to other relevant working groups will drive the interoperability between the various decentralized identity vendors and hence enabling a range of decentralized identity-related use cases.",,https://medium.com/decentralized-identity/dif-starts-didcomm-working-group-9c114d9308dc,,Post,,,Working Group,,,,,,,,2020-01-09,,,,,,,,,,,,,
DIDComm,DIDComm WG,,,,,,,,,decentralized-identity/DIDComm-js,DIDComm JS LibA shared effort with the HL Aries project to create a standardized means of authenticated general message passing between DID controllers. More information will be added soon.,,https://github.com/decentralized-identity/DIDComm-js,,Code,,,Working Group,,,,,,,,2020-01-09,,,,,,,,,,,,,
DIDComm,IDCommons,,https://docs.google.com/presentation/d/16HTPyZV_-BtM6EifQpxjivRHKYUeVtOAReUD1eGUA9M/edit?usp=sharing,Sam Curren,,,,,IIW,2D/ Why the Internet Needs DIDComm - IIW,- Enables Verifiable Communication<br> - Intelligence at the edge (like email)<br> - Protocol Based (like email)<br> - Supports HTTP(s) (like APIs) and others as a transport<br> - Bluetooth enables Edge to Edge transport<br> - Mobile / Offline Friendly (like email)<br> - Supports rotating from one DID to another<br> - Security independent of transport<br> - Protocol development becomes easier and more robust (unlike email),,https://iiw.idcommons.net/2D/_Why_the_Internet_Needs_DIDComm,,Session Notes,,,Explainer,,,,,,,,2021-05-06,,,,,,,,,,,,,
DIDComm,IDCommons,,,Paul Knowles,,,,,IIW,2E/ Decentralized Semantics 101 - IIW,"A digital network must contain authenticable data entry and immutable data<br> <br> capture elements in order to maintain balance and integrity.<br> <br> Within the context of a decentralized network, these fundamentals enable a self-regulating system where ...<br> <br> (1) data inputs can be trusted as having come from an assured source under the control of a governing entity; and<br> <br> (2) semantic items ensure that the meaning and use of inputted data remains unaltered for all interacting actors.",,https://iiw.idcommons.net/2E/_Decentralized_Semantics_101,,Session Notes,,,Explainer,,,,,,,,2021-05-06,,,,,,,,,,,,,
DIDComm,IDCommons,,,Phil Windley,,,,,IIW,21A/ DIDComm and the Self-Sovereign Internet - IIW,"DID-based relationships are the foundation of self-sovereign identity (SSI). The exchange of DIDs to form a connection with another party gives both parties a relationship that is self-certifying and mutually authenticated. Further, the connection forms a secure messaging channel called DID Communication or DIDComm. DIDComm messaging is more important than most understand, providing a secure, interoperable, and flexible general messaging overlay for the entire internet.",,https://iiw.idcommons.net/21A/_DIDComm_and_the_Self-Sovereign_Internet,,Session Notes,,,Explainer,,,,,,,,2021-05-06,,,,,,,,,,,,,
DIDComm,Personal,,,Phillip J. Windley,,,,,,DIDComm and the Self-Sovereign Internet,"DIDComm is a protocol layer capable of supporting specialized application protocols for specific workflows. Because of its general nature and inherent support for self-sovereign relationships, DIDComm provides a basis for a self-sovereign internet much more private, enabling, and flexible than the one we've built using Web 2.0 technologies. This talk introduces DIDComm, discusses its protocological nature, and presents use cases in the Internet of Things. Demonstrations of DIDComm protocol interactions will be shown on the Pico platform, which implements the Aries Cloud Agent (ACA) specification.",,https://www.windley.com/archives/2020/11/didcomm_and_the_self-sovereign_internet.shtml,https://www.windley.com/archives/2020/11/mesh.jpg,Post,,,Explainer,,,,,,,,2020-11-11,,,,,,,,,,,,,
DIDComm,Personal,,,Phillip J. Windley,,,,,,DIDComm and the Self-Sovereign Internet,"DIDComm is a protocol layer capable of supporting specialized application protocols for specific workflows. Because of its general nature and inherent support for self-sovereign relationships, DIDComm provides a basis for a self-sovereign internet much more private, enabling, and flexible than the one we've built using Web 2.0 technologies. This talk introduces DIDComm, discusses its protocological nature, and presents use cases in the Internet of Things. Demonstrations of DIDComm protocol interactions will be shown on the Pico platform, which implements the Aries Cloud Agent (ACA) specification.",,https://www.windley.com/archives/2020/11/didcomm_and_the_self-sovereign_internet.shtml,,Post,,,Explainer,,,,,,,,2020-11-11,,,,,,,,,,,,,
DIDComm,DIF,,,Kaliya Young,,,,,,Why we need DIDComm - Identity Woman,This is the text of an email I got today from a company that I had a contract with last year [...] I was reminded quite strongly why we need DIDComm as a protocol to enable the secure transport of all sorts of things not just signed VCs but intermediate uses,,https://identitywoman.net/why-we-need-didcomm/,,Post,,,Explainer,,,,,,,,2022-01-12,,,,,,,,,,,,,
DIDComm,Personal,,,Daniel Hardman,,,,,,DIDComm Mythconceptions,DIDComm is a peer-to-peer communication technology for SSI (self-sovereign identity) with security and privacy properties rooted in DIDs (decentralized identifiers). Its core value proposition is often misunderstood or oversimplified. This webinar provides a proper mental model.,,https://www.youtube.com/watch?v=rwvQdRyMeY4,https://i.ytimg.com/vi/rwvQdRyMeY4/maxresdefault.jpg?sqp=-oaymwEmCIAKENAF8quKqQMa8AEB-AH-CYAC0AWKAgwIABABGGUgXig_MA8=&rs=AOn4CLCxo_GS9BmeYLTCl5mB-923nmd_Vg,Video,,,Explainer,,,,,,,,2021-11-10,,,,,,,,,,,,,
DIDComm,twit.tv,,,Sam Curren,,,,,,DIDCOMM,Sam Curren unpacks for Doc Searls and Dan Lynch why DIDs and DIDcomm are the best approach to identity—and to making people first-class citizens on the Internet. Curren also discusses the origin story of picos and the advantages of nomadic living and hacking.,,https://twit.tv/shows/floss-weekly/episodes/685,https://elroy.twit.tv/sites/default/files/images/episodes/836442/hero/floss_0685.jpg,episode,,,Explainer,,,,,,,,2022-06-15,,,,,,,,,,,,,
DIDComm,DIF,,,,,,,,,DIDComm V2 reaches approved spec status!,"Following the approval of the Decentralized Identifiers (DID) Core Spec by the W3C as an official open web standard, the Decentralized Identity Foundation (DIF) announced the approval of the DIDComm v2 specification. Combined, this represents a major step forward in the acceptance of decentralized identity, one that opens the path to widespread adoption and further development especially with regard to the types of peer-to-peer communication now possible.<br><br>DIDComm defines how messages are composed into application-level protocols and workflows.","DIDComm v2 has now reached DIF Approved Status, joining SideTree as a complete and approved open-source specification.",https://blog.identity.foundation/didcomm-v2/,,Post,,,Spec,,,,,,,DIDComm WG,2022-07-26,,,,,,,,,,,,,
DIDComm,twit.tv,,,Sam Curren,,,,,,"DIDCOMM - Sam Curren, Importance of DIDs",Sam Curren unpacks for Doc Searls and Dan Lynch why DIDs and DIDcomm are the best approach to identity—and to making people first-class citizens on the Internet. Curren also discusses the origin story of picos and the advantages of nomadic living and hacking.,,https://twit.tv/shows/floss-weekly/episodes/685,,episode,,,Explainer,,,,,,,,2022-06-15,,,,,,,,,,,,,
DIDComm,Hyperledger,,,,,,,,,Aries RFC 0453 - credential issuance protocol using DIDComm V1 data formats,An optional mechanism for providing credential supplements during issuance. Supplements are also used in credential presentation.,,https://github.com/hyperledger/aries-rfcs/tree/master/features/0453-issue-credential-v2,,rfc,,,RFCs,,,,,,,Aries RFC,2021-04-15,,,,,,,,,,,,,
DIDComm,Hyperledger,,,,,,,,,Aries RFC 0454 - Present Proof protocol V2 using DIDCommV1 data formats,"A minor update to add mechanism for a Verifier to request the Prover submit multiple presentations in the ""presentation"" message(s), each presentation sourced from different credentials that satisfy the presentation request. An example use of this capability is an employer (Verifier) requesting multiple ""proof of employment"" presentations from a job application (Prover), each satisfying the one presentation request.",,https://github.com/hyperledger/aries-rfcs/tree/master/features/0454-present-proof-v2,,rfc,,,RFCs,,,,,,,Aries RFC,2021-04-15,,,,,,,,,,,,,
DIDComm,IDCommons,,,,,,,,IIW,"DIDComm V2: Implementation and integration 'technical' - did:key and did:keri resolvers, seamless and partial integrations","Technical session covering basics of DIDComm v2 Rust implementation (didcomm-rs), including JWM message format overview, JWE/JWM envelopes and key identifiers structures as well as cryptography usage. In addition weve discussed how key resolution of public keys happening from `kid` and `skid` envelope header fields using plugable resolvers and private keys resolver using Vault Key provider in form of “Universal wallet” spec implementation [wallet-rs].",,"https://iiw.idcommons.net/11D/_DIDComm_V2:_Implementation_and_integration_%27technical%27_-_did:key_and_did:keri_resolvers,_seamless_and_partial_integrations-",,Session Notes,,,Development,,,,,,,,2021-05-07,,,,,,,,,,,,,
DIDComm,Jolocom,,,Ivan Temchenko,,,,,,didcomm-rs implementation,What is this talk about?<br><br>• didcomm-rs implementation<br>• Resolver[s] integration<br>• Application level integration (with wallet-rs)<br>• End-to-end consuming application example demo simple console chat application based on DIDComm v2 and did:key/did:keri (with resolvers)<br>• Floor open for discussions,,https://drive.google.com/file/d/1dn5f2SqnCeQocOy5quJD9gpMPipKRmdC/view?usp=sharing,,Presentation,,,Development,,,,,,,,2021-04-21,,,,,,,,,,,,,
DIDComm,DIF,,,,,,,,,Rust implementation of DIDComm v2,This is a sample implementation of the DIDComm V2 spec. The DIDComm V2 spec is still actively being developed by the DIDComm WG in the DIF and therefore subject to change.,,https://github.com/decentralized-identity/didcomm-rs,,Code,,,Development,,,,,,,,2022-10-10,,,,,,,,,,,,,
DIDComm,uPort,,,Oliver Terbu,uPort,,,,,Trusted P2P messaging with DIDs DIDComm and VCs,"about their path towards trusted P2P messaging and announces the [DIDAgent Framework (DAF)](https://github.com/uport-project/daf)<br>when we speak about a DID, then we need to be more precise and also speak about the particular DID method of that DID which defines the CRUD operations on a target system such as Ethereum.",A Decentralized Identifier (DID) is a stable identifier in form of an URI that introduces a level of indirection for key management and managing other useful information such as service endpoints. It…,https://medium.com/uport/trusted-p2p-messaging-with-dids-didcomm-and-vcs-398f4c3f3cda,https://miro.medium.com/v2/resize:fit:1200/1*bE-GDUWPuUPGyuNPCErJQQ.jpeg,Post,,,Development,,,,,,,,2020-11-12,,,,,,,,,,,,,
DIDComm,uPort,,,Oliver Terbu,,,,,,DIDComm Messaging through libp2p,"We outlined the next generation decentralized messaging solution built on top of [DIDComm Messaging](https://identity.foundation/didcomm-messaging/spec/), [DIDs](https://www.w3.org/TR/did-core/) and [VCs](https://www.w3.org/TR/vc-data-model/) and a [libp2p](https://libp2p.io/) overlay network. We presented how Alice and Bob establish a connection, exchange messages and demonstrated what connection types are supported.",With InterPlanetary File System (IPFS) the Web3 community has established a critical piece of infrastructure that is used by the majority of web3 protocols to different degrees. Libp2p is part of the…,https://medium.com/uport/didcomm-messaging-through-libp2p-cffe0f06a062,https://miro.medium.com/v2/resize:fit:1200/1*cBMXWaM8DEH870d6h57mBg.png,Post,,,Development,,,,,,,,2021-11-30,,,,,,,,,,,,,
DIDComm,uPort,,,Oliver Terbu,uPort,,,,,Trusted P2P messaging with DIDs DIDComm and VCs,"about their path towards trusted P2P messaging and announces the [DIDAgent Framework (DAF)](https://github.com/uport-project/daf)<br>when we speak about a DID, then we need to be more precise and also speak about the particular DID method of that DID which defines the CRUD operations on a target system such as Ethereum.",A Decentralized Identifier (DID) is a stable identifier in form of an URI that introduces a level of indirection for key management and managing other useful information such as service endpoints. It…,https://medium.com/uport/trusted-p2p-messaging-with-dids-didcomm-and-vcs-398f4c3f3cda,,Post,,,Development,,,,,,,,2020-11-12,,,,,,,,,,,,,
DIDComm,uPort,,,Oliver Terbu,,,,,,DIDComm Messaging through libp2p,"We outlined the next generation decentralized messaging solution built on top of [DIDComm Messaging](https://identity.foundation/didcomm-messaging/spec/), [DIDs](https://www.w3.org/TR/did-core/) and [VCs](https://www.w3.org/TR/vc-data-model/) and a [libp2p](https://libp2p.io/) overlay network. We presented how Alice and Bob establish a connection, exchange messages and demonstrated what connection types are supported.",With InterPlanetary File System (IPFS) the Web3 community has established a critical piece of infrastructure that is used by the majority of web3 protocols to different degrees. Libp2p is part of the…,https://medium.com/uport/didcomm-messaging-through-libp2p-cffe0f06a062,,Post,,,Development,,,,,,,,2021-11-30,,,,,,,,,,,,,
DIDComm,WebofTrustInfo,,,Karim Stekelenburg,Animo Solutions,,,,,Advanced DIDComm Messaging,"in order for DIDComm to provide a potential replacement for commonly used chat protocols like WhatsApp (Extensible Messaging and Presence Protocol (XMPP)), Telegram (MTProto), or Signal (Signal Protocol), it needs to support modern chat features we use everyday",,https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/advance-readings/advanced-didcomm-messaging.md,,Paper,,0.1,Development,,,,,,,,2022-07-19,,,,,,,,,,,,,
DIDComm,DATEV,,,Tim Vorgs,,,,,,DIDComm & DIDComm Messaging,"Based on the research project we conducted with SAP, we developed a Proof of Concept (PoC for order-to-cash-business processes. As part of this PoC, we integrated DIDComm based communication to seamlessly transfer data within the boundaries of the process. The overall steps are:",,https://medium.com/datev-techblog/didcomm-didcomm-messaging-3e10fbf12bb8,https://miro.medium.com/v2/resize:fit:1200/1*prcKX5OvEifMsbSiijDj1A.png,Post,,,Development,,,,,,,,2022-07-18,,,,,,,,,,,,,
DIDComm,DIF,,,,,,,,,"DIF F2FJan21 - DIDComm Demo Session with Ivan Temchenko, Tobias Looker, and Oliver Terbu","During the live demo he showed the message lifecycle in various setups using the new, [open source didcomm-rs library](http://github.com/jolocom/didcomm-rs) on GitHub","In this informal F2F side-session, Jolocom's Ivan Temchenko gives a detailed tour of their core DIDComm v2 library in Rust, followed by a brief CLI demo from...",https://www.youtube.com/watch?v=SaNvIorKQ9I&feature=youtu.be,https://i.ytimg.com/vi/SaNvIorKQ9I/maxresdefault.jpg,Video,,,Development,,,,,,,,2021-01-26,,,,,,,,,,,,,
DIDComm,gold and double blue,,,Siddhi,,,,,,Blockchain and Self-Sovereign Identity Empowered Cyber Threat Information Sharing Platform,Blockchain and Self-Sovereign Identity Empowered Cyber Threat Information Sharing Platform<br>- Presented in 7th IEEE International Conference on Smart Computing(IEEE SmartComp 2021),- Siddhi - Blockchain and Self-Sovereign Identity Empowered Cyber Threat Information Sharing Platform- Presented in 7th IEEE International Conference on Smar...,https://www.youtube.com/watch?v=lzS49R52PwA,https://i.ytimg.com/vi/lzS49R52PwA/maxresdefault.jpg,Video,,,Implementation,,,,,,,,2021-08-11,,,,,,,,,,,,,
DIDComm,DIF,,,,,,,,,"DIF F2FJan21 - DIDComm Demo Session with Ivan Temchenko, Tobias Looker, and Oliver Terbu","During the live demo he showed the message lifecycle in various setups using the new, [open source didcomm-rs library](http://github.com/jolocom/didcomm-rs) on GitHub","In this informal F2F side-session, Jolocom's Ivan Temchenko gives a detailed tour of their core DIDComm v2 library in Rust, followed by a brief CLI demo from...",https://www.youtube.com/watch?v=SaNvIorKQ9I&feature=youtu.be,,Video,,,Development,,,,,,,,2021-01-26,,,,,,,,,,,,,
DIDComm,gold and double blue,,,Siddhi,,,,,,Blockchain and Self-Sovereign Identity Empowered Cyber Threat Information Sharing Platform,Blockchain and Self-Sovereign Identity Empowered Cyber Threat Information Sharing Platform<br>- Presented in 7th IEEE International Conference on Smart Computing(IEEE SmartComp 2021),- Siddhi - Blockchain and Self-Sovereign Identity Empowered Cyber Threat Information Sharing Platform- Presented in 7th IEEE International Conference on Smar...,https://www.youtube.com/watch?v=lzS49R52PwA,,Video,,,Implementation,,,,,,,,2021-08-11,,,,,,,,,,,,,
DIDComm,Personal,,https://didcomm.org/shorten-url/1.0/,Timo Glastra,,,,,,Just got my first DIDComm protocol published on the https://didcomm.org website.,"A protocol to request a shortened URL for a given URL. For example, an agent requesting a shortened out of band invitation url from a mediator.",,https://twitter.com/TimoGlastra/status/1572976791136137216,,tweet,,,Implementation,,,,,,,,2022-08-22,,,,,,,,,,,,,
DIDComm,DIF,,,,,,,,,DIDComm: ECDH-1PU Implementation,"In short, ECDH-1PU is a key derivation process that allows for sender authenticity and enables a “[Perfect Forward Secrecy](https://www.wired.com/2016/11/what-is-perfect-forward-secrecy/#:~:text=Perfect%20forward%20secrecy%20means%20that,of%20the%20user%27s%20sensitive%20data.)” mechanism, in addition to significant performance gains over JWS message nested in a JWE envelope, as used by existign ECDH-ES aproaches.","ECDH-1PU is a key derivation process that offers sender authenticity, as well as significant performance gains over existing ECDH-ES aproaches.",https://blog.identity.foundation/ecdh-1pu-implementation/,https://blog.identity.foundation/content/images/2021/09/mathyas-kurmann-fb7yNPbT0l8-unsplash-2.jpg,Post,,,Implementation,,,,,,,,2021-09-21,,,,,,,,,,,,,
DIDComm,DIF,,,,,,,,,DIDComm: ECDH-1PU Implementation,"In short, ECDH-1PU is a key derivation process that allows for sender authenticity and enables a “[Perfect Forward Secrecy](https://www.wired.com/2016/11/what-is-perfect-forward-secrecy/#:~:text=Perfect%20forward%20secrecy%20means%20that,of%20the%20user%27s%20sensitive%20data.)” mechanism, in addition to significant performance gains over JWS message nested in a JWE envelope, as used by existign ECDH-ES aproaches.","ECDH-1PU is a key derivation process that offers sender authenticity, as well as significant performance gains over existing ECDH-ES aproaches.",https://blog.identity.foundation/ecdh-1pu-implementation/,,Post,,,Implementation,,,,,,,,2021-09-21,,,,,,,,,,,,,
DIDComm,Jolocom,,,,,,,,,Community matters: Jolocoms latest contributions to DIF,"We at Jolocom strongly believe that DIDComm is a crucial infrastructure element for the broader and future-proof SSI stack, and [current work on DIDComm v2 includes Jolocoms implementation of the specification](http://github.com/jolocom/didcomm-rs) with authcrypt (authenticated encrypted) and most of the low level of the protocol.",...Interested parties can already start building high-level verifiable credential-based services and workflows on the Rust KERI implementation.,https://jolocom.io/blog/jolocoms-contributions-to-dif/,https://jolocom.io/wp-content/uploads/2020/05/Jolocom-Logbook-DIF-contribution-cover-02-alt.jpg,Post,,,Implementation,,,,,,,,2021-01-19,,,,,,,,,,,,,
mDL,INATBA,,,,,,,,,“Decentralised Identity: Whats at Stake?”,"Looking at the above comparison, It is clear that both approaches strive to maintain user control of their personal data, selective disclosure/data minimization, and cryptographic methods to prove the integrity of identity claims. The differences are: first in their reliance (mDL) or independence (SSI) from issuer involvement in verification interactions, and second in their cryptographic approach, where the mDL relies on externally provided cryptographic tools while SSI builds on holder controlled private keys",← earlier paper,https://inatba.org/wp-content/uploads/2020/11/2020-11-INATBA-Decentralised-Identity-001.pdf,https://inatba.org/wp-content/uploads/2023/05/Background_561821321-scaled-copie.jpg,Post,,,Intro,,,,,,,,2021-11,,,,,,,,,,,,,
mDL,SpruceID,,,,,,,,,An Identity Wallet Bill of Rights - Starting With the Mobile Driver License,"Spruces continued mission is to let users control their data across the web, whether its web2, web3, or beyond. This also applies to credentials issued by existing entities, such as the Mobile Driver License (mDL) issued by motor vehicle authorities across the world.","Spruces continued mission is to let users control their data across the web, whether its web2, web3, or beyond. This also applies to credentials issued by existing entities, such as the Mobile Driver License (mDL) issued by motor vehicle authorities across the world.",https://blog.spruceid.com/an-identity-wallet-bill-of-rights/,https://blog.spruceid.com/content/images/2022/09/mDL.png,Post,,,Intro,,,,,,,,2022-09-12,,,,,,,,,,,,,
mDL,INATBA,,,,,,,,,Mobile Drivers Licence (mDL) VS. Self-Sovereign Identity (SSI),"The ISO mDL specification (ISO-compliant Driving License or IDL)  is purpose driven, as its name implies, but is said to be specifically intended to:<br>* enable verifiers not affiliated with or associated with the issuing authority to gain access to and authenticate the information<br>* allow the holder of the driving license to decide what information to release to a verifier<br>* include the ability to update information frequently, and to authenticate information at a high level of confidence.",,https://inatba.org/identity/mobile-drivers-licence-mdl-self-sovereign-identity-ssi-comparison/,https://inatba.org/wp-content/uploads/2023/05/Background_561821321-scaled-copie.jpg,Post,,,Main,,,,,,,,2020-11,,,,,,,,,,,,,
mDL,CCG Mailing List,,,Manu Sporny,"Spruce, MATTR, Digital Bazaar, CCG",,,,,Verifiable Driver's Licenses and ISO-18013-5 (mDL),"As some of you might be aware, ISO-18013-5 (mDL -- Mobile Driver's License) was published as a global ISO standard in September 2021. A number of us in the W3C CCG and W3C VCWG attempted to ensure that W3C Verifiable Credentials were supported by the mDL work, but that effort is not reflected in the finalized ISO mDL standard (and due to the way ISO operates, we are not at liberty to share any details). There have been increasing concerns related to the divergence of mDL with W3C Verifiable Credentials and to the market dynamics at play around mDL.",,https://lists.w3.org/Archives/Public/public-credentials/2021Nov/0105.html,,Discussion,,,Main,,,,,,,,2021-11-29,,,,,,,,,,,,,
mDL,Procivis,,,,,,,,,ISO/IEC 18013-5 vs Self-Sovereign Identity: A proposal for an mDL Verifiable Credential,"in the context of government identity programs we see it as useful to compare them on the following parameters background, credential data model & trust anchor and transmission protocols.",,https://www.procivis.ch/post/iso-iec-18013-5-vs-self-sovereign-identity-a-proposal-for-an-mdl-verifiable-credential,https://uploads-ssl.webflow.com/5fae427844470c4d4b49d62b/62440e2a85213a51704c8641_Picture%203.png,Post,,,Main,,,,,,,,2022-03-30,,,,,,,,,,,,,
mDL,AAMVA,,,,,,,,,Mobile Driver's License (mDL) Implementation Guidelines 1.2,"The AAMVA Joint Mobile Drivers License (mDL) Working Group (WG) has been active around mobile identification since 2012. As the mDL evolves, the mDL WG continues to identify and address topics on which guidance to Issuing Authorities can be helpful. This document represents the bulk of the current guidance, and points to additional resources as needed",,https://www.aamva.org/getmedia/b801da7b-5584-466c-8aeb-f230cef6dda5/mDL-Implementation-Guidelines-Version-1-2_final.pdf,,Report,,,Main,,,,,,,,2023-01,,,,,,,,,,,,,
mDL,AAMVA,,,,,,,,,Mobile Driver's License Model Legislation,"The Mobile Drivers License (mDL) Model Legislation has been developed to facilitate the uniformity of proposed legislative changes related to implementation of mDL in various jurisdictions. The model legislation is meant to demonstrate how the requirements in the ISO standards and AAMVA Mobile Drivers License Implementation Guidelines could be represented in jurisdiction-specific legislation. Thus, the language contained in the model legislation is designed to offer examples and is not expected to be proposed to legislatures without consideration for controlling legal provisions in your jurisdiction",,https://www.aamva.org/getmedia/cb9fd6c7-29e6-48a4-926b-e16d6400eab5/mDL-Model-Legislation_final.pdf,,Report,,,Main,,,,,,,,2023-01,,,,,,,,,,,,,
mDL,Kantara Initiative,,,,,,,,,Working Group for Privacy Enhancing Mobile Credentials,Clearly the use of a drivers license goes well beyond proving eligibility to drive a vehicle. It has become the de-facto standard for proving that you are who you say you are and are entitled to the product or service requested. An increasing number of states are adopting mobile ID systems to recognise and verify mobile credentials including drivers licenses (mDL).,,https://kantarainitiative.org/introducing-kantaras-working-group-for-privacy-enhancing-mobile-credentials/,https://kantarainitiative.org/wp-content/uploads/2021/11/mitya-ivanov-2HWkORIX3II-unsplash-scaled-1.jpg,Post,,,Guidance,,,,,,,,2021-11-15,,,,,,,,,,,,,
mDL,Kantara Initiative,,,,,,,,,Kantara Releases Report on Identity and Privacy Protection For mobile Drivers Licenses,The report outlines how to implement mDL systems as Privacy Enhancing Technologies. It provides guidance on protecting peoples individual privacy and the digital identifiers of an individual who carries or uses an mDL.,,https://kantarainitiative.org/kantara-releases-report-on-identity-and-privacy-protection-for-mobile-drivers-licenses/,https://kantarainitiative.org/wp-content/uploads/2019/08/favicon_kantara.png,Post,,,Guidance,,,,,,,,2021-08-27,,,,,,,,,,,,,
mDL,Biometric Update,,https://kantarainitiative.org/kantara-lays-out-trust-building-recommendations-for-mdls/,,,,,,,Kantara lays out trust-building recommendations for mDLs,"A global digital ID association has published steps vendors and others need to take in order to build effective mobile driving license services that also put ID holders in control of their identity. The Kantara Initiatives report starts from the premise that trust in mobile driving licenses grows with the degree of control that license holders have over the documents, their privacy and their biometric identifiers.","Trust in mobile driving licenses grows with the degree of control that license holders have over the documents, their privacy and their biometric identifiers.",https://www.biometricupdate.com/202108/kantara-lays-out-trust-building-recommendations-for-mdls,https://d1sr9z1pdl3mb7.cloudfront.net/wp-content/uploads/2020/04/06115457/mDL-mobile-drivers-license.png,Post,,,Guidance,,,,,,,,2021-08-27,,,,,,,,,,,,,
mDL,CCG,,,,,,,,,Verifiable Driver's License Interoperability Report 1.0,The purpose of this test suite is to demonstrate a path to interoperability between the ISO-18013-5 Mobile Driver's License data model and the W3C Verifiable Credentials ecosystem. The technologies explored in this test suite are experimental and meant to be complementary to ISO-18013-5 (mDL) and not a replacement of the standard. This document contains the most recent interoperability report between issuers and verifiers for Verifiable Driver's License Credentials using the Verifiable Driver's License Vocabulary. This report is generated on a weekly basis.,,https://w3c-ccg.github.io/vdl-test-suite/,,Report,,,Guidance,,,,,,,,2023-01-08,,,,,,,,,,,,,
mDL,INATBA,,,,,,,,,Mobile Drivers Licence (mDL) VS. Self-Sovereign Identity (SSI),"The ISO mDL specification (ISO-compliant Driving License or IDL)  is purpose driven, as its name implies, but is said to be specifically intended to:<br>* enable verifiers not affiliated with or associated with the issuing authority to gain access to and authenticate the information<br>* allow the holder of the driving license to decide what information to release to a verifier<br>* include the ability to update information frequently, and to authenticate information at a high level of confidence.",,https://inatba.org/identity/mobile-drivers-licence-mdl-self-sovereign-identity-ssi-comparison/,https://inatba.org/wp-content/uploads/2023/05/Background_561821321-scaled-copie.jpg,Post,,,180135,,,,,,,,2020-11,,,,,,,,,,,,,
mDL,CCG Mailing List,,,Manu Sporny,"Spruce, MATTR, Digital Bazaar, CCG",,,,,Verifiable Driver's Licenses and ISO-18013-5 (mDL),"As some of you might be aware, ISO-18013-5 (mDL -- Mobile Driver's License) was published as a global ISO standard in September 2021. A number of us in the W3C CCG and W3C VCWG attempted to ensure that W3C Verifiable Credentials were supported by the mDL work, but that effort is not reflected in the finalized ISO mDL standard (and due to the way ISO operates, we are not at liberty to share any details). There have been increasing concerns related to the divergence of mDL with W3C Verifiable Credentials and to the market dynamics at play around mDL.",,https://lists.w3.org/Archives/Public/public-credentials/2021Nov/0105.html,,Discussion,,,180135,,,,,,,,2021-11-29,,,,,,,,,,,,,
mDL,Procivis,,,,,,,,,ISO/IEC 18013-5 vs Self-Sovereign Identity: A proposal for an mDL Verifiable Credential,"in the context of government identity programs we see it as useful to compare them on the following parameters background, credential data model & trust anchor and transmission protocols.",,https://www.procivis.ch/post/iso-iec-18013-5-vs-self-sovereign-identity-a-proposal-for-an-mdl-verifiable-credential,https://uploads-ssl.webflow.com/5fae427844470c4d4b49d62b/62440e2a85213a51704c8641_Picture%203.png,Post,,,180135,,,,,,,,2022-03-30,,,,,,,,,,,,,
mDL,AAMVA,,,,,,,,,Mobile Driver's License (mDL) Implementation Guidelines 1.2,"The AAMVA Joint Mobile Drivers License (mDL) Working Group (WG) has been active around mobile identification since 2012. As the mDL evolves, the mDL WG continues to identify and address topics on which guidance to Issuing Authorities can be helpful. This document represents the bulk of the current guidance, and points to additional resources as needed",,https://www.aamva.org/getmedia/b801da7b-5584-466c-8aeb-f230cef6dda5/mDL-Implementation-Guidelines-Version-1-2_final.pdf,,Report,,,180135,,,,,,,,2023-01,,,,,,,,,,,,,
mDL,AAMVA,,,,,,,,,Mobile Driver's License Model Legislation,"The Mobile Drivers License (mDL) Model Legislation has been developed to facilitate the uniformity of proposed legislative changes related to implementation of mDL in various jurisdictions. The model legislation is meant to demonstrate how the requirements in the ISO standards and AAMVA Mobile Drivers License Implementation Guidelines could be represented in jurisdiction-specific legislation. Thus, the language contained in the model legislation is designed to offer examples and is not expected to be proposed to legislatures without consideration for controlling legal provisions in your jurisdiction",,https://www.aamva.org/getmedia/cb9fd6c7-29e6-48a4-926b-e16d6400eab5/mDL-Model-Legislation_final.pdf,,Report,,,180135,,,,,,,,2023-01,,,,,,,,,,,,,
mDL,IETF,RFC 8943,,,,,,,,RFC 8943: Concise Binary Object Representation (CBOR) Tags for Date,"In CBOR, one point of extensibility is the definition of CBOR tags. RFC 7049 defines two tags for time: CBOR tag 0 (date/time string as per RFC 3339) and tag 1 (POSIX ""seconds since the epoch""). Since then, additional requirements have become known. This specification defines a CBOR tag for a date text string (as per RFC 3339) for applications needing a textual date representation within the Gregorian calendar without a time. It also defines a CBOR tag for days since the date 1970-01-01 in the Gregorian calendar for applications needing a numeric date representation without a time. This specification is the reference document for IANA registration of the CBOR tags defined.","The Concise Binary Object Representation (CBOR), as specified in RFC 7049, is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation.",https://www.rfc-editor.org/rfc/rfc8943,,rfc,,,CBOR,,,,,,,,2020-11,,,,,,,,,,,,,
mDL,Personal,,https://www.rfc-editor.org/rfc/rfc8943,Mike Jones,,,,,,Concise Binary Object Representation (CBOR) Tags for Date is now RFC 8943,"The Concise Binary Object Representation (CBOR) Tags for Date specification has now been published as RFC 8943. In particular, the full-date tag requested for use by the ISO Mobile Driver’s License specification in the ISO/IEC JTC 1/SC 17 “Cards and security devices for personal identification” working group has been created by this RFC. The abstract of the RFC is:",Mike Jones shares that CBOR (Concise Binary Object Representation) is officially a specification at IETF. woohoo! and it is a key part of [ISOs mDL standard](https://www.iso.org/committee/45144.html) (date fields must use it).,https://self-issued.info/?p=2136,,Post,,,CBOR,,,,,,,,2020-11-20,,,,,,,,,,,,,
Competition,VentureBeat,,,Emil Protalinski,Google,,,,,Google is bringing Electronic IDs to Android,"very soon, we will launch another [Jetpack compatibility library](https://venturebeat.com/2019/05/07/google-adds-10-libraries-to-android-jetpack-unveils-kotlin-toolkit-for-ui-development/) that app developers can use immediately to write such apps for various DMVs or whatever cards — in the future, maybe even travel documents, although that kind of standardization for international travel is even further out.","Google is bringing Electronic IDs to Android so that your driver's license and your passport are accessible on your phone, even when the battery is dead.",https://venturebeat.com/security/google-is-bringing-electronic-ids-to-android/,https://venturebeat.com/wp-content/uploads/2019/05/MzE5MTU4Ng.jpeg?w=1200&strip=all,Post,,,Main,,,,,,,,2019-05-09,,,,,,,,,,,,,
Competition,Apple,,,,Apple,,,,,Apple announces first states signed up to adopt drivers licenses and state IDs in Apple Wallet,"Arizona, Connecticut, Georgia, Iowa, Kentucky, Maryland, Oklahoma, and Utah are among the first states to bring state IDs and drivers licenses in Wallet to their residents",Apple is working with states across the country to roll out the ability for their residents to add their drivers license or state ID to Wallet.,https://www.apple.com/newsroom/2021/09/apple-announces-first-states-to-adopt-drivers-licenses-and-state-ids-in-wallet/,https://www.apple.com/newsroom/images/product/os/ios/standard/apple_wallet-state-id_hero_08232021.jpg.og.jpg?202305231359,Post,,,Main,,,,,,,,2021-09-01,,,,,,,,,,,,,
Competition,CNBC,,https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0231.html,"Hugh Son,Kif Leswing",,,,,,"Apple launches the first drivers license and state ID in Wallet with Arizona” Its sad and frustrating that this isnt based on verifiable credentials… it appears vendor lock in is going to be hard to prevent.<br><br>For anyone who missed the November coverage about this, heres a pretty outrageous CNBC article: Apple is sticking taxpayers with part of the bill for rollout of tech giant's digital ID card","- Apple requires states to maintain the systems needed to issue and service credentials at taxpayer expense, according to contracts signed by four states.<br>- The agreement, obtained through public record requests from CNBC and other sources, mostly portrays Apple as having a high degree of control over the government agencies responsible for issuing identification cards.<br>- Apple has “sole discretion” for key aspects of the program.","Contracts between Apple and states including Georgia, Arizona, Kentucky and Oklahoma provide a rare glimpse into the dealings of the powerful company. ",https://www.cnbc.com/2021/11/14/apple-sticking-taxpayers-with-part-of-the-bill-for-digital-id-rollout.html,https://image.cnbcfm.com/api/v1/image/106893252-1623087055894Screen-Shot-2021-06-07-at-1-27-30-PM-png?v=1623087200&w=1920&h=1080,Post,,,Main,,,,,,,,2021-11-14,,,,,,,,,,,,,
Competition,CCG Mailing List,,https://www.ietf.org/archive/id/draft-secure-credential-transfer-03.html,Manu Sporny,CCG,,,,,Re: IETF: Secure Credential Transfer,"Seems like a point solution -- digital dead drop box for bearer credentials that are encrypted to specific individuals. Very little overlap w/ VCs and the protocols we're discussing here (but, would be good to keep our eye on this one).",,https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0030.html,,Discussion,,,Main,,,,,,,,2022-04-05,,,,,,,,,,,,,
Exchange Protocols,IDCommons,,https://docs.google.com/document/d/1_b5MxzUPWzYxXxWt7Tw6-MySqh77ZvYHBnUgEBCFH7Q/edit,"Kaliya Young, Orie Steele, Drummond, Kyle, et al.",,,,,,"Figuring out Verifiable Credentials Exchange - combining Bloom, Aires Protocols, Presentation Exchange into a unified - Killer Whale Jello Salad",- Because what we need is interoperable - issuance - issue-holder || holder -verifier some conversation about SIOP - has not been the focus of the discussion.<br - Goal to create a bridge between<br - the W3C CCG / DHS SVIP - VCI-HTTP-API (VHA) in combination with CHAPI protocol and the (VC Request) for issuing credentials.<br - Aries protocols run on top of DIDComm<br - If we agree on a credential format we can exchange across those universes - JSON-LD ZKP BBS+ then we need a protocol to do it - can go between.,,"https://iiw.idcommons.net/22H/_Figuring_out_Verifiable_Credentials_Exchange_-_combining_Bloom,_Aires_Protocols,_Presentation_Exchange_into_a_unified_-_Killer_Whale_Jello_Salad",,Session Notes,,,Background,,,,,,,,2021-05-06,,,,,,,,,,,,,
Exchange Protocols,IDCommons,,https://docs.google.com/document/d/1_b5MxzUPWzYxXxWt7Tw6-MySqh77ZvYHBnUgEBCFH7Q/edit,"Kaliya Young, Orie Steele, Drummond, Kyle, et al.",,,,,,"Figuring out Verifiable Credentials Exchange - combining Bloom, Aires Protocols, Presentation Exchange into a unified - Killer Whale Jello Salad",- Because what we need is interoperable - issuance - issue-holder || holder -verifier some conversation about SIOP - has not been the focus of the discussion.<br> - Goal to create a bridge between<br> - the W3C CCG / DHS SVIP - VCI-HTTP-API (VHA) in combination with CHAPI protocol and the (VC Request) for issuing credentials.<br> - Aries protocols run on top of DIDComm<br> - If we agree on a credential format we can exchange across those universes - JSON-LD ZKP BBS+ then we need a protocol to do it - can go between.,,"https://iiw.idcommons.net/22H/_Figuring_out_Verifiable_Credentials_Exchange_-_combining_Bloom,_Aires_Protocols,_Presentation_Exchange_into_a_unified_-_Killer_Whale_Jello_Salad",,Session Notes,,,Background,,,,,,,,2021-05-06,,,,,,,,,,,,,
Exchange Protocols,IDCommons,,https://iiw.animo.id,,,,,,,BBS+ Credential Exchange in Hyperledger Aries,"19:18:25 From Sebastian Schmittner : Is there some working implementation out there to actually generate/work with these VCs shown currently?<br>19:18:58 From Troy Ronda : aries-framework-go is one of them.<br>19:19:24 From Karim Stekelenburg : The ACA-Py implementation will be merged in shortly<br>19:20:50 From Stephen Curran : PR: https://github.com/hyperledger/aries-cloudagent-python/pull/1061<br>19:22:02 From Sebastian Schmittner : awesome! We are doing some prototyping right now where we are using JSON-LD VCs with the americans, but, since we are also running a node in the HL Indy network of ID Union, it would be really great if we could bridge the Ocean here ;)",,https://iiw.idcommons.net/11E/_BBS+_Credential_Exchange_in_Hyperledger_Aries,,Session Notes,,,Background,,,,,,,,2021-05-06,,,,,,,,,,,,,
Exchange Protocols,IDCommons,,,,,,,,,Credentials Exchange - figuring it out - (Jello Bowl Death Match?),"The ultimate goal is to get to a clear exchange protocols.<br><br>Also to have a paper similar to [this one](https://www.lfph.io/wp-content/uploads/2021/02/Verifiable-Credentials-Flavors-Explained.pdf) that outlines the choice landscape that is and points to a convergence point<br><br>Good Health Pass is literally right now trying to figure this out and will “pick” solutions it needs to get implementations working in the next 30-90 days and point the whole industry in one direction.<br><br>We started out with this framework of understanding<br><br>Contextualizing VC Exchange in Layers<br><br>Verifiable Credentials (VC or VCs) is one of the key standardized components of decentralized identity. [The VCs Data Model](https://www.w3.org/TR/vc-data-model/), defined at the W3C, is a universal data format that lets any entity express anything about another entity.  It provides a common mechanism for the interoperable implementation of digital credentials that are cryptographically secure, tamper-evident, privacy-respecting, and machine-verifiable.<br><br>There clarity emerging on standards that are interoperable with one another for the VC format.<br><br>There is less clarity on the Exchange mechanisms.<br><br>One way that has been proposed to look at the exchange options available is to see them in different layers.",,https://iiw.idcommons.net/12F/_Credentials_Exchange_-_figuring_it_out_-_(Jello_Bowl_Death_Match%3F)_%E2%80%93,,Session Notes,,,Background,,,,,,"DIDComm, Verifiable Credential Exchange, Aries Protocol, Bloom Protocol, Presentation Exchange",,2021-05-06,,,,,,,,,,,,,
Exchange Protocols,CCG,,,Manu Sporny,,,,,,"chapi.io launches, includes VC playground","TL;DR: chapi.io is a site that helps developers integrate Verifiable Credential issuance, holding, and presentation into their applications. It includes a playground that can issue arbitrary VCs to digital wallets (web and native). It also includes tutorials on how Web Developers can add CHAPI integration to their websites. All you need to try it out is a web browser.",,https://lists.w3.org/Archives/Public/public-credentials/2022Jun/0055.html,,Discussion,,,CHAPI,,,,,,,,2022-06-27,,,,,,,,,,,,,
@ -632,7 +635,7 @@ OpenID Connect,IDCommons,,https://www.slideshare.net/TorstenLodderstedt/openid-c
OpenID Connect,IDCommons,,,David Waite,,,,,IIW,OpenID Connect: Session Management vs Privacy,"To recap:<br>* Front-channel logout is simple<br>* …but brittle and doesnt give good security guarantees<br>* Back-channel logout is robust<br>* …but difficult to implement/support, can still miss signals<br>* Session Management is useful for some apps<br>* …but is broken in many browsers<br>On their own independent schedules, all browsers have either broken or have plans to break state sharing via cross-site iframes to limit user tracking - arguably making the Session Management approach unusable.",,https://iiw.idcommons.net/11M/_OpenID_Connect:_Session_Management_vs_Privacy,,Session Notes,,,Development,,,,,,,,2021-05-06,,,,,,,,,,,,,
OpenID Connect,Auth0,,,,,,,,,"Identity, Unlocked... SIOP with Kristina Yasuda","As a discovery mechanism to invoke a Self-Issued OP, the discussion on the podcast covered the usage of a custom schema 'openid://'. Alternative mechanisms to address the limitations of custom schemas are being actively explored in the WG.<br><br>The conversation meanders through deeper details, from how the current [SIOP specification draft](https://bitbucket.org/openid/connect/src/master/openid-connect-self-issued-v2-1_0.md) under the OpenID Foundation picks up the mission from a [former attempt under DIF](https://identity.foundation/did-siop/) to encoding approaches for verifiable presentations (embedding in JWTs, [LD proofs](https://w3c-ccg.github.io/ld-proofs/), how to represent attributes",,https://auth0.com/blog/identity-unlocked-explained-season-2-ep-5/,https://images.ctfassets.net/23aumh6u8s0i/3v8k53STScYaDqv0oL1Fyd/373fa786764a8e6684d6c677a4e4bb88/identity-unlocked-hero.png,episode,,,Development,,,,,,,,2021-03-22,,,,,,,,,,,,,
OpenID Connect,SpruceID,,https://blog.spruceid.com/sign-in-with-ethereum-decentralizing-an-identity-provider-server/,,,,,,,Spruce Developer Update #20,We've set up a [release pipeline](https://github.com/spruceid/ens-oidc/) and had our first witnessed deployment for the ENS Community-Maintained OIDC IdP,,https://blog.spruceid.com/spruce-developer-update-20/,,Post,,,Development,,,,,,,,2022-06-01,,,,,,,,,,,,,
OpenID Connect,IETF,,,Sam Goto,,,,,,Browser APIs to enable OpenID Session Management and Privacy,"How does logout in OIDC happen?<br>* Classification problem - browsers do not know it is a logout now<br>* Easiest way<br * Browser asks for a user consent<br * Hard from a permission implementation perspective<br * Tim: No issues with this idea<br * If user logged into several OPs, user will not look to all the ones they log out from<br>* Option2<br * Browser classifies signing-in event<br * On log out does not prompt the user and IdP has no incentives to lie<br * RPs get to determine if they want to log the user out or not<br * Whether you can swap generic frame with fenced frame, frame can see its own cookies<br * May not be able to pass any parameters that you need to pass; no link decoration for framed frame<br * Subdomains also considered, but not well thought out<br * Logout URL - other option to add, but more work for RP: Resource metadata. Specification - not much adoption. It just feels like a place where RP metadata could be declared which could be useful in this context of the RP defining its metadata (e.g. what IDP it uses)",,https://iiw.idcommons.net/13L/_Browser_APIs_to_enable_OpenID_Session_Management_and_Privacy,,Session Notes,,,Development,,,,,,,,2021-05-06,,,,,,,,,,,,,
OpenID Connect,IETF,,,Sam Goto,,,,,,Browser APIs to enable OpenID Session Management and Privacy,"How does logout in OIDC happen?<br>* Classification problem - browsers do not know it is a logout now<br>* Easiest way<br> * Browser asks for a user consent<br> * Hard from a permission implementation perspective<br> * Tim: No issues with this idea<br> * If user logged into several OPs, user will not look to all the ones they log out from<br>* Option2<br> * Browser classifies signing-in event<br> * On log out does not prompt the user and IdP has no incentives to lie<br> * RPs get to determine if they want to log the user out or not<br> * Whether you can swap generic frame with fenced frame, frame can see its own cookies<br> * May not be able to pass any parameters that you need to pass; no link decoration for framed frame<br> * Subdomains also considered, but not well thought out<br> * Logout URL - other option to add, but more work for RP: Resource metadata. Specification - not much adoption. It just feels like a place where RP metadata could be declared which could be useful in this context of the RP defining its metadata (e.g. what IDP it uses)",,https://iiw.idcommons.net/13L/_Browser_APIs_to_enable_OpenID_Session_Management_and_Privacy,,Session Notes,,,Development,,,,,,,,2021-05-06,,,,,,,,,,,,,
KERI,Blockchain Bird,,https://iiw.idcommons.net/3K/_KERI_Q%26A_basic_introduction,,,,,,IIW32,KERI Q&A basic introduction,"It has lots of relevant links in it to start your journey in KERI.<br><br>What is KERI?<br>* Key Event Receipt Infrastructure<br>* Intends to repair the Internet<br>* KERI = CT with decentralized CA<br>* NOT a coin, token…<br><br>Why KERI? (and not something else)<br>* Strong autonomous identifiers<br>* Abiding to privacy (laws and good habits)<br>* Portability, delegation, rotatable keys<br>* Direct & Indirect method<br>* <theres more>",,https://blockchainbird.org/downloads/KERI-QA-introduction.pdf,,Presentation,,,Main,,,,,,,,2021,,,,,,,,,,,,,
KERI,DIF,,,,,,,,,"KERI: For every DID, a microledger","The world of digital identifiers (DIDs) and verifiable credentials (VCs) is evolving quickly, giving much cause for optimism. Standards are starting to connect and move towards functional interoperability, governed by testable protocols. Most of this work is happening on the level of VCs. However, DIDs and their infrastructure are also starting to converge and mature as an extensible-yet-interoperable technology.",,https://medium.com/decentralized-identity/keri-for-every-did-a-microledger-f9457fa80d2d,https://miro.medium.com/v2/resize:fit:1000/0*ZdrUkaJCemaCIBAw,Post,,,Main,,,,,,,,2020-10-19,,,,,,,,,,,,,
KERI,personal,,,Samuel Smith,,,,,,Key Event Receipt Infrastructure: A Secure Identifier Overlay for the Internet,Secure attribution of any communication to its source<br>Authentic communication<br>Authentic interactions based an secure attribution of all statements by participants<br>Verifiable authenticity of data<br>Data Provenance<br>Authentic data economy,,https://github.com/SmithSamuelM/Papers/blob/master/presentations/KERI_Overview.web.pdf,,Presentation,2.60,,Main,,,,,,,,2021-03-23,,,,,,,,,,,,,

1 main parent name supporting authors related location serving policy event title text description link image type status platform section sector industry market focus projects tech working group date github twitter youtube list feed discord crunchbase linkedin docs devtools app telegram forum
5 Standards ContinuumLoop Darrell O'Donnell Premature Standardization & Interoperability Here’s my premise – we don’t have standards nor interoperability – at least not as people really need. We have been through a process that is powerful and good – but what we have is what I call “premature standardization.” It’s a great start but nowhere near where things will be. Within the decentralized identity space its premature to think we have real Standardization & Interoperability https://www.continuumloop.com/premature-standardization-interoperability/ Post Standardization 2022-09-11
6 Standards Trinsic Anna Johnson Trinsic Basics: What Are SSI Standards? There are two kinds of standards that Trinsic implements to enable interoperability and avoid vendor lock-in: data model standards and protocol standards. Our engineering team ensures that the Trinsic platform is always based on the most recent SSI standards and protocols. https://trinsic.id/what-are-ssi-standards/ page Standardization 2020-11-12
7 Standards Scripting.com Dave Winer Manifesto: Rules for standards-makers I've used all kinds of formats and protocols in a long career as a software developer, even created a few. My new manifesto summarizes what I've learned about what works and what doesn't. http://scripting.com/2017/05/09/rulesForStandardsmakers.html Post Standardization 2017-05-08
8 Standards ContinuumLoop Darrell O'Donnell Why Engage with Standards? too many people complain about problems but don’t step to Fix It!. There are certainly a lot of flawed standards – but they make interoperability possible – not perfect – but possible. If you haven’t used them then you have no right to complain that they are too complex, too simple (even in the same standard) or too domain specific – or any of the other rants and raves that go on. <br><brIf 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. too many people complain about problems but don’t step to Fix It!. There are certainly a lot of flawed standards – but they make interoperability possible – not perfect – but possible. If you haven’t used them then you have no right to complain that they are too complex, too simple (even in the same standard) or too domain specific – or any of the other rants and raves that go on. <br><br>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. https://www.continuumloop.com/why-engage-with-standards/ Post Standardization 2013-09-28
9 Standards Forgerock Who Are the Identerati? - ForgeRock 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 the scenes at the Internet Identity Workshop (IIW), a bi-annual gathering of identity experts where we work on improving the identity systems that make the web run. It’s a great event that’s flown under the radar, so I’m excited to share a new documentary on IIW, “Not Just Who They Say We Are: Claiming our identity on the Internet”. This short film shines a light on the stealth community of “Identerati” at IIW that are defining and refining digital identity. 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 the scenes at the Internet Identity Workshop (IIW), a bi-annual gathering of identity experts where we work on improving the identity systems that make the web run. https://www.forgerock.com/blog/who-are-the-identerati Post Standardization 2017-03-22
10 Standards Wikipedia Who Runs the Internet? NO ONE PERSON, COMPANY, ORGANIZATION OR GOVERNMENT RUNS THE INTERNET.<BR>The Internet itself is a globally distributed computer network comprised of many volantarily interconnected autonomous networks. Similarly, its overnance is conducte by a decentralized and international multi-stakeholder network of interconnected autonomous groups drawing from civil society, the private sector, governments, the academic and research communities, and national and international organizations. They work cooperatively from their respective roles to create shared policies and standards that mantian the Internet's global interoperability for the public good. NO ONE PERSON, COMPANY, ORGANIZATION OR GOVERNMENT RUNS THE INTERNET.<br>The Internet itself is a globally distributed computer network comprised of many volantarily interconnected autonomous networks. Similarly, its overnance is conducte by a decentralized and international multi-stakeholder network of interconnected autonomous groups drawing from civil society, the private sector, governments, the academic and research communities, and national and international organizations. They work cooperatively from their respective roles to create shared policies and standards that mantian the Internet's global interoperability for the public good. https://es.wikipedia.org/wiki/Archivo:Who-Runs-the-Internet-graphic.png https://upload.wikimedia.org/wikipedia/commons/thumb/e/ed/Who-Runs-the-Internet-graphic.png/1024px-Who-Runs-the-Internet-graphic.png wiki entry Standardization 2013-01-31
11 Standards Hyperledger Identity Standards We hope to accumulate links here that talk to all Identity Standards work. Short updates form this will be used in the paper. Some are already input into the paper and need work polishing up. https://wiki.hyperledger.org/display/IWG/Identity+Standards wiki entry Decentralized Identity Stack Hyperledger Identity Working Group 2019-05-20
12 Standards CCG Mailing List Manu Sporny CCG Roadmap: Verifiable Trust Standards Green - General data format standards<br>Yellow - Vocabulary standards (I the mislabeled VC work)<brMagenta - Protocol standards (I mislabeled DID Resolution)<brRed - Low-level cryptographic primitives<brPurple - General crypto packaging/protocol standards<brOrange - Application layer standards Green - General data format standards<br>Yellow - Vocabulary standards (I the mislabeled VC work)<br>Magenta - Protocol standards (I mislabeled DID Resolution)<br>Red - Low-level cryptographic primitives<br>Purple - General crypto packaging/protocol standards<br>Orange - Application layer standards https://lists.w3.org/Archives/Public/public-credentials/2021Mar/0014.html https://lists.w3.org/Archives/Public/public-credentials/2021Mar/att-0014/VerifiableTrustStandards.png Discussion Decentralized Identity Stack Credentials Community Group 2021-03-03
13 Standards CCG Mailing List https://lists.w3.org/Archives/Public/public-credentials/2021Feb/att-0134/2021-Linked-Data-Security.pdf Manu Sporny CCG Linked Data Security The attached slide deck provides a basic overview (with examples) of Linked Data Security as well as the specifications in that orbit. The W3C CCG is  actively developing a number of these specifications. https://lists.w3.org/Archives/Public/public-credentials/2021Feb/0134.html Discussion Decentralized Identity Stack Credentials Community Group 2021-02-29
14 Standards arxiv A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems (NIST CYBERSECURITY WHITE PAPER) 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. JULY 9, 2019 https://arxiv.org/pdf/1908.00929.pdf Paper DRAFT Decentralized Identity Stack 2020-01-14
15 Standards Personal Tim Bouma Building Blocks for a New Architecture First, you will see the Issuer, Holder and Verifier. This is the archetypal pattern of the decentralized architecture. An issuer issues something to a holder, who then presents it to a verifier, who make a decision. A simple example: government(issuer) issues you a passport (holder), which you present to a border control officer (verifier) who lets you through the gate. When you look at all the use cases (described above), they all fall into this pattern. https://i.imgur.com/qGXEnW1.png Note: These are my opinions only, and not that of my employer. All information used in developing this post is open and freely available. No statements should be considered as advice or representing… https://medium.com/@trbouma/building-blocks-for-a-new-architecture-fda2238ac005 Post Decentralized Identity Stack 2019-09-23
17 Standards DIF https://gist.github.com/creatornader/c8a20c534d3cf8f65a9b34ce2ad81725 Nader Helmy Overview of Decentralized Identity Standards we can think of each specification as addressing one or more of the SSI “building blocks” that we described above. In some cases a standard may be a bridge between layers, enabling a closer link between connections, data, and keys, making the ecosystem more secure as a whole. What you will find below is a list of all relevant standards, links to every specification, the organizations they belong to, their relationship to the ecosystem, and their relative maturity as internet technologies. There are a number of organizations working towards standardization of technologies that span across the web. Of these, there are a handful of umbrella organizations that are particularly important… https://medium.com/decentralized-identity/overview-of-decentralized-identity-standards-f82efd9ab6c7 https://miro.medium.com/v2/resize:fit:1000/1*oDeFSKBXhWkltGqXZ82yDA.png Post Decentralized Identity Stack 2020-03-02
18 Standards SSIMeetup.org https://www.youtube.com/watch?v=RllH91rcFdE Drummond Reed Evernym The Story of Open SSI Standards Drummond Reed, Chief Trust Officer at Evernym and Sovrin Foundation Trustee, features in our first Webinar “The Story of SSI Open Standards” by giving us the background on the foundation of Self Sovereign Identity. Drummond explains the technical and development aspects of DIDs, DKMS, DID Auth and Verifiable Credentials that will make Self Sovereign Identity possible. https://ssimeetup.org/story-open-ssi-standards-drummond-reed-evernym-webinar-1/ https://imgur.com/6MLNgXal.png Presentation Decentralized Identity Stack 2018-04-27
19 Standards DIF SSI Architectural Stack and Community Efforts Overview While a more thorough (and competitive) separation of concerns might slice today’s and tomorrow’s identity systems into more modular and interchangeable parts at many more layers, the diagram used here organizes the space into just three broad divisions, which map roughly to the bottom three in the mapping dominant in the Aries & ToIP communities. For a more detailed and complex mapping, see the forthcoming map by the DIF interoperability working group. https://github.com/decentralized-identity/interoperability/blob/master/assets/ssi-architectural-stack--and--community-efforts-overview.pdf infographic Decentralized Identity Stack 2020-09-23
20 Verifiable Credentials,Standards Personal Kristina Yasuda VC spec map Distributed ID Learning Path There is a lot of information about decentralized IDs on the web. I struggled too. (I still do that lol)<BR><BR>There are many standards for decentralized identities, and they are interdependent and interrelated, as you can see from the diagram below. There is a lot of information about decentralized IDs on the web. I struggled too. (I still do that lol)<br><br>There are many standards for decentralized identities, and they are interdependent and interrelated, as you can see from the diagram below. Describes pre-requisite knowledge, including JSON, JSON-LD, JWT, JWS, JWK, JWA, and sometimes CBOR. She then goes on to break down knowledge areas beginning with the basics: DID-Core, DID-Resolution, DID-Spec, DID Use-Cases. Next, she covers Verifiable Credentials with VC-Data Model, VC Use-Cases, and VC-Implementors Guide, and also Transport, Credential Presentation, and Other Data Formats. https://translate.google.com/translate?sl=auto&tl=en&u=https://kristinayasuda.com/posts/decentralized-identity-catch-up-path/ https://images.ctfassets.net/iifz0jg6o9rt/1frepoi3bOWvEZOIAKlWkC/de5013e3d77fc29ce3c19a3a532c603d/IBO_WebUI.JPG Post Interoperability, Decentralized Identity Stack 2020-12-09
21 Standards WebOfTrustInfo RWoT Recommendations for Decentralized Key Management Systems A decentralized key management system (DKMS) aims to solve how consumers can manage their own keys and certificates without relying on a third-party provider having access or controls over the keys.. This method helps to ensure that no third-party can compromise the integrity and security of the system as a whole. Entities can use the system to safely authenticate each other and validate keys and certificates. Centralized key management systems (CKMS) manage key and certificate creation, signing, and validity. Specific problems arise when these authorities become unavailable, or the data they control becomes corrupted or known. Central authorities often become choice targets for attackers. This document proposes to meet these requirements with a decentralized blockchain ledger for providing an oracle of trust and leave control over all keys with end users. The use of a blockchain permits globally readable identifiers and public data to be shared in a secure manner that is not vulnerable to the man-in-the-middle attack or system wide compromise and permits consumers to be self-sovereign. This leaves consumers with the task of key management and protection. This document covers various ideas for how users may create, recover, backup, and revoke keys and provides recommended suggestions. https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/topics-and-advance-readings/dkms-recommendations.md Paper Decentralized Identity Stack 2017-09-15
22 Standards SSIMeetup.org https://www.slideshare.net/SSIMeetup/decentralized-key-management-dkms-an-essential-missing-piece-of-the-ssi-puzzle-drummond-reed Drummond Reed DKMS - An Essential Missing Piece of the SSI Puzzle DKMS inverts a core assumption of conventional PKI (public key infrastructure) architecture, namely that public key certificates will be issued by centralized or federated certificate authorities (CAs). With DKMS, the initial “root of trust” for all participants is any blockchain or distributed ledger that supports DIDs. This webinar will explain why we need DKMS, what a DKMS-compatible identity wallet looks like, how DKMS can solve some longstanding problems in wallet backup and recovery, and where DKMS is headed for standardization. If you can't manage the keys for your DIDs (Decentralized Identifiers), then the SSI engine will never get started. That's why DKMS (Decentralized Key Management System) is one of the core open standards in the DID "stack". http://ssimeetup.org/decentralized-key-management-dkms-essential-missing-piece-ssi-puzzle-drummond-reed-webinar-8/ https://i.imgur.com/5qc1qrG.png Presentation Decentralized Identity Stack 2018-06-28
23 Verifiable Credentials Wikipedia Verifiable Credentials - Wikipedia Verifiable credentials (VCs) are the electronic equivalent of the physical credentials that we all possess today, such as: plastic cards, passports, driving licences, qualifications and awards, etc. The data model for verifiable credentials is a World Wide Web Consortium Recommendation, "Verifiable Credentials Data Model 1.0 - Expressing verifiable information on the Web" published 19 November 2019. https://en.wikipedia.org/wiki/Verifiable_credentials https://upload.wikimedia.org/wikipedia/commons/thumb/5/51/VC_triangle_of_Trust.svg/1200px-VC_triangle_of_Trust.svg.png wiki entry About 2023-04-25
44 Verifiable Credentials IDCommons Grace Rachmany IIW Could an NFT be a VC? Case discussed: A group of villages in Africa using a cryptocurrency platform for alternative currencies. Different organizations issue the coins under different circumstances. When you accept a currency, you want to know who is the issuer. The Red Cross might be more or less trusted than the local leader or agricultural cooperative as the issuer of a currency that is supposedly equivalent to a shilling.<br><br>What types of tech could be used for this?<br><br>- Multiple currencies on the blockchains<br>- Certifications in the form of some kind of NFT issued by the issuer.<br>- Limited supply tokens or NFTs that are “expired” when you use them<br>- Open Credential Publisher framework was suggested<br>- VCs are generally authorizations associated with a person, so maybe a person could have the VC and show their credit rating in some way while they are making a transaction<br>- Similarly maybe the VC belongs to the organization that is issuing the coin, proving its reputation over time. https://iiw.idcommons.net/20I/_Could_an_NFT_be_a_VC%3F Session Notes Comparisons 2021-05-06
45 Verifiable Credentials Personal Timothy Ruff How does VC Functional Stack compare to #ToIP Stack? 1. ToIP Layers 2 & 3 compare to Functional Layer 2<br>2. ToIP Layer 4 compares to Functional Layers 3 & 4 (horizontal layer for VC Management, vertical layer for Applications)<br>3. Functional stack doesn't require #blockchain<br>4. Functional Stack doesn't detail steps for trust or verification; ToIP Stack doesn't separate management or storage<br>5. Functional Stack clarifies functions, roles, and potential business models; ToIP stack clarifies trust & security They are complementary, not contradictory. https://twitter.com/rufftimo/status/1301314001251438593 https://i.imgur.com/8zakrMQ.png Thread Comparisons 2020-09-03
46 Verifiable Credentials CCG Mailing List Michael Herman CCG What are VCs similar to? The chip in your e-passport is the analogy I’ve been most successful with<br>An issuer gives it to you.<br>You carry it around and show to whom you choose<br>The verifier can check its integrity without contacting the issuer<br>“A VC is like the chip in your passport - bit for any document type”<br>So far the best analogy I’ve found.  Policy makers say “ah, I see” https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0338.html Discussion Comparisons Credentials Community Group 2021-08-23
47 Verifiable Credentials fossandcrafts Hygiene for a computing pandemic This episode of FOSS and Crafts features Christopher Lemmer Webber discussing the object capability security approach. Its a generalization not specific to VCs, continuing from the conversation on the CCG mailinglist, [Hygiene for a computing pandemic: separation of VCs and ocaps/zcaps](https://lists.w3.org/Archives/Public/public-credentials/2020Dec/0028.html), we shared last month.<br This episode of FOSS and Crafts features Christopher Lemmer Webber discussing the object capability security approach. Its a generalization not specific to VCs, continuing from the conversation on the CCG mailinglist, [Hygiene for a computing pandemic: separation of VCs and ocaps/zcaps](https://lists.w3.org/Archives/Public/public-credentials/2020Dec/0028.html), we shared last month.<br> The podcast *show-notes include an epic list of references* supporting the discussion. https://fossandcrafts.org/episodes/20-hygiene-for-a-computing-pandemic.html Post Comparisons 2021-01-03
48 Verifiable Credentials Personal https://lists.w3.org/Archives/Public/public-credentials/2021Jun/0244.html Kyle Den Hartog, Manu Sporny Re: The dangers of using VCs as permission tokens (was: PROPOSALs for VC HTTP API call on 2021-06-22) Agreed, when it comes to the number of checks that occur it's much greater<brbecause of the delegation. With that in mind, looking at the semantics only<brof the system VCs in my opinion weren't optimally designed for permission<brtokens. This difference between the two requires that an implementation<brthat wants to support both claims tokens and permissions tokens has to<brgrapple with the different mental model that arise when trying to stuff<brthese things together. This introduces additional complexity. Additionally<brit leads to weird statements that are being made where it's difficult to<brtell if the VC is behaving like a claims token or a permissions token.<br><br>Yes, exactly this. Exactly what Kyle states above is the reason why it's so complicated (and thus dangerous) to use VCs as permissions tokens.<br><br>This is one of the primary reasons that we separated out the Authorization Capabilities work from the Verifiable Credentials work. Things get really complicated when you start mixing authz/authn/claims/permissions into a Verifiable Credential. Just because you can do it doesn't mean you should Agreed, when it comes to the number of checks that occur it's much greater<br>because of the delegation. With that in mind, looking at the semantics only<br>of the system VCs in my opinion weren't optimally designed for permission<br>tokens. This difference between the two requires that an implementation<br>that wants to support both claims tokens and permissions tokens has to<br>grapple with the different mental model that arise when trying to stuff<br>these things together. This introduces additional complexity. Additionally<br>it leads to weird statements that are being made where it's difficult to<br>tell if the VC is behaving like a claims token or a permissions token.<br><br>Yes, exactly this. Exactly what Kyle states above is the reason why it's so complicated (and thus dangerous) to use VCs as permissions tokens.<br><br>This is one of the primary reasons that we separated out the Authorization Capabilities work from the Verifiable Credentials work. Things get really complicated when you start mixing authz/authn/claims/permissions into a Verifiable Credential. Just because you can do it doesn't mean you should https://kyledenhartog.com/example-authz-with-VCs/ Post Comparisons 2021-06-24
49 Verifiable Credentials Personal Kyle Den Hartog Comparing VCs to ZCAP-LD Why make the investment then to put the time and effort into ZCAPs when we’ve already got VCs? Simply put because security is hard and trying to push square pegs into round holes often times leads to bugs which are elevated to mission critical authentication/authorization bypass vulnerabilities. By designing around a fit for purpose data model with a well defined problem being solved it allows for us to be much more precise about where we believe extensibility is important versus where normative statements should be made to simplify the processing of the data models. By extension this leads to a simpler security model and likely a much more robust design with fewer vulnerabilities. https://kyledenhartog.com/comparing-VCs-with-zcaps/ Post Comparisons 2021-09-25
50 Verifiable Credentials CCG Mailing List Dave Longley CCG Re: VCs - zCaps / OCap a Discussion TL; DR: My current view is that the main confusion here may be over the difference between VCs and LD Proofs, not VCs and ZCAPs. VCs are not a generalized container for attaching a cryptographic proof to a document. That's what LD proofs (or JOSE style proofs) are for. VCs *use* LD proofs (or JOSE style proofs) to attach an assertion proof to a document that specifically models statements made by an issuer about some subject, which is therefore inherently about the identity of that subject https://lists.w3.org/Archives/Public/public-credentials/2020Dec/0027.html Discussion Comparisons Credentials Community Group 2020-12-05
51 Verifiable Credentials W3C Verifiable Credentials Working Group https://www.w3.org/2020/01/vc-wg-charter.html Verifiable Credentials Working Group The mission of the Verifiable Credentials (formerly known as 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.<br><br>The Chairs of the Working Group are Kristina Yasuda and Brent Zundel. The W3C Staff Contact for the Working Group is Ivan Herman. https://www.w3.org/2017/vc/WG/ Working Group Working Group 2017-04-14 https://github.com/w3c/verifiable-claims https://lists.w3.org/Archives/Public/public-vc-wg/ https://lists.w3.org/Archives/Public/public-vc-wg/
52 Verifiable Credentials VCWG Manu Sporny Verifiable Credentials Data Model v1.1 is an official W3C standard! It's official, the Verifiable Credentials Data Model v1.1 is a W3C standard!<br><br Verifiable Credentials Data Model v1.1<br https://www.w3.org/TR/2022/REC-vc-data-model-20220303/<br><br>This was largely a maintenance release of the specification. The list of (minor) revisions since the v1.0 release can be found here:https://www.w3.org/TR/2022/REC-vc-data-model-20220303/#revision-history It's official, the Verifiable Credentials Data Model v1.1 is a W3C standard!<br><br> Verifiable Credentials Data Model v1.1<br> https://www.w3.org/TR/2022/REC-vc-data-model-20220303/<br><br>This was largely a maintenance release of the specification. The list of (minor) revisions since the v1.0 release can be found here:https://www.w3.org/TR/2022/REC-vc-data-model-20220303/#revision-history https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0005.html Specificationification Working Group Credentials Community Group 2022-03-03
53 Verifiable Credentials VCWG Verifiable Credentials Data Model v1.1 Credentials are a part of our daily lives; driver's licenses are used to assert that we are capable of operating a motor vehicle, university degrees can be used to assert our level of education, and government-issued passports enable us to travel between countries. This specification provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable. Driver's licenses are used to claim that we are capable of operating a motor vehicle, university degrees can be used to claim our education status, and government-issued passports enable holders to travel between countries. This specification provides a standard way to express these sorts of claims on the Web in a way that is cryptographically secure, privacy respecting, and automatically verifiable. https://www.w3.org/TR/2022/REC-vc-data-model-20220303/ https://www.w3.org/TR/2022/REC-vc-data-model-20220303/diagrams/ecosystem.svg Specificationification RECOMMEND Working Group Verifiable Credentials Working Group 2022-03-03
54 Verifiable Credentials VCWG Verifiable Credentials Data Model v2.0 - The components that constitute a [verifiable credential](https://www.w3.org/TR/2022/WD-vc-data-model-2.0-20220811/%23dfn-verifiable-credentials) Credentials are a part of our daily lives; driver's licenses are used to assert that we are capable of operating a motor vehicle, university degrees can be used to assert our level of education, and government-issued passports enable us to travel between countries. This specification provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable. https://www.w3.org/TR/vc-data-model-2.0/ https://www.w3.org/TR/vc-data-model-2.0/diagrams/zkp-cred-pres.svg Specificationification DRAFT Working Group Verifiable Credentials Working Group 2023-05-20
55 Verifiable Credentials VCWG Verifiable Credential Data Integrity 1.0 This specification describes mechanisms for ensuring the authenticity and integrity of Verifiable Credentials and similar types of constrained digital documents using cryptography, especially through the use of digital signatures and related mathematical proofs. https://www.w3.org/TR/vc-data-integrity/ https://www.w3.org/TR/vc-data-integrity/diagrams/hiw-verification.svg Specification Working Draft Working Group Cryptography Verifiable Credentials WG 2023-05-15
102 Verifiable Credentials DIF https://github.com/decentralized-identity/vc-spec-map/releases/tag/v1.2.0 Michael Ruminer Verifiable Credentials Specification Relationships diagrams and documentation on the relationship of verfiable credential specifications<br><br>The current release contains some of the most core specifications and their related specs in a diagram. It does not yet address some of the items especially under DIF work groups for secure data storage, SIOP, Sidetree etc. "Good for anyone but especially useful when trying to jump in on the deep end. If you walk even this limited tree of specs you know a lot" - @michaelruminer https://github.com/decentralized-identity/vc-spec-map http://decentralized-id.com/images/VC-spec-map.webp infographic Interoperability 2021-05-27
103 Verifiable Credentials Evernym Brent Zundel Why the Verifiable Credentials Community Should Converge on BBS+ BBS+ LD-Proofs use JSON-LD schemas, so credentials that use them can have a rich, hierarchical set of attributes. Instead of the heavy-handed mechanism for the encoding and canonicalization of attributes values that we’d imagined for Rich Schemas, they use RDF canonicalization and a hash function. Rather than expanding the credential definition, they discarded it, taking advantage of some properties of BBS+ keys which allow for deterministic expansion. BBS+ ZKP signatures: The breakthrough the industry has been looking for to converge on a universal format for privacy-respecting VCs. https://www.evernym.com/blog/bbs-verifiable-credentials/ Post Varieties 2021-03-24
104 Verifiable Credentials Personal Steve Lockstep The original #VerifiableCredentials were PKI-based SIM cards and EMV cards. These bind key pairs to individuals, and to signed assertions (account numbers) to deliver provenance, fidelity and proof of possession. [https://constellationr.com/blog-news/not-too-much-identity-technology-and-not-too-little](https://constellationr.com/blog-news/not-too-much-identity-technology-and-not-too-little)<br>$5 https://twitter.com/Steve_Lockstep/status/1419935186188341249 https://i.imgur.com/ucAVxCX.png tweet Varieties 2021-06-27
105 Verifiable Credentials CCG Mailing List Anil John CCG FYI >> DHS W3C VC/DID Implementation Profile: Credential Data Model Representation Syntax & Proof Format We are walking this path step-by-step by documenting the results and lessons from the DHS sponsored multi-platform, multi-vendor interoperability plug-fests and other rigorous plug-fests with similar goals to develop a “DHS Implementation Profile of W3C Verifiable Credentials and W3C Decentralized Identifiers” to ensure the use of Security, Privacy and Interoperability implementation choices that are acceptable to the USG such that these capabilities can be deployed on and connect to USG networks and infrastructure.<br … please [find attached the DHS Implementation Profile](https://lists.w3.org/Archives/Public/public-credentials/2022Sep/att-0253/DHS.W3C.VC-DID.Implemenation.Profile-20220929-SHARE.pdf) of W3C VCs and W3C DIDs normative guidance on:<br - Credential Data Model Representation Syntax<br - Credential Data Model Proof Format We are walking this path step-by-step by documenting the results and lessons from the DHS sponsored multi-platform, multi-vendor interoperability plug-fests and other rigorous plug-fests with similar goals to develop a “DHS Implementation Profile of W3C Verifiable Credentials and W3C Decentralized Identifiers” to ensure the use of Security, Privacy and Interoperability implementation choices that are acceptable to the USG such that these capabilities can be deployed on and connect to USG networks and infrastructure.<br> … please [find attached the DHS Implementation Profile](https://lists.w3.org/Archives/Public/public-credentials/2022Sep/att-0253/DHS.W3C.VC-DID.Implemenation.Profile-20220929-SHARE.pdf) of W3C VCs and W3C DIDs normative guidance on:<br> - Credential Data Model Representation Syntax<br> - Credential Data Model Proof Format https://lists.w3.org/Archives/Public/public-credentials/2022Sep/0253.html Discussion Interoperability Credentials Community Group 2022-09-29
106 Verifiable Credentials DIF Interoperability Mapping Exercise The archive and information hub for the cross-community interoperability project. Focus is on education and familiarity for various efforts across multiple groups for interoperable decentralized identity infrastructure. https://github.com/decentralized-identity/interoperability/blob/master/assets/interoperability-mapping-exercise-10-12-20.pdf https://i.imgur.com/QvpMl6M.png infographic Interoperability 2020-10-13
107 Verifiable Credentials Github creatornader Decentralized Identity Standards.md Decentralized Identifiers (DIDs), Decentralized Identifier (DID) Resolution, DID Spec Registries, DID Use Cases, DID Rubric, DID Key, DID Web, WebCrypto, WebAuthn, WebKMS, Verifiable Credentials (VCs), VC Use Cases, VC JSON Schemas, Credential Revocation List, Credential Handler API (CHAPI), Verifiable Presentation Request, JSON Linked Data (JSON-LD), CBOR Linked Data (CBOR-LD), Authorization Capabilities (ZCAP-LD), Linked Data Security Vocab, Linked Data Citizenship Vocab, Linked Data Traceability Vocab, Linked Data Cryptographic Suite Registry, Linked Data Proofs, Linked Data Proofs BBS+ Signatures, Universal Wallet, Encrypted Data Vaults (EDVs), Data Privacy Vocabulary, Data Minimization, ActivityPub, Confidential Storage, DID Peer, DIDComm Messaging, Well Known DID Configuration, Self-Issued DID Profile for OpenID, Verifiable Presentation Exchange, Identity Hubs, Credential Manifest, Sidetree, Key Event Receipt Infrastructure (KERI), OAuth 2.0, Grant Negotiation Access Protocol (GNAP), JWA/JWK, JWT/JWS/JWE, JSON Web Message (JWM), HTTP Signatures, Hashlink, BBS+ Signatures Scheme, Biometric Service Providers (BSPs), Aries RFCs, Interop Test Suite, The Trust Over IP (ToIP) Stack, Rich Schemas, Chained Credentials, Data Overlays, Data Consent Lifecycle, Indirect Identity Control, Anoncreds, Machine-Readable Trust Frameworks, Decentralized Key Management System (DKMS), eXtensible Data Interchange (XDI), OpenID Connect (OIDC), OIDC Credential Provider, User-Managed Access (UMA) 2.0, Consent Receipts, Blinding Identity Taxonomy (BIT) https://gist.github.com/creatornader/c8a20c534d3cf8f65a9b34ce2ad81725 gist Interoperability 2020-11-25
108 Verifiable Credentials Personal Samuel Smith VC Spec Enhancement Proposal the VC standard appears to be an adoption vector for Linked Data, not the other way around. My overriding interest is that the concept of a VC as a securely attributable statement is a very powerful and attractive one and therefore should be widely adopted. We should therefore be picking the best technologies that best support broad VC adoption, not the other way around. https://github.com/SmithSamuelM/Papers/blob/master/whitepapers/VC_Enhancement_Strategy.md Paper Literature 2022-04-04
123 Verifiable Credentials IDCommons Mahmoud Alkhraishi IDCommons IIW Verifiable Credentials for Assets General Framework on how to think of VCs for Assets including leveraging GS1 and other vocabularies in the traceability vocab.<br><br>Requirements and Opportunities that block adoption of VCs in Supply chains https://iiw.idcommons.net/21E/_Verifiable_Credentials_for_Assets_30_min Session Notes Use Case 2021-05-07
124 Verifiable Credentials Trusted Digital Web Using Paper-based Structured Credentials to Humanize Verifiable Credentials User Scenario: ABC Grocery wants to use the Trusted Digital Web to issue a Purchase Order for 10 cabbages from David's Cabbages. Michael Herman User Scenario: ABC Grocery wants to use the Trusted Digital Web to issue a Purchase Order for 10 cabbages from David's Cabbages.This tutorial was inspired by... https://www.youtube.com/watch?v=kM30pd3w8qE Video Rough Cut User Experience 2021-11-19
125 Verifiable Credentials WebofTrustInfo Manu Sporny RWoT Rendering Verifiable Credentials This paper explores ways in which the Verifiable Credentials data model could be extended to support visual, audio, and physical renderings for Verifiable Credentials. https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/advance-readings/rendering-verifiable-credentials.md Paper User Experience 2022-07-17
126 Verifiable Credentials Personal Pamela Dingle Thread: VCs need Threat Modeling Another pre-read recommendation for @identiverse: the @openid for Verifiable Credentials Whitepaper.<br>* [Firstyear Replying to @Erstejahre @pamelarosiedee and 4 others](https://twitter.com/Erstejahre/status/1537615778106658816) "It also seems to lack any sections about threat modelling and possible risks, making it hard to trust since risks are not directly and clearly addressed."<BR>* [Torsten Lodderstedt Replying to @Erstejahre @pamelarosiedee and 3 others](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics) "I agree. We [threat] model while we are designing the protocol, we also need to add it to the spec. Please note: we build on existing work. There is an extensive thread model for OAuth and countermeasures that we built on ([datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics). Feel free to contribute." Another pre-read recommendation for @identiverse: the @openid for Verifiable Credentials Whitepaper.<br>* [Firstyear Replying to @Erstejahre @pamelarosiedee and 4 others](https://twitter.com/Erstejahre/status/1537615778106658816) "It also seems to lack any sections about threat modelling and possible risks, making it hard to trust since risks are not directly and clearly addressed."<br>* [Torsten Lodderstedt Replying to @Erstejahre @pamelarosiedee and 3 others](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics) "I agree. We [threat] model while we are designing the protocol, we also need to add it to the spec. Please note: we build on existing work. There is an extensive thread model for OAuth and countermeasures that we built on ([datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics). Feel free to contribute." https://twitter.com/pamelarosiedee/status/1537233243086327812?s%3D20%26t%3DWWt14_H4AXgtn09xb5-yew Thread Critique 2022-06-16
127 Decentralized Identifiers CCG A Primer for Decentralized Identifiers An introduction to self-administered identifiers for curious people A Decentralized Identifier (DID) is a new type of identifier that is globally unique, resolvable with high availability, and cryptographically verifiable. DIDs are typically associated with cryptographic material, such as public keys, and service endpoints, for establishing secure communication channels. DIDs are useful for any application that benefits from self-administered, cryptographically verifiable identifiers such as personal identifiers, organizational identifiers, and identifiers for Internet of Things scenarios. For example, current commercial deployments of W3C Verifiable Credentials heavily utilize Decentralized Identifiers to identify people, organizations, and things and to achieve a number of security and privacy-protecting guarantees. This document is an introduction to the concept of Decentralized Identifiers. https://w3c-ccg.github.io/did-primer/ https://w3c-ccg.github.io/did-primer/did-primer-diagrams/urn-format.png Report Main Credentials Community Group 2021-11-11 https://github.com/w3c-ccg/did-primer
128 Decentralized Identifiers W3C Markus Sabadello Danube Tech, Sovrin Foundation, OASIS XDI TC Vienna W3C Workshop on Privacy and Linked Data Decentralized IDentifers (DIDs) - Developed at Rebooting-the-Web-of-Trust workshop and W3C Credentials CG<br>- Persistent, dereference-able, cryptographically verifable identifers<br>- Registered in a blockchain or other decentralized network https://www.w3.org/2018/vocabws/presentations/Sabadello.pdf https://i.imgur.com/7NRcJbq.png Presentation Main 2018-04-17
129 Decentralized Identifiers Identity Foundation Decentralized Identifiers (DID) 1.0 specification approved as W3C Recommendation Announcing the [Decentralized Identifiers (DID) v1.0 specification](https://www.w3.org/TR/did-core/) as an open web standard signals that it is technically sound, mature, and ready for widespread adoption. Having an established v1.0 specification allows work to continue with renewed energy and focus, not only at the many groups meeting at DIF, but across the digital identity community. The W3C has approved the DIDCore V1.0 spec as an official Recommentdation; DIDs are now an open web standard ready for use and further development https://blog.identity.foundation/w3cdidspec-2/ Post Main 2022-06-22
160 Decentralized Identifiers IDCommons https://iiw.idcommons.net/13D/_We_evaluated_7_DID_methods_with_the_W3C_DID_Rubric!_did:btcr,_did:sov,_did:ion,_did:web,_did:key,_did:peer,_did:ethr Walid Fdhila, Markus Sabadello did:btcr, did:sov, did:ion, did:web, did:key, did:peer, did:ethr, Decentralized Identifiers IIW DID Methods Evaluation Report This report evaluates a selection of DiD methods using the guidelines specified in the W3C DiD method Rubric V1.0 (draft 06 January 2021). The evaluation reflects the authors’ opinion based on documents and source code that are publicly available. The report mainly includes a comprehensive evaluation. Web word processing, spreadsheets and presentations https://docs.google.com/document/d/1jP-76ul0FZ3H8dChqT2hMtlzvL6B3famQbseZQ0AGS8// Report About DID Methods 2021-04-04
161 Decentralized Identifiers IDCommons https://iiw.idcommons.net/13D/_We_evaluated_7_DID_methods_with_the_W3C_DID_Rubric!_did:btcr,_did:sov,_did:ion,_did:web,_did:key,_did:peer,_did:ethr Walid Fdhila, Markus Sabadello Decentralized Identifiers IIW Critera for DID Method Evaluation The criteria selected for did evaluation are derived from (i) did rubric and (ii) principles of SSI.<br>(i) https://w3c.github.io/did-rubric/<br>(ii) https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/self-sovereign-identity-principles.md https://docs.google.com/document/d/1vAKtMrsrjO_tLQhah8tRoLaIS7HpOIE6xM38ZoBpgWU/ https://lh3.googleusercontent.com/docs/ADP-6oGo4pZN6hzrDT7Ac5x4QQp6fiOaI5VvfXK6lrPstUV7ugHLmwFd2--hUy7QXjnSqEA_uz6CCgQz71VrxM-DnIiJGz9wR0k4QnknbocdcTn4=w1200-h630-p Guidance About DID Methods 2021-05
162 Decentralized Identifiers ArcBlock did:abt: did:abt: One of our main goal is to protect users’ privacy. So people do not use the DID generated from their master key to talk to DAPPs, instead, the WALLET automatically generates an extended DID according to the user’s master DID and the DAPP’s DID and use this extended DID to communicate with the DAPP. ABT DID Protocol https://arcblock.github.io/abt-did-spec/ Specification ABT Network The DID Methods 2019-10-11 https://github.com/arcblock/abt-did-spec/
163 Decentralized Identifiers CCG did:btcr: Christopher Allen, Ryan Grant, Kim Hamilton Duffy did:btcr: The Bitcoin Reference DID method (did:btcr) supports DIDs on the public Bitcoin blockchain. The Bitcoin Reference method has minimal design goals: a DID trust anchor based on the Bitcoin blockchain, updates publicly visible and auditable via Bitcoin transactions, and optionally, additional DID Document information referenced in the transaction OP_RETURN data field. No other Personal Identifiable Information (PII) would be placed on the immutable blockchain.<brA secondary intent of the BTCR method is to serve as a very conservative, very secure example and some best practices for creating a DID method. The use cases for BTCR are focused on anonymous and pseudo-anonymous identities, web-of-trust style webs of identity, and absolute mimimal personal information disclosure. Other DID methods will likely need to loosen these standards.<brSome aspects of the BTCR method will not be practical if inappropriately scaled — for instance, there is a transaction cost to update keys and DDO object, potential UTXO inflation (i.e. one additional unspent output for every BTCR-based identity), and even if segwit isn’t used it could cause blockchain bloat. However, identities using the BTCR method can be a strong as Bitcoin itself -- currently securing billions of dollars of digital value. The Bitcoin Reference DID method (did:btcr) supports DIDs on the public Bitcoin blockchain. The Bitcoin Reference method has minimal design goals: a DID trust anchor based on the Bitcoin blockchain, updates publicly visible and auditable via Bitcoin transactions, and optionally, additional DID Document information referenced in the transaction OP_RETURN data field. No other Personal Identifiable Information (PII) would be placed on the immutable blockchain.<br>A secondary intent of the BTCR method is to serve as a very conservative, very secure example and some best practices for creating a DID method. The use cases for BTCR are focused on anonymous and pseudo-anonymous identities, web-of-trust style webs of identity, and absolute mimimal personal information disclosure. Other DID methods will likely need to loosen these standards.<br>Some aspects of the BTCR method will not be practical if inappropriately scaled — for instance, there is a transaction cost to update keys and DDO object, potential UTXO inflation (i.e. one additional unspent output for every BTCR-based identity), and even if segwit isn’t used it could cause blockchain bloat. However, identities using the BTCR method can be a strong as Bitcoin itself -- currently securing billions of dollars of digital value. https://w3c-ccg.github.io/didm-btcr/ https://w3c-ccg.github.io/didm-btcr/diagrams/btcr-tx-ref.png Specification Bitcoin The DID Methods 2019-08-08
164 Decentralized Identifiers Blockstack did:stack: Jude Nelson did:stack: Blockstack's DID method is specified as part of its decentralized naming system. Each name in Blockstack has one or more corresponding DIDs, and each Blockstack DID corresponds to exactly one name -- even if the name was revoked by its owner, expired, or was re-registered to a different owner.<br>Blockstack is unique among decentralized identity systems in that it is not anchored to a specific blockchain or DLT implementation. The system is designed from the ground up to be portable, and has already been live-migrated from the Namecoin blockchain to the Bitcoin blockchain. The operational ethos of Blockstack is to leverage the must secure blockchain at all times -- that is, the one that is considered hardest to attack.<br>Blockstack's naming system and its DIDs transcend the underlying blockchain, and will continue to resolve to DID document objects (DDOs) even if the system migrates to a new blockchain in the future. https://github.com/blockstack/blockstack-core/blob/stacks-1.0/docs/blockstack-did-spec.md Specification Bitcoin, Namecoin, Portable The DID Methods 2019-07-19
165 Decentralized Identifiers WebofTrustInfo did:erc725: Markus Sabadello, Fabian Vogelsteller, Peter Kolarov rwot06 did:erc725: Decentralized Identifiers (DIDs, see [1]) are designed to be compatible with any distributed ledger or network (called the target system). In the Ethereum community, a pattern known as ERC725 (see [2]) utilizes smart contracts for standard key management functions. We propose a new DID method that allows ERC725 identities to be treated as valid DIDs. One advantage of this DID method over others appears to be the ability to use the full flexibility of Ethereum smart contracts for key management purposes. https://github.com/WebOfTrustInfo/rwot6-santabarbara/blob/master/topics-and-advance-readings/DID-Method-erc725.md Specification Ethereum The DID Methods ERC725 2018-02-21
166 Decentralized Identifiers DIDWG did:example: did:example: A DID is a simple text string consisting of three parts, the:<br>- URI scheme identifier (did)<br>- Identifier for the DID method<br>- DID method-specific identifier.<br**EXAMPLE 1: A simple example of a decentralized identifier (DID)**<code>did:example:123456789abcdefghi</code><br>The example DID above resolves to a DID document. A DID document contains information associated with the DID, such as ways to cryptographically authenticate the DID controller, as well as services that can be used to interact with the DID subject. A DID is a simple text string consisting of three parts, the:<br>- URI scheme identifier (did)<br>- Identifier for the DID method<br>- DID method-specific identifier.<br>**EXAMPLE 1: A simple example of a decentralized identifier (DID)**<code>did:example:123456789abcdefghi</code><br>The example DID above resolves to a DID document. A DID document contains information associated with the DID, such as ways to cryptographically authenticate the DID controller, as well as services that can be used to interact with the DID subject. https://w3c.github.io/did-core/#a-simple-example https://w3c.github.io/did-core/diagrams/did_detailed_architecture_overview.svg Specification Portable The DID Methods Credentials Community Group 2022-07-19
167 Decentralized Identifiers TranSendX did:ipid: did:ipid: The Interplanetary Identifiers DID method (did:ipid:) supports DIDs on the public and private Interplanetary File System (IPFS) networks. IPFS is the distributed content addressable permanent web. More specifically, the IPID DID method utilizes the Interplanetary Linked Data (IPLD) suite of tools. The IPID DID method has minimal design goals: a DID trust anchor based on the IPFS and Libp2p protocol. In and of itself, this is not a blockchain solution. However, blockchains and other distributed ledger technologies could be utilized to anchor the artifacts of this DID methods for further enhanced security. https://did-ipid.github.io/ipid-did-method/ Specification IPFS The DID Methods 2018-12-31
168 Decentralized Identifiers lifeID Foundation did:life: lifeID did:life: lifeID is a decentralized, blockchain-based protocol that acts as an open identity provider. The protocol enables the creation and use of self-sovereign identities as well as the issuance of verifiable credentials to those identities. The blockchain-based components of the protocol include smart contracts for storage, revocation, and recovery of keys and credentials. These contracts may be run on any open, permissionless blockchain. The purpose of this protocol is to allow users to transact their identity in a way that minimizes data disclosure, is cryptographically secure, and enables censorship-resistant decentralized identity provisioning and recovery. The purpose of this specification is to describe how lifeID DIDs are created and the technical requirements to operate on the lifeID platform. https://lifeid.github.io/did-method-spec/ Specification RChain The DID Methods 2019-08-13
169 Decentralized Identifiers Sovrin Foundation did:sov: Mike Lodder did:sov: Sovrin is a public ledger designed specifically and only for privacy-preserving self-sovereign identity. The Sovrin Ledger is governed by the international non-profit Sovrin Foundation. As the only public ledger designed exclusively for self-sovereign identity, Sovrin is optimized for DIDs and DID Documents. DIDs are created, stored, and used with verifiable claims. This specification covers how these DIDs are managed. It also describes related features of Sovrin of particular interest to DID owners, guardians, and developers. https://sovrin-foundation.github.io/sovrin/spec/did-method-spec-template.html Specification Sovrin The DID Methods 2023-04-19
205 Decentralized Identifiers OmniOne did:omn: did:omn: OmniOne is a decentralized network system for Self-Sovereign identity and Verifiable Claims. It can replace a legacy centralized credential system that with trusted blockchain node. In the OmniOne system, several types of certificates are issued. DID(Decentralized Identifiers) is used as the unique identifier of the certificate. Also DID allows to obtain public key information for secure exchange of information between users. https://github.com/OmniOneID/did_method/blob/master/did_method.md Specification OmniOne The DID Methods 2019-05-30
206 Decentralized Identifiers Workday, Inc. did:work: did:work: Workday offers a decentralized Credentialing Platform with a Blockchain based trust layer. A key component of the platform is the WayTo by Workday mobile app which allows the user to store verifiable identity documents, encrypted using their own personal encryption key, which is managed in the Trusted Execution Environment (TEE) of their mobile device. The mobile app can hold official documents, training certifications, verified accomplishments and other credentials. The user can choose what to share, and with whom to share it with. Users of the Workday Credentialing Platform will have a DID and a corresponding DID Document on a permissioned ledger, which credential verifiers can use to validate users’ cryptographic signatures, included in their credentials. https://workday.github.io/work-did-method-spec/ data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAYAAABzenr0AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAyRpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADw/eHBhY2tldCBiZWdpbj0i77u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlkIj8+IDx4OnhtcG1ldGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhNUCBDb3JlIDUuMy1jMDExIDY2LjE0NTY2MSwgMjAxMi8wMi8wNi0xNDo1NjoyNyAgICAgICAgIj4gPHJkZjpSREYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjIj4gPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIgeG1sbnM6eG1wPSJodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvIiB4bWxuczp4bXBNTT0iaHR0cDovL25zLmFkb2JlLmNvbS94YXAvMS4wL21tLyIgeG1sbnM6c3RSZWY9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC9zVHlwZS9SZXNvdXJjZVJlZiMiIHhtcDpDcmVhdG9yVG9vbD0iQWRvYmUgUGhvdG9zaG9wIENTNiAoTWFjaW50b3NoKSIgeG1wTU06SW5zdGFuY2VJRD0ieG1wLmlpZDpFMTZCRDY3REIzRjAxMUUyQUQzREIxQzRENUFFNUM5NiIgeG1wTU06RG9jdW1lbnRJRD0ieG1wLmRpZDpFMTZCRDY3RUIzRjAxMUUyQUQzREIxQzRENUFFNUM5NiI+IDx4bXBNTTpEZXJpdmVkRnJvbSBzdFJlZjppbnN0YW5jZUlEPSJ4bXAuaWlkOkUxNkJENjdCQjNGMDExRTJBRDNEQjFDNEQ1QUU1Qzk2IiBzdFJlZjpkb2N1bWVudElEPSJ4bXAuZGlkOkUxNkJENjdDQjNGMDExRTJBRDNEQjFDNEQ1QUU1Qzk2Ii8+IDwvcmRmOkRlc2NyaXB0aW9uPiA8L3JkZjpSREY+IDwveDp4bXBtZXRhPiA8P3hwYWNrZXQgZW5kPSJyIj8+SM9MCAAAA+5JREFUeNrEV11Ik1EY3s4+ddOp29Q5b0opCgKFsoKoi5Kg6CIhuwi6zLJLoYLopq4qsKKgi4i6CYIoU/q5iDAKs6syoS76IRWtyJ+p7cdt7sf1PGOD+e0c3dygAx/67ZzzPM95/877GYdHRg3ZjMXFxepQKNS6sLCwJxqNNuFpiMfjVs4ZjUa/pmmjeD6VlJS8NpvNT4QQ7mxwjSsJiEQim/1+/9lgMHgIr5ohuxG1WCw9Vqv1clFR0dCqBODElV6v90ogEDjGdYbVjXhpaendioqK07CIR7ZAqE49PT09BPL2PMgTByQGsYiZlQD4uMXtdr+JxWINhgINYhGT2MsKgMrm2dnZXgRXhaHAg5jEJodUAHxux4LudHJE9RdEdA+i3Juz7bGHe4mhE9FNrgwBCLirMFV9Okh5eflFh8PR5nK5nDabrR2BNJlKO0T35+Li4n4+/J+/JQCxhmu5h3uJoXNHPbmWZAHMshWB8l5/ipqammaAf0zPDDx1ONV3vurdidqwAQL+pEc8sLcAe1CCvQ3YHxIW8Pl85xSWNC1hADDIv0rIE/o4J0k3kww4xSlwIhcq3EFFOm7KN/hUGOQkt0CFa5WpNJlMvxBEz/IVQAxg/ZRZl9wiHA63yDYieM7DnLP5CiAGsC7I5sgtYKJGWe2A8seFqgFJrJjEPY1Cn3pJ8/9W1e5VWsFDTEmFrBcoDhZJEQkXuhICMyKpjhahqN21hRYATKfUOlDmkygrR4o4C0VOLGJKrOITKB4jijzdXygBKixyC5TDQdnk/Pz8qRw6oOWGlsTKGOQW6OH6FBWsyePxdOXLTgxiyebILZCjz+GLgMIKnXNzc49YMlcRdHXcSwxFVgTInQhC9G33UhNoJLuqq6t345p9y3eUy8OTk5PjAHuI9uo4b07FBaOhsu0A4Unc+T1TU1Nj3KsSSE5yJ65jqF2DDd8QqWYmAZrIM2VlZTdnZmb6AbpdV9V6ec9znf5Q7HjYumdRE0JOp3MjitO4SFa+cZz8Umqe3TCbSLvdfkR/kWDdNQl5InuTcysOcpFT35ZrbBxx4p3JAHlZVVW1D/634VRt+FvLBgK/v5LV9WS+10xMTEwtRw7XvqOL+e2Q8V3AYIOIAXQ26/heWVnZCVfcyKHg2CBgTpmPmjYM8l24GyaUHyaIh7XwfR9ErE8qHoDfn2LTNAVC0HX6MFcBIP8Bi+6F6cdW/DICkANRfx99fEYFQ7Nph5i/uQiA214gno7K+guhaiKg9gC62+M8eR7XsBsYJ4ilam60Fb7r7uAj8wFyuwM1oIOWgfmDy6RXEEQzJMPe23DXrVS7rtyD3Df8z/FPgAEAzWU5Ku59ZAUAAAAASUVORK5CYII= Specification dead Hyperledger Fabric The DID Methods 2020-06-25
207 Decentralized Identifiers VP Inc. did:vid: did:vid: The system aims to provide secure authentication and various payment services based on the DID and Verifiable Claims specificiatons published by the W3C and the Decentralised Identity Foundation. VP DID is a decentralized identifier devised to provide a way to uniquely identify a person, an organization. VP DID document contains information for providing various payment methods among network participants in a decentralized way. This specification defines how VP blockchain stores DIDs and DID documents, and how to do CRUD operations on DID documents. https://github.com/vpayment/did-method-spec/blob/master/vid.md Specification VP The DID Methods 2019-10-15
208 Decentralized Identifiers Baidu, Inc. did:ccp: did:ccp: Application scenarios:<br>- Digital identity<br>- Joint member key customer system<br>- Financial KYC<br>- Exchange<br>- Smart City<br>- IoT deviceless identity management<br><brProgram features:<brBuilding a decentralized ID system based on blockchain and consortium chains will have almost equal control over the system and enhance cooperation intentions.<br><br>Blockchain asymmetric encryption technology combines public and private keys to ensure the authenticity and reliability of ID and certification.<br><br>Form a richer user portrait, with multiple tags (VIP authentication, privilege authentication, asset authentication...) and one ID. Application scenarios:<br>- Digital identity<br>- Joint member key customer system<br>- Financial KYC<br>- Exchange<br>- Smart City<br>- IoT deviceless identity management<br><br>Program features:<br>Building a decentralized ID system based on blockchain and consortium chains will have almost equal control over the system and enhance cooperation intentions.<br><br>Blockchain asymmetric encryption technology combines public and private keys to ensure the authenticity and reliability of ID and certification.<br><br>Form a richer user portrait, with multiple tags (VIP authentication, privilege authentication, asset authentication...) and one ID. https://did.baidu.com/did-spec/ https://did.baidu.com/images/did-login-pc.png Specification Quorum The DID Methods 2016-02-08
209 Decentralized Identifiers Jnctn Limited did:jnctn: did:jnctn: The system provides secure credential management services based on the DID and Verifiable Claims specifications published by the W3C and the Decentralised Identity Foundation. JNCTN DID method enables an interoperability bridge between the worlds of centralized, federated, and decentralized identifiers with self soverign identity services. JNCTN DID document contains information for accessing JNCTN DID network methods, how JNCTN stores DIDs and DID documents, and how to do CRUD operations on JNCTN DID documents. https://github.com/jnctn/did-method-spec/ Specification dead Jnctn Network The DID Methods
210 Decentralized Identifiers evan GmbH did:evan: did:evan: evan.network is a blockchain for digitalization and automation of business transactions. The network members create digital twins for their machines and products and develop standards for cross-company transactions. The open technology allows integration into existing business models. evan.network guarantees 100% reliable and permanently secured information. https://github.com/evannetwork/evan.network-DID-method-specification/blob/master/evan_did_method_spec.md Specification evan.network The DID Methods 2020-03-24
211 Decentralized Identifiers Elastos Foundation did:elastos: did:elastos: DID is completely under the control of the DID subject, without reliance on any centralized registration body, commercial identity provider, or organization issuing certificates. The DID is described in the DID documents. Each DID document includes at least two items: encryption materials and verification methods. The encryption materials integrated with the verification methods provides a set of identify verification mechanisms (such as a public key, anonymous biological identification agreement, etc.), with other optional parts that can be used according to the needs of the application and of the user. https://github.com/elastos/Elastos.DID.Method/blob/master/DID/Elastos-DID-Method-Specification_en.md Specification Elastos ID Sidechain The DID Methods 2021-01-04
213 Decentralized Identifiers Transmute did:elem: did:elem: Element is an implementation of the Sidetree protocol that uses the Ethereum blockchain as the ledger layer and IPFS as the Content-addressable storage layer https://github.com/decentralized-identity/element/blob/master/docs/did-method-spec/spec.md Specification The DID Methods Element DID 2020-04-06
214 Decentralized Identifiers Transmute did:github: did:github: The `github` method is meant to make working with DIDs very simple at the cost of trusting Github.com for assisting in resolving DID Documents.<br><br>Many developers are familar with Github, and its 2 supported public key cryptosystems, GPG and SSH.<br><br>Linked Data Signatures are difficult to work with when operating a server or running a local node of some distributed system / blockchain is a requirement.<br><br>The objective of GitHub DID is to encourage contribution to the DID Spec and Linked Data Signatures, and allow rapid development of extensions to these without requiring the use of slow, or complicated more trustless infrastructure, such as blockchains or other distributed systems. https://docs.github-did.com/did-method-spec/ Specification Github The DID Methods 2020-05-08
215 Decentralized Identifiers teleinfo caict did:bid: did:bid: BID provides distributed identifiers and blockchain-based digital identity services for people, enterprises, devices and digital objects. It aims to build a decentralized, data-secure, privacy-protected and flexible identifier system that addresses trusted connections among people, enterprises, devices and digital objects,enabling the vision of the Internet of Things and trust ingress with everything. https://github.com/teleinfo-bif/bid/tree/master/doc/en Specification bif The DID Methods 2022-11-03
216 Decentralized Identifiers PalletOne did:ptn: did:ptn: Description of each field in the Base DID Document example (★ required fields, others are optional fields):<br><br>* ★ `context` A single value or an array, specifying the syntax standard that the DID Document format complies with.<br* `controller` Single value or array, other owners of DID Document. You can specify other DIDs to manage the file, and the permissions of other DIDs will be set in the corresponding operations authentication, updation, deletion, and recovery later. The default is controlled by the DID in the DID Document corresponding to the Base DID Document.<br>* ★ `publicKey` A single value or an array that controls the public key information corresponding to the private key of the DID Document.<br>* ★ `id` The ID of the public key, `#keys-<num>` expressed in a unified way, incremented `<num>` from the `1` beginning.<br>* ★ `type` The algorithm of public key generation is unified with the chain,<br * `controller` The owner of the public key `controller` corresponds to the one in the previous level. The format is `<DID>#keys-<num>`. The default situation is controlled by the document DID. `<DID>` The value on the stage controller, a `#keys-<num>` is `<DID>` a corresponding public key `id`.<br>* `publicKeyHex` Hexadecimal information of the public key. When the above controller is the default, this field is **required**.<br* ★ `authentication` Specify `publicKey` which fields can be used for authentication.<br>* `updation` Specify `publicKey` which fields can be used for DID Document **update** operations, such as updating information such as pubkey or service.<br* `deletion` Specify `publicKey` which fields can be used for DID Document **delete** operation.<br>* `recovery` Specify `publicKey` which fields can be used for DID Document **recovery** operations. Description of each field in the Base DID Document example (★ required fields, others are optional fields):<br><br>* ★ `context` A single value or an array, specifying the syntax standard that the DID Document format complies with.<br>* `controller` Single value or array, other owners of DID Document. You can specify other DIDs to manage the file, and the permissions of other DIDs will be set in the corresponding operations authentication, updation, deletion, and recovery later. The default is controlled by the DID in the DID Document corresponding to the Base DID Document.<br>* ★ `publicKey` A single value or an array that controls the public key information corresponding to the private key of the DID Document.<br>* ★ `id` The ID of the public key, `#keys-<num>` expressed in a unified way, incremented `<num>` from the `1` beginning.<br>* ★ `type` The algorithm of public key generation is unified with the chain,<br> * `controller` The owner of the public key `controller` corresponds to the one in the previous level. The format is `<DID>#keys-<num>`. The default situation is controlled by the document DID. `<DID>` The value on the stage controller, a `#keys-<num>` is `<DID>` a corresponding public key `id`.<br>* `publicKeyHex` Hexadecimal information of the public key. When the above controller is the default, this field is **required**.<br>* ★ `authentication` Specify `publicKey` which fields can be used for authentication.<br>* `updation` Specify `publicKey` which fields can be used for DID Document **update** operations, such as updating information such as pubkey or service.<br>* `deletion` Specify `publicKey` which fields can be used for DID Document **delete** operation.<br>* `recovery` Specify `publicKey` which fields can be used for DID Document **recovery** operations. https://github.com/palletone/palletone-DID/blob/master/docs/did-method/README.md Specification PalletOne The DID Methods 2020-02-29
217 Decentralized Identifiers Echo Technological Solutions LLC did:echo: did:echo: We propose a new DID method that allows special objects in ECHO network to be treated as valid DIDs. https://github.com/echoprotocol/uni-resolver-driver-did-echo/blob/master/echo_did_specifications.md Specification Echo The DID Methods 2022-10-11
218 Decentralized Identifiers SecureKey did:trustbloc: did:trustbloc: The did:trustbloc DID method allows groups of independent entities to share custody of a DID registry consisting of a Sidetree implementation over a permissioned ledger. For more information on Sidetree, please refer to the Sidetree protocol specification.<br><br>Independent stakeholders wishing to transact with one another using DIDs can come together to form a consortium to manage their shared custody of a ledger.<br><br>This spec defines a discovery service. The discovery service provided by the TrustBloc DID Method allows a client to verify that a consortium is endorsed by its constituent stakeholders, verify that the configuration files of each stakeholder (which includes a list of Sidetree endpoints) are signed by the respective stakeholders, and use the provided Sidetree endpoints to perform Sidetree DID operations. https://github.com/trustbloc/trustbloc-did-method/blob/master/docs/spec/trustbloc-did-method.md Specification Hyperledger Fabric The DID Methods 2020-04-09
219 Decentralized Identifiers YLZ Inc. did:san: did:san: The system aims to provide secure authentication and various health services based on the SAN blockchain and DID & Verifiable Credential Specifications published by the W3C. https://github.com/Baasze/DID-method-specification Specification SAN Cloudchain The DID Methods 2020-04-17
220 Decentralized Identifiers Gataca did:gatc: did:gatc: Gataca’s platform is based on a mobile identity portfolio, a set of APIs, and controllers for multiple blockchain networks.<br<br>Gataca is agnostic to the blockchain network. We adapt our infrastructure to the third party’s preferred ledger. Gataca currently supports the public network Ethereum and private networks based on Hyperledger Fabric, Hyperledger Besu or Quorum. Other networks may be added as requested.<br>This document provides the DID method specs for how our DID schema is implemented on the Ethereum network.<br><br>The simple structure links an object to a DID with states and public keys. Users do not need privileges to read the information on the blockchain but do need them to write. Gataca is the unique user that can modify the smart contract. Gataca’s platform is based on a mobile identity portfolio, a set of APIs, and controllers for multiple blockchain networks.<br><br>Gataca is agnostic to the blockchain network. We adapt our infrastructure to the third party’s preferred ledger. Gataca currently supports the public network Ethereum and private networks based on Hyperledger Fabric, Hyperledger Besu or Quorum. Other networks may be added as requested.<br>This document provides the DID method specs for how our DID schema is implemented on the Ethereum network.<br><br>The simple structure links an object to a DID with states and public keys. Users do not need privileges to read the information on the blockchain but do need them to write. Gataca is the unique user that can modify the smart contract. https://github.com/gatacaid/gataca-did-method Specification Ethereum, Hyperledger Fabric, Hyperledger Besu, Alastria The DID Methods 2020-05-05
221 Decentralized Identifiers Sphereon, Factomatic, Factom Inc did:factom: did:factom: This proposal contains the interoperability specifications for products creating, reading (resolving) updating and deactivating Decentralized Identifiers on top of the Factom Protocol. This specification is not about other products wanting to use DIDs for their specific purpose, like signing or voting. This document describes the low level data structures and rules for DIDs, DID documents, resolution and registration on Factom itself. https://github.com/factom-protocol/FIS/blob/master/FIS/DID.md Specification Factom The DID Methods 2019-11-02
222 Decentralized Identifiers Cryptonics Consulting did:signor: did:signor: DIDs are registered in the DID Registry on-chain, and have a controller and a subject, expressed in the form of Ethereum addresses. The DID controller may or may not be the subject itself. Multiple controllers can be implemented through proxy smart contracts. https://github.com/cryptonicsconsulting/signor-did-contracts/blob/master/did-method-spec.md Specification Ethereum, Hedera Hashgraph, Quorum, Hyperledger Besu The DID Methods 2020-11-16
223 Decentralized Identifiers Hedera Hashgraph, Swisscom Blockchain AG did:hedera: did:hedera: This document defines a binding of the Decentralized Identifier architecture to Hedera Hashgraph - specifically how to use the Hedera File Service to record membership in 'business application networks' (appnets) and how to use the Hedera Consensus Service (HCS) for CRUD mechanisms on DID documents stored in such business application network. An business application network is a network of computers that store some set of business data (such as DID Documents) in a shared state, and rely on the Hedera mainnet for timestamping and ordering the transactions that cause that business application network state to change. An business application network could be exclusively dedicated to managing DID Documents and other identity artifacts in its state, or it could itself be multi-purpose. https://github.com/hashgraph/did-method/blob/master/did-method-specification.md Specification Hedera Hashgraph The DID Methods 2020-05-14
224 Decentralized Identifiers ProximaX Enterprise, Proximax Inc. did:sirius: did:sirius: The target system is the ProximaX Sirius Chain network. This can either be:<br>- Sirius Chain on Main Net<br>- Sirius Chain on Test Net<br>- Sirius Chain on Private Net https://gitlab.com/proximax-enterprise/siriusid/sirius-id-specs/-/blob/master/docs/did-method-spec.md Specification ProximaX Sirius Chain The DID Methods 2020-07-04
225 Decentralized Identifiers Dock did:dock: did:dock: Currently, three public key and signing algorithms are supported for authentication.<br>- Schnorr signatures with Sr25519. The public key is 32 bytes and signature is 64 bytes in size. These are supported by Substrate and Polkadot.<br>- EdDSA signatures with Ed25519 curve. The public key is 32 bytes and signature is 64 bytes in size.<br><br>Dock is currently running as a proof of authority network but will evolve into a proof of stake chain. DIDs can be created by anyone holding Dock tokens but the creator of the DID is not necessarily the owner of the DID and thus cannot manage (update, remove) them. DIDs are managed using their corresponding private keys and these keys are independent of keys controlling the Dock tokens spent while creating the DID.<br><br>The chain does not store the full DID document but only the DID, the corresponding keys and controllers and block number for the last update and this block number changes with each update to the DID. This is needed for replay protection. Dock's client SDK retrieves those details and constructs the full DID document. https://github.com/docknetwork/dock-did-driver/blob/master/Dock%20DID%20method%20specification.md Specification Dock The DID Methods 2022-07-21
226 Decentralized Identifiers did-twit did:twit: did:twit: Twitter is a highly used and influential social media network that lacks decentralization and higher levels of trust (i.e. signed messages). The `did:twit` specification makes an attempt to increase trust in Twitter interactions.<br><br>The method is similar to [did:key](https://w3c-ccg.github.io/did-method-key) in the sense that it is uses a `did` to wrap a single public key.<br<br>The objective of Twitter DID, similar to that of the [GitHub DID Method](https://github.com/decentralized-identity/github-did), is to encourage use of the [DID Spec](https://w3c-ccg.github.io/did-spec/), by lowering the barrier to entry for use of the technology, and promote higher trust interactions. Twitter is a highly used and influential social media network that lacks decentralization and higher levels of trust (i.e. signed messages). The `did:twit` specification makes an attempt to increase trust in Twitter interactions.<br><br>The method is similar to [did:key](https://w3c-ccg.github.io/did-method-key) in the sense that it is uses a `did` to wrap a single public key.<br><br>The objective of Twitter DID, similar to that of the [GitHub DID Method](https://github.com/decentralized-identity/github-did), is to encourage use of the [DID Spec](https://w3c-ccg.github.io/did-spec/), by lowering the barrier to entry for use of the technology, and promote higher trust interactions. https://github.com/did-twit/did-twit/blob/master/spec/index.md Specification Twitter The DID Methods 2020-07-29
227 Decentralized Identifiers Ontology Foundation did:near: did:near: NEAR uses readable account identifiers instead of a hash of a public key, and the accounts have some DID features, but not all. We have developed this specification to define a new DID method for hosting DIDs on the NEAR blockchain, also referred to as NEAR DID, and facilitate developers to work with related contracts. https://github.com/ontology-tech/DID-spec-near/blob/master/NEAR/DID-Method-NEAR.md Specification NEAR The DID Methods 2020-08-02
228 Decentralized Identifiers China Academy of Information and Communications Technology (CAICT) did:vaa: did:vaa: Blockchain Identifier Infrastructure (BIF) is a permissioned public blockchain aiming for creating a distributed trust management framework typical for internet ID service, and the [BIF blockchain](http://bidspace.cn/) is governed by China Academy of Information and Communications Technology (CAICT). CAICT is also the official issuing agency with Issuing Agency Code (IAC)——"VAA", given by ISO/IEC 15459. The IAC indicates an authorized qualification of distributing identifiers with own allocation rules. https://github.com/caict-develop-zhangbo/vaa-method/blob/master/README.md Specification BIF The DID Methods 2020-08-05
229 Decentralized Identifiers Attila Aldemir did:bba: did:bba: The `bba` DID method aims to enable the Ardor blockchain to act as a DPKI within the SSI ecosystem. It runs on the independent IGNIS child chain and utilizes Ardors Account Properties feature to manage DIDs and corresponding DID controllers. The Account Properties feature provides the possibility to tag an account with a small amount of data (160 characters). A DID controller is always represented in form of an Ardor account and is by default separated from the public keys (if present) embedded in a DID document. Think of a master key controlling the DID operations create, update and deactivate. A DID controller always corresponds to exactly one Ardor account, whereas one Ardor account can control multiple DIDs.<br><br>DID and DID document handling is decoupled so that multiple DID document storages can be defined and integrated to store DID document templates (DID documents without a DID reference). In its current state, the `bba` DID method defines only one storage type (Ardor Cloud Storage).<br>In the following, `bba` DID method compliant account properties are called DID attestations. An account property is `bba` DID method compliant if it aligns to the data model described in the DID Attestation Data Fields section and is self-set. A self-set account property is a property in which sender and receiver accounts are identical. https://github.com/blobaa/bba-did-method-specification/blob/master/docs/markdown/spec.md Specification Ardor The DID Methods 2020-08-31
235 Decentralized Identifiers Ontology Foundation did:trx: did:trx: This TRON DID method specification describes a new DID method, that is, TRON DID and defines how TRON blockchain stores TRON DIDs and their corresponding DID documents, and how to do CRUD operations on TRON DID documents. https://github.com/ontology-tech/DID-method-specs/blob/master/did-trx/DID-Method-trx.md Specification TRON The DID Methods 2020-08-14
236 Decentralized Identifiers GRGBanking Blockchain Express did:grg: did:grg: GRG did document security authentication is based on the cryptography algorithm. A signature is used to verify that the claim is from a trusted did user. What should be noted is the authenticity verification of the issuer. An alliance blockchain maintained by an official organization is designed and used. In the alliance chain, the did document of the certification authority should be stored, and its did ID number should be displayed on the official website of the relevant organization. Therefore, the verifier can verify claims based on this information. https://github.com/GrgChain/DID-method-specs/blob/master/README.md Specification GrgChain The DID Methods 2020-08-01
237 Decentralized Identifiers 51nodes GmbH did:schema: did:schema: The Schema Registry DID Method aims to provide unique and universal identification for schemas in multiple formats hosted on multiple storage mechanisms or networks. https://github.com/51nodes/schema-registry-did-method/blob/master/README.md Specification Portable, IPFS, evan.network The DID Methods 2020-08-26
238 Decentralized Identifiers CCG did:key Rick Astley, Manu Sporny, Dmitri Zagidulin, Dave Longley, Orie Steele did:key Ledger independent DID method based on public/private key pairs.<BR><BR>While DLT-based DID Methods have great decentralization characteristics, and some of the more centralized DID Methods provide strong system control guarantees, the general approaches tend to be expensive to setup and operate. Some use cases requiring DIDs do not need the guarantees provided by these heavy-weight systems. For example, a DID that will only be used for a single, ephemeral interaction might not need to be registered, updated, or deactivated. It is for this class of use cases that the did:key method exists Ledger independent DID method based on public/private key pairs.<br><br>While DLT-based DID Methods have great decentralization characteristics, and some of the more centralized DID Methods provide strong system control guarantees, the general approaches tend to be expensive to setup and operate. Some use cases requiring DIDs do not need the guarantees provided by these heavy-weight systems. For example, a DID that will only be used for a single, ephemeral interaction might not need to be registered, updated, or deactivated. It is for this class of use cases that the did:key method exists https://w3c-ccg.github.io/did-method-key/ Specification Portable, IPFS, evan.network The DID Methods 2022-09-02
239 Decentralized Identifiers CCG did:key did-key-creator published This has been tested to create did:keys from the P-256,P-384, and P-521 curves specified in https://github.com/w3c-ccg/did-method-key and https://w3c-ccg.github.io/did-method-key/ This is a library for converting public keys to the did:key format. Latest version: 1.2.0, last published: 7 months ago. Start using did-key-creator in your project by running `npm i did-key-creator`. There is 1 other project in the npm registry using did-key-creator. https://www.npmjs.com/package/did-key-creator Code Portable, IPFS, evan.network The DID Methods 2022-11-03
240 Decentralized Identifiers Crates Tomislav Markovski did:key Rust implementation of the did:key method This crate is intended to provide basic support for did:key methods. It has no external dependencies and can be compiled for any target. It was originally designed for use with DIDComm Extension for gRPC, but we recognized it may be useful if this was an independent library https://crates.io/crates/did-key Code Portable, IPFS, evan.network The DID Methods 2022-11-28
241 Decentralized Identifiers Tryon did:tyron: Julio, Cabrapan Duarte did:tyron: Tyronzil is the W3C Decentralized Identifier Method of the Tyron Self-Sovereign Identity Protocol. You can find it published at the W3C DID Specification Registries, and it is the first DID Method of the Zilliqa blockchain - funded by ZILHive Innovation grants. https://www.tyronzil.com/ Specification Zilliqa The DID Methods
245 Decentralized Identifiers Hyperledger Foundation did:indy: did:indy: Indy is a public ledger designed specifically and only for privacy-preserving self-sovereign identity. A Hyperledger Indy ledger is designed specifically to enable the use of verifiable credentials, allowing credential issuers to publish data necessary for issuing verifiable credentials and constructing presentations from those verifiable credentials. This specification covers how DIDs on an Indy ledger are managed and the operations for creating, reading, updating, and deleting DIDs. https://github.com/hyperledger/indy-did-method Specification Hyperledger Indy The DID Methods 2023-02-23
246 Decentralized Identifiers IDCommons Stephen Curran did:indy: IIW The did:indy DID Method - Future Indy Ledgers Getting involved with this work: https://iiw.idcommons.net/4I/_The_did:indy_DID_Method_-_Future_Indy_Ledgers Session Notes Hyperledger Indy The DID Methods 2021-05-06
247 Decentralized Identifiers BCGov Stephen Curran did:indy: did:indy Presentation - Namespaced DIDs useful across all Indy instances<br>- Indy network discovery<br>- Full DIDDoc support<br>- Namespaced identifiers for other Indy objects (schemas, etc.)<br>- Support for important resolution parameters<br>- E.g. version-id, version-time, resource<br><br>Nice to have (but not likely to be there):<br>- Cross-ledger registration of networks for discovery<br>- Support for KERI identifiers on Indy networks<br><br>Getting involved with this work:<br>- [HackMD Document](https://hackmd.io/@icZC4epNSnqBbYE0hJYseA/S1eUS2BQw) with current spec<br>- Home of future spec: [indy-did-method](https://github.com/hyperledger/indy-did-method)<br>- [Meeting Wiki](https://wiki.hyperledger.org/display/indy/Indy%2BDID%2BMethod%2BSpecification) and schedule<br>- Hyperledger [indy-did-method](https://chat.hyperledger.org/channel/indy-did-method) chat channel https://docs.google.com/presentation/d/1c5K7E5CRx9ANuwmVBIyFVG5hJ4lH0EyW-wkmraLivBI/edit?usp%3Dsharing Presentation Hyperledger Indy The DID Methods 2021-04-20
248 Decentralized Identifiers Blockchain Commons did:onion: did:onion: 🧅 part of the torgap technology family<brDIDs that target a distributed ledger face significant practical challenges in bootstrapping enough meaningful trusted data around identities to incentivize mass adoption. We propose using a new DID method that allows them to bootstrap trust using a Tor Hidden Service's existing reputation.<br><br>we'd like to review more with our community how close we want to keep did:onion to did:web, and if we want to incorporate some elements of did:peer or KERI or to leverage services like Open Time Stamps. 🧅 part of the torgap technology family<br>DIDs that target a distributed ledger face significant practical challenges in bootstrapping enough meaningful trusted data around identities to incentivize mass adoption. We propose using a new DID method that allows them to bootstrap trust using a Tor Hidden Service's existing reputation.<br><br>we'd like to review more with our community how close we want to keep did:onion to did:web, and if we want to incorporate some elements of did:peer or KERI or to leverage services like Open Time Stamps. http://htmlpreview.github.io/?https://raw.githubusercontent.com/BlockchainCommons/did-method-onion/main/index.html Specification Tor The DID Methods 2021-08-06
249 Decentralized Identifiers Ceramic did:nft: did:nft: The NFT DID Method converts any non-fungible token on any blockchain into a decentralized identifier where the owner of the NFT is the controller of the DID. This is achieved by using the Chain Agnostic Improvement Proposals to describe NFT assets and blockchain accounts, as well as the Ceramic network to find the DID associated with the owner of the NFT. https://github.com/ceramicnetwork/CIPs/blob/main/CIPs/cip-94.md Specification Ethereum The DID Methods 2021-02-12
250 Decentralized Identifiers Gimly did:eos: did:eos: 1. Identity - the management of accessible public key infrastructure and identifies. Decentralized Identifiers is the W3C standard that allows this. Compliance with this standard allows application layers to interoperate without a need to understand the base layer decentralised protocols that power identities.<br>2. Application - use of the identity layer to interact and provide meaningful, secure and verifiable data communications and interaction. The Verifiable Credentials W3C standard is the most prominent and adopted standard here which is a data structure and message protocol allowing people and organisations to securely and in a verifiable way send and verify information about themselves "credentials" to each other. DIDComm is another important application layer that uses DID methods to communicate between SSI identities. https://github.com/Gimly-Blockchain/eosio-did-spec Specification EOS The DID Methods 2021-06-30
251 Decentralized Identifiers Gimly did:eos: The EOSIO DID method specification We have been working with the [Decentralised Identity Foundation](https://identity.foundation) to shape this specification, and also want to thank the [W3C Credentials Community Group](https://www.w3.org/community/credentials/) for their support in the creation of the [Verifiable Condition](https://github.com/Gimly-Blockchain/verifiable-conditions) type, a necessary component to create the EOSIO DID document to represent EOSIO account permissions. Gimly has built a full draft of the EOSIO Decentralised Identifier (DID) method specification. This specification guides the implementation of DIDs on EOSIO powered blockchains. https://www.gimly.io/blog/the-eosio-did-method-specification Post EOS The DID Methods 2021-04-02
252 Decentralized Identifiers SpruceID did:did: https://lists.w3.org/Archives/Public/public-credentials/2021Apr/0026.html did:did: DID Identity DID (DID) DID method<BR><BR>Spruce announces did:did, a DID method based on Decentralized Identifiers (DIDs). We hope the community will find this useful to help increase adoption and interoperability of Decentralized Identity technology. DID Identity DID (DID) DID method<br><br>Spruce announces did:did, a DID method based on Decentralized Identifiers (DIDs). We hope the community will find this useful to help increase adoption and interoperability of Decentralized Identity technology. https://github.com/spruceid/did-did/ Specification humor The DID Methods 2021-04-01
253 Decentralized Identifiers SpruceID did:undid: did:undid: did:un-did is a DID method that enables using any valid Decentralized Identifier (DID) as a did:un-did DID, but more importantly it un-does the did that did:did did method performs.<br><br>*Clarification, a few week ago we shared about the [DID:DID](https://did-did.spruceid.com/) method. [April Fools Joke](https://en.wikipedia.org/wiki/April_Fools%2527_Day_RFC)!!! Here’s yet another DID method in the series.* https://did-undid.github.io/did-undid/ Specification humor The DID Methods 2021-04-01
254 Decentralized Identifiers SpruceID did:doge: did:doge: We draw heavily from prior work by Christopher Allen and Kim Hamilton Duffy within the W3C Credentials Community Group on the BTCR DID Method due to strong architectural similarities between the Bitcoin and Dogecoin blockchains.<br><br>However, there are some key differences that enable new privacy-preserving benefits. Namely, the did:doge method-specific identifier is the Base58Check-encoded Dogecoin address itself, allowing for DID usage even in the absence of any public transaction histories and only relying upon them for rotation events for verification methods and service endpoints. https://spruceid.github.io/did-doge/index.html Specification Dogecoin The DID Methods 2023-05-04 https://github.com/spruceid/did-doge
255 Decentralized Identifiers SpruceID, TQ Tezos did:tz: did:tz: did:tz is a multi-modal DID method design with many offchain, on-chain, and side-chain/L2 use cases in mind. A valid Tezos address (controlled by a private key from any of 3 supported curves) can control an "implicit" DID document (generatively created from the address like a did:key), an "onchain" DID document (published via smart contract on any Tezos ledger), or have "patches" applied to it that are published and governed by a closed network or authority (including, for example, a sidetree network). In particular, this third option has not been specified in any detail, and we would be particularly curious to hear from implementers of such systems before further specifying it. https://github.com/w3c-ccg/did-tz Specification Tezos The DID Methods 2022-01-13
273 Decentralized Identifiers IDCommons Dave Huseby IIW Don’t use DIDs, DIDs, nor DIDs: Change My Mind (a.k.a. Oh no he DIDn’t) This session was to talk about the topics I put in a recent article that created a huge fire in our community where I lay out the case for completely abandoning the W3C DID standards. https://iiw.idcommons.net/10A/_Don%27t_use_DIDs,_DIDs,_nor_DIDs:_Change_My_Mind_(a.k.a._Oh_no_he_DIDn%27t) Session Notes Critique 2021-05-07
274 Decentralized Identifiers cardossier CH https://iiw.idcommons.net/21D/_The_world_between_public_and_private_DIDs_-_Or_how_to_make_use_of_SSI_without_the_subjects This Loepfe The world between public and private DIDs - Or how to make use of SSI without the subjects - It was very hard for me to explain the problem I’m searching a solution for and equally for the proposed solution ideas.<br>- We discussed a lot of more philosophical questions and if peer-dids are a good thing or not and if it is worth trying to minimize correlation when any involved party anyway stores the personal data of the related persons. I think we should make it as hard as possible to correlate data, even if we can not completely prevent it.<br>- We also discussed the potential complexity of such a solution and if it is worth it. The conclusion was to minimize the number of personas one should (be forced) to hold, such that it is still easy to maintain. https://cardossier.ch/wp-content/uploads/2021/05/iiw-between-public-and-private.pdf Presentation Discussion Public vs Private 05-2021
275 Decentralized Identifiers CCG Mailing List Steve Capell CCG DID methods as W3C standards - a happy compromise? can't we pick just a small number of un-controversial methods to standardise?  even if it's just did:key and did:web to start with. https://lists.w3.org/Archives/Public/public-credentials/2022Feb/0117.html Discussion Discussion Methods as Standards 2022-02-22
276 Decentralized Identifiers CCG Mailing List Manu Sporny CCG Re: CCG Community opinions needed to define CCG scope (specifically re: did methods as work items) Heather Vescent wrote:<br1. What are the *pros* of including did methods as work items in the CCG?<brCommunity vetting and approval of particular DID Methods.<br><br>Basically, broader and deeper review of DID Methods that we expect to be of great use to the world. I expect there will be DID Methods that the community wants to eventually propose as DID Methods for standardization (did:key and<br><br>did:web feel like two ones where we could get consensus on doing so). Heather Vescent wrote:<br>1. What are the *pros* of including did methods as work items in the CCG?<br>Community vetting and approval of particular DID Methods.<br><br>Basically, broader and deeper review of DID Methods that we expect to be of great use to the world. I expect there will be DID Methods that the community wants to eventually propose as DID Methods for standardization (did:key and<br><br>did:web feel like two ones where we could get consensus on doing so). https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0376.html Discussion Discussion Methods as Standards 2021-08-26
277 Decentralized Identifiers GoDiddy https://iiw.idcommons.net/2C/_godiddy.com_-_Universal_DID_Services Markus Sabadello godiddy.com - Universal DID Services Basic functions are creating, resolving, updating, and deactivating DIDs across multiple DID methods and networks. Advanced functions include key management, search, transfer of DIDs, lookup of historical DID document versions, notification of DID-related events, and more. https://godiddy.com site Tools and Utilities 2021-05-06 https://docs.godiddy.com/ https://api.godiddy.com/
278 Decentralized Identifiers IDCommons Markus Sabadello Standard Interfaces for DID Create/Update/Deactivate - There is an attempt to specify abstract interfaces if you want to Create/Update/Deactivate a did that could be implemented for all did methods.<br>- The idea of this specification is to provide a standard with the same assumptions as with resolution. It should be in an abstract level, meaning it should specify the inputs and outputs of creating/updating/deactivating a did but not how it should be implemented. https://iiw.idcommons.net/3C/_Standard_Interfaces_for_DID_Create/Update/Deactivate Session Notes Tools and Utilities 2021-07-17
279 Decentralized Identifiers W3C DID test suite DID test suite is not for runtime, but the Universal Resolver could do a few simple checks on a driver's responses. But there's also a philosophical question: Should the Universal Resolver be "allowed" to check and potentially transform driver responses, or should it just "pass through" everything that comes from a driver? https://github.com/w3c/did-test-suite Code Tools and Utilities 2023-01-17
280 Decentralized Identifiers Personal Micheal Herman BlueToque Tools Toolkit BlueToque Tools is a collection of software tools for working with DID Method Namespaces, DID Identifiers, DID Documents, DID Agent Service Endpoints, DID Agent Servers, DID Agent Clusters, and DID Objects (the 7 DIDs). The flagship tool is didlang, a language for interactively working with the 7 DIDs. https://github.com/mwherman2000/BlueToqueTools Code Tools and Utilities 2022-12-06
281 Decentralized Identifiers W3C Objections overruled by W3C director approving the DIDCore specification as a W3C Recommendation In its next chartered period the Working Group should address and deliver proposed standard DID method(s) and demonstrate interoperable implementations.  The community and Member review of such proposed methods is the natural place to evaluate the questions raised by the objectors and other Member reviewers regarding decentralization, fitness for purpose, and sustainable resource utilization. -Ralph Swick, for Tim Berners-Lee https://www.w3.org/2022/06/DIDRecommendationDecision.html Post W3C Recommendation 2022-06-30
282 Decentralized Identifiers DIF Decentralized Identifiers (DID) 1.0 specification approved as W3C Recommendation Announcing the [Decentralized Identifiers (DID) v1.0 specification](https://www.w3.org/TR/did-core/) as an open web standard signals that it is technically sound, mature, and ready for widespread adoption. Having an established v1.0 specification allows work to continue with renewed energy and focus, not only at the many groups meeting at DIF, but across the digital identity community. The W3C has approved the DIDCore V1.0 spec as an official Recommentdation; DIDs are now an open web standard ready for use and further development https://blog.identity.foundation/w3cdidspec-2/ Post W3C Recommendation 2022-06-30
283 Decentralized Identifiers TOIP A DIF & TOIP Joint Statement of Support for the Decentralized Identifiers (DIDS) V1.0 Specification Becoming A W3C Specification DIDs are a critical part of a technical foundation for the products and activities of many of our members. Many of the implementations in the [DID Working Group’s implementation report](https://w3c.github.io/did-test-suite/%23report-by-methods) were developed by engineers and companies who collaborate openly at DIF on points of technical interoperability, and at ToIP on points of policy and governance.<brWhy would you have 75 logins when you could have 1? DIDs are a critical part of a technical foundation for the products and activities of many of our members. Many of the implementations in the [DID Working Group’s implementation report](https://w3c.github.io/did-test-suite/%23report-by-methods) were developed by engineers and companies who collaborate openly at DIF on points of technical interoperability, and at ToIP on points of policy and governance.<br>Why would you have 75 logins when you could have 1? https://trustoverip.org/blog/2021/10/29/a-dif-toip-joint-statement-of-support-for-the-decentralized-identifiers-dids-v1-0-specification-becoming-a-w3c-standard/ Post W3C Recommendation 2021-10-29
284 Decentralized Identifiers Indicio Sam Curren Indicio’s support for the W3C DID Specification and its path to standardization The position of Indicio is that the DID Specification is of signal importance to creating a better digital world. We recognize that, as with any specification, improvements can and will be made in the future; but we back its recommendations and its approval. The W3C’s DID Specification is critical to building a better digital world. https://indicio.tech/indicios-support-for-the-w3c-did-specification-and-its-path-to-standardization/ Post W3C Recommendation 2022-07-01
285 Decentralized Identifiers The Register W3C overrules objections by Google, Mozilla to decentralized identifier spec The [DID specification](https://www.w3.org/TR/did-core/%23introduction) describes a way to deploy a globally unique identifier without a centralized authority (eg, Apple [for Sign in with Apple](https://developer.apple.com/sign-in-with-apple/) as a verifying entity. https://www.theregister.com/2022/07/01/w3c_overrules_objections/ Post W3C Recommendation 2022-07-01
286 Decentralized Identifiers IOHK Advancing digital identity through DID core specification The recent DID core specification approval at the World Wide Web Consortium (W3C) provided clearer and stronger foundations for identity platforms building decentralized identifiers. Good to see Cardano jumping on the bandwagon, looks like they will bring DID\VC to Atla Prism. https://iohk.io/en/blog/posts/2022/09/08/advancing-digital-identity-through-did-core-specification/ Post W3C Recommendation 2022-09-08
435 Blockcerts Learning Machine Learning Machine Get a complete system to issue digital credentials in a blockchain-secured format that is easily shareable and instantly verifiable anywhere in the world. https://www.learningmachine.com/ https://www.learningmachine.com/wp-content/uploads/2019/06/mobile-cert-min.png company Learning Machine 2016
436 Blockcerts Personal Natalie Smolenski Natalie Smolenski - Author, Speaker Natalie Smolenski is an anthropologist leading business development for blockchain technology firm Learning Machine. She writes and speaks about identity, tech, and government. https://www.nataliesmolenski.com/ blog Learning Machine
437 Blockcerts Learning Machine Academic Credentialing and the Blockchain Hello everyone. My name is Chris Jagers. I’m the CEO of Learning Machine, the software company that has been working with MIT over the last year to develop an open standard for blockchain certificates. I’ll be giving a short presentation about blockchain-based academic credentials, followed by a discussion with our panel and with all of you. https://www.learningmachine.com/academic-credentialing-blockchain/ page Learning Machine 2016-10-28
438 Blockcerts Hyland Credentials Future Proof Learning Machine is proud to announce that we have won Phase-1 funding for our response to the open call “Preventing Forgery & Counterfeiting of Certificates and Licenses through the use of Blockchain and Distributed Ledger Technology.” [...] The open-source reference implementation, targeted for 2020, will include:<br- Updating the Blockcerts schema to a Verifiable Credentials-based format<br- Updating the Blockcerts signature/verification scheme to conform to the latest JSON-LD signature suite format<br- Updating Blockcerts credential issuance and verification<br- Incorporating a cost-efficient DID method for issuers Learning Machine is proud to announce that we have won Phase-1 funding for our response to the open call “Preventing Forgery & Counterfeiting of Certificates and Licenses through the use of Blockchain and Distributed Ledger Technology.” [...] The open-source reference implementation, targeted for 2020, will include:<br>- Updating the Blockcerts schema to a Verifiable Credentials-based format<br>- Updating the Blockcerts signature/verification scheme to conform to the latest JSON-LD signature suite format<br>- Updating Blockcerts credential issuance and verification<br>- Incorporating a cost-efficient DID method for issuers https://www.hylandcredentials.com/future-proof https://www.learningmachine.com/wp-content/uploads/2019/07/vc.png page Learning Machine 2017-07
439 Blockcerts Blockcerts Blockcerts Blockcerts open standard for issuing and verifying blockchain-based official records; The project offers open-source libraries, tools, and mobile apps. MIT has [issued](https://www.insidehighered.com/news/2017/10/19/mit-introduces-digital-diplomas) digital certificates based on this standard. Build apps that issue and verify blockchain-based credentials for academic credentials, professional certifications, workforce development, and civic records. https://www.blockcerts.org/ project Blockcerts 2016 https://github.com/blockchain-certificates https://twitter.com/blockcerts http://community.blockcerts.org/
440 Blockcerts Blockcerts Introduction Blockcerts is an open standard for building apps that issue and verify blockchain-based official records. These may include certificates for civic records, academic credentials, professional licenses, workforce development, and more.<br><brBlockcerts consists of open-source libraries, tools, and mobile apps enabling a decentralized, standards-based, recipient-centric ecosystem, enabling trustless verification through blockchain technologies.<br><br>Blockcerts uses and encourages consolidation on open standards. Blockcerts is committed to self-sovereign identity of all participants, and enabling recipient control of their claims through easy-to-use tools such as the certificate wallet (mobile app). Blockcerts is also committed to availability of credentials, without single points of failure. Blockcerts is an open standard for building apps that issue and verify blockchain-based official records. These may include certificates for civic records, academic credentials, professional licenses, workforce development, and more.<br><br>Blockcerts consists of open-source libraries, tools, and mobile apps enabling a decentralized, standards-based, recipient-centric ecosystem, enabling trustless verification through blockchain technologies.<br><br>Blockcerts uses and encourages consolidation on open standards. Blockcerts is committed to self-sovereign identity of all participants, and enabling recipient control of their claims through easy-to-use tools such as the certificate wallet (mobile app). Blockcerts is also committed to availability of credentials, without single points of failure. Build apps that issue and verify blockchain-based credentials for academic credentials, professional certifications, workforce development, and civic records. https://www.blockcerts.org/guide/ https://www.blockcerts.org/assets/img/pictures/blockcerts.png page Blockcerts
441 Blockcerts MIT Media Lab Blockcerts — An Open Infrastructure for Academic Credentials on the Blockchain What would an academic degree look like if it was designed today? Or a professional certificate? These are questions we have been working on over the last year, and we are excited to announce the… https://medium.com/mit-media-lab/blockcerts-an-open-infrastructure-for-academic-credentials-on-the-blockchain-899a6b880b2f https://miro.medium.com/v2/resize:fit:1200/1*zrTpMx8dQKK_XAJLtLdOGg.png Post Blockcerts 2016-10-25
442 Blockcerts Learning Machine Natalie Smolenski Top 10 Reasons to Use Blockcerts The open standard for issuing blockchain-based records is your easiest bet for creating records that remain verifiable for a lifetime. With more blockchain credentialing solutions popping up every week, it can be difficult to navigate the landscape of offerings. How do you decide which blockchain credentialing framework to use? One… https://medium.com/learning-machine-blog/top-10-reasons-to-use-blockcerts-ec7d29f2712c Post Blockcerts 2018-05-19
443 Blockcerts SSIMeetup https://www.slideshare.net/SSIMeetup/blockcerts-the-open-standard-for-blockchain-credentials Blockcerts: The Open Standard for Blockchain Credentials <center><iframe src="//www.slideshare.net/slideshow/embed_code/key/rVC25i8FzeTPiw" 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</center> Anthony Ronning, an engineer behind Blockcerts and backend dev at Learning Machine and Daniel Paramo, co-founder of swys and advisor at Xertify, explains how Blockcerts started, deep dive on how Blockcerts work, which institutions are implementing this solution and what companies have made a solution for the adoption of this standard. We will review the current Blockcerts roadmap and their pros and cons. What considerations do we need to take when developing a solution around Blockcerts? https://ssimeetup.org/blockcerts-open-standard-blockchain-credentials-daniel-paramo-anthony-ronning-webinar-39/ Presentation Blockcerts 2019-10-12
444 Blockcerts WebofTrustInfo rwot5-boston A Decentralized Approach to Blockcerts Credential Revocation The initial release of the Blockcerts standard and reference implementation described only one revocation mechanism, the issuer-hosted revocation list approach also used by Open Badges. This has known limitations, including: centralization, single point of failure, and inability for a recipient to revoke. Other approaches to revocation were considered, but none were technically or economically feasible at the time given the project goals, including Bitcoin blockchain anchoring, low overhead, and minimal cost. https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/final-documents/blockcerts-revocation.md Paper Blockcerts 2018-02-09
445 Blockcerts WebofTrustInfo https://community.blockcerts.org/t/blockcerts-v3-proposal-verifiable-credentials-decentralized-identifiers/2221 rwot9-prague Blockcerts V3 Proposal - Verifiable Credentials & Decentralized Identifiers As the standards around Verifable Credentials are starting to take form, different favors of "verifiable credentials-like" data structures need to make necessary changes to leverage on the rulesets outlined and constantly reviewed by knowledgeable communities such as the W3C. The purpose of this paper is to identify all of the changes needed for Blockcerts to comply with the Verifiable Credentials (VCs) and Decentralized Identifers (DIDs) standards and to expand upon the additional benefits of using a blockchain in combination with Verifiable Credentials. This paper is meant to act as an explainer in which a formal specification can be created. This paper proposes multiple implementation options for several properties. The intention is that we can engage the Blockcerts / Verifiable Credential communities and see what fts best. Some of you may already know and/or have been following along. Over the last few months, since Rebooting the Web of Trust 9, we have been coming up with drafts and proposals for Blockcerts V3 for the al&hellip; https://nbviewer.jupyter.org/github/WebOfTrustInfo/rwot9-prague/blob/master/final-documents/BlockcertsV3.pdf Paper Blockcerts 2019-12-19 https://github.com/blockchain-certificates/cert-issuer/tree/v3 https://community.blockcerts.org/t/blockcerts-v3-proposal-verifiable-credentials-decentralized-identifiers/2221
446 Blockcerts Learning Machine Badges and Blockcerts In education and workforce development, it’s important to understand the differences between digital credential formats and how to combine them for greatest impact [...]<br><br2011 saw the birth of Open Badges, which digitally and visually convey the achievement of a specific skill. Similar to the Scouts movement, which uses a small fabric symbol to represent specific achievements, digital badges were designed to convey a singular achievement through a digital image and a hosted set of data. Initially spearheaded by the Mozilla Foundation, the Open Badges standard is now maintained by the IMS Global Learning Consortium, ensuring interoperability between platforms. [...]<br><br>In response to the desire for high-stakes credentials in a digital format, the development of Blockcerts began in 2015 as part of a project by the MIT Media Lab. In education and workforce development, it’s important to understand the differences between digital credential formats and how to combine them for greatest impact [...]<br><br>2011 saw the birth of Open Badges, which digitally and visually convey the achievement of a specific skill. Similar to the Scouts movement, which uses a small fabric symbol to represent specific achievements, digital badges were designed to convey a singular achievement through a digital image and a hosted set of data. Initially spearheaded by the Mozilla Foundation, the Open Badges standard is now maintained by the IMS Global Learning Consortium, ensuring interoperability between platforms. [...]<br><br>In response to the desire for high-stakes credentials in a digital format, the development of Blockcerts began in 2015 as part of a project by the MIT Media Lab. https://www.learningmachine.com/badges-and-blockcerts/ https://www.learningmachine.com/wp-content/uploads/2019/01/Screen-Shot-2019-01-29-at-9.54.40-AM.png page Open Badges 2018-12-13
447 Blockcerts WebofTrustInfo Open Badges rwot6-santabarbera Open Badges are Verifable Credentials 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. https://nbviewer.jupyter.org/github/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/open-badges-are-verifiable-credentials.pdf Paper Open Badges 2018-06-22
448 Blockcerts Draftin Open Badges OPEN BADGES ON THE BLOCKCHAIN This document gives an overview of the status, interesting companies and people regarding Verifiable Open Badges on the Blockchain. https://draftin.com/documents/1138961?token=hQ5q0mCHizZum8-pkDFYUZr4YFYOWMN01BPT-5uX00hAaGxYOAlgAlhyenat76hjNpTCs-CMWPI38KWn_omp0Oc Paper Open Badges 2019-07-19
449 Blockcerts FSMB Healthcare and Digital Credentials: Technical, Legal, and Regulatory Considerations Credentials expressed through a trusted identity framework can be accorded a higher value within a social interaction due to the underlying assumption that someone within the system is managing the creation and transfer of these credentials. Within any high functioning identity framework specifications, rules, and agreements based in both technological capacity and social need are necessary to ensure that the level of trustworthiness required by participants in the identity system and the community relying on the services offered by the identity system is met. https://www.fsmb.org/siteassets/digital-credentials/digital-credentials-report-june-2019.pdf Report Literature 2019-06
474 Blockcerts Blockcerts An iOS wallet for viewing, validating, and sharing certs This repository contains the core modules used to implement Blockcerts functionality in iOS. https://github.com/blockchain-certificates/BlockcertsFramework-iOS Code Development; Apps 2022-09-19
475 Blockcerts Blockcerts An iOS wallet for Blockcerts. Blockcerts mobile app for iOS to receive and share certificates that are verifiable via the blockchain https://github.com/blockchain-certificates/wallet-iOS Code Development; Apps 2022-02-17
476 Linked Data TwoBitHistory Whatever Happened to the Semantic Web? In 2001, Tim Berners-Lee, inventor of the World Wide Web, published an article in Scientific American. Berners-Lee, along with two other researchers, Ora Lassila and James Hendler, wanted to give the world a preview of the revolutionary new changes they saw coming to the web. Since its introduction only a decade before, the web had fast become the world’s best means for sharing documents with other people. Now, the authors promised, the web would evolve to encompass not just documents but every kind of data one could imagine https://twobithistory.org/2018/05/27/semantic-web.html Post Getting Started 2018-05-27
477 Linked Data W3C LinkedData - W3C Wiki The idea behind these principles is on the one hand side, to use standards for the representation and the access to data on the Web. On the other hand, the principles propagate to set hyperlinks between data from different sources. These hyperlinks connect all Linked Data into a single global data graph, similar as the hyperlinks on the classic Web connect all HTML documents into a single global information space. Thus, LinkedData is to spreadsheets and databases what the Web of hypertext documents is to word processor files. The Linked Open Data cloud diagramms give an overview of the linked data sets that are available on the Web. https://www.w3.org/wiki/LinkedData https://www.w3.org/wiki/resources/assets/poweredby_mediawiki_88x31.png entry Getting Started 2016-08-01
478 Linked Data W3C Tim Berners Lee Linked Data - Design Issues The Semantic Web isn't just about putting data on the web. It is about making links, so that a person or machine can explore the web of data. With linked data, when you have some of it, you can find other, related, data.<br>Like the web of hypertext, the web of data is constructed with documents on the web. However, unlike the web of hypertext, where links are relationships anchors in hypertext documents written in HTML, for data they links between arbitrary things described by RDF,. The URIs identify any kind of object or concept. But for HTML or RDF, the same expectations apply to make the web grow:<br>- Use URIs as names for things<br>- Use HTTP URIs so that people can look up those names.<br>- When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL)<br>- Include links to other URIs. so that they can discover more things. https://www.w3.org/DesignIssues/LinkedData https://www.w3.org/DesignIssues/diagrams/lod/597992118v2_350x350_Back.jpg page Getting Started 2006-07-27
479 Linked Data Semantalytics Awesome Semantic Web A curated list of various semantic web and linked data resources. https://github.com/semantalytics/awesome-semantic-web list Getting Started 2023-04-26
480 Linked Data Nandana Mihindukulasooriya Awesome Linked Data A list of tools for publishing and consuming Linked Data. https://github.com/nandana/awesome-linkeddata list Getting Started 2017-03-07
484 Linked Data Read-Write Linked Data Examples in the Wild << Pretty Awesome List dokieli is a decentralised article authoring, annotation, and social notification tool which works from Web browsers. It is built with the following principles in mind: freedom of expression, decentralisation, interoperability, and accessibility. https://github.com/linkeddata/dokieli/wiki wiki Getting Started 2019-07-03
485 Linked Data Solid Understanding Linked Data slide deck (in Remark.js format) A slide deck introduction to Linked Data aimed at developers. https://github.com/solid/understanding-linked-data Presentation Getting Started 2019-10-03
486 Linked Data LinkedDataTools Introducing Linked Data And The Semantic Web What is Linked Data and the Semantic Web and what is all the hype about? Principally, the Semantic Web is a Web 3.0 web technology - a way of linking data between systems or entities that allows for rich, self-describing interrelations of data available across the globe on the web. http://www.linkeddatatools.com/semantic-web-basics https://2mye7d.n3cdn1.secureserver.net/wp-content/uploads/2023/02/semantic-web-learning-curve.png page Getting Started 2011-06-12
487 Linked Data Personal Ruben Verborgh Designing a Linked Data developer experience Making decentralized Web app development fun<br>While the Semantic Web community was fighting its own internal battles, we failed to gain traction with the people who build apps that are actually used: front-end developers. Ironically, Semantic Web enthusiasts have failed to... https://ruben.verborgh.org/blog/2018/12/28/designing-a-linked-data-developer-experience/ https://ruben.verborgh.org/images/blog/front-end-devs.jpg Post Main 2018-12-28
488 Linked Data WebofTrustInfo Christopher Lemmer Webber, Mark S. Miller rwot05-boston Linked Data Capabilities Linked Data Signatures enable a method of asserting the integrity of linked data documents that are passed throughout the web. The object capability model is a powerful system for ensuring the security of computing systems. In this paper, we explore layering an object capability model on top of Linked Data Signatures via chains of signed proclamations. fn:1 We call this system "Linked Data Capabilities", or "ld-ocap" for short. https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/final-documents/lds-ocap.md Paper Main 2022-12-28
489 Linked Data WebofTrustInfo rwot3-sf Identity as Linked Data on Immutable Ledgers Content creators on the Web are getting a raw deal. They get a fraction of a cent for an ad played on YouTube, and nothing on Facebook, for filling these sites with traffic-driving content. It’s hard to make a living when you’re a creative. Licensing is hard; the user experience is bad, so lawyers and middlemen extract the most value. In the music industry, more money flows into the pockets of distributors than creatives. Consumers are often happy to pay for their content. Instead, they're forced to sit through ads. https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/identity-as-linked-data-on-immutable-ledgers.md Paper Main 2016-10-17
490 Linked Data WebofTrustInfo Manu Sporny, Harlan Wood, Noah Thorp, Wayne Vaughn, Christopher Allen, Jason Bukowski, and Dave Longley rwot3-sf Blockchain Extensions for Linked Data Signatures The term Linked Data is used to describe a recommended best practice for exposing, sharing, and connecting information on the Web using standards, such as URLs, to identify things and their properties. When information is presented as Linked Data, other related information can be easily discovered and new information can be easily linked to it. Linked Data is extensible in a decentralized way, greatly reducing barriers to large scale integration.<br>With the increase in usage of Linked Data for a variety of applications, there is a need to be able to verify the authenticity and integrity of Linked Data documents. The Linked Data Signatures specification added authentication and integrity protection to linked data documents through the use of public/private key cryptography without sacrificing Linked Data features such as extensibility and composability. https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/blockchain-extensions-for-linked-data-signatures.md Paper Main 2016-10-30
491 Linked Data WebofTrustInfo Ganesh Annan, Kim Hamilton Duffy rwot7-toronto Resource Integrity Proofs Cryptographic linking provides discoverability, integrity, and scheme agility<brContributors: Manu Sporny, Dave Longley, David Lehn, and Bohdan Andriyiv<br>Currently, the Web provides a simple yet powerful mechanism for the dissemination of information via links. Unfortunately, there is no generalized mechanism that enables verifying that a fetched resource has been delivered without unexpected manipulation. Would it be possible to create an extensible and multipurpose cryptographic link that provides discoverability, integrity, and scheme agility?<br>Cryptographic linking solutions today have yet to provide a generalized mechanism for creating tamper-evident links. The Subresource Integrity standard limits this guarantee to script and link resources loaded on Web pages via the use of HTML attributes. IPFS provides a verification mechanism that is constrained to hash-based, content-addressable links, with no ability to complete content negotiation. RFC6920 proposes another mechanism that cannot be applied to existing links: it recommends the use of named information hashes and a resolution method that creates a content addressable URL [1]. Resource Integrity Proofs incorporates ideas from these standards and solutions to provide a new data format for cryptographic links that is fit for the open world. Cryptographic linking provides discoverability, integrity, and scheme agility<br>Contributors: Manu Sporny, Dave Longley, David Lehn, and Bohdan Andriyiv<br>Currently, the Web provides a simple yet powerful mechanism for the dissemination of information via links. Unfortunately, there is no generalized mechanism that enables verifying that a fetched resource has been delivered without unexpected manipulation. Would it be possible to create an extensible and multipurpose cryptographic link that provides discoverability, integrity, and scheme agility?<br>Cryptographic linking solutions today have yet to provide a generalized mechanism for creating tamper-evident links. The Subresource Integrity standard limits this guarantee to script and link resources loaded on Web pages via the use of HTML attributes. IPFS provides a verification mechanism that is constrained to hash-based, content-addressable links, with no ability to complete content negotiation. RFC6920 proposes another mechanism that cannot be applied to existing links: it recommends the use of named information hashes and a resolution method that creates a content addressable URL [1]. Resource Integrity Proofs incorporates ideas from these standards and solutions to provide a new data format for cryptographic links that is fit for the open world. https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/resource-integrity-proofs.md Paper Main 2018-12-12
492 Linked Data WebofTrustInfo rwot6-santabarbera Recent happenings with Linked Data Capabilities Veres One's architecture has been adjusted to take full advantage of Linked Data Capabilities as its primary mechanism for granting authority to perform operations on the ledger as well as on DID Documents. permission to update key materials can be conditionally handed out to an entity (or entities) and later revoked if deemed appropriate using Linked Data Capabilities' design.<br>As for ledger updates, Accelerators also make use of Linked Data Capabilities. To prevent spamming the ledger, the costs of an update must somehow be accounted for. The traditional way to do this on a blockchain is to use proof of work, and this is also an option in Veres One, but for those use cases where expending time and energy on proof of work is less desirable users can use an "accelerator".<br>An accelerator is an entity that has been granted a capability to perform updates on the ledger more quickly. Accelerators may likewise take advantage of Linked Data Capabilities' support for delegation, with or without caveats. https://github.com/WebOfTrustInfo/rwot6-santabarbara/blob/master/topics-and-advance-readings/ld-ocap-recent-happenings.md Paper Main 2018-03-02
493 Linked Data WebofTrustInfo rwot4-paris LD Signature Format Alignment The goal of the "LD Signature Format Alignment" Working Group at Rebooting the Web of Trust IV was to investigate the feasibility and impact of the proposed 2017 RSA Signature Suite spec, which brings JSON-LD signatures into alignment with the JOSE JSON Web Signature (JWS) standards.The 2017 RSA Signature Suite is based on RFC 7797, the JSON Web Signature (JWS) Unencoded Payload Option specifcation. This approach avoids past concerns about JWT raised in the LD signature adopters, including:•Increased space consumption associated withbase-64 encoding.•Difculty of nesting or chaining signatures, leading to data duplication.•Use of a format that is not a JSON object, preventing ability to rely exclusively on a JSON document-based storage engine (whilepreserving the signature) https://nbviewer.jupyter.org/github/WebOfTrustInfo/rwot4-paris/blob/master/final-documents/ld-signatures.pdf Paper Main 2017-08-18
494 Linked Data CCG Authorization Capabilities for Linked Data v0.3 Authorization Capabilities for Linked Data (ZCAP-LD for short) provides a secure way for linked data systems to grant and express authority utilizing the object capability model. Capabilities are represented as linked data objects which are signed with Linked Data Proofs. ZCAP-LD supports delegating authority to other entities on the network by chaining together capability documents. "Caveats" may be attached to capability documents which may be used to restrict the scope of their use, for example to restrict the actions which may be used or providing a mechanism by which the capability may be later revoked. https://w3c-ccg.github.io/zcap-spec/ Specification Main Credentials Community Group 2023-01-22 https://github.com/w3c-ccg/zcap-spec
497 Linked Data CCG Linked Data Keys Registry This repository contains the Linked Data Cryptographic Suite Registry which is a list of all known Linked Data cryptographic suites and their current level of maturity. https://github.com/w3c-ccg/ld-cryptosuite-registry registry Implementation Credentials Community Group 2020-12-29
498 Linked Data DigitalBazaar Linked Data Capabilities reference implementation JavaScript reference implementation for Authorization Capabilities. https://github.com/digitalbazaar/ocapld.js Code Implementation 2023-01-14
499 Linked Data W3C RDF AND JSON-LD UseCases This wiki page strive to address one of many question about use of RDF vs JSON-LD to store linked data. This page attempts to provide a general introduction of both the technologies and provide suitability analysis of various kind of applications to use either technology. https://www.w3.org/2013/dwbp/wiki/RDF_AND_JSON-LD_UseCases https://www.w3.org/2013/dwbp/wiki/images/thumb/1/17/RDFSerialization-formats.png/800px-RDFSerialization-formats.png page RDF 2014-09-15
500 Linked Data W3C Comparison of RDFJS libraries This is a comparison of JavaScript libraries for working with RDF. https://www.w3.org/community/rdfjs/wiki/Comparison_of_RDFJS_libraries https://www.w3.org/community/rdfjs/wiki/resources/assets/poweredby_mediawiki_88x31.png entry RDF 2019-01-18
501 Linked Data W3C RDF.js: The new RDF and Linked Data JavaScript library A diverse web requires decentralized data storage and maintenance. According to MIT’s Tim Berners-Lee, “it is about making links, so that a person or machine can explore the web of data. With Linked Data, when you have some of it, you can find other, related, data”.<br><br>Zazuko’s CTO Thomas Bergwinkl adds that “Linked Data is built on top of the web stack and the programming language of the web is JavaScript. It is crucial for Web Developers to have access to well-designed JavaScript libraries to work with RDF and Linked Data”.<br><br>The RDFJS W3C Community Group did a tremendous job in defining a standard to represent Linked Data in JavaScript. Several individuals and groups started to implement the RDFJS specification. https://www.w3.org/community/rdfjs/2018/04/23/rdf-js-the-new-rdf-and-linked-data-javascript-library/ Post RDF 2018-04-23
502 Linked Data RCH Working Group CCG RDF Dataset Canonicalization RDF [RDF-CONCEPTS] describes a graph-based data model for making claims about the world and provides the foundation for reasoning upon that graph of information. At times, it becomes necessary to compare the differences between sets of graphs, digitally sign them, or generate short identifiers for graphs via hashing algorithms. This document outlines an algorithm for normalizing RDF datasets such that these operations can be performed. https://w3c.github.io/rdf-canon/spec/ Report RDF 2023-05-24 https://github.com/w3c/rdf-canon/
503 GS1 GS1 GS1 - How we got here Since 1973, we have opened offices in over 110 countries and amassed more than 2 million members using supply chain standards that make business easier. Learn about key dates in our history.<br- 1973: The barcode standard is agreed<br- 1974: The first barcode is scanned<br- 1977: The GS1 system is launched<br- 1983: Barcodes are used on wholesale multi-packs<br- 1989: GS1 moves beyond barcodes<br - With wide area networks making an impact on supply chains, we create our first international standard for electronic data interchange.<br- 1990: Responsibilities grow<br - The US and international arms of GS1 come together formally, creating a single organisation with a presence in 45 countries.<br- 1995: First healthcare standards created<br- 1999: The GS1 DataBar arrives<br- 2000: 90th local office opens<br - In just ten years, we double the number of countries in which we have a local presence.<br- 2002: Global standards forum launched<br - Our Global Standards Management Process is launched. This global forum gives GS1 members one place to discuss standards.<br- 2004: The first standard for RFID is created<br- 2007: GS1 enters the business-to-consumer world<br - As ecommerce grows, we begin to create open standards that give consumers direct access to key product information.<br- 2013: A 40-year celebration<br - With a presence in over 100 countries and more than a million members, we celebrate 40 years of the global language of business. Since 1973, we have opened offices in over 110 countries and amassed more than 2 million members using supply chain standards that make business easier. Learn about key dates in our history.<br>- 1973: The barcode standard is agreed<br>- 1974: The first barcode is scanned<br>- 1977: The GS1 system is launched<br>- 1983: Barcodes are used on wholesale multi-packs<br>- 1989: GS1 moves beyond barcodes<br> - With wide area networks making an impact on supply chains, we create our first international standard for electronic data interchange.<br>- 1990: Responsibilities grow<br> - The US and international arms of GS1 come together formally, creating a single organisation with a presence in 45 countries.<br>- 1995: First healthcare standards created<br>- 1999: The GS1 DataBar arrives<br>- 2000: 90th local office opens<br> - In just ten years, we double the number of countries in which we have a local presence.<br>- 2002: Global standards forum launched<br> - Our Global Standards Management Process is launched. This global forum gives GS1 members one place to discuss standards.<br>- 2004: The first standard for RFID is created<br>- 2007: GS1 enters the business-to-consumer world<br> - As ecommerce grows, we begin to create open standards that give consumers direct access to key product information.<br>- 2013: A 40-year celebration<br> - With a presence in over 100 countries and more than a million members, we celebrate 40 years of the global language of business. https://www.gs1.org/about/how-we-got-here https://gs1go2.azureedge.net/cdn/ff/72KV_kX-aZGtwUlmD5KjuSzFpY-TPv1WkMRH0_CHCVE/1675165342/public/2023-01/1973.png page Main 2023-04-25
504 GS1 GS1 Standards development A neutral participant, GS1 facilitates dialogue and the development of standards-based solutions among business and technical people from nearly sixty countries. Industries represented include retail and consumer goods, fresh foods, healthcare, transport and logistics, governments and many more.<br><br>The GSMP (Global Standards Management Process) is a community-based forum for businesses facing similar problems to work together and develop standards-based solutions. Standards created by industry, for industry. The GSMP (Global Standards Management Process) is a community-based forum for businesses facing similar problems to work together and develop standards-based solutions. Standards created by industry, for industry. https://www.gs1.org/standards/development https://gs1go2.azureedge.net/cdn/ff/Vts5yHWR2YqcWFYp2bXZSKYgfHhlDZVDNC-giMBOFYs/1635150532/public/2021-06/thumb_video_standards_0.png page Main 2023-04-25
505 GS1 GS1 How we develop standards Our standards development team guide the regular upgrading of our standards through a document development life cycle whose rules everyone agrees to. The Global Standards Management Process (GSMP) enables us to reach consensus around the creation and adoption of new standards smoothly and rapidly! We develop our global supply chain standards in partnership with the industry experts and business teams who actually use them. Find out how we do it. https://www.gs1.org/how-we-develop-standards https://gs1go2.azureedge.net/cdn/ff/j98vq8ZwoGIDZaJf1YJMp_IQ0Vxr7IlpF5CWqXSrmGE/1639585169/public/2021-12/why-join-workgroup.png page Main 2023-04-27
506 GS1 IDCommons IIW30 GS1's decentralized approach to resolving identifiers over HTTPS Slides are at http://docs.google.com/presentation/d/1fLDETcghxxRfac7mDCTGpqktaVnn9bjl/edit# General principles paper is at http://gs1.github.io/DigitalLinkDocs/principles/<br><br>GS1 DIgital Link standard makes the standard product Identifier - the “UPC” code web resolvable. Making it do more than go beep at the check out.<br><br>SSI / DIDs “not central point of issuance, no single point of failure”...but we can meet those requirements with persistent identifiers with centralized federation… centralized + delegation can work. https://iiw.idcommons.net/GS1%27s_decentralized_approach_to_resolving_identifiers_over_HTTPS Session Notes Main 2009-06-18
507 GS1 IDCommons https://gs1.github.io/DigitalLinkDocs/principles/ Phil Archer, Mark Harrison, Henri Barthel IIW30 Decentralized resolution of identifiers with HTTPS 11 Transferable Principles from GS1 Digital Link https://docs.google.com/presentation/d/1fLDETcghxxRfac7mDCTGpqktaVnn9bjl/edit#slide=id.p1 https://lh3.googleusercontent.com/docs/ADP-6oHa-ouWp6hpdtK-96YC0Ar-fwMZxk26EYXKOlxsExdj5_JUeW6Ee6R6qXgneyJetUEcnuab9B5Cy_d8gxyFxF9-P_AugQ=w1200-h630-p Presentation Main 2020-04
508 GS1 GS1 GSMP Manual The GSMP 4-Step Process is designed to ensure that business needs and requirements are understood before standards and guidelines are developed, and that supporting materials are created afterward. Each step culminates in the completion of one or more outputs, created through a consensus-based process within a working group and with larger consensus confirmed through community review and eBallot. https://www.gs1.org/docs/gsmp/GSMP_Manual.pdf docs Global Standards Mapping Process 2022-07
509 GS1 GS1 Global Data Model (GDM) Governance Manual The retail landscape is changing at an unprecedented rate. In this connected world, consumers increasingly rely on product information for purchasing decisions. The purpose of the Global Data Model (GDM) is to simplify and harmonise the exchange of master data. The GDM will identify and define—in a globally consistent way—the set of foundational attributes needed to list/order, move, store and sell a product, both digitally and physically. By harmonising foundational data across the industry around the globe, it will enable an improved consumer experience and reduce complexity by delivering more reliable and complete product information to consumers. https://www.gs1.org/sites/default/files/docs/gsmp/gdm_manual_i1_a_2020-03-19.pdf docs Global Standards Mapping Process 2020-03-19
510 GS1 GS1 GSMP Value Statement Are business challenges holding back your company’s full potential and growth? You are not alone. Business is easier when you speak the same language as your customers, suppliers and partners. Though we all work in our own way, problems and differences become solutions when we all work together. That’s where GS1 can help.<br><br>The GSMP is a community-based forum for businesses facing similar problems to work together and develop standards-based solutions to address them. Standards created by industry, for industry. https://www.gs1.org/sites/default/files/docs/gsmp/gsmp_execsummary.pdf docs Global Standards Mapping Process 2015-10-02
511 GS1 GS1 https://www.gs1.org/standards/development-work-groups GSMP Data Accuracy SMG This processes all maintenance Work Requests for the **[GS1 Package Measurement Rules Standard](https://www.gs1.org/docs/gdsn/3.1/GS1_Package_Measurement_Rules.pdf)** and the **[Package Measurement Rules Implementation Guideline](https://www.gs1.org/sites/default/files/docs/gdsn/GDSN_Pack_Measure_Rules_Implementation_Guide.pdf)**. This group acts as a pool of experts for all Data Accuracy SMG work requests and coordinate with associated Mission Specific groups as defined in the GSMP Manual. The work the Data Accuracy SMG allows our community to increase savings throughout the supply chain by synchronising accurate dimensions and weight data which enables better transportation, logistics and retail shelf planning. https://www.gs1.org/standards/development-work-groups#DA https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png Working Group Working Groups 2010-04-15
512 GS1 GS1 https://www.gs1.org/standards/development-work-groups GSMP Electronic Data Interchange (EDI) SMG This group maintains and improves [GS1 EDI (Electronic Data Interchange) standards](https://www.gs1.org/standards/edi). Examples of standards maintained in this group (but not limited to) are:<br>- EANCOM®<br>- GS1 XML<br>- GS1 UN/CEFACT XML https://www.gs1.org/standards/development-work-groups#EDI https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png Working Group Working Groups 2010-04-15
513 GS1 GS1 https://www.gs1.org/standards/development-work-groups GSMP Global Master Data (GMD) SMG The group maintains and improves the GS1 Master Data standards. Examples of standards maintained in this group (but not limited to) are:<br- [Master Data Standards](https://www.gs1.org/standards/gs1-global-data-model)<br- GS1 Attributes, definitions, code lists, and guidance definitions<br- [GDSN solutions and GDSN Validation Rules](https://www.gs1.org/standards/gdsn)<br- GS1 Web Vocabulary<br- Global Data Model Standards and Attribute Definitions for Business The group maintains and improves the GS1 Master Data standards. Examples of standards maintained in this group (but not limited to) are:<br>- [Master Data Standards](https://www.gs1.org/standards/gs1-global-data-model)<br>- GS1 Attributes, definitions, code lists, and guidance definitions<br>- [GDSN solutions and GDSN Validation Rules](https://www.gs1.org/standards/gdsn)<br>- GS1 Web Vocabulary<br>- Global Data Model Standards and Attribute Definitions for Business https://www.gs1.org/standards/development-work-groups#GMD https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png Working Group Working Groups 2013-12-14
514 GS1 GS1 https://www.gs1.org/standards/development-work-groups GSMP Global Product Classification (GPC) SMG The GPC Standards Maintenance Group maintains and improves the GS1 Global Product Classification (GPC) standard.<br><br>The [GS1 Global Product Classification (GPC) standard](https://www.gs1.org/standards/gpc) helps global trading partners to group products in the same way, everywhere in the world. The resulting common business language is clear and instantly understandable. https://www.gs1.org/standards/development-work-groups#GPC https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png Working Group Working Groups 2010-04-15
515 GS1 GS1 https://www.gs1.org/standards/development-work-groups GSMP Identification SMG The ID Standards Maintenance Group maintains and improves the GS1 Automatic Identification and Data Capture (AIDC) standards including Identification Keys, Barcodes, Electronic Product Code, and Radio-Frequency Identification (RFID) standards.<br><br- The GS1 General Specification is the core foundational GS1 standard that defines how identification keys, data attributes and barcodes must be used in business applications<br- GS1 Identification Keys provides companies efficient ways to access and share information about items in their supply chains.<br- Barcodes are symbols that can be scanned electronically using laser or camera-based systems.<br- The Electronic Product Code™ (EPC) is syntax for unique identifiers assigned to physical objects, unit loads, locations, or other identifiable entity playing a role in business operations.<br- GS1's EPC Tag Data Standard (TDS) defines the Electronic Product Code (EPC), including its correspondence to GS1 keys and other existing codes. TDS also specifies data that is carried on Gen 2 RFID tags, including the EPC, User Memory data, control information, and tag manufacture information. The ID Standards Maintenance Group maintains and improves the GS1 Automatic Identification and Data Capture (AIDC) standards including Identification Keys, Barcodes, Electronic Product Code, and Radio-Frequency Identification (RFID) standards.<br><br>- The GS1 General Specification is the core foundational GS1 standard that defines how identification keys, data attributes and barcodes must be used in business applications<br>- GS1 Identification Keys provides companies efficient ways to access and share information about items in their supply chains.<br>- Barcodes are symbols that can be scanned electronically using laser or camera-based systems.<br>- The Electronic Product Code™ (EPC) is syntax for unique identifiers assigned to physical objects, unit loads, locations, or other identifiable entity playing a role in business operations.<br>- GS1's EPC Tag Data Standard (TDS) defines the Electronic Product Code (EPC), including its correspondence to GS1 keys and other existing codes. TDS also specifies data that is carried on Gen 2 RFID tags, including the EPC, User Memory data, control information, and tag manufacture information. https://www.gs1.org/standards/development-work-groups#ID https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png Working Group Working Groups 2010-04-15
516 GS1 GS1 GSMP Traceability and Event Sharing Standards Maintenance Group SMG The SMG maintains updates to the GS1 EPCglobal standards that support physical event capture and sharing and the [Global Traceability Standard that supports tracking and tracing of goods](https://www.gs1.org/sites/default/files/docs/gsmp/call_to_action_gtc_h.pdf) and information about the goods. This includes all simple work requests indicated as impacting the event data sharing and traceability standards.<br><br>In addition, the group acts as a pool of experts for all Mission Specific Work Groups that are related to the SMG, as defined in the GSMP Manual in section 3.4. Work Groups. https://www.gs1.org/standards/development-work-groups#TRACE_EVENT https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png Working Group Working Groups 2011-05-26
517 GS1 GS1 GSMP Digital Signature MSWG Provide a GS1 standard solution approach to digital signatures. Otherwise, there will be no open, brand owner determined digital signatures to set as an alternative to proprietary digital signature use in barcodes with GS1 standards. Mission-specific Working Groups (MSWGs) develop new standards https://www.gs1.org/standards/development-work-groups#DigitalSignature https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png Working Group Working Groups 2020-03-26
518 GS1 GS1 GSMP EPCIS & CBV 2.0 MSWG Since its initial ratification as an EPCglobal standard in 2007 and its subsequent integration into the GS1 “Share” portfolio, EPCIS and its companion standard the Core Business Vocabulary (CBV) have been updated twice (2014 and 2016) and published by ISO (as ISO/IEC 19987 and 19988, respectively). In the meantime, EPCIS and the CBV have gained importance as visibility enablers in various industries. Updates are needed to ensure the relevance of these standards into the coming decades. Mission-specific Working Groups (MSWGs) develop new standards https://www.gs1.org/standards/development-work-groups#EPCISCBV https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png Working Group Working Groups 2018-02-19
519 GS1 GS1 GSMP GLN Modernisation MSWG This work group will update the GLN Standards to be more clear and concise and provide guidance to enable industry partners to create, manage, share, and use the GLN to meet their party and location use cases needs in a scalable, standardised manner. Mission-specific Working Groups (MSWGs) develop new standards https://www.gs1.org/standards/development-work-groups#GLNM https://gs1go2.azureedge.net/cdn/ff/TjtVDccMMldeo9WSBIJWvvCBUdA0vh899UqiaVbf90Y/1681480847/public/inline-images/gsmp-gs1-circularity-digital-product-passport-mswg_2.png Working Group Working Groups 2022-08-16
520 Object Capabilities Personal Dan Connolly Awesome Object Capabilities and Capability-based Security Capability-based security enables the concise composition of powerful [patterns](https://github.com/dckc/awesome-ocap/wiki) of cooperation without vulnerability. [What Are Capabilities?](http://habitatchronicles.com/2017/05/what-are-capabilities/) explains in detail. https://github.com/dckc/awesome-ocap list Main 2023-03-03
521 Object Capabilities Wikipedia Object Capability Model Computer scientist E. Dean Tribble stated that in smart contracts, identity-based access control did not support well dynamically changing permissions, compared to the object-capability model. He analogized the ocap model with giving a valet the key to one's car, without handing over the right to car ownership.<br><br>The structural properties of object capability systems favor modularity in code design and ensure reliable encapsulation in code implementation.<br><br>These structural properties facilitate the analysis of some security properties of an object-capability program or operating system. Some of these – in particular, information flow properties – can be analyzed at the level of object references and connectivity, independent of any knowledge or analysis of the code that determines the behavior of the objects. As a consequence, these security properties can be established and maintained in the presence of new objects that contain unknown and possibly malicious code. https://en.wikipedia.org/wiki/Object-capability_model entry Main 2023-04-12
522 Object Capabilities eRights Mark S. Miller Object Capabilities The capability model is, in a sense, the object model taken to its logical extreme. Where object programmers seek modularity -- a decrease in the dependencies between separately thought-out units -- capability programmers seek security, recognizing that required trust is a form of dependency. Object programmers wish to guard against bugs: a bug in module A should not propagate to module B. Capability programmers wish to guard against malice. However, if B is designed to be invulnerable to A's malice, it is likely also invulnerable to A's bugs. E: Cryptographic Capabilities for Distributed Smart Contracting http://erights.org/elib/capability/ode/ode-capabilities.html http://erights.org/elib/capability/ode/images/money.png page Main 1998-10-03
533 DIDComm CCG Mailing List Daniel Hardman CCG announcement: DIDComm user group Now that the [DIDComm v2 spec](https://identity.foundation/didcomm-messaging/spec/) is nearing completion, and there are [robust libraries in multiple programming languages](https://github.com/decentralized-identity/didcomm-messaging#implementations), we are starting a user group to share learnings as we put DIDComm into production. We will organize community resources, produce a handbook, foster application-level protocol creation, maintain the [didcomm.org website](https://didcomm.org) and [repo](https://github.com/decentralized-identity/didcomm.org), and recommend best practices. https://lists.w3.org/Archives/Public/public-credentials/2022Jan/0168.html Discussion main 2022-01-20
534 DIDComm CCG Mailing List https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0032.html CCG DIDComm V2 Primer 1. What it is<br>2. What it does and doesn't do<br>3. Relationship to WACI-DIDComm, CHAPI, OIDC-SIOP<br>4. Versions<br>5. Implementations https://lists.w3.org/Archives/Public/public-credentials/2022Apr/att-0032/DIDComm_v2_Primer.pdf Discussion main 2022-04
535 DIDComm didcomm.org didcomm.org DIDComm lets people and software use [DIDs](https://www.w3.org/TR/did-core/) to communicate securely and privately over many channels: the web, email, mobile push notifications, QR codes, Bluetooth, message queues, sneakernet, and more. https://didcomm.org/ site main
536 DIDComm DIF DIDComm WG https://github.com/decentralized-identity/org/blob/master/Org%20documents/WG%20documents/DIF_DIDcomm_WG_Charter_v1.pdf DIDComm Working Group DID Communications Working Group Join this group to contribute to specs that embody a method for secure, private and authenticated message-based communication, where trust is rooted in DIDs and used over a wide variety of transports. https://identity.foundation/working-groups/did-comm.html Working Group main Working Group 2020-08-18 2020-09-18 https://github.com/decentralized-identity/didcomm-messaging/ https://dif.groups.io/g/didcomm-wg
537 DIDComm DIF Sam Curren, Tobias Looker, Oliver Terbu, Kyle Den Hartog, Baha Shaaban, Drummond Reed, Steve McCown, Troy Ronda, George Aristy, Vyacheslav Gudkov, Alexander Shcherbakov, Alexander Martynov, Daniel Buchner, Devin Fisher, Orie Steele, Brian Richter, Juan Caballero, @liormargalit, Timo Glastra, Andrew Whitehead, Nader Helmy, Markus Sabadello, Patrick McClurg, Stephen Curran, Daniel Hardman, Moe Jangda Indicio, TBD, SICPA, Danube Tech, MATTR, Animo, Aviary, Transmute, Centre, Microsoft, Evernym, DSR, SecureKey, ConsenSys, BCGov, Anonyome DIDComm Messaging DIDComm V2 reaches approved spec status! DIDComm Messaging enables higher-order protocols that inherit its security, privacy, decentralization, and transport independence. Examples include exchanging verifiable credentials, creating and maintaining relationships, buying and selling, scheduling events, negotiating contracts, voting, presenting tickets for travel, applying to employers or schools or banks, arranging healthcare, and playing games. Like web services atop HTTP, the possibilities are endless; unlike web services atop HTTP, many parties can participate without being clients of a central server, and they can use a mixture of connectivity models and technologies. And these protocols are composable into higher-order workflows without constantly reinventing the way trust and identity transfer across boundaries. Following the approval of the Decentralized Identifiers (DID) Core Spec by the W3C as an official open web standard, the Decentralized Identity Foundation (DIF) announced the approval of the DIDComm v2 specification. Combined, this represents a major step forward in the acceptance of decentralized identity, one that opens the path to widespread adoption and further development especially with regard to the types of peer-to-peer communication now possible.<br><br>DIDComm defines how messages are composed into application-level protocols and workflows. DIDComm v2 has now reached DIF Approved Status, joining SideTree as a complete and approved open-source specification. https://identity.foundation/didcomm-messaging/spec/ https://blog.identity.foundation/didcomm-v2/ https://identity.foundation/didcomm-messaging/collateral/problem-code-structure.png Specification Post Spec Working Group DIDComm WG 2022-04-12 2022-07-26
538 DIDComm IDCommons DIDComm WG https://docs.google.com/presentation/d/16HTPyZV_-BtM6EifQpxjivRHKYUeVtOAReUD1eGUA9M/edit?usp=sharing Sam Curren Sam Curren, Tobias Looker, Oliver Terbu, Kyle Den Hartog, Baha Shaaban, Drummond Reed, Steve McCown, Troy Ronda, George Aristy, Vyacheslav Gudkov, Alexander Shcherbakov, Alexander Martynov, Daniel Buchner, Devin Fisher, Orie Steele, Brian Richter, Juan Caballero, @liormargalit, Timo Glastra, Andrew Whitehead, Nader Helmy, Markus Sabadello, Patrick McClurg, Stephen Curran, Daniel Hardman, Moe Jangda Indicio, TBD, SICPA, Danube Tech, MATTR, Animo, Aviary, Transmute, Centre, Microsoft, Evernym, DSR, SecureKey, ConsenSys, BCGov, Anonyome IIW 2D/ Why the Internet Needs DIDComm - IIW DIDComm Messaging v2.1 Editor’s Draft - Enables Verifiable Communication<br - Intelligence at the edge (like email)<br - Protocol Based (like email)<br - Supports HTTP(s) (like APIs) and others as a transport<br - Bluetooth enables Edge to Edge transport<br - Mobile / Offline Friendly (like email)<br - Supports rotating from one DID to another<br - Security independent of transport<br - Protocol development becomes easier and more robust (unlike email) DIDComm enables higher-order protocols that inherit its security, privacy, decentralization, and transport independence. Examples include exchanging verifiable credentials, creating and maintaining relationships, buying and selling, scheduling events, negotiating contracts, voting, presenting tickets for travel, applying to employers or schools or banks, arranging healthcare, and playing games. Like web services atop HTTP, the possibilities are endless; unlike web services atop HTTP, many parties can participate without being clients of a central server, and they can use a mixture of connectivity models and technologies. https://iiw.idcommons.net/2D/_Why_the_Internet_Needs_DIDComm https://identity.foundation/didcomm-messaging/spec/ Session Notes Specification Explainer Working Group 2021-05-06 2023-04-26 https://github.com/decentralized-identity/didcomm-messaging
539 DIDComm IDCommons DIDComm WG Paul Knowles IIW 2E/ Decentralized Semantics 101 - IIW DIDcomm WG Operating Addendum A digital network must contain authenticable data entry and immutable data<br <br capture elements in order to maintain balance and integrity.<br <br Within the context of a decentralized network, these fundamentals enable a self-regulating system where ...<br <br (1) data inputs can be trusted as having come from an assured source under the control of a governing entity; and<br <br (2) semantic items ensure that the meaning and use of inputted data remains unaltered for all interacting actors. We are designing communications protocols specifically for use with the decentralized identifier specification at W3C (​https://www.w3.org/TR/did-core/​). The DID Core specification and the surrounding family of DID specifications (e.g ​https://w3c-ccg.github.io/did-resolution/​) represent the format for entity identification in our DIDComm efforts. https://iiw.idcommons.net/2E/_Decentralized_Semantics_101 https://github.com/decentralized-identity/org/blob/master/Org%20documents/WG%20documents/DIF_DIDcomm_WG_Operating_Addendum_v1.pdf Session Notes Page Explainer Working Group 2021-05-06 2020-09-18
540 DIDComm DIDComm WG DIF starts DIDComm Working Group Over the past few months, the DIF and Hyperledger Aries community have come together and agreed to work on a common work item aimed at developing secure communication based on Decentralized Identifiers (DIDs) — hence the name DIDComm, which is short for DID Communication. Significant prior work in developing a messaging-based communication protocol using DIDs has been incubating in the HyperLedger (HL) Aries community, with the progress of this effort evident in the resulting [Aries RFCs](https://github.com/hyperledger/aries-rfcs). To address the requirements of a broader and more heterogeneous community we selected DIF as the place to pursue the next phase of work associated with this effort. Presenting the progress of DIDcomm to other relevant working groups will drive the interoperability between the various decentralized identity vendors and hence enabling a range of decentralized identity-related use cases. https://medium.com/decentralized-identity/dif-starts-didcomm-working-group-9c114d9308dc Post Working Group 2020-01-09
541 DIDComm DIDComm WG decentralized-identity/DIDComm-js DIDComm JS LibA shared effort with the HL Aries project to create a standardized means of authenticated general message passing between DID controllers. More information will be added soon. https://github.com/decentralized-identity/DIDComm-js Code Working Group 2020-01-09
542 DIDComm IDCommons https://docs.google.com/presentation/d/16HTPyZV_-BtM6EifQpxjivRHKYUeVtOAReUD1eGUA9M/edit?usp=sharing Sam Curren IIW 2D/ Why the Internet Needs DIDComm - IIW - Enables Verifiable Communication<br> - Intelligence at the edge (like email)<br> - Protocol Based (like email)<br> - Supports HTTP(s) (like APIs) and others as a transport<br> - Bluetooth enables Edge to Edge transport<br> - Mobile / Offline Friendly (like email)<br> - Supports rotating from one DID to another<br> - Security independent of transport<br> - Protocol development becomes easier and more robust (unlike email) https://iiw.idcommons.net/2D/_Why_the_Internet_Needs_DIDComm Session Notes Explainer 2021-05-06
543 DIDComm IDCommons Paul Knowles IIW 2E/ Decentralized Semantics 101 - IIW A digital network must contain authenticable data entry and immutable data<br> <br> capture elements in order to maintain balance and integrity.<br> <br> Within the context of a decentralized network, these fundamentals enable a self-regulating system where ...<br> <br> (1) data inputs can be trusted as having come from an assured source under the control of a governing entity; and<br> <br> (2) semantic items ensure that the meaning and use of inputted data remains unaltered for all interacting actors. https://iiw.idcommons.net/2E/_Decentralized_Semantics_101 Session Notes Explainer 2021-05-06
544 DIDComm IDCommons Phil Windley IIW 21A/ DIDComm and the Self-Sovereign Internet - IIW DID-based relationships are the foundation of self-sovereign identity (SSI). The exchange of DIDs to form a connection with another party gives both parties a relationship that is self-certifying and mutually authenticated. Further, the connection forms a secure messaging channel called DID Communication or DIDComm. DIDComm messaging is more important than most understand, providing a secure, interoperable, and flexible general messaging overlay for the entire internet. https://iiw.idcommons.net/21A/_DIDComm_and_the_Self-Sovereign_Internet Session Notes Explainer 2021-05-06
545 DIDComm Personal Phillip J. Windley DIDComm and the Self-Sovereign Internet DIDComm is a protocol layer capable of supporting specialized application protocols for specific workflows. Because of its general nature and inherent support for self-sovereign relationships, DIDComm provides a basis for a self-sovereign internet much more private, enabling, and flexible than the one we've built using Web 2.0 technologies. This talk introduces DIDComm, discusses its protocological nature, and presents use cases in the Internet of Things. Demonstrations of DIDComm protocol interactions will be shown on the Pico platform, which implements the Aries Cloud Agent (ACA) specification. https://www.windley.com/archives/2020/11/didcomm_and_the_self-sovereign_internet.shtml https://www.windley.com/archives/2020/11/mesh.jpg Post Explainer 2020-11-11
546 DIDComm DIF Kaliya Young Why we need DIDComm - Identity Woman This is the text of an email I got today from a company that I had a contract with last year [...] I was reminded quite strongly why we need DIDComm as a protocol to enable the secure transport of all sorts of things not just signed VCs but intermediate uses https://identitywoman.net/why-we-need-didcomm/ Post Explainer 2022-01-12
547 DIDComm Personal Daniel Hardman DIDComm Mythconceptions DIDComm is a peer-to-peer communication technology for SSI (self-sovereign identity) with security and privacy properties rooted in DIDs (decentralized identifiers). Its core value proposition is often misunderstood or oversimplified. This webinar provides a proper mental model. https://www.youtube.com/watch?v=rwvQdRyMeY4 https://i.ytimg.com/vi/rwvQdRyMeY4/maxresdefault.jpg?sqp=-oaymwEmCIAKENAF8quKqQMa8AEB-AH-CYAC0AWKAgwIABABGGUgXig_MA8=&rs=AOn4CLCxo_GS9BmeYLTCl5mB-923nmd_Vg Video Explainer 2021-11-10
548 DIDComm twit.tv Sam Curren DIDCOMM DIDCOMM - Sam Curren, Importance of DIDs Sam Curren unpacks for Doc Searls and Dan Lynch why DIDs and DIDcomm are the best approach to identity—and to making people first-class citizens on the Internet. Curren also discusses the origin story of picos and the advantages of nomadic living and hacking. https://twit.tv/shows/floss-weekly/episodes/685 https://elroy.twit.tv/sites/default/files/images/episodes/836442/hero/floss_0685.jpg episode Explainer 2022-06-15
DIDComm DIF DIDComm V2 reaches approved spec status! Following the approval of the Decentralized Identifiers (DID) Core Spec by the W3C as an official open web standard, the Decentralized Identity Foundation (DIF) announced the approval of the DIDComm v2 specification. Combined, this represents a major step forward in the acceptance of decentralized identity, one that opens the path to widespread adoption and further development especially with regard to the types of peer-to-peer communication now possible.<br><br>DIDComm defines how messages are composed into application-level protocols and workflows. DIDComm v2 has now reached DIF Approved Status, joining SideTree as a complete and approved open-source specification. https://blog.identity.foundation/didcomm-v2/ Post Spec DIDComm WG 2022-07-26
549 DIDComm Hyperledger Aries RFC 0453 - credential issuance protocol using DIDComm V1 data formats An optional mechanism for providing credential supplements during issuance. Supplements are also used in credential presentation. https://github.com/hyperledger/aries-rfcs/tree/master/features/0453-issue-credential-v2 rfc RFCs Aries RFC 2021-04-15
550 DIDComm Hyperledger Aries RFC 0454 - Present Proof protocol V2 using DIDCommV1 data formats A minor update to add mechanism for a Verifier to request the Prover submit multiple presentations in the "presentation" message(s), each presentation sourced from different credentials that satisfy the presentation request. An example use of this capability is an employer (Verifier) requesting multiple "proof of employment" presentations from a job application (Prover), each satisfying the one presentation request. https://github.com/hyperledger/aries-rfcs/tree/master/features/0454-present-proof-v2 rfc RFCs Aries RFC 2021-04-15
551 DIDComm IDCommons IIW DIDComm V2: Implementation and integration 'technical' - did:key and did:keri resolvers, seamless and partial integrations Technical session covering basics of DIDComm v2 Rust implementation (didcomm-rs), including JWM message format overview, JWE/JWM envelopes and key identifiers structures as well as cryptography usage. In addition we’ve discussed how key resolution of public keys happening from `kid` and `skid` envelope header fields using plugable resolvers and private keys resolver using Vault Key provider in form of “Universal wallet” spec implementation [wallet-rs]. https://iiw.idcommons.net/11D/_DIDComm_V2:_Implementation_and_integration_%27technical%27_-_did:key_and_did:keri_resolvers,_seamless_and_partial_integrations- Session Notes Development 2021-05-07
552 DIDComm Jolocom Ivan Temchenko didcomm-rs implementation What is this talk about?<br><br>• didcomm-rs implementation<br>• Resolver[s] integration<br>• Application level integration (with wallet-rs)<br>• End-to-end consuming application example demo – simple console chat application based on DIDComm v2 and did:key/did:keri (with resolvers)<br>• Floor open for discussions https://drive.google.com/file/d/1dn5f2SqnCeQocOy5quJD9gpMPipKRmdC/view?usp=sharing Presentation Development 2021-04-21
553 DIDComm DIF Rust implementation of DIDComm v2 This is a sample implementation of the DIDComm V2 spec. The DIDComm V2 spec is still actively being developed by the DIDComm WG in the DIF and therefore subject to change. https://github.com/decentralized-identity/didcomm-rs Code Development 2022-10-10
554 DIDComm uPort Oliver Terbu uPort Trusted P2P messaging with DIDs DIDComm and VCs about their path towards trusted P2P messaging and announces the [DIDAgent Framework (DAF)](https://github.com/uport-project/daf)<br>when we speak about a DID, then we need to be more precise and also speak about the particular DID method of that DID which defines the CRUD operations on a target system such as Ethereum. A Decentralized Identifier (DID) is a stable identifier in form of an URI that introduces a level of indirection for key management and managing other useful information such as service endpoints. It… https://medium.com/uport/trusted-p2p-messaging-with-dids-didcomm-and-vcs-398f4c3f3cda https://miro.medium.com/v2/resize:fit:1200/1*bE-GDUWPuUPGyuNPCErJQQ.jpeg Post Development 2020-11-12
555 DIDComm uPort Oliver Terbu DIDComm Messaging through libp2p We outlined the next generation decentralized messaging solution built on top of [DIDComm Messaging](https://identity.foundation/didcomm-messaging/spec/), [DIDs](https://www.w3.org/TR/did-core/) and [VCs](https://www.w3.org/TR/vc-data-model/) and a [libp2p](https://libp2p.io/) overlay network. We presented how Alice and Bob establish a connection, exchange messages and demonstrated what connection types are supported. With InterPlanetary File System (IPFS) the Web3 community has established a critical piece of infrastructure that is used by the majority of web3 protocols to different degrees. Libp2p is part of the… https://medium.com/uport/didcomm-messaging-through-libp2p-cffe0f06a062 https://miro.medium.com/v2/resize:fit:1200/1*cBMXWaM8DEH870d6h57mBg.png Post Development 2021-11-30
556 DIDComm WebofTrustInfo Karim Stekelenburg Animo Solutions Advanced DIDComm Messaging in order for DIDComm to provide a potential replacement for commonly used chat protocols like WhatsApp (Extensible Messaging and Presence Protocol (XMPP)), Telegram (MTProto), or Signal (Signal Protocol), it needs to support modern chat features we use everyday https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/advance-readings/advanced-didcomm-messaging.md Paper 0.1 Development 2022-07-19
557 DIDComm DATEV Tim Vorgs DIDComm & DIDComm Messaging Based on the research project we conducted with SAP, we developed a Proof of Concept (PoC for order-to-cash-business processes. As part of this PoC, we integrated DIDComm based communication to seamlessly transfer data within the boundaries of the process. The overall steps are: https://medium.com/datev-techblog/didcomm-didcomm-messaging-3e10fbf12bb8 https://miro.medium.com/v2/resize:fit:1200/1*prcKX5OvEifMsbSiijDj1A.png Post Development 2022-07-18
558 DIDComm DIF DIF F2FJan21 - DIDComm Demo Session with Ivan Temchenko, Tobias Looker, and Oliver Terbu During the live demo he showed the message lifecycle in various setups using the new, [open source didcomm-rs library](http://github.com/jolocom/didcomm-rs) on GitHub In this informal F2F side-session, Jolocom's Ivan Temchenko gives a detailed tour of their core DIDComm v2 library in Rust, followed by a brief CLI demo from... https://www.youtube.com/watch?v=SaNvIorKQ9I&feature=youtu.be https://i.ytimg.com/vi/SaNvIorKQ9I/maxresdefault.jpg Video Development 2021-01-26
559 DIDComm gold and double blue Siddhi Blockchain and Self-Sovereign Identity Empowered Cyber Threat Information Sharing Platform Blockchain and Self-Sovereign Identity Empowered Cyber Threat Information Sharing Platform<br>- Presented in 7th IEEE International Conference on Smart Computing(IEEE SmartComp 2021) - Siddhi - Blockchain and Self-Sovereign Identity Empowered Cyber Threat Information Sharing Platform- Presented in 7th IEEE International Conference on Smar... https://www.youtube.com/watch?v=lzS49R52PwA https://i.ytimg.com/vi/lzS49R52PwA/maxresdefault.jpg Video Implementation 2021-08-11
560 DIDComm Personal https://didcomm.org/shorten-url/1.0/ Timo Glastra Just got my first DIDComm protocol published on the https://didcomm.org website. A protocol to request a shortened URL for a given URL. For example, an agent requesting a shortened out of band invitation url from a mediator. https://twitter.com/TimoGlastra/status/1572976791136137216 tweet Implementation 2022-08-22
561 DIDComm DIF DIDComm: ECDH-1PU Implementation In short, ECDH-1PU is a key derivation process that allows for sender authenticity and enables a “[Perfect Forward Secrecy](https://www.wired.com/2016/11/what-is-perfect-forward-secrecy/#:~:text=Perfect%20forward%20secrecy%20means%20that,of%20the%20user%27s%20sensitive%20data.)” mechanism, in addition to significant performance gains over JWS message nested in a JWE envelope, as used by existign ECDH-ES aproaches. ECDH-1PU is a key derivation process that offers sender authenticity, as well as significant performance gains over existing ECDH-ES aproaches. https://blog.identity.foundation/ecdh-1pu-implementation/ https://blog.identity.foundation/content/images/2021/09/mathyas-kurmann-fb7yNPbT0l8-unsplash-2.jpg Post Implementation 2021-09-21
562 DIDComm Jolocom Community matters: Jolocom’s latest contributions to DIF We at Jolocom strongly believe that DIDComm is a crucial infrastructure element for the broader and future-proof SSI stack, and [current work on DIDComm v2 includes Jolocom’s implementation of the specification](http://github.com/jolocom/didcomm-rs) with authcrypt (authenticated encrypted) and most of the low level of the protocol. ...Interested parties can already start building high-level verifiable credential-based services and workflows on the Rust KERI implementation. https://jolocom.io/blog/jolocoms-contributions-to-dif/ https://jolocom.io/wp-content/uploads/2020/05/Jolocom-Logbook-DIF-contribution-cover-02-alt.jpg Post Implementation 2021-01-19
563 mDL INATBA “Decentralised Identity: What’s at Stake?” Looking at the above comparison, It is clear that both approaches strive to maintain user control of their personal data, selective disclosure/data minimization, and cryptographic methods to prove the integrity of identity claims. The differences are: first in their reliance (mDL) or independence (SSI) from issuer involvement in verification interactions, and second in their cryptographic approach, where the mDL relies on externally provided cryptographic tools while SSI builds on holder controlled private keys ← earlier paper https://inatba.org/wp-content/uploads/2020/11/2020-11-INATBA-Decentralised-Identity-001.pdf https://inatba.org/wp-content/uploads/2023/05/Background_561821321-scaled-copie.jpg Post Intro 2021-11
564 mDL SpruceID An Identity Wallet Bill of Rights - Starting With the Mobile Driver License Spruce’s continued mission is to let users control their data across the web, whether it’s web2, web3, or beyond. This also applies to credentials issued by existing entities, such as the Mobile Driver License (mDL) issued by motor vehicle authorities across the world. Spruce’s continued mission is to let users control their data across the web, whether it’s web2, web3, or beyond. This also applies to credentials issued by existing entities, such as the Mobile Driver License (mDL) issued by motor vehicle authorities across the world. https://blog.spruceid.com/an-identity-wallet-bill-of-rights/ https://blog.spruceid.com/content/images/2022/09/mDL.png Post Intro 2022-09-12
565 mDL INATBA ​​Mobile Driver’s Licence (mDL) VS. Self-Sovereign Identity (SSI) The ISO mDL specification (ISO-compliant Driving License or IDL)  is purpose driven, as its name implies, but is said to be specifically intended to:<br>* enable verifiers not affiliated with or associated with the issuing authority to gain access to and authenticate the information<br>* allow the holder of the driving license to decide what information to release to a verifier<br>* include the ability to update information frequently, and to authenticate information at a high level of confidence. https://inatba.org/identity/mobile-drivers-licence-mdl-self-sovereign-identity-ssi-comparison/ https://inatba.org/wp-content/uploads/2023/05/Background_561821321-scaled-copie.jpg Post Main 2020-11
566 mDL CCG Mailing List Manu Sporny Spruce, MATTR, Digital Bazaar, CCG Verifiable Driver's Licenses and ISO-18013-5 (mDL) As some of you might be aware, ISO-18013-5 (mDL -- Mobile Driver's License) was published as a global ISO standard in September 2021. A number of us in the W3C CCG and W3C VCWG attempted to ensure that W3C Verifiable Credentials were supported by the mDL work, but that effort is not reflected in the finalized ISO mDL standard (and due to the way ISO operates, we are not at liberty to share any details). There have been increasing concerns related to the divergence of mDL with W3C Verifiable Credentials and to the market dynamics at play around mDL. https://lists.w3.org/Archives/Public/public-credentials/2021Nov/0105.html Discussion Main 2021-11-29
567 mDL Procivis ISO/IEC 18013-5 vs Self-Sovereign Identity: A proposal for an mDL Verifiable Credential in the context of government identity programs we see it as useful to compare them on the following parameters – background, credential data model & trust anchor and transmission protocols. https://www.procivis.ch/post/iso-iec-18013-5-vs-self-sovereign-identity-a-proposal-for-an-mdl-verifiable-credential https://uploads-ssl.webflow.com/5fae427844470c4d4b49d62b/62440e2a85213a51704c8641_Picture%203.png Post Main 2022-03-30
568 mDL AAMVA Mobile Driver's License (mDL) Implementation Guidelines 1.2 The AAMVA Joint Mobile Driver’s License (mDL) Working Group (WG) has been active around mobile identification since 2012. As the mDL evolves, the mDL WG continues to identify and address topics on which guidance to Issuing Authorities can be helpful. This document represents the bulk of the current guidance, and points to additional resources as needed https://www.aamva.org/getmedia/b801da7b-5584-466c-8aeb-f230cef6dda5/mDL-Implementation-Guidelines-Version-1-2_final.pdf Report Main 2023-01
569 mDL AAMVA Mobile Driver's License Model Legislation The Mobile Driver’s License (mDL) Model Legislation has been developed to facilitate the uniformity of proposed legislative changes related to implementation of mDL in various jurisdictions. The model legislation is meant to demonstrate how the requirements in the ISO standards and AAMVA Mobile Driver’s License Implementation Guidelines could be represented in jurisdiction-specific legislation. Thus, the language contained in the model legislation is designed to offer examples and is not expected to be proposed to legislatures without consideration for controlling legal provisions in your jurisdiction https://www.aamva.org/getmedia/cb9fd6c7-29e6-48a4-926b-e16d6400eab5/mDL-Model-Legislation_final.pdf Report Main 2023-01
570 mDL Kantara Initiative Working Group for Privacy Enhancing Mobile Credentials Clearly the use of a driver’s license goes well beyond proving eligibility to drive a vehicle. It has become the de-facto standard for proving that you are who you say you are – and are entitled to the product or service requested. An increasing number of states are adopting mobile ID systems to recognise and verify mobile credentials including driver’s licenses (mDL). https://kantarainitiative.org/introducing-kantaras-working-group-for-privacy-enhancing-mobile-credentials/ https://kantarainitiative.org/wp-content/uploads/2021/11/mitya-ivanov-2HWkORIX3II-unsplash-scaled-1.jpg Post Guidance 2021-11-15
571 mDL Kantara Initiative Kantara Releases Report on Identity and Privacy Protection For mobile Driver’s Licenses The report outlines how to implement mDL systems as Privacy Enhancing Technologies. It provides guidance on protecting people’s individual privacy and the digital identifiers of an individual who carries or uses an mDL. https://kantarainitiative.org/kantara-releases-report-on-identity-and-privacy-protection-for-mobile-drivers-licenses/ https://kantarainitiative.org/wp-content/uploads/2019/08/favicon_kantara.png Post Guidance 2021-08-27
572 mDL Biometric Update https://kantarainitiative.org/kantara-lays-out-trust-building-recommendations-for-mdls/ Kantara lays out trust-building recommendations for mDLs A global digital ID association has published steps vendors and others need to take in order to build effective mobile driving license services that also put ID holders in control of their identity. The Kantara Initiative’s report starts from the premise that trust in mobile driving licenses grows with the degree of control that license holders have over the documents, their privacy and their biometric identifiers. Trust in mobile driving licenses grows with the degree of control that license holders have over the documents, their privacy and their biometric identifiers. https://www.biometricupdate.com/202108/kantara-lays-out-trust-building-recommendations-for-mdls https://d1sr9z1pdl3mb7.cloudfront.net/wp-content/uploads/2020/04/06115457/mDL-mobile-drivers-license.png Post Guidance 2021-08-27
573 mDL CCG Verifiable Driver's License Interoperability Report 1.0 The purpose of this test suite is to demonstrate a path to interoperability between the ISO-18013-5 Mobile Driver's License data model and the W3C Verifiable Credentials ecosystem. The technologies explored in this test suite are experimental and meant to be complementary to ISO-18013-5 (mDL) and not a replacement of the standard. This document contains the most recent interoperability report between issuers and verifiers for Verifiable Driver's License Credentials using the Verifiable Driver's License Vocabulary. This report is generated on a weekly basis. https://w3c-ccg.github.io/vdl-test-suite/ Report Guidance 2023-01-08
mDL INATBA ​​Mobile Driver’s Licence (mDL) VS. Self-Sovereign Identity (SSI) The ISO mDL specification (ISO-compliant Driving License or IDL)  is purpose driven, as its name implies, but is said to be specifically intended to:<br>* enable verifiers not affiliated with or associated with the issuing authority to gain access to and authenticate the information<br>* allow the holder of the driving license to decide what information to release to a verifier<br>* include the ability to update information frequently, and to authenticate information at a high level of confidence. https://inatba.org/identity/mobile-drivers-licence-mdl-self-sovereign-identity-ssi-comparison/ https://inatba.org/wp-content/uploads/2023/05/Background_561821321-scaled-copie.jpg Post 180135 2020-11
mDL CCG Mailing List Manu Sporny Spruce, MATTR, Digital Bazaar, CCG Verifiable Driver's Licenses and ISO-18013-5 (mDL) As some of you might be aware, ISO-18013-5 (mDL -- Mobile Driver's License) was published as a global ISO standard in September 2021. A number of us in the W3C CCG and W3C VCWG attempted to ensure that W3C Verifiable Credentials were supported by the mDL work, but that effort is not reflected in the finalized ISO mDL standard (and due to the way ISO operates, we are not at liberty to share any details). There have been increasing concerns related to the divergence of mDL with W3C Verifiable Credentials and to the market dynamics at play around mDL. https://lists.w3.org/Archives/Public/public-credentials/2021Nov/0105.html Discussion 180135 2021-11-29
mDL Procivis ISO/IEC 18013-5 vs Self-Sovereign Identity: A proposal for an mDL Verifiable Credential in the context of government identity programs we see it as useful to compare them on the following parameters – background, credential data model & trust anchor and transmission protocols. https://www.procivis.ch/post/iso-iec-18013-5-vs-self-sovereign-identity-a-proposal-for-an-mdl-verifiable-credential https://uploads-ssl.webflow.com/5fae427844470c4d4b49d62b/62440e2a85213a51704c8641_Picture%203.png Post 180135 2022-03-30
mDL AAMVA Mobile Driver's License (mDL) Implementation Guidelines 1.2 The AAMVA Joint Mobile Driver’s License (mDL) Working Group (WG) has been active around mobile identification since 2012. As the mDL evolves, the mDL WG continues to identify and address topics on which guidance to Issuing Authorities can be helpful. This document represents the bulk of the current guidance, and points to additional resources as needed https://www.aamva.org/getmedia/b801da7b-5584-466c-8aeb-f230cef6dda5/mDL-Implementation-Guidelines-Version-1-2_final.pdf Report 180135 2023-01
mDL AAMVA Mobile Driver's License Model Legislation The Mobile Driver’s License (mDL) Model Legislation has been developed to facilitate the uniformity of proposed legislative changes related to implementation of mDL in various jurisdictions. The model legislation is meant to demonstrate how the requirements in the ISO standards and AAMVA Mobile Driver’s License Implementation Guidelines could be represented in jurisdiction-specific legislation. Thus, the language contained in the model legislation is designed to offer examples and is not expected to be proposed to legislatures without consideration for controlling legal provisions in your jurisdiction https://www.aamva.org/getmedia/cb9fd6c7-29e6-48a4-926b-e16d6400eab5/mDL-Model-Legislation_final.pdf Report 180135 2023-01
574 mDL IETF RFC 8943 RFC 8943: Concise Binary Object Representation (CBOR) Tags for Date In CBOR, one point of extensibility is the definition of CBOR tags. RFC 7049 defines two tags for time: CBOR tag 0 (date/time string as per RFC 3339) and tag 1 (POSIX "seconds since the epoch"). Since then, additional requirements have become known. This specification defines a CBOR tag for a date text string (as per RFC 3339) for applications needing a textual date representation within the Gregorian calendar without a time. It also defines a CBOR tag for days since the date 1970-01-01 in the Gregorian calendar for applications needing a numeric date representation without a time. This specification is the reference document for IANA registration of the CBOR tags defined. The Concise Binary Object Representation (CBOR), as specified in RFC 7049, is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. https://www.rfc-editor.org/rfc/rfc8943 rfc CBOR 2020-11
575 mDL Personal https://www.rfc-editor.org/rfc/rfc8943 Mike Jones Concise Binary Object Representation (CBOR) Tags for Date is now RFC 8943 The Concise Binary Object Representation (CBOR) Tags for Date specification has now been published as RFC 8943. In particular, the full-date tag requested for use by the ISO Mobile Driver’s License specification in the ISO/IEC JTC 1/SC 17 “Cards and security devices for personal identification” working group has been created by this RFC. The abstract of the RFC is: Mike Jones shares that CBOR (Concise Binary Object Representation) is officially a specification at IETF. woohoo! and it is a key part of [ISO’s mDL standard](https://www.iso.org/committee/45144.html) (date fields must use it). https://self-issued.info/?p=2136 Post CBOR 2020-11-20
576 Competition VentureBeat Emil Protalinski Google Google is bringing Electronic IDs to Android very soon, we will launch another [Jetpack compatibility library](https://venturebeat.com/2019/05/07/google-adds-10-libraries-to-android-jetpack-unveils-kotlin-toolkit-for-ui-development/) that app developers can use immediately to write such apps for various DMVs or whatever cards — in the future, maybe even travel documents, although that kind of standardization for international travel is even further out. Google is bringing Electronic IDs to Android so that your driver's license and your passport are accessible on your phone, even when the battery is dead. https://venturebeat.com/security/google-is-bringing-electronic-ids-to-android/ https://venturebeat.com/wp-content/uploads/2019/05/MzE5MTU4Ng.jpeg?w=1200&strip=all Post Main 2019-05-09
577 Competition Apple Apple Apple announces first states signed up to adopt driver’s licenses and state IDs in Apple Wallet Arizona, Connecticut, Georgia, Iowa, Kentucky, Maryland, Oklahoma, and Utah are among the first states to bring state IDs and driver’s licenses in Wallet to their residents Apple is working with states across the country to roll out the ability for their residents to add their driver’s license or state ID to Wallet. https://www.apple.com/newsroom/2021/09/apple-announces-first-states-to-adopt-drivers-licenses-and-state-ids-in-wallet/ https://www.apple.com/newsroom/images/product/os/ios/standard/apple_wallet-state-id_hero_08232021.jpg.og.jpg?202305231359 Post Main 2021-09-01
578 Competition CNBC https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0231.html Hugh Son,Kif Leswing Apple launches the first driver’s license and state ID in Wallet with Arizona” It’s sad and frustrating that this isn’t based on verifiable credentials… it appears vendor lock in is going to be hard to prevent.<br><br>For anyone who missed the November coverage about this, here’s a pretty outrageous CNBC article: Apple is sticking taxpayers with part of the bill for rollout of tech giant's digital ID card - Apple requires states to maintain the systems needed to issue and service credentials at taxpayer expense, according to contracts signed by four states.<br>- The agreement, obtained through public record requests from CNBC and other sources, mostly portrays Apple as having a high degree of control over the government agencies responsible for issuing identification cards.<br>- Apple has “sole discretion” for key aspects of the program. Contracts between Apple and states including Georgia, Arizona, Kentucky and Oklahoma provide a rare glimpse into the dealings of the powerful company. https://www.cnbc.com/2021/11/14/apple-sticking-taxpayers-with-part-of-the-bill-for-digital-id-rollout.html https://image.cnbcfm.com/api/v1/image/106893252-1623087055894Screen-Shot-2021-06-07-at-1-27-30-PM-png?v=1623087200&w=1920&h=1080 Post Main 2021-11-14
579 Competition CCG Mailing List https://www.ietf.org/archive/id/draft-secure-credential-transfer-03.html Manu Sporny CCG Re: IETF: Secure Credential Transfer Seems like a point solution -- digital dead drop box for bearer credentials that are encrypted to specific individuals. Very little overlap w/ VCs and the protocols we're discussing here (but, would be good to keep our eye on this one). https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0030.html Discussion Main 2022-04-05
580 Exchange Protocols IDCommons https://docs.google.com/document/d/1_b5MxzUPWzYxXxWt7Tw6-MySqh77ZvYHBnUgEBCFH7Q/edit Kaliya Young, Orie Steele, Drummond, Kyle, et al. Figuring out Verifiable Credentials Exchange - combining Bloom, Aires Protocols, Presentation Exchange into a unified - Killer Whale Jello Salad - Because what we need is interoperable - issuance - issue-holder || holder -verifier some conversation about SIOP - has not been the focus of the discussion.<br - Goal to create a bridge between<br - the W3C CCG / DHS SVIP - VCI-HTTP-API (VHA) in combination with CHAPI protocol and the (VC Request) for issuing credentials.<br - Aries protocols run on top of DIDComm<br - If we agree on a credential format we can exchange across those universes - JSON-LD ZKP BBS+ then we need a protocol to do it - can go between. - Because what we need is interoperable - issuance - issue-holder || holder -verifier some conversation about SIOP - has not been the focus of the discussion.<br> - Goal to create a bridge between<br> - the W3C CCG / DHS SVIP - VCI-HTTP-API (VHA) in combination with CHAPI protocol and the (VC Request) for issuing credentials.<br> - Aries protocols run on top of DIDComm<br> - If we agree on a credential format we can exchange across those universes - JSON-LD ZKP BBS+ then we need a protocol to do it - can go between. https://iiw.idcommons.net/22H/_Figuring_out_Verifiable_Credentials_Exchange_-_combining_Bloom,_Aires_Protocols,_Presentation_Exchange_into_a_unified_-_Killer_Whale_Jello_Salad Session Notes Background 2021-05-06
581 Exchange Protocols IDCommons https://iiw.animo.id BBS+ Credential Exchange in Hyperledger Aries 19:18:25 From Sebastian Schmittner : Is there some working implementation out there to actually generate/work with these VCs shown currently?<br>19:18:58 From Troy Ronda : aries-framework-go is one of them.<br>19:19:24 From Karim Stekelenburg : The ACA-Py implementation will be merged in shortly<br>19:20:50 From Stephen Curran : PR: https://github.com/hyperledger/aries-cloudagent-python/pull/1061<br>19:22:02 From Sebastian Schmittner : awesome! We are doing some prototyping right now where we are using JSON-LD VCs with the americans, but, since we are also running a node in the HL Indy network of ID Union, it would be really great if we could bridge the Ocean here ;) https://iiw.idcommons.net/11E/_BBS+_Credential_Exchange_in_Hyperledger_Aries Session Notes Background 2021-05-06
582 Exchange Protocols IDCommons Credentials Exchange - figuring it out - (Jello Bowl Death Match?) The ultimate goal is to get to a clear exchange protocols.<br><br>Also to have a paper similar to [this one](https://www.lfph.io/wp-content/uploads/2021/02/Verifiable-Credentials-Flavors-Explained.pdf) that outlines the choice landscape that is and points to a convergence point<br><br>Good Health Pass is literally right now trying to figure this out and will “pick” solutions it needs to get implementations working in the next 30-90 days and point the whole industry in one direction.<br><br>We started out with this framework of understanding<br><br>Contextualizing VC Exchange in Layers<br><br>Verifiable Credentials (VC or VCs) is one of the key standardized components of decentralized identity. [The VCs Data Model](https://www.w3.org/TR/vc-data-model/), defined at the W3C, is a universal data format that lets any entity express anything about another entity.  It provides a common mechanism for the interoperable implementation of digital credentials that are cryptographically secure, tamper-evident, privacy-respecting, and machine-verifiable.<br><br>There clarity emerging on standards that are interoperable with one another for the VC format.<br><br>There is less clarity on the Exchange mechanisms.<br><br>One way that has been proposed to look at the exchange options available is to see them in different layers. https://iiw.idcommons.net/12F/_Credentials_Exchange_-_figuring_it_out_-_(Jello_Bowl_Death_Match%3F)_%E2%80%93 Session Notes Background DIDComm, Verifiable Credential Exchange, Aries Protocol, Bloom Protocol, Presentation Exchange 2021-05-06
583 Exchange Protocols CCG Manu Sporny chapi.io launches, includes VC playground TL;DR: chapi.io is a site that helps developers integrate Verifiable Credential issuance, holding, and presentation into their applications. It includes a playground that can issue arbitrary VCs to digital wallets (web and native). It also includes tutorials on how Web Developers can add CHAPI integration to their websites. All you need to try it out is a web browser. https://lists.w3.org/Archives/Public/public-credentials/2022Jun/0055.html Discussion CHAPI 2022-06-27
635 OpenID Connect IDCommons David Waite IIW OpenID Connect: Session Management vs Privacy To recap:<br>* Front-channel logout is simple<br>* …but brittle and doesn’t give good security guarantees<br>* Back-channel logout is robust<br>* …but difficult to implement/support, can still miss signals<br>* Session Management is useful for some apps<br>* …but is broken in many browsers<br>On their own independent schedules, all browsers have either broken or have plans to break state sharing via cross-site iframes to limit user tracking - arguably making the Session Management approach unusable. https://iiw.idcommons.net/11M/_OpenID_Connect:_Session_Management_vs_Privacy Session Notes Development 2021-05-06
636 OpenID Connect Auth0 Identity, Unlocked... SIOP with Kristina Yasuda As a discovery mechanism to invoke a Self-Issued OP, the discussion on the podcast covered the usage of a custom schema 'openid://'. Alternative mechanisms to address the limitations of custom schemas are being actively explored in the WG.<br><br>The conversation meanders through deeper details, from how the current [SIOP specification draft](https://bitbucket.org/openid/connect/src/master/openid-connect-self-issued-v2-1_0.md) under the OpenID Foundation picks up the mission from a [former attempt under DIF](https://identity.foundation/did-siop/) to encoding approaches for verifiable presentations (embedding in JWTs, [LD proofs](https://w3c-ccg.github.io/ld-proofs/), how to represent attributes https://auth0.com/blog/identity-unlocked-explained-season-2-ep-5/ https://images.ctfassets.net/23aumh6u8s0i/3v8k53STScYaDqv0oL1Fyd/373fa786764a8e6684d6c677a4e4bb88/identity-unlocked-hero.png episode Development 2021-03-22
637 OpenID Connect SpruceID https://blog.spruceid.com/sign-in-with-ethereum-decentralizing-an-identity-provider-server/ Spruce Developer Update #20 We've set up a [release pipeline](https://github.com/spruceid/ens-oidc/) and had our first witnessed deployment for the ENS Community-Maintained OIDC IdP https://blog.spruceid.com/spruce-developer-update-20/ Post Development 2022-06-01
638 OpenID Connect IETF Sam Goto Browser APIs to enable OpenID Session Management and Privacy How does logout in OIDC happen?<br>* Classification problem - browsers do not know it is a logout now<br>* Easiest way<br * Browser asks for a user consent<br * Hard from a permission implementation perspective<br * Tim: No issues with this idea<br * If user logged into several OPs, user will not look to all the ones they log out from<br>* Option2<br * Browser classifies signing-in event<br * On log out does not prompt the user and IdP has no incentives to lie<br * RPs get to determine if they want to log the user out or not<br * Whether you can swap generic frame with fenced frame, frame can see it’s own cookies<br * May not be able to pass any parameters that you need to pass; no link decoration for framed frame<br * Subdomains also considered, but not well thought out<br * Logout URL - other option to add, but more work for RP: Resource metadata. Specification - not much adoption. It just feels like a place where RP metadata could be declared which could be useful in this context of the RP defining its metadata (e.g. what IDP it uses) How does logout in OIDC happen?<br>* Classification problem - browsers do not know it is a logout now<br>* Easiest way<br> * Browser asks for a user consent<br> * Hard from a permission implementation perspective<br> * Tim: No issues with this idea<br> * If user logged into several OPs, user will not look to all the ones they log out from<br>* Option2<br> * Browser classifies signing-in event<br> * On log out does not prompt the user and IdP has no incentives to lie<br> * RPs get to determine if they want to log the user out or not<br> * Whether you can swap generic frame with fenced frame, frame can see it’s own cookies<br> * May not be able to pass any parameters that you need to pass; no link decoration for framed frame<br> * Subdomains also considered, but not well thought out<br> * Logout URL - other option to add, but more work for RP: Resource metadata. Specification - not much adoption. It just feels like a place where RP metadata could be declared which could be useful in this context of the RP defining its metadata (e.g. what IDP it uses) https://iiw.idcommons.net/13L/_Browser_APIs_to_enable_OpenID_Session_Management_and_Privacy Session Notes Development 2021-05-06
639 KERI Blockchain Bird https://iiw.idcommons.net/3K/_KERI_Q%26A_basic_introduction IIW32 KERI Q&A basic introduction It has lots of relevant links in it to start your journey in KERI.<br><br>What is KERI?<br>* Key Event Receipt Infrastructure<br>* Intends to repair the Internet<br>* KERI = CT with decentralized CA<br>* NOT a coin, token…<br><br>Why KERI? (and not something else)<br>* Strong autonomous identifiers<br>* Abiding to privacy (laws and good habits)<br>* Portability, delegation, rotatable keys<br>* Direct & Indirect method<br>* <there’s more> https://blockchainbird.org/downloads/KERI-QA-introduction.pdf Presentation Main 2021
640 KERI DIF KERI: For every DID, a microledger The world of digital identifiers (DIDs) and verifiable credentials (VCs) is evolving quickly, giving much cause for optimism. Standards are starting to connect and move towards functional interoperability, governed by testable protocols. Most of this work is happening on the level of VCs. However, DIDs and their infrastructure are also starting to converge and mature as an extensible-yet-interoperable technology. https://medium.com/decentralized-identity/keri-for-every-did-a-microledger-f9457fa80d2d https://miro.medium.com/v2/resize:fit:1000/0*ZdrUkaJCemaCIBAw Post Main 2020-10-19
641 KERI personal Samuel Smith Key Event Receipt Infrastructure: A Secure Identifier Overlay for the Internet Secure attribution of any communication to its source<br>Authentic communication<br>Authentic interactions based an secure attribution of all statements by participants<br>Verifiable authenticity of data<br>Data Provenance<br>Authentic data economy https://github.com/SmithSamuelM/Papers/blob/master/presentations/KERI_Overview.web.pdf Presentation 2.60 Main 2021-03-23

View File

@ -1,46 +1,21 @@
---
date: 2020-11-26
title: DID Communications WG - DIF
title: DID Communications - DIF
name: DIDComm
layout: standards
headings: ["Explainer","RFCs","Development","Implementation"]
description: contribute to specs that embody a method for secure, private and authenticated message-based communication, where trust is rooted in DIDs and used over a wide variety of transports.
excerpt: >
Produce one or more high-quality specs that embody a method (“DIDComm”) for secure, private and (where applicable) authenticated message-based communication, where trust is rooted in DIDs and depends on the messages themselves, not on the external properties of the transport(s) used. The method must be usable over many means of transport, including those that are asynchronous and simplex, and ones that do not necessarily use the internet. It must support routing and relay through untrusted intermediaries, not just point-to-point delivery. In addition to the communication and protocols described above, the protocols for exchanging DIDs/keys to bootstrap such communication are within scope. These protocols can be the foundation of higher-level protocols such as credential exchange and higher-level authentication protocols.
permalink: organizations/decentralized-identity-foundation/wg/did-comm/
canonical_url: https://decentralized-id.com/organizations/decentralized-identity-foundation/wg/did-comm/
permalink: organizations/decentralized-identity-foundation/did-communications/
canonical_url: https://decentralized-id.com/organizations/decentralized-identity-foundation/did-communications/
redirect_from:
- organizations/decentralized-identity-foundation/wg/did-comm/
categories: ["Web Standards"]
tags: ["DIDComm WG","DIDComm","DIF","Aries","DID","W3C"]
header:
image: /images/DIDComm-header.webp
teaser: /images/DIDComm-teaser.webp
last_modified_at: 2020-11-26
last_modified_at: 2023-06-03
---
[Webpage](https://identity.foundation/working-groups/did-comm.html) - [GitHub](https://github.com/decentralized-identity/didcomm-messaging/)
> Join this group to contribute to specs that embody a method for secure, private and authenticated message-based communication, where trust is rooted in DIDs and used over a wide variety of transports.
* [Mailing list](https://dif.groups.io/g/didcomm-wg) - The more foundational communication protocols have been known by several names during their history, including Agent to Agent Communication and more recently DID Communications (DIDComm for short). On top of this foundation are other protocols, including credential exchange, basic user messaging, etc
* [DIDcomm WG Charter](https://github.com/decentralized-identity/org/blob/master/Org%20documents/WG%20documents/DIF_DIDcomm_WG_Charter_v1.pdf)
> Produce one or more high-quality specs that embody a method (“DIDComm”) for secure, private and (where applicable) authenticated message-based communication, where trust is rooted in DIDs and depends on the messages themselves, not on the external properties of the transport(s) used. The method must be usable over many means of transport, including those that are asynchronous and simplex, and ones that do not necessarily use the internet. It must support routing and relay through untrusted intermediaries, not just point-to-point delivery. In addition to the communication and protocols described above, the protocols for exchanging DIDs/keys to bootstrap such communication are within scope. These protocols can be the foundation of higher-level protocols such as credential exchange and higher-level authentication protocols.
* [DIDcomm WG Operating Addendum](https://github.com/decentralized-identity/org/blob/master/Org%20documents/WG%20documents/DIF_DIDcomm_WG_Operating_Addendum_v1.pdf)
> We are designing communications protocols specifically for use with the decentralized identifier specification at W3C (https://www.w3.org/TR/did-core/). The DID Core specification and the surrounding family of DID specifications (e.g https://w3c-ccg.github.io/did-resolution/) represent the format for entity identification in our DIDComm efforts.
* [DIF starts DIDComm Working Group](https://medium.com/decentralized-identity/dif-starts-didcomm-working-group-9c114d9308dc)
> Over the past few months, the DIF and Hyperledger Aries community have come together and agreed to work on a common work item aimed at developing secure communication based on Decentralized Identifiers (DIDs) — hence the name DIDComm, which is short for DID Communication. Significant prior work in developing a messaging-based communication protocol using DIDs has been incubating in the HyperLedger (HL) Aries community, with the progress of this effort evident in the resulting [Aries RFCs](https://github.com/hyperledger/aries-rfcs). To address the requirements of a broader and more heterogeneous community we selected DIF as the place to pursue the next phase of work associated with this effort. Presenting the progress of DIDcomm to other relevant working groups will drive the interoperability between the various decentralized identity vendors and hence enabling a range of decentralized identity-related use cases.
## Specs & Projects
* [decentralized-identity/DIDComm-js](https://github.com/decentralized-identity/DIDComm-js)
> DIDComm JS LibA shared effort with the HL Aries project to create a standardized means of authenticated general message passing between DID controllers. More information will be added soon.
### DIDComm Messaging
* [decentralized-identity/didcomm-messaging](https://github.com/decentralized-identity/didcomm-messaging)
> DIDComm Messaging is a powerful way for people, institutions, and IoT things to interact via machine-readable messages, using features of decentralized identifiers (DIDs) as the basis of security and privacy. It works over any transport: HTTP, BlueTooth, SMTP, raw sockets, and sneakernet, for example.
>
> This repo is where we develops specs and reference code to explain DIDComm Messaging. Some of the work incubated here is likely to be standardized at IETF or in other places.
* [Spec](https://identity.foundation/didcomm-messaging/spec/) - [Markdown](https://github.com/decentralized-identity/didcomm-messaging/blob/master/spec.md)
> DIDComm enables higher-order protocols that inherit its security, privacy, decentralization, and transport independence. Examples include exchanging verifiable credentials, creating and maintaining relationships, buying and selling, scheduling events, negotiating contracts, voting, presenting tickets for travel, applying to employers or schools or banks, arranging healthcare, and playing games. Like web services atop HTTP, the possibilities are endless; unlike web services atop HTTP, many parties can participate without being clients of a central server, and they can use a mixture of connectivity models and technologies.
* [Implementers Guide](https://identity.foundation/didcomm-messaging/guide/) - This guide contains concepts, explanations, and important considerations for those building DIDComm capable systems.
> Routing is the process of managing the delivery of messages from sender to recipient, possibly adapting the packaging and transfer to intermediate nodes. A route is a map or plan that specifies enough to achieve delivery in at least one direction; it may omit uninteresting details.
>
> A sender emits a message hoping that a recipient eventually receives it. As a message moves toward the recipient, we say it is moving destward; the opposite direction is sourceward. Note that sender and recipient flip if a request-like message is followed by a response-like message in the opposite direction; the context that defines a sender is a single message, not a paired interaction. (DIDComm supports request-response but does not require it.)