Merge 9d7015cd8a into 93018b8cd1

Bumps [activesupport](https://github.com/rails/rails) from 7.0.7 to 7.0.7.2.
- [Release notes](https://github.com/rails/rails/releases)
- [Changelog](https://github.com/rails/rails/blob/v7.0.7.2/activesupport/CHANGELOG.md)
- [Commits](https://github.com/rails/rails/compare/v7.0.7...v7.0.7.2)

---
updated-dependencies:
- dependency-name: activesupport
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Gemfile.lock

@@ -1,7 +1,7 @@
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (7.0.7)
+    activesupport (7.0.7.2)
       concurrent-ruby (~> 1.0, >= 1.0.2)
       i18n (>= 1.6, < 2)
       minitest (>= 5.1)

_data/catz.yml

@@ -0,0 +1,4 @@
+Meta: ["About","History","Events"]
+Standards and Development: ["Verifiable Credentials and Decentralized Identifiers","Related Standards","Open Source Projects","Technology","Standards Development Orgs"]
+Organizations: ["Companies","Community Orgs","Standards Development Orgs"]
+Application: ["Government","Uses","Decentralized Web","Web 3"]

_data/standards.csv

@@ -48,11 +48,6 @@ Verifiable Credentials,CCG Mailing List,,,Michael Herman,,,,,,What are VCs simil
 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, Object Capabilities",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, Main",,,,,,Object Capabilities,,2021-09-25,,,,,,,,,,,,,
 "Verifiable Credentials, Object Capabilities",CCG Mailing List,,,Dave Longley,,,,,,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, Main",,,,,,Object Capabilities,Credentials Community Group,2020-12-05,,,,,,,,,,,,,
-Verifiable Credentials,LPFH,,,Kaliya IdentityWoman,,,,,,Verifiable Credentials Flavors Explained,"Below are the three primary flavors of VCs discussed in this paper. All have more than one critical implementation in various stages of production. There are advocated variations of these types, but they are less common.<br>* JSON-LD family with LD Signatures or with BBS+ Signatures that enable Zero Knowledge Proofs (ZKP or ZKPs)<br>* JSON with JSON Web Signatures, precisely in the form of a JSON Web Token (JWT)<br>* ZKP with Camenisch-Lysyanskaya Signatures (ZKP-CL)",,https://www.lfph.io/wp-content/uploads/2021/02/Verifiable-Credentials-Flavors-Explained.pdf,,Post,,,Varieties,,,,,,,,2021-02,,,,,,,,,,,,,
-"Standards, Verifiable Credentials",LFPH,,https://www.lfph.io/wp-content/uploads/2021/02/Verifiable-Credentials-Flavors-Explained.pdf,Lucy Yang,,,,,,The Flavors of Verifiable Credentials,The differences between the different flavors of VCs for technically inclined readers. It elaborated on the differences between JSON and JSON-LD and articulated differences between the two different implementations of ZKP style credentials. The ‘Journey of a VC’ section articulated all steps where VCs are active and highlighted the differences in how different VC flavors ’behave’.,,https://www.lfph.io/2021/02/11/cci-verifiable-credentials-flavors-and-interoperability-paper/,,Paper,,,"Varieties, Decentralized Identity Stack",,,,,,,,2021-11-11,,,,,,,,,,,,,
-Verifiable Credentials,Evernym,,,Daniel Hardman,,,,,,Categorizing Verifiable Credentials - Evernym,Not all verifiable credentials are created the same. This post examines the categories of credentials and the architectural choices driving this variation.,Not all verifiable credentials are created the same. This post examines the categories of credentials and the architectural choices driving this variation.,https://www.evernym.com/blog/categorizing-verifiable-credentials/,,Post,,,Varieties,,,,,,,,2019-11-07,,,,,,,,,,,,,
-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,,,,,,,,,,,,,
-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,DSpace@MIT,,,,,,,,,SolidVC : a decentralized framework for Verifiable Credentials on the web,"SolidVC is a decentralized Verifiable Credentials platform built with the open protocols of the Web. It is implemented on top of Solid, a Web framework developed at MIT in 2016 that allows decentralized applications to interact with personal user data to provide services in an access controlled environment.",,https://dspace.mit.edu/handle/1721.1/121667,https://dspace.mit.edu/bitstream/handle/1721.1/121667/1102055877-MIT.pdf.jpg?sequence=4&isAllowed=y,paper,,,Implementations,,,,,,,,2019,,,,,,,,,,,,,
 Verifiable Credentials,Paris P2P,,,,,,,,Paris P2P Festival,Blockstack and Verifiable Credentials - Paris P2P Festival,• Keep auth and smart contracts on-chain<br> • Keep encrypted data off-chain<br>  > • Wrap everything in an easy JavaScript API,,https://p2p.paris/gen/attADzQJ92rNIv6B3-Blockstack_and_Verifiable_Credentials_-_Paris_P2P_Festival_.pdf,,presentation,,,Implementations,,,,,,,,2020-01-10,,,,,,,,,,,,,
 Verifiable Credentials,LibP2P,,,,,,,,,Verifiable credentials and libp2p,Hi - we’re looking into libp2p as a network stack for our application and exploring how we could integrate verifiable credentials (https://w3c.github.io/vc-data-model/ 2) infrastructure. A basic use case is that of a node being challenged to provide some specific credential to join the network. The bootstrap node handling the incoming connection should verify the credential with the issuer and complete the connection/bootstrap or terminate it.,,https://discuss.libp2p.io/t/verifiable-credentials-and-libp2p/206,https://global.discourse-cdn.com/standard17/uploads/libp2p/original/1X/aacb49457c3aace79a1038dd02996b402260215d.png,discussion,,,Implementations,,,,,,,,2019-07-09,,,,,,,,,,,,,
@@ -125,6 +120,10 @@ VCs Development,CCG Mailing List,,,Bob Wyman,,,,,,Any Good use case of PAM (Priv
 VCs Development,Mattr,,,,,,,,,Paper based Verifiable Credentials,Paper-based Verifiable Credentials allow us to have a low-tech solution for adopting VC's in situations where access to a phone cannot be guaranteed. This presentation looks at how this solution can be used to aid with the distribution of Vaccine Credentials.,Paper-based verifiable credentials allow us to have a low-tech solution for adopting verifiable credential's in situations where access to a phone cannot be ...,https://www.youtube.com/watch?v=EXvWxFjHvdY,,Video,,,Development,,,,,,,,2021-03-02,,,,,,,,,,,,,
 VCs Development,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,,,,,,,,,,,,,
 VCs Development,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,,,,,,,,,,,,,
+"Standards, VCs Development",LPFH,,https://www.lfph.io/2021/02/11/cci-verifiable-credentials-flavors-and-interoperability-paper/,"Kaliya IdentityWoman, Lucy Yang",,,,,,Verifiable Credentials Flavors Explained,"Below are the three primary flavors of VCs discussed in this paper. All have more than one critical implementation in various stages of production. There are advocated variations of these types, but they are less common.<br>* JSON-LD family with LD Signatures or with BBS+ Signatures that enable Zero Knowledge Proofs (ZKP or ZKPs)<br>* JSON with JSON Web Signatures, precisely in the form of a JSON Web Token (JWT)<br>* ZKP with Camenisch-Lysyanskaya Signatures (ZKP-CL)",The differences between the different flavors of VCs for technically inclined readers. It elaborated on the differences between JSON and JSON-LD and articulated differences between the two different implementations of ZKP style credentials. The ‘Journey of a VC’ section articulated all steps where VCs are active and highlighted the differences in how different VC flavors ’behave’.,https://www.lfph.io/wp-content/uploads/2021/02/Verifiable-Credentials-Flavors-Explained.pdf,,Paper,,,"Varieties, Decentralized Identity Stack",,,,,,,,2021-02-11,,,,,,,,,,,,,
+VCs Development,Evernym,,,Daniel Hardman,,,,,,Categorizing Verifiable Credentials - Evernym,Not all verifiable credentials are created the same. This post examines the categories of credentials and the architectural choices driving this variation.,Not all verifiable credentials are created the same. This post examines the categories of credentials and the architectural choices driving this variation.,https://www.evernym.com/blog/categorizing-verifiable-credentials/,,Post,,,Varieties,,,,,,,,2019-11-07,,,,,,,,,,,,,
+VCs Development,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,,,,,,,,,,,,,
+VCs Development,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,,,,,,,,,,,,,
 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,,,,,,,,,,,,,
@@ -481,9 +480,8 @@ Linked Data,WebofTrustInfo,,,"Manu Sporny, Harlan Wood, Noah Thorp, Wayne Vaughn
 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, Object Capabilities",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, Literature",,,,,,,Credentials Community Group,2023-01-22,https://github.com/w3c-ccg/zcap-spec,,,,,,,,,,,,
+"Linked Data, Object Capabilities",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.<br><br>[...] Relationship to Verifiable Credentials [...]<br><br>We seem to be in a conundrum. Claims and credentials are forms of correlation that allow us to reason about an entity in our squishy human world, but are unsafe when used as mechanisms to authorize some event to occur within a system. Capabilities are a safe mechanism to model the flow of authority through a system, but there are times when capabilities have not been granted and we need to make a ""judgement call"" by correlating information about that entity. What should we do?<br><br>To pose the question is to see the answer: the right approach is to use each system for what it does best. Use correlation (Verifiable Credentials) in a reasoning system (most commonly human reasoning) as a path to make judgements about whether to hand an entity a specific set of initial capabilities. Use capabilities (ZCAP-LD) as the mechanism to grant and exercise authority through computing systems. To return to our system administrator example, when Alice applies for the job, she submits a series of credentials about her prior work history and degree, and Eva is able to verify that it is Alice's former employers and university which have made these claims. Deciding that Alice is fit for the job, Eva hands Alice her initial capability which grants her authority to administrate the systems in question (with a caveat that allows Eva to revoke that authority at a future date, if appropriate). Alice uses that capability as the initial entry point into administrating the system. ",,https://w3c-ccg.github.io/zcap-spec/,,Specification,,,"Main, Literature",,,,,,,Credentials Community Group,2023-01-22,https://github.com/w3c-ccg/zcap-spec,,,,,,,,,,,,
 Linked Data,WebofTrustInfo,,,,,,,,,Java implementation of Linked Data Signatures,This is an implementation of the following cryptographic suites for Linked Data Proofs:<br>Ed25519Signature2018<br>Ed25519Signature2020<br>EcdsaSecp256k1Signature2019<br>RsaSignature2018<br>JsonWebSignature2020<br>JcsEd25519Signature2020<br>JcsEcdsaSecp256k1Signature2019,,https://github.com/WebOfTrustInfo/ld-signatures-java,,Code,,,Implementation,,,,,,,,2023-05-13,,,,,,,,,,,,,
-Linked Data,WebofTrustInfo,,,,,,,,,JSON-LD Signatures with JSON Web Signatures,"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://github.com/WebOfTrustInfo/ld-signatures-python,,Code,,,Implementation,,,,,,Object Capabilities,,2017-04-25,,,,,,,,,,,,,
 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,,,,,,,,,,,,,

_drafts/2020-11-10-blockstack.md

@@ -0,0 +1,61 @@
+---
+title: "Stacks: A Bitcoin Layer for Smart Contracts"
+description: Stacks is a blockchain anchored by Bitcoin that enables apps, smart contracts, and digital assets.
+excerpt: >
+  the Stacks Bitcoin layer unlocks smart contracts and decentralized applications that use Bitcoin as their asset and perform the final settlement of transactions on the Bitcoin blockchain. Stacks allows BTC to be a productive asset without compromising its security and durability and enabling a wide range of applications like decentralized Bitcoin lending and Bitcoin-backed stablecoins.
+layout: single
+header:
+  image: /images/blockstack_header.webp
+  teaser: /images/blockstack_teaser.webp
+categories: ["Web 3"]
+tags: ["Blockstack","Bitcoin","Blockchain","DPKI"]
+permalink: blockchain/blockstack/
+toc: true
+last_modified_at: 2023-06-10
+---
+
+## Main
+
+[Website](https://www.stacks.co/) • [Foundation](https://www.stacks.org) • [GitHub](https://github.com/blockstack) • [Forum](https://forum.stacks.org/) • [Docs](https://docs.stacks.co/) • [Blog](https://www.stacks.co/blog) • [Twitter](https://twitter.com/Stacks) • [Apps](https://stacks.co) • [Discord](https://discord.gg/5DJaBrf)
+
+* [Stacks: A Bitcoin Layer for Smart Contracts](https://gaia.blockstack.org/hub/1AxyPunHHAHiEffXWESKfbvmBpGQv138Fp/stacks.pdf)
+  > With its Nakamoto release, the Stacks Bitcoin layer unlocks smart contracts and decentralized applications that use Bitcoin as their asset and perform the final settlement of transactions on the Bitcoin blockchain. Stacks allows BTC to be a productive asset without compromising its security and durability and enabling a wide range of applications like decentralized Bitcoin lending and Bitcoin-backed stablecoins. These applications through the Stacks layer allow people to use Bitcoin as money and the Bitcoin blockchain as the settlement of identity or application data, reducing the need for users to explore alternate, less secure L1 blockchains and crypto assets than BTC
+* [Awesome Blockstack](https://github.com/friedger/awesome-stacks-chain) 2023-05-18
+  > Stacks is a blockchain anchored by Bitcoin that enables apps, smart contracts, and digital assets. Stacks is a layer-1 blockchain that connects to Bitcoin and implements smart contracts and decentralized applications through the Clarity language. Through the Proof of Transfer (PoX) consensus mechanism, the state of the Stacks blockchain is anchored against the Bitcoin blockchain, thus providing the security and finality of Bitcoin to Stacks. Stacks brings the programmability of other blockchain technologies to Bitcoin, without the need to modify the core consensus mechanism of Bitcoin itself.
+* [Launch HN: Stacks (YC S14) – The first SEC-qualified crypto token offering](https://news.ycombinator.com/item?id=20413420) 2019-07-11 news.ycombinator
+  > Our regulatory approach is also very different from typical “ICOs” you may have seen. For distributing Stacks to the general public, we decided to work with US regulators. We wanted to open up the US market to our offering instead of blocking US investors. Yesterday, we received qualification from the SEC. The SEC has never qualified any token offering until now.
+* [BitcoinWiki](http://en.bitcoinwiki.org/wiki/BlockStack)] 2019-02-22
+  > BlockStack is a new network for decentralized applications[1]. Blockstack aims to address the centralization at the application-layer of the internet. More specifically, Blockstack builds an alternate DNS and alternate public-key infrastructure. It's the first implementation of a decentralized DNS system on top of the Bitcoin blockchain It combines DNS functionality with public key infrastructure and is primarily meant to be used by new blockchain applications.
+
+## Decentralized ID
+
+* [GreenPass Integrates Blockstack: Fighting Coronavirus While Protecting Your Privacy](https://blog.blockstack.org/greenpass-integrates-blockstack) 2020-08-18 Jenny Mith
+  > GreenPass is a mobile app that aims to mitigate the impact of COVID-19 by helping users track and manage health data in a secure and private way. By utilizing decentralized identity (DID), verifiable credentials (VC), and distributed storage, GreenPass is able to preserve user privacy, which is critical given the sensitivity of the health related data being shared.
+* [Presentation] [Blockstack and Verifiable Credentials](https://p2p.paris/gen/attADzQJ92rNIv6B3-Blockstack_and_Verifiable_Credentials_-_Paris_P2P_Festival_.pdf) 2020-01-10 Paris P2P Festival
+  > • Keep auth and smart contracts on-chain
+  > • Keep encrypted data off-chain
+  > • Wrap everything in an easy JavaScript API
+* [Blockstack DID Method Specification](https://github.com/blockstack/stacks-blockchain/blob/stacks-1.0/docs/blockstack-did-spec.md) 2019-07-19 Blockstack
+  > Blockstack is a network for decentralized applications where users own their identities and data. Blockstack utilizes a public blockchain to implement a decentralized naming layer, which binds a user's human-readable username to their current public key and a pointer to their data storage buckets. The naming layer ensures that names are globally unique, that names can be arbitrary human-meaningful strings, and that names are owned and controlled by cryptographic key pairs such that only the owner of the private key can update the name's associated state.
+
+## Web3 ID
+
+* [Documentation] [Authentication](https://docs.blockstack.org/authentication/overview) - Blockstack Auth provides single sign on and authentication without third parties or remote servers.
+  > A decentralized application and the Blockstack App communicate during the authentication flow by passing back and forth two tokens. The requesting application sends the Blockstack App an authRequest token. Once a user approves a sign-in, the Blockstack App responds to the application with an authResponse token. These tokens are JSON Web Tokens, and they are passed via URL query strings.
+* [Documentation] [Blockchain naming system (BNS)](https://docs.blockstack.org/technology/naming-system)
+  > BNS is a network system that binds names to off-chain state without relying on any central points of control. The Stacks V1 blockchain implemented BNS through first-order name operations. In Stacks V2, BNS is instead implemented through a smart-contract loaded during the genesis block.Names in BNS have three properties:
+  > - Names are globally unique. The protocol does not allow name collisions, and all well-behaved nodes resolve a given name to the same state.
+  > - Names are human-meaningful. Each name is chosen by its creator.
+  > - Names are strongly-owned. Only the name's owner can change the state it resolves to. Specifically, a name is owned by one or more ECDSA private keys.
+* [Blockstack Auth] [Bringing decentralized identity to traditional apps](https://larrysalibra.com/adding-blockstack-auth-to-discourse/) 2018-09-14
+  > We really liked the Discourse forum software and wanted to give users the option to sign in with their Blockstack IDs.
+  >
+  > Enabling Blockstack Authentication on a centralized app potentially enables a range of functionality:
+  > - single sign on - users with a Blockstack ID don't have to register again or sign up for your app
+  > - an instant profile system - users can bring their existing profile to your app
+  > - client-side encryption - you can encrypt user data on your users' client devices before sending it to your server. This is great for user privacy and may offer legal and security advantages for your business. Both hackers and law enforcement aren't able to access user data that has been encrypted with keys generated from a Blockstack ID. Hopefully this means they leave you alone!
+* [Archived] [Blockstack: Design and Implementation of a Global Naming System with Blockchains](http://web.archive.org/web/20160909124003/https://blockstack.org/blockstack.pdf) 2016-06-22 Muneeb Ali, Jude Nelson, Ryan Shea
+  > Blockchains like Bitcoin and Namecoin and their respective P2P networks have seen significant adoption in the past few years and show promise as naming systems with no trusted parties. Users can register human meaningful names and securely associate data with them, and only the owner of the particular private keys that registered them can write or update the name-value pair. In theory, many decentralized systems can be built using these blockchain networks, such as new, decentralized versions of DNS and PKI. As the technology is relatively new and evolving rapidly, however, little production data or experience is available to guide design tradeoffs.
+  > 
+  > In this paper, we describe our experiences operating a large deployment of a decentralized PKI service built on top of the Namecoin blockchain. We present various challenges pertaining to network reliability, throughput, and security that we needed to overcome while registering and updating over 33,000 entries and 200,000 transactions on the Namecoin blockchain. Further, we discuss how our experience informed the design of a new blockchain-based naming and storage system called Blockstack. We detail why we switched from the Namecoin network to the Bitcoin network for the new system, and present operational lessons from this migration.
+  

_drafts/2020-11-10-veres-one-io.md

@@ -8,13 +8,14 @@ header:
   teaser: /images/veres_one-teaser.webp
 layout: single
 permalink: /blockchain/veres-one/
-categories: ["Blockchain"]
+categories: ["Community Orgs"]
 tags: ["Blockchain","Veres One","Digital Bazaar","Veres One CG","W3C"]
 last_modified_at: 2020-11-10
 toc: false
+published: false
 ---
 
-**[Download](https://nodejs.org/en/download/) • [GitHub](https://github.com/veres-one/) • [Community Group](https://www.w3.org/community/veres-one/) • [Developers](https://veres.one/developers/) • [Twitter](https://twitter.com/veresoneid)**
+**[Download](https://nodejs.org/en/download/) • [GitHub](https://github.com/veres-one/) • [Community Group](https://www.w3.org/community/veres-one/) • [Developers](https://veres.one/developers/)**
 
 
 * [Veres One - Summary](https://veres.one/summary/)

_layouts/home.html

@@ -19,10 +19,12 @@ layout: archive
     {% assign categories_max = category[1].size %}
   {% endif %}
 {% endfor %}
-<ul class="taxonomy__index">
+{% for item in site.data.catz %}
+  <strong>{{ item[0] | upcase }}</strong>
+  <ul class="taxonomy__index">
   {% for i in (1..categories_max) reversed %}
     {% for category in site.categories %}
-      {% if category[1].size == i %}
+      {% if category[1].size == i and item[1] contains category[0] %}
         <li>
           <a href="/categories/#{{ category[0] | slugify }}">
             <strong>{{ category[0] }}</strong> <span class="taxonomy__count">{{ i }}</span>
@@ -31,7 +33,8 @@ layout: archive
       {% endif %}
     {% endfor %}
   {% endfor %}
-</ul>
+  </ul>
+{% endfor %}
 <h2>Tags Grouped by Section</h2>
 <p>This system of navigation is part of an ongoing transition towards making this content, and its subject-matter, more accessible based upon the specific topic you are interested in.</p>
 <h3>Sections</h3>

_layouts/standards.html

@@ -22,11 +22,11 @@ layout: single
   {%endif%}
   {% for row in content %}
     {% unless item contains ";" %}
-      {% if row.section == item and row.main == page.name and mark != 1 %}{%assign mark = 1%}<h2 id="{{item}}">{{item}}</h2><ul>{%endif%}
+      {% if row.section contains item and row.main contains page.name and mark != 1 %}{%assign mark = 1%}<h2 id="{{item}}">{{item}}</h2><ul>{%endif%}
 	{% endunless %}
 	{% if item contains ";" %}
 	  {% assign head = item | split: ";"%}
-      {% if row.section == item and row.main == page.name and marktwo != 1 %}{%assign marktwo = 1%}</ul><h3 id="{{head.last}}">{{head.last}}</h3><ul>{%endif%}
+      {% if row.section contains item and row.main contains page.name and marktwo != 1 %}{%assign marktwo = 1%}</ul><h3 id="{{head.last}}">{{head.last}}</h3><ul>{%endif%}
     {% endif %}
 	{% if row.section contains item and row.main contains page.name %}
       {% include entry_single.html %}

_posts/blockchain/2019-03-05-ethereum.md

@@ -15,7 +15,7 @@ redirect_from:
   - id-initiatives/ethereum/
   - ethereum.html
   - ethereum/
-categories: ["Blockchain"]
+categories: ["Web 3"]
 tags: ["Ethereum","Jolocom","Web3","Transmute","3box","OASIS","Microsoft","Consensys","ERC725","Nuggets","Sidetree","Web3","Ethereum Enterprise Alliance","uPort","Serto","Veramo","Sign in with ETH","ENS","Web3"]
 last_modified_at: 2023-06-26
 

_posts/blockchain/2019-03-11-bitcoin.md

@@ -14,7 +14,7 @@ redirect_from:
   - blockchain/bitcoin
   - id-initiatives/bitcoin/
   - id-initiatives/bitcoin
-categories: ["Blockchain"]
+categories: ["Web 3"]
 tags: ["Bitcoin","Blockchain","Microsoft","History","ION","BTCR","XDI","RWoT"]
 last_modified_at: 2023-06-25
 

_posts/blockchain/2019-04-11-blockchain-identity.md

@@ -9,8 +9,8 @@ header:
 layout: single
 permalink: /blockchain/
 canonical_url: "https://decentralized-id.com/blockchain/"
-categories: ["Blockchain"]
-tags: ["NIST","Identiverse",Authenteq,Blockstack,Civic,Microsoft,Datum,ProCivis]
+categories: ["Web 3"]
+tags: ["NIST","Identiverse","Authenteq","Civic","Microsoft","Datum","ProCivis"]
 last_modified_at: 2023-06-09
 toc: true
 toc_sticky: false

_posts/blockchain/2020-11-10-blockstack.md

@@ -1,50 +0,0 @@
----
-date: 2020-11-10
-title: Blockstack
-description: Blockstack is an open-source and developer-friendly network for building decentralized apps and smart contracts.
-excerpt: >
-  Blockstack builds an alternate DNS and alternate public-key infrastructure. It's the first implementation of a decentralized DNS system on top of the Bitcoin blockchain It combines DNS functionality with public key infrastructure and is primarily meant to be used by new blockchain applications.
-layout: single
-header:
-  image: /images/blockstack_header.webp
-  teaser: /images/blockstack_teaser.webp
-categories: ["Blockchain"]
-tags: [Blockstack,Bitcoin,DID,Blockchain]
-permalink: blockchain/blockstack/
-toc: false
-last_modified_at: 2020-11-10
----
-
-**[Website](https://blockstack.org/) • [GitHub](https://github.com/blockstack) • [Forum](https://forum.blockstack.org/) • [Blog](https://blockstack.org/blog) • [Twitter](https://twitter.com/blockstack) • [Whitepaper](https://blockstack.org/whitepaper.pdf) • [Apps](https://app.co)**
-
-## Blockchain
-
-* [BitcoinWiki](https://en.bitcoinwiki.org/wiki/BlockStack)]
-  > BlockStack is a new network for decentralized applications[1]. Blockstack aims to address the centralization at the application-layer of the internet. More specifically, Blockstack builds an alternate DNS and alternate public-key infrastructure. It's the first implementation of a decentralized DNS system on top of the Bitcoin blockchain It combines DNS functionality with public key infrastructure and is primarily meant to be used by new blockchain applications.
-* [Awesome Blockstack](https://github.com/dantrevino/awesome-blockstack) -[gitlab](https://gitlab.com/dantrevino/awesome-blockstack)
-* [Launch HN: Stacks (YC S14) – The first SEC-qualified crypto token offering](https://news.ycombinator.com/item?id=20413420) -news.ycombinator
-* [Introducing Clarity, a language for predictable smart contracts](https://blog.blockstack.org/introducing-clarity-the-language-for-predictable-smart-contracts/)
-* [Extending Existing Blockchains with Virtualchain](https://www.zurich.ibm.com/dccl/papers/nelson_dccl.pdf)
-* [Breaking Down Blockstack — Whitepaper Review](https://tokeneconomy.co/breaking-down-blockstack-whitepaper-review-3c828788f3e9)
-  * [Breaking Down Blockstack pt2 —  Stack Tokens](https://tokeneconomy.co/breaking-down-blockstack-pt-2-stack-tokens-7718578cfeae)
-
-## Identity
-
-* [Blockchain naming system (BNS)](https://docs.blockstack.org/technology/naming-system)
-  > BNS is a network system that binds names to off-chain state without relying on any central points of control. The Stacks V1 blockchain implemented BNS through first-order name operations. In Stacks V2, BNS is instead implemented through a smart-contract loaded during the genesis block.Names in BNS have three properties:
-  > - Names are globally unique. The protocol does not allow name collisions, and all well-behaved nodes resolve a given name to the same state.
-  > - Names are human-meaningful. Each name is chosen by its creator.
-  > - Names are strongly-owned. Only the name's owner can change the state it resolves to. Specifically, a name is owned by one or more ECDSA private keys.
-* [Blockstack DID Method Specification](https://github.com/blockstack/stacks-blockchain/blob/stacks-1.0/docs/blockstack-did-spec.md)
-  > Blockstack is a network for decentralized applications where users own their identities and data. Blockstack utilizes a public blockchain to implement a decentralized naming layer, which binds a user's human-readable username to their current public key and a pointer to their data storage buckets. The naming layer ensures that names are globally unique, that names can be arbitrary human-meaningful strings, and that names are owned and controlled by cryptographic key pairs such that only the owner of the private key can update the name's associated state.
-* [Authentication](https://docs.blockstack.org/authentication/overview) - Blockstack Auth provides single sign on and authentication without third parties or remote servers.
-  > A decentralized application and the Blockstack App communicate during the authentication flow by passing back and forth two tokens. The requesting application sends the Blockstack App an authRequest token. Once a user approves a sign-in, the Blockstack App responds to the application with an authResponse token. These tokens are JSON Web Tokens, and they are passed via URL query strings.
-* [DID method at identity.foundation](https://forum.blockstack.org/t/did-method-at-identity-foundation/4287) (forum post about DID Method)
-* [Bringing decentralized identity to traditional apps](https://larrysalibra.com/adding-blockstack-auth-to-discourse/)
-  > We really liked the Discourse forum software and wanted to give users the option to sign in with their Blockstack IDs.
-  >
-  > Enabling Blockstack Authentication on a centralized app potentially enables a range of functionality:
-  > - single sign on - users with a Blockstack ID don't have to register again or sign up for your app
-  > - an instant profile system - users can bring their existing profile to your app
-  > - client-side encryption - you can encrypt user data on your users' client devices before sending it to your server. This is great for user privacy and may offer legal and security advantages for your business. Both hackers and law enforcement aren't able to access user data that has been encrypted with keys generated from a Blockstack ID. Hopefully this means they leave you alone!
-  

_posts/blockchain/2020-11-11-ontology.md

@@ -1,99 +0,0 @@
----
-date: 2020-11-11
-title: Ontology
-description: "'Distributed Trust Network' which combines a cross-chain identity system, peer-to-peer data transmission, data authorization mechanisms, distributed data storage, attestation, and various industry-specific modules."
-excerpt: >
-  Ontology is a high performance, open source blockchain specializing in digital identity and data. Ontology's unique infrastructure supports robust cross-chain collaboration and Layer 2 scalability, offering businesses the flexibility to design a blockchain that suits their needs. With a suite of decentralized identity and data sharing protocols to enhance speed, security, and trust, Ontology’s features include ONT ID, a mobile digital ID application and DID used throughout the ecosystem, and DDXF, a decentralized data exchange, and collaboration framework.
-layout: single
-permalink: blockchain/ontology/
-canonical_url: 'https://decentralized-id.com/blockchain/ontology/'
-categories: ["Blockchain"]
-tags: ["Blockchain","Ontology","Ethereum","NEO","Polkadot","Microsoft","Consensys","Universal Resolver"]
-header:
-  image: /images/ontology_header.webp
-  teaser: /images/ontology_teaser.webp
-last_modified_at: 2020-11-11
-toc: true
----
-
-**[Website](https://ont.io/) • [Onto.App](https://onto.app) • [OoDApp](https://oodapp.io/) • [Blog](https://medium.com/ontologynetwork) • [GitHub](https://github.com/ontio/) • [Telegram](https://t.me/OntologyNetwork) • [Telegram Ann](https://t.me/OntologyAnnouncements) • [Twitter](https://twitter.com/OntologyNetwork) • [Youtube](https://www.youtube.com/channel/UCXzLZJgDglAWRU0b2GOa7pA) • [Linkedin](https://www.linkedin.com/company/ontology-network-official/) • [Discord](https://discordapp.com/invite/pQRHtbD) • [Reddit](https://www.reddit.com/r/OntologyNetwork/)**
-
-* [ONTology](https://ont.io/) [[**G**](https://github.com/ontio/ontology-DID)]— "a "Distributed Trust Network" which combines a cross-chain identity system, peer-to-peer data transmission, data authorization mechanisms, distributed data storage, attestation, and various industry-specific modules. It also includes an Ontology Crypto Package (OCP) and an Ontology Marketplace (OM)."
-
-## Company
-
-* [Ontology is Now Officially a Technical Provider for Enterprise Solutions through Cointelegraph](https://medium.com/ontologynetwork/ontology-is-now-officially-a-technical-provider-for-enterprise-solutions-through-cointelegraph-80db38c45489)
-  > [With over 5 million unique visitors each month and over 17 million page views](https://cointelegraph.com/advertise), Cointelegraph has rapidly established itself as one of the media anchors in the blockchain space. But the readers it attracts aren’t merely traders, enthusiasts, or bitcoin fiends — rather, Cointelegraph has quietly established itself as a legitimate mediator between established enterprises and blockchain technology providers. As a result, a [consulting arm](https://cointelegraph.com/consulting) was launched that aims to “connect the world between blockchain and traditional institutions of all sizes by bringing wider adoption of digital assets and enterprise-grade blockchain solutions through education and professional consulting services.”\
-  > [...]\
-  > The [SAGA market](https://www.sagamarket.io/) is another real-case application for Ontology’s public chain as over 200,000+ users and 10,000+ ecosystem partners rely on SAGA to access streams of decentralized data ranging from foreign exchanges to meteorology.
-* [Ontology Takes Centre Stage at Blockchain Expo Tokyo](https://medium.com/ontologynetwork/ontology-takes-centre-stage-at-blockchain-expo-tokyo-d82a50f8682c)
-  > Following the launch of our highly anticipated bespoke automotive solution and our [recent partnership](https://medium.com/ontologynetwork/daimler-mobility-partners-with-ontology-to-leverage-high-performance-technologies-and-transform-b469aa46e671) with global financial and mobility services provider, Daimler Mobility, Morio Katayama, Ontology’s Japan Ecosystem Lead, will share Ontology’s unique automotive solution at the newly launched [Blockchain Expo Tokyo](https://www.bc-expo-at.jp/en-gb.html). To learn more about this partnership, Morio will be speaking on Wednesday, 28th October from 12.45 pm to 13.45 pm. At the venue, his talk will be taking place in the presentation room located next to the exhibition venue, where there will be 50 seats available.
-
-### Use Cases
-
-* [Automotive](https://ont.io/automotive) 
-* [Data Marketplace](https://ont.io/marketplace)
-* [Data Attestation](https://ont.io/attestation)
-* [Digital Finance](https://ont.io/finance)
-* [Enterprise Solutions](https://ont.io/Ontology%20Enterprise%20Solutions%20Brochure_July%202020.pdf)
-
-
-## Blockchain
-
-* [ONTO’s cross-chain aggregate swap function now is available](https://medium.com/ontologynetwork/ontos-cross-chain-aggregate-swap-function-now-is-available-eedd26dab60a)
-  > In the recently released ONTO v3.6.0, the built-in cross-chain aggregate swap function in the “Market” tab added multiple trading pairs, enabling users to instantly swap assets between multiple chains at any time.
-* [Everything you need to know about Ontology node staking on ONTO](https://medium.com/ontologynetwork/everything-you-need-to-know-about-ontology-node-staking-on-onto-467d0dc71844)
-  * > Q1： Is there a guideline to Ontology node staking on ONTO?
-  * > Q2： What is the APY for Ontology node staking on ONTO?
-  * > Q3： Are the staked assets on nodes safe？
-  * > Q4：How long does one staking round take？
-  * > Q5： Are there limits on the node staking amount?
-  * > Q6： Will I be rewarded ONG immediately if I confirm the stake?
-  * > Q7： How much does transaction for node staking cost?
-  * > Q8： When can users withdraw the staking rewards？
-  * > Q9： When will I receive the ONT if I cancel the stake?
-  * > Q10: Compared with the ONT staking services provided by other third-party trading platforms and wallets, what advantages does the node staking of ONTO wallet have?
-
-
-### [GitHub](https://github.com/ontio/)
-
-* [ontology](https://github.com/ontio/ontology) - Official Go implementation of the Ontology protocol. 
-* [documentation](https://github.com/ontio/documentation) 
-* [OEPs](https://github.com/ontio/OEPs) - Ontology Enhancement Proposal
-* [OWallet](https://github.com/ontio/OWallet/releases) - a comprehensive Ontology desktop wallet
-* [ontology-explorer](https://github.com/ontio/ontology-explorer) - Ontology blockchain explorer
-* [ontology-go-sdk](https://github.com/ontio/ontology-go-sdk)
-* [ontology-oracle](https://github.com/ontio/ontology-oracle) - The Oracle node and Oracle contract
-* [ontology-crypto](https://github.com/ontio/ontology-crypto) - Cryptography Library for Ontology Network
-* [oracle-chainlink-smartcontract](https://github.com/ontio/oracle-chainlink-smartcontract)
-* [ontology-smartcontract](https://github.com/ontio/ontology-smartcontract) - tools, tutorials for ontology smart contact
-* [go-bip32](https://github.com/ontio/go-bip32) - Golang implementation of the BIP32 HD address spec
-
-## Identity
-
-* [Ontology Builds on Polkadot to Accelerate Adoption Of Decentralized Identity Solution](https://medium.com/ontologynetwork/ontology-builds-on-polkadot-to-accelerate-adoption-of-decentralized-identity-solution-acf7b8357ee)
-  > Developed over the past couple of months, the Ontology [parachain](https://github.com/siovanus/DID-substrate) currently consists of a DID Substrate pallet, with plans for further integration of other custom components. Further plans for the Ontology parachain include:
-  >
-  > Ontology OScore — an off-chain DID authorization mechanism to manage wallet-identity relationships and provide ID-based credit scores for on-chain actions related to digital assets. The integration of Ontology’s distributed data exchange framework (DDXF), permitting both token association and data tokenization. Expanding DID’s use cases from users to also include data and resources, providing authentication, authorization, and accounting (AAA) for DID based resource instances via on-chain data access control with data-tokens (tokenization), and association of its value. DDXF provides on-chain AAA for data interoperability cross systems.
-* [Ontology Boosts Security And Compliance Through Integration With Chainalysis](https://medium.com/ontologynetwork/ontology-boosts-security-and-compliance-through-integration-with-chainalysis-3dfce3c154ec)
-  > [Ontology](https://ont.io/), the high performance, open-source blockchain specializing in digital identity and data, has announced today an integration with [Chainalysis](https://www.chainalysis.com/), the blockchain analysis company.
-  > 
-  > Ontology will utilize Chainalysis’s compliance and investigative solutions, KYT (Know Your Transaction) and Reactor, to enhance trust, provide a safer experience to traders, and combat illicit activity through transaction monitoring and tracing.
-* [Lower Your Collateral Requirements & Loan Interests with OScore](https://medium.com/ontologynetwork/lower-your-collateral-requirements-loan-interests-with-oscore-fb2c835a9998)
-  > [OScore](https://ocredit.io/), the first credit score for the decentralized world built with Ontology’s Decentralized Identity has officially launched. For simplicity, consider OScore an on-chain reputational system that supports cross-chain interaction with verifiable credentials on the Ontology blockchain, hence eliminating third-party verification programs from the process. Once a user authorizes their digital financial data, Ontology’s OScore system automatically generates a quantifiable credit score while ensuring a user’s privacy is fully protected and controlled by themselves.
-
-### Identity Repos
-* [ontology-DID](https://github.com/ontio/ontology-DID) Ontology decentralized identification protocol based on W3C DID specifications.
-  > Ontology DID(Also: ONT ID) is a decentralized identification protocol which based on W3C DID specifications.It supports collaborative services such as distributed and diversified ownership confirmation, identification, and authentication of various entities including individuals, legal entities, objects, and contents. ONT ID establishes a cryptographically-based digital identity for each entity, allowing self-sovereign of data authorization and ownership confirmation, which makes the identity and data truly assets that the user can control. ONT ID has the characteristics of decentralization, self-management, privacy protection, security and ease of use.
-* [ontology-ddxf](https://github.com/ontio/ontology-ddxf) - Distributed data eXchange Framework,which allows to build data marketplaces.
-  > The downsides of centralized data exchange include data caching, use of data without user authorization and data copyright protection. Ontology is proposing a Distributed Data Protocol (ONT Data). Based on the protocol , we have come up with distributed data exchange framework(DDXF) which allows to customize data trading marketplaces with secured data and financial security. With DDXF, the developer of the ontology ecosystem can easily develop decentralized data application that meets the needs of various scenarios with various features.
-* [ontology-eventbus](https://github.com/ontio/ontology-eventbus) - The Go Language Implementation of Ontology Actor Model
-  > Actor is a model of parallel computation model in computer science that treats "actors" as the the universal primitives of concurrent computation. In response to a message that it receives, an actor can make local decisions: make local decisions, create more actor, send more messages, and determine how to respond to the next message received.
-* [ONTO](https://github.com/ontio/ONTO)
-  > ONTO is a comprehensive decentralized client product, which is an entrance of trust search engine and blockchain system.
-* [ontid-driver](https://github.com/ontio/ontid-driver) - ONT ID driver for universal resolver
-
-### [OntologyCommunityDevelopers](https://github.com/OntologyCommunityDevelopers/) 
-
-### [Ontio Cyano](https://github.com/ontio-cyano/)
-

_posts/decentralized-web/2021-04-14-iota.md

@@ -9,7 +9,7 @@ excerpt: >
 layout: single
 permalink: blockchain/iota-foundation/
 canonical_url: 'https://decentralized-id.com/blockchain/iota-foundation/'
-category: ["Blockchain"]
+category: ["Decentralized We"]
 tags: ["IOTA","Blockchain","Dark Matter Labs","Eclipse"]
 header:
   image: /images/iota-identity.webp

_posts/decentralized-web/2023-07-05-web5.md

@@ -4,7 +4,7 @@ description: "Leverage Decentralized Identifiers, Verifiable Credentials, and De
 excerpt: >
   TBD’s open source platform enables developers to build products and services on technologies. We believe an open source model will win in a decentralized, world. TBD’s strategy: build open source, collaborate with the community, and invest in the as a public good to advance the state of decentralization.
 layout: single
-categories: ["Open Source Projects","Web 3"] 
+categories: ["Open Source Projects","Decentralized Web"] 
 tags: ["Block","TBD","Web5","Web3","DWeb","GLEIF"]
 permalink: /projects/tbd/web5/
 canonical_url: "https://decentralized-id.com/projects/tbd/web5/"

_posts/development/2019-02-27-Microledgers-Edgechains-Hardman-HGF.md

@@ -11,7 +11,7 @@ redirect_from:
   - /hgf-2018/Microledgers-Edgechains-Hardman-HGF/
   - /hgf-2018/Microledgers-Edgechains-Hardman-HGF
 author_profile: false
-categories: ["Development"]
+categories: ["Technology"]
 tags: ["Indy","Transcript","Hyperledger Forum","Evernym","GDPR","DID:PEER","Literature","HGF 2018"]
 published: true
 last_modified_at: 2019-12-11

_posts/development/2020-01-10-linked-data.md

@@ -7,7 +7,7 @@ description: These hyperlinks connect all Linked Data into a single global data
 excerpt: >
   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.
 tags: ["Linked Data","Solid","JSON-LD","RDF","W3C","Veres One","RSA"]
-categories: ["Development"]
+categories: ["Technology"]
 permalink: /development/linked-data/
 canonical_url: "https://decentralized-id.com/development/linked-data/"
 redirect_from:

_posts/development/2021-04-18-object-capabilities.md

@@ -6,7 +6,7 @@ title: "Object Capability Model"
 description: in which a capability describes a transferable right to perform one (or more) operations on a given object.
 excerpt: >
   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.
-categories: ["Development"]
+categories: ["Technology"]
 tags: ["oCap","JSON-LD","zCap","Cosmos"]
 permalink: /development/object-capabilities/
 canonical_url: "https://decentralized-id.com/development/object-capabilities/"

_posts/development/2023-06-13-biometrics.md

@@ -6,7 +6,7 @@ excerpt: >
 layout: single
 permalink: /development/biometrics/
 canonical_url: "https://decentralized-id.com/development/biometrics/"
-categories: ["Development"]
+categories: ["Technology"]
 tags: ["Biometrics"]
 last_modified_at: 2023-06-09
 toc: true

_posts/development/2023-06-22-user-experience.md

@@ -12,7 +12,7 @@ redirect_from:
   - /literature/self-sovereign-identity/user-experience/
   - self-sovereign-identity/user-experience
   - self-sovereign-identity/user-experience/
-categories: ["Development"]
+categories: ["Technology"]
 tags: ["User Experience","Relationships"]
 last_modified_at: 2023-06-23
 published: true

_posts/development/2023-06-23-architecture.md

@@ -7,7 +7,7 @@ layout: single
 toc: true
 permalink: /development/architecture/
 canonical_url: 'https://decentralized-id.com/development/architecture/'
-categories: ["Development"]
+categories: ["Technology"]
 tags: ["Architecture"]
 last_modified_at: 2023-06-23
 ---

_posts/development/2023-06-23-ethics-rights-sovereignty.md

@@ -8,7 +8,7 @@ toc: true
 toc_sticky: false
 permalink: /development/ethics-rights-sovereignty/
 canonical_url: 'https://decentralized-id.com/development/ethics-rights-sovereignty/'
-categories: ["Development"]
+categories: ["About"]
 tags: ["Ethics","Human Rights","Sovereignty"]
 last_modified_at: 2023-06-23
 ---

_posts/development/2023-06-29-decentralization.md

@@ -4,7 +4,7 @@ description: "Fixating on the degree—rather than the type—of decentralizatio
 excerpt: >
   Decentralization is a commonly misunderstood concept. For example, it is sometimes said that the reason cryptonetwork advocates favor decentralization is to resist government censorship, or because of libertarian political views. These are not the main reasons decentralization is important.
 layout: single
-categories: ["Development"]
+categories: ["Technology"]
 tags: ["Decentralization"]
 permalink: /development/decentralization/
 canonical_url: "https://decentralized-id.com/development/decentralization/"

_posts/development/2023-06-30-business.md

@@ -8,7 +8,7 @@ toc: true
 toc_sticky: false
 permalink: /development/business/
 canonical_url: 'https://decentralized-id.com/development/business/'
-categories: ["Development"]
+categories: ["About"]
 tags: ["Business","Trends","Markets"]
 last_modified_at: 2023-06-30
 ---

_posts/development/2023-07-01-governance.md

@@ -4,7 +4,7 @@ description: "Trust frameworks are complicated so getting governance right requi
 excerpt: >
   The trust infrastructure is concerned with the question of how and why the presented information can be trusted. It defines the rules for all stakeholders and enables legally binding relationships with the combination of governance frameworks, which are built on top of trust frameworks.
 layout: single
-categories: ["Development"]
+categories: ["Technology"]
 tags: ["Governance","Trust Frameworks","Trust Registries","Machine Readable Governance"]
 permalink: /development/governance-trust-frameworks-registries/
 canonical_url: "https://decentralzed-id.com/development/governance-trust-frameworks-registries/"

_posts/development/2023-07-01-wallets.md

@@ -4,7 +4,7 @@ description:
 excerpt: > 
   SSI and identity wallets will make it easier for citizens, organizations and governments to manage (digital) identities. It will make registrations and transactions across the internet private and secure. It will also make organizations more efficient and effective.
 layout: single 
-categories: ["Development"]
+categories: ["Technology"]
 tags: ["Wallets","User Experience"]
 toc: true
 toc_sticky: false

_posts/development/2023-07-02-interop.md

@@ -5,7 +5,7 @@ excerpt: >
   Interoperability moves from theory to reality when companies have meaningful ability to choose. It is predicated on open standards foundations that enable easy movement of data and vendors.
 layout: single
 toc: true
-categories: ["Development"]
+categories: ["Technology"]
 tags: ["Aries","INTABA","Indicio","Transmute","Danube Tech","DHS","Open Badges","Interop"]
 permalink: /development/interop/
 canonical_url: "https://decentralized-id.com/development/interop/"

_posts/events/2019-03-02-rebooting-web-of-trust.md

@@ -15,7 +15,7 @@ redirect_from:
   - rebooting-web-of-trust
   - rebooting-web-of-trust/
 toc_sticky: false
-categories: ["Resources","Events"]
+categories: ["Events"]
 tags: ["RWoT","Bitcoin","Ethereum","DPKI","Verifiable Credentials","Consensys","Blockstack","JSON-LD","Data Hubs","Self Sovereign Identity","eIDAS","Blockcerts","GDPR","PGP","Veres One","W3C","XDI","BTCR","California","DKMS","Digital Bazaar","IPID"]
 last_modified_at: 2020-10-10
 ---

_posts/events/2020-11-03-iiw-session-topics.md

@@ -3,7 +3,7 @@ title: Session Topics from the Internet Identity Workshop since 2005
 layout: single
 description: Session topics from the Internet Identity Workshop over the past 15 years
 excerpt: "If you want to stay current in digital identity, keeping an eye on the session topics of the biannual internet identity workshop is a good place to start."
-categories: ["Events","Resources"]
+categories: ["Events"]
 tags: ["Decentralized Identifiers","WebAuthN","MATTR","GS1","JSON-LD","KERI","Evernym","GDPR","CCPA","DIF","DIDComm","ID2020","Aries","Indy","BBS Signatures","JLinc","Verifiable Credentials","W3C","XDI","Veres One","Ethereum","eIDAS","Universal Resolver","DKMI","Universal Registrar","OASIS","OAuth","OIDC","Blockstack","Onfido","XDI","Ursa","Respect Network","AI","California","DKMS","Danube Tech","FIDO","iRespond","Trust Framework","MyData"]
 permalink: workshops/internet-identity-workshop/
 redirect_from:

_posts/government/canada/2020-12-04-diacc.md

@@ -11,7 +11,7 @@ excerpt: >
 
     Together we can unlock opportunities for Canadians, decrease costs for governments, consumers, and business, improve service delivery, and drive GDP growth.
 layout: single
-categories: ["Organizations"]
+categories: ["Government"]
 tags: ["Policy","DIACC","Canada","Trust Framework","BMO","Canadapost","Cibc","Desjardins","ForgeRock","Interac","Manulife","Newbruns","Ontairo","SecureKey","Td","Telus","2Keys","ATB","Affinity Credit Union","Applied Recognition","CCUA","CDIC","C1","Canada Health Infoway","Convergence","DI","Digidentity","Equifax","FIDO","Equitable Bank","Hypersecu","iComply","IDC2018","IdentityNorth","Identos","In fidem","Ltsa","Libro","LD","Mastercard","Northern Block","Notarius couleur","OARO","One span","Onfido","Outlier","Payments Canada","Prodigy","PlaceSpeak","Quartech","RBC 1","Safran","Saskatchewan","Securefact","Simeio","Smart species","TreeFort","Trulioo","Vallid","Vancity","Worldreach","Yoti","IBM","BCGov","Vivvo","UXP Systems","Boloro","Plurilock","1Kosmos","Gambit","In-Sec-M","Ingenico","ISO 18013-5","100101075","Get Group","Pragma","Modohr","Celero","Vlinder","Mavennet","iProov","Peer Social","Jumio","Folio","Auth0","Arucc","Stash","Supercluster","PCTF"]
 header:
   image: /images/diacc-header.webp

_posts/open-source-projects/2020-11-22-keri.md

@@ -2,7 +2,7 @@
 date: 2020-11-22
 name: KERI
 layout: standards
-headings: ["Main","About","Organization","Development","Presentations","Literature; Self-Certifying Identifiers","Literature; Autonomic Identifiers","Literature; Certificate Transparency","Assorted"]
+headings: ["Main","About","Organization","Technology","Presentations","Literature; Self-Certifying Identifiers","Literature; Autonomic Identifiers","Literature; Certificate Transparency","Assorted"]
 title: KERI - Key Event Receipt Infrastructure
 description: The first truly fully decentralized identity system.
 excerpt: >

_posts/open-source-projects/2020-11-26-DID-communications.md

@@ -3,7 +3,7 @@ date: 2020-11-26
 title: DID Communications (DIDComm) - DIF
 name: DIDComm
 layout: standards
-headings: ["Explainer","RFCs","Development","Implementation"]
+headings: ["Explainer","RFCs","Technology","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.

_posts/organizations/2019-03-07-identity-foundation.md

@@ -10,7 +10,7 @@ redirect_from:
   - organizations/identity-foundation
   - identity-foundation.html
   - organizations/identity-foundation/
-categories: ["Organizations"]
+categories: ["Standards Development Orgs"]
 tags: ["DIF","DIDComm WG","Claims and Credentials WG","Storage and Compute WG","Identifiers and Discovery WG","DIDAuth WG","Interop WG","Affinidi","Anonyome Labs","ArcBlock","Auth0","Beijing Teleinfo Technology","Blockchain Foundry","Blockchain","Blockpass","Blockstack","Hiro","Bloom Protocol","BOTLabs","BCGov","Burrata","Centre","ceramic","civic","CollaboGate","Condatis","Consensys Mesh","Credivera","CU Ledger","Cybavo","Cyber Securiteam","Danube Tech","Diwala","dock","Earth ID","Enterprise Ethereum Alliance","extrimian","Fennel Labs","Finema","Gen Digital","Genoo","GS1","Hedera","IBCT","ID Ramp","iDAKTO","iden3","Identity.com","Infra Blockchain","Input Output","Interac","Iuncta","Keyless","Litentry","Magic Labs","Mattr","Meeco","Metadium","Microsoft","Monokee","myDid","Nayuta","Neosfer","Nest(R)","nuggets","NuID","Nymlab","OneSpan","PassiveBolt","Ping Identity","Polygon Labs","Portabl","Proxy","Qikfox","Resiliant","Sezoo","Silence Laboratories","Sphereon","SpruceID","Superlunar","Switchchord","Taqanu","The Humanized Internet","Torus Labs","Transmute","Trinsic","Trudenty","UNIFY Solutions","UniWorld","Validated ID","VelocityCareer Labs","Web3 Labs","WeBank","Workday",YellowDotPink,"Aries","Universal Resolver","Standards Development Org"]
 last_modified_at: 2023-06-12
 ---

_posts/organizations/2019-03-09-sovrin-foundation.md

@@ -15,7 +15,7 @@ permalink: organizations/sovrin-foundation/
 canonical_url: 'https://decentralized-id.com/organizations/sovrin-foundation/'
 redirect_from: 
   - organizations/sovrin/
-categories: ["Organizations"]
+categories: ["Community Orgs"]
 tags: ["Indy","Verifiable Organizations Network","Sovrin Foundation","ABSA Group","AyanWorks","Bloqzone","Certizen","Condatis","CPQD","Danube Tech","Desert Financial Credit Union","Dhiway","ID Crypt Global","Monokee","RIDDLE&CODE","The Institute for Internet-Security","Trinsic","Axuall","Outlier Ventures","One Global","Fetch.ai","MakoLab","Regio iT","Anonyome Labs","Unveil.Social","NEC","Truu (ID)","SITA","Digicert","Veridium","Finicity","Perkins Coie","SICPA","OAS Staff Federal Credit Union","Deutsche Telekom AG","ATB Financial","esatus AG","ProSapien","InfoCert","Evernym","Royal Credit Union","iRespond","DIDx","Verifiable Credentials","W3C","GDPR","Trust Framework","Sovrin Foundation","DKMS","Humanitarian"]
 last_modified_at: 2023-06-12
 ---

_posts/organizations/2019-04-04-mydata.md

@@ -6,7 +6,7 @@ excerpt: >
   We are entrepreneurs, activists, academics, listed corporations, public agencies, and developers. For years, we’ve been using different words for what we do – MyData, Self Data, VRM (Vendor Relationship Management), Internet of Me, PIMS (Personal Information Management Services) etc, while sharing a common goal: to empower individuals with their personal data, thus helping them and their communities develop knowledge, make informed decisions, and interact more consciously and efficiently with each other as well as with organisations.
 toc: true
 toc_sticky: false
-categories: ["Organizations"]
+categories: ["Community Orgs"]
 tags: ["MyData","eIDAS","GDPR","Meeco","JLinc","Verifiable Credentials","OAuth","AI","DKMS","Avast","MyDex","Cozy Cloud","Data Governance"]
 redirect_from: organizations/mydata
 canonical_url: 'https://decentralized-id.com/organizations/mydata/'

_posts/organizations/2019-07-15-women-in-identity.md

@@ -4,7 +4,7 @@ title: "Women in Identity - @WomeninID"
 excerpt: >
   Digital identity solutions built for everyone are built by everyone.
   Women in Identity inspires, elevates and supports a more diverse workforce in the digital identity industry.
-categories: ["Organizations"]
+categories: ["Community Orgs"]
 tags: ["WomeninID","GDPR"]
 permalink: organizations/women-in-identity/
 redirect_from: 

_posts/organizations/2020-10-11-hyperledger.md

@@ -13,7 +13,7 @@ permalink: blockchain/hyperledger/
 redirect_from:
   - organizations/hyperledger/
 canonical_url: 'https://decentralized-id.com/blockchain/hyperledger/'
-categories: ["Organizations"]
+categories: ["Community Orgs"]
 tags: ["Indy","Fabric","Aries","Evernym","Sovrin Foundation","Enterprise Ethereum Alliance","Linux Foundation","Ursa","Microsoft","Salesforce","Sawtooth","agreementsolutions","BTP","Ayanworks","Blinking","SecureKey","Oracle","HealthDigit","T-Mobile NEXT Identity","Sony","Global","Education"]
 last_modified_at: 2023-06-12
 header:

_posts/organizations/2020-11-25-planetwork.md

@@ -4,7 +4,7 @@ title: Planetwork
 description: Dedicated to addressing the global imperatives of our time
 excerpt: >
     We are dedicated to the creation and maintenance of a digital communications platform, operated as a public interest utility, that will strengthen civil society by enabling people to connect, communicate, make transactions, and self-organize in a manner that is consistent with the highest principles of democracy and reflects an enlightened understanding of the fragile beauty of our planet. We will bring together, develop, promote, and hold as a global public commons, software tools and infrastructure that facilitate the emergence, growth, and vitality of networks of individuals and organizations who share ecological and social justice values, as articulated in the Earth Charter.
-categories: ["Organizations","History"]
+categories: ["Community Orgs","History"]
 tags: ["Planetwork","Augmented Social Network","Bloom","XDI","JLinc","IDCommons","OASIS"]
 permalink: organizations/planetwork/
 header: 

_posts/organizations/2021-04-15-id2020.md

@@ -3,7 +3,7 @@ title: The ID2020 Alliance
 description: The ID2020 Alliance is a global partnership maximizing the potential of digital ID to improve lives.
 excerpt: >
   The ability to prove who you are is a fundamental and universal human right. Because we live in a digital era, we need a trusted and reliable way to do that both in the physical world and online.
-categories: ["Organizations"]
+categories: ["Community Orgs"]
 tags: ["DIAL","Accenture","ID2020","Gavi","Ideo","Microsoft","Rockefeller Foundation","UC Berkeley","BLOK","FHI360","hyperledger foundation","ICC","iRespond","Kiva","Mastercard","Mercy Corps","National Cybersecurity Center","Panta Transportation","Simprints","RWoT"]
 permalink: organizations/id2020/
 header: 

_posts/organizations/2021-04-16-gleif.md

@@ -3,7 +3,7 @@ title: Global Legal Entity Identifier Foundation - GLEIF
 description: The ID2020 Alliance is a global partnership maximizing the potential of digital ID to improve lives.
 excerpt: >
     Established by the Financial Stability Board in June 2014, the Global Legal Entity Identifier Foundation (GLEIF) is tasked to support the implementation and use of the Legal Entity Identifier (LEI). The foundation is backed and overseen by the LEI Regulatory Oversight Committee, representing public authorities from around the globe that have come together to jointly drive forward transparency within the global financial markets. GLEIF is a supra-national not-for-profit organization headquartered in Basel, Switzerland.
-categories: ["Organizations"]
+categories: ["Standards Development Orgs"]
 tags: ["GLEIF","Verifiable Credentials","Serto","CFCA","DigiCert","InfoCert","DIZME","Entrust Datacard","ICAI India","SwissSign","Evernym","Ubisecure","Standards Development Org","Contour","RapidLEI","Amazon","Government","Policy"]
 permalink: /organizations/gleif/
 header: 

_posts/organizations/2023-06-05-TOIP.md

@@ -6,7 +6,7 @@ excerpt: >
 layout: single
 permalink: organizations/trustoverip/
 canonical_url: 'https://decentralized-id.com/organizations/trustoverip/'
-categories: ["Organizations"]
+categories: ["Community Orgs"]
 tags: ["Centre","BCGov","GLEIF","Interop","Governance","OIX","Sovrin Foundation","Avast","KABN Network"]
 last_modified_at: 2023-07-02
 ---

_posts/organizations/2023-06-05-centre.md

@@ -6,7 +6,7 @@ excerpt: >
 layout: single
 permalink: organizations/centre/
 canonical_url: 'https://decentralized-id.com/organizations/centre/'
-categories: ["Web 3","Organizations"]
+categories: ["Web 3","Community Orgs"]
 tags: ["Centre","Coinbase","Web3","Policy"]
 last_modified_at: 2023-07-03
 ---

_posts/organizations/2023-08-12-lfph.md

@@ -6,7 +6,7 @@ excerpt: >
 layout: single
 permalink: /organizations/Linux-Foundation-Public-Health_Cardea/
 canonical_url: 'https://decentralized-id.com/organizations/Linux-Foundation-Public-Health_Cardea/'
-categories: ["Organizations"]
+categories: ["Community Orgs"]
 tags: ["Linux Foundation","LFPH","Healthcare","Covid 19","Public Health Advisory Council","Cardea","TRAIN","ESSIF","GCCN","Hyperledger Labs"]
 last_modified_at: 2023-08-12
 ---

_posts/organizations/2023-08-12-openid.md

@@ -4,7 +4,7 @@ description: "Our mission is to lead the global community in creating identity s
 layout: single
 excerpt: >
   Founded in 2007, the OpenID Foundation (OIDF) is a global open standards body committed to helping people assert their identity wherever they choose. We are global vibrant community where identity peers and thought leaders convene to craft the identity ecosystems of tomorrow.
-categories: ["Organizations"]
+categories: ["Standards Development Orgs"]
 tags: ["OpenID","Open Banking","SSE","GAIN","Standards Development Org"]
 permalink: /organizations/openid/
 canonical_url: 'https://decentralized-id.com/organizations/openid/'

_posts/organizations/2023-08-13-we-are-open.md

@@ -4,7 +4,7 @@ description: "whatever your project, our interest, knowledge and networks can he
 layout: single
 excerpt: >
   We’re a collective of independent thinkers and makers helping charities, ethical companies, government departments and educational institutions with sensemaking and digital transformation.
-categories: ["Organizations"]
+categories: ["Community Orgs"]
 tags: ["We are Open","Open Badges","Open Recognition","Accredible","Badgecraft","Open Recognition","Keep Badges Weird","BadgeCollect","Badge List","BadgeFactor","BadgeOS","Badgetree™","BCdiploma","Bestr","CanCred.ca","Canvas Credentials","Credly","ForAllRubrics","HPass","Hyland Credentials","Milestone","NOCTI","Open Badge Factory","Openbadges.me","Participate","RedCritter","Sertifier","VerifyEd"]
 permalink: /organizations/we-are-open/
 canonical_url: 'https://decentralized-id.com/organizations/we-are-open/'

_posts/resources/2019-03-11-literature.md

@@ -7,7 +7,7 @@ excerpt: >
   provides an overview of the SSI properties, focusing on an in-depth analysis, furthermore presenting a comprehensive collection of SSI properties that are important for the implementation of the SSI system. 
 header: 
   image: /images/literature-christian-wiediger-unsplash.webp
-categories: ["Resources"]
+categories: ["About"]
 tags: ["Literature","Resources"]
 toc: true
 toc_sticky: false

_posts/resources/2021-04-17-resources.md

@@ -10,7 +10,7 @@ redirect_from:
   - media/
   - podcasts/
 canonical_url: 'https://decentralized-id.com/resources/'
-categories: ["Resources"]
+categories: ["About"]
 tags: ["Resources"]
 last_modified_at: 2023-06-30
 ---

_posts/web-standards/2019-03-03-web-standards.md

@@ -11,7 +11,7 @@ redirect_from:
   - standards
   - standards/
   - specs-standards/
-categories: ["Web Standards"]
+categories: ["Related Standards"]
 tags: ["W3C","Credentials Community Group","hyperledger foundation","FIDO","OpenID","XDI","OASIS","JSON-LD","Verifiable Credentials","Ethereum","Blockcerts","OAuth","OIDC","DKMS","ERC725","RWoT","Schema.org","Learning Machine"]
 last_modified_at: 2023-06-01
 header: 

_posts/web-standards/2020-01-04-JSON-LD.md

@@ -3,7 +3,7 @@ date: 2020-01-04
 title: JSON-LD - W3C
 name: JSON-LD
 layout: standards
-headings: ["Main","Explainer","Presentation","Working Group","Development"]
+headings: ["Main","Explainer","Presentation","Working Group","Technology"]
 excerpt: >
   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
    
@@ -16,7 +16,7 @@ redirect_from:
   - specs-standards/JSON-LD/
   - specs-standards/linked-data/JSON-LD/
 canonical_url: 'https://decentralized-id.com/web-standards/w3c/wg/json-ld/json-ld/'
-categories: ["Web Standards"]
+categories: ["Related Standards"]
 tags: ["Digital Bazaar","JSON-LD","Credentials Community Group","Veres One","Linked Data","W3C","Verifiable Credentials","RDF","Schema.org"]
 last_modified_at: 2023-05-19 
 ---

_posts/web-standards/2020-01-07-blockcerts.md

@@ -3,7 +3,7 @@ date: 2020-01-07
 title: Blockcerts
 name: Blockcerts
 layout: standards
-headings: ["Learning Machine","Blockcerts","Open Badges","Literature","Adoption","Development","Development; Issuing","Development; Demo","Development; Verifiable Credentials","Development; Validation","Development; Verification","Development; Apps"]
+headings: ["Learning Machine","Blockcerts","Open Badges","Literature","Adoption","Technology","Development; Issuing","Development; Demo","Development; Verifiable Credentials","Development; Validation","Development; Verification","Development; Apps"]
 description: "Open Standard for Blockchain Certificates"
 excerpt: >
   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.
@@ -14,7 +14,7 @@ permalink: /web-standards/blockcerts/
 redirect_from: 
   - /blockchain/bitcoin/blockcerts/
   - /specs-standards/blockcerts/
-categories: ["Web Standards"]
+categories: ["Related Standards"]
 tags: ["Bitcoin","Learning Machine","BTCR","Verifiable Credentials","JSON-LD","Ethereum","Blockcerts","RWoT","DHS","DID"]
 last_modified_at:  2023-06-02
 ---

_posts/web-standards/2020-01-09-webauthn.md

@@ -2,14 +2,14 @@
 title: WebAuthN - W3C
 name: WebAuthN
 layout: standards
-headings: ["Main","FIDO Alliance","Working Group","Development"]
+headings: ["Main","FIDO Alliance","Working Group","Technology"]
 description: Allows users to register and authenticate on websites or mobile apps using an "authenticator" instead of a password.
 excerpt: >
   The Web Authentication Working Group will develop recommendation-track specifications defining an API, as well as signature and attestation formats which provide an asymmetric cryptography-based foundation for authentication of users to Web Applications.
   
   Overall goals include obviating the use of shared secrets, i.e. passwords, as authentication credentials, facilitating multi-factor authentication support as well as hardware-based key storage while respecting the Same Origin Policy (SOP) by default and allowing for explicit, constrained SOP relaxation.
 tags: ["W3C","WebAuthN","Microsoft","FIDO","Stranger Labs"]
-categories: ["Web Standards"]
+categories: ["Related Standards"]
 redirect_from: 
   - web-standards/w3c/webauthn/webauthn/
   - specs-standards/webauthn/

_posts/web-standards/2020-11-09-world-wide-web-consortium_w3c.md

@@ -8,7 +8,7 @@ description: An international community that develops open standards to ensure t
 excerpt: "First started as an IETF application area at the beginning of 1990, the Web standard stack, given its foreseen volume and applicative nature on top of the Internet protocols, quickly spun off its own forum. The W3C then laid the foundations of the Web with the development of HTML 4 and XML at the end of the last century. It still works closely with IETF today, on the HTTP or URL specifications and in other areas of common interest (e.g. crypto, security, video)."
 permalink: /web-standards/w3c/
 canonical_url: 'https://decentralized-id.com/web-standards/w3c/'
-categories: ["Web Standards","Organizations"]
+categories: ["Standards Development Orgs"]
 tags: ["W3C","Credentials Community Group","JSON-LD","WebAuthN","Decentralized Identifiers","Verifiable Credentials","Veres One","BTCR","Linked Data","Standards Development Org"]
 header:
   image: /images/w3c_banner.webp

_posts/web-standards/2020-11-20-GS1.md

@@ -8,7 +8,7 @@ description: We are a global, neutral, non-profit standards organisation that br
 excerpt: >
   Gs1 introduced the barcode in 1974. We are a global, neutral, non-profit standards organisation that brings efficiency and transparency to the supply chain. Our standards are proven by industry and can help you achieve your public policy goals.
   Designed by consensus, our standards are proven, open and benefit from collaboration with respected global companies as well as local SME's. GS1 tools help organisations exchange critical data - from manufacturing all the way to the consumer - creating a common language that underpins systems and processes all over the world.
-categories: ["Web Standards","Organizations"]
+categories: ["Related Standards","Standards Development Orgs"]
 tags: ["GS1","KERI","Digital Link","Enterprise","Barcode","RFID","Global Standards Management Process","Supply Chain","Healthcare","Digital Signatures"]
 permalink: web-standards/gs1/
 redirect_from:

_posts/web-standards/2020-11-27-schema-org.md

@@ -8,7 +8,7 @@ permalink: web-standards/w3c/schema-org/
 redirect_from:
   - web-standards/w3c/cg/schema-org/
 tags: ["Schema.org","W3C","JSON-LD","RDF","Microsoft"]
-categories: ["Web Standards"]
+categories: ["Related Standards"]
 header:
   image: /images/schema-header.webp
   teaser: /images/schema-teaser.webp

_posts/web-standards/2023-05-15-credentials-community-group.md

@@ -5,7 +5,7 @@ excerpt: >
     explore the creation, storage, presentation, verification, and user control of credentials. We focus on a verifiable credential (a set of claims) created by an issuer about a subject—a person, group, or thing—and seek solutions inclusive of approaches such as: self-sovereign identity; presentation of proofs by the bearer; data minimization; and centralized, federated, and decentralized registry and identity systems. 
 permalink: /web-standards/sdo/w3c/credentials-community-group/
 canonical_url: "https://decentralized-id.com/web-standards/w3c/credentials-community-group/"
-categories: ["Web Standards","Organizations"]
+categories: ["Standards Development Orgs"]
 tags: ["Credentials Community Group","Verifiable Credentials","Decentralized Identifiers","W3C","ECDSA Cryptosuite v2019","ECDSA Cryptosuite v2020","JWS","Tracability","Standards Development Org"]
 last_modified_at: 2023-07-03
 ---

_posts/web-standards/2023-06-03-exchange-protocol.md

@@ -8,7 +8,7 @@ excerpt: >
   data model and HTTP protocols to issue, verify, present, and manage data used in such an ecosystem. 
 permalink: web-standards/exchange-protocol/
 canonical_url: https://decentralized-id.com/web-standards/exchange-protocol/
-categories: ["Web Standards"]
+categories: ["Related Standards"]
 tags: ["CHAPI","VC Api","WACI","Credentials Community Group","TrustBloc","DIF","Bloom","hyperledger foundation","Human Colossus Foundation"]
 last_modified_at: 2023-06-03
 ---

_posts/web-standards/2023-06-03-mdl.md

@@ -8,7 +8,7 @@ excerpt: >
   This document establishes interface specifications for the implementation of a driving licence in association with a mobile device. This document specifies the interface between the mDL and mDL reader and the interface between the mDL reader and the issuing authority infrastructure.
 permalink: web-standards/mobile-drivers-license-mdl-iso-18013/
 canonical_url: https://decentralized-id.com/web-standards/mobile-drivers-license-mdl-iso-18013/
-categories: ["Web Standards"]
+categories: ["Related Standards"]
 tags: ["mDL","iso-18013","SpruceID","MATTR","Digital Bazaar","INATBA","Procivis","AAMVA","Kantara Initiative","IETF"]
 last_modified_at: 2023-06-03
 ---

_posts/web-standards/2023-06-03-openid-connect.md

@@ -1,12 +1,12 @@
 ---
 title: OpenID Connect - OpenID Foundation
 name: OpenID Connect
-headings: ["Main","About","Organization","Working Group","Verifiable Credentials","Development"]
+headings: ["Main","About","Organization","Working Group","Verifiable Credentials","Technology"]
 layout: standards
 description: authentication built on top of OAuth 2.0 and the use of Claims to communicate information about the End-User
 excerpt: >
   OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol. It enables Clients to verify the identity of the End-User based on the authentication performed by an Authorization Server, as well as to obtain basic profile information about the End-User in an interoperable and REST-like manner.
-categories: ["Web Standards"]
+categories: ["Related Standards"]
 tags: ["OpenID","OpenID Connect","Ubisecure","Identiverse","OpenID Japan","DIF","Sphereon","Auth0","SpruceID","IETF"]
 permalink: /web-standards/openid/openid-connect/
 redirect_from:  /web-standards/openid-connect/

_posts/web-standards/DIDs-and-VCs/2020-01-10-decentralized-identifier-did.md

@@ -6,7 +6,7 @@ headings: ["Main","Explainer","Literature","Supporting","Critique"]
 description: Decentralized identifiers (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity. 
 excerpt: >
   A DID identifies any subject (e.g., a person, organization, thing, data model, abstract entity, etc.) that the controller of the DID decides that it identifies. In contrast to typical, federated identifiers, DIDs have been designed so that they may be decoupled from centralized registries, identity providers, and certificate authorities. Specifically, while other parties might be used to help enable the discovery of information related to a DID, the design enables the controller of a DID to prove control over it without requiring permission from any other party. DIDs are URIs that associate a DID subject with a DID document allowing trustable interactions associated with that subject.
-categories: ["Web Standards"]
+categories: ["Verifiable Credentials and Decentralized Identifiers"]
 tags: ["Credentials Community Group","Decentralized Identifiers","DIDWG","DIF","Evernym","FIMSA","ID2020","IETF","IIW","NIST","RWoT","SRI International","W3C"]
 permalink: /web-standards/w3c/decentralized-identifier/
 canonical_url: https://decentralized-id.com/web-standards/decentralized-identifier/

_posts/web-standards/DIDs-and-VCs/2020-01-10-verifiable-credentials.md

@@ -7,7 +7,7 @@ description: a standard way to express credentials on the Web in a way that is c
 excerpt: >
   Verifiable credentials (VCs) are the electronic equivalent of the physical credentials that we all possess today, such as: plastic cards, passports, driving licenses, 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.
 tags: ["W3C","Verifiable Credentials","Credentials Community Group","VC-WG","JSON-LD","Claims and Credentials WG"]
-categories: ["Web Standards"]
+categories: ["Verifiable Credentials and Decentralized Identifiers"]
 permalink: web-standards/w3c/verifiable-credentials/
 header:
   image: /images/verifiable-credentials_head.webp

_posts/web-standards/DIDs-and-VCs/2023-06-12-anoncreds.md

@@ -4,7 +4,7 @@ description: Anoncreds has been modularized from the Hyperledger Indy blockchain
 excerpt: > 
   Hyperledger AnonCreds – short for “Anonymous Credentials”- is the most commonly used Verifiable Credential (VC) format in the world. Ledger agnostic and with a formal open specification, AnonCreds is a VC format that adds important privacy-protecting ZKP (zero-knowledge proof) capabilities to the core VC assurances.
 layout: single
-categories: ["Open Source Projects"]
+categories: ["Verifiable Credentials and Decentralized Identifiers"]
 tags: ["Hyperledger Foundation","IBM","IDEMIX","Anoncreds","Sovrin Foundation","Evernym"]
 permalink: /projects/hyperledger/anoncreds/
 canonical_url: 'https://decentralized-id.com/projects/hyperledger/anoncreds/'

_posts/web-standards/DIDs-and-VCs/2023-08-18-DID-Methods.md

@@ -8,7 +8,7 @@ excerpt: >
   DID methods are the magic ingredient that gives DIDs their flexibility. Before creating any specific DID, you first choose a DID method, which determines how you perform the create, read, update, and deactivate operations on a DID of that method.
 
   Once created, each DID includes the name of its method in the identifier itself, so that when you use the DID, others know how to retrieve the associated DID Document that contains the cryptographic material for secure interactions.
-categories: ["Web Standards"]
+categories: ["Verifiable Credentials and Decentralized Identifiers"]
 tags: ["51nodes","ABT Network","Aergo","Alastria","ArcBlock","Ardor","Baidu","BCGov","Besu","BIF","BiiLabs","Binance","Bitcoin","BlockchainCommons","Blockcore","Blocko","Blockstack","BOTLabs","bryk","BSC","Teleinfo CAICT","Celo","Ceramic Network","Chainyard","Cloudchain","Commercio","Consensys","Consent","Corda","Cosmos","Credentials Community Group","cryptonics","DID:AERGO","DID:ALA","DID:AVVCYBER","DID:BBA","DID:BID","DID:BNB","DID:BRYK","DID:BTCR","DID:CCP","DID:CELO","DID:COM","DID:CORDA","DID:DID","DID:DOCK","DID:DOGE","DID:ECHO","DID:ELASTOS","DID:ELEM","DID:EMTRUST","DID:EOS","DID:ERC725","DID:ETHO","DID:ETHR","DID:EVAN","DID:FACTOM","DID:GATC","DID:GIT","DID:GITHUB","DID:GRG","DID:HEDERA","DID:HOLO","DID:ICON","DID:INDY","DID:IO","DID:ION","DID:IPID","DID:IS","DID:IWT","DID:JLINC","DID:JNCTN","DID:JOLO","DID:JWK","DID:KEY","DID:KILT","DID:KLAY","DID:LIFE","DID:META","DID:MOAC","DID:MORPHEUS","DID:NEAR","DID:NFT","DID:OBJECT","DID:OCKAM","DID:OMN","DID:ONION","DID:ONT","DID:OP","DID:ORB","DID:PANACEA","DID:PEER","DID:PISTIS","DID:PKH","DID:PTN","DID:SAN","DID:SCHEMA","DID:SELFKEY","DID:SIGNOR","DID:SIRIUS","DID:SOV","DID:STACK","DID:TAG","DID:TANGLE","DID:TRUSTBLOC","DID:TRX","DID:TTM","DID:TWIT","DID:TYRON","DID:TYS","DID:TZ","DID:UNDID","DID:UNISOT","DID:UNS","DID:V1","DID:VAA","DID:VAULTIE","DID:VID","DID:VVO","DID:WEB","DID:WLK","DID:WORK","Decentralized Identifiers","Digital Bazaar","Dock","Echo","Elastos","Element","Email","EOS","ERC725","Ethereum","Evan Network","Evernym","Fabric","Factom","Gatica","Github","GRGBanking","GrgChain","Halialabs","Hashgraph","Holochain","Hydra","Hyland Credentials","hyperledger foundation","IBM","ICONLOOP","IIW","Indy","InfoWallet","ION","IOP","IOTA","IoTeX","IPFS","JLinc","Jnctn","Jolocom","JWK","KILT","Klaytn","lifeID","MediBloc","Metadium","Microsoft","MOAC","NEAR","Ocean Protocol","Ockam","OmniOne","Ontology","Panacea","ProximaX","Quorum","Raonsecure","RChain","RWoT","SecureKey","SelfKey Identity","SelfKey","Sovrin Foundation","Sovrin","SpaceElephant","Sphereon","SpruceID","Swisscom","TIFAC-CORE","TMChain","Token.TM","TOR","TranSendX","Transmute","TRON","Twitter","UNISOT","UNS","uPort","Vaultie","VeramoLabs","Veres One","Vivvo","VP","W3C","Weelink","Workday","YLZ Inc","Zilliqa"]
 permalink: /web-standards/w3c/decentralized-identifier/did-methods/
 canonical_url: https://decentralized-id.com/web-standards/w3c/decentralized-identifier/did-methods/

_posts/web-standards/DIDs-and-VCs/2023-08-29-VCs-Standards-and-Development.md

@@ -2,12 +2,12 @@
 title: "Verifiable Credentials - Working Groups, Standards and Development"
 name: VCs Development
 layout: standards
-headings: ["Verifiable Credentials Working Group","Credentials Community Group","Claims and Credentials Working Group","Varieties","Development","User Experience"]
+headings: ["Verifiable Credentials Working Group","Credentials Community Group","Claims and Credentials Working Group","Varieties","Technology","User Experience"]
 description: a standard way to express credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.
 excerpt: >
   Verifiable credentials (VCs) are the electronic equivalent of the physical credentials that we all possess today, such as: plastic cards, passports, driving licenses, 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.
 tags: ["W3C","Verifiable Credentials","Credentials Community Group","VC-WG","JSON-LD","OAuth","FIDO","Claims and Credentials WG"]
-categories: ["Web Standards","Development"]
+categories: ["Verifiable Credentials and Decentralized Identifiers"]
 permalink: web-standards/w3c/verifiable-credentials/standards-and-development/
 header:
   image:

_posts/web3/2020-11-11-ontology.md

@@ -0,0 +1,76 @@
+---
+date: 2020-11-11
+title: Ontology
+description: "'Distributed Trust Network' which combines a cross-chain identity system, peer-to-peer data transmission, data authorization mechanisms, distributed data storage, attestation, and various industry-specific modules."
+excerpt: >
+  Ontology is a high performance, open source blockchain specializing in digital identity and data. Ontology's unique infrastructure supports robust cross-chain collaboration and Layer 2 scalability, offering businesses the flexibility to design a blockchain that suits their needs. With a suite of decentralized identity and data sharing protocols to enhance speed, security, and trust, Ontology’s features include ONT ID, a mobile digital ID application and DID used throughout the ecosystem, and DDXF, a decentralized data exchange, and collaboration framework.
+layout: single
+permalink: blockchain/ontology/
+canonical_url: 'https://decentralized-id.com/blockchain/ontology/'
+categories: ["Web 3"]
+tags: ["Web3","Ontology","Ethereum","NEO","Polkadot","Microsoft","Consensys","Universal Resolver","Compliance"]
+header:
+  image: /images/ontology_header.webp
+  teaser: /images/ontology_teaser.webp
+last_modified_at: 2020-11-11
+toc: true
+---
+
+## Main
+
+**[Website](https://ont.io/) • [Onto.App](https://onto.app) • [Blog](https://medium.com/ontologynetwork) • [GitHub](https://github.com/ontio/) • [Telegram](https://t.me/OntologyNetwork) • [Twitter](https://twitter.com/OntologyNetwork) • [Youtube](https://www.youtube.com/channel/UCXzLZJgDglAWRU0b2GOa7pA) • [Linkedin](https://www.linkedin.com/company/ontology-network-official/) • [Discord](https://discordapp.com/invite/pQRHtbD)**
+
+A "Distributed Trust Network" which combines a cross-chain identity system, peer-to-peer data transmission, data authorization mechanisms, distributed data storage, attestation, and various industry-specific modules. It also includes an Ontology Crypto Package (OCP) and an Ontology Marketplace (OM).
+
+* [Ontology is Now Officially a Technical Provider for Enterprise Solutions through Cointelegraph](https://medium.com/ontologynetwork/ontology-is-now-officially-a-technical-provider-for-enterprise-solutions-through-cointelegraph-80db38c45489)
+  > [With over 5 million unique visitors each month and over 17 million page views](https://cointelegraph.com/advertise), Cointelegraph has rapidly established itself as one of the media anchors in the blockchain space. But the readers it attracts aren’t merely traders, enthusiasts, or bitcoin fiends — rather, Cointelegraph has quietly established itself as a legitimate mediator between established enterprises and blockchain technology providers. As a result, a [consulting arm](https://cointelegraph.com/consulting) was launched that aims to “connect the world between blockchain and traditional institutions of all sizes by bringing wider adoption of digital assets and enterprise-grade blockchain solutions through education and professional consulting services.”
+* [White Paper] [Ontology Trust Framework](https://ont.io/wp/Ontology-Trust-Framework-White-Paper-EN-2.0.0.pdf) 2019/07 V2.0
+  > Through history, people have established trust from different dimensions and methods, for instances, via technology, legal system and communities etc. However, multi-source, multi-system and multi-method single-point trust collaboration will incur very high collaboration costs, hindering the depth and breadth of trust collaboration. Although internet technology changes rapidly, but the pain points of trust still exist today, such as trusted source decentralization, data fragmentation, lack of individual roles, identity verification and difficulty in identifying false information. During the collaboration process of society governance, economic collaboration, and financial service, there is a large amount of cost incurred by “trust” every day.
+
+## OntID
+
+* [OntID](https://ontid.ont.io/) - [Docs](https://docs.ont.io/)
+  > ONT ID is a decentralized identity framework based on the W3C recommendations for decentralized identifiers and verifiable credentials, using blockchain and cryptographic technology, that can quickly identify and connect people, data, and services. It is decentralized, self-sovereign, privacy-preserving, and easy to use, enabling users to fully control their own data and identities.
+* [Docs] [Ontology's decentralized identity framework](https://docs.ont.io/v/v2.2/ontology-elements/ontid) 2020-04-03 Ontology
+  > Ontology establishes a decentralized trust model and a distributed trust delivery system through ONT ID and a mechanism that uses verifiable claims. It uses the zero-knowledge proof protocol to assure the privacy protection of verifiable claims. Through ONT ID, Ontology will also incorporate various authentication service agencies, and establish multi-source authentication to achieve a more complete picture of the respective entity's identity.
+* [Enter Web 3.0 with ONT ID](https://ont.io/news/748) 
+  > The world is becoming increasingly digitized, with Web 3.0 right around the corner. With more and more of our lives being spent online, it is essential to develop a reliable and trustless way to verify who we are. Blockchain has equipped us with the technology needed to not only authenticate identities on-chain, but to do so in a way that protects user privacy. ONT ID is Ontology’s decentralized identity solution, designed to be both trustless and private, empowering users. This article outlines ONT ID’s key features, along with its complementary services, ONT Login and ONT TAG.
+* [Explainer] [Verifiable Credentials](https://docs.ont.io/decentralized-identity-and-data/ontid/trust-mechanism)
+  > ![](https://i.imgur.com/Lk2d9fS.png)
+* [Explainer] [Anonymous Credentials](https://docs.ont.io/decentralized-identity-and-data/ontid/trust-mechanism/anonymous-credentials) Ontology
+  > The anonymous credential scheme is a part of the Ontology Crypto library that provides several cryptography related utilities for the Ontology network. The main features provided by the crypto library basically revolve around digital signature. It provides general APIs for processing digital signatures and keys. 
+* [did:etho Method Specification for Ethereum](https://docs.ont.io/decentralized-identity-and-data/ontid/decentralized-identifiers/method-specification) 2021 Ontology
+  > Decentralized identifiers (DIDs) are a new type of identifiers that enables verifiable, self-sovereign digital identity. This ETHO DID method specification describes a new DID method, that is, ETHO DID and defines how Ethereum blockchain stores ETHO DIDs and their corresponding DID documents, and how to do CRUD operations on ETHO DID documents.
+* [did:bnb Method Specification for BSC](https://docs.ont.io/decentralized-identity-and-data/ontid/decentralized-identifiers/method-specification-1) 2021 Ontology
+  > Decentralized identifiers (DIDs) are a new type of identifiers that enables verifiable, self-sovereign digital identity. This Binance DID method specification describes a new DID method, that is, Binance DID and defines how Binance Smart Chain stores Binance DIDs and their corresponding DID documents, and how to do CRUD operations on Binance DID documents.
+
+
+### Product
+* [Ontology Providing DID Solutions to NFT + Music Streaming Platform, ROCKI](https://medium.com/ontologynetwork/ontology-providing-did-solutions-to-music-streaming-platform-rocki-5ae6c1704483) 2021-05-24 Ontology
+  > NFTs offer creators a novel way to monetize their creations. Unfortunately, there have been reports of artists having their artwork sold by impersonators. This is, in part, due to popular NFT platforms lacking a robust verification process for determining a creator’s identity.
+  > 
+  > The potential for fraud in the growing NFT market recently attracted the attention of the Financial Action Task Force (FATF)
+* [Ontology Partnership with Binance Smart Chain](https://medium.com/ontologynetwork/ontology-the-only-decentralized-identity-partner-for-binance-smart-chain-d531efbc569) 2021-02-20
+    Ontology and Binance have a long history of cooperation and partnership that has generated benefits for both sides, none possibly more important the integration of Ontology’s Decentralized Identity Solution into the Binance Smart Chain. The symbiotic relationship sees Ontology, and ONT ID, as the sole partner for BSC in terms of providing a truly decentralized identity option and KYC user verification.
+* [Ontology Builds on Polkadot to Accelerate Adoption Of Decentralized Identity Solution](https://medium.com/ontologynetwork/ontology-builds-on-polkadot-to-accelerate-adoption-of-decentralized-identity-solution-acf7b8357ee) 2020-10-03 Ontology Network
+  > Developed over the past couple of months, the Ontology [parachain](https://github.com/siovanus/DID-substrate) currently consists of a DID Substrate pallet, with plans for further integration of other custom components. Further plans for the Ontology parachain include:
+  >
+  > Ontology OScore — an off-chain DID authorization mechanism to manage wallet-identity relationships and provide ID-based credit scores for on-chain actions related to digital assets. The integration of Ontology’s distributed data exchange framework (DDXF), permitting both token association and data tokenization. Expanding DID’s use cases from users to also include data and resources, providing authentication, authorization, and accounting (AAA) for DID based resource instances via on-chain data access control with data-tokens (tokenization), and association of its value. DDXF provides on-chain AAA for data interoperability cross systems.
+* [Ontology Boosts Security And Compliance Through Integration With Chainalysis](https://medium.com/ontologynetwork/ontology-boosts-security-and-compliance-through-integration-with-chainalysis-3dfce3c154ec) 2020-10-20 Ontology Network
+  > [Ontology](https://ont.io/), the high performance, open-source blockchain specializing in digital identity and data, has announced today an integration with [Chainalysis](https://www.chainalysis.com/), the blockchain analysis company.
+  > 
+  > Ontology will utilize Chainalysis’s compliance and investigative solutions, KYT (Know Your Transaction) and Reactor, to enhance trust, provide a safer experience to traders, and combat illicit activity through transaction monitoring and tracing.
+* [Lower Your Collateral Requirements & Loan Interests with OScore](https://medium.com/ontologynetwork/lower-your-collateral-requirements-loan-interests-with-oscore-fb2c835a9998) 2020-10-19 Ontology network
+  > [OScore](https://ocredit.io/), the first credit score for the decentralized world built with Ontology’s Decentralized Identity has officially launched. For simplicity, consider OScore an on-chain reputational system that supports cross-chain interaction with verifiable credentials on the Ontology blockchain, hence eliminating third-party verification programs from the process. Once a user authorizes their digital financial data, Ontology’s OScore system automatically generates a quantifiable credit score while ensuring a user’s privacy is fully protected and controlled by themselves.
+
+### Identity Repos
+* [ontology-DID](https://github.com/ontio/ontology-DID) 2020-04-08 Ontology decentralized identification protocol based on W3C DID specifications.
+  > Ontology DID(Also: ONT ID) is a decentralized identification protocol which based on W3C DID specifications.It supports collaborative services such as distributed and diversified ownership confirmation, identification, and authentication of various entities including individuals, legal entities, objects, and contents. ONT ID establishes a cryptographically-based digital identity for each entity, allowing self-sovereign of data authorization and ownership confirmation, which makes the identity and data truly assets that the user can control. ONT ID has the characteristics of decentralization, self-management, privacy protection, security and ease of use.
+* [Mercury](https://github.com/ont-id/mercury) - [Docs](https://docs.ont.io/decentralized-identity-and-data/ontid/mercury)
+  > Mercury is a trustless, peer to peer decentralized communication protocol that makes entities be able to securely transmit messages, verifiable credentials, and verifiable presentations with each other.
+* [ontology-ddxf](https://github.com/ontio/ontology-ddxf) - Distributed data eXchange Framework,which allows to build data marketplaces.
+  > The downsides of centralized data exchange include data caching, use of data without user authorization and data copyright protection. Ontology is proposing a Distributed Data Protocol (ONT Data). Based on the protocol , we have come up with distributed data exchange framework(DDXF) which allows to customize data trading marketplaces with secured data and financial security. With DDXF, the developer of the ontology ecosystem can easily develop decentralized data application that meets the needs of various scenarios with various features.
+* [ontology-eventbus](https://github.com/ontio/ontology-eventbus) - The Go Language Implementation of Ontology Actor Model
+  > Actor is a model of parallel computation model in computer science that treats "actors" as the the universal primitives of concurrent computation. In response to a message that it receives, an actor can make local decisions: make local decisions, create more actor, send more messages, and determine how to respond to the next message received.
+* [ontid-driver](https://github.com/ontio/ontid-driver) - ONT ID driver for universal resolver
+

_sass/minimal-mistakes/_variables.scss

@@ -105,7 +105,7 @@ $xing-color: #006567 !default;
 /* links */
 $link-color: mix(#000, $info-color, 50%) !default;
 $link-color-hover: mix(#000, $link-color, 75%) !default;
-$link-color-visited: mix(#fff, $link-color, 40%) !default;
+$link-color-visited: mix(#fff, $link-color, 25%) !default;
 $masthead-link-color: $primary-color !default;
 $masthead-link-color-hover: mix(#000, $primary-color, 25%) !default;
 $navicon-link-color-hover: mix(#fff, $primary-color, 75%) !default;

requirements.txt

@@ -1,2 +0,0 @@
-tweepy
-webpreview

staticman.yml

@@ -1,28 +0,0 @@
-# To encrypt strings use the following endpoint:
-# https://api.staticman.net/v2/encrypt/{TEXT TO BE ENCRYPTED}
-
-comments:
-  allowedFields: ["name", "email", "message"]
-  allowedOrigins: ["decentralized-id.com"]
-  branch: "master"
-  commitMessage: "New comment by {fields.name}"
-  filename: "comment-{@timestamp}"
-  format: "yaml"
-  generatedFields:
-    date:
-      type: "date"
-      options:
-        format: "iso8601" # "iso8601" (default), "timestamp-seconds", "timestamp-milliseconds"
-  moderation: true
-  akismet:
-    enabled: true  
-  name: "Decentralized-id.com"
-  path: "_data/comments/{options.slug}" # "_data/comments/{options.slug}" (default)
-  requiredFields: ["name", "email", "message"]
-  transforms:
-    email: md5
-  # Register your domain at https://www.google.com/recaptcha/ and choose reCAPTCHA V2
-  reCaptcha:
-    enabled: true
-    siteKey: 6LfHeawUAAAAAATc0Sckhl9FJLGog3m7qLrYA8V0
-    secret: jG+tpXA7GdYSuIT/rcr5pyy9GG/ZP6808NE8SS+/ggGZ0Si0/uelJpZuElRrIITjfB7YjW6+MyWEBM/q/BFWQqRfkpCZ0RK5AETrx/awrvKSlCVCQfpN20MFpu54yFgkyj82umuoxOyiVczwUnkD8Sav0cXESbllHgC+2J2hw6nOYQ+ZnOFL4J4m3yoABhyGpKnhzw7enmaAm+pbxPXyLhjj9+LiRqGLWNUYOt+yOuo/i1aeE8p0lYwdESVoetkuNfKf1Q13Vs/KSPGceVXWLJAf7mDlwCf8wGrAZzCGAd9GQJM3KjliB+0hGOWs9X01+PdUr6ZeeGrAFjBERZXpTPdJmHDBmUNnX5Tdvhq9uU4I3NcZveIg5FyjLe4nMG30ha/hALW4KLvspzCL8nYWpFl27RTqN6v735xcBgcfVR4JPfInb91/EtAFe3gyM3BCe3enuiezGDZsqCn+glQZ7adeOrCaZ0pLG+FmL7WXR2QsSfq70biUp6uLZtGfJ4W9I9DIezbj3Z/ltJRFVTmWHGp3g4/2LAcsDLMfyR4QLVkcgqQjuAbYk3ItPNuLPAVV6mbHKvBmyoyimT1SpPWgu6uJCRkCyU90DMsBK/xNzhep9ljp73qV2B3qHvFqHIKKzYEoA2rtQexTsRWxf+20axauwWO/DdpcOqOQC8mUqBE=

twscraper.py

@@ -1,248 +0,0 @@
-# -*- coding: utf-8 -*-
-
-import tweepy
-import csv
-import os
-
-#### Credentials
-
-consumer_key = os.environ.get('CONSUMER_KEY')
-consumer_secret = os.environ.get('CONSUMER_SECRET')
-access_token = os.environ.get('ACCESS_KEY')
-access_token_secret = os.environ.get('ACCESS_SECRET')
-
-#### Authorization
-auth = tweepy.OAuthHandler(consumer_key, consumer_secret)
-auth.set_access_token(access_token, access_token_secret)
-api = tweepy.API(auth,wait_on_rate_limit=True)
-
-#### Keywords
-keywords = ["#verifiablecredentials","#selfsovereignidentity","Self+Sovereign+Identity","Hyperledger+Aries","DIDComm","Key+Event+Receipt+Infrastructure","#ToIP","#TrustoverIP","w3c+Credentials"]
-
-#### Get Date
-from datetime import date, timedelta, datetime
-
-#### Find 7 Days Ago
-current_date = date.today()   
-days_before = (date.today()-timedelta(days=7))
-now = datetime.now()
-date_time = current_date.strftime("%Y-%m-%d")
-startDate = days_before.strftime("%Y-%m-%d, %H:%M:%S")
-
-
-#### Open CSV + Write Column Names
-fname = '_data/twitter/search_' + date_time + '.csv'
-csvFile = open(fname, 'w+')
-csvWriter = csv.writer(csvFile)
-csvWriter.writerow(["Time","Link", "Urls", "UrlTitle", "UrlDesc", "UrlImg", "ImageUrls", "ReplyURL", "QuoteID", "QuoteImg", "QuoteUrl"])
-lines_seen = []
-text_seen = []
-tweet_ids = []
-
-for keyword in keywords:
-    # Search hashtags\keywords
-    for tweet in tweepy.Cursor(api.search,q=keyword + ' -filter:retweets', count=100, tweet_mode="extended", lang="en", since=days_before).items():
-        ### Reset Variables
-        medias = []
-        lnks = []
-        replink = ""
-        title = []
-        description = []
-        image = []
-        qtid = ''
-        qttext = ''
-        qtmedia = ['']
-        qturls = ['']
-        seen = 'FALSE'
-
-        ### Set basic tweet attributes
-        username = tweet.user.screen_name
-        id = "https://twitter.com/" + username + "/status/" + tweet.id_str
-        idstr = tweet.id_str
-        text = tweet.full_text
-        created = str(tweet.created_at)
-
-        #### Only add line to csv if it's not already been added
-        if hasattr(tweet, 'quoted_status'):
-            quotedid = 'https://twitter.com/' + tweet.quoted_status.user.screen_name + '/status/' + tweet.quoted_status_id_str
-            if quotedid in lines_seen:
-                seen = 'TRUE'
-        for y in lines_seen:
-            if id == y:
-                seen = 'TRUE'
-        for q in text_seen:
-            if text == q:
-                seen = 'TRUE'
-        if seen == 'TRUE': continue
-        else:
-            ### Keep track of seen lines \ tweets
-            lines_seen.append(id)
-            text_seen.append(text)
-            ### Check for reply id
-            try:
-                reply = tweet.in_reply_to_status_id_str
-                user = tweet.in_reply_to_user_id_str
-                replink = "https://twitter.com/" + user + "/" + reply
-            except:
-                pass
-            ### Check for images in tweet
-            if 'media' in tweet.entities:
-                for media in tweet.extended_entities['media']:
-                    medias.append(media['media_url_https'])
-            ### Check for urls in tweet
-            if 'urls' in tweet.entities:
-                for url in tweet.entities['urls']:
-                    lkn = url['expanded_url']
-                    lnks.append(url['expanded_url'])
-                    ### Look for metadata
-                    from webpreview import web_preview
-                    ### Unless link is an image pdf twitter or insta
-                    if 'twitter.com' in lkn or '.png' in lkn or '.jpg' in lkn or '.pdf' in lkn or 'instagram.com' in lkn or 'linkedin.com' in lkn or 'facebook.com' in lkn: pass
-                    else:
-                        try:
-                        ### get title img description
-                            print('>>Getting Link Metadata<<')
-                            headers = {'User-Agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36'}
-                            tit, desc, ima = web_preview(lkn,timeout=10,headers=headers,parser='lxml')
-                            title.append(tit)
-                            description.append(desc)
-                            image.append(ima) 
-                        except:
-                            pass
-                ### If it's a quote-tweet, get original stats
-            if hasattr(tweet, 'quoted_status'):
-                qtmedia = ['']
-                qturls = ['']
-                qttext = tweet.quoted_status.full_text
-                qtuser = tweet.quoted_status.user.screen_name
-                qtid = "https://twitter.com/" + qtuser + "/status/" + tweet.quoted_status.id_str
-                if 'media' in tweet.quoted_status.entities:
-                    for media in tweet.quoted_status.extended_entities['media']:
-                        qtmedia.append(media['media_url_https'])
-                if 'urls' in tweet.quoted_status.entities:
-                    for url in tweet.quoted_status.entities['urls']:
-                        qturls.append(url['expanded_url'])
-            #### Column attributes
-            line = [created, id, lnks, title, description, image, medias, replink, qtid, qtmedia, qturls]
-
-            #### Write row to CSV and print line
-            csvWriter.writerow(line)
-            tweet_ids.append(idstr)
-            print(idstr)
-
-#### Get USER Tweets
-tweets = []
-ids = []
-tmpTweets = api.user_timeline('DecentralizeID')
-for tweet in tmpTweets:
-    created = tweet.created_at.strftime("%Y-%m-%d, %H:%M:%S")
-    if created < date_time and created > startDate:
-        tweets.append(tweet)
-
-while (tmpTweets[-1].created_at.strftime("%Y-%m-%d, %H:%M:%S") > startDate):
-    print("Last Tweet @", tmpTweets[-1].created_at, " - fetching some more")
-    tmpTweets = api.user_timeline(username, max_id = tmpTweets[-1].id)
-    for tweet in tmpTweets:
-        createdate = tweet.created_at.strftime("%Y-%m-%d, %H:%M:%S")
-        if createdate < date_time and createdate > startdate:
-            tweets.append(tweet)
-
-
-for tweet in tweets:
-    created = str(tweet.created_at)
-    id = "https://twitter.com/" + username + "/status/" + tweet.id_str
-    idstr = str(tweet.id_str)
-    username = tweet.user.screen_name
-    if hasattr(tweet, 'text'):
-        text = tweet.text
-    if hasattr(tweet, 'full_text'):
-        text = tweet.full_text
-    try: 
-        username = tweet.retweeted_status.user.screen_name
-        id = "https://twitter.com/" + tweet.retweeted_status.user.screen_name + "/status/" + tweet.retweeted_status.id_str
-        idstr = tweet.retweeted_status.id_str
-    except:
-        pass
-    if id not in ids:
-        ids.append(id)
-        tweet_ids.append(idstr)
-        line = [created, id, lnks, title, description, image, medias, replink, qtid, qttext, qtmedia, qturls]
-        #### Write row to CSV and print line
-        csvWriter.writerow(line)
-csvFile.close()
-print(tweet_ids)
-
-# Create Collection
-from requests_oauthlib import OAuth1Session
-import json
-## OAuth vs Tweepy auth, idk why can't create collection with above tweepy auth
-consumer_key = os.environ.get('CONSUMER_KEY')
-consumer_secret = os.environ.get('CONSUMER_SECRET')
-access_token = os.environ.get('ACCESS_KEY')
-access_token_secret = os.environ.get('ACCESS_SECRET')
-print(consumer_key)
-print(consumer_secret)
-print(access_token)
-print(access_token_secret)
-twitter = OAuth1Session(consumer_key,
-                        client_secret=consumer_secret,
-                        resource_owner_key=access_token,
-                        resource_owner_secret=access_token_secret)
-
-# create
-url = 'https://api.twitter.com/1.1/collections/create.json'
-params_create = {
-    'name': 'Decentralized-ID Curated ' + date_time,
-    'description': 'Decentralized Identity Curated Tweets by @infominer33 via identosphere.net',
-    'timeline_order': 'tweet_chron'
-    }
-r = twitter.post(url, data=params_create)
-print(r.json())
-print(r.json()['response'])
-# 'response': {'timeline_id': 'custom-1180945428222595074'}}
-## Extract ID from response
-res = str(r.json()['response'])
-ss1 = "{'timeline_id': 'custom-"
-ss2 = "'}"
-resp = res.removeprefix(ss1)
-response = resp.removesuffix(ss2)
-
-timeline_id = r.json()['response']['timeline_id']
-# the collection can be viewed at, eg: https://twitter.com/laurenfratamico/timelines/1180945428222595074
-
-# bulk add
-url = 'https://api.twitter.com/1.1/collections/entries/curate.json'
-# split into batches of 100 for the uploads
-n = 100
-batches = [tweet_ids[i:i + n] for i in range(0, len(tweet_ids), n)]
-print (len(batches))
-
-for batch in batches:
-    params_add = {
-        "id": timeline_id,
-        "changes": []
-    }
-    for tweet_id in batch:
-        sub_params_add = {
-            "tweet_id": str(tweet_id),
-            "op": "add"
-        }
-        params_add['changes'].append(sub_params_add)
-    
-    r = twitter.post(url, data=json.dumps(params_add))
-    print(r.json())
-
-file_name = "_posts/twitter/" + str(date_time) + '-twitter.md'
-f = open(file_name,"w+")
-
-str1 = "---\n"
-str2 = 'title: "Twitter Collection – ' + date_time + '"\n'
-str3 = 'description: "Collection of tweets on decentralized identity – ' + date_time + '"\n'
-str4 = "last_modified_at: " + date_time + '\n'
-str5 = "---\n"
-str6 = "\n\n"
-str7 = '<a class="twitter-timeline" href="https://twitter.com/DecentralizeID/timelines/' + response + '">Decentralized Identity - Curated ' + date_time + '</a> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>'
-
-L = [str1, str2, str3, str4, str5, str6, str7] 
-f.writelines(L)
-f.close()