dh

Bump glob-parent and onchange

.bundle/config

@@ -0,0 +1,2 @@
+---
+BUNDLE_PATH: "vendor/bundle"

.github/workflows/github-pages.yml

@@ -0,0 +1,29 @@
+name: Build and deploy Jekyll site to GitHub Pages
+
+on:
+  push:
+    branches:
+      - master
+    paths-ignore:
+      - '_data/**'
+      - '.github/workflows/twitter.yml'
+
+jobs:
+  jekyll:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+
+    # Use GitHub Actions' cache to shorten build times and decrease load on servers
+    - uses: actions/cache@v2
+      with:
+        path: vendor/bundle
+        key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile') }}
+        restore-keys: |
+          ${{ runner.os }}-gems-
+
+    # Specify the target branch (optional)
+    - uses: helaili/jekyll-action@v2
+      with:
+        token: ${{ secrets.GITHUB_TOKEN }}
+        target_branch: 'gh-pages'

.github/workflows/twitter.yml

@@ -0,0 +1,45 @@
+# This is a basic workflow to help you get started with Actions
+name: twitter collections
+
+# Controls when the action will run. Triggers the workflow on push or pull request
+# events but only for the master branch
+on:
+  schedule:
+    - cron: '0 18 * * 6'
+  push:
+    paths:
+    - 'twscraper.py'
+    - '.github/workflows/twitter.yml'
+
+# A workflow run is made up of one or more jobs that can run sequentially or in parallel
+jobs:
+  # This workflow contains a single job called "build"
+  build:
+    # The type of runner that the job will run on
+    runs-on: ubuntu-latest
+
+    # Steps represent a sequence of tasks that will be executed as part of the job
+    steps:
+      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
+      - uses: actions/checkout@v2
+      - uses: actions/setup-python@v2
+        with:
+          python-version: '3.9.0' # Version range or exact version of a Python version to use, using SemVer's version range syntax
+      - uses: py-actions/py-dependency-install@v2   
+        with:
+          path: requirements.txt
+      - shell: bash
+        env: # Or as an environment variable
+          CONSUMER_KEY: ${{ secrets.CONSUMER_KEY }}
+          CONSUMER_SECRET: ${{ secrets.CONSUMER_SECRET }}
+          ACCESS_KEY: ${{ secrets.ACCESS_KEY }}
+          ACCESS_SECRET: ${{ secrets.ACCESS_SECRET }}
+        run: python twscraper.py
+      - name: Deploy Changes
+        run: |
+          git remote add gh-token "https://github.com/decentralized-id/decentralized-id.github.io.git"
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+          git pull
+          git commit -a -m "add twitter collection"
+          git push gh-token master

.gitignore

@@ -0,0 +1,18 @@
+Gemfile.tmp
+Gemfile.lock.tmp
+Rakefile
+_config.bak
+_site/
+_algolia_api_key
+.DS_Store
+.ruby-version
+twscrapter.py
+_posts/companies/2020-12-17-arcblock.md
+_posts/companies/2020-12-20-authentech.md
+_posts/companies/2020-12-30-bloom.md
+_posts/companies/2020-12-31-blockpass.md
+_posts/organizations/2020-12-30-ixo-foundation.md
+_posts/blockchain/2020-12-22-polkadot.md
+_posts/blockchain/2020-12-30-ocean-protocol.md
+_posts/blockchain/ethereum/2020-12-12-lab10-collective.md
+vendor

CNAME

@@ -0,0 +1 @@
+decentralized-id.com

Gemfile

@@ -0,0 +1,36 @@
+source "https://rubygems.org"
+
+# Hello! This is where you manage which Jekyll version is used to run.
+# When you want to use a different version, change it below, save the
+# file and run `bundle install`. Run Jekyll with `bundle exec`, like so:
+#
+#     bundle exec jekyll serve
+#
+# This will help ensure the proper Jekyll version is running.
+# Happy Jekylling!
+
+gem "github-pages", group: :jekyll_plugins
+
+# To upgrade, run `bundle update`.
+
+# gem "jekyll"
+# gem "minimal-mistakes-jekyll"
+
+# The following plugins are automatically loaded by the theme-gem:
+#   gem "jekyll-paginate"
+#   gem "jekyll-sitemap"
+#   gem "jekyll-gist"
+#   gem "jekyll-feed"
+#   gem "jemoji"
+#   gem "jekyll-data"
+#
+# If you have any other plugins, put them here!
+group :jekyll_plugins do
+  gem "jekyll-include-cache"
+  gem "jekyll-redirect-from"
+  gem "jekyll-mentions"
+  gem 'jekyll-gist'
+  gem 'webrick'
+end
+
+gem "faraday-retry", "~> 2.1"

Gemfile.lock

@@ -0,0 +1,269 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    activesupport (7.0.8)
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      i18n (>= 1.6, < 2)
+      minitest (>= 5.1)
+      tzinfo (~> 2.0)
+    addressable (2.8.5)
+      public_suffix (>= 2.0.2, < 6.0)
+    base64 (0.1.1)
+    coffee-script (2.4.1)
+      coffee-script-source
+      execjs
+    coffee-script-source (1.11.1)
+    colorator (1.1.0)
+    commonmarker (0.23.10)
+    concurrent-ruby (1.2.2)
+    dnsruby (1.70.0)
+      simpleidn (~> 0.2.1)
+    em-websocket (0.5.3)
+      eventmachine (>= 0.12.9)
+      http_parser.rb (~> 0)
+    ethon (0.16.0)
+      ffi (>= 1.15.0)
+    eventmachine (1.2.7)
+    execjs (2.9.1)
+    faraday (2.7.11)
+      base64
+      faraday-net_http (>= 2.0, < 3.1)
+      ruby2_keywords (>= 0.0.4)
+    faraday-net_http (3.0.2)
+    faraday-retry (2.2.0)
+      faraday (~> 2.0)
+    ffi (1.16.2)
+    forwardable-extended (2.6.0)
+    gemoji (3.0.1)
+    github-pages (228)
+      github-pages-health-check (= 1.17.9)
+      jekyll (= 3.9.3)
+      jekyll-avatar (= 0.7.0)
+      jekyll-coffeescript (= 1.1.1)
+      jekyll-commonmark-ghpages (= 0.4.0)
+      jekyll-default-layout (= 0.1.4)
+      jekyll-feed (= 0.15.1)
+      jekyll-gist (= 1.5.0)
+      jekyll-github-metadata (= 2.13.0)
+      jekyll-include-cache (= 0.2.1)
+      jekyll-mentions (= 1.6.0)
+      jekyll-optional-front-matter (= 0.3.2)
+      jekyll-paginate (= 1.1.0)
+      jekyll-readme-index (= 0.3.0)
+      jekyll-redirect-from (= 0.16.0)
+      jekyll-relative-links (= 0.6.1)
+      jekyll-remote-theme (= 0.4.3)
+      jekyll-sass-converter (= 1.5.2)
+      jekyll-seo-tag (= 2.8.0)
+      jekyll-sitemap (= 1.4.0)
+      jekyll-swiss (= 1.0.0)
+      jekyll-theme-architect (= 0.2.0)
+      jekyll-theme-cayman (= 0.2.0)
+      jekyll-theme-dinky (= 0.2.0)
+      jekyll-theme-hacker (= 0.2.0)
+      jekyll-theme-leap-day (= 0.2.0)
+      jekyll-theme-merlot (= 0.2.0)
+      jekyll-theme-midnight (= 0.2.0)
+      jekyll-theme-minimal (= 0.2.0)
+      jekyll-theme-modernist (= 0.2.0)
+      jekyll-theme-primer (= 0.6.0)
+      jekyll-theme-slate (= 0.2.0)
+      jekyll-theme-tactile (= 0.2.0)
+      jekyll-theme-time-machine (= 0.2.0)
+      jekyll-titles-from-headings (= 0.5.3)
+      jemoji (= 0.12.0)
+      kramdown (= 2.3.2)
+      kramdown-parser-gfm (= 1.1.0)
+      liquid (= 4.0.4)
+      mercenary (~> 0.3)
+      minima (= 2.5.1)
+      nokogiri (>= 1.13.6, < 2.0)
+      rouge (= 3.26.0)
+      terminal-table (~> 1.4)
+    github-pages-health-check (1.17.9)
+      addressable (~> 2.3)
+      dnsruby (~> 1.60)
+      octokit (~> 4.0)
+      public_suffix (>= 3.0, < 5.0)
+      typhoeus (~> 1.3)
+    html-pipeline (2.14.3)
+      activesupport (>= 2)
+      nokogiri (>= 1.4)
+    http_parser.rb (0.8.0)
+    i18n (1.14.1)
+      concurrent-ruby (~> 1.0)
+    jekyll (3.9.3)
+      addressable (~> 2.4)
+      colorator (~> 1.0)
+      em-websocket (~> 0.5)
+      i18n (>= 0.7, < 2)
+      jekyll-sass-converter (~> 1.0)
+      jekyll-watch (~> 2.0)
+      kramdown (>= 1.17, < 3)
+      liquid (~> 4.0)
+      mercenary (~> 0.3.3)
+      pathutil (~> 0.9)
+      rouge (>= 1.7, < 4)
+      safe_yaml (~> 1.0)
+    jekyll-avatar (0.7.0)
+      jekyll (>= 3.0, < 5.0)
+    jekyll-coffeescript (1.1.1)
+      coffee-script (~> 2.2)
+      coffee-script-source (~> 1.11.1)
+    jekyll-commonmark (1.4.0)
+      commonmarker (~> 0.22)
+    jekyll-commonmark-ghpages (0.4.0)
+      commonmarker (~> 0.23.7)
+      jekyll (~> 3.9.0)
+      jekyll-commonmark (~> 1.4.0)
+      rouge (>= 2.0, < 5.0)
+    jekyll-default-layout (0.1.4)
+      jekyll (~> 3.0)
+    jekyll-feed (0.15.1)
+      jekyll (>= 3.7, < 5.0)
+    jekyll-gist (1.5.0)
+      octokit (~> 4.2)
+    jekyll-github-metadata (2.13.0)
+      jekyll (>= 3.4, < 5.0)
+      octokit (~> 4.0, != 4.4.0)
+    jekyll-include-cache (0.2.1)
+      jekyll (>= 3.7, < 5.0)
+    jekyll-mentions (1.6.0)
+      html-pipeline (~> 2.3)
+      jekyll (>= 3.7, < 5.0)
+    jekyll-optional-front-matter (0.3.2)
+      jekyll (>= 3.0, < 5.0)
+    jekyll-paginate (1.1.0)
+    jekyll-readme-index (0.3.0)
+      jekyll (>= 3.0, < 5.0)
+    jekyll-redirect-from (0.16.0)
+      jekyll (>= 3.3, < 5.0)
+    jekyll-relative-links (0.6.1)
+      jekyll (>= 3.3, < 5.0)
+    jekyll-remote-theme (0.4.3)
+      addressable (~> 2.0)
+      jekyll (>= 3.5, < 5.0)
+      jekyll-sass-converter (>= 1.0, <= 3.0.0, != 2.0.0)
+      rubyzip (>= 1.3.0, < 3.0)
+    jekyll-sass-converter (1.5.2)
+      sass (~> 3.4)
+    jekyll-seo-tag (2.8.0)
+      jekyll (>= 3.8, < 5.0)
+    jekyll-sitemap (1.4.0)
+      jekyll (>= 3.7, < 5.0)
+    jekyll-swiss (1.0.0)
+    jekyll-theme-architect (0.2.0)
+      jekyll (> 3.5, < 5.0)
+      jekyll-seo-tag (~> 2.0)
+    jekyll-theme-cayman (0.2.0)
+      jekyll (> 3.5, < 5.0)
+      jekyll-seo-tag (~> 2.0)
+    jekyll-theme-dinky (0.2.0)
+      jekyll (> 3.5, < 5.0)
+      jekyll-seo-tag (~> 2.0)
+    jekyll-theme-hacker (0.2.0)
+      jekyll (> 3.5, < 5.0)
+      jekyll-seo-tag (~> 2.0)
+    jekyll-theme-leap-day (0.2.0)
+      jekyll (> 3.5, < 5.0)
+      jekyll-seo-tag (~> 2.0)
+    jekyll-theme-merlot (0.2.0)
+      jekyll (> 3.5, < 5.0)
+      jekyll-seo-tag (~> 2.0)
+    jekyll-theme-midnight (0.2.0)
+      jekyll (> 3.5, < 5.0)
+      jekyll-seo-tag (~> 2.0)
+    jekyll-theme-minimal (0.2.0)
+      jekyll (> 3.5, < 5.0)
+      jekyll-seo-tag (~> 2.0)
+    jekyll-theme-modernist (0.2.0)
+      jekyll (> 3.5, < 5.0)
+      jekyll-seo-tag (~> 2.0)
+    jekyll-theme-primer (0.6.0)
+      jekyll (> 3.5, < 5.0)
+      jekyll-github-metadata (~> 2.9)
+      jekyll-seo-tag (~> 2.0)
+    jekyll-theme-slate (0.2.0)
+      jekyll (> 3.5, < 5.0)
+      jekyll-seo-tag (~> 2.0)
+    jekyll-theme-tactile (0.2.0)
+      jekyll (> 3.5, < 5.0)
+      jekyll-seo-tag (~> 2.0)
+    jekyll-theme-time-machine (0.2.0)
+      jekyll (> 3.5, < 5.0)
+      jekyll-seo-tag (~> 2.0)
+    jekyll-titles-from-headings (0.5.3)
+      jekyll (>= 3.3, < 5.0)
+    jekyll-watch (2.2.1)
+      listen (~> 3.0)
+    jemoji (0.12.0)
+      gemoji (~> 3.0)
+      html-pipeline (~> 2.2)
+      jekyll (>= 3.0, < 5.0)
+    kramdown (2.3.2)
+      rexml
+    kramdown-parser-gfm (1.1.0)
+      kramdown (~> 2.0)
+    liquid (4.0.4)
+    listen (3.8.0)
+      rb-fsevent (~> 0.10, >= 0.10.3)
+      rb-inotify (~> 0.9, >= 0.9.10)
+    mercenary (0.3.6)
+    minima (2.5.1)
+      jekyll (>= 3.5, < 5.0)
+      jekyll-feed (~> 0.9)
+      jekyll-seo-tag (~> 2.1)
+    minitest (5.20.0)
+    nokogiri (1.15.4-x86_64-darwin)
+      racc (~> 1.4)
+    octokit (4.25.1)
+      faraday (>= 1, < 3)
+      sawyer (~> 0.9)
+    pathutil (0.16.2)
+      forwardable-extended (~> 2.6)
+    public_suffix (4.0.7)
+    racc (1.7.1)
+    rb-fsevent (0.11.2)
+    rb-inotify (0.10.1)
+      ffi (~> 1.0)
+    rexml (3.2.6)
+    rouge (3.26.0)
+    ruby2_keywords (0.0.5)
+    rubyzip (2.3.2)
+    safe_yaml (1.0.5)
+    sass (3.7.4)
+      sass-listen (~> 4.0.0)
+    sass-listen (4.0.0)
+      rb-fsevent (~> 0.9, >= 0.9.4)
+      rb-inotify (~> 0.9, >= 0.9.7)
+    sawyer (0.9.2)
+      addressable (>= 2.3.5)
+      faraday (>= 0.17.3, < 3)
+    simpleidn (0.2.1)
+      unf (~> 0.1.4)
+    terminal-table (1.8.0)
+      unicode-display_width (~> 1.1, >= 1.1.1)
+    typhoeus (1.4.0)
+      ethon (>= 0.9.0)
+    tzinfo (2.0.6)
+      concurrent-ruby (~> 1.0)
+    unf (0.1.4)
+      unf_ext
+    unf_ext (0.0.8.2)
+    unicode-display_width (1.8.0)
+    webrick (1.8.1)
+
+PLATFORMS
+  x86_64-darwin-20
+
+DEPENDENCIES
+  faraday-retry (~> 2.1)
+  github-pages
+  jekyll-gist
+  jekyll-include-cache
+  jekyll-mentions
+  jekyll-redirect-from
+  webrick
+
+BUNDLED WITH
+   2.3.7

Minimal-Mistakes-LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2013-2019 Michael Rose and contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -1,90 +1,17 @@
+# [decentralized-id.com](https://decentralized-id.com)
 
-<center><img src="images/identity-decentralized.png"/></center>
+## Stay Current on SSI with [Identosphere Weekly](https://newsletter.identosphere.net) a free newsletter by [Infominer](https://infominer.xyz) and [Identitywoman](https://identitywoman.net/)
+
+<center><img src="images/did-twitter.webp"/></center>
 
-# DID - Identity Decentralized
 
 >A good self‐sovereign identity system will allow individuals to directly influence how companies, governments, and others correlate our interactions across different services and locations by default. It won’t fix all identity problems nor preclude alternative identity approaches, but it will put the individual in control of most uses of identity and give organizations a simpler, easier, more ethical way to use identity to improve how they provide services and products. When successful, it will not only enable individuals to exercise greater control over how companies and governments keep track of us, it will also illuminate those situations where self‐sovereign identity is restricted, facilitating a conversation about when and where such limits are appropriate. [Joe Andrieu -A Technology‐Free Definition of Self‐Sovereign Identity](https://github.com/jandrieu/rebooting-the-web-of-trust-fall2016/blob/master/topics-and-advance-readings/a-technology-free-definition-of-self-sovereign-identity.pdf)
 
-## Note:
-
-I changed the name of the repository, as it no longer resembles anything like an awesome-list and won't move that direction any time soon. I also figured out how to run this as a directory off of my personal page...
-
-Don't worry, I won't neglect the README's.
-![](/images/distracted-infominer.png)
-
-
-For now, [**infominer.id/DIDecentralized**](https://infominer.id/DIDecentralized) will be the most up to date - and I will make every effort to optimize for that experience, including mobile; rather than for navigation through github.
-
-**ATTN:** It would be really helpful to me, if you have a project in this ecosystem and want to make a page that highlights your best traits and includes your most valuable resources - or even personal page that describes who you are and what you do, history, as far as you want to go really- I can add it to the repository and build upon it, or simply add it to the collection, whatever works for everyone. 
-
-I'm open to collaboration.
-
-
-
-## Contents
-
-[[**T**](#contents)]witter • [[**G**](#contents)]ithub • [[**B**](#contents)]log • [[**wp**](#contents)] whitepaper • [[**D**](#contents)]ocumentation • [[**F**](#contents)]orums • [[**C**](#contents)]hat • [[**tele**](#contents)]gram • [[**web**](#contents)]site
-• [[**ϟ**](#contents)] related resource • [[**>**](#contents)] related section • [[**>>**](#contents)] another page on site. • [[**^**](#contents)] back to the contents.
-
-
-* [What is Decentralized ID?](#what-is-decentralized-id-)
-* [Decentralized Identity History](#decentralized-identity-history-)
-* [What is Self Sovereign Identity?](#self-sovereign-identity-)
-* [DID Related Web Standards](#did-related-web-standards-)
-  * [OASIS XDI TC Technical Committee](#oasis-xdi-tc-technical-committee-)
-  * [W3C](#w3c-)
-    * [DID the Decentralized Identifier](#did-the-decentralized-identifier-)
-    * [Verifiable Claims](#verifiable-claims-)
-  * [Decentralized Key Managment DKMS](#decentralized-key-management-agents-)
-  * [DID Auth](#did-auth-) 
-  * [Blockcerts](#blockcerts-)
-  * [Schema](#schema-)
-* [DID Adoption](#did-adoption-)
-* [Directory](#directory-) To other pages within this repository.
-  * [SSI\DID History](history.md) >>
-  * [Self Sovereign Identity](self-sovereign-identity) >>
-  * [GDPR](gdpr) >>
-  * [Humanitarian](humanitarian.md) >>
-  * [Identity Related GitHub Repositories](identity-github.md) >>
-  * [Literature](literature.md) >>
-  * [Rebooting Web of Trust](rebooting-web-of-trust.md) >>
-  * [Media](media.md) >> - Video, Podcasts and Slideshare  
-  * [Decentralized Identity Foundation—DIF](identity-foundation.md) >>
-  * [Bitcoin](bitcoin.md) >>
-    * [Spidchain](bitcoin.md#spidchain-) >>
-  * [Ethereum](ethereum.md) >>
-    * [ERC-EIP](ethereum.md#erc-eip-) >>
-    * [ERC725-735](ethereum.md#erc725-735-)
-    * [uPort](ethereum.md#uport-) >>
-    * [Jolocom](ethereum.md#jolocom-) >>
-    * [Spidchain](ethereum.md#spidchain-) >>
-    * [Cryptonomica](ethereum.md#cryptonomica-) >>
-    * [Assorted Ethereum Apps](ethereum.md#assorted-ethereum-apps-) >>
-  * [Indy Ecosystem](indy-ecosystem/) >>
-    * [Adoption](indy-ecosystem/adoption.md) >>
-    * [Indy Github](indy-ecosystem/indy-github.md) >>
-    * [Literature](indy-ecosystem/literature.md) >>
-    * [Sovrin Foundation](indy-ecosystem/sovrin.foundation.md) >>
-    * [VON](indy-ecosystem/VON.md) >>
-  * [Hyperledger Global Forum](hgf-2018/) >>
-  * [State Sponsored](state-sponsored.md) >>
-  * [Microsoft](microsoft.md) >>
-  * [IBM](ibm.md) >>
-* [Sources](#sources-)
-* [Tips Jar](#tips-jar-)
-* [github.com/infominer33/DIDecentralized](https://github.com/infominer33/DIDecentralized)
-* [infominer.id](https://infominer.id)
-
-
-*Pull Requests Welcome*
-
-
-
 
 ![](https://i.imgur.com/9KpJRDr.png)
 
 
-## What is Decentralized ID? [**^**](#contents)
+## What is Decentralized ID?
 
 That's a big question, and what follows are just some notes, until I work out a more thoughtful answer.
 
@@ -92,240 +19,83 @@ The essence of Decentralized-ID is in creating open standards for a privacy pres
 
 It's impossible to have a conversation about decentralized-id without discussing blockchain and self sovereign identity: 
   * Self Sovereign Identity principles (with some help from the GDPR) have helped to shape the narrative around putting the identity owner in control over their personal information.
-  * Blockchain fueled longstanding efforts to create a privacy preserving internet-wide identity protocol, and inspired development of decentralized networks for online identification. 
-  * The United Nations Sustainable Development Goals (SDGs) have also helped to fueled efforts for a global and widely accessible identity solution.
-
-## Decentralized Identity History [**^**](#contents)
-
-* [Losing Control over our Personal Information >>](history.md#losing-control-over-our-personal-information) '80s
-* [PGP - Web of Trust >>](#pgp---web-of-trust-) '91
-* [International Planetwork Conference >>](history.md#international-planetwork-conference-) '00s
-* [XNS Public Trust Organization >>](history.md#xns-public-trust-organization-)
-* [The Augmented Social Network >>](history.md#the-augmented-social-network-) '03
-* [IDCommons >>](history.md#idcommons-) '01
-* [Identity Gang >>](history.md#identity-gang-) '04
-  * [Kim Cameron - Laws of Identity >>](history.md#kim-cameron---laws-of-identity) 
-* [Internet Identity Workshop—IIW >>](history.md#internet-identity-workshop-) '05
-* [W3C Credentials Community Group >>](history.md#w3c-credentials-community-group-) '14 
-* [Bitnation >>](history.md#bitnation-) '15
-* [The United Nations Sustainable Development Goals >>](history.md#the-united-nations-sustainable-development-goals-) '15
-* [history.md#Rebooting-Web-of-Trust (RWoT) >>](history.md#rebooting-the-web-of-trust-) 
-* [Evernym >>](history.md#evernym-)
-* [ID2020 and the GDPR >>](history.md#id2020-and-the-gdpr-) '16
-* [The End of 2016 >>](history.md#the-end-of-2016-)
-* [Decentralized Identity Foundation >>](history.md#decentralized-identity-foundation-) '17
-* [Standards History >>](history.md#standards-history-)
-* [Resources >>](history.md#resources-)
+  * Excitement over Blockchain Tech has spilled over in support of longstanding efforts to create a privacy preserving internet-wide identity protocol, and inspired development of decentralized networks for online identification. 
+  * The United Nations Sustainable Development Goals (SDGs) have also fueled efforts towards a global and widely accessible identity solution.
 
 
-## Self Sovereign Identity [**^**](#contents)
+
+## Self Sovereign Identity
 
 ![](https://imgur.com/3zz62kpl.png)
 
 
 * [Christopher Allen](http://www.lifewithalacrity.com/)[[**info**](https://christophera.info/)] details the overarching history of internet idenitity standards and outlines [10 Principles of Self Sovereign Identity](https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/self-sovereign-identity-principles.md) in his seminal work [The Path to Self-Soverereign Identity](http://www.lifewithalacrity.com/2016/04/the-path-to-self-soverereign-identity.html)[[**ϟ**](https://www.coindesk.com/path-self-sovereign-identity/amp/)]
-* <a href="https://github.com/jandrieu/rebooting-the-web-of-trust-fall2016/raw/master/topics-and-advance-readings/a-technology-free-definition-of-self-sovereign-identity.pdf"><u>A Technlogy-Free Definition of Self-Sovereign Identity</u></a> is a continuation of the discussion started by Allen, offering 3 "Core Characteristics of Sovereign Identity".
+* [<u>A Technlogy-Free Definition of Self-Sovereign Identity</u>](https://github.com/jandrieu/rebooting-the-web-of-trust-fall2016/raw/master/topics-and-advance-readings/a-technology-free-definition-of-self-sovereign-identity.pdf) is a continuation of the discussion started by Allen, offering 3 "Core Characteristics of Sovereign Identity".
 * [7 Myths of Self Sovereign Identity](https://medium.com/evernym/7-myths-of-self-sovereign-identity-67aea7416b1)
 * [Inevitable Rise of Self-Sovereign Identity](https://sovrin.org/wp-content/uploads/2018/03/The-Inevitable-Rise-of-Self-Sovereign-Identity.pdf)
 * [SSIMeetup](http://ssimeetup.org/) [[**S**](https://www.slideshare.net/SSIMeetup/presentations)] [[**V**](https://www.youtube.com/channel/UCSqSTlKdbbCM1muGOhDa3Og)] [[**tele**](https://t.me/SSIMeetup)]
 \- SSI Meetup is an open, collaborative community to help SSI evangelists around the world, independent of company interests or standards. 
 * [SSI: A Roadmap for Adoption](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/a-roadmap-for-ssi.md)
-* **[/DIDecentralized/self-sovereign-identity](self-sovereign-identity)** SSI documentation is still under development. This directory is to organize existing thought on SSI in one place for ease of study, and the development of new documentation.
 * [Matching Identity Management Solutions to Self Sovereign Identity Solutions](https://www.slideshare.net/TommyKoens/matching-identity-management-solutions-to-selfsovereign-identity-principles)
+<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">0/ “Self-Sovereign Identity: A Progress Report”…</p>&mdash; Christopher Allen (@ChristopherA) [April 25, 2018](https://twitter.com/ChristopherA/status/989120215702261761?ref_src=twsrc%5Etfw)</blockquote>
+
+[Self Sovereign Identity - Literature](https://decentralized-id.com/literature/self-sovereign-identity/)
+Here, I've gathered literature on Self Sovereign Identity, and begun considering it comparatively.
 
 
-<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">0/ “Self-Sovereign Identity: A Progress Report”…</p>&mdash; Christopher Allen (@ChristopherA) <a href="https://twitter.com/ChristopherA/status/989120215702261761?ref_src=twsrc%5Etfw">April 25, 2018</a></blockquote>
+## Directory
 
+[SSI\DID History](https://decentralized-id.com/history/)
+  * [User Centric Identity - 2000-2009](https://decentralized-id.com/history/2000-2009/)
+  * [Personal Data Ecosystem - 2010-2014](https://decentralized-id.com/history/2010-2014)
+  * [Blockchain Identity - 2015-2019](https://decentralized-id.com/history/2015-2019/)
 
-## DID Related Web Standards [**^**](#contents)
+[Self Sovereign Identity](https://decentralized-id.com/literature/self-sovereign-identity/)
+  * [Evolution of SSI](https://decentralized-id.com/literature/self-sovereign-identity/evolution-of-ssi/)
+  * [SSI Principles vs Characteristics](https://decentralized-id.com/literature/self-sovereign-identity/ssi-principles-vs-characteristics/)
+  * [User Experience](https://decentralized-id.com/literature/self-sovereign-identity/user-experience/)
 
-### OASIS XDI TC Technical Committee [**^**](#contents)
+[DID Related Web Standards](https://decentralized-id.com/specs-standards/)
+  * [XDI](https://decentralized-id.com/specs-standards/xdi/)
+  * [JSON-LD](https://decentralized-id.com/specs-standards/json-ld/)
 
-* <a href="https://github.com/OASIS-XDI-Technical-Committee/xdi-spec-docbook">/OASIS-XDI-Technical-Committee/xdi-spec-docbook</a> - XDI Specifications (Docbook)
-* <a href="https://github.com/OASIS-XDI-Technical-Committee/xdi-developers-guide">/OASIS-XDI-Technical-Committee/xdi-developers-guide</a> - XDI Developer's Guide
-* <a href="https://github.com/OASIS-XDI-Technical-Committee/xdi-spec-openoffice">/OASIS-XDI-Technical-Committee/xdi-spec-openoffice</a> - XDI Specifications (Open Office)
-* <a href="https://github.com/OASIS-XDI-Technical-Committee/xdi-spec-dita">/OASIS-XDI-Technical-Committee/xdi-spec-dita</a> - XDI Specifications (DITA)
+[Identity Related GitHub Repositories](https://decentralized-id.com/code/github/)
 
+[Literature](https://decentralized-id.com/literature/)
+  * [Rebooting Web of Trust - Papers Index](https://decentralized-id.com/literature/rebooting-web-of-trust/)
 
-### W3C [**^**](#contents)
+[Workshops](https://decentralized-id.com/workshops)
+[Media](https://decentralized-id.com/media/)  (Video, Podcasts and Slideshare)
+[DID Adoption](https://decentralized-id.com/adoption/)
+[GDPR](https://decentralized-id.com/government/europe/regulation/gdpr)
 
-![](https://imgur.com/Lz6RTysl.png)
+[Organizations](https://decentralized-id.com/organizations)
+  * [Decentralized Identity Foundation—DIF](https://decentralized-id.com/organizations/identity-foundation/)
+  * [My Data](https://decentralized-id.com/organizations/mydata/)
+  * [Sovrin Foundation](https://decentralized-id.com/organizations/sovrin/)
+  * [SSI Meetup](https://decentralized-id.com/organizations/ssi-meetup/)
 
-* [World Wide Web Consortium(W3C)](https://www.w3.org/) [[**T**](https://twitter.com/w3c)] [[**G**](https://github.com/w3c)]
-  >The [World Wide Web Consortium (W3C)](https://www.w3.org/Consortium/) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards. Led by Web inventor and Director Tim Berners-Lee and CEO Jeffrey Jaffe, W3C's mission is to lead the Web to its full potential.
-* <a href="https://lists.w3.org/Archives/Public/public-vc-wg/" target="_blank">Verifiable Claims WG - Mailing List</a> (and archives)
-* [Credentials Community Group](https://www.w3.org/community/credentials/)[[**B**](https://w3c-ccg.github.io/)]  
-* <a href="http://lists.w3.org/Archives/Public/public-credentials/" target="_blank">Public mailing list for the Credentials Community Group</a> (and archives) - Anyone may read or write to this list.
-* <a href="https://github.com/opencreds/website" target="_blank">/opencreds/website</a> 
-  * [opencreds.org — Identity Credentials 1.0](https://opencreds.org/specs/source/identity-credentials/)
-* <a href="https://sea-region.github.com/w3c-dvcg/w3c-dvcg.github.io" target="_blank">/w3c-dvcg/w3c-dvcg.github.io</a> - Landing site for W3C Digital Verification Community Group. [<a href="https://www.w3.org/community/digital-verification/">**W**</a>]
-* [JSON-LD 1.0, W3C Recommendation](https://www.w3.org/TR/json-ld/)
+[Blockchain](https://decentralized-id.com/blockchain/)
+  * [Bitcoin](https://decentralized-id.com/blockchain/bitcoin/)
+  * [Ethereum](https://decentralized-id.com/blockchain/ethereum/)
 
-![](https://imgur.com/6MLNgXal.png)\
-<sup><a href="https://www.youtube.com/watch?v=RllH91rcFdE">The Story of Open SSI Standards - Drummond Reed/Evernym SSIMeetup.org</a>[<b><a href="https://www.slideshare.net/SSIMeetup/self-sovereign-identity-ssi-open-standards-with-drummond-reed">ϟ</a></b>]</sup>
+[Hyperledger Indy](https://decentralized-id.com/hyperledger/indy/)
+  * [Adoption](https://decentralized-id.com/hyperledger/indy/adoption/)
+  * [Indy Github](https://decentralized-id.com/hyperledger/indy/github/)
+  * [Literature](https://decentralized-id.com/organizations/sovrin/literature/)
+  * [VON](https://decentralized-id.com/government/canada/von/)
+[Hyperledger Global Forum](https://decentralized-id.com/hyperledger/hgf-2018/)
 
-#### DID the Decentralized Identifier [**^**](#contents) 
+Private Sector
+  * [IBM](https://decentralized-id.com/private-sector/ibm/)
+  * [Microsoft](https://decentralized-id.com/private-sector/microsoft/)
+  * [Danube Tech](https://decentralized-id.com/private-sector/danube-tech/)
 
-<a href="https://www.w3.org/2018/vocabws/presentations/Sabadello.pdf"><img src="https://i.imgur.com/7NRcJbq.png"/></a>
+[Government](https://decentralized-id.com/government/)
 
-* [DID Whitepaper](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/DID-Whitepaper.md)
-  > A DID architecture should focus on the set of components that Mr. Gupta refers to as "the minimum required for people to be able to do business (or other critical functions) together".
-  >
-  >**A Decentralized Identifier (DID) Registry and Discovery Service**
-  >
-  > This "minimum required" is defined by a union of the proposed requirements identified by the W3C Credential Community Group, the XDI.org Registry Working Group, and the Rebooting the Web of Trust group. It consists of three functions that can be addressed by a combination of blockchain and DHT technology:
-  >
-  > * A DID registration function
-  > * A discovery function that enables looking up a registered DID in the blockchain
-  > * A master key recovery function
-* [A Universally Unique IDentifier (UUID) URN Namespace](https://www.ietf.org/rfc/rfc4122.txt) <-DID's modeled after
-  * [All you need to know about sequential UUID generators](https://blog.2ndquadrant.com/sequential-uuid-generators/)
-* [w3c- Decentralized Identifiers (DIDs) v0.11](https://w3c-ccg.github.io/did-spec/)
-  * Authors:
-     * [Drummond Reed](https://equalsdrummond.name/) [[**T**](https://twitter.com/drummondreed)] ([Evernym](https://www.evernym.com/))  
-     * [Manu Sporney](http://manu.sporny.org/)[[**T**](https://twitter.com/manusporny)]  ([Digital Bazaar](https://digitalbazaar.com))
-     * Dave Longley ([Digital Bazaar](https://digitalbazaar.com))
-     * [Christopher Allen](http://www.lifewithalacrity.com/) [[**info**](https://github.com/ChristopherA/info)] ([Blockstream](https://blockstream.com/))
-     * Ryan Grant
-     * [Markus Sabadello (Peacekeeper)](http://mydata2016.org/speaker/markus-sabadello/) [[**T**](https://twitter.com/peacekeeper)] [[**G**](https://github.com/peacekeeper)] [[**B**](https://medium.com/@markus.sabadello)] ([Danube Tech](https://github.com/projectdanube))
-* [Understanding Decentralized IDs (DIDs)](https://medium.com/@adam_14796/understanding-decentralized-ids-dids-839798b91809)
-* [DID Primer](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/draft-documents/did-primer.md) [[**ϟ**](https://github.com/WebOfTrustInfo/rwot7-fall2018/blob/master/topics-and-advance-readings/did-primer-extended.md)]
-* [Decentralized IDentifers (DIDs)](https://www.w3.org/2018/vocabws/presentations/Sabadello.pdf) 
-* [Requirements for DIDs](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/final-documents/requirements-for-dids.pdf)
-* [DIDs in DPKI](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/dids-in-dpki.md)
-* [What is a DID?](https://docs.google.com/document/d/1Ym85y_bDVN9xkRZ-oD-zlUUIeZjVGWNihfZBk2GQidk/edit)
-* [The Path from an id (DID) to a Real-Life Something](https://hyperonomy.com/2019/01/04/the-path-from-a-id-did-to-a-real-life-something)
+## Resources
 
-<a href="https://hyperonomy.files.wordpress.com/2019/01/path-id-did-real-life-somethings-v0.2-1.png"><img src="https://hyperonomy.files.wordpress.com/2019/01/path-id-did-real-life-somethings-v0.2-1.png?w=500"/></a>
-
-#### Verifiable Claims [**^**](#contents) 
-
-<a href="https://www.w3.org/2018/vocabws/presentations/Sabadello.pdf"><img src="https://i.imgur.com/nsZ0X7r.png"/></a>
-
-
-* [Verifiable Claims Working Group](https://www.w3.org/2017/vc/WG/) [[**D**](https://www.w3.org/2017/vc/charter.html)]
-* [Verifiable Claims Data Model 1.0](https://w3c.github.io/vc-data-model/) [[**G**](https://github.com/w3c/vc-data-model)] [[**D**](https://w3c.github.io/vc-use-cases/)]
-* [Verifiable Credentials 101 for SSI – Tyler Ruff – Webinar 11](http://ssimeetup.org/verifiable-credentials-101-ssi-tyler-ruff-webinar-11/)
-
-
-### DID Auth [**^**](#contents) 
-
-![](https://imgur.com/XMaq5cil.png)
-
-
-   * [DID Auth and the Little I-am-Me](https://medium.com/@markus.sabadello/did-auth-and-the-little-i-am-me-ec14d757ff09)
-   * [Introduction to DID Auth](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/did-auth.md) [[**ϟ**](http://ssimeetup.org/introduction-did-auth-markus-sabadello-webinar-10/)]
-
-<a href="http://ssimeetup.org/introduction-did-auth-markus-sabadello-webinar-10/"><img src="https://i.imgur.com/YNlk8RY.png"/></a>\
-http://ssimeetup.org/introduction-did-auth-markus-sabadello-webinar-10
-
-
-### Decentralized Key Management-Agents [**^**](#contents) 
-
-<img src="https://i.imgur.com/0SLcjUv.png"/>
-
-* [Decentralized Key Management (DKMS): An Essential Missing Piece of the SSI Puzzle - Drummond Reed](https://www.slideshare.net/SSIMeetup/decentralized-key-management-dkms-an-essential-missing-piece-of-the-ssi-puzzle-drummond-reed)
-* [Recommendations for Decentralized Key Management Systems](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/topics-and-advance-readings/dkms-recommendations.md)
-* [Agent to Agent Communication](https://drive.google.com/file/d/1PHAy8dMefZG9JNg87Zi33SfKkZvUvXvx/view): Daniel Hardman explains the goals of agent to agent communication
-
-
-![](https://i.imgur.com/5qc1qrG.png)\
-<sup><a href="http://ssimeetup.org/decentralized-key-management-dkms-essential-missing-piece-ssi-puzzle-drummond-reed-webinar-8/">DKMS - An Essential Missing Piece of the SSI Puzzle. Drummond Reed. SSIMeetup.org</a></sup>
-
-* <a href="https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE2DjfY" target="_blank">Microsoft- Decentralized Identity — Own and Control Your Identity.</a>
-![](https://i.imgur.com/ozOLCuW.png)
-
-
-### Blockcerts [**^**](#contents) 
-* [Learning Machine](https://www.learningmachine.com/)
-* [Academic Credentialing and the Blockchain](https://www.learningmachine.com/academic-credentialing-blockchain/)
-* [Blockcerts](https://www.blockcerts.org), developed by learning machine is an open standard for issuing and verifying blockchain-based official records; The project offers  open-source libraries, tools, and mobile apps. MIT has [issued](https://www.insidehighered.com/news/2017/10/19/mit-introduces-digital-diplomas) digital certificates based on this standard.
-  * [CXC (Carribean) Pilots E-Certificates on the Blockchain](https://www.cxc.org/cxc-pilots-e-certificates-on-the-blockchain/)
-  * [A Decentralized Approach to Blockcerts Credential Revocation](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/blockcerts-revocation.md)
-
-
-### Schema [**^**](#contents)
-* [Schema](https://schema.org) — a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet. Schema.org vocabulary can be used with many different encodings, including RDFa, Microdata and JSON-LD. These vocabularies cover entities, relationships between entities and actions, and can easily be extended through a well-documented extension model. Over 10 million sites use Schema.org to markup their web pages and email messages. Many applications from Google, Microsoft, Pinterest, Yandex and others already use these vocabularies to power rich, extensible experiences."
-
-
-## DID Adoption [**^**](#contents)
-
-**[DID Method Registry](https://w3c-ccg.github.io/did-method-registry/#the-registry)**
-* did:example:   - [DID Specification](https://w3c-ccg.github.io/did-spec/)
-* did:btcr:      - [BTCR DID Method](https://w3c-ccg.github.io/didm-btcr/) 
-  * The Bitcoin Reference DID method (did:btcr) supports DIDs on the public Bitcoin blockchain. The Bitcoin Reference method has minimal design goals: a DID trust anchor based on the Bitcoin blockchain, updates publicly visible and auditable via Bitcoin transactions, and optionally, additional DID Document information referenced in the transaction OP_RETURN data field. No other Personal Identifiable Information (PII) would be placed on the immutable blockchain.
-  * [btcr tx conversion playground](https://weboftrustinfo.github.io/btcr-tx-playground.github.io/) 
-* did:stack:     - [Blockstack DID Method](https://github.com/blockstack/blockstack-core/blob/master/docs/blockstack-did-spec.md) [[**ϟ**](https://forum.blockstack.org/t/did-method-at-identity-foundation/4287/9)] 
-  - 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.
-* did:cnsnt:   - Consent 	
-* did:erc725:  - [erc725 DID Method](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/DID-Method-erc725.md)
-* did:ipid:    - [IPID DID method](https://did-ipid.github.io/ipid-did-method/)
-  - Implementation of the DID spec over IPFS (Interplanetary File System) 
-* did:life:    - [lifeID DID Method](https://lifeid.github.io/did-method-spec/)
-* did:sov: 	   - [Sovrin DID Method](https://sovrin-foundation.github.io/sovrin/spec/did-method-spec-template.html)
-* did:uport: 	- uPort 	
-* did:v1: 	   - [Veres One DID Method](https://w3c-ccg.github.io/didm-veres-one/)
-  * [**veres.one**](https://veres.one) — a permissionless public ledger designed specifically for the creation and management of decentralized identifiers (DIDs)
-* did:dom:     - Dominode 	
-* did:ont: 	   - [Ontology DID Method](https://github.com/ontio/ontology-DID/blob/master/docs/en/DID-ONT-method.md)
-* did:vvo: 	   - [Vivvo DID Method](https://vivvo.github.io/vivvo-did-scheme/spec/did-method-spec-template.html)
-* did:icon:    - [ICON DID Method](https://github.com/icon-project/icon-DID/blob/master/docs/ICON-DID-method.md)
-* did:iwt: 	   - [InfoWallet DID Method](https://github.com/infowallet/did_method/blob/master/did_method.md)
-* did:ockam:   - [Ockam DID Method](https://github.com/ockam-network/did-method-spec/blob/master/README.md)
-  * [did:ockam:](https://medium.com/ockam/an-introduction-to-did-ockam-8626d5aecc53) [[**ϟ**](https://twitter.com/Ockam_io/status/1064589363269365763)]
-* did:ala: 	   - [Alastria DID Method](https://github.com/alastria/alastria-identity/wiki/Alastria-DID-Method-Specification-(Quorum-version))
-* did:op:      - [Ocean Protocol DID Method](https://github.com/oceanprotocol/OEPs/blob/master/7/did-method-spec.md)
-* did:jlinc:   - [JLINC Protocol DID Method](https://did-spec.jlinc.org/)
-* did:ion:     - [ION DID Method](https://github.com/decentralized-identity/ion-did-method)
-* did:jolo:    - Jolocom 	
-* did:ethr:    - [ETHR DID Method](https://github.com/uport-project/ethr-did-resolver/blob/develop/doc/did-method-spec.md)
-
----
-
-* [Peer DID Method Spec](https://dhh1128.github.io/peer-did-method-spec/index.html)
-* [@ChristopherA on DID adoption](https://twitter.com/ChristopherA/status/989122017348784130)
-   > "22/ Over a dozen companies and organizations, using multiple blockchains (Bitcoin, Ethereum, Hyperledger, etc.), have committed to deploying DIDs, including IBM, Microsoft, Digital Bazaar, Consensys, Evernym, Learning Machine, British Columbia, and more:" —[How blockchain could solve the internet privacy problem](https://www.computerworld.com/article/3267930/blockchain/how-blockchain-could-solve-the-internet-privacy-problem.html)
-
-![](https://oneworldidentity.com/wp-content/uploads/2018/10/companies.png)
-
-2018 Identity Landsacpe brought to you by: [One World Identity](https://oneworldidentity.com/) — independent advisory and digital strategy consultancy focused on trust and the data economy.
-
-
-
-## Directory [**^**](#contents)
-Other files and folders within this repository:
-
-  * [SSI\DID History](history.md)
-  * [Self Sovereign Identity](self-sovereign-identity)
-  * [Identity Related GitHub Repositories](identity-github.md)
-  * [Literature](literature.md)
-  * [Rebooting Web of Trust](rebooting-web-of-trust.md)
-  * [Media](assorted-media.md) - Video, Podcasts and Slideshare  
-  * [GDPR](gdpr)
-  * [Humanitarian](humanitarian.md)
-  * [Decentralized Identity Foundation—DIF](identity-foundation.md)
-  * [Bitcoin](bitcoin.md)
-    * [Spidchain](bitcoin.md#spidchain-)
-  * [Ethereum](ethereum.md)
-    * [uPort](ethereum.md#uport-)
-    * [Jolocom](ethereum.md#jolocom-)
-    * [Spidchain](ethereum.md#spidchain-)
-  * [Indy Ecosystem](indy-ecosystem/)
-    * [Adoption](indy-ecosystem/adoption.md)
-    * [Indy Github](indy-ecosystem/indy-github.md)
-    * [Literature](indy-ecosystem/literature.md)
-    * [Sovrin Foundation](indy-ecosystem/sovrin.foundation.md)
-    * [VON](indy-ecosystem/VON.md)
-  * [Hyperledger Global Forum](hgf-2018/)
-  * [State Sponsored](state-sponsored.md)
-  * [IBM](ibm.md)
-  * [Microsoft](microsoft.md)
-
-
-
-
-## Sources [**^**](#contents)
-* [SSI Meetup](http://ssimeetup.org/) [[**V**](https://www.youtube.com/channel/UCSqSTlKdbbCM1muGOhDa3Og)][[**ϟ**](https://www.slideshare.net/SSIMeetup/presentations/)] 
+* [SSI Meetup](http://ssimeetup.org/) • [video](https://www.youtube.com/channel/UCSqSTlKdbbCM1muGOhDa3Og) • [presentations](https://www.slideshare.net/SSIMeetup/presentations/)
 * [IIW-Wiki](https://iiw.idcommons.net/Main_Page)
 * [wiki.idcommons.net](http://wiki.idcommons.net/Main_Page)
 * [/WebOfTrustInfo](https://github.com/WebOfTrustInfo/)
@@ -334,14 +104,22 @@ Other files and folders within this repository:
 * [windley.com/tags/identity](http://www.windley.com/tags/identity.shtml)
 * [Kim Camerons Identity Blog](https://identityblog.com)
 
----
-
-## Tips Jar [**^**](#contents)
-
-BTC— 1GvkjHtiy9LUjVkStnEAXxjhcoS56aCokY
-
-![](https://imgur.com/yXLLm9Bl.png) 
-
-DOGE— DSzMxfABB8EwKiumzV7YHhS7HTvWAyM7QF
-
-![](https://i.imgur.com/0zBLoUP.png) 
+<h3>Tips Welcome</h3>
+<table class="table table-bordered table-hover table-condensed">
+  <thead>
+    <tr>
+      <th title="Field #1">Bitcoin</th>
+      <th title="Field #2">DOGE</th>
+    </tr>
+    </thead>
+    <tbody>
+    <tr>
+      <td>1D9382Y1hwF9mx8tRu8ZUVxcm2aq6yZDYR</td>
+      <td>D9y38ChAZP9aZG2mAJ94VAynAG4YGSvTpp</td>
+    </tr>
+    <tr>
+      <td><img src="https://imgur.com/j1hzcTo.png" width="150"></td>
+      <td><img src="https://raw.githubusercontent.com/Decentralized-ID/decentralized-id.github.io/master/images/doge-address.webp" width="150"></td>
+    </tr>
+  </tbody>
+</table>  

_config.yml

@@ -1,29 +1,351 @@
-plugins:
-    - jekyll-seo-tag
-    - jekyll-github-metadata
-    - jekyll-redirect-from
-    - jekyll-sitemap
-    - jekyll-mentions
+# Welcome to Jekyll!
+#
+# This config file is meant for settings that affect your entire site, values
+# which you are expected to set up once and rarely need to edit after that.
+# For technical reasons, this file is *NOT* reloaded automatically when you use
+# `jekyll serve`. If you change this file, please restart the server process.
 
-jekyll-mentions: https://twitter.com
+# Theme Settings
+#
+# Review documentation to determine if you should use `theme` or `remote_theme`
+# https://mmistakes.github.io/minimal-mistakes/docs/quick-start-guide/#installing-the-theme
 
-theme: jekyll-theme-modernist
-rooturl       : "https://infominer.id/DIDecentralized"    
-baseurl       : "/DIDecentralized"
-title         : "Identity Decentralized"
-description   : "Resources for Creating a Vendor Agnostic, User-Controlled, Identity Layer for the Internet."
-author        : "⧉ Infominer"
-logo          : "https://infominer.id/DIDecentralized/images/IDecentralized.png"
-repository    : "infominer33/DIDecentralized"
-github        : [metadata]
-image         : "https://infominer.id/DIDecentralized/images/IDecentralized.png"
+# theme                  : "minimal-mistakes-jekyll"
+# remote_theme           : "mmistakes/minimal-mistakes"
+minimal_mistakes_skin    : "air" # "air", "aqua", "contrast", "dark", "dirt", "neon", "mint", "plum", "sunrise"
 
+# Site Settings
+locale                   : "en-US"
+title                    : "Verifiable Credentials and Self Sovereign Identity Web Directory"
+title_separator          : "| "
+name                     : "Infominer"
+description              : "The largest, and longest-running, web directory surrounding decentralized identity and verifiable credentials."
+url                      : "https://decentralized-id.com"
+baseurl                  : ""
+repository               : "Decentralized-ID/decentralized-id.github.io"
+github                   : [metadata]
+teaser                   : /images/did-square.webp
+logo                     : "/images/DID.webp"
+masthead_title           : "Decentralized Identity"
+# breadcrumbs            : false # true, false (default)
+words_per_minute         : 200
+comments:
+  provider               : "staticman_v2"
+staticman:
+  allowedFields          : ["name", "email", "message"]
+  repository             : Decentralized-ID/decentralized-id.github.io 
+  branch                 : "master"
+  commitMessage          : "New comment by {fields.name}"
+  filename               : comment-{@timestamp}
+  format                 : "yml"
+  moderation             : true
+  path                   : "_data/comments/{options.slug}"
+  requiredFields         : ["name", "message"]
+  generatedFields:
+    date:
+      type: "date"
+      options:
+        format: "timestamp-seconds" #"timestamp-milliseconds"
+  endpoint               : https://tools.identosphere.net/staticman/v2/entry/
+
+reCaptcha:
+  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=
+
+atom_feed:
+  path                   : # blank (default) uses feed.xml
+search                   : false
+search_provider          : algolia #  lunr (default), algolia, google
+algolia:
+  application_id         : Q7H7K9X8DV
+  index_name             : didecentral
+  search_only_api_key    : c02bbc81162fc9aaaf03cd6573962a94 # YOUR_SEARCH_ONLY_API_KEY
+  powered_by             : true # true (default), false
+  files_to_exclude:
+    - _pages/sitemap.md
+    - unsorted/*
+    - _posts/twitter/*.md
+    - _posts/drafts/*
+    - _posts/2020-01-10-welcome.md
+    - _posts/2020-01-10-getting-started.md
+    - _pages/*
+    - _drafts/*
+google:
+  search_engine_id       : # YOUR_SEARCH_ENGINE_ID
+  instant_search         : # false (default), true
+# SEO Related
+google_site_verification :
+bing_site_verification   :
+yandex_site_verification :
+naver_site_verification  :
+
+# Social Sharing
 twitter:
-  site        : "infominer33"
-  title       : "Identity Decentralized"
-  description : "Resources for Creating a Vendor Agnostic, User-Controlled, Identity Layer for the Internet."
-  image       : "https://infominer.id/DIDecentralized/images/identity-decentralized.png"
-  card        : "summary"
- 
-google_analytics: UA-132558656-1
+  username               : "infominer33"
+  site: "decentralizeid"
+#  description            : "Resources for Creating a Vendor Agnostic, User-Controlled, Identity Layer for the Internet."
+#  image                  : "/images/IDecentralized.webp"
+facebook:
+  username               :
+  app_id                 :
+  publisher              :
+og_image                 : /images/DID_og.webp
+# For specifying social profiles
+# - https://developers.google.com/structured-data/customize/social-profiles
+social:
+  type                   : # Person or Organization (defaults to Person)
+  name                   : # If the user or organization name differs from the site's name
+  links: # An array of links to social media profiles
 
+# Analytics
+analytics:
+  provider               : custom # false (default), "google", "google-universal", ""
+  google:
+    tracking_id          : #UA-132558656-3
+    anonymize_ip         : true
+
+# Site Author
+author:
+  name             : "DIDecentral"
+  avatar           : /images/did-square.webp
+  bio              : "Collaborative Curation, Community Research Initiative"
+  location         : "Curating the Web"
+  links:
+    - label: "Email"
+      icon: "fas fa-fw fa-envelope-square"
+      url: mailto:nfo@infominer.xyz
+    - label: "Website"
+      icon: "fas fa-fw fa-link"
+      url: "https://decentralized-id.com"
+    - label: "GitHub"
+      icon: "fab fa-fw fa-github"
+      url: "https://github.com/Decentralized-ID"
+    - label: "Twitter"
+      icon: "fab fa-fw fa-twitter-square"
+      url: "https://twitter.com/DecentralizeID"
+# https://fontawesome.com/icons/telegram?style=brands
+# Just go to fontawesome.com and add whatever social sites you need here.
+
+
+# Site Footer
+footer:
+  links:
+    - label: "Email"
+      icon: "fas fa-fw fa-envelope-square"
+      url: mailto:nfo@infominer.xyz
+    - label: "Website"
+      icon: "fas fa-fw fa-link"
+      url: "https://decentralized-id.com"
+    - label: "Twitter"
+      icon: "fab fa-fw fa-twitter-square"
+      url: "https://twitter.com/DecentralizeID"
+    - label: "GitHub"
+      icon: "fab fa-fw fa-github"
+      url: "https://github.com/Decentralized-ID"
+    
+    
+
+# Reading Files
+include:
+  - .htaccess
+  - _pages
+  - _posts
+exclude:
+  - "*.sublime-project"
+  - "*.sublime-workspace"
+  - vendor
+  - .asset-cache
+  - .bundle
+  - .jekyll-assets-cache
+  - .sass-cache
+  - assets/js/plugins
+  - assets/js/_main.js
+  - assets/js/vendor
+  - Capfile
+  - CHANGELOG
+  - config
+  - Gemfile
+  - Gruntfile.js
+  - gulpfile.js
+  - LICENSE
+  - log
+  - node_modules
+  - package.json
+  - Rakefile
+  - README
+  - tmp
+  - _drafts
+  - _data/toml
+keep_files:
+  - .git
+  - .svn
+encoding: "utf-8"
+markdown_ext: "markdown,mkdown,mkdn,mkd,md"
+
+
+# Conversion
+markdown: kramdown
+highlighter: rouge
+lsi: false
+excerpt_separator: "\n\n"
+incremental: false
+
+
+# Markdown Processing
+kramdown:
+  input: GFM
+  hard_wrap: false
+  auto_ids: true
+  footnote_nr: 1
+  entity_output: as_char
+  toc_levels: 1..6
+  smart_quotes: lsquo,rsquo,ldquo,rdquo
+  enable_coderay: false
+
+
+# Sass/SCSS
+sass:
+  sass_dir: _sass
+  style: compressed # http://sass-lang.com/documentation/file.SASS_REFERENCE.html#output_style
+
+
+# Outputting
+permalink: /:categories/:title/
+paginate: 12 # amount of posts to show
+paginate_path: /posts/page:num/
+timezone: Pacific/Fakaofo # https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
+
+
+# Plugins (previously gems:)
+plugins:
+  - jekyll-paginate
+  - jekyll-sitemap
+  - jekyll-gist
+  - jekyll-feed
+  - jemoji
+  - jekyll-include-cache
+  - jekyll-redirect-from
+  - jekyll-mentions
+
+jekyll-mentions:
+  base_url: https://twitter.com
+
+# mimic GitHub Pages with --safe
+whitelist:
+  - jekyll-paginate
+  - jekyll-sitemap
+  - jekyll-gist
+  - jekyll-feed
+  - jemoji
+  - jekyll-include-cache
+  - jekyll-redirect-from
+  - jekyll-mentions
+
+liquid:
+  error_mode: strict
+  strict_filters: true
+
+# Archives
+#  Type
+#  - GitHub Pages compatible archive pages built with Liquid ~> type: liquid (default)
+#  - Jekyll Archives plugin archive pages ~> type: jekyll-archives
+#  Path (examples)
+#  - Archive page should exist at path when using Liquid method or you can
+#    expect broken links (especially with breadcrumbs enabled)
+#  - <base_path>/tags/my-awesome-tag/index.html ~> path: /tags/
+#  - <base_path/categories/my-awesome-category/index.html ~> path: /categories/
+#  - <base_path/my-awesome-category/index.html ~> path: /
+category_archive:
+  type: liquid
+  path: /categories/
+tag_archive:
+  type: liquid
+  path: /tags/
+# https://github.com/jekyll/jekyll-archives
+# jekyll-archives:
+#   enabled:
+#     - categories
+#     - tags
+#   layouts:
+#     category: archive-taxonomy
+#     tag: archive-taxonomy
+#   permalinks:
+#     category: /categories/:name/
+#     tag: /tags/:name/
+
+
+# HTML Compression
+# - http://jch.penibelst.de/
+compress_html:
+  clippings: all
+  ignore:
+    envs: development
+
+# Defaults
+defaults:
+  # _pages
+  - scope:
+      path: "_pages"
+      type: pages
+    values:
+      sidebar:
+        - title: "Identity Decentralized"
+          image: "/images/the-world-map-from-a-binary-code.webp"
+          image_alt: "Binary Globe Image by GDj"
+          nav: "didnav"
+      layout: single
+      author_profile: false
+      read_time: false
+      classes: wide
+      comments: # true
+      share: true
+      related: true
+      toc: true
+      toc_sticky: false
+  # _posts
+  - scope:
+      path: "_posts"
+      type: posts
+    values:
+      sidebar:
+        - title: "Identity Decentralized"
+          image: "/images/the-world-map-from-a-binary-code.webp"
+          image_alt: "Binary Globe by GDj"
+          nav: "didnav"
+      layout: single
+      header:
+        og_image: /images/DID_og.webp
+      author_profile: false
+      read_time: true
+      comments: true
+      share: true
+      classes: wide
+      related: true
+      toc: true
+      toc_label: "Contents"
+      toc_icon: "link"
+      toc_sticky: false
+  - scope:
+      path: "_posts/companies"
+      type: posts
+    values:
+      sidebar:
+        - title: "Identity Decentralized"
+          image: "/images/the-world-map-from-a-binary-code.webp"
+          image_alt: "Binary Globe by GDj"
+          nav: "didnav"
+      layout: companys
+      author_profile: false
+      header:
+        og_image: /images/DID_og.webp
+      read_time: true
+      comments: false
+      share: true
+      classes: wide
+      related: true
+      toc: true
+  - scope:
+      path: "unsorted"
+      type: posts
+    values:
+      published: false

_data/authors.yml

@@ -0,0 +1,47 @@
+# /_data/authors.yml
+
+Infominer:
+  name        : "Infominer"
+  bio         : "Information Logistics"
+  avatar      : "/images/info-id.webp"
+  links:
+    - label: "Email"
+      icon: "fas fa-fw fa-envelope-square"
+      url: "mailto:nfo@infominer.xyz"
+    - label: "Website"
+      icon: "fas fa-fw fa-link"
+      url: "https://infominer.xyz"
+    - label: "GitHub"
+      icon: "fab fa-fw fa-github"
+      url: "https://github.com/infominer33/"
+
+Decentralized-ID:
+  name             : "Decentralized-ID"
+  avatar           : https://decentralized-id.com/images/did-square.png
+  bio              : "Collaborative Curation, Community Research Initiative"
+  links:
+    - label: "Email"
+      icon: "fas fa-fw fa-envelope-square"
+      url: mailto:info@identosphere.net
+    - label: "Website"
+      icon: "fas fa-fw fa-link"
+      url: "https://decentralized-id.com/"
+    - label: "GitHub"
+      icon: "fab fa-fw fa-github"
+      url: "https://github.com/Decentralized-ID"
+    - label: "Twitter"
+      icon: "fab fa-fw fa-twitter-square"
+      url: "https://twitter.com/DecentralizeID"
+
+
+Cornelius Fiddlebone:
+  name        : "Cornelius Fiddlebone"
+  bio         : "I ordered what?"
+  avatar      : "/assets/images/bio-photo.jpg"
+  links:
+    - label: "Email"
+      icon: "fas fa-fw fa-envelope-square"
+      url: "mailto:cornelius@thewhip.com"
+    - label: "Twitter"
+      icon: "fab fa-fw fa-twitter-square"
+      url: "https://twitter.com/rhymeswithsackit"

_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: ["Government","Companies","Community Orgs","Standards Development Orgs"]
+Application: ["Government","Uses","Decentralized Web","Web 3"]

_data/comments/blockchain-2015-19/comment-1602408872820.yml

@@ -0,0 +1,7 @@
+_id: f7de1180-0ba4-11eb-a0a0-cff907ce0303
+message: I submited the very first comment ever!
+name: infominer
+email: nfo@infominer.xyz
+url: ''
+hidden: ''
+date: '2020-10-11T09:34:32.820Z'

_data/navigation.yml

@@ -0,0 +1,112 @@
+# main links
+main:
+  - title: "Introduction"
+    url: /introduction/
+  - title: "Ecosystem"
+    url: /ecosystem/
+  - title: "New"
+    url: "/posts/"
+  - title: "Updated"
+    url: "/recent/"
+  - title: "Categories"
+    url: "/categories/"
+  - title: "Welcome"
+    url: "/about/"
+  - title: "Aim"
+    url: "/aim/"
+
+didnav:
+  - title: "Home"
+    url: "/"
+    children:
+      - title: "• Resources & Pre-History"
+        url: "/history/"
+      - title: "• 2000-2009"
+        url: "/history/2000-2009/"
+      - title: "• 2010-2014"
+        url: /history/2010-2014/
+      - title: "• 2015-2019"
+        url: /history/2015-2019/
+  - title: New Pages New Structure
+    url: "/categories/#companies"
+    children:
+      - title: "• ValidatedID"
+        url: "/companies/ValidatedID/"
+      - title: "• SpruceID"
+        url: "/companies/ValidatedID/"
+      - title: "• Spherity"
+        url: "/companies/Spherity/"
+      - title: "• MyDEX"
+        url: "/companies/MyDEX/"
+      - title: "• Mattereum"
+        url: "/companies/Mattereum/"
+      - title: "• Magic Labs"
+        url: "/companies/MagicLabs/"
+      - title: "• Lissi"
+        url: "/companies/Lissi/"
+      - title: "• Indicio"
+        url: "/companies/Indicio/"
+      - title: "• IDRamp"
+        url: "/companies/IDramp/"
+      - title: "• GlobalID" 
+        url: "/companies/GlobalID/"
+      - title: "• Gataca" 
+        url: "/companies/Gataca/"
+  - title: Literature
+    children:
+      - title: "• Identosphere Blog Catcher"
+        url: https://identosphere.net/
+      - title: "• Identosphere Newsletter"
+        url: https://newsletter.identosphere.net/
+      - title: "• SSI Literature"
+        url: "/literature/self-sovereign-identity/"
+      - title: "• IIW Session Topics"
+        url: "/workshops/internet-identity-workshop/"
+      - title: "• RWoT Papers Index"
+        url: "/workshops/rebooting-web-of-trust/"
+  - title: Web Standards
+    url: /web-standards/
+    children:
+      - title: "• W3C"
+        url: "/web-standards/w3c/"
+      - title: "• Verifiable Credentials"
+        url: "/web-standards/w3c/wg/vc/verifiable-credentials/"
+      - title: "• JSON-LD"
+        url: "/web-standards/linked-data/JSON-LD/"
+      - title: "• GS1"
+        url: "/web-standards/gs1/"
+  - title: Regulation
+    children:
+      - title: "• eIDAS"
+        url: "/government/europe/regulation/eidas/"
+      - title: "• GDPR"
+        url: "/government/europe/regulation/gdpr/"
+  - title: "Organizations"
+    url: "/organizations/"
+    children:
+      - title: "• Identity Foundation"
+        url: "/organizations/decentralized-identity-foundation/"
+      - title: "• My Data"
+        url: "/organizations/mydata/"
+      - title: "• Hyperledger Foundation"
+        url: "/blockchain/hyperledger/"
+      - title: "• Sovrin Foundation"
+        url: "/organizations/sovrin-foundation/"
+      - title: "• SSI Meetup"
+        url: "/organizations/ssi-meetup/"
+      - title: "• Women in Identity"
+        url: "/organizations/women-in-identity/"
+  - title: "Infominer"
+    children:
+      - title: "• InfoHub"
+        url: "https://infominer.xyz/"
+      - title: "• Identosphere Newsletter"
+        url: "https://identosphere.net/"
+      - title: "• Identosphere BlogCatcher"
+        url: "https://identosphere.net/"
+      - title: "• Bitcoin Histories"
+        url: "https://bitcoinfo.github.io/history/"
+      - title: "• Decentralized Web Histories"
+        url: "https://sourcecrypto.github.io/decentralized-web/"
+      - title: "• Source⧉Crypto"
+        url: "https://sourcecrypto.github.io"

_data/standards.csv

@@ -0,0 +1,690 @@
+main,parent,name,supporting,authors,related,location,serving,policy,event,title,text,description,link,image,type,status,platform,section,sector,industry,market,focus,projects,tech,working group,date,github,twitter,youtube,list,feed,discord,crunchbase,linkedin,docs,devtools,app,telegram,forum
+Standards,ETSI,,https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0213.html,,,,,,,A Guide To Writing World Class Standards,- A world class standard should have well-defined objectives that respond to real needs in a timely manner.<br>- Its technical content should be complete and accurate.<br>- It should be easy to understand (or as easy as the subject matter allows!) and easy to implement.<br>- Its requirements should be expressed clearly and unambiguously.<br>- It should be validated.<br>- It should be well-maintained.,,https://www.etsi.org/images/files/Brochures/AGuideToWritingWorldClassStandards.pdf,,Paper,,,Standardization,,,,,,,,2020-07-29,,,,,,,,,,,,,
+Standards,Medium,,,Tim Bouma,,,,,,Trust Frameworks? Standards Matter,"He points at the NIST documents about it [Developing Trust Frameworks to Support Identity Federations](https://nvlpubs.nist.gov/nistpubs/ir/2018/NIST.IR.8149.pdf) published in 2018. He also points at the Canadian government’s definition of standards.<br>a document that provides a set of agreed-upon rules, guidelines or characteristics for activities or their results. Standards establish accepted practices, technical requirements, and terminologies for diverse fields.”  He goes on to highlight a lot of the work being done in Canada and where it all sits relative to being a standard - “In closing, there are lots of trust frameworks being developed today. But to be truly trusted, a trust framework needs to either apply existing standards or become a standard itself.”","Note: This post is the author’s opinion only and does not represent the opinion of the author’s employer, or any organizations with which the author is involved. Over the past few years, and…",https://medium.com/@trbouma/trust-frameworks-standards-matter-47c946992f44,,Post,,,Standardization,,,,,,,,2020-11-26,,,,,,,,,,,,,
+Standards,WeAreOpen,,,Doug Belshaw,,,,,,Open standards should be developed openly,"Open standards should be developed openly because not enough people work to ensure that equity is central to innovation and development. We believe that openness is an attitude, and one which bears fruit over time from which everyone can benefit.<br>5",Imagine a community garden with abundant fruit and vegetables for anyone to come and pick and consume. Now imagine a factory creating standardised parts to be used by manufacturers. The two metaphors…,https://blog.weareopen.coop/open-standards-should-be-developed-openly-1f0cf552308d,,Post,,,Standardization,,,,,,,,2021-08-19,,,,,,,,,,,,,
+Standards,ContinuumLoop,,,Darrell O'Donnell,,,,,,Premature Standardization & Interoperability,Here’s my premise – we don’t have standards nor interoperability – at least not as people really need. We have been through a process that is powerful and good – but what we have is what I call “premature standardization.” It’s a great start but nowhere near where things will be.,Within the decentralized identity space its premature to think we have real Standardization & Interoperability,https://www.continuumloop.com/premature-standardization-interoperability/,,Post,,,Standardization,,,,,,,,2022-09-11,,,,,,,,,,,,,
+Standards,Trinsic,,,Anna Johnson,,,,,,Trinsic Basics: What Are SSI Standards?,There are two kinds of standards that Trinsic implements to enable interoperability and avoid vendor lock-in: data model standards and protocol standards.,Our engineering team ensures that the Trinsic platform is always based on the most recent SSI standards and protocols.,https://trinsic.id/what-are-ssi-standards/,,page,,,Standardization,,,,,,,,2020-11-12,,,,,,,,,,,,,
+Standards,Scripting.com,,,Dave Winer,,,,,,Manifesto: Rules for standards-makers,"I've used all kinds of formats and protocols in a long career as a software developer, even created a few. My new manifesto summarizes what I've learned about what works and what doesn't.",,http://scripting.com/2017/05/09/rulesForStandardsmakers.html,,Post,,,Standardization,,,,,,,,2017-05-08,,,,,,,,,,,,,
+Standards,ContinuumLoop,,,Darrell O'Donnell,,,,,,Why Engage with Standards?,"too many people complain about problems but don’t step to Fix It!. There are certainly a lot of flawed standards – but they make interoperability possible – not perfect – but possible. If you haven’t used them then you have no right to complain that they are too complex, too simple (even in the same standard) or too domain specific – or any of the other rants and raves that go on. <br><br>If you’re willing to put up with a lot of work for incremental improvements then step up and join a standard. Whether that is a (relatively) fast moving standard group like OASIS (www.oasis-open.org) or a slower but more international group like ISO you will learn. You’ll also benefit from working with experts. These experts donate their time and are more than happy to provide ideas, guidance, and leadership.",,https://www.continuumloop.com/why-engage-with-standards/,,Post,,,Standardization,,,,,,,,2013-09-28,,,,,,,,,,,,,
+Standards,Forgerock,,,,,,,,,Who Are the Identerati? - ForgeRock,"You’re familiar with digital identity standards like OpenID Connect, OAuth, and User-Managed Access, fundamental elements of privacy and security on the internet. But have you ever wondered how they came to be? A lot of work on these protocols went on (and goes on) behind the scenes at the Internet Identity Workshop (IIW), a bi-annual gathering of identity experts where we work on improving the identity systems that make the web run. It’s a great event that’s flown under the radar, so I’m excited to share a new documentary on IIW,  “Not Just Who They Say We Are: Claiming our identity on the Internet”. This short film shines a light on the stealth community of “Identerati” at IIW that are defining and refining digital identity.","You’re familiar with digital identity standards like OpenID Connect, OAuth, and User-Managed Access, fundamental elements of privacy and security on the internet. But have you ever wondered how they came to be? A lot of work on these protocols went on (and goes on) behind the scenes at the Internet Identity Workshop (IIW), a bi-annual gathering of identity experts where we work on improving the identity systems that make the web run.",https://www.forgerock.com/blog/who-are-the-identerati,,Post,,,Standardization,,,,,,,,2017-03-22,,,,,,,,,,,,,
+Standards,Wikipedia,,,,,,,,,Who Runs the Internet?,"NO ONE PERSON, COMPANY, ORGANIZATION OR GOVERNMENT RUNS THE INTERNET.<br>The Internet itself is a globally distributed computer network comprised of many volantarily interconnected autonomous networks. Similarly, its overnance is conducte by a decentralized and international multi-stakeholder network of interconnected autonomous groups drawing from civil society, the private sector, governments, the academic and research communities, and national and international organizations. They work cooperatively from their respective roles to create shared policies and standards that mantian the Internet's global interoperability for the public good.",,https://es.wikipedia.org/wiki/Archivo:Who-Runs-the-Internet-graphic.png,https://upload.wikimedia.org/wikipedia/commons/thumb/e/ed/Who-Runs-the-Internet-graphic.png/1024px-Who-Runs-the-Internet-graphic.png,wiki entry,,,Standardization,,,,,,,,2013-01-31,,,,,,,,,,,,,
+Standards,Hyperledger,,,,,,,,,Identity Standards ,We hope to accumulate links here that talk to all Identity Standards work. Short updates form this will be used in the paper. Some are already input into the paper and need work polishing up.,,https://wiki.hyperledger.org/display/IWG/Identity+Standards,,wiki entry,,,Decentralized Identity Stack,,,,,,,Hyperledger Identity Working Group,2019-05-20,,,,,,,,,,,,,
+Standards,CCG Mailing List,,,Manu Sporny,,,,,,Roadmap: Verifiable Trust Standards,Green - General data format standards<br>Yellow - Vocabulary standards (I the mislabeled VC work)<br>Magenta - Protocol standards (I mislabeled DID Resolution)<br>Red - Low-level cryptographic primitives<br>Purple - General crypto packaging/protocol standards<br>Orange - Application layer standards,,https://lists.w3.org/Archives/Public/public-credentials/2021Mar/0014.html,https://lists.w3.org/Archives/Public/public-credentials/2021Mar/att-0014/VerifiableTrustStandards.png,Discussion,,,Decentralized Identity Stack,,,,,,,Credentials Community Group,2021-03-03,,,,,,,,,,,,,
+Standards,CCG Mailing List,,https://lists.w3.org/Archives/Public/public-credentials/2021Feb/att-0134/2021-Linked-Data-Security.pdf,Manu Sporny,,,,,,Linked Data Security,The attached slide deck provides a basic overview (with examples) of Linked Data Security as well as the specifications in that orbit. The W3C CCG is  actively developing a number of these specifications.,,https://lists.w3.org/Archives/Public/public-credentials/2021Feb/0134.html,,Discussion,,,Decentralized Identity Stack,,,,,,,Credentials Community Group,2021-02-29,,,,,,,,,,,,,
+Standards,arxiv,,,,,,,,,A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems (NIST CYBERSECURITY WHITE PAPER),"Identity management systems (IDMSs) are widely used to provision user identities while managing authentication, authorization, and data sharing both within organizations as well as on the Internet more broadly. Traditional identity systems typically suffer from single points of failure, lack of interoperability, and privacy issues such as encouraging mass data collection and user tracking. Blockchain technology has the potential to support novel data ownership and governance models with built-in control and consent mechanisms, which may benefit both users and businesses by alleviating these concerns; as a result, blockchain-based IDMSs are beginning to proliferate. This work categorizes these systems into a taxonomy based on differences in architecture, governance models, and other salient features. We provide context for the taxonomy by describing related terms, emerging standards, and use cases, while highlighting relevant security and privacy considerations. JULY 9, 2019",,https://arxiv.org/pdf/1908.00929.pdf,,Paper,DRAFT,,Decentralized Identity Stack,,,,,,,,2020-01-14,,,,,,,,,,,,,
+Standards,Personal,,,Tim Bouma,,,,,,Building Blocks for a New Architecture,"First, you will see the Issuer, Holder and Verifier. This is the archetypal pattern of the decentralized architecture. An issuer issues something to a holder, who then presents it to a verifier, who make a decision. A simple example: government(issuer) issues you a passport (holder), which you present to a border control officer (verifier) who lets you through the gate. When you look at all the use cases (described above), they all fall into this pattern. https://i.imgur.com/qGXEnW1.png","Note: These are my opinions only, and not that of my employer. All information used in developing this post is open and freely available. No statements should be considered as advice or representing…",https://medium.com/@trbouma/building-blocks-for-a-new-architecture-fda2238ac005,,Post,,,Decentralized Identity Stack,,,,,,,,2019-09-23,,,,,,,,,,,,,
+Standards,DIF,,,Oliver Terbu,,,,,,The Self-Sovereign Identity Stack,"<table><tr><td>Layer</td><td>Examples</td></tr><tr><td>Application</td><td>Selective Disclosure, music app, rideshare service, extensions, etc.</td></tr><tr><td>Implementation</td><td>DIF Hubs, Indy Agents, uPort app, etc.</td></tr><tr><td>Payload</td><td>JSON-LD, JWT, CWT</td></tr><tr><td>Encoding</td><td>ProtoBuf, Cap&#39;n Proto, MessagePack, JSON, CBOR, etc.</td></tr><tr><td>Encryption</td><td>Ciphersuite, JWE, etc.</td></tr><tr><td>DID AuthN</td><td>Key ownership, verification, challenge/response, etc.</td></tr><tr><td>Transport</td><td>QR Code, HTTP, BLE, NFC, FTP, SMTP, etc.</td></tr><tr><td>DID Resolution</td><td>DID-DID Doc / service and key resolution</td></tr><tr><td>DID Operations</td><td>CRUD support for a DID Doc</td></tr><tr><td>Storage</td><td>Optional, separate storage of DID metadata</td></tr><tr><td>Anchor</td><td>Bitcoin, Ethereum, Veres One, Sovrin, etc.</td></tr></table>","For anyone who isn’t working on the emerging technologies and concepts being developed in the self-sovereign identity (SSI) community, it can be difficult to track and digest all the concepts, tools…",https://medium.com/decentralized-identity/the-self-sovereign-identity-stack-8a2cc95f2d45,https://miro.medium.com/v2/resize:fit:1200/1*4zUczSBaVH-8qilvK4nKwQ.png,Post,,,Decentralized Identity Stack,,,,,,,,2019-01-27,,,,,,,,,,,,,
+Standards,DIF,,https://gist.github.com/creatornader/c8a20c534d3cf8f65a9b34ce2ad81725,Nader Helmy,,,,,,Overview of Decentralized Identity Standards,"we can think of each specification as addressing one or more of the SSI “building blocks” that we described above. In some cases a standard may be a bridge between layers, enabling a closer link between connections, data, and keys, making the ecosystem more secure as a whole. What you will find below is a list of all relevant standards, links to every specification, the organizations they belong to, their relationship to the ecosystem, and their relative maturity as internet technologies.","There are a number of organizations working towards standardization of technologies that span across the web. Of these, there are a handful of umbrella organizations that are particularly important…",https://medium.com/decentralized-identity/overview-of-decentralized-identity-standards-f82efd9ab6c7,https://miro.medium.com/v2/resize:fit:1000/1*oDeFSKBXhWkltGqXZ82yDA.png,Post,,,Decentralized Identity Stack,,,,,,,,2020-03-02,,,,,,,,,,,,,
+Standards,SSIMeetup.org ,,https://www.youtube.com/watch?v=RllH91rcFdE,Drummond Reed,Evernym,,,,,The Story of Open SSI Standards,"Drummond Reed, Chief Trust Officer at Evernym and Sovrin Foundation Trustee, features in our first Webinar “The Story of SSI Open Standards” by giving us the background on the foundation of Self Sovereign Identity. Drummond explains the technical and development aspects of DIDs, DKMS, DID Auth and Verifiable Credentials that will make Self Sovereign Identity possible.",,https://ssimeetup.org/story-open-ssi-standards-drummond-reed-evernym-webinar-1/,https://imgur.com/6MLNgXal.png,Presentation,,,Decentralized Identity Stack,,,,,,,,2018-04-27,,,,,,,,,,,,,
+Standards,DIF,,,,,,,,,SSI Architectural Stack and Community Efforts Overview,"While a more thorough (and competitive) separation of concerns might slice today’s and tomorrow’s identity systems into more modular and interchangeable parts at many more layers, the diagram used here organizes the space into just three broad divisions, which map roughly to the bottom three in the mapping dominant in the Aries & ToIP communities. For a more detailed and complex mapping, see the forthcoming map by the DIF interoperability working group.",,https://github.com/decentralized-identity/interoperability/blob/master/assets/ssi-architectural-stack--and--community-efforts-overview.pdf,,infographic,,,Decentralized Identity Stack,,,,,,,,2020-09-23,,,,,,,,,,,,,
+"Verifiable Credentials,Standards",Personal,,,Kristina Yasuda,VC spec map,,,,,Distributed ID Learning Path,"There is a lot of information about decentralized IDs on the web. I struggled too. (I still do that lol)<br><br>There are many standards for decentralized identities, and they are interdependent and interrelated, as you can see from the diagram below.","Describes pre-requisite knowledge, including JSON, JSON-LD, JWT, JWS, JWK, JWA, and sometimes CBOR. She then goes on to break down knowledge areas beginning with the basics: DID-Core, DID-Resolution, DID-Spec, DID Use-Cases. Next, she covers Verifiable Credentials with VC-Data Model, VC Use-Cases, and VC-Implementors Guide, and also Transport, Credential Presentation, and Other Data Formats.",https://translate.google.com/translate?sl=auto&tl=en&u=https://kristinayasuda.com/posts/decentralized-identity-catch-up-path/,https://images.ctfassets.net/iifz0jg6o9rt/1frepoi3bOWvEZOIAKlWkC/de5013e3d77fc29ce3c19a3a532c603d/IBO_WebUI.JPG,Post,,,"Interoperability, Decentralized Identity Stack",,,,,,,,2020-12-09,,,,,,,,,,,,,
+Standards,WebOfTrustInfo,,,,,,,,RWoT,Recommendations for Decentralized Key Management Systems,"A decentralized key management system (DKMS) aims to solve how consumers can manage their own keys and certificates without relying on a third-party provider having access or controls over the keys.. This method helps to ensure that no third-party can compromise the integrity and security of the system as a whole. Entities can use the system to safely authenticate each other and validate keys and certificates. Centralized key management systems (CKMS) manage key and certificate creation, signing, and validity. Specific problems arise when these authorities become unavailable, or the data they control becomes corrupted or known. Central authorities often become choice targets for attackers. This document proposes to meet these requirements with a decentralized blockchain ledger for providing an oracle of trust and leave control over all keys with end users. The use of a blockchain permits globally readable identifiers and public data to be shared in a secure manner that is not vulnerable to the man-in-the-middle attack or system wide compromise and permits consumers to be self-sovereign. This leaves consumers with the task of key management and protection. This document covers various ideas for how users may create, recover, backup, and revoke keys and provides recommended suggestions.",,https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/topics-and-advance-readings/dkms-recommendations.md,,Paper,,,Decentralized Identity Stack,,,,,,,,2017-09-15,,,,,,,,,,,,,
+Standards,SSIMeetup.org,,https://www.slideshare.net/SSIMeetup/decentralized-key-management-dkms-an-essential-missing-piece-of-the-ssi-puzzle-drummond-reed,Drummond Reed,,,,,,DKMS - An Essential Missing Piece of the SSI Puzzle,"DKMS inverts a core assumption of conventional PKI (public key infrastructure) architecture, namely that public key certificates will be issued by centralized or federated certificate authorities (CAs). With DKMS, the initial “root of trust” for all participants is any blockchain or distributed ledger that supports DIDs. This webinar will explain why we need DKMS, what a DKMS-compatible identity wallet looks like, how DKMS can solve some longstanding problems in wallet backup and recovery, and where DKMS is headed for standardization.","If you can't manage the keys for your DIDs (Decentralized Identifiers), then the SSI engine will never get started. That's why DKMS (Decentralized Key Management System) is one of the core open standards in the DID ""stack"".",http://ssimeetup.org/decentralized-key-management-dkms-essential-missing-piece-ssi-puzzle-drummond-reed-webinar-8/,https://i.imgur.com/5qc1qrG.png,Presentation,,,Decentralized Identity Stack,,,,,,,,2018-06-28,,,,,,,,,,,,,
+Verifiable Credentials,Wikipedia,,,,,,,,,Verifiable Credentials - Wikipedia,"Verifiable credentials (VCs) are the electronic equivalent of the physical credentials that we all possess today, such as: plastic cards, passports, driving licences, qualifications and awards, etc. The data model for verifiable credentials is a World Wide Web Consortium Recommendation, ""Verifiable Credentials Data Model 1.0 - Expressing verifiable information on the Web"" published 19 November 2019.",,https://en.wikipedia.org/wiki/Verifiable_credentials,https://upload.wikimedia.org/wikipedia/commons/thumb/5/51/VC_triangle_of_Trust.svg/1200px-VC_triangle_of_Trust.svg.png,wiki entry,,,About,,,,,,,,2023-04-25,,,,,,,,,,,,,
+Verifiable Credentials,Auth0,,,"Vittorio Bertocci, Filip Skokan",,,,,,"Identity, Unlocked... Explained: Season 2, Ep. 2","a conversation about a few three-letter extensions to OAuth (which, incidentally, would also fit well in a pirate incantation!): PAR, RAR, and JAR. Filip is a Senior Engineer II at Auth0, the author of a popular book on open source identification, and a contributor to both the [IETF](https://www.ietf.org/) and the [OpenID Foundation](https://openid.net/foundation/).<br>$5","PAR, RAR, and JAR with Filip Skokan",https://auth0.com/blog/identity-unlocked-explained-season-2-ep-2/,,Post,,,About,,,,,,,,2021-03-12,,,,,,,,,,,,,
+Verifiable Credentials,Digital Bazaar,,https://docs.google.com/presentation/d/1GMQy4rI093c_9zojwLRgp2r-fTscpDUSfX-wqwBk4j4/edit#slide=id.g3605fe1474_2_0,Manu Sporny,,,,,"IIW26, IIW",IIW26 Primer On DIDs and VCs,"A new type of globally resolvable, cryptographically-verifiable identifier, registered directly on a distributed ledger (aka Blockchain). Portable identifiers for any person, organization, or thing that does not depend on a centralized authority, are protected by cryptography, and enable privacy and data portability.",,https://docs.google.com/presentation/d/1GMQy4rI093c_9zojwLRgp2r-fTscpDUSfX-wqwBk4j4/edit#slide=id.g3605fe1474_2_0,https://i.imgur.com/TeMxwwW.png,Presentation,,,About,,,,,,,,2018-03-05,,,,,,,,,,,,,
+Verifiable Credentials,Evernym,,,Daniel Hardman,,,,,,A Gentle Introduction to Verifiable Credentials,"But while digital records are nothing new, today’s credentials come with certain ‘cryptographic superpowers’ that make them tamperproof, secure, and verifiable. Whereas a simple digital copy of a car title can easily be edited, a verifiable digital credential is one that has been issued by a trusted authority for, and only for, its holder.","What are verifiable credentials, and what requirements must they meet to conform to W3C specifications? Let's dig in.",https://www.evernym.com/blog/gentle-introduction-verifiable-credentials/,,Post,,,About,,,,,,,,2019-10-24,,,,,,,,,,,,,
+Verifiable Credentials,WebOfTrustInfo,,,,,,,,RWoT,A Verifiable Credentials Primer,"NOTE: ""Verifiable Claims"" are now known as ""Verifiable Credentials"". The W3C Verifiable Claims Working Group's experience with using the term ""Verifiable Claims"" demonstrated that it led to confusion in the marketplace. The group has since found consensus in shifting to use the term ""Verifiable Credentials"", which contain ""Claims"".",,https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/topics-and-advance-readings/verifiable-credentials-primer.md,,Paper,,,About,,,,,,,,2018-07-17,,,,,,,,,,,,,
+Verifiable Credentials,SSIMeetup,,,Tyler Ruff,,,,,,Verifiable Credentials 101 for SSI,"Tyler Ruff, product manager at Evernym, will be our next guest to walk us through Verifiable Credentials in the context of Self-Sovereign Identity. He will cover how they are created, issued and shared, as well as cover some common technical questions.","Tyler Ruff, product manager at Evernym, will be our next guest to walk us through Verifiable Credentials in the context of Self-Sovereign Identity. He will cover how they are created, issued and shared, as well as cover some common technical questions.",http://ssimeetup.org/verifiable-credentials-101-ssi-tyler-ruff-webinar-11/,,Presentation,,,About,,,,,,,,2018-09-12,,,,,,,,,,,,,
+Verifiable Credentials,Hackernoon,,,,,,,,,"Verifiable Credentials: What They Are, Why They Matter","From permanent resident cards to anonymous payments to automatic notarization, verifiable credentials and DIDs are a technology whose time has arrived. Use cases are currently being piloted; many will surface in coming months and years. Security on the internet as we know it may be broken, but it is not beyond saving. A touch of the cryptographic wand, and we'll be able to repair trust once more.",,https://hackernoon.com/verifiable-credentials-what-they-are-why-they-matter-kl133t3d,,Post,,,About,,,,,,,,2020-10-02,,,,,,,,,,,,,
+Verifiable Credentials,Arcblock,,,,,,,,,Understand Verifiable Cresidentials in 10 Minutes,"This article is a soft introduction into Verifiable Credentials and the potential use cases for organizations, businesses and government institutions and creating new levels of trust for individuals and the services/institutions they use.",Born for blockchain 3.0,https://www.arcblock.io/en/post/2020/04/15/verifiable-credentials,,Post,,,About,,,,,,,,2020-04-15,,,,,,,,,,,,,
+Verifiable Credentials,Affinidi,,,,,,,,,What are Verifiable Credentials,"At the most basic level, verifiable credentials, or VC in short, are tamper-proof credentials that can be verified cryptographically.",How W3C Verifiable Credentials (VC) Work: Part 1 – Issuance,https://academy.affinidi.com/what-are-verifiable-credentials-79f1846a7b9,,page,,,About,,,,,,,,2022-11-17,,,,,,,,,,,,,
+Verifiable Credentials,Personal,,,Michael Ruminer,, ,,,,The Role of Witness Organizations in Verifiable Credentials,The basis is that not every source of a verifiable credential has an interest in issuing verifiable credentials and that it is not only logical but beneficial to the ecosystem of trust that witness organizations will issue on behalf of these sources.,Verifiable credentials aren’t just P2P.. “On the Role of Witness Organizations in Verifiable Credentials” is published by Michael Ruminer.,https://medium.com/@m.ruminer/on-the-role-of-witness-organizations-in-self-sovereign-identity-or-vcs-aren-t-just-p2p-e2cbafce6928,https://miro.medium.com/v2/resize:fit:915/1*yKIkcfnadFv8uPblIsMk9g.png,Post,,,About,,,,,,,,2021-03-09,,,,,,,,,,,,,
+Verifiable Credentials,HackerNoon,,,,,,,,,An introductory dive into VCs (verifiable credentials),"Verifiable Credentials heavily utilize Decentralized Identifiers to identify people, organizations, and things and to achieve a number of security and privacy-protecting guarantees. They are issued and cryptographically signed documents, intended to be understood by computers rather than people.",,https://hackernoon.com/understanding-the-verifiable-credentials-vcs-it1535e9,,Post,,,About,,,,,,,,2021-04-28,,,,,,,,,,,,,
+Verifiable Credentials,Evernym,,,Brent Zundel,,,,,,How Does a Verifier Know the Credential is Yours?,"A link secret is a large random number, wrapped in a way that allows the holder to prove that they know the secret.",This post examine how link secrets bind a credential to its holder and enable powerful compound proofs without the risk of correlation.,https://www.evernym.com/blog/how-does-a-verifier-know-the-credential-is-yours/,https://www.evernym.com/wp-content/uploads/2021/08/linksecrets-social.png,Post,,,About,,,,,,,,2021-08-10,,,,,,,,,,,,,
+Verifiable Credentials,Ubisecure,,,Petteri Stenius,,,,,,Introduction to Verifiable Credentials,"The Verifiable Credentials specification is quite new, and many pieces that are required to create interoperable solutions are still incomplete or missing at time of writing. However, there is significant momentum around verifiable credentials (VCs). This is partly attributed to VCs being part of the solution for blockchain-based decentralised identity.","An introduction to the Verifiable Credentials concept, including the wallet analogy and privacy considerations - SSI and ZKP.",https://www.ubisecure.com/identity-management/verifiable-credentials/,,page,,,About,,,,,,,,2021-08-04,,,,,,,,,,,,,
+Verifiable Credentials,Affinidi,,,,,,,,,8 Reasons to use Verifiable Credentials,VCs are interoperable across many systems and can be used in almost every possible scenario.,"The growing digitalization of our lives means that we interact with thousands of apps, hundreds of companies, and possibly millions of users each year, depending on what we do online. While these…",https://academy.affinidi.com/8-reasons-to-use-verifiable-credentials-300833276b52,https://miro.medium.com/v2/resize:fit:1200/1*GlQVpv3oPkfNU2eNa9JdTQ.png,page,,,About,,,,,,,,2021-09-08,,,,,,,,,,,,,
+Verifiable Credentials,HelpNetSecurity,,,,,,,,,Verifiable credentials are key to the future of online privacy,"- All the data is decentralized, meaning there’s no need for a database of student records that could be jeopardized. Alice’s data lives with her.<br>- The employer doesn’t need to keep a copy of Alice’s transcript to verify her education.<br>- The college doesn’t play intermediary and doesn’t have access to the list of organizations Alice shares her data with. Other parties have no way of correlating this data as each exchange is private and unique.<br>- If desired, Alice could pick and choose what she wants to share. She could prove her degree without sharing her date of graduation or GPA, for example.",Verifiable credentials are the digital equivalents of the paper documents we carry in our wallets and prove who we are in the physical world.,https://www.helpnetsecurity.com/2021/07/26/verifiable-credentials/,,Post,,,About,,,,,,,,2021-07-26,,,,,,,,,,,,,
+Verifiable Credentials,IDCommons,,,"Stew Whitman, Alka Lachhwani",,,,,IIW,Self Attested vs Chain of Custody - assurance levels in data provenance in VCs,There are two important factors in establishing “truth” or the trustworthiness of the information. Attributional and Reputational. You need to have both to have trust.<br><br>Digital needs higher level of attestation because it is easier to forge and easier to propagate that forgery.,,https://iiw.idcommons.net/23G/_Self_Attested_vs_Chain_of_Custody_-_assurance_levels_in_data_provenance_in_VCs,,Session Notes,,,About,,,,,,,,2021-05-06,,,,,,,,,,,,,
+Verifiable Credentials,BLOCK6,,,Pranav Kirtani,,,,,,How a combination of Federated identity and Verifiable Credentials can help with Customer onboarding,"Before we dive into how Federated systems like OIDC and SAML along with Verifiable Credentials (VC) can help improve customer onboarding to your application, let us first understand what are the current methods being used for onboarding.","Before we dive into how Federated systems like OIDC and SAML along with Verifiable Credentials (VC) can help improve customer onboarding to your application, let us first understand what are the…",https://pranavkirtani.medium.com/how-a-combination-of-federated-identity-and-verifiable-credentials-can-help-with-customer-7e6518feb018,https://miro.medium.com/v2/resize:fit:1200/0*ENXUBvSdImT5qL_f,Post,,,About,,,,,,,,2022-07-27,,,,,,,,,,,,,
+Verifiable Credentials,Affinidi,,,,Open Badges,,,,,Compare and Contrast: OpenBadges vs Verifiable Credentials,"As we move towards a world of digital identity, many ways of sharing and verifying Personally Identifiable Information are emerging. Two such modes that we’ll talk about today are Open Badges and Verifiable Credentials.",Open Badges are a format for issuing digital badges while verifiable credentials are tamper-proof credentials for implementing self sovereign identity.,https://academy.affinidi.com/compare-and-contrast-openbadges-vs-verifiable-credentials-d504c054d5db,https://miro.medium.com/v2/resize:fit:1200/1*GfdafX7dlTbrOg57MvfIMA.png,page,,,Comparisons,,,,,,,,2022-11-17,,,,,,,,,,,,,
+Verifiable Credentials,Affinidi,,,,,,,,,Non-Fungible Tokens (NFTs) vs Verifiable Credentials (VCs),"A common thread that connects both NFTs and VCs is that they leverage the potential benefits of the digital world to give users more security, flexibility, and freedom to monetize.","Are Non-fungible tokens (NFTs) and Verifiable Credentials synonymous?  Well, NFTs verify the ownership of an object while VCs uniquely identify an entity.",https://academy.affinidi.com/non-fungible-tokens-nfts-vs-verifiable-credentials-vcs-cd0ebb13f1fb,https://miro.medium.com/v2/resize:fit:1200/1*SQxFteogQX5jwf-yC_y8eA.jpeg,page,,,Comparisons,,,,,,,,2022-11-17,,,,,,,,,,,,,
+Verifiable Credentials,CCG Mailing List,,,Michael Herman,,,,,,ERC-721 Non-Fungible Token Standard on Ethereum vs. VCs on Hyperledger Indy,When are Hyperledger Indy/Sovrin VCs better than Ethereum smart contracts for NFEs/NFTs (non-fungible entities/tokens)?<br><br>It seems obvious but I don't have a detailed/worked out answer.  One project I'm associated with wants to use the [ERC-721 Non-Fungible Token Standard](https://eips.ethereum.org/EIPS/eip-721) on Ethereum but I believe VCs are a better route to take. Part of the desire to stay on Ethereum is there is quite a vibrant NFT community on Ethereum and lots of different EC-721 tokens.,,https://lists.w3.org/Archives/Public/public-credentials/2021Feb/0059.html,,Discussion,,,Comparisons,,,,,,,Credentials Community Group,2021-02-11,,,,,,,,,,,,,
+Verifiable Credentials,Affinidi,,,,,,,,,Compare and Contrast — IRMA vs Verifiable Credentials,"IRMA [is] based on the Idemix technology. Idemix is a public-private key pair where the private key is used by the issuer to sign a credential and the public key is used by the verifier to establish that the credential is signed by the issuer and hence is authentic. [...] Verifiable credentials, or VC in short, are tamper-evident credentials that can be verified cryptographically.",Do you need a distributed ledger technology for implementing SSI? IRMA vs VCs can show different ways to implement self sovereign identity.,https://academy.affinidi.com/compare-and-contrast-irma-vs-verifiable-credentials-58e4b30d85f1,,page,,,Comparisons,,,,,,,,2022-11-17,,,,,,,,,,,,,
+Verifiable Credentials,IDCommons,,,Grace Rachmany,,,,,IIW,Could an NFT be a VC?,"Case discussed: A group of villages in Africa using a cryptocurrency platform for alternative currencies. Different organizations issue the coins under different circumstances. When you accept a currency, you want to know who is the issuer. The Red Cross might be more or less trusted than the local leader or agricultural cooperative as the issuer of a currency that is supposedly equivalent to a shilling.<br><br>What types of tech could be used for this?<br><br>- Multiple currencies on the blockchains<br>- Certifications in the form of some kind of NFT issued by the issuer.<br>- Limited supply tokens or NFTs that are “expired” when you use them<br>- Open Credential Publisher framework was suggested<br>- VCs are generally authorizations associated with a person, so maybe a person could have the VC and show their credit rating in some way while they are making a transaction<br>- Similarly maybe the VC belongs to the organization that is issuing the coin, proving its reputation over time.",,https://iiw.idcommons.net/20I/_Could_an_NFT_be_a_VC%3F,,Session Notes,,,Comparisons,,,,,,,,2021-05-06,,,,,,,,,,,,,
+Verifiable Credentials,Personal,,,Timothy Ruff,,,,,,How does VC Functional Stack compare to #ToIP Stack?,"1. ToIP Layers 2 & 3 compare to Functional Layer 2<br>2. ToIP Layer 4 compares to Functional Layers 3 & 4 (horizontal layer for VC Management, vertical layer for Applications)<br>3. Functional stack doesn't require #blockchain<br>4. Functional Stack doesn't detail steps for trust or verification; ToIP Stack doesn't separate management or storage<br>5. Functional Stack clarifies functions, roles, and potential business models; ToIP stack clarifies trust & security They are complementary, not contradictory.",,https://twitter.com/rufftimo/status/1301314001251438593,https://i.imgur.com/8zakrMQ.png,Thread,,,Comparisons,,,,,,,,2020-09-03,,,,,,,,,,,,,
+Verifiable Credentials,CCG Mailing List,,,Michael Herman,,,,,,What are VCs similar to?,"The chip in your e-passport is the analogy I’ve been most successful with<br>An issuer gives it to you.<br>You carry it around and show to whom you choose<br>The verifier can check its integrity without contacting the issuer<br>“A VC is like the chip in your passport - bit for any document type”<br>So far the best analogy I’ve found.  Policy makers say “ah, I see”",,https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0338.html,,Discussion,,,Comparisons,,,,,,,Credentials Community Group,2021-08-23,,,,,,,,,,,,,
+"Verifiable Credentials, Object Capabilities",fossandcrafts,,,,,,,,,Hygiene for a computing pandemic,"This episode of FOSS and Crafts features Christopher Lemmer Webber discussing the object capability security approach. Its a generalization not specific to VCs, continuing from the conversation on the CCG mailinglist, [Hygiene for a computing pandemic: separation of VCs and ocaps/zcaps](https://lists.w3.org/Archives/Public/public-credentials/2020Dec/0028.html), we shared last month.<br>",The podcast *show-notes include an epic list of references* supporting the discussion.,https://fossandcrafts.org/episodes/20-hygiene-for-a-computing-pandemic.html,,Post,,,"Comparisons, Main",,,,,,Object Capabilities,,2021-01-03,,,,,,,,,,,,,
+Verifiable Credentials,Personal,,https://lists.w3.org/Archives/Public/public-credentials/2021Jun/0244.html,"Kyle Den Hartog, Manu Sporny",,,,,,Re: The dangers of using VCs as permission tokens (was: PROPOSALs for VC HTTP API call on 2021-06-22),"Agreed, when it comes to the number of checks that occur it's much greater<br>because of the delegation. With that in mind, looking at the semantics only<br>of the system VCs in my opinion weren't optimally designed for permission<br>tokens. This difference between the two requires that an implementation<br>that wants to support both claims tokens and permissions tokens has to<br>grapple with the different mental model that arise when trying to stuff<br>these things together. This introduces additional complexity. Additionally<br>it leads to weird statements that are being made where it's difficult to<br>tell if the VC is behaving like a claims token or a permissions token.<br><br>Yes, exactly this. Exactly what Kyle states above is the reason why it's so complicated (and thus dangerous) to use VCs as permissions tokens.<br><br>This is one of the primary reasons that we separated out the Authorization Capabilities work from the Verifiable Credentials work. Things get really complicated when you start mixing authz/authn/claims/permissions into a Verifiable Credential. Just because you can do it doesn't mean you should",,https://kyledenhartog.com/example-authz-with-VCs/,,Post,,,Comparisons,,,,,,,,2021-06-24,,,,,,,,,,,,,
+"Verifiable Credentials, 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,VCWG,,,,,,,,,List of Implementations for the Verifiable Credentials Data Model,"<ul><li>Go<ul><li><a href=""https://github.com/TBD54566975/ssi-sdk/tree/main/credential"">Credential Manifest Builders</a> (DI &amp; JWT)</li><li><a href=""https://github.com/hyperledger/aries-framework-go"">Hyperledger Aries Framework Go</a> (DI &amp; JWT)</li></ul></li><li>Java<ul><li><a href=""https://github.com/danubetech/verifiable-credentials-java"">Verifiable Credentials Java</a> (DI &amp; JWT)</li></ul></li><li>JavaScript/TypeScript<ul><li><a href=""https://github.com/digitalbazaar/vc-js"">Verifiable Credentials JS Library</a> (DI)</li><li><a href=""https://github.com/transmute-industries/verifiable-data/tree/main/packages/vc.js"">Verifiable Data Credential JS Library with JWT</a> (DI &amp; JWT)</li><li><a href=""https://github.com/decentralized-identity/did-jwt-vc"">W3C Verifiable Credentials and Presentations in JWT format</a> (JWT)</li></ul></li><li>Kotlin<ul><li><a href=""https://github.com/microsoft/VerifiableCredential-SDK-Android"">Verifiable Credentials in Kotlin</a> (JWT)</li></ul></li><li>Python<ul><li><a href=""https://github.com/hyperledger/aries-cloudagent-python"">Hyperledger Aries Cloud Agent - Python (ACA-Py)</a> (DI &amp; JWT)</li></ul></li><li>Rust<ul><li><a href=""https://github.com/spruceid/didkit"">DIDKit</a> (DI &amp; JWT)</li></ul></li><li>Swift<ul><li><a href=""https://github.com/microsoft/VerifiableCredential-SDK-iOS"">Verifiable Credentials in Swift</a> (JWT)</li></ul></li></ul>",,https://github.com/w3c/verifiable-credentials/blob/main/implementations.md,,Page,,,Implementations,,,,,,,,2022-06-03,,,,,,,,,,,,,
+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,,,,,,,,,,,,,
+Verifiable Credentials,Ontology,,,,,,,,,Verifiable Claim Protocol,The entire workflow of the verifiable claim is shown in the figure below. It contains three major parts:<br><br>Request claim;<br>Issue claim;<br>Verify claim.,Ontology decentralized identification protocol based on W3C DID specifications. - ontology-DID/claim_spec.md at master · ontio/ontology-DID,https://github.com/ontio/ontology-DID/blob/master/docs/en/claim_spec.md,,Specification,,,Implementations,,,,,,,,2017-03-20,,,,,,,,,,,,,
+Verifiable Credentials,Crossword ,,,,Cybersecurity NGI,,,,,Crossword wins NGI Atlantic funds for Verifiable Credentials project,European Commission’s Next Generation Internet (NGI) initiative to lead a project to test the OpenID Foundation’s protocols for transferring verifiable credentials. Crossword’s partners in this project are Spruce Inc from the USA and Fraunhofer from Germany,,https://www.crosswordcybersecurity.com/post/next-generation-internet-grant-win,"https://static.wixstatic.com/media/082467_48feff2ccec04cb682e6101aefebd971~mv2.jpg/v1/fill/w_1000,h_563,al_c,q_85,usm_0.66_1.00_0.01/082467_48feff2ccec04cb682e6101aefebd971~mv2.jpg",Post,,,Implementations,,,,,,,,2022-08-04,,,,,,,,,,,,,
+Verifiable Credentials,Identity.com,,,,,,,,,Identity.com Verifiable Credential Library,"This Javascript Library provides functionality around Verifiable Credentials (VC), a W3C standard. Enables Validators to issue, Credential Wallets to verify, filter and Requesters to verify credentials.","Verifiable Credential and Attestation Library. Latest version: 3.0.2, last published: 4 months ago. Start using @identity.com/credential-commons in your project by running `npm i @identity.com/credential-commons`. There are 3 other projects in the npm registry using @identity.com/credential-commons.",https://www.npmjs.com/package/@identity.com/credential-commons,,code,,,Implementations,,,,,,,,2023-02-13,,,,,,,,,,,,,
+Verifiable Credentials,Personal,,,Samuel Smith,,,,,,VC Spec Enhancement Proposal,"the VC standard appears to be an adoption vector for Linked Data, not the other way around. My overriding interest is that the concept of a VC as a securely attributable statement is a very powerful and attractive one and therefore should be widely adopted. We should therefore be picking the best technologies that best support broad VC adoption, not the other way around.",,https://github.com/SmithSamuelM/Papers/blob/master/whitepapers/VC_Enhancement_Strategy.md,,Paper,,,Literature,,,,,,,,2022-04-04,,,,,,,,,,,,,
+Verifiable Credentials,Personal,,,Phil Windley,,,,,,Verifiable Credential Exchange,"Multi-source identity (MSI) depends on issuing, exchanging, and verifying digital credentials. The specification for verifiable credentials is being formulated by the World Wide Web Consortium’s Verifiable Credentials Working Group. Verifiable credentials provide a standard way to express credentials in a way that is cryptographically secure, privacy respecting, and automatically verifiable.","Verifiable credential exchange is the foundation of decentralized, online identity. This post describes how it works.",https://www.windley.com/archives/2018/12/verifiable_credential_exchange.shtml,https://www.windley.com/archives/2018/12/claim_issuing_and_presenting.png,Post,,,Literature,,,,,,,,2018-12-10,,,,,,,,,,,,,
+Verifiable Credentials,"Service-centric Networking, Telekom Innovation Laboratories, Technische Universiät Berlin",,,"Zoltán András Lux, Felix Beierle, Sebastian Zickau, Sebastian Göndör",,,,,,Full-text Search for Verifiable Credential Metadata on Distributed Ledgers,"The proposed solution is able to find credential types based on textual input from the user by using a full-text search engine and maintaining a local copy of the ledger. Thus, we do not need to rely on information about credentials coming from a very large candidate pool of third parties we would need to trust, such as the website of a company displaying its own identifier and a list of issued credentials. We have also proven the feasiblity of the concept by implementing and evaluating a prototype of the full-text credential metadata search service.",,https://arxiv.org/abs/1909.02895,,Paper,,,Literature,,,,,,,,2019-09-06,,,,,,,,,,,,,
+Verifiable Credentials,NDSS Symposium,,,,,,,,,Enabling Decentralised Identifiers and Verifiable Credentials for Constrained IoT Devices using OAuth-based Delegation,"Abstract—Decentralised identifiers (DIDs) and verifiable credentials (VCs) are upcoming standards for self-sovereign privacypreserving identifiers and authorisation, respectively. This focus on privacy can help improve many services and open up new business models, but using DIDs and VCs directly on constrained IoT devices can be problematic due to the management and resource overhead. This paper presents an OAuth-based method to delegate the processing and access policy management to the Authorisation Server thus allowing also systems with constrained IoT devices to benefit from DIDs and VCs.",,https://www.ndss-symposium.org/wp-content/uploads/diss2019_05_Lagutin_paper.pdf,,Post,,,Literature,,,,,,,,2020-06-08,,,,,,,,,,,,,
+Verifiable Credentials,"Service-centric Networking, Technische Universitat Berlin, Telekom Innovation Laboratories, Deutsche Telekom",,,"Zoltán András Lux, Dirk Thatmann, Sebastian Zickau, Felix Beierle",,,,,,Distributed-Ledger-based Authentication with Decentralized Identifiers and Verifiable Credentials,"Authentication with username and password is becoming an inconvenient process for the user. End users typically have little control over their personal privacy, and data breaches effecting millions of users have already happened several times. We have implemented a proof of concept decentralized OpenID Connect Provider by marrying it with Self-Sovereign Identity, which gives users the freedom to choose from a very large pool of identity providers instead of just a select few corporations, thus enabling the democratization of the highly centralized digital identity landscape. Furthermore, we propose a verifiable credential powered decentralized Public Key Infrastructure using distributed ledger technologies, which creates a straightforward and verifiable way for retrieving digital certificates.",,https://arxiv.org/abs/2006.04754,,Paper,,,Literature,,,,,,,,2020-06-06,,,,,,,,,,,,,
+Verifiable Credentials,WebofTrustInfo,,,,,,,,RWoT,Addition of Proof Request/Response to a formal Verifiable Credentials specification,"The W3C Verifiable Credentials (hereafter VC) specification does not currently outline how credential data should be requested by a Verifier. This document outlines the approach taken at Workday and proposes it as an addition or companion to the VC spec.<br><br>At RWoT we wish to present our approach in order to get community feedback and consensus. Workday recently announced our credentialing platform and will shortly begin to issue credentials within our market verticals. We fully intend to support the community standards around credentialing and therefore wish to drive consensus in the community on a simple, standard approach for requesting and sharing VCs between a holder and verifier.","RWOT9 in Prague, The Czech Republic (September 2019) - rwot9-prague/verifiable-credentials-proof-request.md at master · WebOfTrustInfo/rwot9-prague",https://github.com/WebOfTrustInfo/rwot9-prague/blob/master/topics-and-advance-readings/verifiable-credentials-proof-request.md,,Paper,,,Literature,,,,,,,,2019-08-26,,,,,,,,,,,,,
+Verifiable Credentials,Personal,,,Tsuyoshi Matsuzaki,,,,,,Verifiable Credentials (DID Credential Flows) : Technical Overview,"In the perspective of W3C specification, verifiable credential (VC) doesn’t rely on DID specification. (i.e, The “id” property used in VC shouldn’t be necessarily a DID.) However, in its real implementations, it might be expected that verifiable credentials will resolve DIDs with consistent decentralized manners and technologies. Then, in this post, we also assume that DID is used with verifiable credentials.<br><br>In order to explain things plainly, I’ll include not only VC flows, but also other parts of flows, such as, DID flows or OpenID compliant flows.","Microsoft has launched ION hosting (beta) on Bitcoin mainnet, and new verifiable credentials service (private preview) on Azure Active Directory (Azure AD). In this post, I will summarize what is verifiable credentials and how it works. This style of identity and credentials are very much like our physical world. I hope this future credential backed…",https://tsmatz.wordpress.com/2020/06/25/what-is-verifiable-credentials/,https://tsmatz.files.wordpress.com/2020/09/20200902_issuer_did.jpg,Post,,,Literature,,,,,,,,2020-06-25,,,,,,,,,,,,,
+Verifiable Credentials,CCG Mailing List,,,Kerri Lemoie,,,,,,Add Your VC-EDU Use Cases,"For Github users, submit your use cases as issues here: [https://github.com/w3c-ccg/vc-ed-use-cases/issues](https://github.com/w3c-ccg/vc-ed-use-cases/issues)<br><br>This template can help guide you: [https://github.com/w3c-ccg/vc-ed-use-cases/blob/main/.github/ISSUE_TEMPLATE/use-case-template.md](https://github.com/w3c-ccg/vc-ed-use-cases/blob/main/.github/ISSUE_TEMPLATE/use-case-template.md)",,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0296.html,,Discussion,,,Use Case,,,,,,,Credentials Community Group,2021-07-30,,,,,,,,,,,,,
+Verifiable Credentials,Personal,,,Kerri Lemoie,,,,,,W3C Verifiable Credentials Education Task Force 2022 Planning,"We’ve been hard at work writing use cases, helping education standards organizations understand and align with VCs, and we’ve been heading towards a model recommendation doc for the community.","At the W3C VC-EDU Task Force we’ve been planning meeting agendas and topics for 2022. We’ve been hard at work writing use cases, helping education standards organizations understand and align with…",https://kayaelle.medium.com/w3c-verifiable-credentials-education-task-force-2022-planning-efc9b07cc2a3,,Post,,,Use Case,,,,,,,,2022-01-18,,,,,,,,,,,,,
+Verifiable Credentials,The Paypers,,,,,,,,,Better digital living with blockchain-backed verifiable credentials,"The NHS can now provide you with a digital verifiable credential to prove your vaccination status, securely stored in the NHS app and easily accessible, generating a QR code to prove to airlines and employers that you are fit to fly or work. But this is just the first step in the development of an enabling technology that can bring benefits to many areas of modern life.",Better digital living with blockchain-backed verifiable credentials,https://thepaypers.com/expert-opinion/better-digital-living-with-blockchain-backed-verifiable-credentials--1250869,,Post,,,Use Case,,,,,,,,2021-08-06,,,,,,,,,,,,,
+Verifiable Credentials,Velocity Network,,,,,,,,,On Climate Crisis and Self-Sovereign Verifiable Career Credentials,"This rich verifiable self-sovereign career identity will be the ‘great transformer’ of the global labor market. It will change the way people navigate their careers and livelihoods, and how employers make talent decisions.","Reinventing how career records are shared across the global market. Empowering individuals, businesses and educational institutions through transformational blockchain technology – public, open, trusted and self-sovereign. Turn career achievements into digital credentials. Verified, secured and truly global. Own them, use them to access better opportunities.",https://www.velocitynetwork.foundation/on-climate-crisis-and-self-sovereign-verifiable-career-credentials/,,Post,,,Use Case,,,,,,,,2021-08-12,,,,,,,,,,,,,
+Verifiable Credentials,Dock,,,,,,,,,The World of Anonymous Credentials,"A credential is called a verifiable credential when its authenticity can be cryptographically checked by anyone because the credential contains a cryptographic signature by the issuer, and the issuer's public key is well known.","The main idea in anonymous credentials is that rather than considering the credential data as arbitrary bytes which are then signed by the issuer, anonymous credentials adds ""structure"" to the credential.",https://blog.dock.io/anonymous-credentials/,,Post,,,Use Case,,,,,,,,2022-01-20,,,,,,,,,,,,,
+Verifiable Credentials,LTO Network,,,,Sphereon,,,,,25 Use Cases for Verifiable Credentials,"Age-related Goods or Services, Verifying Educational Qualifications, Employment Endorsements, Background Checks, Protecting your Identity Papers, Validity of Visas, Health Checks, Sharing Health Data and Medical Records, COVID Tests for Safe Travel, Generating Boarding Pass, Checking Tickets, Access to Events or Restricted Spaces, Application for Credit Cards, Checking Eligibility for Rentals, Application for Utility Connections, Access to Services, Applying and Approving Loans, Selling/Buying a Property, Computing the Insurance Premiums, Submitting and Handling of Claims, Using Death Certificates, Driving Offences, Web shop onboarding and access, Loyalty Programs, B2B Trade",,https://drive.google.com/file/d/1BrFjh6-TVkJ4Rfllh5fUTjh6hkYtPbR_/view,,Paper,,,Use Case,,,,,,,,2021-05-11,,,,,,,,,,,,,
+Verifiable Credentials,CCG Mailing List,,,Michael Herman,,,,,,Verifiable Credential Notarization and Third-Party Notary Services Providers: User Scenarios,User Scenario A: Alice self-issues a blood pressure home reading (BPHR) credential to Dr. Bob's Clinic using SOVRONA's credential notarization services. SOVRONA is a third-party notary services provider/network.<br><br>User Scenario B: The Province of Sovronia issues a Sovronia Driver's License to Alice using SOVRONA's credential notarization services. SOVRONA is a third-party notary services provider/network.,,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0109.html,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/att-0109/image003.jpg,user journies,,,Use Case,,,,,,,Credentials Community Group,2021-07-15,,,,,,,,,,,,,
+Verifiable Credentials,IDCommons,,,"Gena Morgan, Kevin Dean",IDCommons,,,,IIW,Verifiable Credentials for Authentic Data in the Supply Chain,"Using DiDs and VCs for verifiable product data in supply chains, leveraging the largest supply chain standard system in the world,<br><br>2.5 million users companies, over 6 billion product scans per day<br><br>Product data and attestations from a number of various authoritative sources<br><br>Leverage DIDs/VCs for distributed data sharing, verification",,https://iiw.idcommons.net/10G/_Verifiable_Credentials_for_Authentic_Data_in_the_Supply_Chain,,Session Notes,,,Use Case,,,,,,,,2021-05-06,,,,,,,,,,,,,
+Verifiable Credentials,IDCommons,,,Mahmoud Alkhraishi,IDCommons,,,,IIW,Verifiable Credentials for Assets,General Framework on how to think of VCs for Assets including leveraging GS1 and other vocabularies in the traceability vocab.<br><br>Requirements and Opportunities that block adoption of VCs in Supply chains,,https://iiw.idcommons.net/21E/_Verifiable_Credentials_for_Assets_30_min,,Session Notes,,,Use Case,,,,,,,,2021-05-07,,,,,,,,,,,,,
+VCs Development,W3C,Verifiable Credentials Working Group,https://www.w3.org/2020/01/vc-wg-charter.html,,,,,,,Verifiable Credentials Working Group,The mission of the Verifiable Credentials (formerly known as Verifiable Claims) Working Group (VCWG) is to make expressing and exchanging credentials that have been verified by a third party easier and more secure on the Web.<br><br>The Chairs of the Working Group are Kristina Yasuda and Brent Zundel. The W3C Staff Contact for the Working Group is Ivan Herman.,,https://www.w3.org/2017/vc/WG/,,Working Group,,,Verifiable Credentials Working Group,,,,,,,,2017-04-14,https://github.com/w3c/verifiable-claims,,,https://lists.w3.org/Archives/Public/public-vc-wg/,,,,,,https://lists.w3.org/Archives/Public/public-vc-wg/,,,
+VCs Development,VCWG,,,Manu Sporny,,,,,,Verifiable Credentials Data Model v1.1 is an official W3C standard!,"It's official, the Verifiable Credentials Data Model v1.1 is a W3C standard!<br><br>  Verifiable Credentials Data Model v1.1<br>  https://www.w3.org/TR/2022/REC-vc-data-model-20220303/<br><br>This was largely a maintenance release of the specification. The list of (minor) revisions since the v1.0 release can be found here:https://www.w3.org/TR/2022/REC-vc-data-model-20220303/#revision-history",,https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0005.html,,Specificationification,,,Verifiable Credentials Working Group,,,,,,,Credentials Community Group,2022-03-03,,,,,,,,,,,,,
+VCs Development,VCWG,,,,,,,,,Verifiable Credentials Data Model v1.1,"Credentials are a part of our daily lives; driver's licenses are used to assert that we are capable of operating a motor vehicle, university degrees can be used to assert our level of education, and government-issued passports enable us to travel between countries. This specification provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.","Driver's licenses are used to claim that we are capable of operating a motor vehicle, university degrees can be used to claim our education status, and government-issued passports enable holders to travel between countries. This specification provides a standard way to express these sorts of claims on the Web in a way that is cryptographically secure, privacy respecting, and automatically verifiable.",https://www.w3.org/TR/2022/REC-vc-data-model-20220303/,https://www.w3.org/TR/2022/REC-vc-data-model-20220303/diagrams/ecosystem.svg,Specificationification,RECOMMEND,,Verifiable Credentials Working Group,,,,,,,Verifiable Credentials Working Group,2022-03-03,,,,,,,,,,,,,
+VCs Development,VCWG,,,,,,,,,Verifiable Credentials Data Model v2.0,- The components that constitute a [verifiable credential](https://www.w3.org/TR/2022/WD-vc-data-model-2.0-20220811/%23dfn-verifiable-credentials),"Credentials are a part of our daily lives; driver's licenses are used to assert that we are capable of operating a motor vehicle, university degrees can be used to assert our level of education, and government-issued passports enable us to travel between countries. This specification provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.",https://www.w3.org/TR/vc-data-model-2.0/,https://www.w3.org/TR/vc-data-model-2.0/diagrams/zkp-cred-pres.svg,Specificationification,DRAFT,,Verifiable Credentials Working Group,,,,,,,Verifiable Credentials Working Group,2023-05-20,,,,,,,,,,,,,
+VCs Development,VCWG,,,,,,,,,Verifiable Credential Data Integrity 1.0,"This specification describes mechanisms for ensuring the authenticity and integrity of Verifiable Credentials and similar types of constrained digital documents using cryptography, especially through the use of digital signatures and related mathematical proofs.",,https://www.w3.org/TR/vc-data-integrity/,https://www.w3.org/TR/vc-data-integrity/diagrams/hiw-verification.svg,Specification,Working Draft,,Verifiable Credentials Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-05-15,,,,,,,,,,,,,
+VCs Development,VCWG,,,,,,,,,Verifiable Credentials Status List v2021,"This specification describes a privacy-preserving, space-efficient, and high-performance mechanism for publishing status information such as suspension or revocation of Verifiable Credentials.",,https://www.w3.org/TR/vc-status-list/,https://www.w3.org/TR/vc-status-list/diagrams/StatusList2021.svg,Specification,Working Draft,,Verifiable Credentials Working Group,,,,,,,Verifiable Credentials WG,2023-04-27,,,,,,,,,,,,,
+VCs Development,VCWG,,,,,,,,,Verifiable Credentials Implementation Guidelines 1.0,"This guide provides some examples and resources for implementing protocols which make use of verifiable credentials, beyond those available in the core specification.",,https://w3c.github.io/vc-imp-guide/,https://w3c.github.io/vc-imp-guide/diagrams/subject-ne-holder.svg,Guidance,Note,,Verifiable Credentials Working Group,,,,,,,Verifiable Credentials Working Group,2023-02-03,https://github.com/w3c/vc-imp-guide,,,,,,,,,,,,
+VCs Development,VCWG,,,,,,,,,W3C Verifiable Credentials WG Test Suite,"Any conforming implementation MUST pass all tests in the test suite. There are multiple test suites, each of which is detailed below. You can review the current draft implementation report.",,https://w3c.github.io/vc-test-suite/,,Code,,,Verifiable Credentials Working Group,,,,,,,Verifiable Credentials Working Group,2021-10-31,https://github.com/w3c/vc-test-suite/,,,,,,,,,,,,
+VCs Development,VCWG,,,,,,,,,Verifiable Credentials Use Cases,"This document does NOT attempt to define an architecture for the support of Verifiable Claims. Instead it expresses the sorts of needs that real users have that could be addressed through support for some sort of self-sovereign claim environment. It attempts to use terminology that is consistent with the other deliverables of the Verifiable Claims Working Group (you can see the relevant terms in Appendix A).<br><br>The use cases outlined here are provided in order to make progress toward possible future standardization and interoperability of both low- and high-stakes claims with the goals of storing, transmitting, and receiving digitally verifiable proof of attributes such as qualifications and achievements. The use cases in this document focus on concrete scenarios that the technology defined by the group should address.","A verifiable claim is a qualification, achievement, quality, or piece of information about an entity's background such as a name, government ID, payment provider, home address, or university degree. Such a claim describes a quality or qualities, property or properties of an entity which establish its existence and uniqueness. The use cases outlined here are provided in order to make progress toward possible future standardization and interoperability of both low- and high-stakes claims with the goals of storing, transmitting, and receiving digitally verifiable proof of attributes such as qualifications and achievements. The use cases in this document focus on concrete scenarios that the technology defined by the group should address.",https://www.w3.org/TR/vc-use-cases/,https://i.imgur.com/J2IgVgl.png,Specification,Note,,Verifiable Credentials Working Group,,,,,,,Verifiable Credentials Working Group,2019-09-24,https://github.com/w3c/vc-use-cases,,,,,,,,,,,,
+VCs Development,VCWG,,,,,,,,,Verifiable Credentials Data Model Implementation Report 1.0,The purpose of this document is to demonstrate that there are at least two interoperable implementations of processors that are capable of generating output that is conformant to the Verifiable Credentials Data Model.,,https://w3c.github.io/vc-test-suite/implementations/,,Report,,,Verifiable Credentials Working Group,,,,,,,,2021-10-30,,,,,,,,,,,,,
+VCs Development,VCWG,,,,,,,,,The Verifiable Credential Specifications Directory,"This document serves as an unofficial directory for all known Verifiable Credential specifications whether they are released by a global standards setting organization, a community group, an open source project, or an individual.",,https://w3c.github.io/vc-specs-dir/,,registry,,,Verifiable Credentials Working Group,,,,,,,Verifiable Credentials WG,2023-04-08,https://github.com/w3c/vc-specs-dir/tree/main/specifications,,,,,,,,,,,,
+VCs Development,VCWG,,,,,,,,,ECDSA Cryptosuite v2019,This specification describes a Data Integrity Cryptosuite for use when generating a digital signature using the Elliptic Curve Digital Signature Algorithm (ECDSA) based on the Standards for Efficient Cryptography over prime fields using a verifiably random Elliptic Curve (secpr1).,,https://www.w3.org/TR/vc-di-ecdsa/,,Specification,Working Draft,,Verifiable Credentials Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-05-18,,,,,,,,,,,,,
+VCs Development,VCWG,,,,,,,,,EdDSA Cryptosuite v2022,This specification describes a Data Integrity cryptographic suite for use when creating or verifying a digital signature using the twisted Edwards Curve Digital Signature Algorithm (EdDSA) and Curve25519 (ed25519).,,https://www.w3.org/TR/vc-di-eddsa/,,Specification,Working Draft,,Verifiable Credentials Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-05-18,,,,,,,,,,,,,
+VCs Development,VCWG,,,,,,,,,BBS Cryptosuite v2023,This specification describes the BBS+ Signature Suite created in 2023 for the Data Integrity specification. The Signature Suite utilizes BBS+ signatures to provide the capability of zero knowledge proof disclosures.,,https://www.w3.org/TR/vc-di-bbs/,,Specification,Working Draft,,Verifiable Credentials Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-05-18,,,,,,,,,,,,,
+VCs Development,VCWG,,,,,,,,,JSON Web Signatures for Data Integrity Proofs,This specification describes a JSON Web Signature Suite created in 2020 for the Verifiable Credentials Data Integrity Proof specification. The Signature Suite utilizes Detached JWS signatures to provide support for a subset of the digital signature algorithms registered with IANA.,,https://www.w3.org/TR/vc-jws-2020/,,Specification,Working Draft,,Verifiable Credentials Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-01-27,,,,,,,,,,,,,
+VCs Development,VCWG,,,,,,,,,Securing Verifiable Credentials using JSON Web Tokens,This specification defines how Verifiable Credentials can be represented as JSON Web Tokens (JWT) [RFC7519] and secured using JSON Web Signatures (JWS) [RFC7515].,,https://www.w3.org/TR/vc-jwt/,,Specification,Working Draft,,Verifiable Credentials Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-05-15,,,,,,,,,,,,,
+VCs Development,W3C,CCG,https://w3c-ccg.github.io/,,"Verifiable Credentials, Decentralized Identifiers",,,,,Credentials Community Group,"The mission of the Credentials Community Group is to 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. Our tasks include drafting and incubating Internet specifications for further standardization and prototyping and testing reference implementations.",,https://www.w3.org/community/credentials/,,Working Group,,,Credentials Community Group,,,,,,,Credentials Community Group,2014-08-19,https://github.com/w3c-ccg/community,,,https://lists.w3.org/Archives/Public/public-credentials/,,,,,,,,,
+VCs Development,CCG,,,,,,,,,W3C CCG meeting transcripts,"This repo contains the meeting archives for the W3C-CCG (Credentials Community Group), including transcripts based on the IRC logs and audio files for our regular meetings, ancillary material such as slide presentations, etc. The archives for 2014-2019 can be found here.",COMMUNITY: W3C Credentials Community Group meeting transcripts - GitHub - w3c-ccg/meetings: COMMUNITY: W3C Credentials Community Group meeting transcripts,https://github.com/w3c-ccg/meetings,,Page,,,Credentials Community Group,,,,,,,,,,,,,,,,,,,,,
+VCs Development,CCG,,,,,,,,"RWOT, IIW",W3C CCG announcements,Announcements and events associated with the W3C Credentials CG,,https://github.com/w3c-ccg/announcements,,Page,,,Credentials Community Group,,,,,,,,,,,,,,,,,,,,,
+VCs Development,CCG,,,,,,,,,W3C CCG Work Item Process,"This lets you write your specs in markdown, or technically bikeshed -- a markdown document, with special extensions understood by the bikeshed tool. The bikeshed tool is run on-commit via the spec-prod github action, generating the familiar ""spec looking"" ReSpec format. ReSpec is just html with a javascript ReSpec library.",,https://github.com/w3c-ccg/workitem-process,,Page,,,Credentials Community Group,,,,,,,,,,,,,,,,,,,,,
+VCs Development,CCG,,,,"Global Open Badges Workgroup, Verifiable Credentials WG, Credentials Commiunity Group, Schema.org",,,,,WORK ITEM: Drafts and Ideas of Educational and Occupational Verifiable Credentials - w3c-ccg/edu_occ_verifiable_credentials,"Work on describing credentials is occurring within the IMS Global Open Badges Workgroup, W3C Verifiable Credentials Working Group, W3C Credentials Commiunity Group, Educational and Occupational Credentials in Schema.org Community Group, and Credential Engine/CTDL.<br><br>This effort will result in requirements, use cases, and/or draft specs to be formalized in the appropriate standards group",,https://github.com/w3c-ccg/edu_occ_verifiable_credentials,,Code,,,Credentials Community Group,,,,,,,Credentials Community Group,,,,,,,,,,,,,,
+VCs Development,CCG,,,,,,,,,WORK ITEM: Verifiable Credentials Examples,"This GitHub Pages Website hosts example credentials, as well as documents needed to construct them. When contributing an example, you are encouraged to provide everything needed to generate an verify a credential. Do your best not to include ANY broken links or missing documentation. If possible, try to make the credential id resolvable as well.",,https://github.com/w3c-ccg/vc-examples,,Code,,,Credentials Community Group,,,,,,,Credentials Community Group,,,,,,,,,,,,,,
+VCs Development,CCG,,Verifiable Credentials Extension Registry,,,,,,,Verifiable Credentials Extension Registry,- This document contains a list of all known Verifiable Credential extensions and their associated specifications. Credentials Community Group,,https://w3c-ccg.github.io/vc-extension-registry/,,Report,draft,,Credentials Community Group,,,,,,,Credentials Community Group,2022-11-14,,,,,,,,,,,,,
+VCs Development,CCG,,Verifiable Credentials Extension Registry,Markus Sabadello,,,,,,Ed25519Signature2018,This specification describes a standard signature suite created in 2018 for the Linked Data Signatures [LD-SIGNATURES] specification. It uses the RDF Dataset Normalization Algorithm [RDF-DATASET-NORMALIZATION] to transform the input document into its canonical form. It uses SHA-256 [RFC6234] as the message digest algorithm and Ed25519 [ED25519] as the signature algorithm.,,https://w3c-ccg.github.io/lds-ed25519-2018/,,Report,draft,,Credentials Community Group,,,,Proof Methods,,,Credentials Community Group,2021-07-23,,,,,,,,,,,,,
+VCs Development,CCG,,Verifiable Credentials Extension Registry,"Manu Sporny, Dave Longley",,,,,,RsaSignature2018,This specification describes the RSA Signature Suite created in 2018 for the Linked Data Signatures [LD-SIGNATURES] specification. It uses the RDF Dataset CANONICALIZATION Algorithm [RDF-DATASET-CANONICALIZATION] to transform the input document into its canonical form. It uses SHA-256 [RFC6234] as the message digest algorithm and the RS256 algorithm defined in JSON Web Signatures [RFC7515] as the signature algorithm.,,https://w3c-ccg.github.io/lds-rsa2018/,,Report,draft,,Credentials Community Group,,,,Proof Methods,,,Credentials Community Group,2020-05-26,,,,,,,,,,,,,
+VCs Development,CCG,,Verifiable Credentials Extension Registry,"Manu Sporny, Dave Longley",,,,,,CredentialStatusList2017,A simple list-based mechanism for publishing and checking the status of a credential,,https://w3c-ccg.github.io/vc-csl2017/,,Report,,,Credentials Community Group,,,,Status Methods,,,Credentials Community Group,2020-12-29,,,,,,,,,,,,,
+VCs Development,CCG,,,,,,,,,Ecdsa Secp256k1 Signature 2019,This specification describes the Ecdsa Secp256k1 Signature created in 2019 for the Linked Data Signatures specification,,https://w3c-ccg.github.io/lds-ecdsa-secp256k1-2019/,,Code,Draft,,Credentials Community Group,,,,,,,,2020-04-08,,,,,,,,,,,,,
+VCs Development,CCG,,,,,,,,,Verifiable Credential JSON Schemas,"The [VC_DATA_MODEL](https://www.w3.org/TR/vc-data-model/) specifies the models used for Verifiable Credentials and Verifiable Presentations, and explains the relationships between three parties: issuer, holder, and verifier. A critical piece of infrastructure out of the scope of those specifications is the Credential Schema.",A mechanism to use JSON Schemas with Verifiable Credentials - GitHub - w3c/vc-json-schema: A mechanism to use JSON Schemas with Verifiable Credentials,https://github.com/w3c-ccg/vc-json-schemas,,Code,,,Credentials Community Group,,,,,,,,2023-05-24,,,,,,,,,,,,,
+VCs Development,CCG,,,,,,,,,Traceability Vocabulary v0.1,"This specification describes a Linked Data vocabulary for asserting Verifiable Credentials related to supply chain and other traceability information, similar to what is often referred to as ""provenance"", including country of origin, chemical properties, mechanical properties, and other attributes of products and materials. VCs using these terms can then be used to help determine the legitimacy of organizations participating in global trade and the status of the products and materials described therein",,https://w3c-ccg.github.io/traceability-vocab/,https://w3c-ccg.github.io/traceability-vocab/resources/product-identifier-verification-from-identification-key-license.png,Specification,v0.1,,Credentials Community Group,,,,,,,Credentials Community Group,2023-05-23,,,,,,,,,,,,,
+VCs Development,DIF,,,,,,,,,Claims and Credentials Working Group,"Join this group to contribute to the standards and technology that create, exchange, and verify claims and credentials in a decentralized identity ecosystem. For example, a cryptographically verifiable credential that proves an individual has a college degree or is of a certain age. Our members focus on specs that are vendor agnostic and based on industry standards.",,https://identity.foundation/working-groups/claims-credentials.html,,page,,,Claims and Credentials Working Group,,,,,,,,2020-09-18,,,,,,,,,,,,,
+VCs Development,DIF,,,,,,,,,presentation-exchange,Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions,Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions (Presentation Submission) - GitHub - decentralized-identity/presentation-exchange: Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions (Presentation Submission),https://github.com/decentralized-identity/presentation-exchange,,Code,,,Claims and Credentials Working Group,,,,,,,,2023-05-31,,,,,,,,,,,,,
+VCs Development,DIF,,,,,,,,,presentation-request,Requirements Analysis and Protocol Design for a VC Presentation Request Format,Requirements Analysis and Protocol Design for a VC Presentation Request Format - GitHub - decentralized-identity/presentation-request: Requirements Analysis and Protocol Design for a VC Presentation Request Format,https://github.com/decentralized-identity/presentation-request,,Code,,,Claims and Credentials Working Group,,,,,,,,2020-01-08,,,,,,,,,,,,,
+VCs Development,DIF,,,,,,,,,Credential Manifest,"Credential Manifests do not themselves define the contents of the output credential(s), the process the Issuer uses to evaluate the submitted inputs, or the protocol Issuers, Subjects, and their User Agents rely on to negotiate credential issuance. Instead, Credential Manifests are a data model for issuers to publish and/or send individually to would-be holders, allowing the software of the latter to understand and negotiate an issuance process.",,https://identity.foundation/credential-manifest/,,page,,,Claims and Credentials Working Group,,,,,,,,2023-05-04,,,,,,,,,,,,,
+VCs Development,Personal,,,Kyle Den Hartog,,,,,,Example Design of an Authorization System with Verifiable Credentials and the Tradeoffs,"The primary focus of this blog post is to highlight the different problems that are likely to occur when going down the path of building an authorization system with verifiable credentials. I’ll be sure to keep things at a higher level so that anyone can understand these tradeoffs, but take you through the details that would be thought through by an architect designing the system.",,https://kyledenhartog.com/example-authz-with-VCs/,,Post,,,Development,,,,,,,,2021-06-22,,,,,,,,,,,,,
+VCs Development,51 Nodes,,,,,,,,,Indexing and Querying Revoked Verifiable Credentials,this article describes a simple approach to revoke verifiable credentials and a decentralized and efficient way to index and query those revoked credentials using the [Graph protocol](https://thegraph.com/en/).,"Due to its immutability and censorship resistance, the Blockchain seems to be a suitable place to manage identities and credentials. However, querying the data on the blockchain in a trusted and…",https://medium.com/51nodes/indexing-and-querying-revoked-verifiable-credentials-e229dc2781d4,,Post,,,Development,,,,,,,,2022-07-01,,,,,,,,,,,,,
+VCs Development,CCG Mailing List,,,Nikos Fotiou  ,,,,,,VC Issuance based on OAuth 2.0,"We design, implement, and evaluate a solution for achieving continuous authorization of HTTP requests exploiting Verifiable Credentials (VCs) and OAuth 2.0. Specifically, we develop a VC issuer that acts as an OAuth 2.0 authorization server, a VC verifier that transparently protects HTTP-based resources, and a VC wallet implemented as a browser extension capable of injecting the necessary authentication data in HTTP requests without needing user intervention.",,https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0084.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2022-04-14,,,,,,,,,,,,,
+VCs Development,CCG Mailing List,,,Orie Steele,,,,,,Supporting VC-JWT and BBS+ Presentation Exchange in the VC-HTTP-API,"[https://github.com/OR13/GNARLY](https://github.com/OR13/GNARLY)  (while we wait for a better name...)<br><br>This demo API and Spec has a number of improvements over the current<br><br>VC-HTTP-API, including tested support for VC-JWT, JsonWebSignature2020 and<br><br>BBS+ Selective Disclosure Presentation Exchange.",,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0313.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-07-31,,,,,,,,,,,,,
+VCs Development,CCG Mailing List,,https://lists.w3.org/Archives/Public/public-credentials/2021Sep/0141.html,Joe Andrieu,,,,,,Updated VC-API diagram for Supply Chain flow,I updated the supply chain version of the data flow diagram for verification. ,,https://lists.w3.org/Archives/Public/public-credentials/2021Sep/0141.html,https://i.imgur.com/mH5TBtU.png,Discussion,,,Development,,,,,,,Credentials Community Group,2021-09-28,,,,,,,,,,,,,
+VCs Development,CCG Mailing List,,,Manu Sporny,,,,,,re: VC API: handling large documents client to server,"Typical solutions to this problem require that you put the binary data outside of the VC, if at all possible. This works well for common static images such as logos. It is also possible to split the VC into two VCs... one with the machine-readable data from the issuer (with a digital signature) and one with the image data from any source (without a digital signature, since, if hashlinked, the signature will verify the validity of the image data). That latter approach can be more privacy preserving AND more complex than many might feel is necessary.",,https://lists.w3.org/Archives/Public/public-credentials/2022Feb/0035.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2022-02-10,,,,,,,,,,,,,
+VCs Development,CCG Mailing List,,,Manu Sporny,,,,,,VC-API interoperability test suites ready for experimental integration,* [The VC API test suite for basic issuer interop is here](https://w3c-ccg.github.io/vc-api-issuer-test-suite/)<br>* [The VC API test suite for basic verifier interop is here](https://w3c-ccg.github.io/vc-api-verifier-test-suite/)<br>* [The Data Integrity test suite for Ed25519Signature2020 interop is here](https://w3c-ccg.github.io/di-ed25519-test-suite/),,https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0126.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2022-04-26,,,,,,,,,,,,,
+VCs Development,CCG Mailing List,,,Manu Sporny,,,,,,Cross-industry VC API test suite achieves first multi-vendor interop for issue/verify,We are happy to announce today that we have our first demonstration of cross-vendor interoperability between Danube Tech and Digital Bazaar for the VC Issuer API and VC Verifier API. The test suites test the OAS definition files (which are used to generate the specification):<br>* [2.1 Verify Credential - Data Integrity](https://w3c-ccg.github.io/vc-api-verifier-test-suite/#Verify%20Credential%20-%20Data%20Integrity)<br>* [2.1 Issue Credential - Data Integrity](https://w3c-ccg.github.io/vc-api-issuer-test-suite/#Issue%20Credential%20-%20Data%20Integrity),,https://lists.w3.org/Archives/Public/public-credentials/2022May/0041.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2022-05-18,,,,,,,,,,,,,
+VCs Development,CCG Mailing List,,,Joe Andrieu,,,,,,Diagrams for VC HTTP API work [was Re: [AGENDA] VC HTTP API Work Item - August 17th 2021],"a. *Holder* The entity who holds the VC once issued and later presents it for verification.<br>b. *Holder Application *The software or service that allows holders to manage their credentials. Often called a wallet. For symmetry, it could be called a Holder Service.<br>c. *Storage Service *The software or service that actually stores VCs long term (on behalf of the holder)<br>d. *Issuer Role* The website or software that provides issuing functionality to a holder on behalf of that issuer)<br>e. *Issuer Service* Software or service that actually signs VCs and VPs) This component is used by both the issuer  (to mint VCs) and the holder (to create VPs for presentation)<br>f. *Verifier Role* The website or software that uses a Verification Service as part of its decision making process for providing services to holders.<br>g. *Verifier Service *The software or service that verifies VCs and VPs by checking proofs and checking status.",,https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0231.html,https://i.imgur.com/4hCNLVA.png,Discussion,,,Development,,,,,,,Credentials Community Group,2021-08-16,,,,,,,,,,,,,
+VCs Development,CCG Mailing List,,,Brian Richter,,,,,,Issuer API Cross Trust Boundary Scoping - VC-HAPI (f.k.a. VC-HTTP-API),I think I'm starting to understand how RAR fits into this picture. This decision can be made for us by punting the question to the authorization process entirely. With RAR we can force the user to authorize for the actual subject they are issuing the credential about. Is Alice authorized to issue VCs with claims about did:example:12345? To answer that question Alice asks for a token with the following RAR request,,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0263.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-07-24,,,,,,,,,,,,,
+VCs Development,CCG Mailing List,,,Justin Richer,,,,,,RAR Structures for VC HTTP API,"It seemed like a good idea when I first invented it a decade ago:[https://blue-button.github.io/blue-button-plus-pull/#scopes](https://blue-button.github.io/blue-button-plus-pull/#scopes) or when it got pulled into other efforts like [https://openid.net/specs/openid-heart-fhir-oauth2-1_0-2017-05-31.html](https://openid.net/specs/openid-heart-fhir-oauth2-1_0-2017-05-31.html)… and Orie even suggested the following set of parameterized scopes for this API:<br>'create:credentials': Grants permission to create credentials<br>'derive:credentials': Grants permission to derive credentials<br>'create:presentations': Grants permission to create presentations<br>'verify:presentations': Grants permission to verify presentations<br>'exchange:presentations': Grants permission to exchange presentations<br>So what’s the problem? I can say with full confidence after years of experience building and deploying systems to support parameterized scopes like this that they are fragile, awkward, and lead to insecure corner cases.",,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0208.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-07-21,,,,,,,,,,,,,
+VCs Development,CCG Mailing List,,,Manu Sporny,,,,,,Bikeshed: Renaming the VC HTTP API,"the fundamental issue is that stringing a bunch of consonants together (""HTTP"") rarely leads to something easy to say in conversation.",,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0131.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-07-17,,,,,,,,,,,,,
+VCs Development,CCG Mailing List,,,Kerri Lemoie,,,,,,Question About Signatures & Contexts,Is a VC still considered to be valid if it contains fields that are not described in its context file(s)? Does it depend on the signature type?,,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0290.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-07-30,,,,,,,,,,,,,
+VCs Development,CCG Mailing List,,,Bob Wyman,,,,,,Any Good use case of PAM (Privileged account Management) using Vcs,"A common example of this is when someone uses a ""Power of Attorney,"" to sign a contract. When they do, they typically sign documents with their own names and an annotation ""on behalf of,"" ""for,"" or ""by power of attorney,"" they don't forge the signature of the one who granted the power of attorney.",,https://lists.w3.org/Archives/Public/public-credentials/2021Nov/0028.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-11-06,,,,,,,,,,,,,
+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,,,,,,,,,,,,,
+Decentralized Identifiers,DIDWG,,https://w3c-ccg.github.io/did-wg-charter/,,W3C,,,,,Decentralized Identifier Working Group,"The mission of the Decentralized Identifier Working Group is to standardize the DID URI scheme, the data model and syntax of DID Documents, which contain information related to DIDs that enable the aforementioned initial use cases, and the requirements for DID Method specifications.",,https://www.w3.org/2019/did-wg/,,Working Group,,,Main,,,,,,,,2019-05-31,https://github.com/w3c/did-wg,,,,,,,,,,,,
+Decentralized Identifiers,DIDWG,,,,,,,,,Decentralized Identifier (DID) 1.0 Specification - Data Model and Syntax,"This document specifies the DID syntax, a common data model, core properties, serialized representations, DID operations, and an explanation of the process of resolving DIDs to the resources that they represent.","Decentralized identifiers (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity. 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.",https://w3c.github.io/did-core/,https://w3c.github.io/did-core/diagrams/did_detailed_architecture_overview.svg,Specification,,,Main,,,,,,,Decentralized Identifier WG,2022-07-19,https://github.com/w3c/did-core,,,,,,,,,,,,
+Decentralized Identifiers,DIDWG,,,,,,,,,DID Specification Registries,"This document serves as an official registry for all known global parameters, properties, and values used by the Decentralized Identifier ecosystem.",,https://w3c.github.io/did-spec-registries/,,Registry,,,Main,,,,,,,DID Working Group,2023-05-14,https://github.com/w3c/did-spec-registries,,,,,,,,,,,,
+Decentralized Identifiers,Personal,,,Adam Powers,,,,,,Understanding Decentralized IDs (DIDs),"This article starts off with an overview of DIDs, DID Documents, Verifiable Claims and DIDAuth — basically laying out how the technology works. It then explores the economics of DIDs to try and understand what problems they propose to solve, for whom, and how they go about solving them.","Decentralized identifiers (DIDs) came to my attention at the last Internet Identity Workshop (IIW), where it seemed like 30% of all presentations were about DIDs. I feel like I’m a latecomer to the…",https://medium.com/@adam_14796/understanding-decentralized-ids-dids-839798b91809,https://miro.medium.com/v2/resize:fit:1200/1*lHXvR78dlN63nbyYKu7z_Q.png,Post,,,Explainer,,,,,,,,2018-06-02,,,,,,,,,,,,,
+Decentralized Identifiers,Personal,,https://docs.google.com/document/d/1Ym85y_bDVN9xkRZ-oD-zlUUIeZjVGWNihfZBk2GQidk/edit,Michael Herman,,,,,,What is a DID? The Path from an id (DID) to a Real-Life Subject,"The following graphic illustrates the path (flow) of a client app trying to: a) communicate/interact with, and/or b) access the metadata about a real-life subject by using a Decentralized Identifier (id (DID)).<br>That is, in (almost) 10 steps or less, how to you get from an id (DID) attribute on the left to a Real-Life Subject on the right?",Hyperledger Indy/Sovrin/DID Comprehensive Architecture Reference Model (INDY ARM) - Draft document for discussion purposes - indy-arm/README.md at master · mwherman2000/indy-arm,https://github.com/mwherman2000/indy-arm/blob/master/README.md#appendix-e---did-resolution-path-from-a-did-to-a-real-life-subject-,,Page,,,Explainer,,,,,,,,2019-05-19,,,,,,,,,,,,,
+Decentralized Identifiers,Affinidi,,,,,,,,,Demystifying Decentralized Identifiers (DIDs),"- Does not require a centralized registration authority<br>- Many DIDs use the distributed ledger technology or any other decentralized network, though it is not mandatory<br>- It is a permanent identifier because it does not depend on a single third-party or centralized registry for its existence.<br><br>- Can be cryptographically verified<br>- They connect a DID subject (the entity identified by the DID) with a DID document (a set of data that describes the DID subject) to enable the subject to have trustable interactions.<br>- They are interoperable and portable, provided they conform to the existing standards laid down by W3C",Self-Sovereign Identity (SSI) gives users control over how their data is stored and shared and a building block of SSI is Decentralized Identifiers (DIDs).,https://academy.affinidi.com/demystifying-decentralized-identifiers-dids-2dc6fc3148fd,https://miro.medium.com/v2/resize:fit:1200/1*D5oqVHELQBRxW4AcasQepA.png,Post,,,Explainer,,,,,,,,2021-05-05,,,,,,,,,,,,,
+Decentralized Identifiers,Hackernoon,,,,,,,,,Decentralized Identifiers (DIDs) - A Deeper Dive,"The same way the SSL/TLS protocol changed internet use forever by opening a gate to the world of encrypted Web traffic, which is the basis for the protocol that keeps the web safe and secure HTTPS; the same way will DIDs enhance the verification process in world of blockchain, such as decentralized finance.",,https://hackernoon.com/decentralized-identifiers-dids-a-deeper-dive-04383442,,Post,,,Explainer,,,,,,,,2021-04-26,,,,,,,,,,,,,
+Decentralized Identifiers,Elastos,,,,,,,,,Decentralized Identity: Why Are DIDs The Future of Digital Identity Management?,You need to create separate digital identity credentials for each one. Only after you’ve registered with them can you access the services of each organization. And don’t forget: all free-to-use apps and websites control the storage of your data and are happy to sell access to it to third parties for profit. That’s literally their business plan: they understand the value of your data and how they can monetize it.,"We have more accounts than we can recall, and each one stores our data on central servers. With a DID (decentralized identity), you can own your own data. Discover why blockchain-based digital identities are the future of digital identity management...",https://elastos.info/decentralized-identity-dids/,,Post,,,Explainer,,,,,,,,2021-10-14,,,,,,,,,,,,,
+Decentralized Identifiers,Impervious,,,,,,,,,"Decentralized Identifiers: Implications for Your Data, Payments and Communications","Through the DID Specification, service endpoints and DIDComm, Impervious has interlaced DIDs with Bitcoin Lightning, IPFS, WebRTC and resilient relays to introduce a new peer-to-peer internet standard with practical applications for mitigating censorship and surveillance risk.",,https://newsletter.impervious.ai/decentralized-identifiers-implications-for-your-data-payments-and-communications-2/,,Post,,,Explainer,,,,,,,,2022-03-22,,,,,,,,,,,,,
+Decentralized Identifiers,WebOfTrustInfo,,,,,,,,rwot02-2020,DID Whitepaper,"A DID architecture should focus on the set of components that Mr. Gupta refers to as ""the minimum required for people to be able to do business (or other critical functions) together"".<br><br>**A Decentralized Identifier (DID) Registry and Discovery Service**<br><br>This ""minimum required"" is defined by a union of the proposed requirements identified by the W3C Credential Community Group, the XDI.org Registry Working Group, and the Rebooting the Web of Trust group. It consists of three functions that can be addressed by a combination of blockchain and DHT technology:<br><br>- A DID registration function<br>- A discovery function that enables looking up a registered DID in the blockchain<br>- A master key recovery function",,https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/DID-Whitepaper.md,,Paper,,,Literature,,,,,,,,2016-05-18,,,,,,,,,,,,,
+Decentralized Identifiers,IETF,,,,,,,,,A Universally Unique IDentifier (UUID) URN Namespace,"A UUID is 128 bits long, and can guarantee uniqueness across space and time.  UUIDs were originally used in the Apollo Network Computing System and later in the Open Software Foundation's (OSF) Distributed Computing Environment (DCE), and then in Microsoft Windows platforms",,https://www.ietf.org/rfc/rfc4122.txt,,Specification,,,Literature,,,,,,,,2005-07,,,,,,,,,,,,,
+Decentralized Identifiers,2ndQuadrant,,,Tomas Vondra,,,,,,All you need to know about sequential UUID generators,"UUIDs are a popular identifier data type – they are unpredictable, and/or globally unique (or at least very unlikely to collide) and quite easy to generate. Traditional primary keys based on sequences won’t give you any of that, which makes them unsuitable for public identifiers, and UUIDs solve that pretty naturally.","sequential-uuids extension introduces generators of sequential UUIDs, addressing some of the common issues - random I/O patterns and WAL write amplification",http://web.archive.org/web/20190320121253/https://blog.2ndquadrant.com/sequential-uuid-generators/,,Post,,,Literature,,,,,,,,2019-03-02,,,,,,,,,,,,,
+Decentralized Identifiers,WebofTrustInfo,,,"Drummond Reed, Manu Sporny, others",,,,,rwot05-boston,DID Primer,"At a superficial level, a decentralized identifier (DID) is simply a new type of globally unique identifier with special features designed for blockchains. But at a deeper level, DIDs are actually the tip of the iceberg -- or the tip of the spear -- of an entirely new layer of decentralized digital identity and public key infrastructure (PKI) for the Internet. This decentralized public key infrastructure (DPKI) could have as much impact on global cybersecurity and cyberprivacy as the development of the SSL/TLS protocol for encrypted Web traffic (now the largest PKI in the world).",,https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/draft-documents/did-primer.md,,Paper,,,Literature,,,,,,,,2017-10-06,,,,,,,,,,,,,
+Decentralized Identifiers,WebofTrustInfo,,,"Drummond Reed, Manu Sporny, others",,,,,rwot07-toronto,DID Primer Extended,- Background on the origin of DIDs and the DID specification.<br>- How DIDs differ from other globally-unique identifiers.<br>- How the syntax of DIDs can be adapted to work with any modern blockchain.<br>- How DIDs resolve to DID documents containing public keys and service endpoints.<br>- The key role that DID methods play in the implementation of DID infrastructure.,,https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/topics-and-advance-readings/did-primer-extended.md,,Paper,,,Literature,,,,,,,,2019-02-14,,,,,,,,,,,,,
+Decentralized Identifiers,DIDWG,,,Markus Sabadello,Decentralized Identifiers,,,,,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<br>- did:sov:3k9dg356wdcj5gf2k9bw8kfg7a<br>- Modular specifcation using “methods”:<br>- did:sov, did:btcr, did:v1, did:uport, ...<br>- Can be pairwise unique for each relationship<br>- Resolution: DID → DID Document",,https://www.w3.org/2018/vocabws/presentations/Sabadello.pdf,,Presentation,,,Literature,,,,,,,DID Working Group,2018-04-17,,,,,,,,,,,,,
+Decentralized Identifiers,WebofTrustInfo,,,,Decentralized Identifiers,,,,rwot02-2020,Requirements for DIDs,"Respect Network is conducting a research project for the U.S. Department of Homeland Security, HSHQDC-16-C-00061, to analyze the applicability of blockchain technologies to a decentralized identifier system. Our thesis is that blockchains, or more generically distributed ledgers, are a potentially powerful new tool for “identity roots” — the starting points for an Internet identity. However “blockchain identity” may not fully address the core security and privacy principles needed in a complete identity system. In this case DIDs — Decentralized Identifiers rooted on a distributed ledger — may end up being a foundational building block for higher level identity management solutions.",,https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/final-documents/requirements-for-dids.pdf,,Paper,,,Literature,,,,,,,,2016-08-24,,,,,,,,,,,,,
+Decentralized Identifiers,WebofTrustInfo,,,,Decentralized Identifiers,,,,rwot07-toronto,DIDs in DPKI,"- DPKI stands for Decentralized Public-key Infrastructure<br>- DPKI seeks to serve as an improved alternative/replacement for X.509 (that thing securing today's Internet)<br>- DPKI changes the web's security model from 1000s of single-points-of-failure to decentralized consensus groups that create namespaces (sorta like what blockchains do!)<br>- DPKI is not a blockchain — it's a protocol for securely accessing blockchains and similar decentralized consensus systems<br>- DPKI has Top-Level Domains (TLDs) representing different blockchains (e.g. .eth, .bit, .id etc.)",,https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/dids-in-dpki.md,,Paper,,,Literature,,,,,,,,2018-08-23,,,,,,,,,,,,,
+Decentralized Identifiers,"SRI International, NIST, FIMSA",,,,Decentralized Identifiers,,,,,Cryptography Review of W3C VC Data Model and DID Standards and Implementation Recommendations,"Cryptography used by U.S. government entities in operational systems must conform to relevant federal government standards and requirements, including the Federal Information Security Management Act (FISMA) and National Institute of Technology (NIST) standards for use of cryptography. As part of its in-depth technical due-diligence to enable operational capabilities for DHS/CBP, DHS/PRIV and DHS/USCIS, the U.S. Department of Homeland Security’s Silicon Valley Innovation Program (SVIP) sponsored independent nonprofit research center SRI International to conduct a cryptographic review of the W3C Verifiable Credentials Data Model and W3C Decentralized Identifiers standards. The review provided constructive feedback and recommendations for technology developers and W3C standards developers to increase their level of compliance with federal government standards.",,https://web.archive.org/web/20230319062836/https://www.csl.sri.com/papers/vcdm-did-crypto-recs/,,Paper,,,Literature,,,,,,,,2023-03-19,,,,,,,,,,,,,
+Decentralized Identifiers,DIDWG,,,,,,,,,Decentralized Identifier Use Cases and Requirements v1.0,"This document sets out use cases and requirements for a new kind of identifier that meets all these basic requirements: decentralized, persistent, cryptographically verifiable, resolvable",,https://w3c.github.io/did-use-cases/,https://w3c.github.io/did-use-cases/images/didUse.svg,Draft,,,Literature,,,,,,,Decentralized Identifier WG,2021-06-16,https://github.com/w3c/did-use-cases,,,,,,,,,,,,
+Decentralized Identifiers,DIDWG,,,,,,,,,Decentralized Identifiers (DIDs) v0.13 Data Model and Syntaxes,"DIDs resolve to DID Documents — simple documents that describe how to use that specific DID. Each DID Document may express cryptographic material, verification methods, and/or service endpoints. These provide a set of mechanisms which enable a DID controller to prove control of the DID. Service endpoints enable trusted interactions with the DID subject.<br><br>This document specifies a common data model, format, and operations that all DIDs support.",,https://www.w3.org/2019/08/did-20190828/,,Report,,,Literature,,,,,,,Decentralized Identifier WG,2019-09-13,,,,,,,,,,,,,
+Decentralized Identifiers,DIDWG,,,,,,,,,DID Implementation Guide,"This document acts as a technical narrative for the implementation of DID methods and is expected to cover many topics related to that subject that a developer may wish to consider, including guidance around implementation details that may also be used for third party evaluation of an authored DID method via the DID-RUBRIC.",,https://w3c.github.io/did-imp-guide/,https://w3c.github.io/did-imp-guide/diagrams/representation-specific-and-foreign-entries.png,Note,,,Literature,,,,,,,DID Working Group,2021-11-04,https://github.com/w3c/did-imp-guide,,,,,,,,,,,,
+Decentralized Identifiers,DIDWG,,,,,,,,,W3C DID Test Suite and Implementation Report,"This document describes the did core test suite, and summarizes the latest test results.",,https://w3c.github.io/did-test-suite/,,Internal,,,Literature,,,,,,,DID Working Group,2023-01-17,https://github.com/w3c/did-test-suite,,,,,,,,,,,,
+Decentralized Identifiers,DIDWG,,,,,,,,,W3C Decentralized Characteristics Rubric v1.0,This rubric presents a set of criteria which an Evaluator can apply to any DID Method based on the use cases most relevant to them. We avoid reducing the Evaluation to a single number because the criteria tend to be multidimensional and many of the possible responses are not necessarily good or bad. It is up to the Evaluator to understand how each response in each criteria might illuminate favorable or unfavorable consequences for their needs.,,https://w3c.github.io/did-rubric/,,Internal,,,Literature,,,,,,,DID Working Group,2022-01-11,https://github.com/w3c/did-rubric,,,,,,,,,,,,
+Decentralized Identifiers,DIDWG,,,,,,,,,Well Known DID Configuration,The DID Configuration resource provides proof of a bi-directional relationship between the controller of an origin and a DID via cryptographically verifiable signatures that are linked to a DID's key material. This document describes the data format of the resource and the resource location at which origin controllers can publish their DID Configuration.,"This repo contains proposals and links to proposals for .well-known uris related to DIDs, Hubs and Agents. See IETF RFC5785 for more details on Defining Well-Known Uniform Resource Identifiers.",https://identity.foundation/.well-known,,Specification,,,Supporting,,,,,,,DID Working Group,2020-12-10,https://github.com/decentralized-identity/.well-known,,,,,,,,,,,,
+Decentralized Identifiers,CCG,,,,,,,,,Decentralized Identifier Resolution (DID Resolution) v0.3,"DID resolution is the process of obtaining a DID document for a given DID. This is one of four required operations that can be performed on any DID (""Read""; the other ones being ""Create"", ""Update"", and ""Deactivate""). The details of these operations differ depending on the DID method. Building on top of DID resolution, DID URL dereferencing is the process of retrieving a representation of a resource for a given DID URL. Software and/or hardware that is able to execute these processes is called a DID resolver.",,https://w3c-ccg.github.io/did-resolution/,https://w3c-ccg.github.io/did-resolution/diagrams/https-dereference-example-1.png,Specification,,,Supporting,,,,,,,Credentials Community Group,2023-01-18,https://github.com/w3c-ccg/did-resolution,,,,,,,,,,,,
+Decentralized Identifiers,GoDiddy,,https://iiw.idcommons.net/2C/_godiddy.com_-_Universal_DID_Services,Markus Sabadello,,,,,,godiddy.com - Universal DID Services,"Basic functions are creating, resolving, updating, and deactivating DIDs across multiple DID methods and networks. Advanced functions include key management, search, transfer of DIDs, lookup of historical DID document versions, notification of DID-related events, and more.",,https://godiddy.com,,site,,,Supporting,,,,,,,,2021-05-06,,,,,,,,,https://docs.godiddy.com/,https://api.godiddy.com/,,,
+Decentralized Identifiers,IDCommons,,,Markus Sabadello,,,,,,Standard Interfaces for DID Create/Update/Deactivate,"- There is an attempt to specify abstract interfaces if you want to Create/Update/Deactivate a did that could be implemented for all did methods.<br>- The idea of this specification is to provide a standard with the same assumptions as with resolution. It should be in an abstract level, meaning it should specify the inputs and outputs of creating/updating/deactivating a did but not how it should be implemented.",,https://iiw.idcommons.net/3C/_Standard_Interfaces_for_DID_Create/Update/Deactivate,,Session Notes,,,Supporting,,,,,,,,2021-07-17,,,,,,,,,,,,,
+Decentralized Identifiers,W3C,,,,,,,,,DID test suite,"DID test suite is not for runtime, but the Universal Resolver could do a few simple checks on a driver's responses. But there's also a philosophical question: Should the Universal Resolver be ""allowed"" to check and potentially transform driver responses, or should it just ""pass through"" everything that comes from a driver?",,https://github.com/w3c/did-test-suite,,Code,,,Supporting,,,,,,,,2023-01-17,,,,,,,,,,,,,
+Decentralized Identifiers,Personal,,,Micheal Herman,,,,,,BlueToque Tools Toolkit,"BlueToque Tools is a collection of software tools for working with DID Method Namespaces, DID Identifiers, DID Documents, DID Agent Service Endpoints, DID Agent Servers, DID Agent Clusters, and DID Objects (the 7 DIDs). The flagship tool is didlang, a language for interactively working with the 7 DIDs.",,https://github.com/mwherman2000/BlueToqueTools,,Code,,,Supporting,,,,,,,,2022-12-06,,,,,,,,,,,,,
+DID Methods,Legendary Requirements,,,,,,,,,did:directory,"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.<br><br>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.<br><br>Different DID methods use different underlying mechanisms with different performance, security, and privacy tradeoffs.",,https://diddirectory.com/,,Directory,,,Main,,,,,,,,,,,,,,,,,,,,,
+DID Methods,DIDWG,,,,Decentralized Identifiers,,,,,DID Specification Registries,This table summarizes the DID method specifications currently in development. The links will be updated as subsequent Implementer’s Drafts are produced.,,https://w3c-ccg.github.io/did-method-registry/#the-registry,,registry,,,Main,,,,,,,DID Working Group,2023-05-14,,,,,,,,,,,,,
+DID Methods,Transmute,,,Margo Johnson,Decentralized Identifiers,,,,,DID:Customer,"While we are committed to providing optionality to our customers, it’s equally important to communicate the selection criteria behind these options so that customers can consider the tradeoffs of underlying DID-methods alongside the problem set they’re solving for.","Transmute builds solutions that solve real business problems. For this reason, we support a number of different decentralized identifier (DID) methods. While we are committed to providing optionality…",https://medium.com/transmute-techtalk/did-customer-4ca8b7957112,,Post,,,Main,,,,,,,,2020-10-30,,,,,,,,,,,,,
+DID Methods,WebOfTrustInfo,,,"Joe Andrieu, Shannon Appelcline, Amy Guy, Joachim Lohkamp, Drummond Reed, Markus Sabadello, Oliver Terbu, Kai Wagner",Decentralized Identifiers,,,,rwot9-prague,A Rubric for Decentralization of DID Methods,"The communities behind Decentralized Identifiers (DIDs) bring together a diverse group of contributors, who have decidedly different notions of exactly what “decentralization” means. For some, the notion of a DID anchored to DNS is anathema, for others, DIDs that cannot be publicly verified are problematic. This debate about decentralization is a continuation of a similar, ongoing argument in cryptocurrency circles: the question of whether or not bitcoin or ethereum is more decentralized is a nearly endless source of argument. Rather than attempting to resolve this potentially unresolvable question, we propose a rubric — which is a scoring guide used to evaluate performance, a product, or a project — that teaches how to evaluate a given DID method according to one’s own requirements. Our goal is to develop a guide that minimizes judgment and bias. Rather than advocating particular solutions, the rubric presents a series of criteria which an evaluator can apply to any DID method based on their particular use cases. We also avoid reducing the evaluation to a single number because the criteria tend to be multidimensional and many of the options are not necessarily good or bad: it is the obligation of the evaluator to understand how each response in each criteria might illuminate favorable or unfavorable consequences for their needs. Finally, this rubric allows evaluating aspects of decentralization of a DID method, but it is not exhaustive, and does not cover other issues that may affect selection or adoption of a particular method, such as privacy or efficiency.","RWOT9 in Prague, The Czech Republic (September 2019) - rwot9-prague/decentralized-did-rubric.md at master · WebOfTrustInfo/rwot9-prague",https://github.com/WebOfTrustInfo/rwot9-prague/blob/master/draft-documents/decentralized-did-rubric.md,,Paper,,,Main,,,,,,,,2019-09-06,,,,,,,,,,,,,
+DID Methods,IDCommons,,"https://iiw.idcommons.net/13D/_We_evaluated_7_DID_methods_with_the_W3C_DID_Rubric!_did:btcr,_did:sov,_did:ion,_did:web,_did:key,_did:peer,_did:ethr",,Decentralized Identifiers,,,,IIW,DID Method Rubric v1.0,This rubric presents a set of criteria which an Evaluator can apply to any DID Method based on the use cases most relevant to them. We avoid reducing the Evaluation to a single number because the criteria tend to be multidimensional and many of the possible responses are not necessarily good or bad. It is up to the Evaluator to understand how each response in each criteria might illuminate favorable or unfavorable consequences for their needs.,,https://w3c.github.io/did-rubric/,,Guidance,Draft,,Main,,,,,,,,2022-01-11,,,,,,,,,,,,,
+DID Methods,IDCommons,,"https://iiw.idcommons.net/13D/_We_evaluated_7_DID_methods_with_the_W3C_DID_Rubric!_did:btcr,_did:sov,_did:ion,_did:web,_did:key,_did:peer,_did:ethr","Walid Fdhila, Markus Sabadello","did:btcr, did:sov, did:ion, did:web, did:key, did:peer, did:ethr, Decentralized Identifiers",,,,IIW,DID Methods Evaluation Report,This report evaluates a selection of DiD methods using the guidelines specified in the W3C DiD method Rubric V1.0 (draft 06 January 2021). The evaluation reflects the authors’ opinion based on documents and source code that are publicly available. The report mainly includes a comprehensive evaluation.,"Web word processing, spreadsheets and presentations",https://docs.google.com/document/d/1jP-76ul0FZ3H8dChqT2hMtlzvL6B3famQbseZQ0AGS8//,,Report,,,Main,,,,,,,,2021-04-04,,,,,,,,,,,,,
+DID Methods,IDCommons,,"https://iiw.idcommons.net/13D/_We_evaluated_7_DID_methods_with_the_W3C_DID_Rubric!_did:btcr,_did:sov,_did:ion,_did:web,_did:key,_did:peer,_did:ethr","Walid Fdhila, Markus Sabadello",Decentralized Identifiers,,,,IIW,Critera for DID Method Evaluation,The criteria selected for did evaluation are derived from (i) did rubric and (ii) principles of SSI.<br>(i) https://w3c.github.io/did-rubric/<br>(ii) https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/self-sovereign-identity-principles.md,,https://docs.google.com/document/d/1vAKtMrsrjO_tLQhah8tRoLaIS7HpOIE6xM38ZoBpgWU/,,Guidance,,,Main,,,,,,,,2021-05,,,,,,,,,,,,,
+DID Methods,CCG Mailing List,,,Steve Capell,,,,,,DID methods as W3C standards - a happy compromise?,can't we pick just a small number of un-controversial methods to standardise?  even if it's just did:key and did:web to start with.,,https://lists.w3.org/Archives/Public/public-credentials/2022Feb/0117.html,,Discussion,,,Discussion,,,,Methods as Standards,,,,2022-02-22,,,,,,,,,,,,,
+DID Methods,CCG Mailing List,,,Manu Sporny,,,,,,Re: CCG Community opinions needed to define CCG scope (specifically re: did methods as work items),"Heather Vescent wrote:<br>1. What are the *pros* of including did methods as work items in the CCG?<br>Community vetting and approval of particular DID Methods.<br><br>Basically, broader and deeper review of DID Methods that we expect to be of great use to the world. I expect there will be DID Methods that the community wants to eventually propose as DID Methods for standardization (did:key and<br><br>did:web feel like two ones where we could get consensus on doing so).",,https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0376.html,,Discussion,,,Discussion,,,,Methods as Standards,,,,2021-08-26,,,,,,,,,,,,,
+DID Methods,ArcBlock,did:abt:,,,,,,,,did:abt:,"One of our main goal is to protect users’ privacy. So people do not use the DID generated from their master key to talk to DAPPs, instead, the WALLET automatically generates an extended DID according to the user’s master DID and the DAPP’s DID and use this extended DID to communicate with the DAPP.",ABT DID Protocol,https://arcblock.github.io/abt-did-spec/,,Specification,,ABT Network,DID Methods,,,,,,,,2019-10-11,https://github.com/arcblock/abt-did-spec/,,,,,,,,,,,,
+DID Methods,CCG,did:btcr:,,"Christopher Allen, Ryan Grant, Kim Hamilton Duffy",,,,,,did:btcr:,"The Bitcoin Reference DID method (did:btcr) supports DIDs on the public Bitcoin blockchain. The Bitcoin Reference method has minimal design goals: a DID trust anchor based on the Bitcoin blockchain, updates publicly visible and auditable via Bitcoin transactions, and optionally, additional DID Document information referenced in the transaction OP_RETURN data field. No other Personal Identifiable Information (PII) would be placed on the immutable blockchain.<br>A secondary intent of the BTCR method is to serve as a very conservative, very secure example and some best practices for creating a DID method. The use cases for BTCR are focused on anonymous and pseudo-anonymous identities, web-of-trust style webs of identity, and absolute mimimal personal information disclosure. Other DID methods will likely need to loosen these standards.<br>Some aspects of the BTCR method will not be practical if inappropriately scaled — for instance, there is a transaction cost to update keys and DDO object, potential UTXO inflation (i.e. one additional unspent output for every BTCR-based identity), and even if segwit isn’t used it could cause blockchain bloat. However, identities using the BTCR method can be a strong as Bitcoin itself -- currently securing billions of dollars of digital value.",,https://w3c-ccg.github.io/didm-btcr/,https://w3c-ccg.github.io/didm-btcr/diagrams/btcr-tx-ref.png,Specification,,Bitcoin,DID Methods,,,,,,,,2019-08-08,,,,,,,,,,,,,
+DID Methods,Blockstack,did:stack:,,Jude Nelson,,,,,,did:stack:,"Blockstack's DID method is specified as part of its decentralized naming system. Each name in Blockstack has one or more corresponding DIDs, and each Blockstack DID corresponds to exactly one name -- even if the name was revoked by its owner, expired, or was re-registered to a different owner.<br>Blockstack is unique among decentralized identity systems in that it is not anchored to a specific blockchain or DLT implementation. The system is designed from the ground up to be portable, and has already been live-migrated from the Namecoin blockchain to the Bitcoin blockchain. The operational ethos of Blockstack is to leverage the must secure blockchain at all times -- that is, the one that is considered hardest to attack.<br>Blockstack's naming system and its DIDs transcend the underlying blockchain, and will continue to resolve to DID document objects (DDOs) even if the system migrates to a new blockchain in the future.",,https://github.com/blockstack/blockstack-core/blob/stacks-1.0/docs/blockstack-did-spec.md,,Specification,,"Bitcoin, Namecoin, Portable",DID Methods,,,,,,,,2019-07-19,,,,,,,,,,,,,
+DID Methods,WebofTrustInfo,did:erc725:,,"Markus Sabadello, Fabian Vogelsteller, Peter Kolarov",,,,,rwot06,did:erc725:,"Decentralized Identifiers (DIDs, see [1]) are designed to be compatible with any distributed ledger or network (called the target system). In the Ethereum community, a pattern known as ERC725 (see [2]) utilizes smart contracts for standard key management functions. We propose a new DID method that allows ERC725 identities to be treated as valid DIDs. One advantage of this DID method over others appears to be the ability to use the full flexibility of Ethereum smart contracts for key management purposes.",,https://github.com/WebOfTrustInfo/rwot6-santabarbara/blob/master/topics-and-advance-readings/DID-Method-erc725.md,,Specification,,Ethereum,DID Methods,,,,,,ERC725,,2018-02-21,,,,,,,,,,,,,
+DID Methods,DIDWG,did:example:,,,,,,,,did:example:,"A DID is a simple text string consisting of three parts, the:<br>- URI scheme identifier (did)<br>- Identifier for the DID method<br>- DID method-specific identifier.<br>**EXAMPLE 1: A simple example of a decentralized identifier (DID)**<code>did:example:123456789abcdefghi</code><br>The example DID above resolves to a DID document. A DID document contains information associated with the DID, such as ways to cryptographically authenticate the DID controller, as well as services that can be used to interact with the DID subject.",,https://w3c.github.io/did-core/#a-simple-example,https://w3c.github.io/did-core/diagrams/did_detailed_architecture_overview.svg,Specification,,Portable,DID Methods,,,,,,,Credentials Community Group,2022-07-19,,,,,,,,,,,,,
+DID Methods,TranSendX,did:ipid:,,,,,,,,did:ipid:,"The Interplanetary Identifiers DID method (did:ipid:) supports DIDs on the public and private Interplanetary File System (IPFS) networks. IPFS is the distributed content addressable permanent web. More specifically, the IPID DID method utilizes the Interplanetary Linked Data (IPLD) suite of tools. The IPID DID method has minimal design goals: a DID trust anchor based on the IPFS and Libp2p protocol. In and of itself, this is not a blockchain solution. However, blockchains and other distributed ledger technologies could be utilized to anchor the artifacts of this DID methods for further enhanced security.",,https://did-ipid.github.io/ipid-did-method/,,Specification,,IPFS,DID Methods,,,,,,,,2018-12-31,,,,,,,,,,,,,
+DID Methods,lifeID Foundation,did:life:,,lifeID,,,,,,did:life:,"lifeID is a decentralized, blockchain-based protocol that acts as an open identity provider. The protocol enables the creation and use of self-sovereign identities as well as the issuance of verifiable credentials to those identities. The blockchain-based components of the protocol include smart contracts for storage, revocation, and recovery of keys and credentials. These contracts may be run on any open, permissionless blockchain. The purpose of this protocol is to allow users to transact their identity in a way that minimizes data disclosure, is cryptographically secure, and enables censorship-resistant decentralized identity provisioning and recovery. The purpose of this specification is to describe how lifeID DIDs are created and the technical requirements to operate on the lifeID platform.",,https://lifeid.github.io/did-method-spec/,,Specification,,RChain,DID Methods,,,,,,,,2019-08-13,,,,,,,,,,,,,
+DID Methods,Sovrin Foundation,did:sov:,,Mike Lodder,,,,,,did:sov:,"Sovrin is a public ledger designed specifically and only for privacy-preserving self-sovereign identity. The Sovrin Ledger is governed by the international non-profit Sovrin Foundation. As the only public ledger designed exclusively for self-sovereign identity, Sovrin is optimized for DIDs and DID Documents. DIDs are created, stored, and used with verifiable claims. This specification covers how these DIDs are managed. It also describes related features of Sovrin of particular interest to DID owners, guardians, and developers.",,https://sovrin-foundation.github.io/sovrin/spec/did-method-spec-template.html,,Specification,,Sovrin,DID Methods,,,,,,,,2023-04-19,,,,,,,,,,,,,
+DID Methods,uPort,did:ethr:,,,,,,,,did:ethr:,"ETHR DID Method Specification<br><br>In the Ethereum community, a pattern known as ERC1056 (see [2]) utilizes a smart contract for a lightweight identity management system intended explicitly for off-chain usage.<br><br>The described DID method allows any Ethereum smart contract or key pair account, or any secp256k1 public key to become a valid identifier. Such an identifier needs no registration. In case that key management or additional attributes such as ""service endpoints"" are required, they are resolved using ERC1056 smart contracts deployed on the networks listed in the registry repository.<br><br>Mainnet • Ropsten • Rinkeby • Goerli • Kovan • RSK • Alastria • Telsius • ARTIS tau1 • ARTIS sigma1<br><br>Since each Ethereum transaction must be funded, there is a growing trend of on-chain transactions that are authenticated via an externally created signature and not by the actual transaction originator. This allows for 3rd party funding services, or for receivers to pay without any fundamental changes to the underlying Ethereum architecture. These kinds of transactions have to be signed by an actual key pair and thus cannot be used to represent smart contract based Ethereum accounts. ERC1056 proposes a way of a smart contract or regular key pair delegating signing for various purposes to externally managed key pairs. This allows a smart contract to be represented, both on-chain as well as off-chain or in payment channels through temporary or permanent delegates.",,https://github.com/decentralized-identity/ethr-did-resolver/blob/master/doc/did-method-spec.md,,Specification,,Ethereum,DID Methods,,,,,,"ERC1056, secp256k1",,2022-11-07,,,,,,,,,,,,,
+DID Methods,DIF,,,,,,,,,DID resolver for Ethereum Addresses with support for key management (and DID reference implementation),This library is intended to use ethereum addresses or secp256k1 publicKeys as fully self-managed Decentralized Identifiers and wrap them in a DID Document,,https://github.com/decentralized-identity/ethr-did-resolver,,Code,,Ethereum,DID Methods,,,,,,"did:ethr:, secp256k1",,,,,,,,,,,,,,,
+DID Methods,Digital Bazaar,did:v1:,,,,,,,,did:v1:,"There are two primary classes of DID-based identifiers in Veres One. The first type of identifier is called a cryptonym-based identifier. This identifier is a SHA-256 hash of a public key. Cryptonym-based identifiers are not required to be registered on the ledger and may be used as unregistered pseudonymous pairwise identifiers. These identifiers may also be registered on the ledger and MUST contain a authentication key with a public key fingerprint equal to the value of the cryptonym-based identifier.<code>did:v1:nym:4jWHwNdrG9-6jd9I7K1si3kTRneNwftZV9m6rkrAfWQ</code>The second type of identifier on Veres One is a UUID-based identifier and may be used by entities that want to store metadata on the ledger. These sorts of identifiers are often used, but not limited to, storing and refering to Capabilities and Revocation lists.<code>did:v1:uuid:804c6ac3-ce3b-46ce-b134-17175d5bee74</code>",,https://w3c-ccg.github.io/did-method-v1/,https://w3c-ccg.github.io/did-method-v1/diagrams/data-model.svg,Specification,,Veres One,DID Methods,,,,,,SHA-256,,2019-11-22,,,,,,,,,,,,,
+DID Methods,Veres One,,,Joe Andrieu,did:v1:,,,,,Veres One (did:v1) Rubric Evaluation,"Veres One, DID Rubric Evaluation, DID methods, DIDs,",,https://iiw.idcommons.net/12B/_Veres_One_(did:v1)_Rubric_Evaluation,,Session Notes,,Veres One,DID Methods,,,,,,,,2021-05-06,,,,,,,,,,,,,
+DID Methods,Commercio Consortium,did:com:,,,,,,,,did:com:,"Commercio.network is a cosmos based sovereign blockchain network, built on the base of cosmos sdk and tendermint state machine replication engine, adopting Proof of Stake as a consensus algorithm.<br>Commercio.network, aims to be known as ""The Documents Blockchain"" and is to become ""the easiest way for companies to manage their business documents using the blockchain technology"".<br>Commercio.newtork ultimate goal is not just to share documents, but to create a network of trusted organizations, on the base of a web of trust, build on the Decentralized Identifier and Verifiable Credentials standard pillars.",,https://github.com/commercionetwork/Commercio.network-DID-Method-Specification/,,Specification,,commercio.network,DID Methods,Cosmos,,,Business Documents,,,,2019-11-12,,,,,,,,,,,,,
+DID Methods,Ontology Foundation,did:ont:,,,,,,,,did:ont:,"This specification defines how Ontology blockchain[1] stores DIDs and DID documents, and how to do CRUD operations on DID documents. More importantly, this specification confirms to the requirements specified in the DID specification[2] currently published by the W3C Credentials Community Group.",,https://github.com/ontio/ontology-DID/blob/master/docs/en/DID-ONT-method.md,,Specification,,Ontology,DID Methods,,,,,,,,2018-08-11,,,,,,,,,,,,,
+DID Methods,Vivvo Application Studios,did:vvo:,,,,,,,,did:vvo:,"Vivvo is a private ledger designed specifically and only for privacy-preserving self-sovereign identity. The Vivvo Ledger is governed by Vivvo Application Studios. As a private ledger designed exclusively for self-sovereign identity, Vivvo is optimized for DIDs and DID Documents. DIDs are created, stored, and used with verifiable claims. This specification covers how these DIDs are managed. It also describes related features of Vivvo of particular interest to DID owners, guardians, and developers.",,https://vivvo.github.io/vivvo-did-scheme/spec/did-method-spec-template.html,,Specification,,Vivvo,DID Methods,,,,,,,,2020-12-18,,,,,,,,,,,,,
+DID Methods,Aergo,did:aergo:,https://www.blocko.io/,,,,,,,did:aergo:,"The described DID method allows any Aergo smart contract or key pair account to become a valid identity. An identity needs no registration. In the case that key management or additional attributes such as ""service endpoints"" are required, we deployed did registry smart contracts [...] Since each Aergo transaction must be funded, in order to update attributes, account balance must be greater than zero.",,https://www.aergo.io/,,Specification,,Aergo,DID Methods,,,,,,,,,,,,,,,,,,,,,
+DID Methods,ICONLOOP,did:icon:,,,,,,,,did:icon:,"ICON[1,2,3] is a decentralized network that connects various independent communities to enable interoperability between them. ICON DID is a decentralized identifier devised to provide a way to uniquely identify a person, an organization, or a digital device across the communities connected to the ICON network. ICON DID method specification conforms to the DID and the DID Documents Spec[4]. This document describes how ICON blockchain manages the DIDs and the DID documents, and specifies a set of rules for how a DID is created, queried, updated, and revoked.",,https://github.com/icon-project/icon-DID/blob/master/docs/ICON-DID-method.md,,Specification,,ICON,DID Methods,,,,,,,,2019-08-14,,,,,,,,,,,,,
+DID Methods,Blockcore,did:is:,,,,,,,,did:is:,This specification describes how the Blockcore Identity framework aligns with the DID specification and how the Blockcore Universal Resolver works.[...]The Blockcore Identity registry is a permissionless and borderless runtime for identities.,,https://github.com/block-core/blockcore-did-method,,Specification,,Blockcore,DID Methods,,,,,,,,2020-08-31,,,,,,,,,,,,,
+DID Methods,Raonsecure,did:iwt:,,,Verifiable Credentials,,,,,did:iwt:,"InfoWallet is a decentralized network system for Self-Sovereign identity and Verifiable Claims. It can replace a legacy centralized credential system that with trusted blockchain node. In the InfoWallet system, several types of certificates are issued. DID(Decentralized Identifiers) is used as the unique identifier of the certificate. Also DID allows to obtain public key information for secure exchange of information between users.",,https://github.com/infowallet/did_method/blob/master/did_method.md,,Specification,,InfoWallet,DID Methods,,,,,,,,2019-02-18,,,,,,,,,,,,,
+DID Methods,Ockam,did:ockam:,,,,,,,,did:ockam:,"A DID that uses this method MUST begin with the following prefix: did:ockam:. Per the DID specification, this prefix MUST be in lowercase. The format of remainder of the DID, after this prefix, is specified below in the section on Method Specific Identifiers.",,https://github.com/ockam-network/did-method-spec/blob/master/README.md,,Specification,,Ockam,DID Methods,,,,,,,,2018-11-18,,,,,,,,,,,,,
+DID Methods,Alastria National Blockchain Ecosystem,did:ala:,,,,,,,,did:ala:,"This document is divided into two parts:<br>- The first one defines the Alastria DID Method Specification, describing the Alastria DID Scheme and the Alastria DID Document.<br>- The second part describes the format for Alastria Credentials and Presentations in the current Alastria Red T, based on Quorum.<br>- The third part describes the Credentials and Presentation Life Cycle and the Private Credential Multi Hashes (PSM Hashes) used to anchor Credential and Presentation actions ensuring privacy.",,https://github.com/alastria/alastria-identity/wiki/Alastria-DID-Method-Specification-(Quorum-version),,Specification,,Alastria,DID Methods,,,,,,Quorum,,2022-02-22,,,,,,,,,,,,,
+DID Methods,Ocean Protocol,did:op:,,,,,,,,did:op:,"**Requirements are:**<br>- The DID resolving capabilities MUST be exposed in the client libraries, enabling to resolve a DDO directly in a totally transparent way<br>- ASSETS are DATA objects describing RESOURCES under control of a PUBLISHER<br>- KEEPER stores on-chain only the essential information about ASSETS<br>- PROVIDERS store the ASSET metadata off-chain<br>- KEEPER doesn't store any ASSET metadata<br>- OCEAN doesn't store ASSET contents (e.g. files)<br>- An ASSET is modeled in OCEAN as on-chain information stored in the KEEPER and metadata stored in OCEANDB<br>- ASSETS on-chain information only can be modified by OWNERS or DELEGATED USERS<br>- ASSETS can be resolved using a Decentralized ID (DID) included on-chain and off-chain<br>- A DID Document (DDO) should include the ASSET metadata<br>- Any kind of object registered in Ocean SHOULD have a DID allowing one to uniquely identify that object in the system<br>- ASSET DDO (and the metadata included as part of the DDO) is associated to the ASSET information stored on-chain using a common DID<br>- A DID can be resolved to get access to a DDO<br>- ASSET DDOs can be updated without updating the on-chain information<br>- ASSET information stored in the KEEPER will include a checksum attribute<br>- The ASSET on-chain checksum attribute SHOULD include a one-way HASH calculated using the DDO content<br>- After the DDO resolving, the DDO HASH can be calculated off-chain to validate if the on-chain and off-chain information is aligned<br>- A HASH not matching with the checksum on-chain means the DDO was modified without the on-chain update<br>- The function to calculate the HASH MUST BE standard",,https://web.archive.org/web/20210428122924/https://github.com/oceanprotocol/OEPs/blob/master/7/v0.2/README.md,,Specification,,Ocean Protocol,DID Methods,,,,,,,,2021-04-28,,,,,,,,,,,,,
+DID Methods,JLinc.org,did:jlinc:,,Victor Grey,,,,,,did:jlinc:,JLINC is a protocol for sharing data protected by an agreement on the terms under which the data is being shared.<br><br>This document specifies methods for creating and editing Decentralized IDs (DIDs) suitable for use with the [JLINC protocol](https://protocol.jlinc.org/).,,https://did-spec.jlinc.org/,,Specification,,JLINC Protocol,DID Methods,,,,,,,,2018-10-13,,,,,,,,,,,,,
+DID Methods,DIF,did:ion:,,,,,,,,did:ion:,"ION is a public, permissionless, Decentralized Identifier (DID) network that implements the blockchain-agnostic Sidetree protocol on top of Bitcoin (as a 'Layer 2' overlay) to support DIDs/DPKI (Decentralized Public Key Infrastructure) at scale.<br><br>IMPORTANT NOTE: The majority of ION's code is developed under the blockchain-agnostic Sidetree protocol's repo: [https://github.com/decentralized-identity/sidetree](https://github.com/decentralized-identity/sidetree), which this project uses internally with the code required to run the protocol on Bitcoin, as the ION network.<br><br>**Key Points:**<br>- ION is public and permissionless - the system is decentralized, no company, organization, or group owns/controls the identifiers and DPKI entries in the system, and no one dictates who can participate.<br>- ION doesn't introduce new tokens/coins - Bitcoin is the only unit of value relevant in the operation of the on-chain aspects of the ION network.<br>- ION is not a sidechain or consensus system - the network nodes do not require any additional consensus mechanism.",The Identity Overlay Network (ION) is a DID Method implementation using the Sidetree protocol atop Bitcoin - GitHub - decentralized-identity/ion: The Identity Overlay Network (ION) is a DID Method implementation using the Sidetree protocol atop Bitcoin,https://github.com/decentralized-identity/ion-did-method,,Specification,,Bitcoin,DID Methods,,,,,,,,2023-04-20,,,,,,,,,,,,,
+DID Methods,Jolocom,did:jolo:,,,,,,,,did:jolo:,It’s core technologies are the Ethereum blockchain and the Interplanetary File System (IPFS). The Jolocom DID method uses IPFS as a decentralised CAS layer for DID Documents. A deployed smart contract provides a mapping from a DID to an IPFS hash address of the corrosponding DID Document. This enables DID Documents on IPFS to be effectively addressed via their DIDs.,,https://github.com/jolocom/jolo-did-method/blob/master/jolocom-did-method-specification.md,,Specification,,Ethereum,DID Methods,,,,,,"ION, Sidetree",,2020-08-16,,,,,,,,,,,,,
+DID Methods,Bryk,did:bryk:,,"Marcos Allende, Sandra Murcia, Flavia Munhoso, Ruben Cessa",,,,,,did:bryk:,"The method specification provides all the technical considerations, guidelines and recommendations produced for the design and deployment of the DID method implementation. The document is organized in 3 main sections.<br><br>- DID Schema. Definitions and conventions used to generate valid identifier instances.<br>- DID Document. Considerations on how to generate and use the DID document associated with a given identifier instance.<br>- Agent Protocol. Technical specifications detailing how to perform basic network operations, and the risk mitigation mechanisms in place, for tasks such as:<br>- Publish a new identifier instance.<br>- Update an existing identifier instance.<br>- Resolve an existing identifier and retrieve the latest published version of its DID Document.",Reference implementation for the 'bryk' DID method. - did-method/README.md at master · aidtechnology/did-method,https://github.com/bryk-io/did-method/blob/master/README.md,,Specification,,bryk,DID Methods,,,,,,IPFS,,2021-12-27,,,,,,,,,,,,,
+DID Methods,Daniel Hardman,did:peer:,,,,,,,,did:peer:,"Most documentation about decentralized identifiers (DIDs) describes them as identifiers that are rooted in a public source of truth like a blockchain, a database, a distributed filesystem, or similar. This publicness lets arbitrary parties resolve the DIDs to an endpoint and keys. It is an important feature for many use cases.",,https://identity.foundation/peer-did-method-spec/,,Specification,,P2P,DID Methods,,,,,,,,2022-10-13,,,,,,,,,,,,,
+DID Methods,Affinidi,,,,did:peer:,,,,,Peer DIDs — An Off-Ledger DID Implementation,"- No transaction costs involved<br>- Easy to create and maintain<br>- Since these DIDs are independent of a central system such as a GDPR controller, they can be scaled as needed<br>- Offers the highest levels of privacy as only the parties involved can access the DIDs<br>- No uncertainties or external problems since these DIDs are not associated with any particular network<br>- No degradation of trust throughout the entire lifecycle.<br>- In tune with local-first software philosophies<br>- Reduces unnecessary correlation between a verifier and an issuer of a [verifiable credential](https://academy.affinidi.com/what-are-verifiable-credentials-79f1846a7b9).","Peer DIDs ensure a cheap, secure, and scalable way to maintain interaction between two entities in SSI implementations through verifiable credentials.",https://academy.affinidi.com/peer-dids-an-off-ledger-did-implementation-5cb6ee6eb168,,page,,P2P,DID Methods,,,,,,,,2021-05-18,,,,,,,,,,,,,
+DID Methods,SelfKey,did:selfkey:,,,,,,,,did:selfkey:,"The following document defines a DID method for the SelfKey Identity platform. Although this method provides support to the SelfKey ecosystem and its related applications, the underlying DID platform is fully decentralized, and it's designed to serve as a DID layer for other systems that might find it valuable.<br><br>The following specifications are subject to change in the future, yet they MUST comply with the latest version of the [generic DID specs](https://w3c-ccg.github.io/did-spec/) as specified by the W3C Credentials Community Group.<br><br>The functionality for this method is provided by the DIDLedger smart contract found in [this repository](https://github.com/SelfKeyFoundation/selfkey-identity).",,https://github.com/SelfKeyFoundation/selfkey-identity/blob/develop/DIDMethodSpecs.md,,Specification,,Ethereum,DID Methods,,,,,,,,2019-04-10,,,,,,,,,,,,,
+DID Methods,Metadium,did:meta:,,,,,,,,did:meta:,"Metadium is the next-generation identity system powered by blockchain technology. Metadium Decentralized Identifiers is a distributed identifier designed to provide a way for a community connected to the Metadium Ecosystem to uniquely identify an individual, organization, or digital device. The role of a Metadium DID is to provide a service that supports user-authentication and personal information verification",,https://github.com/METADIUM/meta-DID/blob/master/doc/DID-method-metadium.md,,Specification,,Metadium,DID Methods,,,,,,,,2021-06-02,,,,,,,,,,,,,
+DID Methods,Chainyard,did:tys:,,,,,,,,did:tys:,"The TYS network is a cross industry source of supplier information and identity helping to simplify and accelerate the onboarding and lifecycle management process. TYS is a fit-for-purpose blockchain optimized for sharing supplier credentials in a supply chain environment. TYS DIDs may be used by Suppliers, Buyers, Verifiers, Banks and other organizations to establish identities for verifiable claims made by any party.<br><br>TYS is implemented on Hyperledger Fabric, a permissioned blockchain technology under the Linux Foundation’s Hyperledger Project. The “Smart Contract” Functions are written in “Golang” and all client APIs are provided as REST APIs written in “Javascript” running on “NodeJS.",,https://github.com/chainyard-tys/tys/blob/master/README.md,,Specification,,TYS Network,DID Methods,,,,Lifecycle Managment,,,,2019-04-23,,,,,,,,,,,,,
+DID Methods,Personal,did:git:,,Dave Huseby,,,,,Internet Identity Workshop,did:git:,"The Git revision control tool is designed to function in a decentralized peer-to-peer fashion to facilitate collaboration in the frequently-disconnected world. Git uses a directed acyclic graph (DAG) of commits that represent the changes to the folders and files in the repository. Because it uses blockchain-like hash-linking of commits, Git is effectively a blockchain and distributed ledger with the patch review and merge process functioning as the consensus mechanism. This makes it a great tool for tracking the provenance of data inside the repository. Git also records the author and other meta data such as digital signatures with each commit linking identity of committers to each commit. Git repos therefore contain all of the information needed to serve as the single source of truth for the provenance of the data it contains and the identities of the contributors that created it.",,https://github.com/dhuseby/did-git-spec/blob/master/did-git-spec.md,,Specification,depreciated,Git,DID Methods,,,,,,DAG,,2019-06-06,,,,,,,,,,,,,
+DID Methods,cryptidtech,,"https://iiw.idcommons.net/12A/_Git_as_Authentic_Data_Creation_Tool_(a.k.a._what_happened_to_did:git%3F_a.k.a._independently_verifiable,_secure,_developer_sovereign,_open_source_software_supply_chain)",Dave Huseby,,,,,,Git Cryptography Protocol,"This specification documents a new, proposed protocol Git uses when interacting with cryptographic signing and verification tools. The goal of this modification is to make Git able to use any signing and verification tools. The design eliminates all of the tool-specific code in Git, easing maintenance and increasing flexibility. The protocol takes is inspired by the Assuan Protocol used by GPG to link its component executables together but uses Git's pkt-line framing.",,https://github.com/cryptidtech/git-cryptography-protocol/blob/main/Git%20Cryptography%20Protocol.md,,Specification,,Git,DID Methods,,,,Software Development,,,,2021-08-14,,,,,,,,,,,,,
+DID Methods,BiiLabs,did:tangle:,,,,,,,,did:tangle:,"IOTA is a public distributed ledger that utilizes an invention called the Tangle at its core, address scalability issues and having no transaction fee, that encourages adoption of the technology in the industry. TangleID is intended to implement DIDs and DID Documents.",,https://github.com/TangleID/TangleID/blob/develop/did-method-spec.md,,Specification,,IOTA Tangle,DID Methods,,,,,,,,2022-06-06,,,,,,,,,,,,,
+DID Methods,Halialabs,did:emtrust:,,,,,,,,did:emtrust:,"The Emtrust DID method utilizes Hyperledger fabric as the DLT implementation, having an identity channel which is shared among the identity nodes with participating organizations. The DID document along with metadata of third party endorsements resides on ledger and the private information of users are kept on the mobile or persona devices which never leaves the device. The Interaction of DID and blockchain ledger happens via the API servers hosted by any participating organizations.",,https://github.com/Halialabs/did-spec/blob/gh-pages/readme.md,,Specification,,Hyperledger Fabric,DID Methods,,,,,,,,2019-06-17,,,,,,,,,,,,,
+DID Methods,Token.TM,did:ttm:,,,,,,,,did:ttm:,"<32 byte hexadecimal stringcorresponds to keccak256 and the hash value of Ethereum address connected by random numbers generated in the DID contract.<br><br>DID is registered in the contract and controlled by a single Ethereum address, which is set by default to the address where the createDID method was originally called. Then, this address can transfer control to a different address, or update/delete the corresponding DID in the contract.",,https://github.com/TokenTM/TM-DID/blob/master/docs/en/DID_spec.md,,Specification,,TMChain,DID Methods,,,,,,,,2019-07-11,,,,,,,,,,,,,
+DID Methods,Weelink,did:wlk:,,,,,,,,did:wlk:,"Weelink DID is a new blockchain-based authentication method that follows all the requirements of W3C. Based on Weelink Wallet, our method provides a series of APIs and services for a fast and secure authentication process.",,https://weelink-team.github.io/weelink/DIDDesignEn,,Specification,,Weelink Network,DID Methods,,,,,,,,2019-07-19,,,,,,,,,,,,,
+DID Methods,Pistis,did:pistis,,"Andrea Taglia, Matteo Sinico",,,,,,did:pistis,"This specification defines how Pistis deals with DID and DID Documents and how it interacts with the Ethereum blockchain. Also CRUD operations on DID documents are described. This specification confirms to the requirements specified in the DID specification[1] currently published by the W3C Credentials Community Group.<br><br>Pistis is a credential management system based on the Ethereum blockchain. It provides a set of novel smart contracts to handle efficient multi signature operations, delegates management, permissioned access to extensible services based upon the Decentralized IDentifier specification.",,https://github.com/uino95/ssi/blob/consensys/dashboard/server/pistis/pistis-did-resolver/README.md,,Specification,,Ethereum,DID Methods,,,,,,,,2019-08-29,,,,,,,,,,,,,
+DID Methods,Holo.Host,did:holo:,,,,,,,,did:holo:,"Decentralized Identifiers (DIDs, see [1]) are designed to be compatible with any distributed ledger or network (called the target system). We will be specing and prototyping a DID method for holochain.",,https://github.com/WebOfTrustInfo/rwot9-prague/blob/master/draft-documents/did:hc-method.md,,Specification,,Holochain,DID Methods,,,,,,,,2019-09-08,,,,,,,,,,,,,
+DID Methods,CCG,did:web:,,"Oliver Terbu, Mike Xu, Dmitri Zagidulin, Amy Guy",,,,,,did:web:,"The target system of the Web DID method is the web host that the domain name described by the DID resolves to when queried through the Domain Name System (DNS).<br><br>The method specific identifier MUST match the common name used in the SSL/TLS certificate, and it MUST NOT include IP addresses or port numbers. Directories and subdirectories MAY optionally be included, delimited by colons rather than slashes.<code>did:web:w3c-ccg.github.io:user:alice</code>",,https://github.com/w3c-ccg/did-method-web,,Specification,,Web,DID Methods,,,,,,,,2023-05-06,,,,,,,,,,,,,
+DID Methods,IoTeX Foundation,did:io:,,,,,,,,did:io:,"Our DID design allows each manufacture or entity to have its own namespace, which stores and manages DIDs through a self-managed DID contract. A self-managed contract could have customized business logic to adapt the application's needs but has to implement the SelfManagedDID interface",,https://github.com/iotexproject/iotex-did/blob/master/README.md,,Specification,,IoTeX,DID Methods,,,,,,,,2021-07-28,,,,,,,,,,,,,
+DID Methods,Vaultie Inc.,did:vaultie:,,,,,,,,did:vaultie:,"Vaultie DID method uses IPFS as a decentralised storage for DID Documents. An Ethereum transaction, that does not require any additional Smart Contracts, provides a mapping from a DID to an IPFS hash address of the corrosponding DID Document. This enables DID Documents on IPFS to be effectively addressed via their DIDs. While this method requires additional step in order to lookup DID Document, the method is much more cost effective than using Smart Contracts and Ethereum's expensive storage.",,https://github.com/vaultie/vaultie-did-method/blob/master/vaultie-did-method-specification.md,,Specification,,Ethereum,DID Methods,,,,,,,,2020-08-19,,,,,,,,,,,,,
+DID Methods,"MOAC Blockchain Tech, Inc.",did:moac:,,David Ricardo Wilde,,,,,,did:moac:,The MOAC DID method uses MOAC blockchain as a decentralized storage layer for DID Documents. A deployed smart-contract provides a mapping from a DID to an MOAC blockchain hash address of the corrosponding DID Document. This enables DID Documents on MOAC blockchain to be effectively addressed via their DIDs.,,https://github.com/DavidRicardoWilde/moac-did/blob/master/did-moac-method.md,,Specification,,MOAC,DID Methods,,,,,,,,2019-10-03,,,,,,,,,,,,,
+DID Methods,OmniOne,did:omn:,,,,,,,,did:omn:,"OmniOne is a decentralized network system for Self-Sovereign identity and Verifiable Claims. It can replace a legacy centralized credential system that with trusted blockchain node. In the OmniOne system, several types of certificates are issued. DID(Decentralized Identifiers) is used as the unique identifier of the certificate. Also DID allows to obtain public key information for secure exchange of information between users.",,https://github.com/OmniOneID/did_method/blob/master/did_method.md,,Specification,,OmniOne,DID Methods,,,,,,,,2019-05-30,,,,,,,,,,,,,
+DID Methods,"Workday, Inc.",did:work:,,,,,,,,did:work:,"Workday offers a decentralized Credentialing Platform with a Blockchain based trust layer. A key component of the platform is the WayTo by Workday mobile app which allows the user to store verifiable identity documents, encrypted using their own personal encryption key, which is managed in the Trusted Execution Environment (TEE) of their mobile device. The mobile app can hold official documents, training certifications, verified accomplishments and other credentials. The user can choose what to share, and with whom to share it with. Users of the Workday Credentialing Platform will have a DID and a corresponding DID Document on a permissioned ledger, which credential verifiers can use to validate users’ cryptographic signatures, included in their credentials.",,https://workday.github.io/work-did-method-spec/,"data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAYAAABzenr0AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAyRpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADw/eHBhY2tldCBiZWdpbj0i77u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlkIj8+IDx4OnhtcG1ldGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhNUCBDb3JlIDUuMy1jMDExIDY2LjE0NTY2MSwgMjAxMi8wMi8wNi0xNDo1NjoyNyAgICAgICAgIj4gPHJkZjpSREYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjIj4gPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIgeG1sbnM6eG1wPSJodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvIiB4bWxuczp4bXBNTT0iaHR0cDovL25zLmFkb2JlLmNvbS94YXAvMS4wL21tLyIgeG1sbnM6c3RSZWY9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC9zVHlwZS9SZXNvdXJjZVJlZiMiIHhtcDpDcmVhdG9yVG9vbD0iQWRvYmUgUGhvdG9zaG9wIENTNiAoTWFjaW50b3NoKSIgeG1wTU06SW5zdGFuY2VJRD0ieG1wLmlpZDpFMTZCRDY3REIzRjAxMUUyQUQzREIxQzRENUFFNUM5NiIgeG1wTU06RG9jdW1lbnRJRD0ieG1wLmRpZDpFMTZCRDY3RUIzRjAxMUUyQUQzREIxQzRENUFFNUM5NiI+IDx4bXBNTTpEZXJpdmVkRnJvbSBzdFJlZjppbnN0YW5jZUlEPSJ4bXAuaWlkOkUxNkJENjdCQjNGMDExRTJBRDNEQjFDNEQ1QUU1Qzk2IiBzdFJlZjpkb2N1bWVudElEPSJ4bXAuZGlkOkUxNkJENjdDQjNGMDExRTJBRDNEQjFDNEQ1QUU1Qzk2Ii8+IDwvcmRmOkRlc2NyaXB0aW9uPiA8L3JkZjpSREY+IDwveDp4bXBtZXRhPiA8P3hwYWNrZXQgZW5kPSJyIj8+SM9MCAAAA+5JREFUeNrEV11Ik1EY3s4+ddOp29Q5b0opCgKFsoKoi5Kg6CIhuwi6zLJLoYLopq4qsKKgi4i6CYIoU/q5iDAKs6syoS76IRWtyJ+p7cdt7sf1PGOD+e0c3dygAx/67ZzzPM95/877GYdHRg3ZjMXFxepQKNS6sLCwJxqNNuFpiMfjVs4ZjUa/pmmjeD6VlJS8NpvNT4QQ7mxwjSsJiEQim/1+/9lgMHgIr5ohuxG1WCw9Vqv1clFR0dCqBODElV6v90ogEDjGdYbVjXhpaendioqK07CIR7ZAqE49PT09BPL2PMgTByQGsYiZlQD4uMXtdr+JxWINhgINYhGT2MsKgMrm2dnZXgRXhaHAg5jEJodUAHxux4LudHJE9RdEdA+i3Juz7bGHe4mhE9FNrgwBCLirMFV9Okh5eflFh8PR5nK5nDabrR2BNJlKO0T35+Li4n4+/J+/JQCxhmu5h3uJoXNHPbmWZAHMshWB8l5/ipqammaAf0zPDDx1ONV3vurdidqwAQL+pEc8sLcAe1CCvQ3YHxIW8Pl85xSWNC1hADDIv0rIE/o4J0k3kww4xSlwIhcq3EFFOm7KN/hUGOQkt0CFa5WpNJlMvxBEz/IVQAxg/ZRZl9wiHA63yDYieM7DnLP5CiAGsC7I5sgtYKJGWe2A8seFqgFJrJjEPY1Cn3pJ8/9W1e5VWsFDTEmFrBcoDhZJEQkXuhICMyKpjhahqN21hRYATKfUOlDmkygrR4o4C0VOLGJKrOITKB4jijzdXygBKixyC5TDQdnk/Pz8qRw6oOWGlsTKGOQW6OH6FBWsyePxdOXLTgxiyebILZCjz+GLgMIKnXNzc49YMlcRdHXcSwxFVgTInQhC9G33UhNoJLuqq6t345p9y3eUy8OTk5PjAHuI9uo4b07FBaOhsu0A4Unc+T1TU1Nj3KsSSE5yJ65jqF2DDd8QqWYmAZrIM2VlZTdnZmb6AbpdV9V6ec9znf5Q7HjYumdRE0JOp3MjitO4SFa+cZz8Umqe3TCbSLvdfkR/kWDdNQl5InuTcysOcpFT35ZrbBxx4p3JAHlZVVW1D/634VRt+FvLBgK/v5LV9WS+10xMTEwtRw7XvqOL+e2Q8V3AYIOIAXQ26/heWVnZCVfcyKHg2CBgTpmPmjYM8l24GyaUHyaIh7XwfR9ErE8qHoDfn2LTNAVC0HX6MFcBIP8Bi+6F6cdW/DICkANRfx99fEYFQ7Nph5i/uQiA214gno7K+guhaiKg9gC62+M8eR7XsBsYJ4ilam60Fb7r7uAj8wFyuwM1oIOWgfmDy6RXEEQzJMPe23DXrVS7rtyD3Df8z/FPgAEAzWU5Ku59ZAUAAAAASUVORK5CYII=",Specification,dead,Hyperledger Fabric,DID Methods,,,,,,,,2020-06-25,,,,,,,,,,,,,
+DID Methods,VP Inc.,did:vid:,,,,,,,,did:vid:,"The system aims to provide secure authentication and various payment services based on the DID and Verifiable Claims specificiatons published by the W3C and the Decentralised Identity Foundation. VP DID is a decentralized identifier devised to provide a way to uniquely identify a person, an organization. VP DID document contains information for providing various payment methods among network participants in a decentralized way. This specification defines how VP blockchain stores DIDs and DID documents, and how to do CRUD operations on DID documents.",,https://github.com/vpayment/did-method-spec/blob/master/vid.md,,Specification,,VP,DID Methods,,,,,,,,2019-10-15,,,,,,,,,,,,,
+DID Methods,"Baidu, Inc.",did:ccp:,,,,,,,,did:ccp:,"Application scenarios:<br>- Digital identity<br>- Joint member key customer system<br>- Financial KYC<br>- Exchange<br>- Smart City<br>- IoT deviceless identity management<br><br>Program features:<br>Building a decentralized ID system based on blockchain and consortium chains will have almost equal control over the system and enhance cooperation intentions.<br><br>Blockchain asymmetric encryption technology combines public and private keys to ensure the authenticity and reliability of ID and certification.<br><br>Form a richer user portrait, with multiple tags (VIP authentication, privilege authentication, asset authentication...) and one ID.",,https://did.baidu.com/did-spec/,https://did.baidu.com/images/did-login-pc.png,Specification,,Quorum,DID Methods,,,,,,,,2016-02-08,,,,,,,,,,,,,
+DID Methods,Jnctn Limited,did:jnctn:,,,,,,,,did:jnctn:,"The system provides secure credential management services based on the DID and Verifiable Claims specifications published by the W3C and the Decentralised Identity Foundation. JNCTN DID method enables an interoperability bridge between the worlds of centralized, federated, and decentralized identifiers with self soverign identity services. JNCTN DID document contains information for accessing JNCTN DID network methods, how JNCTN stores DIDs and DID documents, and how to do CRUD operations on JNCTN DID documents.",,https://github.com/jnctn/did-method-spec/,,Specification,dead,Jnctn Network,DID Methods,,,,,,,,,,,,,,,,,,,,,
+DID Methods,evan GmbH,did:evan:,,,,,,,,did:evan:,evan.network is a blockchain for digitalization and automation of business transactions. The network members create digital twins for their machines and products and develop standards for cross-company transactions. The open technology allows integration into existing business models. evan.network guarantees 100% reliable and permanently secured information.,,https://github.com/evannetwork/evan.network-DID-method-specification/blob/master/evan_did_method_spec.md,,Specification,,evan.network,DID Methods,,,,,,,,2020-03-24,,,,,,,,,,,,,
+DID Methods,Elastos Foundation,did:elastos:,,,,,,,,did:elastos:,"DID is completely under the control of the DID subject, without reliance on any centralized registration body, commercial identity provider, or organization issuing certificates. The DID is described in the DID documents. Each DID document includes at least two items: encryption materials and verification methods. The encryption materials integrated with the verification methods provides a set of identify verification mechanisms (such as a public key, anonymous biological identification agreement, etc.), with other optional parts that can be used according to the needs of the application and of the user.",,https://github.com/elastos/Elastos.DID.Method/blob/master/DID/Elastos-DID-Method-Specification_en.md,,Specification,,Elastos ID Sidechain,DID Methods,,,,,,,,2021-01-04,,,,,,,,,,,,,
+DID Methods,BOTLabs GmbH,did:kilt:,,,,,,,,did:kilt:,"KILT DIDs are stored on KILT Protocol's blockchain that is public and by definition decentralized. The KILT Blockchain runs in a proof-of-authority manner and will become permissionless, see `§ Status of this document` in this specification document.",,https://github.com/KILTprotocol/kilt-did-driver/blob/master/docs/did-spec/spec.md,,Specification,,KILT Blockchain,DID Methods,,,,,,,,2022-10-11,,,,,,,,,,,,,
+DID Methods,Transmute,did:elem:,,,,,,,,did:elem:,Element is an implementation of the Sidetree protocol that uses the Ethereum blockchain as the ledger layer and IPFS as the Content-addressable storage layer,,https://github.com/decentralized-identity/element/blob/master/docs/did-method-spec/spec.md,,Specification,,,DID Methods,,,,,,Element DID,,2020-04-06,,,,,,,,,,,,,
+DID Methods,Transmute,did:github:,,,,,,,,did:github:,"The `github` method is meant to make working with DIDs very simple at the cost of trusting Github.com for assisting in resolving DID Documents.<br><br>Many developers are familar with Github, and its 2 supported public key cryptosystems, GPG and SSH.<br><br>Linked Data Signatures are difficult to work with when operating a server or running a local node of some distributed system / blockchain is a requirement.<br><br>The objective of GitHub DID is to encourage contribution to the DID Spec and Linked Data Signatures, and allow rapid development of extensions to these without requiring the use of slow, or complicated more trustless infrastructure, such as blockchains or other distributed systems.",,https://docs.github-did.com/did-method-spec/,,Specification,,Github,DID Methods,,,,,,,,2020-05-08,,,,,,,,,,,,,
+DID Methods,teleinfo caict,did:bid:,,,,,,,,did:bid:,"BID provides distributed identifiers and blockchain-based digital identity services for people, enterprises, devices and digital objects. It aims to build a decentralized, data-secure, privacy-protected and flexible identifier system that addresses trusted connections among people, enterprises, devices and digital objects，enabling the vision of the Internet of Things and trust ingress with everything.",,https://github.com/teleinfo-bif/bid/tree/master/doc/en,,Specification,,bif,DID Methods,,,,,,,,2022-11-03,,,,,,,,,,,,,
+DID Methods,PalletOne,did:ptn:,,,,,,,,did:ptn:,"Description of each field in the Base DID Document example (★ required fields, others are optional fields):<br><br>* ★ `context` A single value or an array, specifying the syntax standard that the DID Document format complies with.<br>* `controller` Single value or array, other owners of DID Document. You can specify other DIDs to manage the file, and the permissions of other DIDs will be set in the corresponding operations authentication, updation, deletion, and recovery later. The default is controlled by the DID in the DID Document corresponding to the Base DID Document.<br>* ★ `publicKey` A single value or an array that controls the public key information corresponding to the private key of the DID Document.<br>* ★ `id` The ID of the public key, `#keys-<num>` expressed in a unified way, incremented `<num>` from the `1` beginning.<br>* ★ `type` The algorithm of public key generation is unified with the chain,<br>  * `controller` The owner of the public key `controller` corresponds to the one in the previous level. The format is `<DID>#keys-<num>`. The default situation is controlled by the document DID. `<DID>` The value on the stage controller, a `#keys-<num>` is `<DID>` a corresponding public key `id`.<br>* `publicKeyHex` Hexadecimal information of the public key. When the above controller is the default, this field is **required**.<br>* ★ `authentication` Specify `publicKey` which fields can be used for authentication.<br>* `updation` Specify `publicKey` which fields can be used for DID Document **update** operations, such as updating information such as pubkey or service.<br>* `deletion` Specify `publicKey` which fields can be used for DID Document **delete** operation.<br>* `recovery` Specify `publicKey` which fields can be used for DID Document **recovery** operations.",,https://github.com/palletone/palletone-DID/blob/master/docs/did-method/README.md,,Specification,,PalletOne,DID Methods,,,,,,,,2020-02-29,,,,,,,,,,,,,
+DID Methods,Echo Technological Solutions LLC,did:echo:,,,,,,,,did:echo:,We propose a new DID method that allows special objects in ECHO network to be treated as valid DIDs.,,https://github.com/echoprotocol/uni-resolver-driver-did-echo/blob/master/echo_did_specifications.md,,Specification,,Echo,DID Methods,,,,,,,,2022-10-11,,,,,,,,,,,,,
+DID Methods,SecureKey,did:trustbloc:,,,,,,,,did:trustbloc:,"The did:trustbloc DID method allows groups of independent entities to share custody of a DID registry consisting of a Sidetree implementation over a permissioned ledger. For more information on Sidetree, please refer to the Sidetree protocol specification.<br><br>Independent stakeholders wishing to transact with one another using DIDs can come together to form a consortium to manage their shared custody of a ledger.<br><br>This spec defines a discovery service. The discovery service provided by the TrustBloc DID Method allows a client to verify that a consortium is endorsed by its constituent stakeholders, verify that the configuration files of each stakeholder (which includes a list of Sidetree endpoints) are signed by the respective stakeholders, and use the provided Sidetree endpoints to perform Sidetree DID operations.",,https://github.com/trustbloc/trustbloc-did-method/blob/master/docs/spec/trustbloc-did-method.md,,Specification,,Hyperledger Fabric,DID Methods,,,,,,,,2020-04-09,,,,,,,,,,,,,
+DID Methods,YLZ Inc.,did:san:,,,,,,,,did:san:,The system aims to provide secure authentication and various health services based on the SAN blockchain and DID & Verifiable Credential Specifications published by the W3C.,,https://github.com/Baasze/DID-method-specification,,Specification,,SAN Cloudchain,DID Methods,,,,,,,,2020-04-17,,,,,,,,,,,,,
+DID Methods,Gataca,did:gatc:,,,,,,,,did:gatc:,"Gataca’s platform is based on a mobile identity portfolio, a set of APIs, and controllers for multiple blockchain networks.<br><br>Gataca is agnostic to the blockchain network. We adapt our infrastructure to the third party’s preferred ledger. Gataca currently supports the public network Ethereum and private networks based on Hyperledger Fabric, Hyperledger Besu or Quorum. Other networks may be added as requested.<br>This document provides the DID method specs for how our DID schema is implemented on the Ethereum network.<br><br>The simple structure links an object to a DID with states and public keys. Users do not need privileges to read the information on the blockchain but do need them to write. Gataca is the unique user that can modify the smart contract.",,https://github.com/gatacaid/gataca-did-method,,Specification,,"Ethereum, Hyperledger Fabric, Hyperledger Besu, Alastria",DID Methods,,,,,,,,2020-05-05,,,,,,,,,,,,,
+DID Methods,"Sphereon, Factomatic, Factom Inc",did:factom:,,,,,,,,did:factom:,"This proposal contains the interoperability specifications for products creating, reading (resolving) updating and deactivating Decentralized Identifiers on top of the Factom Protocol. This specification is not about other products wanting to use DIDs for their specific purpose, like signing or voting. This document describes the low level data structures and rules for DIDs, DID documents, resolution and registration on Factom itself.",,https://github.com/factom-protocol/FIS/blob/master/FIS/DID.md,,Specification,,Factom,DID Methods,,,,,,,,2019-11-02,,,,,,,,,,,,,
+DID Methods,Cryptonics Consulting,did:signor:,,,,,,,,did:signor:,"DIDs are registered in the DID Registry on-chain, and have a controller and a subject, expressed in the form of Ethereum addresses. The DID controller may or may not be the subject itself. Multiple controllers can be implemented through proxy smart contracts.",,https://github.com/cryptonicsconsulting/signor-did-contracts/blob/master/did-method-spec.md,,Specification,,"Ethereum, Hedera Hashgraph, Quorum, Hyperledger Besu",DID Methods,,,,,,,,2020-11-16,,,,,,,,,,,,,
+DID Methods,"Hedera Hashgraph, Swisscom Blockchain AG",did:hedera:,,,,,,,,did:hedera:,"This document defines a binding of the Decentralized Identifier architecture to Hedera Hashgraph - specifically how to use the Hedera File Service to record membership in 'business application networks' (appnets) and how to use the Hedera Consensus Service (HCS) for CRUD mechanisms on DID documents stored in such business application network. An business application network is a network of computers that store some set of business data (such as DID Documents) in a shared state, and rely on the Hedera mainnet for timestamping and ordering the transactions that cause that business application network state to change. An business application network could be exclusively dedicated to managing DID Documents and other identity artifacts in its state, or it could itself be multi-purpose.",,https://github.com/hashgraph/did-method/blob/master/did-method-specification.md,,Specification,,Hedera Hashgraph,DID Methods,,,,,,,,2020-05-14,,,,,,,,,,,,,
+DID Methods,"ProximaX Enterprise, Proximax Inc.",did:sirius:,,,,,,,,did:sirius:,The target system is the ProximaX Sirius Chain network. This can either be:<br>- Sirius Chain on Main Net<br>- Sirius Chain on Test Net<br>- Sirius Chain on Private Net,,https://gitlab.com/proximax-enterprise/siriusid/sirius-id-specs/-/blob/master/docs/did-method-spec.md,,Specification,,ProximaX Sirius Chain,DID Methods,,,,,,,,2020-07-04,,,,,,,,,,,,,
+DID Methods,Dock,did:dock:,,,,,,,,did:dock:,"Currently, three public key and signing algorithms are supported for authentication.<br>-  Schnorr signatures with Sr25519. The public key is 32 bytes and signature is 64 bytes in size. These are supported by Substrate and Polkadot.<br>- EdDSA signatures with Ed25519 curve. The public key is 32 bytes and signature is 64 bytes in size.<br><br>Dock is currently running as a proof of authority network but will evolve into a proof of stake chain. DIDs can be created by anyone holding Dock tokens but the creator of the DID is not necessarily the owner of the DID and thus cannot manage (update, remove) them. DIDs are managed using their corresponding private keys and these keys are independent of keys controlling the Dock tokens spent while creating the DID.<br><br>The chain does not store the full DID document but only the DID, the corresponding keys and controllers and block number for the last update and this block number changes with each update to the DID. This is needed for replay protection. Dock's client SDK retrieves those details and constructs the full DID document.",,https://github.com/docknetwork/dock-did-driver/blob/master/Dock%20DID%20method%20specification.md,,Specification,,Dock,DID Methods,,,,,,,,2022-07-21,,,,,,,,,,,,,
+DID Methods,did-twit,did:twit:,,,,,,,,did:twit:,"Twitter is a highly used and influential social media network that lacks decentralization and higher levels of trust (i.e. signed messages). The `did:twit` specification makes an attempt to increase trust in Twitter interactions.<br><br>The method is similar to [did:key](https://w3c-ccg.github.io/did-method-key) in the sense that it is uses a `did` to wrap a single public key.<br><br>The objective of Twitter DID, similar to that of the [GitHub DID Method](https://github.com/decentralized-identity/github-did),  is to encourage use of the [DID Spec](https://w3c-ccg.github.io/did-spec/), by lowering the barrier to entry for use of the technology, and promote higher trust interactions.",,https://github.com/did-twit/did-twit/blob/master/spec/index.md,,Specification,,Twitter,DID Methods,,,,,,,,2020-07-29,,,,,,,,,,,,,
+DID Methods,Ontology Foundation,did:near:,,,,,,,,did:near:,"NEAR uses readable account identifiers instead of a hash of a public key, and the accounts have some DID features, but not all. We have developed this specification to define a new DID method for hosting DIDs on the NEAR blockchain, also referred to as NEAR DID, and facilitate developers to work with related contracts.",,https://github.com/ontology-tech/DID-spec-near/blob/master/NEAR/DID-Method-NEAR.md,,Specification,,NEAR,DID Methods,,,,,,,,2020-08-02,,,,,,,,,,,,,
+DID Methods,China Academy of Information and Communications Technology (CAICT),did:vaa:,,,,,,,,did:vaa:,"Blockchain Identifier Infrastructure (BIF) is a permissioned public blockchain aiming for creating a distributed trust management framework typical for internet ID service, and the [BIF blockchain](http://bidspace.cn/) is governed by China Academy of Information and Communications Technology (CAICT). CAICT is also the official issuing agency with Issuing Agency Code (IAC)——""VAA"", given by ISO/IEC 15459. The IAC indicates an authorized qualification of distributing identifiers with own allocation rules.",,https://github.com/caict-develop-zhangbo/vaa-method/blob/master/README.md,,Specification,,BIF,DID Methods,,,,,,,,2020-08-05,,,,,,,,,,,,,
+DID Methods,Attila Aldemir,did:bba:,,,,,,,,did:bba:,"The `bba` DID method aims to enable the Ardor blockchain to act as a DPKI within the SSI ecosystem. It runs on the independent IGNIS child chain and utilizes Ardors Account Properties feature to manage DIDs and corresponding DID controllers. The Account Properties feature provides the possibility to tag an account with a small amount of data (160 characters). A DID controller is always represented in form of an Ardor account and is by default separated from the public keys (if present) embedded in a DID document. Think of a master key controlling the DID operations create, update and deactivate. A DID controller always corresponds to exactly one Ardor account, whereas one Ardor account can control multiple DIDs.<br><br>DID and DID document handling is decoupled so that multiple DID document storages can be defined and integrated to store DID document templates (DID documents without a DID reference). In its current state, the `bba` DID method defines only one storage type (Ardor Cloud Storage).<br>In the following, `bba` DID method compliant account properties are called DID attestations. An account property is `bba` DID method compliant if it aligns to the data model described in the DID Attestation Data Fields section and is self-set. A self-set account property is a property in which sender and receiver accounts are identical.",,https://github.com/blobaa/bba-did-method-specification/blob/master/docs/markdown/spec.md,,Specification,,Ardor,DID Methods,,,,,,,,2020-08-31,,,,,,,,,,,,,
+DID Methods,Hydra Hashgraph,did:morpheus,,,,,,,,did:morpheus,"Distributed ledger technologies (DLT, blockchain) are mostly used by cryptocurrencies, but their event ordering and decentralized consensus algorithms are useful for general purpose. Morpheus needs DLT for safe ordering DID updates and querying the historical state of a DID Document at any given point of time for signature validation. The main benefit of DLTs is that many parties with opposing interests run the infrastructure, therefore it is almost impossible to unilaterally control changes to the history and state of the ledger.",,https://developer.iop.technology/w3c?id=iop-morpheus-did-method,,Specification,,IOP Global,DID Methods,,,,,,,,,,,,,,,,,,,,,
+DID Methods,Ontology Foundation,did:etho:,,,,,,,,did:etho:,"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.",,https://github.com/ontology-tech/DID-method-specs/blob/master/did-etho/DID-Method-etho.md,,Specification,,Ethereum,DID Methods,,,,,,,,2020-08-14,,,,,,,,,,,,,
+DID Methods,Ontology Foundation,did:bnb:,,,,,,,,did:bnb:,"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.",,https://github.com/ontology-tech/DID-method-specs/blob/master/did-bnb/DID-Method-bnb.md,,Specification,,Binance Smart Chain,DID Methods,,,,,,,,2020-08-14,,,,,,,,,,,,,
+DID Methods,Ontology Foundation,did:celo:,,,,,,,,did:celo:,"This Celo DID method specification describes a new DID method, that is, Celo DID and defines how Celo blockchain stores Celo DIDs and their corresponding DID documents, and how to do CRUD operations on Celo DID documents.",,https://github.com/ontology-tech/DID-method-specs/blob/master/did-celo/DID-Method-celo.md,,Specification,,Celo,DID Methods,,,,,,,,2020-08-14,,,,,,,,,,,,,
+DID Methods,Ontology Foundation,did:klay:,,,,,,,,did:klay:,"Decentralized identifiers (DIDs) are a new type of identifiers that enables verifiable, self-sovereign digital identity. This Klaytn DID method specification describes a new DID method, that is, Klaytn DID and defines how Klaytn blockchain stores Klaytn DIDs and their corresponding DID documents, and how to do CRUD operations on Klaytn DID documents.",,https://github.com/ontology-tech/DID-method-specs/blob/master/did-klay/DID-Method-klay.md,,Specification,,Klaytn,DID Methods,,,,,,,,2020-08-14,,,,,,,,,,,,,
+DID Methods,Ontology Foundation,did:trx:,,,,,,,,did:trx:,"This TRON DID method specification describes a new DID method, that is, TRON DID and defines how TRON blockchain stores TRON DIDs and their corresponding DID documents, and how to do CRUD operations on TRON DID documents.",,https://github.com/ontology-tech/DID-method-specs/blob/master/did-trx/DID-Method-trx.md,,Specification,,TRON,DID Methods,,,,,,,,2020-08-14,,,,,,,,,,,,,
+DID Methods,GRGBanking Blockchain Express,did:grg:,,,,,,,,did:grg:,"GRG did document security authentication is based on the cryptography algorithm. A signature is used to verify that the claim is from a trusted did user. What should be noted is the authenticity verification of the issuer. An alliance blockchain maintained by an official organization is designed and used. In the alliance chain, the did document of the certification authority should be stored, and its did ID number should be displayed on the official website of the relevant organization. Therefore, the verifier can verify claims based on this information.",,https://github.com/GrgChain/DID-method-specs/blob/master/README.md,,Specification,,GrgChain,DID Methods,,,,,,,,2020-08-01,,,,,,,,,,,,,
+DID Methods,51nodes GmbH,did:schema:,,,,,,,,did:schema:,The Schema Registry DID Method aims to provide unique and universal identification for schemas in multiple formats hosted on multiple storage mechanisms or networks.,,https://github.com/51nodes/schema-registry-did-method/blob/master/README.md,,Specification,,"Portable, IPFS, evan.network",DID Methods,,,,,,,,2020-08-26,,,,,,,,,,,,,
+DID Methods,CCG,did:key,,"Rick Astley, Manu Sporny, Dmitri Zagidulin, Dave Longley, Orie Steele",,,,,,did:key,"Ledger independent DID method based on public/private key pairs.<br><br>While DLT-based DID Methods have great decentralization characteristics, and some of the more centralized DID Methods provide strong system control guarantees, the general approaches tend to be expensive to setup and operate. Some use cases requiring DIDs do not need the guarantees provided by these heavy-weight systems. For example, a DID that will only be used for a single, ephemeral interaction might not need to be registered, updated, or deactivated. It is for this class of use cases that the did:key method exists",,https://w3c-ccg.github.io/did-method-key/,,Specification,,"Portable, IPFS, evan.network",DID Methods,,,,,,,,2022-09-02,,,,,,,,,,,,,
+DID Methods,CCG,,,,did:key,,,,,did-key-creator published,"This has been tested to create did:keys from the P-256,P-384, and P-521 curves specified in https://github.com/w3c-ccg/did-method-key and https://w3c-ccg.github.io/did-method-key/","This is a library for converting public keys to the did:key format. Latest version: 1.2.0, last published: 7 months ago. Start using did-key-creator in your project by running `npm i did-key-creator`. There is 1 other project in the npm registry using did-key-creator.",https://www.npmjs.com/package/did-key-creator,,Code,,"Portable, IPFS, evan.network",DID Methods,,,,,,,,2022-11-03,,,,,,,,,,,,,
+DID Methods,Crates,,,Tomislav Markovski,did:key,,,,,Rust implementation of the did:key method,"This crate is intended to provide basic support for did:key methods. It has no external dependencies and can be compiled for any target. It was originally designed for use with DIDComm Extension for gRPC, but we recognized it may be useful if this was an independent library",,https://crates.io/crates/did-key,,Code,,"Portable, IPFS, evan.network",DID Methods,,,,,,,,2022-11-28,,,,,,,,,,,,,
+DID Methods,Tryon,did:tyron:,,"Julio, Cabrapan Duarte",,,,,,did:tyron:,"Tyronzil is the W3C Decentralized Identifier Method of the Tyron Self-Sovereign Identity Protocol. You can find it published at the W3C DID Specification Registries, and it is the first DID Method of the Zilliqa blockchain - funded by ZILHive Innovation grants.",,https://www.tyronzil.com/,,Specification,,Zilliqa,DID Methods,,,,,,,,,,,,,,,,,,,,,
+DID Methods,"Persistent Systems, R3",did:corda:,,"Nitesh Solanki, Moritz Platt, Pranav Kirtani",,,,,,did:corda:,"To understand the environment in which the Corda DID method operates, the permissioned nature of a Corda network and the point-to-point approach to data replication must be taken into account. While parties in permissionless blockchains remain anonymous and can join and leave at will, any Corda network utilizes a standard PKIX infrastructure for linking public keys to identities [corda-whitepaper]. As such, individually deployed entities in the network – nodes – have a strong notion of identity. This concept is instrumental in network communication. Similarly, the data-replication model implemented in Corda is different to that of a conventional public blockchain, which makes all in-ledger data visible to all network participants. In Corda, data are distributed to a configurable subset of network members only.<br><br>The Corda DID method operates in an environment where multiple nodes form a consortium in order to replicate decentralized identity data (cf. figure 1). These consortium nodes replicate decentralized identifier documents to form a network-wide and, ultimately, consistent view of the unity of decentralized identifiers, using the Corda DID method.",,https://htmlpreview.github.io/?https://github.com/persistentsystems/corda-did-method/blob/master/corda_did_method.html,,Specification,,Corda,DID Methods,,,,,,,,2020-09-21,,,,,,,,,,,,,
+DID Methods,Space Elephant,did:uns:,https://docs.uns.network/,,,,,,,did:uns:,"The goal of this method is to work in tandem with other, more complex DID methods based on the same blockchain. Uns.network is dedicated to the management of Non Fungible Tokens (NFT). The first type of NFT that it supports is [@uniknames](https://docs.unikname.com/), human-readable identifiers. Just like any other tokens, @uniknames can be bought or exchanged, but they can also be linked to public properties the owner wishes to advertise, or used to connect to compliant websites in a private and secure fashion, among other things. The `unik` DID method associates a DID to these NFT tokens, using uns-did as controllers.",,https://github.com/unik-name/did-method-spec/blob/main/did-uns/UNS-DID-Specification.md,,Specification,,UNS Network,DID Methods,,,,NFT,,,,2020-10-16,,,,,,,,,,,,,
+DID Methods,MediBloc,did:panacea:,,,,,,,,did:panacea:,"Panacea is a public blockchain built by MediBloc to reinvent the healthcare experience. Panacea also supports DID operations. DIDs are created and stored in the Panacea, and they are used with verifiable credentials.",,https://github.com/medibloc/panacea-core/blob/master/docs/did.md,,Specification,,Panacea,DID Methods,,,,,,,,2020-10-10,,,,,,,,,,,,,
+DID Methods,Hyperledger Foundation,did:indy:,,,,,,,,did:indy:,"Indy is a public ledger designed specifically and only for privacy-preserving self-sovereign identity. A Hyperledger Indy ledger is designed specifically to enable the use of verifiable credentials, allowing credential issuers to publish data necessary for issuing verifiable credentials and constructing presentations from those verifiable credentials. This specification covers how DIDs on an Indy ledger are managed and the operations for creating, reading, updating, and deleting DIDs.",,https://github.com/hyperledger/indy-did-method,,Specification,,Hyperledger Indy,DID Methods,,,,,,,,2023-02-23,,,,,,,,,,,,,
+DID Methods,IDCommons,,,Stephen Curran,did:indy:,,,,IIW,The did:indy DID Method - Future Indy Ledgers,Getting involved with this work:,,https://iiw.idcommons.net/4I/_The_did:indy_DID_Method_-_Future_Indy_Ledgers,,Session Notes,,Hyperledger Indy,DID Methods,,,,,,,,2021-05-06,,,,,,,,,,,,,
+DID Methods,BCGov,,,Stephen Curran,did:indy:,,,,,did:indy Presentation,"- Namespaced DIDs useful across all Indy instances<br>- Indy network discovery<br>- Full DIDDoc support<br>- Namespaced identifiers for other Indy objects (schemas, etc.)<br>- Support for important resolution parameters<br>- E.g. version-id, version-time, resource<br><br>Nice to have (but not likely to be there):<br>- Cross-ledger registration of networks for discovery<br>- Support for KERI identifiers on Indy networks<br><br>Getting involved with this work:<br>- [HackMD Document](https://hackmd.io/@icZC4epNSnqBbYE0hJYseA/S1eUS2BQw) with current spec<br>- Home of future spec: [indy-did-method](https://github.com/hyperledger/indy-did-method)<br>- [Meeting Wiki](https://wiki.hyperledger.org/display/indy/Indy%2BDID%2BMethod%2BSpecification) and schedule<br>- Hyperledger [indy-did-method](https://chat.hyperledger.org/channel/indy-did-method) chat channel",,https://docs.google.com/presentation/d/1c5K7E5CRx9ANuwmVBIyFVG5hJ4lH0EyW-wkmraLivBI/edit?usp%3Dsharing,,Presentation,,Hyperledger Indy,DID Methods,,,,,,,,2021-04-20,,,,,,,,,,,,,
+DID Methods,Blockchain Commons,did:onion:,,,,,,,,did:onion:,"🧅 part of the torgap technology family<br>DIDs that target a distributed ledger face significant practical challenges in bootstrapping enough meaningful trusted data around identities to incentivize mass adoption. We propose using a new DID method that allows them to bootstrap trust using a Tor Hidden Service's existing reputation.<br><br>we'd like to review more with our community how close we want to keep did:onion to did:web, and if we want to incorporate some elements of did:peer or KERI or to leverage services like Open Time Stamps.",,http://htmlpreview.github.io/?https://raw.githubusercontent.com/BlockchainCommons/did-method-onion/main/index.html,,Specification,,Tor,DID Methods,,,,,,,,2021-08-06,,,,,,,,,,,,,
+DID Methods,Ceramic,did:nft:,,,,,,,,did:nft:,"The NFT DID Method converts any non-fungible token on any blockchain into a decentralized identifier where the owner of the NFT is the controller of the DID. This is achieved by using the Chain Agnostic Improvement Proposals to describe NFT assets and blockchain accounts, as well as the Ceramic network to find the DID associated with the owner of the NFT.",,https://github.com/ceramicnetwork/CIPs/blob/main/CIPs/cip-94.md,,Specification,,Ethereum,DID Methods,,,,,,,,2021-02-12,,,,,,,,,,,,,
+DID Methods,Gimly,did:eos:,,,,,,,,did:eos:,"1. Identity - the management of accessible public key infrastructure and identifies. Decentralized Identifiers is the W3C standard that allows this. Compliance with this standard allows application layers to interoperate without a need to understand the base layer decentralised protocols that power identities.<br>2. Application - use of the identity layer to interact and provide meaningful, secure and verifiable data communications and interaction. The Verifiable Credentials W3C standard is the most prominent and adopted standard here which is a data structure and message protocol allowing people and organisations to securely and in a verifiable way send and verify information about themselves ""credentials"" to each other. DIDComm is another important application layer that uses DID methods to communicate between SSI identities.",,https://github.com/Gimly-Blockchain/eosio-did-spec,,Specification,,EOS,DID Methods,,,,,,,,2021-06-30,,,,,,,,,,,,,
+DID Methods,Gimly,,,,did:eos:,,,,,The EOSIO DID method specification,"We have been working with the [Decentralised Identity Foundation](https://identity.foundation) to shape this specification, and also want to thank the [W3C Credentials Community Group](https://www.w3.org/community/credentials/) for their support in the creation of the [Verifiable Condition](https://github.com/Gimly-Blockchain/verifiable-conditions) type, a necessary component to create the EOSIO DID document to represent EOSIO account permissions.",Gimly has built a full draft of the EOSIO Decentralised Identifier (DID)  method specification. This specification guides the implementation of DIDs  on EOSIO powered blockchains.,https://www.gimly.io/blog/the-eosio-did-method-specification,,Post,,EOS,DID Methods,,,,,,,,2021-04-02,,,,,,,,,,,,,
+DID Methods,SpruceID,did:did:,https://lists.w3.org/Archives/Public/public-credentials/2021Apr/0026.html,,,,,,,did:did:,"DID Identity DID (DID) DID method<br><br>Spruce announces did:did, a DID method based on Decentralized Identifiers (DIDs). We hope the community will find this useful to help increase adoption and interoperability of Decentralized Identity technology.",,https://github.com/spruceid/did-did/,,Specification,,humor,DID Methods,,,,,,,,2021-04-01,,,,,,,,,,,,,
+DID Methods,SpruceID,did:undid:,,,,,,,,did:undid:,"did:un-did is a DID method that enables using any valid Decentralized Identifier (DID) as a did:un-did DID, but more importantly it un-does the did that did:did did method performs.<br><br>*Clarification, a few week ago we shared about the [DID:DID](https://did-did.spruceid.com/) method. [April Fools Joke](https://en.wikipedia.org/wiki/April_Fools%2527_Day_RFC)!!! Here’s yet another DID method in the series.*",,https://did-undid.github.io/did-undid/,,Specification,,humor,DID Methods,,,,,,,,2021-04-01,,,,,,,,,,,,,
+DID Methods,SpruceID,did:doge:,,,,,,,,did:doge:,"We draw heavily from prior work by Christopher Allen and Kim Hamilton Duffy within the W3C Credentials Community Group on the BTCR DID Method due to strong architectural similarities between the Bitcoin and Dogecoin blockchains.<br><br>However, there are some key differences that enable new privacy-preserving benefits. Namely, the did:doge method-specific identifier is the Base58Check-encoded Dogecoin address itself, allowing for DID usage even in the absence of any public transaction histories and only relying upon them for rotation events for verification methods and service endpoints.",,https://spruceid.github.io/did-doge/index.html,,Specification,,Dogecoin,DID Methods,,,,,,,,2023-05-04,https://github.com/spruceid/did-doge,,,,,,,,,,,,
+DID Methods,"SpruceID, TQ Tezos",did:tz:,,,,,,,,did:tz:,"did:tz is a multi-modal DID method design with many offchain, on-chain, and side-chain/L2 use cases in mind. A valid Tezos address (controlled by a private key from any of 3 supported curves) can control an ""implicit"" DID document (generatively created from the address like a did:key), an ""onchain"" DID document (published via smart contract on any Tezos ledger), or have ""patches"" applied to it that are published and governed by a closed network or authority (including, for example, a sidetree network). In particular, this third option has not been specified in any detail, and we would be particularly curious to hear from implementers of such systems before further specifying it.",,https://github.com/w3c-ccg/did-tz,,Specification,,Tezos,DID Methods,,,,,,,,2022-01-13,,,,,,,,,,,,,
+DID Methods,"SpruceID, TQ Tezos",,,,did:tz:,,,,,Decentralized Identity with the Tezos DID Method,[Spruce](https://www.spruceid.com/) and [TQ Tezos](https://tqtezos.com/) are jointly releasing the [draft specification](https://did-tezos.spruceid.com/) and [initial implementation](https://github.com/spruceid/did-tezos) of [Decentralized Identifiers (DIDs)](https://www.w3.org/TR/did-core/) based on the Tezos blockchain.,"A DID Method geared for privacy, formal verification, and scaling to billions of identifiers by using off-chain updates. Spruce and TQ Tezos are jointly releasing the draft specification and initial…",https://sprucesystems.medium.com/decentralized-identity-with-the-tezos-did-method-d9cf6676dd64,,Post,,Tezos,DID Methods,,,,,,,,2021-03-03,,,,,,,,,,,,,
+DID Methods,Unisot,did:unisot:,,,,,,,,did:unisot:,The UNISOT DID method uses the Bitcoin SV blockchain to generate DIDs as well as potentially store the associated DID documents. The method allows for storage of DID documents on-chain as well as off-chain depending on the business use case scenario.,,https://gitlab.com/unisot-did,,Specification,,Portable,DID Methods,,,,,,,,2020-11-25,,,,,,,,,,,,,
+DID Methods,Unisot,,,Annemie Bergmans,"EBSI, did:unisot",,,"ESSIF, GDPR",,UNISOT DID approved by W3C,We are proud to have UNISOT ID (did:unisot) listed at the Decentralized Identity Foundation (DIF). As part of our commitment to open technologies and global interoperability we have presented our DID schema (did:unisot) to the Decentralized Identity Foundation (DIF) and supplied a driver for their Universal DID Resolver which can be accessed at: [https://resolver.identity.foundation/](https://resolver.identity.foundation/). With this anyone can resolve a UNISOT DID Document in a trusted and easy way.,The UNISOT DID is compliant with W3C specifications,https://unisot.com/unisot-did-approved-by-w3c/,,Post,,Portable,DID Methods,,,,,,,,2021-05-25,,,,,,,,,,,,,
+DID Methods,SecureKey,did:orb:,,,,,,,,did:orb,"Orb is a decentralized identifier (DID) method based on a federated and replicated Verifiable Data Registry (VDR). The decentralized network consists of Orb servers that write, monitor, witness, and propagate batches of DID operations. The batches form a graph that is propagated and replicated between the servers as content-addressable objects. These content-addressable objects can be located via both domain and distributed hash table (DHT) mechanisms. Each Orb witness server observes a subset of batches in the graph and includes them in their ledgers (as append-only Merkle Tree logs). The servers coordinate by propagating batches of DID operations and by monitoring the applicable witness servers' ledgers. The Orb servers form a decentralized network without reliance on a common blockchain for coordination.",,https://trustbloc.github.io/did-method-orb/,https://trustbloc.github.io/did-method-orb/diagrams/flow-model.svg,Specification,,Federated,DID Methods,,,,,,,,2022-03-21,,,,,,,,,,,,,
+DID Methods,SecureKey,,,,did:orb:,,,,,Orb,"Orb implements the following specifications: [did:orb](https://trustbloc.github.io/did-method-orb/), [Activity Anchors](https://trustbloc.github.io/did-method-orb/). The did:orb method is based on the Sidetree specification and Activity Anchors is based on the ActivityPub and ActivityStreams specifications.<br><br>Please see [Read the Docs](https://trustbloc.readthedocs.io/en/latest/orb/index.html) for more details on Orb",A DID method implementation that extends the Sidetree protocol into a Fediverse of interconnected nodes and witnessed using certificate transparency. Spec: https://trustbloc.github.io/did-method-orb/ - GitHub - trustbloc/orb: A DID method implementation that extends the Sidetree protocol into a Fediverse of interconnected nodes and witnessed using certificate transparency. Spec: https://trustbloc.github.io/did-method-orb/,https://github.com/trustbloc/orb,,Code,,,DID Methods,,,,,Trustbloc,"ActivityPub, ActivityStreams, Sidetree",,2023-05-25,,,,,,,,,,,,,
+DID Methods,SecureKey,,,,did:orb:,,,,,SecureKey’s New Ledger-Agnostic did:orb,"did:orb that decouples DIDs from ledgers while maintaining trust and security. SecureKey is leveraging standard and open-source peer-to-peer protocols like ActivityPub, data structures like verifiable credentials content-addressed storage like IPFS, and distributed trust services like the Google Trillian project to build a peer-to-peer trust network.","Decentralized Identifiers are usually thought of as being bound to a particular ledger and blockchain, such as SecureKey’s first DID Method.",https://securekey.com/securekeys-new-ledger-agnostic-solution-orb-helps-solve-decentralized-identifier-challenges/,,Post,,,DID Methods,,,,,,"ActivityPub, IPFS, verifiable credentials",,2021-06-10,,,,,,,,,,,,,
+DID Methods,CCG Mailing List,,,Troy Ronda,"did:orb:, ",,,,,did:orb slides Troy Ronda (SecureKey),* Decouple witness ledgers from the critical path.<br>- Allow for Trust but Verify model.<br>- Leverage the Certificate Transparency model<br>- Witnesses observe VDR objects and promise to include in their ledgers.<br>- Provide a signed timestamp and a maximum merge delay.<br>- Enable monitoring to ensure witnesses follow their promises.<br>- Use trusted Witness (and origin) timings to resolve late publishing.<br>- Use origin to enable observers to know if they have the latest operations.,,https://lists.w3.org/Archives/Public/public-credentials/2021Mar/0017.html,,Presentation,,,DID Methods,,,,,,,,2021-03-03,,,,,,,,,,,,,
+DID Methods,Trusted Digital Web,,,Michael Herman,,,,,,did:object,"This ""DID Object"" Decentralized Identifier Method Namespace Specification (""DID Object"" DID Method Namespace Specification) defines the end-to-end lifecycle of DID Identifiers and DID Documents for ""DID Objects"", a key feature of the Fully Decentralized Objects (FDOs) Framework, implemented by the Trusted Digital Web.","Trusted Digital Web (TDW): Trusted Digital Assistant (TDA), Trusted Resource Agent (TRA), Key Management Agent (KMA), and Verifiable Data Agent (VDA) - TrustedDigitalWeb/did-object.md at master · mwherman2000/TrustedDigitalWeb",https://github.com/mwherman2000/TrustedDigitalWeb/blob/master/specifications/did-methods/did-object.md,,Specification,,,DID Methods,,,,,,,,2022-01-26,,,,,,,,,,,,,
+DID Methods,Personal,,,Bob Wyman,,,,,,did:tag,"The did:tag DID method enables any controller of an HTTP accessible domain or subdomain, or of an email address, to create unique, interoperable, persistent DIDs with minimal dependencies on other technologies or systems. By leveraging a subset of the tagURI specification [RFC4151], the did:tag DID method enables the creation of DIDs which are ""unique across space and time while being tractable to humans,"" without preventing the creation of DIDs which are largely intractable to humans. did:tag DIDs can be resolved either synchronously, via the web, or asynchronously, via email or other defined alternative resolution services.",ROUGH DRAFT: did:tag Decentralized Identifier Method Specification - GitHub - bobwyman/did_method_tag: ROUGH DRAFT: did:tag Decentralized Identifier Method Specification,https://github.com/bobwyman/did_method_tag,,Specification,,,DID Methods,,,,,,,,2021-11-02,,,,,,,,,,,,,
+DID Methods,CCG Mailing List,,,Bob Wyman,,,,,,re: Using Email as an Identifier,"There are quite a number of issues with using email addresses as identifiers, or parts of identifiers, and I'm hoping that discussion and development of the did:tag method will illuminate those issues and potentially find solutions for them.",,https://lists.w3.org/Archives/Public/public-credentials/2021Nov/0065.html,,Discussion,,,DID Methods,,,,,,,,2021-11-12,,,,,,,,,,,,,
+DID Methods,"waltid, transmute",,,,did:key,,,,,did:jwk,did:jwk is a deterministic transformation of a JWK into a DID Document.,,https://github.com/quartzjer/did-jwk/blob/main/spec.md,,Specification,,,DID Methods,,,,,,JWK,,2022-04-14,,,,,,,,,,,,,
+DID Methods,CCG,,,,,,,,,did:pkh,"allows most if not all blockchain accounts to instantly leverage an existing identity/account and deploy a W3C Decentralized Identifier from it in a standards-conformant way. This ""DID-wrapping"" of an existing identifier can be used in combination with other DID-compatible technologies, such as W3C Verifiable Credentials or Authorization Capabilities, and produce proper signature-suite definitions, such as ""metamask-signing"" (off-chain signing by externally-owned accounts, i.e., personal wallets, according to the eip712 protocol).",We would like to open up the design process for did:pkh to a more open and consultative/deliberative conversation in the open. - did-pkh/did-pkh-method-draft.md at main · w3c-ccg/did-pkh,https://github.com/w3c-ccg/did-pkh/blob/main/did-pkh-method-draft.md,,Specification,,,DID Methods,,,,,,,,2023-01-27,,,,,,,,,,,,,
+DID Methods,Verite,,,,did:pkh,,,,,"Verification Patterns, Part 2","explains the [did:pkh](https://github.com/w3c-ccg/did-pkh/blob/main/did-pkh-method-draft.md)/[CACAO](https://github.com/ChainAgnostic/CAIPs/blob/master/CAIPs/caip-74.md%23simple-summary) variation for Verite data models and flows, which provides an entry path for wallets that may not support sufficient functionality for emerging decentralized identity patterns","Exploration of Verite verification patterns, with a focus on non-DID wallets. Part 2 in a 2-part series",https://docs.centre.io/blog/verification-patterns-2,https://docs.centre.io/assets/images/verifier_cacao-92d2ea3dba6784af5ecb1bf28b56e52b.jpg,Post,,,DID Methods,,,,,,,,2022-07-27,,,,,,,,,,,,,
+DID Methods,Veramo Labs,,,,,,,,,did:ens,1. to wrap existing ENS names as DIDs to be interoperable with applications relying on Decentralized Identifiers<br>2. to define a canonical way to augment ENS names with DID capabilities such as services and verification methods.,,https://github.com/veramolabs/did-ens-spec,,Specification,,,DID Methods,,,,,,,,2021-10-05,,,,,,,,,,,,,
+DID Methods,uPort,,,Oliver Terbu,,,,,,ENS names are Decentralized Identifiers (DIDs),"The specification is extensible by design which means new types of services, verification materials and other features can be supported. In the core, the specification contains a simple interface to resolve a DID Document from a DID (similar to an Ethereum Account from an ENS name) by anyone who knows the DID of the user. The DID Document will then contain the relevant information to enable use cases such as sign up, sign in, data encryption, secure communication, verifiable authorship and data provenance etc. Since DIDs are URI-compliant, they also make perfect sense for web ontologies.",,https://medium.com/uport/ens-names-are-decentralized-identifiers-dids-724f0c317e4b,,Post,,,DID Methods,,,,,,,,2021-10-19,,,,,,,,,,,,,
+DID Methods,TIFAC-CORE in Cyber Security,,,"Ramaguru Radhakrishnan, Amrita Vishwa Vidyapeetham",,,,,,did:avvcyber:,"TIFAC-CORE in Cyber Security, Amrita School of Engineering, Amrita Vishwa Vidyapeetham Coimbatore is Center of Relevance and Excellence (CORE) in Cyber Security. The Center is working toward Cryptography, Visual Cryptography, Steganography, Cyber Forensics, Machine Learning and Blockchain Technology. There are multiple projects being worked across domains where we are using  DIDs. did:avvcyber: is a dedicated DID created for all our Blockchain Projects from 2022.",,https://github.com/Amrita-TIFAC-Cyber-Blockchain/DID-AVVCYBER/blob/main/did-avvcyber-v1.md,,Code,,,DID Methods,,,,,,,,2022-01-01,,,,,,,,,,,,,
+W3C,,W3C,,,,,,,,World Wide Web Consortium (W3C),The World Wide Web Consortium (W3C) is an international community that develops open standards to ensure the long-term growth of the Web.,,https://w3.org,,site,,,Main,,,,,,,,,,,,,,,,,,,,,
+W3C,ICANN Wiki,,,,,,,,,W3C - ICANN WIki,"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).",,https://icannwiki.org/W3C,,entry,,,Main,,,,history,,,,2022-04-05,,,,,,,,,,,,,
+W3C,W3C,,,,,,,,,World Wide Web Consortium (W3C),"an international community where Member organizations, a full-time staff, and the public work together to develop Web standards. Led by Web inventor and Director Tim Berners-Lee and CEO Jeffrey Jaffe, W3C's mission is to lead the Web to its full potential.",,https://www.w3.org/Consortium/,,page,,,Main,,,,,,,,2022-06-01,https://github.com/w3c,https://twitter.com/w3c,,,,,,https://www.linkedin.com/company/w3c/,,,,,
+W3C,W3C,,,,,,,,,W3C Mission,On 29 August 2012 five leading global organizations jointly signed an agreement to affirm and adhere to a set of Principles in support of The Modern Paradigm for Standards; an open and collectively empowering model that will help radically improve the way people around the world develop new technologies and innovate for humanity.,,https://www.w3.org/Consortium/mission,,page,,,Main,,,,history,,,,2023-01-01,,,,,,,,,,,,,
+W3C,W3C,,,,,,,,,Facts About W3C,"In 1989, Tim Berners-Lee invented the World Wide Web (see the original proposal). He coined the term ""World Wide Web,"" wrote the first World Wide Web server, ""httpd,"" and the first client program (a browser and editor), ""WorldWideWeb,"" in October 1990. He wrote the first version of the ""HyperText Markup Language"" (HTML), the document formatting language with the capability for hypertext links that became the primary publishing format for the Web. His initial specifications for URIs, HTTP, and HTML were refined and discussed in larger circles as Web technology spread.",,https://www.w3.org/Consortium/facts.html,,page,,,Main,,,,history,,,,2023-01-01,,,,,,,,,,,,,
+W3C,W3C,,,,,,,,,Standards - W3C,"W3C standards define an Open Web Platform for application development that has the unprecedented potential to enable developers to build rich interactive experiences, powered by vast data stores, that are available on any device. Although the boundaries of the platform continue to evolve, industry leaders speak nearly in unison about how HTML5 will be the cornerstone for this platform. But the full strength of the platform relies on many more technologies that W3C and its partners are creating, including CSS, SVG, WOFF, the Semantic Web stack, XML, and a variety of APIs.",,https://www.w3.org/standards/,,page,,,Main,,,,,,,,2021-01-01,,,,,,,,,,,,,
+W3C,W3C,,,,,,,,,W3C Workshop on Strong Authentication & Identity,"The W3C Strong Authentication and Identity Workshop gathered experts in the space to explore the existing standards landscape, examine existing technology roadmaps, and identify potential future work for how strong identity and strong authentication should work on the web. The workshop explored aligning recent W3C specifications (WebAuthn, Verifiable Claims, Web Payments) and work that is ongoing in the W3C Credentials Community Group (DID, DIDAuth) along with the IETF and ISO, as well as other existing community standards such as IndieAuth, Open ID Connect, OAuth, and SAML.",,https://www.w3.org/Security/strong-authentication-and-identity-workshop/report.html,,page,,,W3C ID History,,,,,,,,2018-12-11,,,,,,,,,,,,,
+W3C,W3C,,,Tim Berners-Lee,,,,,,A Public Identity,"The world of the last few years has been buzzing with the need for personal privacy a world in which personal data is typically abused by large corporations on the (mistaken) belief that this is the only business model in a connected world. It seems to have got to the point where there has been so much focus on protecting the identity of an individual online that we have actually made it difficult, frustratingly and unnecessarily difficult, to actually claim a completely public identity online.",,https://www.w3.org/DesignIssues/PublicIdentity.html,,page,,,W3C ID History,,,,,,,,2018-01-19,,,,,,,,,,,,,
+W3C,W3C,,,,,,,,,Call for Participation in Digital Identity Community Group,"The mission of the W3C Digital Identity Community Group is to identify and resolve real world identity issues, to explore and build a more secure trusted digital identity ecosystem on internet for people, organizations and things fully controlling, protecting and expressing their identity. Our work focuses on the ecosystem’s scalability, interoperability, mobility, security and privacy. We intend to integrate interoperable identity solutions, systems and networks in our ecosystem.",,https://www.w3.org/community/dic/2019/06/20/call-for-participation-in-digital-identity-community-group/,,Post,,,W3C ID History,,,,,,,,2019-06-20,,,,,,,,,,,,,
+W3C,W3C,,,,,,,,,The Platform for Privacy Preferences 1.1 (P3P1.1) Specification,"This is the specification of the Platform for Privacy Preferences 1.1 (P3P 1.1). This document, along with its normative references, includes all the specification necessary for the implementation of interoperable P3P 1.1 applications. P3P 1.1 is based on the P3P 1.0 Recommendation and adds some features using the P3P 1.0 Extension mechanism. It also contains a new binding mechanism that can be used to bind policies for XML Applications beyond HTTP transactions.",,https://www.w3.org/TR/P3P11/,,Specification,,,W3C ID History,,,,,,,,2018-08-30,,,,,,,,,,,,,
+W3C,W3C,,,Tim Berners-Lee 1998,,,,,,Web Design Issues - Identity,"Identifiers - what is identified?<br>When XML is used to represent a directed laballed graph which is used to represent information about things, then one must be able to make statements about parts of an XML document, parts of the DLG (such as RDF nodes) and of course the objects described.",,https://www.w3.org/DesignIssues/Identity.html,,page,,,W3C ID History,,,,,,,,2009-08-27,,,,,,,,,,,,,
+W3C,W3C,,,,,,,,,Identity Interoperability,"TimBL's diagram at TPAC2012Over the years many different authentication systems have been developed. Each one proposes a method for an agent to prove his relation to an identifier - called a Principal. A Principal is a string that can be mapped to a URI, that usually refers to some network resource, which itself can then be linked to a subject. An LDP authorization system may authenticate agents that are allowed access to a resource using different types of Principals. This page lists a number of ways Authorization agents can prove identity of an agent using one Principal, with an ACL that may be using a different type of Principal. The aim is to gather such examples together in order to find an general theory that underpins these proofs.",,https://www.w3.org/2005/Incubator/webid/wiki/Identity_Interoperability,https://www.w3.org/2005/Incubator/webid/wiki/images/thumb/2/2f/IdentityInterop.jpg/250px-IdentityInterop.jpg,Post,,,W3C ID History,,,,,,,,2013-01-07,,,,,,,,,,,,,
+W3C,W3C,,,,,,,,,Identity Definitions in the P3P Specification,"The P3P Specification Working Group has taken the view point that most information referring to an individual is «identifiable» in some way. As with other important areas of the specification, the goal of the working group was to allow for a wide variety of understandings of identity in order to allow data collectors to best express their policy and users to make choices based on a definition of identity information that is important to them. (1)",,https://www.w3.org/P3P/2003/09-identifiable.html,,page,,,W3C ID History,,,,,,,,2006-11-13,,,,,,,,,,,,,
+W3C,W3C,,,"IdentityWoman, Phillip J. Windley, Aldo Castaneda",IDCommons,,,,,Identity Rights Agreements and Provider Reputation,"Abstract: While decentralized, user-centric identity systems provide hope that useful, secure identity systems may be possible on the Internet, ensuring that user data is protected in these system requires more than a technical solution. In this paper, we describe a project underway at Identity Commons to create a framework within which users can express their protection preferences (called identity rights agreements). Part of this project will establish a reputation system for identity providers and relying parties that engenders trust and lowers user risk.",IDENTITY COMMONS Position Paper,https://www.w3.org/2005/Security/usability-ws/papers/26-idcommons/,,page,,,W3C ID History,,,,,,,,2006-01-26,,,,,,,,,,,,,
+W3C,W3C,,,,,,,,,W3C Workshop on Identity in the Browser,"Over the last ten years, for most end-users there has been no visible progress beyond cookie-managed usernames and passwords entered via HTML forms. Current password-based logins offers little value to the end-user, as they are forced to bear the onerous responsibility of remembering too many passwords or simply re-using low-security passwords. <br><br>As passwords and cookies are easily compromised, both web-site operators and users then expose themselves to massive security breaches. Despite the large amount of valuable standardization work on identity, it is unclear how user agents such as Web browsers can interact with both identity-consuming applications and server-side federated identity services, and many current identity specifications either assume or underspecify secure authentication in the browser. The key missing component to enable trusted identity on the Web is likely then to be found in user-centric cross-browser standards for secure authentication and session management.",,https://www.w3.org/2011/identity-ws/report.html,,Report,,,W3C ID History,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,,,Channy Yun,,,,,A draft charter of Web Identity,The W3C has prepared Web Identity working group and make a draft charter. As following is main track for works.,,https://www.w3.org/community/webcryptoapi/2011/10/05/a-draft-charter-of-web-identity/,,Post,,,W3C ID History,,,,,,,,2011-10-05,,,,,,,,,,,,,
+W3C,W3C,,,,,,,,,"ISSUE-17: Identity, Agent, Person, Persona, Account etc. need clarifications",As for today we don't seem to have clear strategy on how to define and use Online Identity related concepts.,,https://www.w3.org/Social/track/issues/17,https://www.w3.org/2008/site/images/icons/atom,page,,,W3C ID History,,,,,,,,2015-03-03,,,,,,,,,,,,,
+W3C,W3C,,,,,,,,,WebID,"The W3C is still exploring better ways to do authentication, for example in the [2014 workshop on authentication](http://www.w3.org/2012/webcrypto/webcrypto-next-workshop/Overview.html). The WebID is a Community Group, and anyone can start a Community Group. A Community Group does not necessarily reflect the endorsement of the W3C, but we encourage grassroots communities to experiment with technology that may become a future standard.",,https://www.w3.org/wiki/WebID,https://www.w3.org/wiki/images/4/49/X509-Sense-and-Reference.jpg,entry,,,W3C ID History,,,,,,,,2018-06-17,,,,,,,,,,,,,
+W3C,W3C,,,,,,,,,USER IDENTITY ON THE WEB COMMUNITY GROUP,"Currently, more and more services are created on the web and require information about you, me, all of us. Therefore, users have to give away a lot of information about themselves to many different services. The point is that the users lose control of their identity on the web, by filling a lot of forms (e.g., through subscriptions). Privacy on the Internet is extremely important and must remain. Personal information is used by services we, sometimes, don't even know about, and it is a real problem. The aim of this group would be to think about new ways to identify individuals over the internet using trusted web based identities embedded directly into the core protocols of the web. At the same time it is important to maintain equilibrium between total privacy and providing information when needed, which means, when the user wants to.",,https://www.w3.org/community/w3id/,,org,,,W3C ID History,,,,,,,,2014-10-26,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Naveen Agarwal, Miranda Callahan, Tyler Close, Travis McCoy, Chris Messina, Glen Murphy, Dirk Pranke",Google,,,,,Identity in the Browser: Easy Wins and Guiding Principles,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_52.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Peter Alterman,NIH,,,,,National Strategy for Trusted Identities in Cyberspace - Requirements and Potential Use Cases,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_21.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Siddharth Bajaj, Slawek Ligier",Symantec,,,,,A Vision for Browser-Assisted Web Authentication,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_43.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Wendell Baker,Yahoo!,,,,,The Chained Identity Systems of Online Entertainment,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_14.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Dirk Balfanz,Google,,,,,Identity in the Platform - Thinking Beyond the Browser,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_26.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Patrik Bichsel, Dave Raggett, Rigo Wenning",,,,,,"Web authentication is deeply flawed, and it is time to fix it",,,https://www.w3.org/2011/identity-ws/papers/bichsel-raggett-wenning.html,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Aaron Brauer-Rieke,Center for Democracy & Technology,,,,,Considering Browsers' Role in a User-Centric Online Identity Ecosystem: Privacy and Context,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_24.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"David W Chadwick, George Inman, Kristy Siu",University of Kent,,,,,Expression of Interest - Improving Identity Management on the Internet,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_12.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Francisco Corella, Karen P. Lewison",Pomcor,,,,,"NSTIC, Privacy and Social Login",,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_48.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,D. Crocker,Brandenburg InternetWorking,,,,,Tailored Signatures with DOSETA,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_1.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Vito Fabbrizio, Greg Kerr",AuthenTec,,,,,AuthenTec Online Open Authentication,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_34.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Phillip Hallam-Baker,Comodo Group,,,,,Account Management: A Deployment and Usability Problem,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_10.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Kaliya Hamlin, Mary Hodder",Personal Data Ecosystem Consortium,,,,,Empowering Individuals with Tools to Manage Their Personal Data for the Identity in the Browser,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_54.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Mike Hanson, Dan Mills, Ben Adida",Mozilla,,,,,Federated Browser-Based Identity using Email Addresses,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_25.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Dick Hardt,,,,,,"The Chicken, the Egg and the Rooster: Why Internet Identity is Still Unsolved",,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_46.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Sam Hartman (Painless Security), Josh Howlett",JANET(UK),,,,,Identity as a Platform Service,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_9.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Carl Hewitt,,,,,,"Looming private information fiasco versus the new cloud business model: The next generation will ask ""Where were you when this was going down?""",,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_45.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Brad Hill,,,,,,Identity in the Browser - Avoiding Common Flaws,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_37.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Frederick Hirsch,Nokia,,,,,Importance and Impact of Requirements on Technical Solutions for Identity,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_31.html,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Jonas Hogberg,Ericsson,,,,,Mobile Provided Identity Authentication on the Web,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_20.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Maryann Hondo, Mary Ellen Zurko, Matthew Flaherty, Paula K. Austel, Sridhar Muppidi",IBM,,,,,The Nexus of Identity,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_35.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,John Hwang,Neustar,,,,,How to Improve the Security around the Mobile User Authentication Process?,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_6.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Phil Hunt,Oracle,,,,,Evolution of Identity in the Face of a New Lightweight Web Services Paradigm Shift,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_56.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Michael B. Jones,Microsoft,,,,,The Emerging JSON-Based Identity Protocol Suite,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_30.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Kevin Jones, Narm Gradiraju, Jack Matheson",Intel,,,,,Identity Security within Web Browsers,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_8.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Vladimir Katardjiev, Goran Eriksson",LM Ericsson AB,,,,,Selected issues with web identity mechanisms and a possible way forward,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_18.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"James Klo, Marie Bienkowski",SRI International,,,,,Identity in the Federal Learning Registry,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_27.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,John Linn,RSA/EMC,,,,,"Goals, Constraints, and Issues for Identity in the Browser",,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_2.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Ben Livshits,Microsoft,,,,,Browser Personas: Towards a Reasonable Middle Ground,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_40.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Brian Mcginnis, Johnny Bufu, Vlad Skvortsov",Echo,,,,,Backplane Protocol and Identity Scenario,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_49.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Miguel A. Monjas, Jose M. del Alamo, Juan-Carlos Yelmo, Jonas Hogberg",Ericsson,,,,,Privacy Delegate: a browser-based tool for privacy self-management in social networks,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_19.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"RL ""Bob"" Morgan","University of Washington, InCommon",,,,,Browser support for identity federation with many identity providers,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_29.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Yutaka Oiwa, Tatsuya Hayashi, Boku Kihara",AIST,,,,,Reparing HTTP authentication for Web security,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_36.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Mike Perry,The Tor Project,,,,,Bridging the Disconnect Between Web Privacy and User Perception,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_38.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Yngve Pettersen,Opera Software ASA,,,,,Improving password managers and multidevice synchronization,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_47.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Anders Rundgren,PrimeKey Solutions AB,,,,,Two-factor Authentication for the Cloud,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_11.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Jeff Sayre, Henry Story",,,,,,The WebID Protocol & Browsers,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_22/webid.html,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Stephen Schultze,Princeton University,,,,,"Thoughts on Trust Infrastructure, User Interface, and Legal Issues",,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_50.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Dan Schutzer,Financial Services Roundtable/BITS,,,,,Statement of Interest and Requirements for W3C Workshop on Identity in the Browser,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_33.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,David Singer,Apple,,,,,Do you know who I am?,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_51.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Thomas J. Smedinghoff, Wildman Harrold",Allen & Dixon,,,,,Building the Legal Framework for Browser-Enabled Identity,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_39.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Manu Sporny, David Longley, David I. Lehn, Mike Johnson",Digital Bazaar,,,,,A WebID Implementation in Pure JavaScript and Flash,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_7.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Andy Steingruebl, Jeff Hodges",PayPal,,,,,Identity in the Browser: Putting the Cart Before the Horse,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_55.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Olivier Thereaux, Mo McRoberts, Richard Northover",British Broadcasting Corporation,,,,,A usable identity management system for the Digital Public Space,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_17.html,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Don Thibeau,"OpenID Foundation, OIX",,,,,On OIX and NSTIC,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_53.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,John Tolbert,The Boeing Company,,,,,Digital Identity in Perspective,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_57.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Paul Trevithick,Azigo,,,,,Identity In The Browser at 5. Lessons Learned,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_41.html,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Hannes Tschofenig, Barry Leiba, Blaine Cook, Rob van Eijk",,,,,,Browser Support for the Open Authorization (OAuth) Protocol,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_32.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Sean Turner, Stephen Farrell, Peter Saint-Andre",IETF,,,,,The Need for a Web Security API,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_28.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,M. Vanderveen,,,,,,Server Authentication with DNSSEC,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_3.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Yu Wang, Aanchal Gupta",Yahoo!,,,,,Browser Assisted Identity Management,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_15.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,"Mark Watson, Mitch Zollinger, Wesley Miaw",Netflix,,,,,"Position paper from Netflix, Inc.",,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_23.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Nicolas Williams,Cryptonector,,,,,"GSS-REST, a Proposed Method for HTTP Application-Layer Authentication",,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_16.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+W3C,W3C,,https://www.w3.org/2011/identity-ws/papers.html,Craig H. Wittenberg,Microsoft,,,,,Consumer Third Party Authentication: Challenges and Potential Solutions,,,https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_42.pdf,,Paper,,,ID in the Browser 2011,,,,,,,,2011,,,,,,,,,,,,,
+JSON-LD,json-ld.org,,,,,,,,,JSON-LD (json-ld.org),"Data is messy and disconnected. JSON-LD organizes and connects it, creating a better Web.",,https://json-ld.org/,,site,,,Main,,,,,,,,,,,,,,,,,,,,,
+JSON-LD,json-ld.org,,,,,,,,,JSON-LD Playground (json-ld.org),"The JSON-LD Playground is a web-based JSON-LD viewer and debugger. If you are interested in learning JSON-LD, this tool will be of great help to you. Developers may also use the tool to debug, visualize, and share their JSON-LD markup.",,https://json-ld.org/playground/,,tool,,,Main,,,,,,,,,,,,,,,,,,,,,
+JSON-LD,Moz,,,Alexis Sanders,,,,,,JSON-LD for Beginners,"JSON-LD stands for JavaScript Object Notation for Linked Data, which consists of multi-dimensional arrays (think: list of attribute-value pairs). <br><br>It is an implementation format for structuring data analogous to Microdata and RDFa. Typically, in terms of SEO, JSON-LD is implemented leveraging the Schema.org vocabulary","Structured data is a must-have for many sites, but it can be hard to get a handle on the technical considerations. Learn the important basics of JSON-LD and how to ramp up your education as you apply it.",https://moz.com/blog/json-ld-for-beginners,,Post,,,Main,,,,,,,,2017-02-09,,,,,,,,,,,,,
+JSON-LD,json-ld.org,,,,,,,,,Why JSON-LD,"JSON-LD is able to accomplish the same thing, but does not require HTML. It can exist in and of itself. In short, JSON-LD can be inserted into your web page without disrupting the current content or HTML.",,https://jsonld.com/why-json-ld/,,Post,,,Main,,,,,,,,2015-09-26,,,,,,,,,,,,,
+JSON-LD,Transmute,,,Orie Steele,,,,,,On JSON-LD and the semantics of Identity,"In this post, we’ll explore how JSON-LD is used in a number of contexts including decentralized identity and verifiable credentials. We’ll also cover the basics of what you should know before using JSON-LD and how you can contribute to software and standards that rely on it.",,https://medium.com/transmute-techtalk/on-json-ld-and-the-semantics-of-identity-42d051d3ce14,,Post,,,Main,,,,,,,,2020-01-06,,,,,,,,,,,,,
+JSON-LD,DataLanguage,,https://news.ycombinator.com/item?id=17021939,,,,,,,Publishing JSON-LD for Developers,"A case for publishing JSON-LD regardless whether you are working with linked data or RDF, with some simple examples<br><br>JSON-LD has been among us for several years now, its adoption is increasing, but I suspect not as fast as it probably should. JSON-LD arose out of the RDF community, subsequently adopted as a W3C standard, as a pattern for representing RDF and linked data (hence 'LD') as JSON, with a key aim of making RDF much easier to consume for developers.",,https://datalanguage.com/news/publishing-json-ld-for-developers,https://images.datalanguage.com/EHpzmIaNh/mb-jsonld-800.png?w=1200&h=630,Post,,,Main,,,,,,,,2018-04-27,,,,,,,,,,,,,
+JSON-LD,sitechecker,,,,,,,,,What Is JSON-LD Markup and Why Is It Better than Schema.org?,"If you understand how to use schema.org, but do not dare to mark pages up because of the complexity of the process, this article is for you. There is an effective and easy-to-use alternative - the JSON-LD format.",,https://sitechecker.pro/json-ld-markup/,,Post,,,Main,,,,,,,,,,,,,,,,,,,,,
+JSON-LD,Libre Lounge,,,,,,,,,ActivityPub Part 2,"In our ongoing series about ActivityPub, Chris and Serge explore the world of JSON-LD and the ActivityStreams vocabulary.",,https://librelounge.org/episodes/episode-17-activitypub-part-2.html,,episode,,,Main,,,,,,,,2019-04-19,,,,,,,,,,,,,
+JSON-LD,DIF,,,Orie Steel,,,,,,"Mental Models of JSON-LD and what a ""Document Loader"" really does","and terms like ""dereferencing"" that trip up even highly experienced senior developers that show up late to the Linked-Data party and its open-world model (complete with its own security model based on different availability assumptions).","Former Chair Orie Steele (Transmute Industries) was invited to give an ""explain it to me like I'm five"" session about the Document Loader his company donated...",https://www.youtube.com/watch?v=-yUbMDft5O0,,Video,,,Main,,,,,,,,2020-11-09,,,,,,,,,,,,,
+JSON-LD,Manu Sporny,,https://news.ycombinator.com/item?id=14474222,Manu Sporny,,,,,,JSON-LD and Why I Hate the Semantic Web,"JSON-LD is a product of consensus. Nobody agrees on everything in there, but it all sticks together pretty well. There being a consensus on consensus is what makes the W3C, IETF, and thus the Web and the Internet work. Through all of the fits and starts, permathreads, pedantry, idealism, and deadlock, the way it brings people together to build this thing we call the Web is beautiful thing.",,https://web.archive.org/web/20190219191153/https://manu.sporny.org/2014/json-ld-origins-2/,,Post,,,Main,,,,,,,,2014-01-21,,,,,,,,,,,,,
+JSON-LD,Personal,,https://json-ld.org/learn.html,Manu Sporny,,,,,,What is Linked Data?,Short video introduction to Linked Data,,http://www.youtube.com/watch?v=4x_xzT5eF5Q,https://i.ytimg.com/vi/4x_xzT5eF5Q/hqdefault.jpg?sqp=-oaymwEmCOADEOgC8quKqQMa8AEB-AH-BIAC6AKKAgwIABABGGUgZShlMA8=&rs=AOn4CLCvueCMZtGroF8Av7FB6w4qX4gSmA,Video,,,Explainer,,,,,,,,2012-06-17,,,,,,,,,,,,,
+JSON-LD,Personal,,https://json-ld.org/learn.html,Manu Sporny,,,,,,What is JSON-LD?,Short video introduction to JSON-LD,,http://www.youtube.com/watch?v=vioCbTo3C-4,https://i.ytimg.com/vi/vioCbTo3C-4/hqdefault.jpg?sqp=-oaymwEmCOADEOgC8quKqQMa8AEB-AH-BIAC6AKKAgwIABABGGUgZShlMA8=&rs=AOn4CLDVYrCk-mGtd6c_FqzZCIb9tyNIIw,Video,,,Explainer,,,,,,,,2012-06-19,,,,,,,,,,,,,
+JSON-LD,Personal,,https://json-ld.org/learn.html,Manu Sporny,,,,,,JSON-LD: Core Markup,"An overview of some of the core markup features of JSON-LD including types, aliasing, nesting, and internationalization support",,https://www.youtube.com/watch?v=UmvWk_TQ30A,https://i.ytimg.com/vi/UmvWk_TQ30A/maxresdefault.jpg,Video,,,Explainer,,,,,,,,2015-02-18,,,,,,,,,,,,,
+JSON-LD,Personal,,https://json-ld.org/learn.html,Manu Sporny,,,,,,JSON-LD: Compaction and Expansion,An overview of JSON-LD's compaction and expansion features and how you can use them to merge data from multiple sources,,https://www.youtube.com/watch?v=Tm3fD89dqRE,https://i.ytimg.com/vi/Tm3fD89dqRE/maxresdefault.jpg,Video,,,Explainer,,,,,,,,2015-02-18,,,,,,,,,,,,,
+JSON-LD,Personal,,https://json-ld.org/learn.html,Manu Sporny,,,,,,Linked Data Signatures,An overview of how digital signatures can be added to Linked Data to provide verifiable statements on the Web,,https://www.youtube.com/watch?v=QdUZaYeQblY,https://i.ytimg.com/vi/QdUZaYeQblY/maxresdefault.jpg,Video,,,Explainer,,,,,,,,2015-02-17,,,,,,,,,,,,,
+JSON-LD,Personal,,https://json-ld.org/learn.html,Manu Sporny,,,,,,Credentials on the Web,A quick introduction to verifiable credentials on the Web,,https://www.youtube.com/watch?v=eWtOg3vSzxI,,Video,,,Explainer,,,,,,,,2015-02-17,,,,,,,,,,,,,
+JSON-LD,Personal,,https://json-ld.org/learn.html,Markus Lanthaler,,,,,World Wide Web Conference,Creating 3rd Generation Web APIs with JSON-LD and Hydra,"Proceedings of the Proceedings of the 22nd International World Wide Web Conference (WWW2013), pp. 35-37. Rio de Janeiro, Brazil: ACM Press",,http://m.lanthi.com/www2013-paper,,Paper,,,Explainer,,,,,,,,2013-04-01,,,,,,,,,,,,,
+JSON-LD,Personal,,https://json-ld.org/learn.html,"Markus Lanthaler, Christian Gütl",,,,,World Wide Web Conference,"Model Your Application Domain, Not Your JSON Structures","Proceedings of the 4th International Workshop on RESTful Design (WS-REST 2013) at WWW2013, pp. 1415-1420. Rio de Janeiro, Brazil: ACM Press",,http://m.lanthi.com/wsrest2013-paper,,Paper,,,Explainer,,,,,,,,2013-04-03,,,,,,,,,,,,,
+JSON-LD,Personal,,https://json-ld.org/learn.html,"Markus Lanthaler, Christian Gütl",,Rio de Janeiro,,,World Wide Web Conference,Hydra: A Vocabulary for Hypermedia-Driven Web APIs,Proceedings of the 6th Workshop on Linked Data on the Web (LDOW2013) at WWW2012,,http://m.lanthi.com/ldow2013-paper,,Paper,,,Explainer,,,,,,,,2013-04-11,,,,,,,,,,,,,
+JSON-LD,Personal,,https://json-ld.org/learn.html,"Markus Lanthaler, Christian Gütl",,,,,World Wide Web Conference,On Using JSON-LD to Create Evolvable RESTful Services,"Proceedings of the 3rd International Workshop on RESTful Design (WS-REST 2012) at WWW2012, pp. 25-32. Lyon, France: ACM Press",,http://www.markus-lanthaler.com/research/on-using-json-ld-to-create-evolvable-restful-services.pdf,,Paper,,,Explainer,,,,,,,,2012-04-26,,,,,,,,,,,,,
+JSON-LD,Personal,,https://json-ld.org/learn.html,Gregg Kellogg,,"San Francisco, CA, USA",,,Social Standards Workshop 2013,JSON-LD: JSON for the Social Web,"JSON-LD JSON for the Social Web Gregg Kellogg gregg@greggkellogg.net @gkellogg Wednesday, August 7, 13 Introducing JSON-LD JSON-based syntax to express linked...",Short presentation on JSON-LD for the W3C Social Standards Workshop held in San Francisco in August 2013.,http://www.slideshare.net/gkellogg1/jsonld-json-for-the-social-web,,Presentation,,,Presentation,,,,,,,,2013-08-01,,,,,,,,,,,,,
+JSON-LD,Personal,,https://json-ld.org/learn.html,Markus Lanthaler,,"OR, USA",,,Symfony Live Portland 2013,Building Next-Generation Web APIs with JSON-LD and Hydra,Building Next-Gen Web APIs with JSON-LD and Hydra Markus Lanthaler Why do we need a website? Of course we have a website Why do we need an API? 1995 2000 2005...,"Presented at the Symfony Live Portland 2013 in Portland (Oregon), USA<br>The recording of the talk is available at http://bit.ly/sl-portland2013-video",http://slidesha.re/sl-portland2013,,Presentation,,,Presentation,,,,,,,,2013-05-29,,,,,,,,,,,,,
+JSON-LD,Personal,,https://json-ld.org/learn.html,Markus Lanthaler,,"Rio de Janeiro, Brazil",,,World Wide Web Conference,"Model Your Application Domain, Not Your JSON Structures","Model Your Application Domain, NotYour JSON Structures Markus Lanthaler Graz University ofTechnology RPC REST APIs must be hypertext-driven Got a head...",,http://slidesha.re/wsrest2013-preso,,Presentation,,,Presentation,,,,,,,,2013-05-14,,,,,,,,,,,,,
+JSON-LD,Personal,,https://json-ld.org/learn.html,Markus Lanthaler,,"Rio de Janeiro, Brazil",,,World Wide Web Conference,Hydra: A Vocabulary for Hypermedia-Driven Web APIs,Hydra AVocabulary for HypermediaAPIs Markus Lanthaler Graz University ofTechnology Why can’t Web APIs be browsed? - Layered system REST + Linked Data: a mat...,,http://slidesha.re/ldow2013-preso,,Presentation,,,Presentation,,,,,,,,2013-05-14,,,,,,,,,,,,,
+JSON-LD,Personal,,https://json-ld.org/learn.html,Gregg Kellogg,,"San Francisco, CA, USA",,,Semantic Technology & Business Conference,JSON-LD: JSON for Linked Data,JSON-LD JSON for Linked Data      Gregg Kellogg gregg@greggkellogg.net       @gkellogg JSON-LD JSON for Linked Data               nk ing          Li    Gregg ...,,http://www.slideshare.net/gkellogg1/json-for-linked-data,,Presentation,,,Presentation,,,,,,,,2012-05-30,,,,,,,,,,,,,
+JSON-LD,Personal,,https://json-ld.org/learn.html,Markus Lanthaler,,"Lyon, France",,,,JSON-LD for RESTful Services,JSON-LD for RESTful Services Markus Lanthaler Graz University of Technology Web APIs are becoming a must-have - Layered system Semaphobia!? Linked Data G...,,http://slidesha.re/jsonld4rest,,Presentation,,,Presentation,,,,,,,,2012-04-17,,,,,,,,,,,,,
+JSON-LD,Personal,,https://json-ld.org/learn.html,Gregg Kellogg,,"CA, USA",,,NoSQL Now!,JSON-LD and MongoDB,JSON-LD and   MongoDB Powering Linked Web Apps        Gregg Kellogg   gregg@greggkellogg.net         @gkellogg  JSON-LD and Mongo  • JSON-LD – graph expressio...,,http://www.slideshare.net/gkellogg1/jsonld-and-mongodb,,Presentation,,,Presentation,,,,,,,,2012-08-19,,,,,,,,,,,,,
+JSON-LD,JSON-LD WG,,,,W3C,,,,,JSON-LD Working Group,"The Working Group maintains the JSON-LD specifications (i.e., JSON-LD 1.1, JSON-LD 1.1 API, JSON-LD 1.1 Framing) that together provide a JSON format for Linked Open Data to interoperate at web-scale, in a method which is familiar to and usable by web-focused software engineers.",The mission of the JSON-LD Working Group is to maintain the JSON-LD 1.1 specifications.,https://www.w3.org/2018/json-ld-wg/,,Working Group,,,Working Group,,,,,,,JSON-LD WG,2018-07-15,https://github.com/w3c/json-ld-wg,,,,,,,,,,,,
+JSON-LD,JSON-LD WG,,,,W3C,,,,,JSON-LD 1.1 Framing Specification,"JSON-LD Framing allows developers to query by example and force a specific tree layout to a JSON-LD document.<br><br>This specification describes a superset of the features defined in JSON-LD Framing 1.0 [JSON-LD10-FRAMING] and, except where noted, the algorithms described in this specification are fully compatible with documents created using the previous community standard.",,https://w3c.github.io/json-ld-framing/,,Specification,,,Working Group,,,,,,,JSON-LD WG,2023-04-12,https://github.com/w3c/json-ld-framing,,,,,,,,,,,,
+JSON-LD,JSON-LD WG,,,,W3C,,,,,JSON-LD 1.1 Processing Algorithms and API Specification,"This specification defines a set of algorithms for programmatic transformations of JSON-LD documents. Restructuring data according to the defined transformations often dramatically simplifies its usage. Furthermore, this document proposes an Application Programming Interface (API) for developers implementing the specified algorithms.",,https://w3c.github.io/json-ld-api/,,Specification,,,Working Group,,,,,,,JSON-LD WG,2023-04-12,https://github.com/w3c/json-ld-api,,,,,,,,,,,,
+JSON-LD,JSON-LD WG,,,,W3C,,,,,JSON-LD 1.1 Syntax,"JSON is a useful data serialization and messaging format. This specification defines JSON-LD 1.1, a JSON-based format to serialize Linked Data. The syntax is designed to easily integrate into deployed systems that already use JSON, and provides a smooth upgrade path from JSON to JSON-LD. It is primarily intended to be a way to use Linked Data in Web-based programming environments, to build interoperable Web services, and to store Linked Data in JSON-based storage engines.",,https://github.com/w3c/json-ld-syntax,,Specification,,,Working Group,,,,,,,JSON-LD WG,2023-04-12,,,,,,,,,,,,,
+JSON-LD,JSON-LD WG,,,,W3C,,,,,JSON-LD Best Practices,"Developers share a common problem: they want a simple, but extensible way to create an API for a web service that gets the job done, doesn't design them into a corner, and allows developers to easily interact with their service without reinventing the wheel. JSON-LD [JSON-LD] has become an important solution, as it bridges the gap between formally data and more colloquial JSON interfaces used in APIs from numerous providers. This guide attempts to define certain best practices for publishing data using JSON-LD, and interacting with such services.",,https://w3c.github.io/json-ld-bp/,,note,,,Working Group,,,,,,,JSON-LD WG,2023-04-12,,,,,,,,,,,,,
+JSON-LD,JSON-LD WG,,,,W3C,,,,,JSON-LD Recommended Context,"This is the repository for a recommended context for JSON-LD 1.1, as well as the RDFa Core Initial Context, developed and maintained by the W3C JSON-LD Working Group. Most of the major resources in this repository are redirected from W3C URI-s that have been in use by the community for a while. These are as follows:",,https://w3c.github.io/json-ld-rc/context.jsonld,,note,,,Working Group,,,,,,,JSON-LD WG,2020-05-07,https://github.com/w3c/json-ld-rc,,,,,,,,,,,,
+JSON-LD,JSON-LD WG,,,,,,,,,JSON-LD 1.1 Framing Specification,"This specification describes a superset of the features defined in [JSON-LD10-FRAMING] and, except where noted, the algorithms described in this specification are fully compatible with documents created using the previous community standard.",,https://w3c.github.io/json-ld-framing/,,Specification,,,Working Group,,,,,,,,2023-04-12,https://github.com/w3c/json-ld-framing,,,,,,,,,,,,
+JSON-LD,JSON-LD WG,,,,,,,,,JSON-LD 1.1 Processing Algorithms and API Specification,"This specification defines a set of algorithms for programmatic transformations of JSON-LD documents. Restructuring data according to the defined transformations often dramatically simplifies its usage. Furthermore, this document proposes an Application Programming Interface (API) for developers implementing the specified algorithms.",,https://w3c.github.io/json-ld-api/,,Specification,,,Working Group,,,,,,,,2023-04-12,https://github.com/w3c/json-ld-api,,,,,,,,,,,,
+JSON-LD,JSON-LD WG,,,,,,,,,JSON-LD 1.1 Specification,"This specification describes a superset of the features defined in JSON-LD 1.0 [JSON-LD10] and, except where noted, documents created using the 1.0 version of this specification remain compatible with JSON-LD 1.1",,https://w3c.github.io/json-ld-syntax/,,Specification,,,Working Group,,,,,,,,2023-04-12,https://github.com/w3c/json-ld-syntax,,,,,,,,,,,,
+JSON-LD,JSON-LD WG,,,,,,,,,JSON-LD 1.1 Best Practices Note,"Developers share a common problem: they want a simple, but extensible way to create an API for a web service that gets the job done, doesn't design them into a corner, and allows developers to easily interact with their service without reinventing the wheel. JSON-LD [JSON-LD] has become an important solution, as it bridges the gap between formally data and more colloquial JSON interfaces used in APIs from numerous providers. This guide attempts to define certain best practices for publishing data using JSON-LD, and interacting with such services.",,https://w3c.github.io/json-ld-bp/,,note,,,Working Group,,,,,,,,2023-04-12,,,https://github.com/w3c/json-ld-bp,,,,,,,,,,
+JSON-LD,JSON-LD WG,,,,,,,,,JSON-LD Recommended Context,,,https://w3c.github.io/json-ld-rc/context.jsonld,,Code,,,Working Group,,,,,,,,2023-04-12,https://github.com/w3c/json-ld-rc,,,,,,,,,,,,
+JSON-LD,JSON-LD WG,,,,,,,,,Teleconference minutes - text and audio logs,JSON-LD Teleconference Minutes,,https://github.com/json-ld/minutes,,page,,,Working Group,,,,,,,,2023-05-17,,,,,,,,,,,,,
+JSON-LD,JSON-LD WG,,,,,,,,,Charter for JSON-LD WG,"Since its original publication in 2014 by the RDF 1.1 Working Group, JSON-LD 1.0 has become an essential format for describing structured data on the World Wide Web. It is estimated to be used by between 10% and 18.2% of all websites. This is due largely to its adoption as a recommended format by schema.org. It has been adopted by several Recommendations including those from the Social Web, Web Annotation, and Linked Data Platform Working Groups, and current Working Groups have expressed interest in alignment of their specifications, such as the Publishing and Web of Things Working Groups. It has provided a much-needed bridge between communities that need rich semantics, and those that desire an intuitive and easily usable format (see separate wiki page for more details).",,https://www.w3.org/2018/03/jsonld-wg-charter.html,,page,,,Working Group,,,,,,,,2018-06-07,,,,,,,,,,,,,
+JSON-LD,Personal,,,Daniel Stainback,,,,,,piprate/json-gold,This library is an implementation of the JSON-LD 1.1 specification in Go. It supports both URDNA2015 and URGNA2012 RDF dataset normalisation algorithms.,- JSON-goLD Documentations Travis CI results GoCover.io,https://github.com/piprate/json-gold,,Code,,,Development,,,,,,,,2021-01-11,,,,,,,,,,,,,
+JSON-LD,Personal,,,Jay Holtslander,,,,,,Structured Data / JSON-LD,Collection of structured data snippets in Google preferred JSON-LD format. [codepen.io/collection/DNvPJE/](https://codepen.io/collection/DNvPJE/),Collection of structured data snippets in Google preferred JSON-LD format. - GitHub - JayHoltslander/Structured-Data-JSON-LD: Collection of structured data snippets in Google preferred JSON-LD format.,https://github.com/JayHoltslander/Structured-Data-JSON-LD,,Code,,,Development,,,,,,,,2022-08-16,,,,,,,,,,,,,
+JSON-LD,CodeMeta,,,,,,,,,codemeta/codemeta,"CodeMeta contributors are creating a minimal metadata schema for science software and code, in JSON and XML. The goal of CodeMeta is to create a concept vocabulary that can be used to standardize the exchange of software metadata across repositories and organizations. CodeMeta started by comparing the software metadata used across multiple repositories, which resulted in the CodeMeta Metadata Crosswalk. That crosswalk was then used to generate a set of software metadata concepts, which were arranged into a JSON-LD context for serialization.","Minimal metadata schemas for science software and code, in JSON-LD - GitHub - codemeta/codemeta: Minimal metadata schemas for science software and code, in JSON-LD",https://github.com/codemeta/codemeta,,Code,,,Development,,,,,,,,2023-04-26,,,,,,,,,,,,,
+JSON-LD,Codeship,,https://json-ld.org/learn.html,Benjamin Young,,,,,,JSON-LD: Building Meaningful Data APIs,"Meet JSON-LD! JSON-LD stands for JSON for Linked Data."" It's a specification for encoding contextualized meaning into otherwise meaningless JSON documents. """,,http://blog.codeship.com/json-ld-building-meaningful-data-apis/,,Post,,,Development,,,,,,,,2016-05-17,,,,,,,,,,,,,
+JSON-LD,Personal,,,Daniel Stainback,,,,,,Extremely simple JSON-LD Generator,,,https://github.com/Torann/json-ld,,Code,,,Development,,,,,,,,2021-02-22,,,,,,,,,,,,,
+JSON-LD,Digital Bazaar,,,,,,,,,JSON-LD command line interface tool,"This module provides a command line tool jsonld to manipulate JSON-LD data. It is written in JavaScript for Node.js and uses the jsonld.js and jsonld-request libraries. Inputs can be from stdin, URLs, or files.",,https://github.com/digitalbazaar/jsonld-cli,,Code,,,Development,,,,,,,,2022-08-01,,,,,,,,,,,,,
+JSON-LD,Digital Bazaar,,,,,,,,,JSON-LD processor written in Python,This library is an implementation of the JSON-LD specification in Python,,https://github.com/digitalbazaar/pyld,,Code,,,Development,,,,,,,,2020-08-07,,,,,,,,,,,,,
+JSON-LD,Digital Bazaar,,,,,,,,,A JSON-LD Processor and API implementation in JavaScript,This library is an implementation of the JSON-LD specification in JavaScript.,,https://github.com/digitalbazaar/jsonld.js,,Code,,,Development,,,,,,,,2023-05-20,,,,,,,,,,,,,
+JSON-LD,Digital Bazaar,,,,,,,,,PHP implementation of a JSON-LD Processor and API,This library is an implementation of the JSON-LD specification in PHP,,https://github.com/digitalbazaar/php-json-ld,,Code,,,Development,,,,,,,,2019-05-17,,,,,,,,,,,,,
+JSON-LD,Digital Bazaar,,,,,,,,,An implementation of the Linked Data Signatures specification for JSON-LD. Works in the browser and Node.js,"An implementation of the Linked Data Signatures specification for JSON-LD, for Node.js and browsers.",,https://github.com/digitalbazaar/jsonld-signatures,,Code,,,Development,,,,,,,,2023-05-15,,,,,,,,,,,,,
+JSON-LD,Digital Bazaar,,,,,,,,,"LIbrary to load JSON-LD from stdin, URLs, or files","This JavaScript Node.js library is used to read data from stdin, URLs, or files and convert to JSON-LD via jsonld.js. It can process JSON-LD in JSON and RDFa in HTML and output JSON-LD.",,https://github.com/digitalbazaar/jsonld-request,,Code,,,Development,,,,,,,,2022-08-01,,,,,,,,,,,,,
+JSON-LD,Digital Bazaar,,,,,,,,,JSON patch for JSON-LD,This library provides an API for applying JSON patches to JSON-LD documents. JSON patches may be represented in JSON-LD by using hte will be interpreted as JSON-LD using the JSON-LD Patch @context.,,https://github.com/digitalbazaar/jsonld-patch,,Code,,,Development,,,,,,,,2021-02-26,,,,,,,,,,,,,
+JSON-LD,Digital Bazaar,,,,,,,,,Cryptographic Key Pair Library for Linked Data (crypto-ld),A Javascript library for generating and performing common operations on Linked Data cryptographic key pairs.,,https://github.com/digitalbazaar/crypto-ld,,Code,,,Development,,,,,,,,2022-06-02,,,,,,,,,,,,,
+WebAuthN,Microsoft,,,Pamela Dingle,,,,,,Why WebAuthn will change the world,"A little over a month ago, W3C WebAuthn became a real internet specification.  Most of you don’t know what WebAuthn is yet, but many of you will feel the impact in short order.  In fact, I will go so far as to say that WebAuthn may change how we all authenticate to the resources we use every day. <br><br>We live in a world where the best parts of our individual local hardware and software collection are rarely leveraged to make cloud security decisions.  This is because there has never been a vendor-agnostic and privacy-preserving way for cloud resources to interact with individual hardware configurations in any generic way.  Until now! <br><br>With WebAuthn, any web entity can call a simple Javascript API and ask for a cryptographically secure credential.   What happens next is pretty cool – the world’s browsers have worked with the world’s operating system makers and the world’s hardware manufacturers, so that when a website asks for a credential, the browsers work with the underlying platform to securely locate compliant local hardware and talk to it!",,https://techcommunity.microsoft.com/t5/identity-standards-blog/why-webauthn-will-change-the-world/ba-p/482286,,Post,,,Main,,,,,,,,2019-04-19,,,,,,,,,,,,,
+WebAuthN,ZDNet,,,,,,,,,W3C finalizes Web Authentication (WebAuthn) standard - ZDNet,"WebAuthn allows users to register and authenticate on websites or mobile apps using an ""authenticator"" instead of a password.<br><br>The ""authenticator"" can be a hardware security key that the user has connected to his computer or a biometric ID that can be acquired from the PC or smartphone's sensors --such as fingerprints, face scans, iris scans, and others.",,https://www.zdnet.com/article/w3c-finalizes-web-authentication-webauthn-standard/,,Post,,,Main,,,,,,,,2019-03-04,,,,,,,,,,,,,
+WebAuthN,Microsoft,,,,,,,,,"All about FIDO2, CTAP2 and WebAuthn","This is a great week to be working in Identity Standards, as we at Microsoft celebrate the release of our first ever WebAuthn Relying Party. This one relying party enables standards-based passwordless authentication at Xbox, Skype, Outlook.com and more. But what are the actual pieces of the puzzle and how do they fit? Read on for the big picture of how the W3C WebAuthn and FIDO2 CTAP2 specifications interact. We will start with the industry standards perspective, and then at the end we will summarize how Microsoft implements the various roles. <br><br>To understand how FIDO2 authenticators work, you need knowledge of two specifications in two different standards bodies. The WebAuthentication (aka WebAuthn) spec lives at W3C (where the browser makers meet) while the Client-to-Authenticator (aka CTAP2) spec lives at the FIDO Alliance (where hardware and platform folks have joined to solve the problem of Fast IDentity Online).",,https://techcommunity.microsoft.com/t5/Identity-Standards-Blog/All-about-FIDO2-CTAP2-and-WebAuthn/ba-p/288910,https://techcommunity.microsoft.com/t5/image/serverpage/image-id/60283iDDAE6B0B53A24427/image-size/original?v=v2&px=-1,Post,,,Main,,,,,,,,2018-11-20,,,,,,,,,,,,,
+WebAuthN,Microsoft,,,,,,,,,"To Understand WebAuthn, Read CredMan","The holidays are well and truly over, time to get serious - now is the perfect time to read specifications! If you are planning to read the WebAuthn specification, you can ease into the terminology in a simple way - take a cruise through the W3C Credential Management (aka CredMan) specification first.  CredMan sets up the object model for the Credential object model that WebAuthn's PublicKeyCredential extends.  This post will be an overview of the CredMan spec, geared for folks who want to call the API as clients, not for those few and proud who are tasked with implementation of the API within a user agent.",,https://techcommunity.microsoft.com/t5/identity-standards-blog/to-understand-webauthn-read-credman/ba-p/339652,https://techcommunity.microsoft.com/t5/image/serverpage/image-id/78172i3FDF4848680EABE1/image-size/original?v=v2&px=-1,Post,,,Main,,,,,,,,2019-02-15,,,,,,,,,,,,,
+WebAuthN,GitHub,,,Lucas Garron,,,,,,GitHub supports Web Authentication (WebAuthn) for security keys,"GitHub now supports Web Authentication (WebAuthn) for security keys—the new standard for secure authentication on the web. Starting today, you can use security keys for two-factor authentication on GitHub with even more browsers and devices. And, since many browsers are actively working on WebAuthn features, we’re excited about the potential for strong and easy-to-use authentication options for the entire GitHub community in the future.",The WebAuthn standard for security keys is making authentication as easy as possible. Now you can use security keys for second-factor authentication on GitHub with many more browsers and devices.,https://github.blog/2019-08-21-github-supports-webauthn-for-security-keys/,https://github.blog/wp-content/uploads/2019/08/Screen-Shot-2019-08-21-at-11.34.02-copy.png?fit=2400%2C1260,Post,,,Main,,,,,,,,2019-08-21,,,,,,,,,,,,,
+WebAuthN,Fido Alliance,,,,,,,,,WebAuthn Workshop,,,https://slides.com/fidoalliance/webauthn-overview,https://media.slid.es/thumbnails/0d31fdc30b303d4443a65dd550767eee/thumb.jpg?1538300008,Presentation,,,Main,,,,,,,,2018-06-07,,,,,,,,,,,,,
+WebAuthN,Personal,,,Ackermann Yuri,,,,,,WebAuthn Awesome Awesome,A curated list of awesome WebAuthn/FIDO2 resources,,https://github.com/herrjemand/awesome-webauthn,,list,,,Main,,,,,,,,2023-04-06,,,,,,,,,,,,,
+WebAuthN,WebAuthN Guide,,,,,,,,,Guide to Web Authentication,"Passwords have an ever-growing list of problems associated with them, both for users and developers. Users have to worry about passwords being stolen by phishing tools, or their passwords being leaked online if websites they have accounts with are compromised. They have to worry about creating and remembering passwords without dedicated password management tools. Developers have to worry about all the complications of passing passwords through systems and safely storing them in databases.","An introduction to Web Authentication (WebAuthn), the new API that can replace passwords with strong authentication.",https://webauthn.guide,,page,,,Main,,,,,,,,,,,,,,,,,,,,,
+WebAuthN,Auth0,,,,,,,,,Web Authentication (WebAuthn) Credential and Login Demo,"Web Authentication is a W3C recommendation for defining an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users.<br><br>Web Authentication works hand in hand with other industry standards such as Credential Management Level 1 and FIDO 2.0 Client to Authenticator Protocol 2.<br><br>Auth0 allows you to quickly setup Multi-Factor Authentication with WebAuthn",Try the Web Authentication demo to register a credential and login with biometrics. WebAuthn spec enables public key-based credentials for securely authenticating users using hardware authenticators.,https://webauthn.me,,page,,,Main,,,,,,,,,,,,,,,,,,,,,
+WebAuthN,FIDO Alliance,,,,,,,,,FIDO2: WebAuthn & CTAP,"The FIDO Alliance developed FIDO Authentication standards based on public key cryptography for authentication that is more secure than passwords and SMS OTPs, simpler for consumers to use, and easier for service providers to deploy and manage. FIDO Authentication enables password-only logins to be replaced with secure and fast login experiences across websites and apps.",,https://fidoalliance.org/fido2/,,page,,,FIDO Alliance,,,,,,,,,,,,,,,,,,,,,
+WebAuthN,FIDO Alliance,,,,,,,,,FIDO2: Web Authentication (WebAuthn),"Web Authentication (WebAuthn), a core component of FIDO Alliance’s FIDO2 set of specifications, is a web-based API that allows websites to update their login pages to add FIDO-based authentication on supported browsers and platforms. FIDO2 enables users to leverage common devices to easily authenticate to online services in both mobile and desktop environments.",,https://fidoalliance.org/fido2/fido2-web-authentication-webauthn/,,page,,,FIDO Alliance,,,,,,,,,,,,,,,,,,,,,
+WebAuthN,WebAuthNWG,,https://w3c.github.io/webauthn/,,W3C,,,,,Web Authentication Working Group,"The mission of the Web Authentication Working Group, in the Security Activity is to define a client-side API providing strong authentication functionality to Web Applications.",,https://www.w3.org/Webauthn/,,Working Group,,,Working Group,,,,,,,Web Authentication Working Group,2016-02-08,https://github.com/w3c/webauthn,,,https://www.w3.org/blog/webauthn/,,,,,,,,,
+WebAuthN,WebAuthNWG,,,,W3C,,,,,Web Authentication: An API for accessing Public Key Credentials,"This specification defines an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users. Conceptually, one or more public key credentials, each scoped to a given WebAuthn Relying Party, are created by and bound to authenticators as requested by the web application. The user agent mediates access to authenticators and their public key credentials in order to preserve user privacy. Authenticators are responsible for ensuring that no operation is performed without user consent. Authenticators provide cryptographic proof of their properties to Relying Parties via attestation. This specification also describes the functional model for WebAuthn conformant authenticators, including their signature and attestation functionality.",,https://w3c.github.io/webauthn/,https://w3c.github.io/webauthn/images/webauthn-registration-flow-01.svg,Specification,,,Working Group,,,,,,,Web Authentication Working Group,2023-05-17,https://github.com/w3c/webauthn,,,,,,,,,,,,
+WebAuthN,WebAuthNWG,,,Samuel Weiler,,,,,,Web Authentication Working Group Charter,"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.<br><br>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.",,https://www.w3.org/2019/10/webauthn-wg-charter.html,,Post,,,Working Group,,,,,,,,2019-10-15,,,,,,,,,,,,,
+WebAuthN,Stranger Labs,,,,,,,,,webauthn - npmjs.com,WebAuthn is a W3C standard that enables web developers to replace passwords in their applications with FIDO authentication. This repository implements a NPM package for use in Node.js services. This package is in active development and not yet ready for production use. You can use it to kick the tires on WebAuthn. Please file issues to ask questions or provide feedback.,"W3C Web Authentication API Relying Party for Node.js and Express. Latest version: 0.2.0, last published: 4 years ago. Start using webauthn in your project by running `npm i webauthn`. There are no other projects in the npm registry using webauthn.",https://www.npmjs.com/package/webauthn,,Code,,,Development,,,,,,,,2019-11-25,,,,,,,,,,,,,
+WebAuthN,WebAuthN.io,,,,,,,,,WebAuthn (FIDO2) server library written in Go,"This library is meant to handle Web Authentication for Go apps that wish to implement a passwordless solution for users. While the specification is currently in Candidate Recommendation, this library conforms as much as possible to the guidelines and implementation procedures outlined by the document.",Demonstration of the WebAuthn specification.,https://webauthn.io/,,page,,,Development,,,,,,,,,https://github.com/duo-labs/webauthn,,,,,,,,,,,,
+WebAuthN,Google,,,,,,,,,What is WebAuthn? What is FIDO2?,"The FIDO2 / WebAuthn allows you to create and use strong, attested public key based credentials for the purpose of authenticating users. The API supports the use of BLE, NFC, and USB roaming authenticators (security keys) as well as a platform authenticator, which allows the user to authenticate using their fingerprint or screenlock.",Learn how to build a website with a simple reauthentication functionality that uses a fingerprint sensor.,https://codelabs.developers.google.com/codelabs/webauthn-reauth/#0,https://developers.google.com/static/codelabs/webauthn-reauth/img/260aab9f1a2587a7.png,Post,,,Development,,,,,,,,2022-05-12,,,,,,,,,,,,,
+WebAuthN,Google,,,,,,,,,Enabling Strong Authentication with WebAuthn,The Web Authentication API gives Web applications user-agent-mediated access to authenticators – which are often hardware tokens accessed over USB/BLE/NFC or modules built directly into the platform – for the purposes of generating and challenging application-scoped (eTLD+k) public-key credentials.,"Chrome 67 beta introduces the Web Authentication (WebAuthn) API, which allows browsers to interact with and manage public-key based credentials. This enables strong authentication using removable security keys and built-in platform authenticators such as fingerprint scanners.",https://developers.google.com/web/updates/2018/05/webauthn,,Post,,,Development,,,,,,,,05-2018,,,,,,,,,,,,,
+WebAuthN,Mozilla,,,,,,,,,Web Authentication API,"The Web Authentication API (WebAuthn) is an extension of the Credential Management API that enables strong authentication with public key cryptography, enabling passwordless authentication and secure multi-factor authentication (MFA) without SMS texts.",,https://developer.mozilla.org/en-US/docs/Web/API/Web_Authentication_API,,page,,,Development,,,,,,,,,,,,,,,,,,,,,
+Blockcerts,Learning Machine,,,,,,,,,Digital Identity,A framework for organizing the categories of digital identity and an analysis of where disruptive innovation is most likely to succeed.,,https://www.learningmachine.com/digital-identity/,,page,,,Learning Machine,,,,,,,,2018-10-06,,,,,,,,,,,,,
+Blockcerts,Learning Machine,,,,,,,,,Learning Machine,Get a complete system to issue digital credentials in a blockchain-secured format that is easily shareable and instantly verifiable anywhere in the world.,,https://www.learningmachine.com/,https://www.learningmachine.com/wp-content/uploads/2019/06/mobile-cert-min.png,company,,,Learning Machine,,,,,,,,2016,,,,,,,,,,,,,
+Blockcerts,Personal,,,Natalie Smolenski,,,,,,"Natalie Smolenski - Author, Speaker","Natalie Smolenski is an anthropologist leading business development for blockchain technology firm Learning Machine. She writes and speaks about identity, tech, and government.",,https://www.nataliesmolenski.com/,,blog,,,Learning Machine,,,,,,,,,,,,,,,,,,,,,
+Blockcerts,Learning Machine,,,,,,,,,Academic Credentialing and the Blockchain,"Hello everyone. My name is Chris Jagers. I’m the CEO of Learning Machine, the software company that has been working with MIT over the last year to develop an open standard for blockchain certificates. I’ll be giving a short presentation about blockchain-based academic credentials, followed by a discussion with our panel and with all of you.",,https://www.learningmachine.com/academic-credentialing-blockchain/,,page,,,Learning Machine,,,,,,,,2016-10-28,,,,,,,,,,,,,
+Blockcerts,Hyland Credentials,,,,,,,,,Future Proof,"Learning Machine is proud to announce that we have won Phase-1 funding for our response to the open call “Preventing Forgery & Counterfeiting of Certificates and Licenses through the use of Blockchain and Distributed Ledger Technology.” [...] The open-source reference implementation, targeted for 2020, will include:<br>- Updating the Blockcerts schema to a Verifiable Credentials-based format<br>- Updating the Blockcerts signature/verification scheme to conform to the latest JSON-LD signature suite format<br>- Updating Blockcerts credential issuance and verification<br>- Incorporating a cost-efficient DID method for issuers",,https://www.hylandcredentials.com/future-proof,https://www.learningmachine.com/wp-content/uploads/2019/07/vc.png,page,,,Learning Machine,,,,,,,,2017-07,,,,,,,,,,,,,
+Blockcerts,Blockcerts,Blockcerts,,,,,,,,Blockcerts,"open standard for issuing and verifying blockchain-based official records; The project offers  open-source libraries, tools, and mobile apps. MIT has [issued](https://www.insidehighered.com/news/2017/10/19/mit-introduces-digital-diplomas) digital certificates based on this standard.","Build apps that issue and verify blockchain-based credentials for academic credentials, professional certifications, workforce development, and civic records.",https://www.blockcerts.org/,,project,,,Blockcerts,,,,,,,,2016,https://github.com/blockchain-certificates,https://twitter.com/blockcerts,,,,,,,,,,,http://community.blockcerts.org/
+Blockcerts,Blockcerts,,,,,,,,,Introduction,"Blockcerts is an open standard for building apps that issue and verify blockchain-based official records. These may include certificates for civic records, academic credentials, professional licenses, workforce development, and more.<br><br>Blockcerts consists of open-source libraries, tools, and mobile apps enabling a decentralized, standards-based, recipient-centric ecosystem, enabling trustless verification through blockchain technologies.<br><br>Blockcerts uses and encourages consolidation on open standards. Blockcerts is committed to self-sovereign identity of all participants, and enabling recipient control of their claims through easy-to-use tools such as the certificate wallet (mobile app). Blockcerts is also committed to availability of credentials, without single points of failure.","Build apps that issue and verify blockchain-based credentials for academic credentials, professional certifications, workforce development, and civic records.",https://www.blockcerts.org/guide/,https://www.blockcerts.org/assets/img/pictures/blockcerts.png,page,,,Blockcerts,,,,,,,,,,,,,,,,,,,,,
+Blockcerts,MIT Media Lab,,,,,,,,,Blockcerts — An Open Infrastructure for Academic Credentials on the Blockchain,"What would an academic degree look like if it was designed today? Or a professional certificate? These are questions we have been working on over the last year, and we are excited to announce the…",,https://medium.com/mit-media-lab/blockcerts-an-open-infrastructure-for-academic-credentials-on-the-blockchain-899a6b880b2f,https://miro.medium.com/v2/resize:fit:1200/1*zrTpMx8dQKK_XAJLtLdOGg.png,Post,,,Blockcerts,,,,,,,,2016-10-25,,,,,,,,,,,,,
+Blockcerts,Learning Machine,,,Natalie Smolenski,,,,,,Top 10 Reasons to Use Blockcerts,The open standard for issuing blockchain-based records is your easiest bet for creating records that remain verifiable for a lifetime.,"With more blockchain credentialing solutions popping up every week, it can be difficult to navigate the landscape of offerings. How do you decide which blockchain credentialing framework to use? One…",https://medium.com/learning-machine-blog/top-10-reasons-to-use-blockcerts-ec7d29f2712c,,Post,,,Blockcerts,,,,,,,,2018-05-19,,,,,,,,,,,,,
+Blockcerts,SSIMeetup,,https://www.slideshare.net/SSIMeetup/blockcerts-the-open-standard-for-blockchain-credentials,,,,,,,Blockcerts: The Open Standard for Blockchain Credentials,"<center><iframe src=""//www.slideshare.net/slideshow/embed_code/key/rVC25i8FzeTPiw"" width=""595"" height=""485"" frameborder=""0"" marginwidth=""0"" marginheight=""0"" scrolling=""no"" style=""border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;"" allowfullscreen</iframe</center>","Anthony Ronning, an engineer behind Blockcerts and backend dev at Learning Machine and Daniel Paramo, co-founder of swys and advisor at Xertify, explains how Blockcerts started, deep dive on how Blockcerts work, which institutions are implementing this solution and what companies have made a solution for the adoption of this standard. We will review the current Blockcerts roadmap and their pros and cons. What considerations do we need to take when developing a solution around Blockcerts?",https://ssimeetup.org/blockcerts-open-standard-blockchain-credentials-daniel-paramo-anthony-ronning-webinar-39/,,Presentation,,,Blockcerts,,,,,,,,2019-10-12,,,,,,,,,,,,,
+Blockcerts,WebofTrustInfo,,,,,,,,rwot5-boston,A Decentralized Approach to Blockcerts Credential Revocation,"The initial release of the Blockcerts standard and reference implementation described only one revocation mechanism, the issuer-hosted revocation list approach also used by Open Badges. This has known limitations, including: centralization, single point of failure, and inability for a recipient to revoke. Other approaches to revocation were considered, but none were technically or economically feasible at the time given the project goals, including Bitcoin blockchain anchoring, low overhead, and minimal cost.",,https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/final-documents/blockcerts-revocation.md,,Paper,,,Blockcerts,,,,,,,,2018-02-09,,,,,,,,,,,,,
+Blockcerts,WebofTrustInfo,,https://community.blockcerts.org/t/blockcerts-v3-proposal-verifiable-credentials-decentralized-identifiers/2221,,,,,,rwot9-prague,Blockcerts V3 Proposal - Verifiable Credentials & Decentralized Identifiers,"As the standards around Verifable Credentials are starting to take form, different favors of ""verifiable credentials-like"" data structures need to make necessary changes to leverage on the rulesets outlined and constantly reviewed by knowledgeable communities such as the W3C. The purpose of this paper is to identify all of the changes needed for Blockcerts to comply with the Verifiable Credentials (VCs) and Decentralized Identifers (DIDs) standards and to expand upon the additional benefits of using a blockchain in combination with Verifiable Credentials. This paper is meant to act as an explainer in which a formal specification can be created. This paper proposes multiple implementation options for several properties. The intention is that we can engage the Blockcerts / Verifiable Credential communities and see what fts best.","Some of you may already know and/or have been following along. Over the last few months, since Rebooting the Web of Trust 9, we have been coming up with drafts and proposals for Blockcerts V3 for the al&hellip;",https://nbviewer.jupyter.org/github/WebOfTrustInfo/rwot9-prague/blob/master/final-documents/BlockcertsV3.pdf,,Paper,,,Blockcerts,,,,,,,,2019-12-19,https://github.com/blockchain-certificates/cert-issuer/tree/v3,,,,,,,,,,,,https://community.blockcerts.org/t/blockcerts-v3-proposal-verifiable-credentials-decentralized-identifiers/2221
+Blockcerts,Learning Machine,,,,,,,,,Badges and Blockcerts,"In education and workforce development, it’s important to understand the differences between digital credential formats and how to combine them for greatest impact [...]<br><br>2011 saw the birth of Open Badges, which digitally and visually convey the achievement of a specific skill. Similar to the Scouts movement, which uses a small fabric symbol to represent specific achievements, digital badges were designed to convey a singular achievement through a digital image and a hosted set of data. Initially spearheaded by the Mozilla Foundation, the Open Badges standard is now maintained by the IMS Global Learning Consortium, ensuring interoperability between platforms. [...]<br><br>In response to the desire for high-stakes credentials in a digital format, the development of Blockcerts began in 2015 as part of a project by the MIT Media Lab.",,https://www.learningmachine.com/badges-and-blockcerts/,https://www.learningmachine.com/wp-content/uploads/2019/01/Screen-Shot-2019-01-29-at-9.54.40-AM.png,page,,,Open Badges,,,,,,,,2018-12-13,,,,,,,,,,,,,
+Blockcerts,WebofTrustInfo,,,,Open Badges,,,,rwot6-santabarbera,Open Badges are Verifable Credentials,The Blockcerts Open Badges Draft Extension introduced a verifcation method based on those used by Verifable Credentials for the specifc use case of blockchain-anchored credentials. This paper expands that work and proposes a new option that can reside alongside existing Open Badges verifcation methods.,,https://nbviewer.jupyter.org/github/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/open-badges-are-verifiable-credentials.pdf,,Paper,,,Open Badges,,,,,,,,2018-06-22,,,,,,,,,,,,,
+Blockcerts,Draftin,,,,Open Badges,,,,,OPEN BADGES ON THE BLOCKCHAIN,"This document gives an overview of the status, interesting companies and people regarding Verifiable Open Badges on the Blockchain.",,https://draftin.com/documents/1138961?token=hQ5q0mCHizZum8-pkDFYUZr4YFYOWMN01BPT-5uX00hAaGxYOAlgAlhyenat76hjNpTCs-CMWPI38KWn_omp0Oc,,Paper,,,Open Badges,,,,,,,,2019-07-19,,,,,,,,,,,,,
+Blockcerts,FSMB,,,,,,,,,"Healthcare and Digital Credentials: Technical, Legal, and Regulatory Considerations","Credentials expressed through a trusted identity framework can be accorded a higher value within a social interaction due to the underlying assumption that someone within the system is managing the creation and transfer of these credentials. Within any high functioning identity framework specifications, rules, and agreements based in both technological capacity and social need are necessary to ensure that the level of trustworthiness required by participants in the identity system and the community relying on the services offered by the identity system is met.",,https://www.fsmb.org/siteassets/digital-credentials/digital-credentials-report-june-2019.pdf,,Report,,,Literature,,,,,,,,2019-06,,,,,,,,,,,,,
+Blockcerts,arxiv,,,"Marco Baldi, Franco Chiaraluce, Migelan Kodra and Luca Spalazzi",Open Badges,,,,,Security analysis of a blockchain-based protocol forthe certification of academic credentials,"Abstract—We consider a blockchain-based protocol forthe certification of academic credentials named Blockcerts,which is currently used worldwide for validating digitalcertificates of competence compliant with the Open Badgesstandard. We study the certification steps that are per-formed by the Blockcerts protocol to validate a certificate,and find that they are vulnerable to a certain typeof impersonation attacks. More in detail, authenticationof the issuing institution is performed by retrieving anunauthenticated issuer profile online, and comparing somedata reported there with those included in the issuedcertificate. We show that, by fabricating a fake issuerprofile and generating a suitably altered certificate, anattacker is able to impersonate a legitimate issuer andcan produce certificates that cannot be distinguished fromoriginals by the Blockcerts validation procedure. We alsopropose some possible countermeasures against an attackof this type, which require the use of a classic public keyinfrastructure or a decentralized identity system integratedwith the Blockcerts protocol.",,https://arxiv.org/pdf/1910.04622.pdf,,Paper,,,Literature,,,,,,,,2019-10-11,,,,,,,,,,,,,
+Blockcerts,Bitcoin.com,,,Jamie Redman,,,,,,MIT Launches Blockcerts Certification Using Bitcoin,"The MIT Media Lab project has already deployed a few instances of blockchain-based digital certificate verification. In October of 2015, the group issued certificates to Media Lab alumni who attended the Lab’s 30th anniversary. The organization Learning Machine also issued HR certificates to employees. MIT’s Global Entrepreneurship Bootcamp workshop in Seoul, South Korea in March 2016 published digital verification using the system. Lastly, Laboratorio para la Ciudad issued digital certificates to workshop participants in Mexico City in September 2015.","Back in June MIT Media Lab tested certification authentication using the Bitcoin blockchain. After working on research and development for over a year, the",https://news.bitcoin.com/mit-blockcerts-certification-bitcoin/,https://static.news.bitcoin.com/wp-content/uploads/2016/10/MIT-Launches-Blockcerts-Certification-Using-Bitcoin.jpg,Post,,,Adoption,,,,,,,,2016-10-28,,,,,,,,,,,,,
+Blockcerts,InsideHighered,,,Lindsay McKenzie,,,,,,MIT Introduces Digital Diplomas,"The Massachusetts Institute of Technology is offering some students the option to be awarded tamper-free digital degree certificates when they graduate, in partnership with Learning Machine. Selected students can now choose to download a digital version of their degree certificate to their smartphones when they graduate, in addition to receiving a paper diploma.",Some of the technology institute’s graduates can now choose to receive secure virtual credentials protected by block-chain technology.,https://www.insidehighered.com/news/2017/10/19/mit-introduces-digital-diplomas,https://www.insidehighered.com/sites/default/files/media/blockcerts.jpg,Post,,,Adoption,,,,,,,,2017-10-19,,,,,,,,,,,,,
+Blockcerts,CWX,,,,,,,,,CXC (Carribean) Pilots E-Certificates on the Blockchain,"During the Blockcerts pilot, some 24, 000 candidates who sat the 2018 May/June examinations and for whom CXC has e-mail addresses, will receive credentials to access their e-certificates. The candidates will also receive the traditional paper-based certificate.",,https://www.cxc.org/cxc-pilots-e-certificates-on-the-blockchain/,,Post,,,Adoption,,,,,,,,2018-10-29,,,,,,,,,,,,,
+Blockcerts,Learning Machine,,,,,,,,,Pluggable foundation blocks for building distributed apps.,When we first started building Exceptionless we found a lack of great solutions (that's not to say there isn't great solutions out there) for many key pieces to building scalable distributed applications while keeping the development experience simple. Here are a few examples of why we built and use Foundatio:,,https://github.com/learningmachine/Foundatio,,Code,,,Development,,,,,,,,2016-03-18,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,,,,,,JSON-LD processor written in Python,This library is an implementation of the JSON-LD specification in Python,,https://github.com/blockchain-certificates/pyld,,Code,,,Development,,,,,,,,2017-10-24,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,,,,,,blockchain-certificates/wallet-test-resources,These are resources used to test implementations of the evolving blockcerts certificate standard and issuer conventions.,,https://github.com/blockchain-certificates/wallet-test-resources,,Code,,,Development,,,,,,,,2018-01-17,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,,,,,,Issues Blockcerts using either the Bitcoin or Ethereum blockchain,The cert-issuer project issues blockchain certificates by creating a transaction from the issuing institution to the recipient on the Bitcoin or Ethereum blockchains. That transaction includes the hash of the certificate itself,,https://github.com/blockchain-certificates/cert-issuer,,Code,,,Development; Issuing,,,,,,,,2023-05-26,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,Open Badges,,,,,Command line tools for designing certificate templates and instantiating a certificate batch,"Blockcerts V3 is now based off W3C Verifiable Credentials specification and does not follow Open Badges V2 nomenclature anymore. To understand the differences between v2 and v3, please refer to the docs. You may also have a look at the JSONLD and JSON-SCHEMA document",,https://github.com/blockchain-certificates/cert-tools,,Code,,,Development; Issuing,,,,,,,,2022-04-08,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,,,,,,cert-core,This python library contains common Blockcerts models and accessors used by other Blockcerts python libraries.,,https://github.com/blockchain-certificates/cert-core,,Code,,,Development; Issuing,,,,,,,,2022-07-12,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,,,,,,Example of baking a blockcert into an Open Badge,The cert-issuer project issues blockchain certificates by creating a transaction from the issuing institution to the recipient on the Bitcoin or Ethereum blockchains. That transaction includes the hash of the certificate itself.,,https://github.com/blockchain-certificates/obi-baking,,Code,,,Development; Demo,,,,,,,,2017-07-13,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,,,,,,PoC for Blockcerts with Status List 2021 spec,,,https://github.com/blockchain-certificates/rl-blockcerts-poc,,Code,,,Development; Demo,,,,,,,,2023-03-30,,,,,,,,,,,,,
+Blockcerts,Learning Machine,,,,,,,,,learningmachine/polymer-redux,"An example use-case to showcase the state/view abstraction in Polymer 3, LitElement and Redux context",,https://github.com/learningmachine/polymer-redux,,Code,,,Development; Demo,,,,,,,,2018-09-28,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,,,,,,cert-schema,"Blockchain Certificate schemas implement those of Verifiable Credentials. As with Verifiable Credentials, we've provided both a JSON-LD context and JSON schema. The purpose of the JSON-LD context is to map types to Internationalized Resource Identifiers (IRIs), providing semantic context for data. The JSON Schema is used for syntactic validation.",,https://github.com/blockchain-certificates/cert-schema,,Code,,,Development; Verifiable Credentials,,,,,,,,2023-05-17,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,https://github.com/w3c-ccg/vc-status-rl-2020,,,,,,,Verifiable Credentials Revocation List 2020 JavaScript implementation,@digitalbazaar/vc-revocation-list,,https://github.com/blockchain-certificates/vc-revocation-list,,Code,,,Development; Verifiable Credentials,,,,,,,,2023-01-09,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,,,,,,A scaffholding to plug cert-issuer to vc-test-suite,,,https://github.com/blockchain-certificates/cert-issuer-node-wrapper,,Code,,,Development; Verifiable Credentials,,,,,,,,2023-05-24,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,,,,,,Verifiable Credentials WG Test Suite,This repository contains the W3C Verifiable Credentials Working Group test suite. Any conforming implementation MUST pass all tests in the test suite.,,https://github.com/blockchain-certificates/vc-test-suite,,Code,,,Development; Verifiable Credentials,,,,,,,,2021-10-31,,,,,,,,,,,,,
+Blockcerts,Learning Machine,,,,,,,,,The fastest JSON-Schema Validator. Supports draft-06,The fastest JSON Schema validator for node.js and browser with draft 6 support,,https://github.com/learningmachine/ajv,,Code,,,Development; Validation,,,,,,,,2017-05-09,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,Open Badges,,,,,Open Badges validation in python,"Open Badges Validator Core is a python package designed to verify the validity of Open Badges based on a variety of input sources and present a useful interface for accessing their properties and validation information. HTTP, Python and command line APIs are provided.",,https://github.com/blockchain-certificates/openbadges-validator-core,,Code,,,Development; Validation,,,,,,,,2017-10-06,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,,,,,,A Blockcerts verifier and viewer.,A standalone universal viewer & verifier for blockcerts credentials,,https://github.com/blockchain-certificates/blockcerts-verifier,,Code,,,Development; Verification,,,,,,,,2023-05-06,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,,,,,,Python library for verifying Blockcerts.,Library for verifying blockchain certificates.,,https://github.com/blockchain-certificates/cert-verifier,,Code,,,Development; Verification,,,,,,,,2020-06-06,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,,,,,,Javascript library for verifying Blockcerts Certificates,"IMPORTANT NOTE: as of version 5 of this library, v1 blockcerts are not supported anymore. Use https://www.npmjs.com/package/@blockcerts/cert-verifier-js-v1-legacy if needed.",,https://github.com/blockchain-certificates/cert-verifier-js,,Code,,,Development; Verification,,,,,,,,2023-05-05,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,,,,,,A web app for viewing and validating Blockchain Certificates,The cert-viewer project is a Flask webapp to display and verify blockchain certificates after they have been issued and to allow learners to request a certificate and generate their own Bitcoin identity needed for the certificate creation process.,,https://github.com/blockchain-certificates/cert-viewer,,Code,,,Development; Apps,,,,,,,,2018-05-10,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,,,,,,An Android app for Blockcerts.,Blockcerts Android application by Learning Machine,,https://github.com/blockchain-certificates/wallet-android,,Code,,,Development; Apps,,,,,,,,2023-02-24,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,,,,,,"An iOS wallet for viewing, validating, and sharing certs",This repository contains the core modules used to implement Blockcerts functionality in iOS.,,https://github.com/blockchain-certificates/BlockcertsFramework-iOS,,Code,,,Development; Apps,,,,,,,,2022-09-19,,,,,,,,,,,,,
+Blockcerts,Blockcerts,,,,,,,,,An iOS wallet for Blockcerts.,Blockcerts mobile app for iOS to receive and share certificates that are verifiable via the blockchain,,https://github.com/blockchain-certificates/wallet-iOS,,Code,,,Development; Apps,,,,,,,,2022-02-17,,,,,,,,,,,,,
+Linked Data,TwoBitHistory,,,,,,,,,Whatever Happened to the Semantic Web?,"In 2001, Tim Berners-Lee, inventor of the World Wide Web, published an article in Scientific American. Berners-Lee, along with two other researchers, Ora Lassila and James Hendler, wanted to give the world a preview of the revolutionary new changes they saw coming to the web. Since its introduction only a decade before, the web had fast become the world’s best means for sharing documents with other people. Now, the authors promised, the web would evolve to encompass not just documents but every kind of data one could imagine",,https://twobithistory.org/2018/05/27/semantic-web.html,,Post,,,Getting Started,,,,,,,,2018-05-27,,,,,,,,,,,,,
+Linked Data,W3C,,,,,,,,,LinkedData - W3C Wiki,"The idea behind these principles is on the one hand side, to use standards for the representation and the access to data on the Web. On the other hand, the principles propagate to set hyperlinks between data from different sources. These hyperlinks connect all Linked Data into a single global data graph, similar as the hyperlinks on the classic Web connect all HTML documents into a single global information space. Thus, LinkedData is to spreadsheets and databases what the Web of hypertext documents is to word processor files. The Linked Open Data cloud diagramms give an overview of the linked data sets that are available on the Web.",,https://www.w3.org/wiki/LinkedData,,entry,,,Getting Started,,,,,,,,2016-08-01,,,,,,,,,,,,,
+Linked Data,W3C,,,Tim Berners Lee,,,,,,Linked Data - Design Issues,"The Semantic Web isn't just about putting data on the web. It is about making links, so that a person or machine can explore the web of data.  With linked data, when you have some of it, you can find other, related, data.<br>Like the web of hypertext, the web of data is constructed with documents on the web. However,  unlike the web of hypertext,  where links are relationships anchors in hypertext documents written in HTML, for data they links  between arbitrary things described by RDF,.  The URIs identify any kind of object or  concept.   But for HTML or RDF, the same expectations apply to make the web grow:<br>- Use URIs as names for things<br>- Use HTTP URIs so that people can look up those names.<br>- When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL)<br>- Include links to other URIs. so that they can discover more things.",,https://www.w3.org/DesignIssues/LinkedData,https://www.w3.org/DesignIssues/diagrams/lod/597992118v2_350x350_Back.jpg,page,,,Getting Started,,,,,,,,2006-07-27,,,,,,,,,,,,,
+Linked Data,Semantalytics,,,,,,,,,Awesome Semantic Web,A curated list of various semantic web and linked data resources.,,https://github.com/semantalytics/awesome-semantic-web,,list,,,Getting Started,,,,,,,,2023-04-26,,,,,,,,,,,,,
+Linked Data,Nandana Mihindukulasooriya,,,,,,,,,Awesome Linked Data,A list of tools for publishing and consuming Linked Data.,,https://github.com/nandana/awesome-linkeddata,,list,,,Getting Started,,,,,,,,2017-03-07,,,,,,,,,,,,,
+Linked Data,Datahub,,,,,,,,,An overview of the Linked Open Data datasets.,A group for Linked Open Data datasets. The initial import of data for this group was done in October 2009 from the list of RDF datasets dumps provided by the W3C Linked Open Data Interest Group.,,https://datahub.io/collections/linked-open-data,https://datahub.io/static/img/opendata/product.png,list,,,Getting Started,,,,,,,,2018-05-10,,,,,,,,,,,,,
+Linked Data,W3C,,,,,,,,,Publishing and consuming Linked Data embedded in HTML,This document provides guidelines for how to create and consume Linked Data embedded in HTML. It extends and updates [HOWTO-LODP] and the [COOL-SWURIS] Note. The examples in this document use RDFa 1.1 and microdata with a special focus on Schema.org vocabulary terms.,,https://www.w3.org/2001/sw/interest/ldh/,https://www.w3.org/2001/sw/interest/ldh/img/acme-tabview.png,page,,,Getting Started,,,,,,,,2011-06-26,,,,,,,,,,,,,
+Linked Data,Personal,,,Kerstin Forsberg,,,,,,Linked Data for Enterprises,Keeping myself up to date on the practical use of Linked Data in Enterprises and related topics,,https://kerfors.blogspot.com/,https://1.bp.blogspot.com/-2T6XUMBB3WU/Vz4Yu-c9wdI/AAAAAAAAE3o/IBYw9dTSb_0JikoLeZ0N9s33OniI0BKMQCKgB/s400/Linked%2BData%2BURIs.png,page,,,Getting Started,,,,,,,,2016-12-15,,,,,,,,,,,,,
+Linked Data,Read-Write Linked Data,,,,,,,,,Examples in the Wild << Pretty Awesome List,"dokieli is a decentralised article authoring, annotation, and social notification tool which works from Web browsers. It is built with the following principles in mind: freedom of expression, decentralisation, interoperability, and accessibility.",,https://github.com/linkeddata/dokieli/wiki,,wiki,,,Getting Started,,,,,,,,2019-07-03,,,,,,,,,,,,,
+Linked Data,Solid,,,,,,,,,Understanding Linked Data slide deck (in Remark.js format),A slide deck introduction to Linked Data aimed at developers.,,https://github.com/solid/understanding-linked-data,,Presentation,,,Getting Started,,,,,,,,2019-10-03,,,,,,,,,,,,,
+Linked Data,LinkedDataTools,,,,,,,,,Introducing Linked Data And The Semantic Web,"What is Linked Data and the Semantic Web and what is all the hype about? Principally, the Semantic Web is a Web 3.0 web technology - a way of linking data between systems or entities that allows for rich, self-describing interrelations of data available across the globe on the web.",,http://www.linkeddatatools.com/semantic-web-basics,https://2mye7d.n3cdn1.secureserver.net/wp-content/uploads/2023/02/semantic-web-learning-curve.png,page,,,Getting Started,,,,,,,,2011-06-12,,,,,,,,,,,,,
+Linked Data,Personal,,,Ruben Verborgh,,,,,,Designing a Linked Data developer experience,"Making decentralized Web app development fun<br>While the Semantic Web community was fighting its own internal battles, we failed to gain traction with the people who build apps that are actually used: front-end developers. Ironically, Semantic Web enthusiasts have failed to...",,https://ruben.verborgh.org/blog/2018/12/28/designing-a-linked-data-developer-experience/,,Post,,,Main,,,,,,,,2018-12-28,,,,,,,,,,,,,
+Linked Data,WebofTrustInfo,,,"Christopher Lemmer Webber, Mark S. Miller",,,,,rwot05-boston,Linked Data Capabilities,"Linked Data Signatures enable a method of asserting the integrity of linked data documents that are passed throughout the web. The object capability model is a powerful system for ensuring the security of computing systems. In this paper, we explore layering an object capability model on top of Linked Data Signatures via chains of signed proclamations. fn:1 We call this system ""Linked Data Capabilities"", or ""ld-ocap"" for short.",,https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/final-documents/lds-ocap.md,,Paper,,,Main,,,,,,,,2022-12-28,,,,,,,,,,,,,
+Linked Data,WebofTrustInfo,,,,,,,,rwot3-sf,Identity as Linked Data on Immutable Ledgers,"Content creators on the Web are getting a raw deal. They get a fraction of a cent for an ad played on YouTube, and nothing on Facebook, for filling these sites with traffic-driving content. It’s hard to make a living when you’re a creative. Licensing is hard; the user experience is bad, so lawyers and middlemen extract the most value. In the music industry, more money flows into the pockets of distributors than creatives. Consumers are often happy to pay for their content. Instead, they're forced to sit through ads.",,https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/identity-as-linked-data-on-immutable-ledgers.md,,Paper,,,Main,,,,,,,,2016-10-17,,,,,,,,,,,,,
+Linked Data,WebofTrustInfo,,,"Manu Sporny, Harlan Wood, Noah Thorp, Wayne Vaughn, Christopher Allen, Jason Bukowski, and Dave Longley",,,,,rwot3-sf,Blockchain Extensions for Linked Data Signatures,"The term Linked Data is used to describe a recommended best practice for exposing, sharing, and connecting information on the Web using standards, such as URLs, to identify things and their properties. When information is presented as Linked Data, other related information can be easily discovered and new information can be easily linked to it. Linked Data is extensible in a decentralized way, greatly reducing barriers to large scale integration.<br>With the increase in usage of Linked Data for a variety of applications, there is a need to be able to verify the authenticity and integrity of Linked Data documents. The Linked Data Signatures specification added authentication and integrity protection to linked data documents through the use of public/private key cryptography without sacrificing Linked Data features such as extensibility and composability.",,https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/blockchain-extensions-for-linked-data-signatures.md,,Paper,,,Main,,,,,,,,2016-10-30,,,,,,,,,,,,,
+Linked Data,WebofTrustInfo,,,"Ganesh Annan, Kim Hamilton Duffy",,,,,rwot7-toronto,Resource Integrity Proofs,"Cryptographic linking provides discoverability, integrity, and scheme agility<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.<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",,,,,,,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,CCG,,,,,,,,,Linked Data Keys Registry,This repository contains the Linked Data Cryptographic Suite Registry which is a list of all known Linked Data cryptographic suites and their current level of maturity.,,https://github.com/w3c-ccg/ld-cryptosuite-registry,,registry,,,Implementation,,,,,,,Credentials Community Group,2020-12-29,,,,,,,,,,,,,
+Linked Data,DigitalBazaar,,,,,,,,,Linked Data Capabilities reference implementation,JavaScript reference implementation for Authorization Capabilities.,,https://github.com/digitalbazaar/ocapld.js,,Code,,,Implementation,,,,,,,,2023-01-14,,,,,,,,,,,,,
+Linked Data,W3C,,,,,,,,,RDF AND JSON-LD UseCases,This wiki page strive to address one of many question about use of RDF vs JSON-LD to store linked data. This page attempts to provide a general introduction of both the technologies and provide suitability analysis of various kind of applications to use either technology.,,https://www.w3.org/2013/dwbp/wiki/RDF_AND_JSON-LD_UseCases,https://www.w3.org/2013/dwbp/wiki/images/thumb/1/17/RDFSerialization-formats.png/800px-RDFSerialization-formats.png,page,,,RDF,,,,,,,,2014-09-15,,,,,,,,,,,,,
+Linked Data,W3C,,,,,,,,,Comparison of RDFJS libraries,This is a comparison of JavaScript libraries for working with RDF.,,https://www.w3.org/community/rdfjs/wiki/Comparison_of_RDFJS_libraries,,entry,,,RDF,,,,,,,,2019-01-18,,,,,,,,,,,,,
+Linked Data,W3C,,,,,,,,,RDF.js: The new RDF and Linked Data JavaScript library,"A diverse web requires decentralized data storage and maintenance. According to MIT’s Tim Berners-Lee, “it is about making links, so that a person or machine can explore the web of data. With Linked Data, when you have some of it, you can find other, related, data”.<br><br>Zazuko’s CTO Thomas Bergwinkl adds that “Linked Data is built on top of the web stack and the programming language of the web is JavaScript. It is crucial for Web Developers to have access to well-designed JavaScript libraries to work with RDF and Linked Data”.<br><br>The RDFJS W3C Community Group did a tremendous job in defining a standard to represent Linked Data in JavaScript. Several individuals and groups started to implement the RDFJS specification.",,https://www.w3.org/community/rdfjs/2018/04/23/rdf-js-the-new-rdf-and-linked-data-javascript-library/,,Post,,,RDF,,,,,,,,2018-04-23,,,,,,,,,,,,,
+Linked Data,RCH Working Group,,,,,,,,,RDF Dataset Canonicalization,"RDF [RDF-CONCEPTS] describes a graph-based data model for making claims about the world and provides the foundation for reasoning upon that graph of information. At times, it becomes necessary to compare the differences between sets of graphs, digitally sign them, or generate short identifiers for graphs via hashing algorithms. This document outlines an algorithm for normalizing RDF datasets such that these operations can be performed.",,https://w3c.github.io/rdf-canon/spec/,,Report,,,RDF,,,,,,,,2023-05-24,https://github.com/w3c/rdf-canon/,,,,,,,,,,,,
+GS1,GS1,,,,,,,,,GS1 - How we got here,"Since 1973, we have opened offices in over 110 countries and amassed more than 2 million members using supply chain standards that make business easier. Learn about key dates in our history.<br>- 1973: The barcode standard is agreed<br>- 1974: The first barcode is scanned<br>- 1977: The GS1 system is launched<br>- 1983: Barcodes are used on wholesale multi-packs<br>- 1989: GS1 moves beyond barcodes<br>  - With wide area networks making an impact on supply chains, we create our first international standard for electronic data interchange.<br>- 1990: Responsibilities grow<br>  - The US and international arms of GS1 come together formally, creating a single organisation with a presence in 45 countries.<br>- 1995: First healthcare standards created<br>- 1999: The GS1 DataBar arrives<br>- 2000: 90th local office opens<br>  - In just ten years, we double the number of countries in which we have a local presence.<br>- 2002: Global standards forum launched<br>  - Our Global Standards Management Process is launched. This global forum gives GS1 members one place to discuss standards.<br>- 2004: The first standard for RFID is created<br>- 2007: GS1 enters the business-to-consumer world<br>  - As ecommerce grows, we begin to create open standards that give consumers direct access to key product information.<br>- 2013: A 40-year celebration<br>  - With a presence in over 100 countries and more than a million members, we celebrate 40 years of the global language of business.",,https://www.gs1.org/about/how-we-got-here,,page,,,Main,,,,,,,,2023-04-25,,,,,,,,,,,,,
+GS1,GS1,,,,,,,,,Standards development,"A neutral participant, GS1 facilitates dialogue and the development of standards-based solutions among business and technical people from nearly sixty countries. Industries represented include retail and consumer goods, fresh foods, healthcare, transport and logistics, governments and many more.<br><br>The GSMP (Global Standards Management Process) is a community-based forum for businesses facing similar problems to work together and develop standards-based solutions. Standards created by industry, for industry.","The GSMP (Global Standards Management Process) is a community-based forum for businesses facing similar problems to work together and develop standards-based solutions. Standards created by industry, for industry.",https://www.gs1.org/standards/development,,page,,,Main,,,,,,,,2023-04-25,,,,,,,,,,,,,
+GS1,GS1,,,,,,,,,How we develop standards,Our standards development team guide the regular upgrading of our standards through a document development life cycle whose rules everyone agrees to. The Global Standards Management Process (GSMP) enables us to reach consensus around the creation and adoption of new standards smoothly and rapidly!,We develop our global supply chain standards in partnership with the industry experts and business teams who actually use them. Find out how we do it.,https://www.gs1.org/how-we-develop-standards,,page,,,Main,,,,,,,,2023-04-27,,,,,,,,,,,,,
+GS1,IDCommons,,,,,,,,IIW30,GS1's decentralized approach to resolving identifiers over HTTPS,"Slides are at http://docs.google.com/presentation/d/1fLDETcghxxRfac7mDCTGpqktaVnn9bjl/edit# General principles paper is at http://gs1.github.io/DigitalLinkDocs/principles/<br><br>GS1 DIgital Link standard makes the standard product Identifier - the “UPC” code web resolvable. Making it do more than go beep at the check out.<br><br>SSI / DIDs “not central point of issuance, no single point of failure”...but we can meet those requirements with persistent identifiers with centralized federation… centralized + delegation can work.",,https://iiw.idcommons.net/GS1%27s_decentralized_approach_to_resolving_identifiers_over_HTTPS,,Session Notes,,,Main,,,,,,,,2009-06-18,,,,,,,,,,,,,
+GS1,IDCommons,,https://gs1.github.io/DigitalLinkDocs/principles/,"Phil Archer, Mark Harrison, Henri Barthel",,,,,IIW30,Decentralized resolution of identifiers with HTTPS,11 Transferable Principles from GS1 Digital Link,,https://docs.google.com/presentation/d/1fLDETcghxxRfac7mDCTGpqktaVnn9bjl/edit#slide=id.p1,,Presentation,,,Main,,,,,,,,2020-04,,,,,,,,,,,,,
+GS1,GS1,,,,,,,,,GSMP Manual,"The GSMP 4-Step Process is designed to ensure that business needs and requirements are understood before standards and guidelines are developed, and that supporting materials are created afterward. Each step culminates in the completion of one or more outputs, created through a consensus-based process within a working group and with larger consensus confirmed through community review and eBallot.",,https://www.gs1.org/docs/gsmp/GSMP_Manual.pdf,,docs,,,Global Standards Mapping Process,,,,,,,,2022-07,,,,,,,,,,,,,
+GS1,GS1,,,,,,,,,Global Data Model (GDM) Governance Manual,"The retail landscape is changing at an unprecedented rate. In this connected world, consumers increasingly rely on product information for purchasing decisions. The purpose of the Global Data Model (GDM) is to simplify and harmonise the exchange of master data. The GDM will identify and define—in a globally consistent way—the set of foundational attributes needed to list/order, move, store and sell a product, both digitally and physically. By harmonising foundational data across the industry around the globe, it will enable an improved consumer experience and reduce complexity by delivering more reliable and complete product information to consumers.",,https://www.gs1.org/sites/default/files/docs/gsmp/gdm_manual_i1_a_2020-03-19.pdf,,docs,,,Global Standards Mapping Process,,,,,,,,2020-03-19,,,,,,,,,,,,,
+GS1,GS1,,,,,,,,,GSMP Value Statement,"Are business challenges holding back your company’s full potential and growth? You are not alone. Business is easier when you speak the same language as your customers, suppliers and partners. Though we all work in our own way, problems and differences become solutions when we all work together. That’s where GS1 can help.<br><br>The GSMP is a community-based forum for businesses facing similar problems to work together and develop standards-based solutions to address them. Standards created by industry, for industry.",,https://www.gs1.org/sites/default/files/docs/gsmp/gsmp_execsummary.pdf,,docs,,,Global Standards Mapping Process,,,,,,,,2015-10-02,,,,,,,,,,,,,
+GS1,GS1,,https://www.gs1.org/standards/development-work-groups,,,,,,,GSMP Data Accuracy SMG,"This processes all maintenance Work Requests for the **[GS1 Package Measurement Rules Standard](https://www.gs1.org/docs/gdsn/3.1/GS1_Package_Measurement_Rules.pdf)** and the **[Package Measurement Rules Implementation Guideline](https://www.gs1.org/sites/default/files/docs/gdsn/GDSN_Pack_Measure_Rules_Implementation_Guide.pdf)**. This group acts as a pool of experts for all Data Accuracy SMG work requests and coordinate with associated Mission Specific groups as defined in the GSMP Manual. The work the Data Accuracy SMG allows our community to increase savings throughout the supply chain by synchronising accurate dimensions and weight data which enables better transportation, logistics and retail shelf planning.",,https://www.gs1.org/standards/development-work-groups#DA,,Working Group,,,Working Groups,,,,,,,,2010-04-15,,,,,,,,,,,,,
+GS1,GS1,,https://www.gs1.org/standards/development-work-groups,,,,,,,GSMP Electronic Data Interchange (EDI) SMG,This group maintains and improves [GS1 EDI (Electronic Data Interchange) standards](https://www.gs1.org/standards/edi). Examples of standards maintained in this group (but not limited to) are:<br>- EANCOM®<br>- GS1 XML<br>- GS1 UN/CEFACT XML,,https://www.gs1.org/standards/development-work-groups#EDI,,Working Group,,,Working Groups,,,,,,,,2010-04-15,,,,,,,,,,,,,
+GS1,GS1,,https://www.gs1.org/standards/development-work-groups,,,,,,,GSMP Global Master Data (GMD) SMG,"The group maintains and improves the GS1 Master Data standards. Examples of standards maintained in this group (but not limited to) are:<br>- [Master Data Standards](https://www.gs1.org/standards/gs1-global-data-model)<br>- GS1 Attributes, definitions, code lists, and guidance definitions<br>- [GDSN solutions and GDSN Validation Rules](https://www.gs1.org/standards/gdsn)<br>- GS1 Web Vocabulary<br>- Global Data Model Standards and Attribute Definitions for Business",,https://www.gs1.org/standards/development-work-groups#GMD,,Working Group,,,Working Groups,,,,,,,,2013-12-14,,,,,,,,,,,,,
+GS1,GS1,,https://www.gs1.org/standards/development-work-groups,,,,,,,GSMP Global Product Classification (GPC) SMG,"The GPC Standards Maintenance Group maintains and improves the GS1 Global Product Classification (GPC) standard.<br><br>The [GS1 Global Product Classification (GPC) standard](https://www.gs1.org/standards/gpc) helps global trading partners to group products in the same way, everywhere in the world. The resulting common business language is clear and instantly understandable.",,https://www.gs1.org/standards/development-work-groups#GPC,,Working Group,,,Working Groups,,,,,,,,2010-04-15,,,,,,,,,,,,,
+GS1,GS1,,https://www.gs1.org/standards/development-work-groups,,,,,,,GSMP Identification SMG,"The ID Standards Maintenance Group maintains and improves the GS1 Automatic Identification and Data Capture (AIDC) standards including Identification Keys, Barcodes, Electronic Product Code, and Radio-Frequency Identification (RFID) standards.<br><br>- The GS1 General Specification is the core foundational GS1 standard that defines how identification keys, data attributes and barcodes must be used in business applications<br>- GS1 Identification Keys provides companies efficient ways to access and share information about items in their supply chains.<br>- Barcodes are symbols that can be scanned electronically using laser or camera-based systems.<br>- The Electronic Product Code™ (EPC) is syntax for unique identifiers assigned to physical objects, unit loads, locations, or other identifiable entity playing a role in business operations.<br>- GS1's EPC Tag Data Standard (TDS) defines the Electronic Product Code (EPC), including its correspondence to GS1 keys and other existing codes. TDS also specifies data that is carried on Gen 2 RFID tags, including the EPC, User Memory data, control information, and tag manufacture information.",,https://www.gs1.org/standards/development-work-groups#ID,,Working Group,,,Working Groups,,,,,,,,2010-04-15,,,,,,,,,,,,,
+GS1,GS1,,,,,,,,,GSMP Traceability and Event Sharing Standards Maintenance Group SMG,"The SMG maintains updates to the GS1 EPCglobal standards that support physical event capture and sharing and the [Global Traceability Standard that supports tracking and tracing of goods](https://www.gs1.org/sites/default/files/docs/gsmp/call_to_action_gtc_h.pdf) and information about the goods. This includes all simple work requests indicated as impacting the event data sharing and traceability standards.<br><br>In addition, the group acts as a pool of experts for all Mission Specific Work Groups that are related to the SMG, as defined in the GSMP Manual in section 3.4. Work Groups.",,https://www.gs1.org/standards/development-work-groups#TRACE_EVENT,,Working Group,,,Working Groups,,,,,,,,2011-05-26,,,,,,,,,,,,,
+GS1,GS1,,,,,,,,,GSMP Digital Signature MSWG,"Provide a GS1 standard solution approach to digital signatures. Otherwise, there will be no open, brand owner determined digital signatures to set as an alternative to proprietary digital signature use in barcodes with GS1 standards.",Mission-specific Working Groups (MSWGs) develop new standards,https://www.gs1.org/standards/development-work-groups#DigitalSignature,,Working Group,,,Working Groups,,,,,,,,2020-03-26,,,,,,,,,,,,,
+GS1,GS1,,,,,,,,,GSMP EPCIS & CBV 2.0 MSWG,"Since its initial ratification as an EPCglobal standard in 2007 and its subsequent integration into the GS1 “Share” portfolio, EPCIS and its companion standard the Core Business Vocabulary (CBV) have been updated twice (2014 and 2016) and published by ISO (as ISO/IEC 19987 and 19988, respectively). In the meantime, EPCIS and the CBV have gained importance as visibility enablers in various industries. Updates are needed to ensure the relevance of these standards into the coming decades.",Mission-specific Working Groups (MSWGs) develop new standards,https://www.gs1.org/standards/development-work-groups#EPCISCBV,,Working Group,,,Working Groups,,,,,,,,2018-02-19,,,,,,,,,,,,,
+GS1,GS1,,,,,,,,,GSMP GLN Modernisation MSWG,"This work group will update the GLN Standards to be more clear and concise and provide guidance to enable industry partners to create, manage, share, and use the GLN to meet their party and location use cases needs in a scalable, standardised manner.",Mission-specific Working Groups (MSWGs) develop new standards,https://www.gs1.org/standards/development-work-groups#GLNM,,Working Group,,,Working Groups,,,,,,,,2022-08-16,,,,,,,,,,,,,
+Object Capabilities,Personal,,,Dan Connolly,,,,,,Awesome Object Capabilities and Capability-based Security,Capability-based security enables the concise composition of powerful [patterns](https://github.com/dckc/awesome-ocap/wiki) of cooperation without vulnerability. [What Are Capabilities?](http://habitatchronicles.com/2017/05/what-are-capabilities/) explains in detail.,,https://github.com/dckc/awesome-ocap,,list,,,Main,,,,,,,,2023-03-03,,,,,,,,,,,,,
+Object Capabilities,Wikipedia,,,,,,,,,Object Capability Model,"Computer scientist E. Dean Tribble stated that in smart contracts, identity-based access control did not support well dynamically changing permissions, compared to the object-capability model. He analogized the ocap model with giving a valet the key to one's car, without handing over the right to car ownership.<br><br>The structural properties of object capability systems favor modularity in code design and ensure reliable encapsulation in code implementation.<br><br>These structural properties facilitate the analysis of some security properties of an object-capability program or operating system. Some of these – in particular, information flow properties – can be analyzed at the level of object references and connectivity, independent of any knowledge or analysis of the code that determines the behavior of the objects. As a consequence, these security properties can be established and maintained in the presence of new objects that contain unknown and possibly malicious code.",,https://en.wikipedia.org/wiki/Object-capability_model,,entry,,,Main,,,,,,,,2023-04-12,,,,,,,,,,,,,
+Object Capabilities,eRights,,,Mark S. Miller,,,,,,Object Capabilities,"The capability model is, in a sense, the object model taken to its logical extreme. Where object programmers seek modularity -- a decrease in the dependencies between separately thought-out units -- capability programmers seek security, recognizing that required trust is a form of dependency. Object programmers wish to guard against bugs: a bug in module A should not propagate to module B. Capability programmers wish to guard against malice. However, if B is designed to be invulnerable to A's malice, it is likely also invulnerable to A's bugs.",E: Cryptographic Capabilities for Distributed Smart Contracting,http://erights.org/elib/capability/ode/ode-capabilities.html,http://erights.org/elib/capability/ode/images/money.png,page,,,Main,,,,,,,,1998-10-03,,,,,,,,,,,,,
+Object Capabilities,IDCommons,,,,,,,,IIW,DIDAuth + Obj. Cap. - IIW,"What is DIDAuth and how is it compatible with Object Capabilities?<br>We started by defining and describing object capabilities:<br>- A Capability is a Transferable Unforgeable Permission. It can be implemented with unguessable URLS or signed objects.<br>- A Java Program object reference is a capability, it allows for actions on the subject (the object instance).<br>- A stronger implementation of object capabilities involves a digital certificate issued by a public key, for a resource with a set of supported methods:<br>`Issuer: AlicePubKey`<br>`Resource: did:dad:0x123`<br>`Actions: Read,Write`<br>`Signature: 0x456`",,https://iiw.idcommons.net/DIDAuth_%2B_Obj._Cap.,https://iiw.idcommons.net/images/c/cb/TH1G.jpg,Session Notes,,,Literature,,,,,,,,2018-10-31,,,,,,,,,,,,,
+Object Capabilities,WebofTrustInfo,,,Bill Tulloh,,,,,rwot8-barcelona,Applying the Principle of Least Authority to User Interaction,"Object capabilities (ocaps) are increasingly recognized as an important tool for achieving the goals of self-sovereign identity. Many of the principles of self-sovereign identity, such as minimization and protection, can best be achieved through the disciplined pursuit of the principle of least authority that ocaps enable. This paper examines how POLA can be extended to better protect users when exercising their self-sovereign identity.",,https://github.com/WebOfTrustInfo/rwot8-barcelona/blob/master/topics-and-advance-readings/Applying_POLA_to_User_Interaction.md,,Paper,,,Literature,,,,,,,,2019-02-25,,,,,,,,,,,,,
+Object Capabilities,WebofTrustInfo,,,James Foley,,,,,rwot7-toronto,Introductory Capability DHT,The Object Capability software design paradigm is a powerful philosophy for the programming of decentralized applications particularly in the realms of security and rights management.,,https://github.com/WebOfTrustInfo/rwot8-barcelona/blob/master/topics-and-advance-readings/introductory-capability-dht-concept.md,,Paper,,,Literature,,,,,,,,2019-02-08,,,,,,,,,,,,,
+Object Capabilities,WebofTrustInfo,,,"Joe Andrieu, Nathan George, Christophe Macintosh, Ouri Poupko, Antoine Rondelet, Andrew Hughes",,,,,rwot7-toronto,Models of Identity,"**Security** • **Liberty** • **Data** • **Relationship** • **Capability** <br><br>Considering different models for handling identity information allows reconciliation, and creates opportunities to address primary use cases across paradigms, increasing overall strength and security of a solution.<br>[...]<br>In the Object Capabilities model, authorization is managed by creating, sharing, attenuating, and using “capabilities” instead of, for example, access control lists. If you have a valid “capability”, you have the authorization. Like a car key, Object Capabilities may be used no matter who you are. This model shifts the burden of identification from error-prone correlations to directly work with individuals’ actual capabilities.",,https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/mental-models.md,,Paper,,,Literature,,,,,,,,2020-05-17,,,,,,,,,,,,,
+Object Capabilities,WebofTrustInfo,,,"Manu Sporny, Dave Longley, Christopher Lemmer Webber",,,,,rwot7-toronto,Cryptographic and Data Modeling Requirements from RWoT,"This paper introduces the uninitiated to the requirements that have been identified over the years that are driving the community toward certain technological solutions.<br><br>Rebooting the Web of Trust is a community that is attempting to create a decentralized ecosystem that enables people to be in control of various aspects of their data and identity information. The group often talks about Decentralized Identifiers, Verifiable Credentials, Object Capabilities, ed25519 keys, cryptographic identifiers, and other technologies but rarely spends time documenting how we got here.",,https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/topics-and-advance-readings/crypto-data-model-requirements.md,,Paper,,,Literature,,,,,,,,2018-08-23,,,,,,,,,,,,,
+Object Capabilities,WebofTrustInfo,,,Christopher Lemmer Webber,,,,,rwot6-santabarbera,Recent happenings with Linked Data Capabilities,"One of the outputs from Rebooting Web of Trust Fall 2017 was a writeup on Linked Data Capabilities based on discussions from the workshop (and particularly thanks to the guide of Mark S. Miller's longstanding work on object capabilities). While the writeup speaks for itself, in short Linked Data Capabilities provide a way to encode object capability security to linked data systems. Much has happened since then.<br><br>After the workshop ideas from the paper were reified into specification form and the W3C Credentials Community Group has taken on the specification as an official work item of the group. Some changes have happened in the design of Linked Data Capabilities from the initial Rebooting Web of Trust paper",,https://github.com/WebOfTrustInfo/rwot6-santabarbara/blob/master/topics-and-advance-readings/ld-ocap-recent-happenings.md,,Paper,,,Literature,,,,,,,,2018-03-02,,,,,,,,,,,,,
+Object Capabilities,WebofTrustInfo,,,Christopher Lemmer Webber and Christopher Allen,,,,,rwot5-boston,Smarm: Requirements for a smart-signatures Scheme,"[Smart signatures](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/draft-documents/smarm.md) are desirable, but how to implement them? We need a language that is powerful and flexible enough to meet our needs while safe and bounded to run while remaining simple enough to feasibly implement.<br><br>[Scheme](https://en.wikipedia.org/wiki/Scheme_programming_language) is a turing-complete language with a (at least stated) fondness for minimalism. Unfortunately Scheme on its own is neither ""safe"" nor (necessarily) deterministic. Thankfully we can get the properties we want through:<br><br>- Making object capabilities a core part of the language. Specifically, [Jonathan Rees' ""W7 security kernel""](http://mumble.net/~jar/pubs/secureos/secureos.html) demonstrates that a pure lexically scoped environment is itself an appropritate substrate for object capabilities.<br>- Restricting space and time precisely in a way that is deterministic and reproducible.<br>- Removing sources of external side effects.",,https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/draft-documents/smarm.md,,Paper,,,Literature,,,,,,,,2017-10-05,,,,,,,,,,,,,
+Object Capabilities,WebofTrustInfo,,,"Adrian Gropper, Drummond Reed, Mark S. Miller",,,,,rwot5-boston,Identity Hubs Capabilities Perspective,"Identity Hubs as currently proposed in the Decentralized Identity Foundation (DIF) are a subset of a general Decentralized Identifier (DID) based user-controlled agent, based on ACLs rather than an object-capabilities (ocap) architecture.  The current approach has both security and scalability issues. Transitioning the Hubs design to an ocap model can be achieved by introducing an UMA authorization server as the control endpoint. This avoids creating confused-deputy security issues and expands scale by enabling the hub to delegate access to resources not stored in the hub itself.",,https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/final-documents/identity-hubs-capabilities-perspective.md,,Paper,,,Literature,,,,,,,,2017-10-14,,,,,,,,,,,,,
+Object Capabilities,WebofTrustInfo,,,"Christopher Lemmer Webber, Mark S. Miller",,,,,rwot5-boston,Linked Data Capabilities,"Linked Data Signatures enable a method of asserting the integrity of linked data documents that are passed throughout the web. The object capability model is a powerful system for ensuring the security of computing systems. In this paper, we explore layering an object capability model on top of Linked Data Signatures via chains of signed proclamations. fn:1 We call this system ""Linked Data Capabilities"", or ""ld-ocap"" for short.",,https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/final-documents/lds-ocap.md,,Paper,,,Literature,,,,,,,,2022-11-28,,,,,,,,,,,,,
+DIDComm,CCG Mailing List,,,Daniel Hardman,,,,,,announcement: DIDComm user group,"Now that the [DIDComm v2 spec](https://identity.foundation/didcomm-messaging/spec/) is nearing completion, and there are [robust libraries in multiple programming languages](https://github.com/decentralized-identity/didcomm-messaging#implementations), we are starting a user group to share learnings as we put DIDComm into production. We will organize community resources, produce a handbook, foster application-level protocol creation, maintain the [didcomm.org website](https://didcomm.org) and [repo](https://github.com/decentralized-identity/didcomm.org), and recommend best practices.",,https://lists.w3.org/Archives/Public/public-credentials/2022Jan/0168.html,,Discussion,,,main,,,,,,,,2022-01-20,,,,,,,,,,,,,
+DIDComm,CCG Mailing List,,https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0032.html,,,,,,,DIDComm V2 Primer,"1. What it is<br>2. What it does and doesn't do<br>3. Relationship to WACI-DIDComm, CHAPI, OIDC-SIOP<br>4. Versions<br>5. Implementations",,https://lists.w3.org/Archives/Public/public-credentials/2022Apr/att-0032/DIDComm_v2_Primer.pdf,,Discussion,,,main,,,,,,,,2022-04,,,,,,,,,,,,,
+DIDComm,didcomm.org,,,,,,,,,didcomm.org,"DIDComm lets people and software use [DIDs](https://www.w3.org/TR/did-core/) to communicate securely and privately over many channels: the web, email, mobile push notifications, QR codes, Bluetooth, message queues, sneakernet, and more.",,https://didcomm.org/,,site,,,main,,,,,,,,,,,,,,,,,,,,,
+DIDComm,DIF,DIDComm WG,https://github.com/decentralized-identity/org/blob/master/Org%20documents/WG%20documents/DIF_DIDcomm_WG_Charter_v1.pdf,,,,,,,DID Communications Working Group,"Join this group to contribute to specs that embody a method for secure, private and authenticated message-based communication, where trust is rooted in DIDs and used over a wide variety of transports.",,https://identity.foundation/working-groups/did-comm.html,,Working Group,,,Working Group,,,,,,,,2020-09-18,https://github.com/decentralized-identity/didcomm-messaging/,,,https://dif.groups.io/g/didcomm-wg,,,,,,,,,
+DIDComm,DIF,,,,,,,,,DIDComm V2 reaches approved spec status!,"Following the approval of the Decentralized Identifiers (DID) Core Spec by the W3C as an official open web standard, the Decentralized Identity Foundation (DIF) announced the approval of the DIDComm v2 specification. Combined, this represents a major step forward in the acceptance of decentralized identity, one that opens the path to widespread adoption and further development especially with regard to the types of peer-to-peer communication now possible.<br><br>DIDComm defines how messages are composed into application-level protocols and workflows.","DIDComm v2 has now reached DIF Approved Status, joining SideTree as a complete and approved open-source specification.",https://blog.identity.foundation/didcomm-v2/,,Post,,,Working Group,,,,,,,DIDComm WG,2022-07-26,,,,,,,,,,,,,
+DIDComm,DIDComm WG,,,"Sam Curren, Tobias Looker, Oliver Terbu, Kyle Den Hartog, Baha Shaaban, Drummond Reed, Steve McCown, Troy Ronda, George Aristy, Vyacheslav Gudkov, Alexander Shcherbakov, Alexander Martynov, Daniel Buchner, Devin Fisher, Orie Steele, Brian Richter, Juan Caballero, @liormargalit, Timo Glastra, Andrew Whitehead, Nader Helmy, Markus Sabadello, Patrick McClurg, Stephen Curran, Daniel Hardman, Moe Jangda","Indicio, TBD, SICPA, Danube Tech, MATTR, Animo, Aviary, Transmute, Centre, Microsoft, Evernym, DSR, SecureKey, ConsenSys, BCGov, Anonyome",,,,,DIDComm Messaging v2.1 Editor’s Draft,"DIDComm enables higher-order protocols that inherit its security, privacy, decentralization, and transport independence. Examples include exchanging verifiable credentials, creating and maintaining relationships, buying and selling, scheduling events, negotiating contracts, voting, presenting tickets for travel, applying to employers or schools or banks, arranging healthcare, and playing games. Like web services atop HTTP, the possibilities are endless; unlike web services atop HTTP, many parties can participate without being clients of a central server, and they can use a mixture of connectivity models and technologies.",,https://identity.foundation/didcomm-messaging/spec/,,Specification,,,Working Group,,,,,,,,2023-04-26,https://github.com/decentralized-identity/didcomm-messaging,,,,,,,,,,,,
+DIDComm,DIDComm WG,,,,,,,,,DIDcomm WG Operating Addendum,We are designing communications protocols specifically for use with the decentralized identifier specification at W3C (​https://www.w3.org/TR/did-core/​).  The DID Core specification and the surrounding family of DID specifications (e.g ​https://w3c-ccg.github.io/did-resolution/​) represent the format for entity identification in our DIDComm efforts.,,https://github.com/decentralized-identity/org/blob/master/Org%20documents/WG%20documents/DIF_DIDcomm_WG_Operating_Addendum_v1.pdf,,Page,,,Working Group,,,,,,,,2020-09-18,,,,,,,,,,,,,
+DIDComm,DIDComm WG,,,,,,,,,DIF starts DIDComm Working Group,"Over the past few months, the DIF and Hyperledger Aries community have come together and agreed to work on a common work item aimed at developing secure communication based on Decentralized Identifiers (DIDs) — hence the name DIDComm, which is short for DID Communication. Significant prior work in developing a messaging-based communication protocol using DIDs has been incubating in the HyperLedger (HL) Aries community, with the progress of this effort evident in the resulting [Aries RFCs](https://github.com/hyperledger/aries-rfcs). To address the requirements of a broader and more heterogeneous community we selected DIF as the place to pursue the next phase of work associated with this effort. Presenting the progress of DIDcomm to other relevant working groups will drive the interoperability between the various decentralized identity vendors and hence enabling a range of decentralized identity-related use cases.",,https://medium.com/decentralized-identity/dif-starts-didcomm-working-group-9c114d9308dc,,Post,,,Working Group,,,,,,,,2020-01-09,,,,,,,,,,,,,
+DIDComm,DIDComm WG,,,,,,,,,decentralized-identity/DIDComm-js,DIDComm JS LibA shared effort with the HL Aries project to create a standardized means of authenticated general message passing between DID controllers. More information will be added soon.,,https://github.com/decentralized-identity/DIDComm-js,,Code,,,Working Group,,,,,,,,2020-01-09,,,,,,,,,,,,,
+DIDComm,IDCommons,,https://docs.google.com/presentation/d/16HTPyZV_-BtM6EifQpxjivRHKYUeVtOAReUD1eGUA9M/edit?usp=sharing,Sam Curren,,,,,IIW,2D/ Why the Internet Needs DIDComm - IIW,- Enables Verifiable Communication<br> - Intelligence at the edge (like email)<br> - Protocol Based (like email)<br> - Supports HTTP(s) (like APIs) and others as a transport<br> - Bluetooth enables Edge to Edge transport<br> - Mobile / Offline Friendly (like email)<br> - Supports rotating from one DID to another<br> - Security independent of transport<br> - Protocol development becomes easier and more robust (unlike email),,https://iiw.idcommons.net/2D/_Why_the_Internet_Needs_DIDComm,,Session Notes,,,Explainer,,,,,,,,2021-05-06,,,,,,,,,,,,,
+DIDComm,IDCommons,,,Paul Knowles,,,,,IIW,2E/ Decentralized Semantics 101 - IIW,"A digital network must contain authenticable data entry and immutable data<br> <br> capture elements in order to maintain balance and integrity.<br> <br> Within the context of a decentralized network, these fundamentals enable a self-regulating system where ...<br> <br> (1) data inputs can be trusted as having come from an assured source under the control of a governing entity; and<br> <br> (2) semantic items ensure that the meaning and use of inputted data remains unaltered for all interacting actors.",,https://iiw.idcommons.net/2E/_Decentralized_Semantics_101,,Session Notes,,,Explainer,,,,,,,,2021-05-06,,,,,,,,,,,,,
+DIDComm,IDCommons,,,Phil Windley,,,,,IIW,21A/ DIDComm and the Self-Sovereign Internet - IIW,"DID-based relationships are the foundation of self-sovereign identity (SSI). The exchange of DIDs to form a connection with another party gives both parties a relationship that is self-certifying and mutually authenticated. Further, the connection forms a secure messaging channel called DID Communication or DIDComm. DIDComm messaging is more important than most understand, providing a secure, interoperable, and flexible general messaging overlay for the entire internet.",,https://iiw.idcommons.net/21A/_DIDComm_and_the_Self-Sovereign_Internet,,Session Notes,,,Explainer,,,,,,,,2021-05-06,,,,,,,,,,,,,
+DIDComm,Personal,,,Phillip J. Windley,,,,,,DIDComm and the Self-Sovereign Internet,"DIDComm is a protocol layer capable of supporting specialized application protocols for specific workflows. Because of its general nature and inherent support for self-sovereign relationships, DIDComm provides a basis for a self-sovereign internet much more private, enabling, and flexible than the one we've built using Web 2.0 technologies. This talk introduces DIDComm, discusses its protocological nature, and presents use cases in the Internet of Things. Demonstrations of DIDComm protocol interactions will be shown on the Pico platform, which implements the Aries Cloud Agent (ACA) specification.",,https://www.windley.com/archives/2020/11/didcomm_and_the_self-sovereign_internet.shtml,,Post,,,Explainer,,,,,,,,2020-11-11,,,,,,,,,,,,,
+DIDComm,DIF,,,Kaliya Young,,,,,,Why we need DIDComm - Identity Woman,This is the text of an email I got today from a company that I had a contract with last year [...] I was reminded quite strongly why we need DIDComm as a protocol to enable the secure transport of all sorts of things not just signed VCs but intermediate uses,,https://identitywoman.net/why-we-need-didcomm/,,Post,,,Explainer,,,,,,,,2022-01-12,,,,,,,,,,,,,
+DIDComm,Personal,,,Daniel Hardman,,,,,,DIDComm Mythconceptions,DIDComm is a peer-to-peer communication technology for SSI (self-sovereign identity) with security and privacy properties rooted in DIDs (decentralized identifiers). Its core value proposition is often misunderstood or oversimplified. This webinar provides a proper mental model.,,https://www.youtube.com/watch?v=rwvQdRyMeY4,https://i.ytimg.com/vi/rwvQdRyMeY4/maxresdefault.jpg?sqp=-oaymwEmCIAKENAF8quKqQMa8AEB-AH-CYAC0AWKAgwIABABGGUgXig_MA8=&rs=AOn4CLCxo_GS9BmeYLTCl5mB-923nmd_Vg,Video,,,Explainer,,,,,,,,2021-11-10,,,,,,,,,,,,,
+DIDComm,twit.tv,,,Sam Curren,,,,,,"DIDCOMM - Sam Curren, Importance of DIDs",Sam Curren unpacks for Doc Searls and Dan Lynch why DIDs and DIDcomm are the best approach to identity—and to making people first-class citizens on the Internet. Curren also discusses the origin story of picos and the advantages of nomadic living and hacking.,,https://twit.tv/shows/floss-weekly/episodes/685,,episode,,,Explainer,,,,,,,,2022-06-15,,,,,,,,,,,,,
+DIDComm,Hyperledger,,,,,,,,,Aries RFC 0453 - credential issuance protocol using DIDComm V1 data formats,An optional mechanism for providing credential supplements during issuance. Supplements are also used in credential presentation.,,https://github.com/hyperledger/aries-rfcs/tree/master/features/0453-issue-credential-v2,,rfc,,,RFCs,,,,,,,Aries RFC,2021-04-15,,,,,,,,,,,,,
+DIDComm,Hyperledger,,,,,,,,,Aries RFC 0454 - Present Proof protocol V2 using DIDCommV1 data formats,"A minor update to add mechanism for a Verifier to request the Prover submit multiple presentations in the ""presentation"" message(s), each presentation sourced from different credentials that satisfy the presentation request. An example use of this capability is an employer (Verifier) requesting multiple ""proof of employment"" presentations from a job application (Prover), each satisfying the one presentation request.",,https://github.com/hyperledger/aries-rfcs/tree/master/features/0454-present-proof-v2,,rfc,,,RFCs,,,,,,,Aries RFC,2021-04-15,,,,,,,,,,,,,
+DIDComm,IDCommons,,,,,,,,IIW,"DIDComm V2: Implementation and integration 'technical' - did:key and did:keri resolvers, seamless and partial integrations","Technical session covering basics of DIDComm v2 Rust implementation (didcomm-rs), including JWM message format overview, JWE/JWM envelopes and key identifiers structures as well as cryptography usage. In addition we’ve discussed how key resolution of public keys happening from `kid` and `skid` envelope header fields using plugable resolvers and private keys resolver using Vault Key provider in form of “Universal wallet” spec implementation [wallet-rs].",,"https://iiw.idcommons.net/11D/_DIDComm_V2:_Implementation_and_integration_%27technical%27_-_did:key_and_did:keri_resolvers,_seamless_and_partial_integrations-",,Session Notes,,,Development,,,,,,,,2021-05-07,,,,,,,,,,,,,
+DIDComm,Jolocom,,,Ivan Temchenko,,,,,,didcomm-rs implementation,What is this talk about?<br><br>• didcomm-rs implementation<br>• Resolver[s] integration<br>• Application level integration (with wallet-rs)<br>• End-to-end consuming application example demo – simple console chat application based on DIDComm v2 and did:key/did:keri (with resolvers)<br>• Floor open for discussions,,https://drive.google.com/file/d/1dn5f2SqnCeQocOy5quJD9gpMPipKRmdC/view?usp=sharing,,Presentation,,,Development,,,,,,,,2021-04-21,,,,,,,,,,,,,
+DIDComm,DIF,,,,,,,,,Rust implementation of DIDComm v2,This is a sample implementation of the DIDComm V2 spec. The DIDComm V2 spec is still actively being developed by the DIDComm WG in the DIF and therefore subject to change.,,https://github.com/decentralized-identity/didcomm-rs,,Code,,,Development,,,,,,,,2022-10-10,,,,,,,,,,,,,
+DIDComm,uPort,,,Oliver Terbu,uPort,,,,,Trusted P2P messaging with DIDs DIDComm and VCs,"about their path towards trusted P2P messaging and announces the [DIDAgent Framework (DAF)](https://github.com/uport-project/daf)<br>when we speak about a DID, then we need to be more precise and also speak about the particular DID method of that DID which defines the CRUD operations on a target system such as Ethereum.",A Decentralized Identifier (DID) is a stable identifier in form of an URI that introduces a level of indirection for key management and managing other useful information such as service endpoints. It…,https://medium.com/uport/trusted-p2p-messaging-with-dids-didcomm-and-vcs-398f4c3f3cda,,Post,,,Development,,,,,,,,2020-11-12,,,,,,,,,,,,,
+DIDComm,uPort,,,Oliver Terbu,,,,,,DIDComm Messaging through libp2p,"We outlined the next generation decentralized messaging solution built on top of [DIDComm Messaging](https://identity.foundation/didcomm-messaging/spec/), [DIDs](https://www.w3.org/TR/did-core/) and [VCs](https://www.w3.org/TR/vc-data-model/) and a [libp2p](https://libp2p.io/) overlay network. We presented how Alice and Bob establish a connection, exchange messages and demonstrated what connection types are supported.",With InterPlanetary File System (IPFS) the Web3 community has established a critical piece of infrastructure that is used by the majority of web3 protocols to different degrees. Libp2p is part of the…,https://medium.com/uport/didcomm-messaging-through-libp2p-cffe0f06a062,,Post,,,Development,,,,,,,,2021-11-30,,,,,,,,,,,,,
+DIDComm,WebofTrustInfo,,,Karim Stekelenburg,Animo Solutions,,,,,Advanced DIDComm Messaging,"in order for DIDComm to provide a potential replacement for commonly used chat protocols like WhatsApp (Extensible Messaging and Presence Protocol (XMPP)), Telegram (MTProto), or Signal (Signal Protocol), it needs to support modern chat features we use everyday",,https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/advance-readings/advanced-didcomm-messaging.md,,Paper,,0.1,Development,,,,,,,,2022-07-19,,,,,,,,,,,,,
+DIDComm,DATEV,,,Tim Vorgs,,,,,,DIDComm & DIDComm Messaging,"Based on the research project we conducted with SAP, we developed a Proof of Concept (PoC for order-to-cash-business processes. As part of this PoC, we integrated DIDComm based communication to seamlessly transfer data within the boundaries of the process. The overall steps are:",,https://medium.com/datev-techblog/didcomm-didcomm-messaging-3e10fbf12bb8,https://miro.medium.com/v2/resize:fit:1200/1*prcKX5OvEifMsbSiijDj1A.png,Post,,,Development,,,,,,,,2022-07-18,,,,,,,,,,,,,
+DIDComm,DIF,,,,,,,,,"DIF F2FJan21 - DIDComm Demo Session with Ivan Temchenko, Tobias Looker, and Oliver Terbu","During the live demo he showed the message lifecycle in various setups using the new, [open source didcomm-rs library](http://github.com/jolocom/didcomm-rs) on GitHub","In this informal F2F side-session, Jolocom's Ivan Temchenko gives a detailed tour of their core DIDComm v2 library in Rust, followed by a brief CLI demo from...",https://www.youtube.com/watch?v=SaNvIorKQ9I&feature=youtu.be,,Video,,,Development,,,,,,,,2021-01-26,,,,,,,,,,,,,
+DIDComm,gold and double blue,,,Siddhi,,,,,,Blockchain and Self-Sovereign Identity Empowered Cyber Threat Information Sharing Platform,Blockchain and Self-Sovereign Identity Empowered Cyber Threat Information Sharing Platform<br>- Presented in 7th IEEE International Conference on Smart Computing(IEEE SmartComp 2021),- Siddhi - Blockchain and Self-Sovereign Identity Empowered Cyber Threat Information Sharing Platform- Presented in 7th IEEE International Conference on Smar...,https://www.youtube.com/watch?v=lzS49R52PwA,,Video,,,Implementation,,,,,,,,2021-08-11,,,,,,,,,,,,,
+DIDComm,Personal,,https://didcomm.org/shorten-url/1.0/,Timo Glastra,,,,,,Just got my first DIDComm protocol published on the https://didcomm.org website.,"A protocol to request a shortened URL for a given URL. For example, an agent requesting a shortened out of band invitation url from a mediator.",,https://twitter.com/TimoGlastra/status/1572976791136137216,,tweet,,,Implementation,,,,,,,,2022-08-22,,,,,,,,,,,,,
+DIDComm,DIF,,,,,,,,,DIDComm: ECDH-1PU Implementation,"In short, ECDH-1PU is a key derivation process that allows for sender authenticity and enables a “[Perfect Forward Secrecy](https://www.wired.com/2016/11/what-is-perfect-forward-secrecy/#:~:text=Perfect%20forward%20secrecy%20means%20that,of%20the%20user%27s%20sensitive%20data.)” mechanism, in addition to significant performance gains over JWS message nested in a JWE envelope, as used by existign ECDH-ES aproaches.","ECDH-1PU is a key derivation process that offers sender authenticity, as well as significant performance gains over existing ECDH-ES aproaches.",https://blog.identity.foundation/ecdh-1pu-implementation/,,Post,,,Implementation,,,,,,,,2021-09-21,,,,,,,,,,,,,
+DIDComm,Jolocom,,,,,,,,,Community matters: Jolocom’s latest contributions to DIF,"We at Jolocom strongly believe that DIDComm is a crucial infrastructure element for the broader and future-proof SSI stack, and [current work on DIDComm v2 includes Jolocom’s implementation of the specification](http://github.com/jolocom/didcomm-rs) with authcrypt (authenticated encrypted) and most of the low level of the protocol.",...Interested parties can already start building high-level verifiable credential-based services and workflows on the Rust KERI implementation.,https://jolocom.io/blog/jolocoms-contributions-to-dif/,https://jolocom.io/wp-content/uploads/2020/05/Jolocom-Logbook-DIF-contribution-cover-02-alt.jpg,Post,,,Implementation,,,,,,,,2021-01-19,,,,,,,,,,,,,
+mDL,INATBA,,,,,,,,,“Decentralised Identity: What’s at Stake?”,"Looking at the above comparison, It is clear that both approaches strive to maintain user control of their personal data, selective disclosure/data minimization, and cryptographic methods to prove the integrity of identity claims. The differences are: first in their reliance (mDL) or independence (SSI) from issuer involvement in verification interactions, and second in their cryptographic approach, where the mDL relies on externally provided cryptographic tools while SSI builds on holder controlled private keys",← earlier paper,https://inatba.org/wp-content/uploads/2020/11/2020-11-INATBA-Decentralised-Identity-001.pdf,,Post,,,Intro,,,,,,,,2021-11,,,,,,,,,,,,,
+mDL,SpruceID,,,,,,,,,An Identity Wallet Bill of Rights - Starting With the Mobile Driver License,"Spruce’s continued mission is to let users control their data across the web, whether it’s web2, web3, or beyond. This also applies to credentials issued by existing entities, such as the Mobile Driver License (mDL) issued by motor vehicle authorities across the world.","Spruce’s continued mission is to let users control their data across the web, whether it’s web2, web3, or beyond. This also applies to credentials issued by existing entities, such as the Mobile Driver License (mDL) issued by motor vehicle authorities across the world.",https://blog.spruceid.com/an-identity-wallet-bill-of-rights/,,Post,,,Intro,,,,,,,,2022-09-12,,,,,,,,,,,,,
+mDL,INATBA,,,,,,,,,​​Mobile Driver’s Licence (mDL) VS. Self-Sovereign Identity (SSI),"The ISO mDL specification (ISO-compliant Driving License or IDL)  is purpose driven, as its name implies, but is said to be specifically intended to:<br>* enable verifiers not affiliated with or associated with the issuing authority to gain access to and authenticate the information<br>* allow the holder of the driving license to decide what information to release to a verifier<br>* include the ability to update information frequently, and to authenticate information at a high level of confidence.",,https://inatba.org/identity/mobile-drivers-licence-mdl-self-sovereign-identity-ssi-comparison/,,Post,,,Main,,,,,,,,2020-11,,,,,,,,,,,,,
+mDL,CCG Mailing List,,https://w3c-ccg.github.io/vdl-test-suite/,Manu Sporny,"Spruce, MATTR, Digital Bazaar, ",,,,,Verifiable Driver's Licenses and ISO-18013-5 (mDL),"As some of you might be aware, ISO-18013-5 (mDL -- Mobile Driver's License) was published as a global ISO standard in September 2021. A number of us in the W3C CCG and W3C VCWG attempted to ensure that W3C Verifiable Credentials were supported by the mDL work, but that effort is not reflected in the finalized ISO mDL standard (and due to the way ISO operates, we are not at liberty to share any details). There have been increasing concerns related to the divergence of mDL with W3C Verifiable Credentials and to the market dynamics at play around mDL.",,https://lists.w3.org/Archives/Public/public-credentials/2021Nov/0105.html,,Discussion,,,Main,,,,,,,,2021-11-29,,,,,,,,,,,,,
+mDL,Procivis,,,,,,,,,ISO/IEC 18013-5 vs Self-Sovereign Identity: A proposal for an mDL Verifiable Credential,"in the context of government identity programs we see it as useful to compare them on the following parameters – background, credential data model & trust anchor and transmission protocols.",,https://www.procivis.ch/post/iso-iec-18013-5-vs-self-sovereign-identity-a-proposal-for-an-mdl-verifiable-credential,https://uploads-ssl.webflow.com/5fae427844470c4d4b49d62b/62440e2a85213a51704c8641_Picture%203.png,Post,,,Main,,,,,,,,2022-03-30,,,,,,,,,,,,,
+mDL,AAMVA,,,,,,,,,Mobile Driver's License (mDL) Implementation Guidelines 1.2,"The AAMVA Joint Mobile Driver’s License (mDL) Working Group (WG) has been active around mobile identification since 2012. As the mDL evolves, the mDL WG continues to identify and address topics on which guidance to Issuing Authorities can be helpful. This document represents the bulk of the current guidance, and points to additional resources as needed",,https://www.aamva.org/getmedia/b801da7b-5584-466c-8aeb-f230cef6dda5/mDL-Implementation-Guidelines-Version-1-2_final.pdf,,Report,,,Main,,,,,,,,2023-01,,,,,,,,,,,,,
+mDL,AAMVA,,,,,,,,,Mobile Driver's License Model Legislation,"The Mobile Driver’s License (mDL) Model Legislation has been developed to facilitate the uniformity of proposed legislative changes related to implementation of mDL in various jurisdictions. The model legislation is meant to demonstrate how the requirements in the ISO standards and AAMVA Mobile Driver’s License Implementation Guidelines could be represented in jurisdiction-specific legislation. Thus, the language contained in the model legislation is designed to offer examples and is not expected to be proposed to legislatures without consideration for controlling legal provisions in your jurisdiction",,https://www.aamva.org/getmedia/cb9fd6c7-29e6-48a4-926b-e16d6400eab5/mDL-Model-Legislation_final.pdf,,Report,,,Main,,,,,,,,2023-01,,,,,,,,,,,,,
+mDL,Kantara Initiative,,,,,,,,,Working Group for Privacy Enhancing Mobile Credentials,Clearly the use of a driver’s license goes well beyond proving eligibility to drive a vehicle. It has become the de-facto standard for proving that you are who you say you are – and are entitled to the product or service requested. An increasing number of states are adopting mobile ID systems to recognise and verify mobile credentials including driver’s licenses (mDL).,,https://kantarainitiative.org/introducing-kantaras-working-group-for-privacy-enhancing-mobile-credentials/,,Post,,,Guidance,,,,,,,,2021-11-15,,,,,,,,,,,,,
+mDL,Kantara Initiative,,,,,,,,,Kantara Releases Report on Identity and Privacy Protection For mobile Driver’s Licenses,The report outlines how to implement mDL systems as Privacy Enhancing Technologies. It provides guidance on protecting people’s individual privacy and the digital identifiers of an individual who carries or uses an mDL.,,https://kantarainitiative.org/kantara-releases-report-on-identity-and-privacy-protection-for-mobile-drivers-licenses/,,Post,,,Guidance,,,,,,,,2021-08-27,,,,,,,,,,,,,
+mDL,Biometric Update,,https://kantarainitiative.org/kantara-lays-out-trust-building-recommendations-for-mdls/,,,,,,,Kantara lays out trust-building recommendations for mDLs,"A global digital ID association has published steps vendors and others need to take in order to build effective mobile driving license services that also put ID holders in control of their identity. The Kantara Initiative’s report starts from the premise that trust in mobile driving licenses grows with the degree of control that license holders have over the documents, their privacy and their biometric identifiers.","Trust in mobile driving licenses grows with the degree of control that license holders have over the documents, their privacy and their biometric identifiers.",https://www.biometricupdate.com/202108/kantara-lays-out-trust-building-recommendations-for-mdls,,Post,,,Guidance,,,,,,,,2021-08-27,,,,,,,,,,,,,
+mDL,CCG,,,,,,,,,Verifiable Driver's License Interoperability Report 1.0,The purpose of this test suite is to demonstrate a path to interoperability between the ISO-18013-5 Mobile Driver's License data model and the W3C Verifiable Credentials ecosystem. The technologies explored in this test suite are experimental and meant to be complementary to ISO-18013-5 (mDL) and not a replacement of the standard. This document contains the most recent interoperability report between issuers and verifiers for Verifiable Driver's License Credentials using the Verifiable Driver's License Vocabulary. This report is generated on a weekly basis.,,https://w3c-ccg.github.io/vdl-test-suite/,,Report,,,Guidance,,,,,,,,2023-01-08,,,,,,,,,,,,,
+mDL,IETF,RFC 8943,,,,,,,,RFC 8943: Concise Binary Object Representation (CBOR) Tags for Date,"In CBOR, one point of extensibility is the definition of CBOR tags. RFC 7049 defines two tags for time: CBOR tag 0 (date/time string as per RFC 3339) and tag 1 (POSIX ""seconds since the epoch""). Since then, additional requirements have become known. This specification defines a CBOR tag for a date text string (as per RFC 3339) for applications needing a textual date representation within the Gregorian calendar without a time. It also defines a CBOR tag for days since the date 1970-01-01 in the Gregorian calendar for applications needing a numeric date representation without a time. This specification is the reference document for IANA registration of the CBOR tags defined.","The Concise Binary Object Representation (CBOR), as specified in RFC 7049, is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation.",https://www.rfc-editor.org/rfc/rfc8943,,rfc,,,CBOR,,,,,,,,2020-11,,,,,,,,,,,,,
+mDL,Personal,,https://www.rfc-editor.org/rfc/rfc8943,Mike Jones,,,,,,Concise Binary Object Representation (CBOR) Tags for Date is now RFC 8943,"The Concise Binary Object Representation (CBOR) Tags for Date specification has now been published as RFC 8943. In particular, the full-date tag requested for use by the ISO Mobile Driver’s License specification in the ISO/IEC JTC 1/SC 17 “Cards and security devices for personal identification” working group has been created by this RFC. The abstract of the RFC is:",Mike Jones shares that CBOR (Concise Binary Object Representation) is officially a specification at IETF. woohoo! and it is a key part of [ISO’s mDL standard](https://www.iso.org/committee/45144.html) (date fields must use it).,https://self-issued.info/?p=2136,,Post,,,CBOR,,,,,,,,2020-11-20,,,,,,,,,,,,,
+Exchange Protocols,IDCommons,,https://docs.google.com/document/d/1_b5MxzUPWzYxXxWt7Tw6-MySqh77ZvYHBnUgEBCFH7Q/edit,"Kaliya Young, Orie Steele, Drummond, Kyle, et al.",,,,,,"Figuring out Verifiable Credentials Exchange - combining Bloom, Aires Protocols, Presentation Exchange into a unified - Killer Whale Jello Salad",Important parts of the protocol - what format you want is in an attachment.<br>You can provide multiple attachments - request things in multiple formats<br>You have the option of responding in different formats.<br>Messages - that go back and forth and messages that respond with different formats. ,,"https://iiw.idcommons.net/22H/_Figuring_out_Verifiable_Credentials_Exchange_-_combining_Bloom,_Aires_Protocols,_Presentation_Exchange_into_a_unified_-_Killer_Whale_Jello_Salad",,Session Notes,,,Background,,,,,,,,2021-05-06,,,,,,,,,,,,,
+Exchange Protocols,IDCommons,,https://iiw.animo.id,,,,,,,BBS+ Credential Exchange in Hyperledger Aries,"19:18:25 From Sebastian Schmittner : Is there some working implementation out there to actually generate/work with these VCs shown currently?<br>19:18:58 From Troy Ronda : aries-framework-go is one of them.<br>19:19:24 From Karim Stekelenburg : The ACA-Py implementation will be merged in shortly<br>19:20:50 From Stephen Curran : PR: https://github.com/hyperledger/aries-cloudagent-python/pull/1061<br>19:22:02 From Sebastian Schmittner : awesome! We are doing some prototyping right now where we are using JSON-LD VCs with the americans, but, since we are also running a node in the HL Indy network of ID Union, it would be really great if we could bridge the Ocean here ;)",,https://iiw.idcommons.net/11E/_BBS+_Credential_Exchange_in_Hyperledger_Aries,,Session Notes,,,Background,,,,,,,,2021-05-06,,,,,,,,,,,,,
+Exchange Protocols,IDCommons,,,,,,,,,Credentials Exchange - figuring it out - (Jello Bowl Death Match?),"The ultimate goal is to get to a clear exchange protocols.<br><br>Also to have a paper similar to [this one](https://www.lfph.io/wp-content/uploads/2021/02/Verifiable-Credentials-Flavors-Explained.pdf) that outlines the choice landscape that is and points to a convergence point<br><br>Good Health Pass is literally right now trying to figure this out and will “pick” solutions it needs to get implementations working in the next 30-90 days and point the whole industry in one direction.<br><br>We started out with this framework of understanding<br><br>Contextualizing VC Exchange in Layers<br><br>Verifiable Credentials (VC or VCs) is one of the key standardized components of decentralized identity. [The VCs Data Model](https://www.w3.org/TR/vc-data-model/), defined at the W3C, is a universal data format that lets any entity express anything about another entity.  It provides a common mechanism for the interoperable implementation of digital credentials that are cryptographically secure, tamper-evident, privacy-respecting, and machine-verifiable.<br><br>There clarity emerging on standards that are interoperable with one another for the VC format.<br><br>There is less clarity on the Exchange mechanisms.<br><br>One way that has been proposed to look at the exchange options available is to see them in different layers.",,https://iiw.idcommons.net/12F/_Credentials_Exchange_-_figuring_it_out_-_(Jello_Bowl_Death_Match%3F)_%E2%80%93,,Session Notes,,,Background,,,,,,"DIDComm, Verifiable Credential Exchange, Aries Protocol, Bloom Protocol, Presentation Exchange",,2021-05-06,,,,,,,,,,,,,
+Exchange Protocols,CCG,,,Manu Sporny,,,,,,"chapi.io launches, includes VC playground","TL;DR: chapi.io is a site that helps developers integrate Verifiable Credential issuance, holding, and presentation into their applications. It includes a playground that can issue arbitrary VCs to digital wallets (web and native). It also includes tutorials on how Web Developers can add CHAPI integration to their websites. All you need to try it out is a web browser.",,https://lists.w3.org/Archives/Public/public-credentials/2022Jun/0055.html,,Discussion,,,CHAPI,,,,,,,,2022-06-27,,,,,,,,,,,,,
+Exchange Protocols,TrustBloc,,,,,,,,,TrustBloc - Duty Free Shop use case (CHAPI Save + WACI Share),This video demonstrates the TrustBloc platform to Issue a W3C Verifiable Credential through CHAPI and Share the Verifiable Credential/Presentation through WACI.,TrustBloc is an Open Source platform to build Digital Identity solutions. This video demonstrates the TrustBloc platform to Issue a W3C Verifiable Credential...,https://www.youtube.com/watch?v=aagFJBI1fBE,https://i.ytimg.com/vi/aagFJBI1fBE/maxresdefault.jpg?sqp=-oaymwEmCIAKENAF8quKqQMa8AEB-AHUBoAC4AOKAgwIABABGGAgTihlMA8=&rs=AOn4CLC_JUslbXvHG_E-z0e2u2iUa9Eu5A,Video,,,CHAPI,,,,,,,,2021-10-12,,,,,,,,,,,,,
+Exchange Protocols,CCG Mailing List,,,Joe Andrieu,,,,,,VC-API Diagram for today. Focus on CHAPI,We'll be discussing this on today's call.,,https://lists.w3.org/Archives/Public/public-credentials/2021Nov/0007.html,https://i.imgur.com/s1C2lA8.png,Discussion,,,CHAPI,,,,,,,,2021-11-02,,,,,,,,,,,,,
+Exchange Protocols,CCG Mailing List,,,Manu Sporny,,,,,,"chapi.io launches, includes VC playground","TL;DR: chapi.io is a site that helps developers integrate Verifiable Credential issuance, holding, and presentation into their applications. It includes a playground that can issue arbitrary VCs to digital wallets (web and native). It also includes tutorials on how Web Developers can add CHAPI integration to their websites. All you need to try it out is a web browser.",,https://lists.w3.org/Archives/Public/public-credentials/2022Jun/0055.html,,Discussion,,,CHAPI,,,,,,,,2022-06-27,,,,,,,,,,,,,
+Exchange Protocols,CCG Mailing List,,https://playground.chapi.io/issuer,Manu Sporny,,,,,,"chapi.io playground upgrades - credential selector, resident card",The credential selector is an icon-based selector for all the credentials that the chapi.io playground currently supports issuing. You can now click on an image of the credential you'd like to issue. [...] We have added a permanent resident card from the fictitious Government of Utopia to the list of credentials that can be issued. This credential uses the Citizenship Vocabulary [...] You can try both of these new features out in the playground,,https://lists.w3.org/Archives/Public/public-credentials/2022Jul/0111.html,https://lists.w3.org/Archives/Public/public-credentials/2022Jul/att-0111/03-chapi-prc-large.png,Discussion,,,CHAPI,,,,,,,,2022-07-27,,,,,,,,,,,,,
+Exchange Protocols,CCG Mailing List,,,Manu Sporny,,,,,,Jobs For The Future VC added to chapi.io playground,"TL;DR: In an attempt to support the current Jobs for the Future Plugfest, an Open Badge v3.0 example for an Academic Achievement has been added to the chapi.io playground. You can now see what a JFF badge issuance and transfer to a Holder wallet looks like in CHAPI (on mobile and web, on any device that can run a web browser). Images of the flow are attached.",,https://lists.w3.org/Archives/Public/public-credentials/2022Jul/0031.html,https://lists.w3.org/Archives/Public/public-credentials/2022Jul/att-0031/chapi.io-jff-1.png,Discussion,,,CHAPI,,,,,,,,2022-07-13,,,,,,,,,,,,,
+Exchange Protocols,CCG,,https://github.com/w3c-ccg/vc-api/,,,,,,,Verifiable Credentials API v0.3,"The W3C Credentials Community Group Verifiable Credential APIs are a set of RESTful API definitions conforming with the OpenAPI 3.0 Specification that support Verifiable Credential Lifecycle Management such as Issuing, Holding/Presentation/Exchange, and Verification for the roles of Issuer, Holder, and Verifier as described in the Verifiable Credential Data Model specification.",,https://w3c-ccg.github.io/vc-api/,https://w3c-ccg.github.io/vc-api/diagrams/components.svg,Specification,,,VC Api,,,,,,,,2023-04-20,,,,,,,,,,,,,
+Exchange Protocols,CCG,,,,,,,,,Test Interoperability Report for Verifiable Credentials API Issuer,This is a test suite to demonstrate interoperability of issuers using the VC HTTP API.,,https://w3c-ccg.github.io/vc-api-issuer-test-suite/,,Report,,,VC Api,,,,,,,,2023-05-28,,,,,,,,,,,,,
+Exchange Protocols,CCG,,,,,,,,,VC API Verifier Interoperability Report 1.0,This test suite demonstrates the interoperability of verifiers using the VC HTTP API.,,https://w3c-ccg.github.io/vc-api-verifier-test-suite/,,Report,,,VC Api,,,,,,,,2023-05-28,,,,,,,,,,,,,
+Exchange Protocols,CCG,,,,,,,,,Ed25519Signature 2020 Interoperability Report 1.0,The purpose of this test suite is to demonstrate a path to interoperability for the Ed25519 Signature 2020. The technologies explored in this test suite are experimental. This document contains the most recent interoperability report for Ed25519 Signature 2020.,,https://w3c-ccg.github.io/di-ed25519-test-suite/,,Report,,,VC Api,,,,,,,,2023-05-28,,,,,,,,,,,,,
+Exchange Protocols,CCG,,,,,,,,,Status List 2021 Interoperability Report 1.0,The purpose of this test suite is to demonstrate a path to interoperability for StatusList2021 .,,https://w3c-ccg.github.io/status-list-2021-test-suite/,,Report,,,VC Api,,,,,,,,2023-05-28,,,,,,,,,,,,,
+Exchange Protocols,IDCommons,,https://w3c-ccg.github.io/meetings/2021-04-22-vchttpapi/,Dmitri Zagidulin,,,,,IIW,"13E/ VC-HTTP-API discussion -FAQ, vs other APIs, etc-",We are going to go through the API and address the challenges... currently only have a YAML file and missing a lot of other documentation. We are going to address these issues with the goal of concrete proposals the community can provide feedback on.,,"https://iiw.idcommons.net/13E/_VC-HTTP-API_discussion_-FAQ,_vs_other_APIs,_etc-",,Session Notes,,,VC Api,,,,,,,,2023-05-21,,,,,,,,,,,,,
+Exchange Protocols,CCG,,,,,,,,,VC HTTP API Special Topic Call,- VC HTTP API Proposals Under Consideration<br>- Use Cases Document<br>- Scope of VC HTTP API<br>- VC HTTP API Specification Structure,,https://w3c-ccg.github.io/meetings/2021-04-22-vchttpapi/,,minutes,,,VC Api,,,,,,,,2021-04-22,,,,,,,,,,,,,
+Exchange Protocols,DIF,,,,Bloom,,,,,Wallet And Credential Interactions,There are interactions between a wallet and relying party that require passing information between the two. WACI provides a standard for these interactions.,,https://identity.foundation/wallet-and-credential-interactions/,https://identity.foundation/wallet-and-credential-interactions/resources/qr.png,Specification,,,WACI,,,,,,,,2022-03-16,https://github.com/decentralized-identity/wallet-and-credential-interactions,,,,,,,,,,,,
+Exchange Protocols,Bloom,,https://iiw.idcommons.net/4K/_Introducing:_WACI_(Wallet_And_Credential_Interaction),,,,,,IIW32,Bloom donates WACI to the Decentralized Identity Foundation (DIF),"WACI was introduced at the annual IIW32 Workshop  with a very warm response. Its goal is to specify how interactions between a wallet and Relying Party (RP) such as an issuer or a verifier happen. At its core, WACI is a handshake of JWTs, where the RP signs a JWT that is given to the wallet, and the wallet signs another JWT containing the initial token as a ""challenge"" claim. This allows the wallet to prove ownership of its DID.<br><br>The easiest way to see the benefit of WACI is to offer a way to log into an application without a password with Verified Credential (VC) based authentication that cannot be faked.",,https://bloom.co/blog/waci-donation/,,Post,,,WACI,,,,,,,,2021-06-21,,,,,,,,,,,,,
+Exchange Protocols,DIF,,https://github.com/decentralized-identity/waci-didcomm,,,,,,,Wallet And Credential Interactions for DIDComm,"This document describes an interoperability profile which incorporates elements from a number of existing specifications and protocols, without assuming or requiring an implementer to understand all of them. It inherits its overall structure from the current pre-draft of WACI, but makes use of elements from the DIDComm v2.0 messaging protocol, along with Aries Present Proof message formats and DIF Presentation Exchange data objects. This version of the specification also restricts itself to Verifiable Credentials that make use of the JsonWebSignature2020 signature suite and Ed25519Signature2018 signature suite.",,https://identity.foundation/waci-didcomm/,https://identity.foundation/waci-didcomm/resources/swimlanes_io_d_C5HnpvA4f.png,Specification,,,WACI,,,,,,,,2023-01-16,https://github.com/decentralized-identity/waci-didcomm,,,,,,,,,,,,
+Exchange Protocols,DIF,,https://identity.foundation/presentation-exchange/,,,,,,,Presentation Exchange,"A common activity between peers in identity systems that feature the ability to generate self-asserted and third-party issued Claims is the demand and submission of proofs from a Holder to a Verifier. This flow implicitly requires the Holder and Verifier have a mechanism to facilitate the two primary steps in a proving exchange: a way for Verifiers to describe proof requirements, and for Holders to describe submissions of proof which align with those requirements.",,https://identity.foundation/presentation-exchange/,,Specification,,,Message Format,,,,,,,,2023-03-31,https://github.com/decentralized-identity/presentation-exchange,,,,,,,,,,,,
+Exchange Protocols,DIF,,,,,,,,,Credential Manifest,"For User Agents (e.g. wallets) and other service that wish to engage with Issuers to acquire credentials, there must exist a mechanism for negotiating (via services and interfaces that are out of scope) what inputs are required from a Subject to process a request for credential(s) issuance. The Credential Manifest is a common data format for describing the inputs a Subject must provide to an Issuer for subsequent evaluation and issuance of the credential(s) indicated in the Credential Manifest, i.e. for a Subject to become a Holder.",,https://identity.foundation/credential-manifest/,,Specification,Editor’s Draft,,Message Format,,,,,,,,2023-05-04,https://github.com/decentralized-identity/credential-manifest,,,,,,,,,,,,
+Exchange Protocols,Hyperledger,,,,,,,,,Negotiate Proof,"After an issuer has completed the ""Save Schema and Cred Def"" and ""Issue Credential"" how-tos, you have all the context for a credential holder and a relying party (verifier) to generate a zero-knowledge proof based on the credential.",,https://hyperledger-indy.readthedocs.io/projects/sdk/en/latest/docs/how-tos/negotiate-proof/README.html,https://hyperledger-indy.readthedocs.io/projects/sdk/en/latest/_images/3-phases.png,docs,,,Assorted,,,,,,,,2018,,,,,,,,,,,,,
+Exchange Protocols,Hyperledger,,,,,,,,,Aries RFC 0023: DID Exchange Protocol 1.0,This RFC describes the protocol to exchange DIDs between agents when establishing a DID based relationship.<br><br>Aries agent developers want to create agents that are able to establish relationships with each other and exchange secure information using keys and endpoints in DID Documents. For this to happen there must be a clear protocol to exchange DIDs.,,https://github.com/hyperledger/aries-rfcs/blob/main/features/0023-did-exchange/README.md,,rfc,,,Assorted,,,,,,,,2021-04-15,,,,,,,,,,,,,
+Exchange Protocols,IDCommons,,,Paul Knowles,,,,,IIW,Dynamic Data Sharing Hub: A target component for criteria searches on distributed structured data,"Dynamic Data Economy is a roadmap towards fair, decentralized and authentic data economy. Many times people are referring to blockchain technology as a revolution within digital space. But often they actually mean something more profound: the promise of Decentralisation brought by blockchain. A Dynamic Data Economy brings decentralization outside the technology realm into digital solutions for any economic actors. It does so by decentralizing all layers of the ecosystem:",,"https://iiw.idcommons.net/10L/_Dynamic_Data_Economy:_Digital_Identity,_Authentic_Data_Flows,_Data_Mesh_and_other_dragons",,Session Notes,,,Assorted,,,,,,,,2021-05-07,,,,,,,,,,,,,
+Exchange Protocols,SSI Orbit,,,,,,,,,#6 - The Importance of Data Inputs and Semantics for SSI with Paul Knowles from Human Colossus Foundation,"In terms of decentralized data initiatives, Paul is the innovation lead behind the Master Mouse Model (MMM), a conceptual model for a Dynamic Data Economy (DDE) – a safe and secure data sharing economy. He is also the inventor of the Overlays Capture Architecture (OCA) and the main spearhead behind the Blinding Identity Taxonomy (BIT), both of which facilitate a unified data language so that harmonized data can be utilized by dynamic data sharing hubs for improved data science, statistics, analytics and other meaningful services.","In today’s episode, I talk about the importance of data inputs and semantics with joined by Paul Knowles, an individual who defines himself as a semantic nerd.",https://podcasters.spotify.com/pod/show/ssi-orbit-podcast/episodes/6---The-Importance-of-Data-Inputs-and-Semantics-for-SSI-with-Paul-Knowles-from-Human-Colossus-Foundation-etvm5p,,episode,,,Assorted,,,,,,,,2023-05-17,,,,,,,,,,,,,
+Exchange Protocols,Human Colossus Foundation,,,,,,,,,Dynamic Data Sharing Hub - DDSH - Patient Recruitment Use Case,"Purpose-based Service Providers<br>• A company's ""why"" is a collective sense of purpose that reflects the company's merit, trustworthiness, and authenticity. It is the feeling the company wants their customers to experience when they engage with proprietary products and services – the identity that their customers want to align with.<br>• Establishing authentic communication channels in a peer-to-peer networking environment provides the basis to initiate transaction flows for consented data capture and data sharing between an organisation and the data subject (or a delegate/guardian acting on behalf of the data subject).<br>• The initial point of new data entry into a decentralised data ecosystem.<br><br>Insight Based Service Providers<br>• The value of data insights is not only to learn and enable validated decision-making, but also to make everybody in the company’s ecosystem ‘move’ in the same direction. As today’s world is volatile, uncertain, complex and ambiguous, insights need to be generated continuously rather than once in a while.<br>• Data insights gained from analysing sets of information that pertain to a given topic (or situation) enables businesses to make better-informed decisions, reducing the risk that comes with trial-and-error testing methods. Semantic harmonisation enables criteria searches on structured data from multiple sources, providing the basis to initiate a transaction flow for consented data access between the requesting party and the data governance authority (acting on behalf of consenting data subjects).<br>• Searching for existing data in a decentralised data ecosystem.",,https://drive.google.com/file/d/1TSfpysHy-UN9GnAiNPB81ZgGQaFCFcjo/view?usp=sharing,,Presentation,,,Assorted,,,,,,,,2023-05-18,,,,,,,,,,,,,
+OpenID Connect,OpenID,,,,,,,,,OpenID Connect,"OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol. It allows 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.",,https://openid.net/connect/,https://openid.net/wp-content/uploads/2023/05/openid-connect-digram-red.png,page,,,Main,,,,,,,,2014-02-04,,,,,,,,,,,,,
+OpenID Connect,OpenID,,,,,,,,,Frequently Asked Questions,"OpenID Connect lets developers authenticate their users across websites and apps without having to own and manage password files. For the app builder, it provides a secure verifiable, answer to the question: “What is the identity of the person currently using the browser or native app that is connected to me?”",,https://openid.net/connect/faq/,,faq,,,Main,,,,,,,,2014-02-20,,,,,,,,,,,,,
+OpenID Connect,OpenID,,,,,,,,,OpenID Certification Program,OpenID Certified markThe OpenID Foundation enables deployments of OpenID Connect and the Financial-grade API (FAPI) Read/Write Profile to be certified to specific conformance profiles to promote interoperability among implementations. The OpenID Foundation’s certification process utilizes self-certification and conformance test suites developed by the Foundation. Certified implementations can use the “OpenID Certified” certification mark.,,https://openid.net/certification/,,page,,,Main,,,,,,,,2015-02-18,,,,,,,,,,,,,
+OpenID Connect,Personal,,,Kim D Hamilton,,,,,,I've read every decentralized identity protocol so you don't have to,"They all just read like ""nothing to see here, just f- right off"" Oh, except for OIDC Credential Provider. Well done to them!",,https://twitter.com/kimdhamilton/status/1397241823190523904,,tweet,,,About,,,,,,,,2021-05-25,,,,,,,,,,,,,
+OpenID Connect,Self Issued,,,Mike Jones,,,,,,OpenID Connect Presentation at IIW XXXII,"If you have an Android phone or log in at Apple, AOL, Deutsche Telekom, Google, KDDI, Microsoft, NEC, NTT, Salesforce, Softbank, Symantec, Verizon, or Yahoo! Japan, you’re already using OpenID Connect – Many other sites and apps large and small also use OpenID Connect",* Introduction to OpenID Connect [(PowerPoint)](https://self-issued.info/presentations/OpenID_Connect_Introduction_12-Oct-21.pptx) [(PDF)](https://self-issued.info/presentations/OpenID_Connect_Introduction_12-Oct-21.pdf)<br><br>The session was well attended. There was a good discussion about the use of passwordless authentication with OpenID Connect.,https://self-issued.info/?p=2167,,Presentation,,,About,,,,,,,,2021-04-21,,,,,,,,,,,,,
+OpenID Connect,Self Issued,,,Mike Jones,,,,,,OpenID Presentations at December 2021 OpenID Virtual Workshop,* OpenID Connect Working Group [(PowerPoint)](http://self-issued.info/presentations/OpenID_Connect_Working_Group_9-Dec-21.pptx) [(PDF)](http://self-issued.info/presentations/OpenID_Connect_Working_Group_9-Dec-21.pdf)<br>* OpenID Enhanced Authentication Profile (EAP) Working Group [(PowerPoint)](http://self-issued.info/presentations/OpenID_EAP_Working_Group_9-Dec-21.pptx) [(PDF)](http://self-issued.info/presentations/OpenID_EAP_Working_Group_9-Dec-21.pdf)<br><br>use of IETF Token Binding specifications with OpenID Connect and integration with FIDO relying parties and/or other strong authentication technologies.”,,https://self-issued.info/?p=2214,,Presentation,,,About,,,,,,,,2021-12-09,,,,,,,,,,,,,
+OpenID Connect,Ubisecure,,,Francesca Hobson,,,,,,"Let’s talk about digital identity with Oscar Santolalla, Nat Sakimura and Petteri Stenius","the history of OpenID Connect and how it became so prevalent, with special guests [Nat Sakimura](https://www.linkedin.com/in/natsakimura/), Chairman at the OpenID Foundation, and [Petteri Stenius](https://www.linkedin.com/in/petteri-stenius-6a637/), Principal Scientist at Ubisecure. [...] “New technology seldomly completely replaces the older technologies. They will form additional layers, and slowly start replacing it.”","Oscar explores the history of OpenID Connect and how it became so prevalent, with special guests Nat Sakimura and Petteri Stenius.",https://www.ubisecure.com/podcast/openid-connect/,,episode,,,About,,,,,,,,2021-11-03,,,,,,,,,,,,,
+OpenID Connect,Ubisecure,,,Petteri Stenius,,,,,,"Differences between SAML, OAuth & OIDC (OpenID Connect)",This article is an update to the popular Difference between SAML and OAuth blog post we published in 2017. This blog expands to cover OpenID Connect (OIDC) vs OAuth 2.0 vs SAML 2.0 (Security Assertion Markup Language).,OpenID Connect (OIDC) vs OAuth 2.0 vs SAML. Learn the technical differences between the protocols. Help determine the most suitable protocol for your requirements.,https://www.ubisecure.com/education/differences-between-saml-oauth-openid-connect/,,Post,,,About,,,,,,,,2020-08-10,,,,,,,,,,,,,
+OpenID Connect,Identiverse,,,"Preeti Rastogi, Nat Sakimura",,,,,Identiverse,Distributed Open Identity: Self-Sovereign OpenID: A Status Report,This session will provide an overview of the development since then and brings the audience up-to-speed on what is happening in the space including Demo of such implementations. It is a follow up of the Identiverse 2019 session “SSO: Self-sovereign OpenID Connect – a ToDo list”.,,https://identiverse.gallery.video/detail/videos/standards/video/6184823227001/distributed-open-identity:-self-sovereign-openid:-a-status-report?autoStart=true,,Video,,,About,,,,,,,,2020-08-26,,,,,,,,,,,,,
+OpenID Connect,OpenID Japan,,,,OpenID,,,,,Personal Digital Transformation and Holistic Digital Identity,"from the OpenID Summit Tokyo 2020 Keynote […] about Claims, Identity, Self-ness, Who-ness, and OpenID Connect and Decentralized Identity.","This probably is the last speech that Kim Cameron, the author of the Laws of Identity, gave in front of a large audience in person. It is from the OpenID Sum...",https://www.youtube.com/watch?v=9DExNTY3QAk,https://i.ytimg.com/vi/9DExNTY3QAk/hqdefault.jpg,Video,,,About,,,,,,,,2021-12-03,,,,,,,,,,,,,
+OpenID Connect,personal,,,Nat Sakimura,,,,,,Announcing GAIN: Global Assured Identity Network,"All business entities in the network are vetted as part of the creation and maintenance of their business accounts at their hosting organization, and they cannot remain anonymous. They will be accountable. As a result, the consumer has the assurance that they will be safe to transact with them—meaning more business for the Relying Parties. All of the good actors benefit.",One key benefit of the approach proposed in the white paper is that the standards required to enable this network already exist: OpenID Connect and eKYC/IDA.,https://nat.sakimura.org/2021/09/14/announcing-gain/,,Post,,,Organization,,,,,,,,2021-09-14,,,,,,,,,,,,,
+OpenID Connect,DIF,,,,,,,,,DIF and OIDF cooperation,"to work together on areas of mutual interest, allowing working groups to align and coordinate through dual-members. The first major collaboration, which has already been underway for weeks, is a process for revising the Self-Issued OpenID Connect (SIOP) chapter of the OpenID Connect (OIDC) specification",DIF is proud to announce that it has entered into a liaison agreement with the OpenID Foundation (OIDF). This provides a mechanism for both parties to work together on areas of mutual interest…,https://medium.com/decentralized-identity/dif-oidf-9753b9bd0093,,Post,,,Organization,,,,,,,,2020-11-09,,,,,,,,,,,,,
+OpenID Connect,OpenID,ABConnectWG,,,,,,,,A/B Connect Working Group,"OpenID Connect performs many of the same tasks as OpenID 2.0, but does so in a way that is API-friendly. OpenID Connect can also be extended to include more robust mechanisms for signing and encryption. Integration of OAuth 1.0a and OpenID 2.0 required an extension (called the OpenID/OAuth hybrid); in OpenID Connect, OAuth 2.0 capability is built into the protocol itself.",,https://openid.net/wg/connect/,,Working Group,,,Working Group,,,,,,,,2015-02-18,,,,,,,,,,,,,
+OpenID Connect,OpenID,ABConnectWG,,,,,,,,Certified OpenID Connect Implementations Featured for Developers,"OpenID Certified markThe following OpenID Connect Implementations have attained OpenID Certification for one or more certification profiles, including an authentication profile. Their certifications are listed at https://openid.net/certification/.",,https://openid.net/developers/certified/,,page,,,Working Group,,,,,,,,2017-02-11,,,,,,,,,,,,,
+OpenID Connect,OpenID,ABConnectWG,,,,,,,,​​First Implementer’s Drafts of OpenID Connect SIOPV2 and OIDC4VP Specifications Approved,- Self-Issued OpenID Provider v2<br>- OpenID Connect for Verifiable Presentations<br>An Implementer’s Draft is a stable version of a specification providing intellectual property protections to implementers of the specification. These are the first Implementer’s Drafts of these specifications. These specifications are products of the OpenID Connect Working group,,https://openid.net/2022/02/08/first-implementers-drafts-of-openid-connect-siopv2-and-oidc4vp-specifications-approved/,,Post,,,Working Group,,,,,,,,2022-02-08,,,,,,,,,,,,,
+OpenID Connect,OpenID,ABConnectWG,,Rodriguez Fernandez,,,,,,OpenID Connect Client-Initiated Backchannel Authentication Flow – Core 1.0,"OpenID Connect Client Initiated Backchannel Authentication Flow is an authentication flow like OpenID Connect. However, unlike OpenID Connect, there is direct Relying Party to OpenID Provider communication without redirects through the user's browser. This specification has the concept of a Consumption Device (on which the user interacts with the Relying Party) and an Authentication Device (on which the user authenticates with the OpenID Provider and grants consent). This specification allows a Relying Party that has an identifier for a user to obtain tokens from the OpenID Provider. The user starts the flow with the Relying Party at the Consumption Device, but authenticates and grants consent on the Authentication Device",,https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0.html,,Specification,,,Working Group,,,,,,,,2021-08-01,,,,,,,,,,,,,
+OpenID Connect,OpenID,ABConnectWG,,Oliver Terbu,,,,,,OpenID Connect for Verifiable Presentations,This specification defines an extension of OpenID Connect to allow presentation of claims in the form of W3C Verifiable Credentials as part of the protocol flow in addition to claims provided in the id_token and/or via UserInfo responses.,,https://openid.net/specs/openid-connect-4-verifiable-presentations-1_0-08.html,,Specification,,,Working Group,,,,,,,,2022-01-28,,,,,,,,,,,,,
+OpenID Connect,OpenID,ABConnectWG,,Kristina Yasuda,,,,,,Self-Issued OpenID Provider v2,"This specification extends OpenID Connect with the concept of a Self-Issued OpenID Provider (Self-Issued OP), an OP which is within the End-User's local control. End-Users can leverage Self-Issued OPs to authenticate themselves and present claims directly to the RPs. This allows users to interact with RPs directly, without relying on third-party providers or requiring the End-User to operate their own hosted OP infrastructure.",,https://openid.net/specs/openid-connect-self-issued-v2-1_0-07.html,,Specification,,,Working Group,,,,,,,,2022-01-28,,,,,,,,,,,,,
+OpenID Connect,OpenID,ABConnectWG,,,,,,,,OpenID Connect for Identity Assurance 1.0,"This specification defines an extension to OpenID Connect [OpenID] for providing Relying Parties with identity information, i.e., Verified Claims, along with an explicit statement about the verification status of these Claims (what, how, when, according to what rules, using what evidence). This specification is aimed at enabling use cases requiring strong assurance, for example, to comply with regulatory requirements such as Anti-Money Laundering laws or access to health data, risk mitigation, or fraud prevention.",,https://openid.net/specs/openid-connect-4-identity-assurance-1_0.html,,Specification,,,Working Group,,,,,,,,2022-08-19,,,,,,,,,,,,,
+OpenID Connect,OpenID,ABConnectWG,,,,,,,,OpenID Connect for Identity Assurance – Overview & Call to Action,"OpenID Connect for Identity Assurance is primarily focussed on addressing use-cases where the details of the assurance process used to verify and validate the end-users identity need to be explicitly communicated.<br><br>The working group believes it’s a good fit for account opening, staff on-boarding, account recovery and access to restricted services where communication of how the underlying identity was established is needed.",,https://openid.net/oidc4ida-overview-call-to-action/,,Post,,,Working Group,,,,,,,,2022-08-25,,,,,,,,,,,,,
+OpenID Connect,OpenID,ABConnectWG,,,,,,,,OpenID Connect Extended Authentication Profile (EAP) ACR Values 1.0,"This specification enables OpenID Connect Relying Parties to request that specific authentication context classes be applied to authentications performed and for OpenID Providers to inform Relying Parties whether these requests were satisfied. Specifically, an authentication context class reference value is defined that requests that phishing-resistant authentication be performed and another is defined that requests that phishing-resistant authentication with a hardware-protected key be performed. These policies can be satisfied, for instance, by using W3C scoped credentials or FIDO authenticators. ",,https://openid.net/specs/openid-connect-eap-acr-values-1_0-01.html,,Specification,,,Working Group,,,,,,,,2021-10-03,,,,,,,,,,,,,
+OpenID Connect,Self Issued,,,Mike Jones,,,,,,The OpenID Connect Logout specifications are now Final Specifications,The OpenID Connect Logout specifications are now Final Specifications<br>Thanks to all who helped us reach this important milestone! This was originally [announced on the OpenID blog](https://openid.net/2022/09/12/the-openid-connect-logout-specifications-are-now-final-specifications/).,,https://self-issued.info/?p=2298,,Post,,,Working Group,,,,,,,,2022-09-27,,,,,,,,,,,,,
+OpenID Connect,IDCommons,,,"Oliver Terbu, Torsten Lodderstedt, Kristina Yasuda, Adam Lemmon, Tobias Looker",,,,,IIW,Use-cases: OIDC for Verifiable Credentials - How do you want to use Identity Provider you control?,"We talk about users controlling their own identities, but what does it really mean in “real-life”?<br><br>For example, in OpenID Connect, what are the real-life use-cases and concrete needs to move from Identity Providers offered by Identity Companies to users controlling their own Identity Provider",,https://iiw.idcommons.net/12G/_Use-cases:_OIDC_for_Verifiable_Credentials_-_How_do_you_want_to_use_Identity_Provider_you_control%3F,,Session Notes,,,Verifiable Credentials,,,,,,,,2021-05-07,,,,,,,,,,,,,
+OpenID Connect,IDCommons,,https://www.slideshare.net/TorstenLodderstedt/openid-connect-for-w3c-verifiable-credential-objects,"Oliver Terbu, Torsten Lodderstedt, Kristina Yasuda, Adam Lemmon, Tobias Looker",,,,,IIW,OpenID Connect for W3C Verifiable Credential Objects,Have been incubated in OpenID Foundation and DIF’s joint Self-Issued OpenID Provider WG - contact Kristina ([kristina.yasuda@microsoft.com](mailto:kristina.yasuda@microsoft.com) for participation details),,https://iiw.idcommons.net/2F/_OpenID_Connect_for_W3C_Verifiable_Credential_Objects,,Session Notes,,,Verifiable Credentials,,,,,,,,2021-05-06,,,,,,,,,,,,,
+OpenID Connect,IDCommons,,https://docs.google.com/presentation/d/1w-rmwZoLiFWczJ4chXuxhY0OsgHQmlIimS2TNlce4UU/edit?usp=sharing,"Nat Sakimura, Edmund Jay, Kristina Yasuda",,,,,IIW,OpenID Connect Claims Aggregation,This session discussed how OIDC Claims Aggregation Draft solves certain problems left open in Connect-Core: 1/ How to get a token from CP is hand-wavy; 2/ No specified method to down scope the userinfo of the CP; 3/ No way to provide a binding information between CP:sub and IdP:sub.,,https://iiw.idcommons.net/5B/_OpenID_Connect_Claims_Aggregation,,Session Notes,,,Verifiable Credentials,,,,,,,,2021-05-06,,,,,,,,,,,,,
+OpenID Connect,Chakaray,,,,,,,,,The Era of Self-Sovereign Identity,"VC-AuthN OIDC uses the OpenID connect standards to easily integrate with the supported systems and also provides a way to authenticate using the verifiable credentials, giving the control back to the user. This is similar to the traditional OpenID connect, the only difference is in the token information. Rather than using the user’s information to construct the token, this uses claims in the verifiable credentials presented by the user.",Discover how to make digitization more secure and reliable with Self-Sovereign Identity and the reasons why we should switch to it.,https://www.chakray.com/era-self-sovereign-identity/,,Post,,,Verifiable Credentials,,,,,,,,2020-12-01,,,,,,,,,,,,,
+OpenID Connect,Personal,,,Pranav Kirtani,,,,,,How a combination of Federated identity and Verifiable Credentials can help with Customer onboarding,"Before we dive into how Federated systems like OIDC and SAML along with Verifiable Credentials (VC) can help improve customer onboarding to your application, let us first understand what are the current methods being used for onboarding.",,https://pranavkirtani.medium.com/how-a-combination-of-federated-identity-and-verifiable-credentials-can-help-with-customer-7e6518feb018,https://miro.medium.com/v2/resize:fit:1200/0*ENXUBvSdImT5qL_f,Post,,,Verifiable Credentials,,,,,,,,2021-07-18,,,,,,,,,,,,,
+OpenID Connect,personal,,,Kristina Yasuda,,,,,IIW,SIOP Use-cases - IIW Spring 2021,"* Continuity of a service<br>* Offline Authentication<br>* Speed, reduced latency<br>* Choice, Portability<br>* Privacy",,https://docs.google.com/presentation/d/1a0C4HvVYwwwDqSw3tgPNhy9Iqyufy9oZdnMgl7rQ9Vc/edit#slide=id.p,,Presentation,,,Verifiable Credentials,,,,,,,,2021,,,,,,,,,,,,,
+OpenID Connect,Sphereon,,,,,,,,,OIDC with SIOPv2 and DIF Presentation Exchange,"I gave the following presentation on the [OpenID Connect Working Group](https://openid.net/wg/connect/) during the [September 13, 2021 OpenID Workshop](https://openid.net/oidf-workshop-at-eic-2021-monday-september-13-2021/) at the [2021 European Identity and Cloud (EIC) conference](https://www.kuppingercole.com/events/eic2021/). As I noted during the talk, this is an exciting time for OpenID Connect; there’s more happening now than at any time since the original OpenID Connect specs were created!",A demo of our implementation of OpenID Connect with SIOPv2 and the DIF Presentation Exchange.,https://vimeo.com/630104529,https://i.vimeocdn.com/video/1272386756-4e38e1ea6118fd8ea001cdb8650e7a2fe6a135a8768e6af6c,Video,,,Verifiable Credentials,,,,,,,,2021-10-12,,,,,,,,,,,,,
+OpenID Connect,personal,,,Phil Windley,,,,,,Using OpenID4VC for Credential Exchange; Technometria - Issue #62,Extending OAuth and OIDC to support the issuance and presentation of verifiable credentials provides for richer interactions than merely supporting authentication. All the use cases we’ve identified for verifiable credentials are available in OpenID4VC as well.,"Verifiable credentials have transport options other than DIDComm. In this post, I explore the OpenID4VC specification which allows credentials to be used in the OpenID ecosystem.",https://www.windley.com/archives/2022/10/using_openid4vc_for_credential_exchange.shtml,https://www.windley.com/archives/2022/10/openid-log.png,Post,,,Verifiable Credentials,,,,,,,,2022-10-11,,,,,,,,,,,,,
+OpenID Connect,IDCommons,,https://docs.google.com/presentation/d/1OaMecHecTUexv1skJZoYzJoHKYH8H03REFpFstLRjPg/edit?ts=607b7e5d#slide=id.gd2c45a9dcd_7_21,Tom Jones,,,,,IIW,DID chooser for SIOP,Goal is to allow folks to pick their DID they want to use for a website.<br><br>“Subject choosing which DID to present”,,https://iiw.idcommons.net/20A/_DID_chooser_for_SIOP,,Session Notes,,,Verifiable Credentials,,,,,,,,2021-05-06,,,,,,,,,,,,,
+OpenID Connect,IDCommons,,https://www.slideshare.net/TorstenLodderstedt/openid-connect-4-identity-assurance-at-iiw-32](https://www.slideshare.net/TorstenLodderstedt/openid-connect-4-identity-assurance-at-iiw-32),Torsten Lodderstedt,,,,,IIW,OpenID Connect 4 Identity Assurance,Jacob Dilles proposed to allow RPs to use handles for pre-configured eKYC requests. I filled an issue for discussion by the WG ([https://bitbucket.org/openid/ekyc-ida/issues/1245/pre-configured-claims-ekyc-requests](https://bitbucket.org/openid/ekyc-ida/issues/1245/pre-configured-claims-ekyc-requests).,,https://iiw.idcommons.net/10J/_OpenID_Connect_4_Identity_Assurance,,Session Notes,,,Development,,,,,,,,2021-05-06,,,,,,,,,,,,,
+OpenID Connect,IDCommons,,,David Waite,,,,,IIW,OpenID Connect: Session Management vs Privacy,"To recap:<br>* Front-channel logout is simple<br>* …but brittle and doesn’t give good security guarantees<br>* Back-channel logout is robust<br>* …but difficult to implement/support, can still miss signals<br>* Session Management is useful for some apps<br>* …but is broken in many browsers<br>On their own independent schedules, all browsers have either broken or have plans to break state sharing via cross-site iframes to limit user tracking - arguably making the Session Management approach unusable.",,https://iiw.idcommons.net/11M/_OpenID_Connect:_Session_Management_vs_Privacy,,Session Notes,,,Development,,,,,,,,2021-05-06,,,,,,,,,,,,,
+OpenID Connect,Auth0,,,,,,,,,"Identity, Unlocked... SIOP with Kristina Yasuda","As a discovery mechanism to invoke a Self-Issued OP, the discussion on the podcast covered the usage of a custom schema 'openid://'. Alternative mechanisms to address the limitations of custom schemas are being actively explored in the WG.<br><br>The conversation meanders through deeper details, from how the current [SIOP specification draft](https://bitbucket.org/openid/connect/src/master/openid-connect-self-issued-v2-1_0.md) under the OpenID Foundation picks up the mission from a [former attempt under DIF](https://identity.foundation/did-siop/) to encoding approaches for verifiable presentations (embedding in JWTs, [LD proofs](https://w3c-ccg.github.io/ld-proofs/), how to represent attributes",,https://auth0.com/blog/identity-unlocked-explained-season-2-ep-5/,,episode,,,Development,,,,,,,,2021-03-22,,,,,,,,,,,,,
+OpenID Connect,SpruceID,,https://blog.spruceid.com/sign-in-with-ethereum-decentralizing-an-identity-provider-server/,,,,,,,Spruce Developer Update #20,We've set up a [release pipeline](https://github.com/spruceid/ens-oidc/) and had our first witnessed deployment for the ENS Community-Maintained OIDC IdP,,https://blog.spruceid.com/spruce-developer-update-20/,,Post,,,Development,,,,,,,,2022-06-01,,,,,,,,,,,,,
+OpenID Connect,IETF,,,Sam Goto,,,,,,Browser APIs to enable OpenID Session Management and Privacy,"How does logout in OIDC happen?<br>* Classification problem - browsers do not know it is a logout now<br>* Easiest way<br> * Browser asks for a user consent<br> * Hard from a permission implementation perspective<br> * Tim: No issues with this idea<br> * If user logged into several OPs, user will not look to all the ones they log out from<br>* Option2<br> * Browser classifies signing-in event<br> * On log out does not prompt the user and IdP has no incentives to lie<br> * RPs get to determine if they want to log the user out or not<br> * Whether you can swap generic frame with fenced frame, frame can see it’s own cookies<br> * May not be able to pass any parameters that you need to pass; no link decoration for framed frame<br> * Subdomains also considered, but not well thought out<br> * Logout URL - other option to add, but more work for RP: Resource metadata. Specification - not much adoption. It just feels like a place where RP metadata could be declared which could be useful in this context of the RP defining its metadata (e.g. what IDP it uses)",,https://iiw.idcommons.net/13L/_Browser_APIs_to_enable_OpenID_Session_Management_and_Privacy,,Session Notes,,,Development,,,,,,,,2021-05-06,,,,,,,,,,,,,
+KERI,WebofTrust,,https://keri.one/keri-resources,,,,,,,KERI One - HomePage,,,https://keri.one,,,,,Main,,,,,,,https://identity.foundation/working-groups/keri.html,,https://github.com/WebOfTrust/keri,,,,,,,,,,,,
+KERI,Blockchain Bird,,https://iiw.idcommons.net/3K/_KERI_Q%26A_basic_introduction,,,,,,IIW32,KERI Q&A basic introduction,"It has lots of relevant links in it to start your journey in KERI.<br><br>What is KERI?<br>* Key Event Receipt Infrastructure<br>* Intends to repair the Internet<br>* KERI = CT with decentralized CA<br>* NOT a coin, token…<br><br>Why KERI? (and not something else)<br>* Strong autonomous identifiers<br>* Abiding to privacy (laws and good habits)<br>* Portability, delegation, rotatable keys<br>* Direct & Indirect method<br>* <there’s more>",,https://blockchainbird.org/downloads/KERI-QA-introduction.pdf,,Presentation,,,Main,,,,,,,,2021,,,,,,,,,,,,,
+KERI,personal,,,Samuel Smith,,,,,,Key Event Receipt Infrastructure: A Secure Identifier Overlay for the Internet,Secure attribution of any communication to its source<br>Authentic communication<br>Authentic interactions based an secure attribution of all statements by participants<br>Verifiable authenticity of data<br>Data Provenance<br>Authentic data economy,,https://github.com/SmithSamuelM/Papers/blob/master/presentations/KERI_Overview.web.pdf,,Presentation,2.60,,Main,,,,,,,,2021-03-23,,,,,,,,,,,,,
+KERI,,,https://arxiv.org/abs/1907.02143,Samuel Smith,,,,,,KEY EVENT RECEIPT INFRASTRUCTURE (KERI) DESIGN,"An identity system based secure overlay for the Internet is presented. This includes a primary root-of-trust in self-certifying identifiers. It presents a formalism for Autonomic Identifiers (AIDs) and Autonomic Namespaces (ANs). They are part of an Autonomic Identity System (AIS). This system uses the design principle of minimally sufficient means to provide a candidate trust spanning layer for the internet. Associated with this system is a decentralized key management infrastructure (DKMI). The primary root-of-trust are self-certifying identifiers that are strongly bound at issuance to a cryptographic signing (public, private) key-pair. These are self-contained until/unless control needs to be transferred to a new key-pair. In that event an append only chained key-event log of signed transfer statements provides end verifiable control provenance. This makes intervening operational infrastructure replaceable because the event logs may be therefore be served up by ambient infrastructure. End verifiable logs on ambient infrastructure enables ambient verifiability (verifiable by anyone, anywhere, at anytime). The primary key management operation is key rotation (transference) via a novel key pre-rotation scheme. Two primary trust modalities motivated the design, these are a direct (one-to-one) mode and an indirect (one-to-any) mode. In the direct mode, the identity controller establishes control via verified signatures of the controlling key-pair. The indirect mode extends that trust basis with witnessed key event receipt logs (KERLs) for validating events. The security and accountability guarantees of indirect mode are provided by KERIs Agreement Algorithm for Control Establishment (KACE) among a set of witnesses.",,https://raw.githubusercontent.com/SmithSamuelM/Papers/master/whitepapers/KERI_WP_2.x.web.pdf,,,2.54,,Main,,,,,,,,2020-10-22,,,,,,,,,,,,,
+KERI,,,,Samuel Smith,Manning,,,,,Decentralized key management,"● Why any form of digital key management is hard<br>● Standardsand best practices for conventional key management<br>● The starting point for key management architectures: roots-of-trust<br>● The special challenges of decentralizedkey management<br>● The new tools that verifiable credentials (VCs), decentralized identifiers (DIDs), and self-sovereign identity (SSI) bring to decentralized key management<br>● Key management for ledger-based DID methods<br>● Key management for peer-based DID methods<br>● Fully autonomous decentralized key management with Key Event Receipt Infrastructure (KERI)",,https://raw.githubusercontent.com/SmithSamuelM/Papers/master/whitepapers/10-ssi-key-management.pdf,,,,,Main,,,,,,,,2020-10-19,,,,,,,,,,,,,
+KERI,,,,Samuel Smith,,,,,,UNIVERSAL IDENTIFIER THEORY,Abstract—A universal theory for identifiers is presented. This theory is based on a unified model of identifiers that include cryptographic autonomic identifiers (AIDs) and legitimized (authorized) human meaningful identifiers (LIDs). This model provides truly decentralized trust bases each derived from the cryptographic root-of-trust of a given AID. An AID is based on a self-certifying identifier (SCID) prefix. Self certifying identifiers are not human meaningful but have strong cryptographic properties. The associated self-certifying trust basis gives rise to a trust do- main for associated cryptographically verifiable non-repudiable statements. Every other type of identifier including human meaningful identifiers may then be secured in this resultant trust do- main via an end-verifiable authorization. This authorization legitimizes that human meaningful identifier as an LID though its association with an AID. The result is a secured trust domain specific identifier couplet of aid\|lid. AIDs are provided by the open standard key event receipt infrastructure (KERI). This unified model provides a systematic methodology for the design and implementation of secure decentralized identifier systems that underpin decentralized trust bases and their associated ecosystems of interactions.,,https://raw.githubusercontent.com/SmithSamuelM/Papers/master/whitepapers/IdentifierTheory_web.pdf,,,,,Main,,,,,,,,2020-10-23,,,,,,,,,,,,,
+KERI,DIF,,,,,,,,,KERI Whitepaper,,,https://raw.githubusercontent.com/decentralized-identity/keri/master/kids/KERI_WP.pdf,,,,,Main,,,,,,,,2021-01-11,,,,,,,,,,,,,
+KERI,DIF,,,,,,,,,"KERI: For every DID, a microledger","The world of digital identifiers (DIDs) and verifiable credentials (VCs) is evolving quickly, giving much cause for optimism. Standards are starting to connect and move towards functional interoperability, governed by testable protocols. Most of this work is happening on the level of VCs. However, DIDs and their infrastructure are also starting to converge and mature as an extensible-yet-interoperable technology.",,https://medium.com/decentralized-identity/keri-for-every-did-a-microledger-f9457fa80d2d,,Post,,,About,,,,,,,,2020-10-19,,,,,,,,,,,,,
+KERI,personal,,https://iiw.idcommons.net/23K/_KERI_Composable_Event_Streaming_Representation,Samuel Smith,,,,,,KERI Composable Event Streaming Representation,"The Three KERI Security Sessions presented at IIW32 have the same set of Slides, it takes 3 hours to get through them.<br><br>This session is slides #190 through #208",,https://github.com/SmithSamuelM/Papers/blob/master/presentations/KERI_Overview.web.pdf,,Presentation,,,About,,,,,,,,2021-03-04,,,,,,,,,,,,,
+KERI,Harvard,,,Doc Searls,,,,,,On KERI: a way not to reveal more personal info than you need to,"Here in civilization we typically reveal information about ourselves to others on a need-to-know basis: “I’m over 18.” “I’m a citizen of Canada.” “Here’s my Costco card.” “Hi, I’m Jane.” We may or may not present credentials in these encounters. And in most we don’t say our names. “Michael” being a common name, a guy called “Mike” may tell a barista his name is “Clive” if the guy in front of him just said his name is “Mike.” (My given name is David, a name so common that another David re-branded me Doc. Later I learned that his middle name was David and his first name was Paul. True story.)",,https://blogs.harvard.edu/doc/2020/10/22/keri/,,Post,,,About,,,,,,,,2020-10-22,,,,,,,,,,,,,
+KERI,Jolocom,,,,Jolocom,,,,,How KERI tackles the problem of trust,"In contrast to blockchain or central registry-based trust systems, KERI is based on a hash-chain data structure called a ‘key event receipt log’ (KERL). Conceptually, it’s similar in some ways to the Peer DID Method specification, except that its data model is a KERL rather than a DID document. And while KERI can be used as a DID method, it is fundamentally not reliant on any of the DID specifications and can be used in many other contexts as well. In particular, it is also useful for Internet of Things (IoT) networks and other security-conscious, low-resource use cases.",,https://jolocom.io/blog/how-keri-tackles-the-problem-of-trust/,,Post,,,About,,,,,,,,2020-10-15,,,,,,,,,,,,,
+KERI,Definitely Identity,,,,Samuel Smith,,,,,"Tim talks with Sam Smith, creator of KERI","In this episode, we explore the Key Event Receipt Infrastructure (KERI)and how it relates to decentralized identity. We also touch topics in the white paper: trust domains, self-certifying identifiers, architectural implications, and more.",,https://podcasts.apple.com/ca/podcast/definitely-identity-episode-14-with-sam-smith/id1496565155?i=1000494102345,,episode,,,About,,,,,,,,2020-10-08,,,,,,,,,,,,,
+KERI,Human Colossus Foundation,,,,,,,,,Thinking of DID? KERI On,"The current generation of DIDs has introduced an innovative approach to digital identifiers, which has triggered the SSI movement. However, the inclusion of the method space in the DID syntax has led to fragmentation and weak security properties of the identifier type. These known method-space issues give the community impetus to redress them. In light of these innovative developments, now is the time to embrace KERI as an improved interoperable and secure solution for digital identity.","In this blog post, we address DIDs security from the viewpoint of KERI (Key Event Receipt Infrastructure), a novel, simple, and improved DKMS (Decentralized Key Management System) solution for digital identifiers. KERI provides a unifying solution to DID document authentication and resolution that will prove invaluable to use cases where security and interoperability are essential (e.g., for global supply chains and humanitarian applications).",https://humancolossus.foundation/blog/thinking-of-did-keri-on,,Post,,,About,,,,,,,,2021-01-27,,,,,,,,,,,,,
+KERI,GLEIF,,https://www.gleif.org/lei-solutions/gleifs-digital-strategy-for-the-lei/2022-06-28_lei-digital-strategy-current_version-focus-vlei_v0.17_work.pdf,,,,,,,LEI Digital Strategy,"The Global LEI System (GLEIS) has a unique opportunity to solve the problem of trust for legal entities on a global scale. It can enable digital transformation in a way that is interoperable, independent and autonomous. As a regulatory endorsed system overseen by the Regulatory Oversight Committee (ROC), the GLEIS is the only system that establishes a recognized, monitored and standardized global identity for legal entities that, whenever possible, is linked to the national ID system in that jurisdiction. The system is underpinned by open data, meaning any person or company can access the LEI and its associated reference data. The GLEIS also bridges traditional and online processes by serving as a tool to identify the counterparty in any transaction and can aggregate data on legal entities held in repositories.<br><br>GLEIF’s digital strategy for the LEI centers on two methods for cryptographically binding the LEI to its organization – digital certificates and Verifiable Credentials.","From banking to production and supply chain management, industries worldwide are adjusting to the digitization of processes and transactions. ",https://www.gleif.org/en/lei-solutions/gleifs-digital-strategy-for-the-lei,,Post,,,Organization,,,,,,,,2022-06-08,,,,,,,,,,,,,
+KERI,IDCommons,,,,GLEIF,,,,IIW,GLEIF vLEI with KERI,"The Global Legal Entity Identifier Foundation (GLEIF) proposes that the Legal Enitity Identifier (LEI) can be used to establish a chain of trust for organizational identity.<br><br>In this session, GLEIF shares plans and progress regarding its development program to create an ecosystem and credential governance framework, together with a technical supporting infrastructure, for a verifiable LEI (vLEI), a digitally verifiable credential containing the LEI.",,https://iiw.idcommons.net/20K/_GLEIF_vLEI_with_KERI,,Session Notes,,,Organization,,,,,,,,2021-05-07,,,,,,,,,,,,,
+KERI,TOIP,,,,,,,,,ACDC (Authentic Chained Data Container) Task Force,The purpose of the Authentic Chained Data Container (ACDC) Task Force is to help draft and incubate a family of IETF-focused specifications that defines the standard requirements for the semantics of Authentic Chained Data Containers. The semantics of ACDCs include both source provenance and authorization provenance or delegation.  The hypothesis is that the W3C Verifiable Credential standard may be expanded to serve as an Authentic Data Container (ADC) with authentic provenance chains (APC) as a super semantic. This may be further expanded to support both a source provenance sub-semantic and a delegated authorization sub-semantic. These are all encapsulated into the semantics with supporting syntax of an ACDC.,,https://wiki.trustoverip.org/display/HOME/ACDC+%28Authentic+Chained+Data+Container%29+Task+Force,,page,,,Organization,,,,,,,,2021-01-19,,,,,,,,,,,,,
+KERI,,Trusted Computing Group,,,,,,,,Trusted Computing Group,"The Trusted Computing Group (TCG) is a not-for-profit organization formed to develop, define and promote open, vendor-neutral, global industry specifications and standards, supportive of a hardware-based root of trust, for interoperable trusted computing platforms.TCG’s core technologies include specifications and standards for the Trusted Platform Module (TPM), Trusted Network Communications (TNC) and network security and self-encrypting drives. TCG also has work groups to extend core concepts of trust into cloud security, virtualization and other platforms and computing services from the enterprise to the Internet of Things.",,https://trustedcomputinggroup.org/,https://trustedcomputinggroup.org/wp-content/plugins/revslider/public/assets/assets/dummy.png,site,,,Organization,,,,,,,,,,,,,,,,,,,,,
+KERI,Micro Controller Tips,,,Maria Guerra,,,,,,What is DICE architecture?,"DICE stands for Device Identifier Composition Engine, and it is a security standard created by the Trusted Computing Group (TCG) which has been addressing security issues for years. TCG announced the establishment of DICE Architecture, or DICE Architecture Work Group to address the need for increased security in the Internet of Things (IoT) therefore targeting products such as MCUs and systems on a chip (SoCs).",,https://www.microcontrollertips.com/what-is-dice-architecture-faq/,https://www.microcontrollertips.com/wp-content/uploads/2018/06/DICE-featured.jpg,faq,,,Organization,,,,,,,,2018-07-27,,,,,,,,,,,,,
+KERI,IDCommons,,,Samuel Smith,,,,,IIW,Security Considerations of KERI. Why and how KERI provides secure portability,"Harm that can be done to the a controller: Unavailability, loss of control authority, externally forced duplicity<br><br>Harm that can be done to a validator: Inadvertent acceptance of verifiable - but forged or duplicitous events<br><br>Breaking the promise of global consistency by a controller is a provable liability. However, global consistency may only matter after members of that community need to interact, not before.",,https://iiw.idcommons.net/2K/_Security_Considerations_of_KERI._Why_and_how_KERI_provides_secure_portability,,Session Notes,,,Development,,,,,,,,2021-05-06,,,,,,,,,,,,,
+KERI,DIF,,,,,,,,,Q&A about KERI’s Security model and Guarantees - Part II Security,"*Q: What are the security risks of KERI with regard to the identity protocol?<br><br>Harm that can be done to the a controller: Unavailability, loss of control authority, externally forced duplicity<br><br>Harm that can be done to a validator: Inadvertent acceptance of verifiable - but forged or duplicitous events<br><br>Breaking the promise of global consistemcy by a controller is a provable liability. However, global consistency may only matter after members of that community need to interact, not before.<br><br>### Q: How secure is the KERI infrastructure?<br><br>KERI changes the discussion about security. From a discussion about the security of infrastructure to a discussion about the security of your key management infrastructure. Most people when they think security, the think “oh, blockchain!”: permissioned or permissionless, how hard is it to get 51% attack, etc.Non of that matters for KERI. KERI is all about “are your private keys private?!” And if yes, that drastically slims down the security discussion to brute force attacks to public keys. And because the next public keys are in fact protected by a hash, you have to brute force the hash algorithm, that is post-quantum secure. So that is a very high level of infrastructural security.<br><br>So private key management and protection is the root of your security in KERI.<br><br>### *Q: You are arguing KERI affords greater security than a decentralized linear event system like Bitcoin?<br><br>…you would be fundamentally arguing that you can record a singular, immutable linear event history more securely than Bitcoin, and I see nothing in KERI that would indicate that.<br><br>Read the answer to [this](https://identity.foundation/keri/docs/Q-and-A-Security.html#keri-is-basically-a-series-of-pay2publickeyhash-transactions) first.<br><br>If you read Szabo’s paper on threshold structures, you get security of the same type when ever you use a threshold structure, be it MFA, Multi-Sig, or Distributed consensus. They all are using a combination of multiple relatively weak attack surfaces that must be simulatenously compromised for a successful attack. So multiplying simulatneous weak surfaces = functional equivalent of a stronger attack surface. So when you look at KERI you see that the security is primarily due to cryptographic strength and the witnesses are not the primary source of security but merely secure one thing, that is the availability of the KEL for an identifier. Not the KEL itself. The KEL iteself is secured by signatures.<br><br>From a Validator perspective their security is due to duplicity detection. Successful attack against duplicity detection requires an eclipse attack. Ledgers such as bitcoin are also susceptible to eclipse attacks. So in an apples to apples (resistance to eclipse attack) a KERI watcher network of comparable reach (1000’s of watchers) would have comparable resistance to an eclipse attack.<br><br>### Q: Differences between blockchain-based security and KERI security<br><br>* Where KERI doesn’t need total ordering in its logs, blockchain do need that. What KERI needs is watchers that construct string of event in the relative order of reception of the KEL {TBW please explain or improve this: what is this, why is it important?}<br><br>* Another characteristic is that KERI identifiers are transferable and blockchain-based identifiers are not, they are bound to their ledger.",Key Event Receipt Infrastructure - the spec and implementation of the KERI protocol,https://identity.foundation/keri/docs/Q-and-A-Security.html#qa-section-keri-security-considerations,https://identity.foundation/keri/images/Direct-mode-kel-kerl.png,page,,,Development,,,,,,,,2021-04-06,,,,,,,,,,,,,
+KERI,,,,Samuel Smith,,,,,,W3C DID Security Concerns,**Certificate Transparency Solution**<br>- Public end-verifiable append-only event log with consistency and inclusion proofs <br>- End-verifiable duplicity detection = ambient verifiability of duplicity <br>- Event log is third party infrastructure but it is not trusted because logs are verifiable. <br>- Sparse Merkle trees for revocation of certificates<br>- (related EFF SSL Observatory),,https://github.com/SmithSamuelM/Papers/blob/master/presentations/W3C_DID_Security_Concerns.pdf,,,,,Development,,,,,,,,2020-01-14,,,,,,,,,,,,,
+KERI,DIF,,https://hackmd.io/orhyiJkLT721v4PCPkvQiA?both,,,,,,,Implementation Notes for KERI,"The interpretation of the data associated with the digest or hash tree root in the seal is independent of KERI. This allows KERI to be agnostic about anchored data semantics. Another way of saying this is that seals are data agnostic; they don’t care about the semantics of its associated data. This better preserves privacy because the seal itself does not leak any information about the purpose or specific content of the associated data. Furthermore, because digests are a type of content address, they are self-discoverable. This means there is no need to provide any sort of context or content specific tag or label for the digests. Applications that use KERI may provide discovery of a digest via a hash table (mapping) whose indexes (hash keys) are the digests and the values in the table are the location of the digest in a specific event. To restate, the semantics of the digested data are not needed for discovery of the digest within a key event sequence.",,https://github.com/decentralized-identity/keri/blob/master/implementation.md,,,,,Development,,,,,,,,2020-05-16,,,,,,,,,,,,,
+KERI,IDCommons,,,"Samuel Smith, Dave Huseby",,,,,IIW,KERI and ADS Key State Provenance Logs Kumbaya (KEL and ADPL),"This was a meeting of the minds between myself and Sam Smith and Adrian Gropper that was hugely successful. We all decided to use the term ""endorser"" for what we all called ""registrar""/""witness""/""notary"". We also realized that the KERI proposal for encoding is good enough for authentic data provenance logs and we will be using the KERI encoding. Sam has modified the spec for KERI key event logs to include scripting capabilities needed in the authentic data economy for doing things like cross-chain atomic swaps for selling non-fungible authentic data (NFADs).<br><br>The result is that there is grand convergence on the encoding and file format for key event provenance logs that will be supported by both KERI networks and the broader authentic data economy.",,https://iiw.idcommons.net/24H/_KERI_and_ADS_Key_State_Provenance_Logs_Kumbaya_(KEL_and_ADPL),,Session Notes,,,Development,,,,,,,,2021-05-06,,,,,,,,,,,,,
+KERI,Jolocom,,,,,,,,,Jolocom’s latest contributions to DIF,"Jolocom added support for an [off-chain element based on KERI](https://github.com/decentralized-identity/keri/blob/master/kids/KERI_WP.pdf). This is in addition to the Jolocom DID method (did:jolo and did:keri), which supports the Jolocom-Lib, our own SDK and the Jolocom SmartWallet.",,https://jolocom.io/blog/jolocoms-contributions-to-dif/,,,,,Development,,,,,,,,2021-01-19,,,,,,,,,,,,,
+KERI,SSI-Meetup,,https://www.youtube.com/watch?v=izNZ20XSXR0,,,,,,,Key Event Receipt Infrastructure (KERI): A secure identifier overlay for the internet – Sam Smith – Webinar 58,,,https://ssimeetup.org/key-event-receipt-infrastructure-keri-secure-identifier-overlay-internet-sam-smith-webinar-58/,,,,,Presentations,,,,,,,,2020-05-19,,,,,,,,,,,,,
+KERI,,,,Samuel Smith,,,,,,KERI Overview,"**Separation of Control** Shared (permissioned) ledger = shared control over shared data.<br>* Shared data = good, shared control = bad.<br>* Shared control between controller and validator may be problematic for governance, scalability, and performance.KERI  = separated control over shared data.<br>* Separated control between controller and validator may provide better decentralization, more flexibility, better scalability, lower cost, higher performance, and more privacy at comparable security.",,https://raw.githubusercontent.com/SmithSamuelM/Papers/master/presentations/KERI2_Overview.web.pdf,,,2.54,,Presentations,,,,,,,,2020-10-22,,,,,,,,,,,,,
+KERI,,,,Samuel Smith,,,,,,The Duplicity Game: or why you can trust KERI,"**Inconsistency vs. Duplicity**<br>- inconsistency: lacking agreement, as two or more things in relation to each other<br>- duplicity: acting in two different ways to different people concerning the same matter<br>**Internal vs. External Inconsistency** <br>- Internally inconsistent log = not verifiable.<br>- Log verification from self-certifying root-of-trust protects against internal inconsistency.<br>Externally inconsistent log with a purported copy of log but both verifiable = duplicitous.<br>Duplicity detection protects against external inconsistency.",,https://raw.githubusercontent.com/SmithSamuelM/Papers/master/presentations/DuplicityGame_IIW_2020_A.pdf,,,,,Presentations,,,,,,,,2020-05-09,,,,,,,,,,,,,
+KERI,,,,Samuel Smith,,,,,,Key Event Receipt Infrastructure (KERI) Model for a Universal DKMI,"**KERI Nomenclature**<br>* **self-certifying identifier**: includes public key<br>* **digital signature**: unique non-repudiable (cypher suite known)<br>* **digest**: collision resistant hash of content<br>* **signed digest**: commitment to content<br>* **controller**: controlling entity of identifier<br>* **message**: serialized data structure event: actionable message<br>* **key event**: key management operation<br>* **inception event**: unique self-signed event that creates identifier and controlling key(s)<br>* **rotation event**: self-signed uniquely ordered event from a sequence that changes the set of controlling keys<br>* **verifier**: cryptographically verifies signature(s) on an event message.<br>* **witness**: entity that may receive, verify, and store key events for an identifier. Each witness controls its own identifier used to sign key event messages, controller is a special case of witness.<br>* **receipt**: event message or reference with one or more witness signatures<br>* **key event log**: ordered record of all self-signed key event messages key event<br>* **receipt log**: ordered record of all key event receipts for a given set of witnesses<br>* **validator**: determines current authoritative key set for identifier from at least one key event (receipt) log. <br>* **judge**: determines current authoritative key set for identifier from the key event receipt logs from a set of witnesses.<br>* **pre-rotation**: commitment to next rotated key set in previous rotation or inception event",,https://raw.githubusercontent.com/SmithSamuelM/Papers/master/presentations/KERI_Overview.pdf,,,,,Presentations,,,,,,,,2019-12,,,,,,,,,,,,,
+KERI,,,,Samuel Smith,,,,,,KERI for Muggles IIW #31 Day 1 - Session #220 October 2020,KERI is a new approach to decentralized identifiers and decentralized key management that promises significant benefits for SSI (self-sovereign identity) and ToIP (Trust over IP) infrastructure,,https://raw.githubusercontent.com/SmithSamuelM/Papers/master/presentations/KERI_for_Muggles.pdf,,,,,Presentations,,,,,,,,2020-10-21,,,,,,,,,,,,,
+KERI,,,,Samuel Smith,,,,,,Verifiable Trust Bases,"* KERI enables cryptographic proof-of-control-authority (provenance) for each identifier.<br>* A proof is in the form of an identifier’s key event receipt log (KERL).<br>* KERLs are *End Verifiable*:<br>  * End user alone may verify. Zero trust in intervening infrastructure.<br>* KERLs may be *Ambient Verifiable*:<br>  * Anyone may verify anylog, anywhere, at anytime.<br>* KERI = self-cert root-of-trust + certificate transparency + KA2CE + recoverable + post-quantum.",,https://raw.githubusercontent.com/SmithSamuelM/Papers/master/presentations/KERIVerifiableTrustBases.web.pdf,,,2.53,,Presentations,,,,,,,,2020-10-20,,,,,,,,,,,,,
+KERI,Springer,,,"Girault, M.",,,,,EUROCRYPT 1991,Self-certifiepublic keys,,,https://link.springer.com/content/pdf/11007%2F3-540-46416-6_42.pdf,,,,,Literature; Self-Certifying Identifiers,,,,,,,,1991,,,,,,,,,,,,,
+KERI,MIT,,,"Kaminsky M., Banks E.",,,,,,SFS-HTTP: Securing the Web with Self-Certifying URLs,,,https://pdos.csail.mit.edu/~kaminsky/sfs-http.ps,,,,,Literature; Self-Certifying Identifiers,,,,,,,,1999,,,,,,,,,,,,,
+KERI,Sigops,,,"Mazieres D., Kaashoek M. F.",MIT,,,,,Escaping the Evils of Centralized Control with self-certifying pathnames,,,http://www.sigops.org/ew-history/1998/papers/mazieres.ps,,,,,Literature; Self-Certifying Identifiers,,,,,,,,2000,,,,,,,,,,,,,
+KERI,CSAIL,,,Mazieres D.,,,,,,Self-certifying File System,,,https://pdos.csail.mit.edu/~ericp/doc/sfs-thesis.ps,,,,,Literature; Self-Certifying Identifiers,,,,,,,,2000-06-01,,,,,,,,,,,,,
+KERI,Trusted Computing Group,,,,,,,,,Implicit Identity Based Device Attestation,,,https://trustedcomputinggroup.org/wp-content/uploads/TCG-DICE-Arch-Implicit-Identity-Based-Device-Attestation-v1-rev93.pdf,,,,,Literature; Self-Certifying Identifiers,,,,,,,,2018-03-05,,,,,,,,,,,,,
+KERI,,,,Samuel Smith,,,,,,Open Reputation Framework,,,https://github.com/SmithSamuelM/Paperblob/master/whitepapers/open-reputation-low-level-whitepaper.pdf,,,,,Literature; Autonomic Identifiers,,,,,,,,2015-05-13,,,,,,,,,,,,,
+KERI,,,,"Samuel Smith, Khovratovich D.",,,,,,Identity System Essentials,,,https://github.com/SmithSamuelM/Papers/blob/master/whitepapers/Identity-System-Essentials.pdf,,,,,Literature; Autonomic Identifiers,,,,,,,,2016-03-29,,,,,,,,,,,,,
+KERI,,,,Samuel Smith,,,,,,Decentralized Autonomic Data (DAD) and the three R’s of Key Management,"Rebooting the Web of Trust RWOT 6, Spring 2018",,https://github.com/SmithSamuelM/Papers/blob/master/whitepapers/DecentralizedAutonomicData.pdf,,,,,Literature; Autonomic Identifiers,,,,,,,,2018-05-23,,,,,,,,,,,,,
+KERI,arXiv,,,Samuel Smith,,,,,,Key Event Receipt Infrastructure (KERI) Design and Build,,,https://arxiv.org/abs/1907.02143,,,,,Literature; Autonomic Identifiers,,,,,,,,2019-07-03,,,,,,,,,,,,,
+KERI,,,,"Conway S, Hughes A",,,,,RWOT 7,A DID for Everything,,,https://github.com/SmithSamuelM/Papers/blob/master/whitepapers/A_DID_for_everything.pdf,,,,,Literature; Autonomic Identifiers,,,,,,,,2018-09-26,,,,,,,,,,,,,
+KERI,WeboftrustInfo,,,"Stocker C, Samuel Smith, Juan Caballero",,,,,RWOT10,Quantum Secure DIDs,,,https://github.com/WebOfTrustInfo/rwot10-buenosaires/blob/master/final-documents/quantum-secure-dids.pdf,,,,,Literature; Autonomic Identifiers,,,,,,,,2020-07-09,,,,,,,,,,,,,
+KERI,ACMQueue,,http://www.certificate-transparency.org/home,Ben Laurie,,,,,,"Certificate Transparency: Public, verifiable, append-only log",,,https://queue.acm.org/detail.cfm?id=2668154,,,,,Literature; Certificate Transparency,,,,,,,,2014-09-08,,,,,,,,,,,,,
+KERI,Links,,,"Ben Laurie, Emilia Kasper",,,,,,Revocation Transparency,,,https://web.archive.org/web/20230309211444/https://www.links.org/files/RevocationTransparency.pdf,,,,,Literature; Certificate Transparency,,,,,,,,2015,,,,,,,,,,,,,
+KERI,,,,Steve Tout,,,,,,Non Conformist Innovation Summit Closing Keynote #2 - Sam Smith,The Economics of Its & Bits - Digital Identity - Freedom Privacy Control Security,,https://www.youtube.com/watch?v=L82O9nqHjRE,,,,,Assorted,,,,,,,,2020-07-23,,,,,,,,,,,,,
+KERI,IDCommons,,,Robert Mitwicki,,,,,IIW,Supply chain – ACDC and KERI + DEMO,"Authentic Chain Data Containers (ACDC) - is a technology which allows to secure and chain data in a generic way. It aims to improve the way we do VC and how we think about authentic data.<br><br>After explanation of ACDC, a demo was performed where it was shown how KERI can enable authentic data flow within the supply chain without the need of having any blockchain nor one single network.",,https://iiw.idcommons.net/14K/_Supply_chain_%E2%80%93_ACDC_and_KERI_+_DEMO,,Session Notes,,,Assorted,,,,,,,,2021-05-07,,,,,,,,,,,,,
+KERI,personal,,,Robert Mitwicki,,,,,,KERI: Facilitating secure data flows in an auditable supply chain,"Supply Chain and why you need Blockchain <br>- Time-stamping, tracking, and automating transactions, so that events can be audited in real time <br>- Minimizing the involvement of intermediaries such as bankers, insurers, and brokers <br>- Setting up a wide range of self-executing contracts to automate repetitive processes such as billing and shipping <br>- Establishing proof of quality, provenance, payment, and performance to minimize counterfeiting and fraud <br>- Making it easier, faster, and cheaper to onboard new vendors and partners by assigning digital IDs<br>Supply Chain and why you DON’T want Blockchain <br>- Lack of Interoperability - my ledger vs someone else ledger, how to bridge it and navigate<br>- Problem with Governance Framework - who decided who can join? <br>- Scaling<br>- Privacy",,https://docs.google.com/presentation/d/1tF_OFGAKUz9RKCLTdwDYDu7hJuEbFz-LQ6PAih7HBK8/edit#slide=id.p,,Presentation,,,Assorted,,,,,,,,2020-10-10,,,,,,,,,,,,,
+Cryptography,SRI,,https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0109.html,"David Balenson, Nick Genise",,,,,,Cryptography Review of W3C Verifiable Credentials Data Model (VCDM) and Decentralized Identifiers (DIDs) Standards and Cryptography Implementation Recommendations,"Cryptography used by U.S. government entities in operational systems must conform to relevant federal government standards and requirements, including the Federal Information Security Management Act (FISMA) and National Institute of Technology (NIST) standards for use of cryptography. As part of its in-depth technical due-diligence to enable operational capabilities for DHS/CBP, DHS/PRIV and DHS/USCIS, the U.S. Department of Homeland Security’s Silicon Valley Innovation Program (SVIP) sponsored independent nonprofit research center SRI International to conduct a cryptographic review of the W3C Verifiable Credentials Data Model and W3C Decentralized Identifiers standards. The review provided constructive feedback and recommendations for technology developers and W3C standards developers to increase their level of compliance with federal government standards.",,http://www.csl.sri.com/papers/vcdm-did-crypto-recs/,,Paper,,,Assorted,,,,,,Verifiable Credentials,,2023-01-01,,,,,,,,,,,,,
+Cryptography,Zero Knowledge,,,,ZeroKnowledge,,,,,ZK for Authentication With Nolan and Locke from NuID,"Here are a few of the articles mentioned in the episode:<br>–[Universally Composable Direct Anonymous Attestation](https://eprint.iacr.org/2015/1246.pdf) by Jan Camenisch , Manu Drijvers , and Anja Lehmann<br>–[Practical UC-Secure Delegatable Credentials with Attributes and Their Application to Blockchain](https://eprint.iacr.org/2015/1246.pdf) by Jan Camenisch , Manu Drijvers , and Anja Lehmann<br>–[Privacy-Preserving User-Auditable Pseudonym Systems](https://researcher.watson.ibm.com/researcher/files/zurich-ANJ/main_nymlog.pdf) by Jan Camenisch & Anja Lehmann IBM Research – Zurich","Zero Knowledge Podcast is a show about zk proofs and other blockchain tech. Learn about the latest in zero knowledge research, cryptography-enabled privacy tech.",https://www.zeroknowledge.fm/154,https://i0.wp.com/zeroknowledge.fm/wp-content/uploads/2021/06/Discourse_icon.svg.png?fit=800%2C815&ssl=1,episode,,,Assorted,,,,,,,,2020-11-04,,,,,,,,,,,,,
+Cryptography,Soatok,,https://lists.w3.org/Archives/Public/public-credentials/2022May/0048.html,,,,,,,Guidance for Choosing an Elliptic Curve Signature Algorithm in 2022,"Most people just defer to SafeCurves, but it’s a little dated: We have complete addition formulas for Weierstrass curves now, but SafeCurves doesn’t reflect that.<br><br>For the purpose of simplicity, I’m not going to focus on a general treatment of Elliptic Curve Cryptography (ECC), which includes pairing-based cryptography, Elliptic-Curve Diffie-Hellman, and (arguably) isogeny cryptography.<br><br>Instead, I’m going to focus entirely on elliptic curve digital signature algorithms.",A cartoon wild canid on the Internet provides general guidance on elliptic curve cryptography parameter choices.,https://soatok.blog/2022/05/19/guidance-for-choosing-an-elliptic-curve-signature-algorithm-in-2022/,,Post,,,Assorted,,,,,,,,2022-05-19,,,,,,,,,,,,,
+Cryptography,CCG,,https://w3c.github.io/cg-reports/credentials/CG-FINAL-data-integrity-20220722/,,,,,,,JSON Web Signature 2020,This specification describes a JSON Web Signature Suite created in 2020 for the Linked Data Proof specification. The Signature Suite utilizes Detached JWS signatures to provide support for a subset of the digital signature algorithms registered with IANA.,,https://www.w3.org/community/reports/credentials/CG-FINAL-lds-jws2020-20220721/,,Specification,,,Specification,,,,,,Verifiable Credentials,,2022-07-21,,,,,,,,,,,,,
+Cryptography,CCG,,https://w3c.github.io/cg-reports/credentials/CG-FINAL-lds-jws2020-20220721/,,,,,,,ECDSA Cryptosuite v2019,This specification describes a Data Integrity Cryptosuite for use when generating a digital signature using the Elliptic Curve Digital Signature Algorithm (ECDSA) based on the Standards for Efficient Cryptography over prime fields using a verifiably random Elliptic Curve (secpr1). The approach is accepted by the U.S. National Institute of Standards and meets U.S. Federal Information Processing requirements when using cryptography to secure digital information. https://www.w3.org/community/reports/credentials/CG-FINAL-di-ecdsa-2019-20220724/,,https://www.w3.org/community/reports/credentials/CG-FINAL-di-ecdsa-2019-20220724/,,Specification,,,Specification,,,,,,Verifiable Credentials,,2022-07-24,,,,,,,,,,,,,
+Cryptography,CCG,,https://w3c.github.io/cg-reports/credentials/CG-FINAL-di-ecdsa-2019-20220724/,,,,,,,EdDSA Cryptosuite v2020,"This specification describes a Data Integrity Cryptosuite for use when creating or verifying a digital signature using the twisted Edwards Curve Digital Signature Algorithm (EdDSA) and Curve25519 (ed25519). The approach is accepted by the U.S. National Institute of Standards in the latest FIPS 186-5 draft and, after ratification, is expected to meet U.S. Federal Information Processing requirements when using cryptography to secure digital information.",,https://www.w3.org/community/reports/credentials/CG-FINAL-di-eddsa-2020-20220724/,,Specification,,,Specification,,,,,,Verifiable Credentials,,2022-07-24,,,,,,,,,,,,,
+Cryptography,CCG,,https://w3c.github.io/cg-reports/credentials/CG-FINAL-di-eddsa-2020-20220724/,,,,,,,Data Integrity 1.0,"This specification describes mechanisms for ensuring the authenticity and integrity of structured digital documents using cryptography, such as digital signatures and other digital mathematical proofs.",,https://www.w3.org/community/reports/credentials/CG-FINAL-data-integrity-20220722/,,Specification,,,Specification,,,,,,Verifiable Credentials,,2022-07-22,,,,,,,,,,,,,
+Cryptography,IETF,,https://self-issued.info/?p=2260,,,,,,,Barreto-Lynn-Scott Elliptic Curve Key Representations for JOSE and COSE,"This specification defines how to represent cryptographic keys for the pairing-friendly elliptic curves known as Barreto-Lynn-Scott (BLS), for use with the key representation formats of JSON Web Key (JWK) and COSE (COSE_Key).",Barreto-Lynn-Scott Elliptic Curve Key Representations for JOSE and COSE,https://datatracker.ietf.org/doc/draft-ietf-cose-bls-key-representations/,,Specification,,,Specification,,,,,,,,2023-03-13,,,,,,,,,,,,,
+Cryptography,NIST,,,,,,,,,"PQC Standardization Process: Announcing Four Candidates to be Standardized, Plus Fourth Round Candidates","NIST has completed the third round of the Post-Quantum Cryptography (PQC) standardization process, which selects public-key cryptographic algorithms to protect information through the advent of quantum computers. A total of four candidate algorithms have been selected for standardization, and four additional algorithms will continue into the fourth round.","NIST is announcing four Post-Quantum Cryptography candidates for standardization, plus candidates for a fourth round of analysis.",https://csrc.nist.gov/News/2022/pqc-candidates-to-be-standardized-and-round-4,,Post,,,Specification,,,,,,,,2022-07-05,,,,,,,,,,,,,
+Cryptography,CISA,,,,,,,,,Prepare for a New Cryptographic Standard to Protect Against Future Quantum-Based Threats,"The National Institute of Standards and Technology (NIST) has announced that a new post-quantum cryptographic standard will replace current public-key cryptography, which is vulnerable to quantum-based attacks. Note: the term “post-quantum cryptography” is often referred to as “quantum-resistant cryptography” and includes, “cryptographic algorithms or methods that are assessed not to be specifically vulnerable to attack by either a CRQC [cryptanalytically relevant quantum computer] or classical computer.” (See the National Security Memorandum on Promoting United States Leadership in Quantum Computing While Mitigating Risks to Vulnerable Cryptographic Systems for more information).",,https://www.cisa.gov/uscert/ncas/current-activity/2022/07/05/prepare-new-cryptographic-standard-protect-against-future-quantum,https://www.cisa.gov/profiles/cisad8_gov/themes/custom/gesso/dist/images/icon-dot-gov.svg,Post,,,Quantum,,,,,,,,2022-07-05,,,,,,,,,,,,,
+Cryptography,CCG Mailing List,,,Manu Sporny,,,,,,Future-proofing VCs via multiple signatures,"What this means is that it is now possible to not have to depend on one signature format, and instead use multiple to meet different needs. The VC above supports NIST-approved cryptography today, while enabling the advanced use of BBS+ (if an organization would like to use it /before/ it is standardized at IETF), and also enabling protection if a quantum computer were to break both Ed25519 and BBS+... all on the same VC in a fairly compact format.",,https://lists.w3.org/Archives/Public/public-credentials/2022Jan/0043.html,,Discussion,,,Quantum,,,,,,Verifiable Credentials,,2022-01-06,,,,,,,,,,,,,
+Cryptography,CCG Mailing List,,,Orie Steele,,,,,,New Work Item Incubating for IETF: JSON Encoding for Post Quantum Signatures from Mike Prorock on 2022-02-01 (public-credentials@w3.org from February 2022),"I look forward to continuing to work on JSON encoding for post quantum signature schemes.<br><br>In particular, support for JWS and JWK as building blocks for higher order cryptographic systems, such as DIDs and VCs.<br><br>If you are interested in contributing, please feel free to open issues here:[https://github.com/mesur-io/post-quantum-signatures](https://github.com/mesur-io/post-quantum-signatures)",,https://lists.w3.org/Archives/Public/public-credentials/2022Feb/0008.html,,Discussion,,,Quantum,,,,,,,,2022-02-01,,,,,,,,,,,,,
+Cryptography,CCG Mailing List,,,Mike Prorock,,,,,,Post Quantum and Related,"Please do be tracking the upcoming changes around crypto primitives,<br>especially signature methods.  See the recent NIST announcement for more<br>details, but effectively, be planning on future support for CRYSTALS-KYBER,<br>and on the signature side of things CRYSTALS-Dilithium, FALCON, and SPHINCS+<br><br>NIST Announcement here:<br>https://csrc.nist.gov/News/2022/pqc-candidates-to-be-standardized-and-round-4<br><br>And a pretty good game plan from CISA with some timing implications here:<br>https://www.cisa.gov/uscert/ncas/current-activity/2022/07/05/prepare-new-cryptographic-standard-protect-against-future-quantum<br><br>The TLDR is to assume that we need hard answers as a community, and at the<br>standards level, on crypto agility by 2024, as well as support for the key<br>algorithms as listed above.<br><br>I would also think that any new specs being drafted should reference these<br>coming changes and start to work them in.  I would also be proactive on<br>adding in references as appropriate to specs you might be an editor or<br>author for (or just a contributor).",,https://lists.w3.org/Archives/Public/public-credentials/2022Jul/0010.html,,Discussion,,,Quantum,,,,,,jose/cose,,2022-07-06,,,,,,,,,,,,,
+Cryptography,CCG Mailing List,,,"Joosten, H.J.M.",,,,,,[CEIP] Draft paper on Cryptographically Enforceable Issuer Policies,"my colleague Sterre and I drafted [a paper that we provisionally called Cryptographically Enforceable Issuer Policies](https://docs.google.com/document/d/1c8kIUqB2BBzM3usfD0_s5wu_z6K2KndzJ4uK_oZcPOs/edit?usp=sharing), which describes our current thinking on this topic.<br><br>The paper isn’t finished. We need more text in the ‘discussions’ section, and hope that by making the draft available we’ll get the discussions that we (or you?) can describe in there. Also, we might have missed stuff that you as a reader need for a proper understanding of what this is all about, and to start pondering for what (other) purposes all this might be used. Or why this proposal is a very bad idea that we should not spend any more time on.",,https://lists.w3.org/Archives/Public/public-credentials/2021May/0170.html,,Discussion,,,Quantum,,,,,,,,2021-05-31,,,,,,,,,,,,,
+Cryptography,CCG Mailing List,,,Rieks Joosten,,,,,,Blog on SSI and Cryptographically Enforceable Policies,"I've posted a new SSI blog entitled: ""[Protecting Sensitive Parts of Credentials with Cryptographically Enforceable Policies](https://blockchain.tno.nl/blog/protecting-sensitive-parts-of-credentials-with-cryptographically-enforceable-policies/)"".<br><br>It has a proposal that enables credential issuers to encrypt sensitive parts of credentials in such a way that can only be decrypted by parties tha satisfy the issuer's policy (that was used to encrypt these parts). The blog motivates the need, introduces a high-level architecture, explains how it would work, and discusses some issues that need to be looked into.",,https://lists.w3.org/Archives/Public/public-credentials/2022Feb/0032.html,,Discussion,,,Discussion,,,,,,,,2022-02-08,,,,,,,,,,,,,
+Cryptography,CCG Mailing List,,,Marcus Sabadello,,,,,,Universal signature verifier,"We (Danube Tech) have a ""Universal Verifier"" here: [https://univerifier.io/](https://univerifier.io/)<br><br>But I don't claim that it actually supports all the credential formats  and signature suites in existence...<br><br>Especially considering that at the last Internet Identity Workshop a lot of different formats were identified",,https://lists.w3.org/Archives/Public/public-credentials/2022May/0005.html,,Discussion,,,Discussion,,,,,,,,2022-05-04,,,,,,,,,,,,,
+Cryptography,CCG Mailing List,,https://soatok.blog/2022/05/19/guidance-for-choosing-an-elliptic-curve-signature-algorithm-in-2022/,Manu Sporny,,,,,,Updating SafeCurves for 2022...,I found this blog post useful for the upcoming VC2WG cryptosuite work:<br><br>Guidance for Choosing an Elliptic Curve Signature Algorithm in 2022<br><br>https://soatok.blog/2022/05/19/guidance-for-choosing-an-elliptic-curve-signature-algorithm-in-2022/<br><br>It suggests updates to the SafeCurves website:<br><br>https://safecurves.cr.yp.to/<br><br>... and does a fairly good job of boiling down the choices and<br>misinterpretations in the space.<br><br>Bonus points because it also included a link to this undiscovered gem:<br><br>https://www.howmanydayssinceajwtalgnonevuln.com/<br><br>Worth a read for those of us that are thinking about good cryptosuite choices<br>for VCs in 2022.,,https://lists.w3.org/Archives/Public/public-credentials/2022May/0048.html,,Discussion,,,Discussion,,,,,,,,2022-05-24,,,,,,,,,,,,,
+Cryptography,CCG Mailing List,,,Manu Sporny,,,,,,Cross-vendor interop for Data Integrity and Ed25519Signature2020 achieved,We are happy to announce today that we have our first demonstration of cross-vendor interoperability between Danube Tech and Digital Bazaar for verification regarding the Data Integrity and Ed25519Signature2020 work items,,https://lists.w3.org/Archives/Public/public-credentials/2022May/0034.html,,Discussion,,,Discussion,,,,,,,,2022-05-17,,,,,,,,,,,,,
+Cryptography,CCG Mailing List,,,Manu Sporny,,,,,,Streamlining Data Integrity Cryptosuites,"How many crypto suites could there be? Well, there are at least this many today:<br>● https://w3id.org/security/suites/ed25519-2020/v1<br>● https://w3id.org/security/suites/x25519-2019/v1<br>● https://w3id.org/security/suites/merkle-disclosure-2021/v1<br>● https://w3id.org/security/suites/secp256k1recovery-2020/v1<br>● https://w3id.org/security/suites/pgp-2021/v1<br>● https://w3id.org/security/suites/blockchain-2021/v1<br>● https://w3id.org/security/suites/jws-2020/v1<br>● https://w3id.org/security/suites/bls12381-2020/v1<br>● https://w3id.org/security/suites/eip712sig-2021/v1<br>● https://w3id.org/security/suites/secp256k1-2020/v1<br>● https://w3id.org/security/suites/secp256k1-2019/v1<br>● https://w3id.org/security/suites/merkle-2019/v1<br>● https://w3id.org/security/suites/chained-2021/v1",,https://lists.w3.org/Archives/Public/public-credentials/2022Jul/0115.html,,Discussion,,,Discussion,,,,,,,,2022-07-31,,,,,,,,,,,,,

_data/tagz.yml

@@ -0,0 +1,18 @@
+region: ["Europe", "Canada", "California", "USA", "Zug", "Switzerland", "Global", "Illinois", "Wyoming", "EU", "Ontairo"]
+policy: ["GDPR", "eIDAS", "CCPA"]
+guidance: ["Augmented Social Network", "Laws of Identity", "UNSDGs", "National Data Strategy", "Data A New Direction", "NSTIC", "PCTF", "Windhover Principles"]
+business: ["100101075", "1Kosmos", "2Keys", "3box", "51nodes", "Aalto", "Absa", "Absolutely Zero Cyber", "ABT Network", "Accenture", "Aergo", "aetna", "agreementsolutions", "Amihan", "Anonyome Labs", "APG", "Applied Recognition", "ArcBlock", "Ardor", "ARTiFACTS", "Arucc", "ATB", "Attinad", "Auth0", "Authenteq", "Ayanworks", "Baidu", "BakerHostetler", "BIF", "BIG", "BigchainDB", "BiiLabs", "Binance", "Bitwise", "BizSecure", "Blinking", "Blockchain Foundry", "Blockcore", "Blocko", "BlockPass", "BlockSpaces", "Blockstack", "Blockster Labs", "BLOK", "Bloom", "BMO", "Boloro", "Bot Ventures", "BOTLabs", "Brightlands", "bryk", "BTP", "Bullet ID", "C1", "Canada Health Infoway", "Celerity", "Celero", "Celo", "Certisign", "CFCA", "Chainlink", "Chainyard", "Cibc", "Cisco", "Civic", "Cloudchain", "Consensys", "Consensys Health", "Consent", "Convergence", "Corda", "Credible", "cryptonics", "CULedger", "Cynjatech", "Cysecure", "Danube Tech", "Dark Matter Labs", "Datacard", "Datum", "De Volksbank", "Desert Financial", "Desjardins", "DFINITY", "DI", "DigiCert", "Digidentity", "Digital Bazaar", "Digital Link", "Dignario", "Distributed ID", "diwala", "DIZME", "Dock", "Dominode", "Echo", "Eclipse", "Elastos", "Enigma", "Entrust", "Equifax", "Equinix", "Equitable Bank", "Estatus", "Evan Network", "Evernym", "Factom", "FHI360", "Finclusive", "Finicity", "Folio", "ForgeRock", "Fujitsu", "Gambit", "gamecredits", "Gatica", "Gavi", "Gem", "Get Group", "Github", "GlobaliD", "GRGBanking", "GS1", "Halialabs", "HealthDigit", "Humanized-internet", "Hypersecu", "IBM", "ICAI India", "ICC", "iComply", "ICONLOOP", "IdentityNorth", "Identos", "Ideo", "IDRamp", "IDUnion", "In fidem", "In-Sec-M", "Indicio", "IndieAuth", "InfoCert", "InfoWallet", "Ingenico", "Intel", "Interac", "IOP", "IoTeX", "IPID", "iProov", "iRespond", "JLinc", "Jnctn", "Jolocom", "Jumio", "Kepler", "KILT", "Kiva", "Kuppinger Cole", "KYC-Chain", "LD", "Learning Machine", "Legisym", "lifeID", "Libro", "Liquid Avatar Technologies", "LNk-E", "Lorica Identity", "Ltsa", "Luxoft", "Manulife", "Mastercard", "MATTR", "Mavennet", "Mavnet", "Meeco", "MediBloc", "Mercy Corps", "Mesur", "Metadium", "MetaX", "Microsoft", "MOAC", "Modohr", "Mooti", "MyCuID", "Narf", "National Cybersecurity Center", "netki", "Networks Synergy", "Newbruns", "Northern Block", "Notarius couleur", "Nuggets", "NuID", "OARO", "Ockam", "Okta", "OmniOne", "One span", "Onfido", "Ontology", "Oracle", "OTA", "Outlier", "Panta Transportation", "Payments Canada", "Peer Social", "Perkins Cole", "Pillar", "PlaceSpeak", "Plurilock", "Pragma", "PRIVATE", "Privatyze", "ProCivis", "Prodigy", "ProSapien", "Proven", "ProximaX", "PWC", "Quartech", "Quorum", "R_Block", "R3", "Rabobank", "Raonsecure", "RBC 1", "remme", "RSA", "Safran", "Salesforce", "Saskatchewan", "Securefact", "SecureKey", "Selfd.id", "SelfKey", "Serto", "SICPA", "Simeio", "Simprints", "SITA", "sitekit", "Smart species", "Snapper Future Tech", "Snowbridge Inc", "Solarity", "Sony", "SpaceElephant", "Spark NZ", "Sphereon", "Spherity", "Stash", "State Street", "Stranger Labs", "Supercluster", "suru", "Swisscom", "SwissSign", "T-Labs", "Taqanu", "Td", "Teleinfo CAICT", "Telus", "Tierion", "TMChain", "TNO", "Token.TM", "TranSendX", "Transmute", "TreeFort", "Trinsic", "Trulioo", "Trust Stamp", "Trusted key", "Truu", "TwinPeek", "Twitter", "Tykn", "Ubisecure", "UC Berkeley", "Uphold", "uPort", "UXP Systems", "Validatedid", "Vallid", "Vancity", "Vaultie", "Veridium", "Verified.ME", "Verio ID", "VERSES Labs", "Vimsa", "Vivvo", "Vlinder", "VP", "Weelink", "Workday", "Worldreach", "YLZ Inc", "Xertify", "Yoti", "SpruceID", "VeramoLabs", "EntTrustient", "MedCreds", "Respect Network", "Unibright", "Verisign"]
+organization: ["BCGov", "DHS", "DIACC", "DIF", "EBSI", "Enterprise Ethereum Alliance", "ESSIFlab", "Ethereum Foundation", "FIDO", "First Education CU", "GLEIF", "Hyperledger", "ID2020", "IDCommons", "IETF", "Linux Foundation", "MyData", "OASIS", "OpenID", "Sovrin Foundation", "SSI-Meetup", "Trust over IP", "Veres One", "W3C", "Canadapost", "Blockchain for Impact", "Ethereum Enterprise Alliance", "BC Ministry of Citizens Services", "WomeninID", "UNHCR", "UNDP", "UN/CEFACT", "WEF", "OAS Staff FCU", "Royal CU", "Crypto Valley Association", "lab10 collective", "Qiy Foundation", "Affinity Credit Union", "Rockefeller Foundation", "Linux Foundation Public Health", "VCI", "BlockchainCommons", "TIFAC-CORE", "UNISOT", "DigitalScot", "Secure Digital Identity Association", "IAB", "IAPP", "CPRA", "ACM", "Dutch Research"]
+focus: ["Compliance", "Development", "DWeb", "Education", "Enterprise", "Financial Services", "Healthcare", "Humanitarian", "IAM", "ID", "Interop", "Onboarding", "Personal Data", "Public Sector", "Supply Chain", "Web3", "COVID", "Machine Readable Governance", "SaaS"]
+affiliation: ["Sovrin Steward", "ID2020 Founder", "VCI Founder", "Founding Sovrin Steward"]
+working_groups: ["Claims and Credentials WG", "Credentials Community Group", "DIDAuth WG", "DIDComm WG", "Identifiers and Discovery WG", "Interop WG", "Storage and Compute WG", "VC-WG", "Veres One CG"]
+specs_standards: ["BBS Signatures", "Blockcerts", "BTCR", "Dataweb", "DID", "DKMI", "DKMS", "Encrypted Data Vaults", "ERC725", "IPFS", "ISO 27001", "JSON-LD", "Linked Data", "OAuth", "OIDC", "PGP", "RDF", "Schema.org", "Secure Data Storage", "Verifiable Credentials", "WebAuthN", "XDI", "Barcode", "RFID", "XRI", "0Auth", "DNS", "ISO 18013-5", "oCap", "zCap", "Public Benefit Corporation", "SMS", "SOIP", "JWK", "OpenID Connect", "FIDO2"]
+did_methods: ["DID:UNS", "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:TEZOS", "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"]
+tech: ["AI", "Blockchain", "Data Hubs", "Digital Signatures", "DPKI", "IOT", "Wallets", "Email", "TOR", "Magic Link"]
+platforms: ["Alastria", "Bitcoin", "Cosmos", "Ethereum", "Verifiable Organizations Network", "Hashgraph", "Holochain", "Ocean Protocol", "IOTA", "Sovrin", "NEO", "Polkadot", "Evan Network", "NEAR", "Klaytn", "BSC", "TRON", "GrgChain", "Zilliqa", "UNS", "RChain", "Panacea", "SelfKey Identity", "Commercio", "Ceramic Network", "EOS", "European Data Infrastructure", "ViDChain", "Hydra", "Veres One", "Namecoin", "Tezos"]
+protocols: ["Aries", "Indy", "Ursa", "DIDComm", "Fabric", "Universal Resolver", "ION", "KERI", "Element", "Sawtooth", "DIDAuth", "Sidetree", "Universal Registrar", "Scuttlebot", "Besu", "Handshake", "DID Registry", "Verifier Api", "ENS"]
+tools: ["Element Block Explorer", "Global Standards Management Process", "Indicio TestNet", "DIDKit", "TreeLDR", "Personal Data Stores", "Mediator Agent", "Mobile Agent"]
+products: ["Custom Authz Servers", "Okta Identity Cloud", "Solid", "uPortlandia", "Hyland Credentials", "Qiqochat", "T-Mobile NEXT Identity Platform", "Cloud Identity Wallet", "Certification", "Aruba Health App", "EUDI Wallet", "Lissi Connect", "Lissi Wallet", "Rebase", "eIDAS Bridge", "VIDSigner", "Good Health Pass"]
+events: ["RWoT", "IIW", "Hyperledger Forum", "Planetwork", "IDC2018", "Graph Hack 2022"]
+content: ["Literature", "Media", "notes", "Transcript", "Adoption", "Code", "DecentralizeID", "History"]
+concepts: ["Self Sovereign Identity", "Trust Framework", "Web3", "Digital Twins", "Passwordless", "Metaverse", "Trusted Digital Ecosystems"]

_data/toml/blockchain-id2.toml

@@ -0,0 +1,169 @@
+["Remme Auth"]
+Link = ["https://remme.io/","https://github.com/Remmeauth"]
+Description = "Using a Hyperledger Sawtooth foundation, Remme implements a DPKI. Its blockchain playing the role of CA and supporting X.509 certificates either signed by the user, or an organization."
+Tags = ["blockchain-id","dpki","sawtooth","x-509"]
+
+["Juru"]
+Link = ["https://juru.io/","https://github.com/juru-identity/dbh17"]
+Description = "Juru Core is an open platform where you can securely store and manage your Identity and Reputation.\n\nToday Juru Core is built on Hyperledger Fabric and BigChainDB, and runs on a permissioned private blockchain. The contributing nodes are hosted by all major banks, which act as reputable gatekeeper.\n\nIt represents your identity and reputation using a smart contract, attributes can be added by the identity owner and are stored in hash form. Attributes and endorsements are formed of field sets, merkle-root hashes are used to allow sharing and verification of partial data"
+Tags = ["blockchain-id","hyperledger-fabric","bigchaindb"]
+
+["Shyft Network"]
+Link = ["https://www.shyft.network/","https://www.shyft.network/pdfs/Shyft-Network-Inc-Whitepaper_V3.1.pdf"]
+Description = "supports the collection of users’ data off-chain using traditional databases and collection strategies with the ability to provide attestation points for third-party utilization."
+Tags = ["blockchain-id","kyc"]
+
+["MyEarth"]
+Link = ["http://myearth.id/","http://myearth.id/wp-content/uploads/2018/04/Earth-ID-Updated-v1.1.pdf","https://imgur.com/EKULw96l.png"]
+Description = "MyEarthID will be the first decentralized Identity Management System (IMS) built on Hashgraph, where the user will own the ID that can be used for various purposes. Trust score kept based on user activity."
+Tags = ["hashgraph","myearth"]
+
+["Hu-manity.co"]
+Link = ["https://hu-manity.co/","https://hu-manity.org","https://hu-manity.science"]
+Description = "Hu-manty.science is responsible for researching the convergence of social good and technological innovation. To find new ways, where technology can solve real world problems.\n\nHu-manity.org is borderless and non-political and is responsible for championing choice and continuous consent to ensure people have a say as to how their data is used.\n\nHu-manity.co is the commercial part of the venture that is responsible for the creation and maintenance of the #My31 app."
+Tags = ["hu-manity","data-rights"]
+
+["Zulu Republic"]
+Link = ["https://www.zulurepublic.io/","https://www.zulurepublic.io/whitepaper/"]
+Description = "Zulu Republic is an ecosystem of blockchain tools, services, and platforms, designed as a place where people, businesses, and organizations can thrive on their own terms — a place where the real promise of the cryptocurrency revolution can be realized.Citizens of the Zulu Republic live anywhere and everywhere, united by a shared vision for a future of economic freedom and empowerment — of taking back our destinies from powerful centralized institutions."
+Tags = ["ztx","erc-20"]
+
+["Blocknify"]
+Link = ["https://blocknify.com/"]
+Description = "Blocknify for individuals is for freelancers and small business to sign and securely send their documents to be signed without their papers touching any server at any time."
+Tags = ["notarization"]
+
+["Handshake"]
+Link = ["https://handshake.org/","https://handshake.org/files/handshake.txt"]
+Description = "This document describes a proposal, operational functionality, and intention to replace centralized trusted internet infrastructure, with a decentralized Certificate Authority and globally unique namespace composed of a decentralized blockchain and cryptographic proofs backed by cryptoeconomic mechanisms. This construction enables the namespaces to point directly to a compact certificate representing a trust anchor which does not rely upon a single trusted authority to create attestations as in the existing federated Certificate Authority model. Handshake builds in compact verifiable proofs to ensure compatibility with embedded and mobile devices, with significant committed merkelized state proof-size and performance improvements."
+Tags = ["handshake","dCA","identification"]
+
+["Urbit"]
+Link = ["https://urbit.org/","https://urbit.org/docs/","https://news.ycombinator.com/item?id=11817721"]
+Description = "Urbit is a virtual city of general-purpose personal servers.\n\nWhat's a personal server? In a sense, you already have one. Your personal server is the combination of all the cloud services you use now.\n\nThis \"server\" is a mess. It's broken into 17 different fragments which are scattered all over the planet. You have no control at all over any of the pieces. The more we depend on Web services, the more we realize how unsustainable this situation is."
+Tags = ["urbit","self-sovereign"]
+
+["Vetri Global"]
+Link = ["https://vetri.global/"]
+Description = "VETRI is a self-sovereign, blockchain-based digital identity and personal data platform connecting identity owners with data consumers. Once completed, VETRI will operate as a not-for-profit, peer-to-peer, open source personal data management platform managed by the VETRI Foundation. The platform will consist of the VETRI wallet and the VETRI marketplace."
+Tags = ["data-market","blockchain-id","self-sovereign"]
+
+["Everest"]
+Link = ["https://everest.org/","https://everest.org/wp-content/uploads/2018/10/Everest_Whitepaper_Nov2018_v1.pdf"]
+Description = "Everest combines EverID, a user-centric self-sovereign identity solution, with EverWallet, a value transfer and document storage solution, and EverChain, a robust transaction system to create and record all system transactions. This product suite is based on blockchain technology and the cryptographic underpinnings of that system. The core focus of the Everest operating company is to create economic and social value."
+Tags = ["self-sovereign","blockchain-id"]
+
+["Agrello"]
+Link = ["https://www.agrello.io/"]
+Description = "The Agrello Platform is a dashboard where you can manage your identity, create contracts, sign the contracts using Agrello legally binding signature and have an overview of all of your agreements"
+Tags = ["identity","legal-contracts"]
+
+["Gataca"]
+Link = ["http://gatacaid.com/"]
+Description = "Gataca delivers fast and secure customer on-boarding experiences by removing the burden of identity verification compliance from businesses. Our products, Verification SDK and NoPassword Sign In, enable fully automated KYC processes and simplify GDPR compliance."
+Tags = ["kyc","gdpr-compliant","mit","identification"]
+
+["Clear.me"]
+Link = ["https://www.clear.me/"]
+Description = "Verified identity claims are digitally-signed by issuers, encrypted, and stored via the blockchain and decentralized systems. These claims could include complete know your customer (KYC) compliance, document authentication, or enable privacy through our unique anonymous verification protocol (AVP). We are also extending support for zero-knowledge proofs through zkSNARKs."
+Tags = ["",""]
+
+["POA Network"]
+Link = ["https://poa.network/","https://medium.com/poa-network/poa-network-how-honey-badger-bft-consensus-works-4b16c0f1ff94"]
+Description = "POA Network is an Ethereum-based platform that offers an open-source framework for smart contracts. POA Network is a sidechain to Ethereum utilizing Proof of Authority as its consensus mechanism. POA provides developers with the flexibility to code in Ethereum standards with the added benefits of POA Network's solutions to scalability and interoperability in blockchain networks."
+Tags = ["ethereum","poa","HBBFT"]
+
+["Essentia"]
+Link = ["https://essentia.one/","https://essentia.one/files/en/essentia_blockchain.pdf"]
+Description = "\"Essentia is a modular decentralized system of interactions and data management [1], which is based on a hybrid PoW/PoS consensus protocol.\" Has a ESS-ID component central to its makeup but not deeply described in pdf link."
+Tags = ["essentia"]
+
+["Digidentity"]
+Link = ["https://www.digidentity.eu/"]
+Description = "You can add an eHerkenning to your Digidentity, but you can also use eSGNG for digital signing. With your Digidentity you can log in to websites or digital services and conduct your business securely and simply.\n\nThe EU member states have agreed that, as from September 2018, European citizens and businesses must be able to log in to all Dutch public sector organisations using their own national login scheme. Thus, the European Union aims to regulate rendering electronic transactions within Europe easier and safer."
+Tags = ["UK","eidas","eu","blockchain-id"]
+
+["LifeID"]
+Link = ["https://lifeid.io/","https://lifeid.io/whitepaper.pdf"]
+Description = "All PII such as name, date of birth, current living address etc., are never stored on the lifeID Platform. This information is encrypted and only stored on a secure device such as the person’s phone. "
+Tags = ["self-sovereign","blockchain-id","did"]
+
+["Usechain"]
+Link = ["http://www.usechain.net/","https://www.usechain.net/usechain_en.pdf","https://www.usechain.net/usechain_tech_en.pdf"]
+Description = "Usechain is dedicated to developing a public chain based on mirror identity, establishing an ecosystem based on identity public chain, promoting the implementation of all sorts of blockchain applications that links blockchain addresses to verified real users, and realizing close integration between social credit, infrastructure, and commercial use."
+Tags = ["usechain","mirroridentity","blockchain-id"]
+
+["Ydentity"]
+Link = ["http://ydentity.org/","http://ydentity.org/doc/YdentityWhitePaper1.0.pdf"]
+Description = "This ERC20 token has a purchase mechanism under BTC or ETH and is designed to address the main elements of General Data Protection Regulation (GDPR) in a time of technological advancement when the consumer has never been more aware of the value of their data."
+Tags = ["eth-app","ydentity","blockchain-id"]
+
+["Digi-ID"]
+Link = ["https://www.digi-id.io/","https://github.com/digibyte/digiid-js","https://www.digi-id.io/documentation.html"]
+Description = "Digi-ID is an authentication method based on the security of the DigiByte blockchain. This allows you to log in to a website, application, building security and more by simply scanning or tapping on a QR code. Digi-ID does away with the need for usernames and password, or it can be used to compliment them for additional security."
+Tags = ["digi-id","digibyte","blockchain-id"]
+
+["0xcert"]
+Link = ["https://0xcert.org/","https://0xcert.org/technical-paper.pdf","https://0xcert.org/whitepaper.pdf","https://github.com/0xcert"]
+Description = "The vision of 0xcert is to provide an open protocol for standardized and certified non-fungible tokens to a wider tech audience​. With 0xcert, you can build on top of the non-fungible token standard, employing a complete toolset, development framework, and a set of conventions for various use cases​."
+Tags = ["eth-app","0xcert"]
+
+["Graphchain"]
+Link = ["https://github.com/MakoLab/graphchain","http://www.graphchain.io/MTSR2018.pdf","https://www.slideshare.net/sopekmir/graphchain"]
+Description = "Rather than trying to add Graphs and Ontologies to Blockchain, GraphChain starts with RDF database and then adds Blockchain features to the system.\n\nLegal Entity Identifier blockchained by a Hyperledger Indy implementation of GraphChain\n\nThe main idea behind GraphChain is to use blockchain mechanisms on top of an abstract RDF graphs. This paper presents an implementation of GraphChain in the Hyperledger Indy framework. The whole setting is shown to be applied to the RDF graphs containing information about Legal Entity Identifiers (LEIs)."
+Tags = ["graphchain","indy"]
+
+["T-Mobile Unveils Identity Platform: Next"]
+Link = ["https://cryptoslate.com/t-mobile-next-identity-platform/","https://github.com/hyperledger/sawtooth-next-directory","http://intelligentsystemsmonitoring.com/community/blockchain-community/t-mobile-unveils-the-next-identity-platform-a-blockchain-powered-database/"]
+Description = "Hyperledger Sawtooth NEXT Identity Platform\n\nIn a company with millions of users with differing levels of service, permission management is a considerable bottleneck. Regulations around user security and privacy add a further layer of complexity to such a system.\n\nNext Identity combines the functionality of a traditional database with the benefits of a centralized ledger. The system handles user identities, accesses, and approvals while retaining the integrity of an immutable blockchain."
+Tags = ["next","sawtooth"]
+
+["dock: Decentralized data exchange powered by Ethereum"]
+Link = ["https://dock.io/","https://dock.io/whitepaper"]
+Description = "By utilizing the secure Ethereum mainchain, data encryption, as well as a token model, the Dock protocol will allow users to take control of their data and exchange it between applications. The Dock token model will simultaneously motivate applications to exchange information by making it beneficial for both platforms involved in the transaction"
+Tags = ["dock","eth-app"]
+
+["Herdius"]
+Link = ["https://herdius.com/"]
+Description = "Herdius intends to build a new infrastructure layer on top of all blockchains. Through our vertically scalable chain and distributed virtual wallet network, Herdius aims to tackle identity & interoperability as well as create a crypto asset agnostic decentralized exchange."
+Tags = ["herdius"]
+
+["IXO Foundation"]
+Link = ["http://ixo.foundation/","https://ixo.foundation/wp-content/uploads/2018/08/ixo-Technical-White-Paper-w-Cover-Version-3.0-8-December-2017-1.pdf"]
+Description = "We are developing the mechanisms to share data-sets through software-mediated governance mechanisms, using the Ocean Protocol. Data resources will become locatable across any data store, using content-addressing, based on the Interplanetary Linked Data (IPLD) specification. The quality of these datasets will improve through the economic incentives and coordination capabilities of curation markets, as described by Simon De la Rouviere."
+Tags = ["ixo","data"]
+
+["Human Trust Protocol —HubToken"]
+Link = ["https://www.hubtoken.org/","https://www.hubtoken.org/images/hub-introduction.pdf","https://www.hubtoken.org/images/hub-white-paper.pdf"]
+Description = "Envision a world in which interactions and transactions between Internet strangers are supported by a new trust layer on the Internet enabled by the Human Trust Protocol. Reputation becomes self-sovereign under the control of users. With appropriate permissions, anyone will be able to assess the relevant trustworthiness of anyone else with whom they are about to engage, and users can transfer their trust from one community to any other. In short, there is an opportunity to rework the underlying incentive mechanisms of social networking and sharing economy services to create more trustworthy interaction."
+Tags = ["hubtoken"]
+
+["Holonet"]
+Link = ["https://simbol.io/","https://www.roadtovr.com/decentralizing-identity-in-vr-with-holonet-self-sovereign-identity/"]
+Description = "Holonet is an open source project that implements the Decentralized Identity Specifications for open web VR platforms like WebXR."
+Tags = ["holonet","uport","simbol"]
+
+["finID"]
+Link = ["http://finid.me/"]
+Description = "finID is a mobile wallet and a transparent  EU compliant Trusted Services Provider powered by blockchain infrastructure  supporting self sovereign identity (SSID). Our goal is to  make  SSID compatible with the existing EU eID infrastructure."
+Tags = ["eidas","eid","self-sovereign"]
+
+["Crayonic"]
+Link = ["https://www.crayonic.com"]
+Description = "Secure Digital Identity for People and Things\n\n Crayonic develops  hardware module  to secure digital identity.  We refer to it as Crayonic Identity Core  or CIC .  CIC hardware module  is running Crayonic Identity OS  firmware which will soon  be open sourced.  These two technologies combined are the basis for all identity projects within our company and soon it will be available to any one wishing to develop projects where secure identity plays a major role. This technology is protecting identities in all types of digital interactions:  person-to-person (P2P) , person-to-machine (P2M), machine-to-machine (M2M). \n\nRead further about technical details on Crayonic Pen -   our flagship  product built on top of CIC that fully utilizes its  machine learning algorithms in combination with cryptography to protect digital identity of a person. For machine-to-machine use case, please see our case study in IOT identity section. "
+Tags = ["eidas","crayonic"]
+
+["Blockpass"]
+Link = ["https://www.blockpass.org/","https://www.blockpass.org/downloads/BlockpassWhitepaper.v1.3.2.pdf"]
+Description = "Blockpass is an identity application for regulated services and the Internet of \n\nThings (IoT). It is positioned as a first step towards the development of a fully self-sovereign identity protocol for the Internet of Everything (IoE). An identity application is a software product that allows users to establish (verify), store, and manage identities. The identities that an identity application platform can store include those of people, things, and of other objects. The current, initial, release of the Blockpass app provides an identity solution for humans. Future releases will include solutions for devices and objects. \n\nA self-sovereign identity application is a platform where users can establish, store, and manage identities whilst maintaining full control over all data involved. Data collected to establish a self-sovereign identity is not stored on any central server. Instead, the data is passed to the verifier (be it a machine or a human) to view only for so long as is required to create the identity. When the verification is completed, the data is sent back to the user’s own personal device. "
+Tags = ["blockpass","iot","ssi"]
+
+["Ledgerstate"]
+Link = ["https://www.ledgerstate.io/","https://www.businesswire.com/news/home/20180125005600/en/Yoti-LedgerState-Showcase-Next-Generation-Blockchain-Technology-Transform"]
+Description = "Ledgerstate shapes their product to the end user's needs by not being tied to one specific decentralizing technology. Instead, they pick from the best technologies to create a tailored application for each use-case. Some of the technologies used include: Hashgraph, Yoti, Ethereum\n\nWe make decentralization and the blockchain simple, inclusive, and easy to implement into each company's ecosystem, putting forward the benefits for the end user.\n\nYoti, the digital identity platform, lets people create verified digital identities through their free smartphone app. The app uses facial recognition technology and a security team to match facial biometrics to approved photo IDs. These digital identities can then be written to a private ledger using an evolution of blockchain technology called Hashgraph."
+Tags = ["ledgerstate","yoti","hashgraph","eth"]
+
+["KeeeX Deploys Bitcoin BIP32 Self Sovereign Identity"]
+Link = ["https://keeex.me/","https://keeex.me/keeex-deploys-bitcoin-bip32-self-sovereign-identity/","https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki"]
+Description = "KeeeX seals trusted metadata in your files to ensure integrity, source and date. Our universal technology makes digital security accessible to everyone and allows you to protect all your file formats.\n\nYour data has value and is easily trackable thanks to a unique identifier. It embeds the link between your documents, your processes and event ledgers (Blockchain, off-chain register).\n\nThe most successful companies are those that have quality data in quantity to supply their analysis tools. You can qualify and insert context elements into your data to make better use of them.\n\nOur patented technology injects trust and exploitation metadata into your files without changing its appearance and format. You are no longer dependent on an infrastructure or Blockchain, all the proofs are in your data.\n\nFor the first time ever, BIP32 hierarchical deterministic wallets can be used to self define, publish, and revoke a cryptographic identity. This identity can be used to generate one time signatures for every item signed, hence achieving unprecedented signature security."
+Tags = ["keeex","data"]

_drafts/2019-03-05-VON.md

@@ -0,0 +1,55 @@
+---
+date: 2019-03-05
+title: "[Archived] Verfiable Organizations Network (VON) - BC Canada"
+description: "The Province of British Columbia, Province of Ontario and the Government of Canada have come together to create the initial services needed to establish VON."
+excerpt: >
+  an initiative by the government of British Columbia to create a trusted network of organizational data. It allows organizations to claim credentials that are part of their own digital identity, using a component called TheOrgBook that lists entities with their associated public verifiable claims.
+layout: single
+header:
+  image: /images/von-header.webp
+  teaser: /images/VON-teaser.webp
+sidebar:
+  nav: "didnav"  
+redirect_from:
+  - /hyperledger/indy/VON/
+  - indy-ecosystem/von/
+  - id-initiatives/indy-ecosystem/von.html
+  - indy-ecosystem/von
+  - indy-ecosystem/VON.html
+  - id-initiatives/indy-ecosystem/VON/
+  - public-sector/von/
+  - public-sector/canada/von/
+permalink: /government/canada/bcgov/von/
+redirect_from: /government/canada/von/
+canonical_url: 'https://decentralized-id.com/government/canada/von/'
+categories: ["Government","History"]
+tags: ["Verifiable Organizations Network","Indy","Verifiable Credentials","Canada","RWoT","IIW","hyperledger foundation"]
+last_modified_at: 2020-01-11
+published: false
+toc: false
+---
+
+>VON's founding members are governments who are, by law, trusted issuers of data about organizations. The Province of British Columbia, Province of Ontario and the Government of Canada have come together to create the initial services needed to establish VON. 
+>
+>VON's founders have delivered new Indy-based open source components which form VON's backbone. TheOrgBook is a publicly accessible repository of verifiable claims about organizations. VON-X enables services to verify and issue credentials. - [A Production Government Deployment of Hyperledger Indy- John Jordan, Stephen Curran.](https://hgf18.sched.com/event/G8rm/verifiable-organizations-network-a-production-government-deployment-of-hyperledger-indy-john-jordan-province-of-british-columbia-stephen-curran-cloudcompass-computing-inc)
+
+![]({{ site.baseurl }}/images/VON-Logo.webp){: .align-center}
+
+* [Verified Organization Network](https://vonx.io/) - "an initiative by the government of British Columbia to create a trusted network of organizational data. It allows organizations to claim credentials that are part of their own digital identity, using a component called TheOrgBook that lists entities with their associated public verifiable claims."
+  * [VON’s Blockchain Basis](https://vonx.io/getting_started/vons-blockchain-basis/)
+  * [A VON Overview](https://vonx.io/getting_started/von-overview/) - An overview of a VON Ecosystem
+  * [Clicky Things: What We Are Working On](https://vonx.io/clickythings/)
+
+{% include figure image_path="/images/von-info.png" alt="IACA May 2018" caption="[VON-Using-Blockchain-Technology IACA May 2018](https://www.iaca.org/wp-content/uploads/VON-Using-Blockchain-Technology.pdf)- Presentation" %}
+
+* [2017 - 09 - Demonstrating the Verifiable Organizations Network (VON)](https://docs.google.com/document/d/1wNnXdQKUtWnx--xw3VQ9Fr2TDa0kUNIBSMmFGR4uoMg/edit#heading=h.kphtj2c176xb)
+* [BC.gov Verifiable Organizations Network Demo](https://drive.google.com/open?id=1Ms2vKqTe-jVDpz5eWtQIqIz8Jl6TLbSE) (video)
+  * [BCGov Verifiable Organization Network - Impressive Client Demo - C...](https://www.continuumloop.com/bcgov-verifiable-organization-network/)
+  > One of my favourite client projects (Verifiable Organization Network) was demonstrated at last month’s Rebooting the Web of Trust conference in Santa Barbara. John Jordan runs an incredible project out of the Office of the CIO for British Columbia. I play a minor role provi...
+
+[Global Connections Made With AgentBook](https://vonx.io/news/2019-03-28-Global-Connection)
+  > Using AgentBook, approximately 30 people from South Africa, Europe, Canada and the USA were able to build and run their own Hyperledger Indy agent, connect with other agents using decentralized identifiers (DIDs) to establish a secure communication mechanism, and using that communication mechanism, send messages to each other. 
+
+[The VON IIW 28 Demonstration: IIWBook](https://vonx.io/how_to/iiwbook) - Now, with IIWBook, we’ve added a (literal) new layer by extending the core of AgentBook with the ability to exchange verifiable credentials. Even more exciting, through collaboration with Streetcred and Spark New Zealand, we have a mobile agent (or two!).
+  * [iiwbook.vonx.io](https://iiwbook.vonx.io)
+    > IIWBook is an authorization service that issues to requesting IIW attendees a Hyperledger Indy-style verifiable credential attesting to their attendance at IIW 28. This is part of a demonstration of self-sovereign identity in action presented by the Government of British Columbia and IIW.

_drafts/2019-03-05-sovrin-literature.md

@@ -0,0 +1,23 @@
+---
+date: 2019-03-05
+layout: single
+title: Sovrin Related Literature and Media
+excerpt: >
+  Digital identity is one of the oldest and hardest problems on the Internet. There is still no way to use digital credentials to prove our online identity the same way we do in the offine world. This is finally changing. First, the World Wide Web Consortium is standardizing the format of digitally-signed credentials. Secondly, public blockchains can provide decentralized registration and discovery of the public keys needed to verify digital signatures. These two steps pave the way to establish a global public utility for self-sovereign identity—lifetime portable digital identity that does not depend on any central authority.
+sidebar:
+  title: Decentralized-ID
+  nav: "sovnav"
+canonical_url: 'https://decentralized-id.com/organizations/sovrin-foundation/literature/'
+redirect_from:
+  - literature/Sovrin/
+  - literature/sovrin/
+  - id-initiatives/indy-ecosystem/literature.html
+  - indy-ecosystem/literature
+  - indy-ecosystem/literature/
+  - organizations/sovrin/literature/
+permalink: organizations/sovrin-foundation/literature/
+categories: ["Organizations"]
+published: false
+last_modified_at: 2019-07-13
+---
+

_drafts/2019-03-08-indy-github.md

@@ -0,0 +1,26 @@
+---
+date: 2019-03-08
+title: Indy Github Repositories
+excerpt: > 
+  "Hyperledger Indy provides tools, libraries, and reusable components for providing digital identities rooted on blockchains or other distributed ledgers so that they are interoperable across administrative domains, applications, and any other silo."
+layout: single
+permalink: blockchain/hyperledger/indy/github/
+canonical_url: 'https://decentralized-id.com/blockchain/hyperledger/indy/github/'
+redirect_from:
+  - organizations/hyperledger/indy/github/
+  - hyperledger/indy/github/
+  - id-initiatives/indy-ecosystem/indy-github/
+  - indy-ecosystem/github
+  - id-initiatives/indy-ecosystem/indy-github.html
+sidebar:
+  title: Decentralized-ID
+  nav: "sovnav"
+toc: false
+categories: ["Hyperledger","Code"]
+tags: ["Hyperledger","Code","Indy",]
+last_modified_at: 2019-03-08
+published: false
+---
+
+<!-- Every company or organization using indy code should be listed in tags, above -->
+

_drafts/2019-03-27-cryptonomica.md

@@ -0,0 +1,63 @@
+---
+date: 2019-03-27
+title: Cryptonomica
+description: Cryptonomica.net is an identity verification service based on OpenPGP and Ethereum with legal framework and online dispute resolution for electronic contracts from London-based court of arbitration
+excerpt: >
+  We make verification of key owner's identity and store data about this verification: who, when, using which document made verification. And unlike in 'Web of trust' there is an established procedure for key verification, i.e. known rules according to witch identity of the key owner have to be proven.
+layout: single
+toc: false
+header:
+  image: /images/cryptonomica-header.webp
+  caption: "[cryptonomica.net](https://cryptonomica.net)"
+  teaser: /images/cryptonomica-teaser.webp
+permalink: /blockchain/ethereum/cryptonomica/
+canonical_url: 'https://decentralized-id.com/blockchain/ethereum/cryptonomica/'
+redirect_from: 
+  - id-initiatives/ethereum/cryptonomica
+  - id-initiatives/ethereum/cryptonomica/
+categories: ["Blockchain ID"]
+tags: ["Ethereum","PGP","Blockchain"]
+last_modified_at: 2019-07-11
+published: false
+---
+
+## Cryptonomica 
+[![](https://i.imgur.com/moVyrrt.png)](https://cryptonomica.github.io)
+
+ * [Cryptonomica.net](https://cryptonomica.net) is an identity verification service based on [OpenPGP](https://en.wikipedia.org/wiki/Pretty_Good_Privacy) and [Ethereum](https://www.ethereum.org) with legal framework and online dispute resolution for electronic contracts from London-based [court of arbitration](https://cryptonomica.net/#!/arbitration) 
+
+* [the Cryptonomica Whitepaper](https://github.com/Cryptonomica/cryptonomica/wiki/Cryptonomica-White-Paper#the-problem):
+> Existing systems of keys-based digital signature for documents are based on a personal visit to a certification center.
+>
+> The key pair for the client is in many countries created by the certification center, and given to the client. In this case, a copy of the user's private key can remain in the certification center, i.e. not only user can have access to it. This problem is often not even realized by users.
+Often the keys for the client-bank systems are created this way.
+>
+> Although signature verification is reliable only if no one else except the owner has access to private key.
+
+[...]
+
+>### Our Solution
+>
+>PGP's ["Web of trust"](https://en.wikipedia.org/wiki/Web_of_trust) was not a success, because, as stated [Wikipedia](https://en.wikipedia.org/wiki/Pretty_Good_Privacy#Web_of_trust):
+> Users have been willing to accept certificates and check their validity *manually* or to simply accept them. *No satisfactory solution has been found for the underlying problem*
+>
+>We offer exactly the solution for this problem that is mentioned in Wikipedia as not yet found. We deny automatic key check, we are offering the user to check and download each key manually.
+>
+>We make verification of key owner's identity and store data about this verification: who, when, using which document made verification. And unlike in ['Web of trust'](https://en.wikipedia.org/wiki/Pretty_Good_Privacy#Web_of_trust) there is an established procedure for key verification, i.e. known rules according to witch identity of the key owner have to be proven.
+>
+>The user can make the information of the key or keys in the database available to all other users of the database, or available only for specified users or user group. Accordingly database user will have access to data about keys of others users, which is open to all users or shared with him, (for some cases, i.e. for arbitrators, including scans on the paper documents)
+>
+>And we offer for the market the first legally relevant global system of public key's certification, that can be run around the world, or more precisely in all states where [Hague Convention Abolishing the Requirement for Legalisation for Foreign Public Documents 1961](https://www.hcch.net/en/instruments/conventions/full-text/?cid=41) ([Apostille Convention](https://en.wikipedia.org/wiki/Apostille_Convention)) and [United Nations Convention on the Recognition and Enforcement of Foreign Arbitral Awards 1958](https://www.uncitral.org/pdf/english/texts/arbitration/NY-conv/New-York-Convention-E.pdf) ([New York Convention 1958](https://en.wikipedia.org/wiki/Convention_on_the_Recognition_and_Enforcement_of_Foreign_Arbitral_Awards)) are recognized.
+>
+>We can provide a legal mechanism for recognizing digitally signed contracts in almost every country: every digital contract in the need can be "transformed" in arbitral award recognized under [The Convention on the Recognition and Enforcement of Foreign Arbitral Awards](https://www.uncitral.org/pdf/english/texts/arbitration/NY-conv/New-York-Convention-E.pdf), and using modern technologies (web-server, databases, videoconferencing, e-mail) make [international arbitration](https://en.wikipedia.org/wiki/International_arbitration) affordable even for small business and individual clients.
+
+
+## Github Repos
+* [Cryptonomica/cryptonomica](https://github.com/Cryptonomica/cryptonomica) - Cryptonomica keys server
+* [Cryptonomica/cryptonomica.github.io](https://github.com/Cryptonomica/cryptonomica.github.io) - Cryptonomica frontend
+* [Cryptonomica/arbitration-rules](https://github.com/Cryptonomica/arbitration-rules) - Cryptonomica Arbitration Rules
+* [Cryptonomica/dappathon-tlv](https://github.com/Cryptonomica/dappathon-tlv)
+* [Cryptonomica/Ethereum-IdentityVerification](https://github.com/Cryptonomica/Ethereum-IdentityVerification) - Indentity verification and KYC for Ethereum blockchain
+* [Cryptonomica/ethnode.cryptonomica.net](https://github.com/Cryptonomica/ethnode.cryptonomica.net) - Ethereum node with API on nodejs and web3.js
+* [Cryptonomica/Ethereum-IdentityProof](https://github.com/Cryptonomica/Ethereum-IdentityProof) - Smart contract for Ethereum's account owner verification using Cryptonomica.net
+* [Cryptonomica/international-arbitration-law](https://github.com/Cryptonomica/international-arbitration-law) - Repository for collecting information about international arbitration law and practice

_drafts/2019-06-03-indieweb-dev-on-did.md

@@ -0,0 +1,290 @@
+---
+date: 2019-06-03
+title: "FreeNode IRC #indieweb-dev on IIW RWoT and DID's"
+description: "Conversation about RWoT and DIDs at #indieweb-dev on Freenode"
+excerpt: >
+  OAuth has become the de facto standard for authorization and authentication on the web. Nearly every company with an API used by third party developers has implemented OAuth to enable people to build apps on top of it.
+
+  While OAuth is a great framework for this, the way it has ended up being used is much more centralized and closed than prior efforts like OpenID 1. Every service that spins up an OAuth-enabled API ends up being its own isolated system. For example, if I want to build an app that can read someone's step count from FitBit, I have to first go register as a developer on FitBit's website in order to get API keys to use with their OAuth API
+date: "2019-06-03T11:22:33-23:00"
+categories: ["Web Standards","Decentralized Web"]
+tags: [P2P", "IndieAuth", "IndieWebRebooting WoT", "IIW", "DIDW3COAuth]
+permalink: /decentralized-web/indieweb-on-did/
+redirect_from: /specs-standards/indieweb-dev-on-did/
+header:
+  image: /images/indieweb-header.webp
+  teaser: /images/indieweb-icon_31635_white.webp
+last_modified_at: 2019-06-03
+---
+
+## Contents
+* [Links](#links)
+  * [In-Chat Links](#in-chat-links)
+    * [Peer to Peer DIDs](#peer-to-peer-dids)
+    * [IndieAuth](#indieauth)
+* [#indieweb-dev on RWoT-DIDs 2019-03-02](#indieweb-dev-on-rwot-dids-2019-03-02)
+* [#indieweb-dev on IIW 2018-08-19](#indieweb-dev-on-iiw-2018-08-19)
+
+## Links 
+
+* [indieweb.org/discuss#Join_Discussions](https://indieweb.org/discuss#Join_Discussions)
+* [Matrix bridge to #dev channnel chat (via riot.im)](https://riot.im/develop/#/room/#freenode_#indieweb-dev:matrix.org)
+* [#indieweb-dev on DIDs 2019-03-02-chat log](https://freenode.logbot.info/indieweb-dev/20190302)
+* [#indieweb-dev on IIW 2018-08-19-chat log](https://freenode.logbot.info/indieweb-dev/20180819)
+
+### Related
+
+* [The Decentralized Identifier (DID) in the DNS](https://datatracker.ietf.org/doc/draft-mayrhofer-did-dns/)
+
+### In-chat Links
+
+* https://docs.ipfs.io/guides/concepts/dnslink/
+  * DNSLink uses DNS TXT records to map a domain name (like ipfs.io) to an IPFS address. Because you can edit your DNS records, you can use them to always point to the latest version of an object in IPFS (remember that an IPFS object’s address changes if you modify the object). Because DNSLink uses DNS records, the names it produces are also usually easy to type and read.
+  * A DNSLink address looks like an IPNS address, but it uses a domain name in place of a hashed public key:
+* [indieweb.org/checkin#Posting_checkins_from_clients](https://indieweb.org/checkin#Posting_checkins_from_clients)
+
+#### Peer-to-Peer DIDs
+
+* [Comparing WebIDs and DIDs](https://docs.google.com/document/d/1SwSWIOOujRCdrwVyrKojwAvQVp-wJJ9P6NBiuQ3bDN4/edit)
+* [Peer to Peer DIDs](https://github.com/WebOfTrustInfo/rwot8-barcelona/blob/master/topics-and-advance-readings/P2P-DID.md)
+* [dhh1128.github.io/peer-did-method-spec/index.html](https://dhh1128.github.io/peer-did-method-spec/index.html)
+    * [#grafting-peer-dids-into-another-did-method-namespace](https://dhh1128.github.io/peer-did-method-spec/index.html#grafting-peer-dids-into-another-did-method-namespace) 
+
+#### IndieAuth
+
+{% include video id="EeCNlB7v08I" provider="youtube" %}
+
+* [indieauth.spec.indieweb.org](https://indieauth.spec.indieweb.org)  
+  * IndieAuth is an identity layer on top of OAuth 2.0 [RFC6749], primarily used to obtain an OAuth 2.0 Bearer Token [RFC6750] for use by [Micropub] clients. End-Users and Clients are all represented by URLs. IndieAuth enables Clients to verify the identity of an End-User, as well as to obtain an access token that can be used to access resources under the control of the End-User.  
+* [W3C Working Group Note 23 January 2018](https://w3.org/TR/2018/NOTE-indieauth-20180123)
+  * An IndieAuth implementation can implement one or more of the roles of an IndieAuth server or client. This section describes the conformance criteria for each role.
+  * Listed below are known types of IndieAuth implementations.
+  * 2.1.1 Authorization Endpoint
+    * An IndieAuth Authorization Endpoint is responsible for obtaining authorization or authentication consent from the end user and generating and verifying authorization codes.
+  * 2.1.2 Token Endpoint
+    * An IndieAuth Token Endpoint is responsible for generating and verifying OAuth 2.0 Bearer Tokens.
+  * 2.1.3 Micropub Client
+    * A Micropub client will attempt to obtain an OAuth 2.0 Bearer Token given an IndieAuth profile URL, and will use the token when making Micropub requests.
+  * 2.1.4 IndieAuth Client
+    * An IndieAuth client is a client that is attempting to authenticate a user given their profile URL, but does not need an OAuth 2.0 Bearer Token.
+* [aaronparecki.com - Oath for the Open Web](https://aaronparecki.com/2018/07/07/7/oauth-for-the-open-web)
+  * OAuth has become the de facto standard for authorization and authentication on the web. Nearly every company with an API used by third party developers has implemented OAuth to enable people to build apps on top of it.
+  * While OAuth is a great framework for this, the way it has ended up being used is much more centralized and closed than prior efforts like OpenID 1. Every service that spins up an OAuth-enabled API ends up being its own isolated system. For example, if I want to build an app that can read someone's step count from FitBit, I have to first go register as a developer on FitBit's website in order to get API keys to use with their OAuth API
+* [indieweb/indieauth #23#issuecomment-414152219](https://github.com/indieweb/indieauth/issues/23#issuecomment-414152219)
+  * 21:13 **Loqi** - [Zegnat] The table above has been updated with new statistics. This shows that `rel="manifest"` are equally as likely to be found on client pages as `h-x-app`. This Web App Manifests may be a more logical alternative than previously realised.
+* [indieweb/wordpress-indieauth #127/files#diff-F81F3DFF36BF04B7A070D642C858E883](https://github.com/indieweb/wordpress-indieauth/pull/127/files#diff-F81F3DFF36BF04B7A070D642C858E883)
+  * **dshanske** commented on Feb 24- Returns a jf2 h-card in the token return on verification so the client can display name and user avatar on an application
+
+## indieweb-dev on RWoT-DIDs 2019-03-02
+
+[![](https://imgur.com/A4IPjIi.png)](https://freenode.logbot.info/indieweb-dev/20190302)
+
+[#indieweb-dev on DIDs 2019-03-02-chat log](https://freenode.logbot.info/indieweb-dev/20190302)
+* 16:14 [@sandhawke](https://twitter.com/sandhawke) - I don't think I have that level of interest to attend IIW - but I happen to be at RWoT right now, and that seems like a sweet spot for me to work on while I'm here. I just made this:
+* 16:14 [@sandhawke](https://twitter.com/sandhawke) - [Comparing WebIDs and DIDs](https://docs.google.com/document/d/1SwSWIOOujRCdrwVyrKojwAvQVp-wJJ9P6NBiuQ3bDN4/edit)
+* 16:14 [@sandhawke](https://twitter.com/sandhawke) - which should perhaps have a column for IndieAuth
+* 16:15 [@sandhawke](https://twitter.com/sandhawke) -although it's not quite the same type of thing, it kina is
+* 16:15 [@sandhawke](https://twitter.com/sandhawke) -Anyway - DIDs seem to have a lot of momentum, so I'm inclined to fit webids & indieauth, which I much prefer, into the DID world
+* 16:16 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) -DIDs lost me when they make the assumption that blockchains are the only resolution mechanism
+* 16:16 [@sandhawke](https://twitter.com/sandhawke) -In person everyone here denies that, and they seem to welcome other mechanisms.
+* 16:17 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) -any examples yet?
+* 16:17 [@sandhawke](https://twitter.com/sandhawke) -Yes, "peer"
+* 16:17 [@sandhawke](https://twitter.com/sandhawke) -[Peer to Peer DIDs](https://github.com/WebOfTrustInfo/rwot8-barcelona/blob/master/topics-and-advance-readings/P2P-DID.md)
+* 16:18 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) -Even just reading w3c-ccg.github.io/did-primer/#the-format-of-a-did-0 they casually drop a mention of blockchain as the only option
+* 16:18 [@sandhawke](https://twitter.com/sandhawke) -[dhh1128.github.io/peer-did-method-spec/index.html](https://dhh1128.github.io/peer-did-method-spec/index.html)
+* 16:18 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) -I'd recommend revising that sentence if they want to not have people think that
+* 16:18 [@sandhawke](https://twitter.com/sandhawke) -Yes, I know, and they know.
+* 16:19 [@sandhawke](https://twitter.com/sandhawke) -But the best solution IMHO is just deploy something as nice and simple as indieauth
+* 16:19 [@sandhawke](https://twitter.com/sandhawke) -But I agree there's a culture clash
+* 16:19 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) -From what I understand they have no interest in relying on DNS so that takes them completely out of the realm of working with current browsers or anything like IndieAuth
+* 16:20 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) -in theory you could make a dns resolver method for did and use domain names as the identifier and get close to something like IndieAuth
+* 16:20 [@sandhawke](https://twitter.com/sandhawke) -Right.
+* 16:21 [@sandhawke](https://twitter.com/sandhawke) -And it doesn't matter if they want that
+* 16:21 [@sandhawke](https://twitter.com/sandhawke) -The end-users benefit
+* 16:22 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) -The other thing missing from DID is the authorization framework that comes with IndieAuth since it's built on OAuth 2.0
+* 16:22 [@sandhawke](https://twitter.com/sandhawke) -They're working on DID-Auth, trying to figure out what that means. There are two papers about that this weekend, one from Microsoft.
+* 16:23 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) -The DID and OIDC groups weren't even getting along very well and while OIDC is way overkill for what we use IndieAuth for, its still more similar to IndieAuth than blockchain stuff is
+* 16:24 [@sandhawke](https://twitter.com/sandhawke) -I agree re "way overkill", so I want to show how simple it can be. They're not the first "way overkill" people in identity / authn / authz.
+* 16:25 [@sandhawke](https://twitter.com/sandhawke) -I mean -- maybe I should just go watch netflix -- this might be a silly waste of time, but I'm here, and it's a lot of smart and motivate people, so I can't help but wonder about trying to steer them a bit.
+* 16:26 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) -I would be very interested in what you come up with. I haven't had much luck in any of these conversations so far
+* 16:27 [@sandhawke](https://twitter.com/sandhawke) -fair enough :-) Is indieauth.spec.indieweb.org pretty much up-to-date with your thinking?
+* 16:28 [@sandhawke](https://twitter.com/sandhawke) -( sad not to see a change log from https://w3.org/TR/2018/NOTE-indieauth-20180123 )
+* 16:28 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) -Yep and https://aaronparecki.com/2018/07/07/7/oauth-for-the-open-web is a good explanation too
+* 16:28 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - oh did I forget a change log section? I'll try to add that
+* 16:29 [@sandhawke](https://twitter.com/sandhawke) - +1
+* 16:30 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - If video is more your thing, I gave this talk at the W3C workshop [youtube.com/watch?v=EeCNlB7v08I](https://youtube.com/watch?v=EeCNlB7v08I)
+* 16:30 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - its nice and short
+* 16:34 [@sandhawke](https://twitter.com/sandhawke) - cool, pulling out headphones and wathching...
+* 16:45 [@sandhawke](https://twitter.com/sandhawke) - ha - amused to hear Wendy's voice moderating the session
+* 16:52 [@sandhawke](https://twitter.com/sandhawke) - I don't understand the value of public apps being identified
+* 16:52 [@sandhawke](https://twitter.com/sandhawke) - (good video)
+* 16:59 [@sandhawke](https://twitter.com/sandhawke) - I guess there's some attack it's intended prevent.
+* 17:01 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - Yeah that's from OAuth. Prevents redirect interception by registering the redirect URL, and also helps the user not get phished
+* 20:28 [[jacky]](https://indieweb.org/User:Jacky.wtf) - tbh as much as I'm for the whole DiD and what not
+* 20:28 [[jacky]](https://indieweb.org/User:Jacky.wtf) - DNS is _not_ going anywhere
+* 20:29 [[jacky]](https://indieweb.org/User:Jacky.wtf) - as least for the people I aim to build for (like myself and then family to an extent)
+* 20:29 [[jacky]](https://indieweb.org/User:Jacky.wtf) - DNS is straight-forward and more-or-less "reliable"
+* 20:30 [[jacky]](https://indieweb.org/User:Jacky.wtf) - the only other idea I've seen thus far that was 'usable' has been [docs.ipfs.io/guides/concepts/dnslink](https://docs.ipfs.io/guides/concepts/dnslink)
+* 20:30 [[jacky]](https://indieweb.org/User:Jacky.wtf) - (which still relies on DNS but one could augment a local DNS resolver to intercept these lookups)
+* 20:51 [[tantek]](https://indieweb.org/User:Tantek.com) - listens intently. (also welcome (back) sandhawke!)
+* 20:55 [[jacky]](https://indieweb.org/User:Jacky.wtf) - I don't know / wonder if a solution that's speech-friendly will arise
+* 20:55 [[jacky]](https://indieweb.org/User:Jacky.wtf) - like if I can't say it out loud, it's incredibly hard to share
+* 20:55 [[jacky]](https://indieweb.org/User:Jacky.wtf) - sure, I can just share a link
+* 21:00 [[tantek]](https://indieweb.org/User:Tantek.com) - speechfriendly++
+* 21:00 [[Loqi]](https://indieweb.org/Loqi) - speechfriendly has 1 karma over the last year
+* 21:05 [[swentel]](https://indieweb.org/User:Realize.be) - [tantek], yeah, I figured that it might be a useful link for people looking for my 'main' feed
+* 21:06 [[swentel]](https://indieweb.org/User:Realize.be) - also because currently in aperture, rel="feed" is ignored. So if people search feeds on realize.be, they will get microformats, but that's on my homepage, which is kind of useless
+* 21:06 [[swentel]](https://indieweb.org/User:Realize.be) - which makes me wonder whether I should remove microformat markup on the homepage maybe
+* 21:08 [[swentel]](https://indieweb.org/User:Realize.be) - (to be more specific, xray underneath ignores rel="feed", but that's technical detail)
+* 21:09 [[swentel]](https://indieweb.org/User:Realize.be) - other than that, fun experiments today with checkins and geocache, I'm getting excited by the location stuff in indigenous :)
+* 21:10 [[jacky]](https://indieweb.org/User:Jacky.wtf) - hm so I saw a question about indieauth and "data", like in comparison to how OAuth2 gives you a blob of info post login
+* 21:11 [[jacky]](https://indieweb.org/User:Jacky.wtf) - IndieAuth doesn't have to do that thanks to MF2; you can just pull what you need from their h-card but now I wonder
+* 21:11 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - jacky: we actually started experimenting with this
+* 21:11 [[jacky]](https://indieweb.org/User:Jacky.wtf) - would it make sense to show a specialized page in the value of the 'me' page? that changes b/c on the authenticated app?
+* 21:11 [[jacky]](https://indieweb.org/User:Jacky.wtf) - aaronpk: oh?
+* 21:12 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - trying to remember where we documented it? it was a quick thing during IWC Austin
+* 21:12 [[jacky]](https://indieweb.org/User:Jacky.wtf) - oh man
+* 21:12 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - GWG added it to wordpress and I added it to Quill
+* 21:12 [[swentel]](https://indieweb.org/User:Realize.be) - hmm, GWG opened an issue for me indigenous, there's probably a link there, let me check
+* 21:12 [[swentel]](https://indieweb.org/User:Realize.be) - indieweb/indieauth #31
+* 21:12 [[Loqi]](https://indieweb.org/Loqi) - [dshanske] #31 Returning Profile Data
+* 21:13 [[jacky]](https://indieweb.org/User:Jacky.wtf) - nice
+* 21:13 [[swentel]](https://indieweb.org/User:Realize.be) - that's at least the indieauth thing
+* 21:13 [[swentel]](https://indieweb.org/User:Realize.be) - maybe there's more?
+* 21:13 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - yep thanks
+* 21:13 [[jacky]](https://indieweb.org/User:Jacky.wtf) - [indieweb/indieauth #23#issuecomment-414152219](https://github.com/indieweb/indieauth/issues/23#issuecomment-414152219)
+* 21:13 [[Loqi]](https://indieweb.org/Loqi) - [Zegnat] The table above has been updated with new statistics. This shows that `rel="manifest"` are equally as likely to be found on client pages as `h-x-app`. This Web App Manifests may be a more logical alternative than previously realised.
+* 21:13 [[Loqi]](https://indieweb.org/Loqi) - Further devel...
+* 21:13 [[GWG]](https://indieweb.org/User:David.shanske.com) - Although Zegnat pointed out it should be nickname not name
+* 21:13 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - hrm I don't think it should be "nickname"
+* 21:13 [[Zegnat]](https://indieweb.org/User:Vanderven.se_martijn) - Hardly “should be”
+* 21:14 [[jacky]](https://indieweb.org/User:Jacky.wtf) - that makes sense
+* 21:14 [[jacky]](https://indieweb.org/User:Jacky.wtf) - b/c name is so vague
+* 21:14 [[jacky]](https://indieweb.org/User:Jacky.wtf) - vs 'username', 'nickname', 'given name'
+* 21:14 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - display name is more accurate
+* 21:14 [[Zegnat]](https://indieweb.org/User:Vanderven.se_martijn) - More like: I ** wondered if it should be more clear to expect a “display name” rather than a personal name (which I feel `name` is often used for)** 
+* 21:15 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - the other reason for doing this is it means it's easier to return private/sensitive profile data to apps without having to have a way to serve protected data from your home page
+* 21:15 [[GWG]](https://indieweb.org/User:David.shanske.com) - aaronpk, I agree with the idea and am willing to change to display name. It is still new and easy to adjust.
+* 21:15 [[jacky]](https://indieweb.org/User:Jacky.wtf) - aaronpk: right 
+* 21:15 [[Zegnat]](https://indieweb.org/User:Vanderven.se_martijn) - aaronpk, yes, that was a bit part of my reasoning over on GitHub :)
+* 21:15 [[Zegnat]](https://indieweb.org/User:Vanderven.se_martijn) - please comment with more details if you think I didn’t make that clear
+* 21:16 [[Zegnat]](https://indieweb.org/User:Vanderven.se_martijn) - s/a bit/a big/
+* 21:16 [[GWG]](https://indieweb.org/User:David.shanske.com) - If someone gives it another +1 I'll go make a PR
+* 21:16 [[swentel]](https://indieweb.org/User:Realize.be) - Hmm, I like name tbh :)
+* 21:16 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - I also don't necessarily think "name" is a bad property for this, just need to make it clear that there is no expectation of a "real name" or "full name"
+* 21:16 [[swentel]](https://indieweb.org/User:Realize.be) - as it's consistent then
+* 21:16 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - there isn't any expectation of that in this stuff anyway so I don't really see the problem
+* 21:17 [[Zegnat]](https://indieweb.org/User:Vanderven.se_martijn) - Except I felt there may have been an expectation of that in JF2, aaronpk. And the issue seemed to suggest using JF2 cards.
+* 21:17 [[GWG]](https://indieweb.org/User:David.shanske.com) - aaronpk, what if someone requests the theoretical profile scope?
+* 21:17 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - Zegnat: what gave you the idea of that from jf2? jf2 shouldn't be defining any new semantics on top of the mf2 properties
+* 21:18 [[swentel]](https://indieweb.org/User:Realize.be) - GWG, do you have a link to the commit in wordpress?
+* 21:18 [[swentel]](https://indieweb.org/User:Realize.be) - Just for inspiration
+* 21:18 [[Zegnat]](https://indieweb.org/User:Vanderven.se_martijn) - “full/formatted name of the person or organisation” is the mf2 definition
+* 21:18 [[Zegnat]](https://indieweb.org/User:Vanderven.se_martijn) - Also, it feels to me like people have been using `name` on their h-cards a lot for full name currently
+* 21:19 [[GWG]](https://indieweb.org/User:David.shanske.com) - [indieweb/wordpress-indieauth #127/files#diff-F81F3DFF36BF04B7A070D642C858E883](https://github.com/indieweb/wordpress-indieauth/pull/127/files#diff-F81F3DFF36BF04B7A070D642C858E883)
+* 21:19 » [[Zegnat]](https://indieweb.org/User:Vanderven.se_martijn) now has 3–5 seconds IRC delay, so discussing is going to be hard
+* 21:19 [[swentel]](https://indieweb.org/User:Realize.be) - thanks
+* 21:20 [[tantek]](https://indieweb.org/User:Tantek.com) - hmm - we've been through this renaming loop before. name is display name, no need to ever change to "display name".
+* 21:21 [[Zegnat]](https://indieweb.org/User:Vanderven.se_martijn) - I do not want to change the name property in mf2 here [tantek]. I just want it to be clear that the minimal info returned from an IndieAuth endpoint is a display name specifically (and further names (?) may be available under something like a profile scope)
+* 21:21 [[tantek]](https://indieweb.org/User:Tantek.com) - in the past other formats have tried to make distinctions between "display name" "full name" etc. and it just results in bad UX. in practice people enter into "name" what they want displayed. period. no need to futz or handwring about bikeshedding the property. it works
+* 21:22 [[tantek]](https://indieweb.org/User:Tantek.com) - Zegnat, calling something display name then implies that other "name"s are not "display" and it just confuses people (implementers, users etc.)
+* 21:22 [[swentel](https://github.com/swentel) - GWG, I've documented my experimental geo:uri;h=card on [indieweb.org/checkin#Posting_checkins_from_clients]](https://indieweb.org/checkin#Posting_checkins_from_clients) (but I'm not sure if that's the right place :/) **** 
+* 21:22 [[tantek]](https://indieweb.org/User:Tantek.com) - there is never a need in practice to ever "be clear" about "is a display name specifically"
+* 21:22 [[swentel]](https://indieweb.org/User:Realize.be) - just wanted to make sure it exists at least
+* 21:22 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - side note: openid connect has "name", "family_name", "given_name", "middle_name" and "nickname" all under the "profile" scope, and tbh is an example of what tantek is talking about where the only one actually used is just "name" 
+* 21:22 [[tantek]](https://indieweb.org/User:Tantek.com) - that's a hypothetical concern from which no one has ever documented any actual harm ever
+* 21:22 [[GWG]](https://indieweb.org/User:David.shanske.com) - swentel, link to that under Micropub experimental as well.
+* 21:23 [[swentel]](https://indieweb.org/User:Realize.be) - GWG, on micropub extensions?
+* 21:23 [[GWG]](https://indieweb.org/User:David.shanske.com) - Swentel, yes, excuse me.
+* 21:23 [[swentel]](https://indieweb.org/User:Realize.be) - Ok, maybe it's better to move it there completely
+* 21:24 [[tantek]](https://indieweb.org/User:Tantek.com) - aaronpk is correct, and opendid connect even there screwed up (inserted Western-centric assumptions by I'm sure the 100% Western white male openid connect "designers) by renaming vCard's "additional name" into "middle_name".
+* 21:24 [[tantek]](https://indieweb.org/User:Tantek.com) - openidconnect--
+* 21:24 [[Loqi]](https://indieweb.org/Loqi) - openidconnect has -1 karma over the last year
+* 21:24 [[GWG]](https://indieweb.org/User:David.shanske.com) - Do we have a theoretical use case for more than minimal data yet?
+* 21:24 [[tantek]](https://indieweb.org/User:Tantek.com) - westerncentricassumptions--
+* 21:24 [[Loqi]](https://indieweb.org/Loqi) - westerncentricassumptions has -1 karma over the last year
+* 21:26 [[GWG]](https://indieweb.org/User:David.shanske.com) - I return name, url, and photo because that was the minimum needed for a client to display. I am happy to return more behind a profile scope the day someone wants it
+* 21:26 [[tantek]](https://indieweb.org/User:Tantek.com) - (note: " middle" is a layout/order specific label, not a semantic. in the past these same kinds of 100% Western white male format designers would have "first_name" "middle_name" "last_name", there's plenty of examples of bad old dead formats with that, programming examples in various "5 minutes to make your own social network!" type stuff etc.) 
+* 21:26 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - GWG: I'd hold off on anything further with this until we get more publishers and consumers of it
+* 21:27 [[jacky]](https://indieweb.org/User:Jacky.wtf) - r^
+* 21:27 [[GWG]](https://indieweb.org/User:David.shanske.com) - aaronpk, I planned on it
+* 21:27 [[GWG]](https://indieweb.org/User:David.shanske.com) - I just was curious about uses
+* 21:27 [[GWG]](https://indieweb.org/User:David.shanske.com) - I have bigger problems right now
+* 21:27 [[tantek]](https://indieweb.org/User:Tantek.com) - swentel - I think if you put rel="alternate" on the link to your h-feed page then it may be discoverable. I believe rel=feed was deprecated (even dropped by WHATWG HTML for lack of interest / implementations)
+* 21:28 [[swentel]](https://indieweb.org/User:Realize.be) - [tantek], oh, interesting, I'll give that a try yes!
+* 21:28 [[GWG]](https://indieweb.org/User:David.shanske.com) - Really? I just added a bunch of rel feeds
+* 21:28 [[GWG]](https://indieweb.org/User:David.shanske.com) - I can't keep up
+* 21:29 [[GWG]](https://indieweb.org/User:David.shanske.com) - I thought alternate was an alternative view of the same page and feed was a different page
+* 21:29 [[GWG]](https://indieweb.org/User:David.shanske.com) - What is rel-feed?
+* 21:29 [[Loqi]](https://indieweb.org/Loqi) - rel-feed is the standard for linking to multiple (potentially alternative) h-feeds from a site's homepage using the code rel="feed" on those links indieweb.org/rel-feed
+* 21:30 [[jacky]](https://indieweb.org/User:Jacky.wtf) - yeah same
+* 21:30 [[jacky]](https://indieweb.org/User:Jacky.wtf) - re: G WG
+* 21:31 [[tantek]](https://indieweb.org/User:Tantek.com) - no feed discovery is done via rel=alternate type="insert your feed mime type here"
+* 21:31 [[tantek]](https://indieweb.org/User:Tantek.com) - like since forever
+* 21:31 [[GWG]](https://indieweb.org/User:David.shanske.com) - That's the way I am using and consuming it
+* 21:31 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - whoa swentel indieweb.org/Micropub-extensions#Location_checkin_information
+* 21:31 [[tantek]](https://indieweb.org/User:Tantek.com) - folks here have been trying to get rel=feed off the ground again but TBH I'm unsure about it's feasibility
+* 21:31 [[GWG]](https://indieweb.org/User:David.shanske.com) - What is feed discovery?
+* 21:31 [[Loqi]](https://indieweb.org/Loqi) - feed discovery is a way to, given someone's home page, discover their feed or feeds that they publish indieweb.org/feed_discovery
+* 21:31 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - that's like an embedded h-card in a geo URL?
+* 21:31 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - URI
+* 21:31 [[swentel]](https://indieweb.org/User:Realize.be) - aaronpk, yeah, works great .. (at least for me)
+* 21:32 [[GWG]](https://indieweb.org/User:David.shanske.com) - aaronpk, yes it is
+* 21:32 [[tantek]](https://indieweb.org/User:Tantek.com) - aaronpk you had it right 🙂
+* 21:32 [[swentel]](https://indieweb.org/User:Realize.be) - I can post checkins and geocaches now from indigenous, with pictures, all in one go :)
+* 21:32 [[swentel]](https://indieweb.org/User:Realize.be) - it's GREAT ;)
+* 21:32 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - [tantek]: re: geo URI? I thought URLs had to be resolvable
+* 21:32 [[tantek]](https://indieweb.org/User:Tantek.com) - swentel++ wow
+* 21:32 [[Loqi]](https://indieweb.org/Loqi) - swentel has 27 karma in this channel over the last year (48 in all channels)
+
+## #indieweb-dev on IIW 2018-08-19
+
+[![](https://imgur.com/MvrlESD.png)](https://freenode.logbot.info/indieweb-dev/20180819)
+
+[#indieweb-dev on IIW 2018-08-19-chat log](https://freenode.logbot.info/indieweb-dev/20180819)
+* 17:08 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - No, IIW
+* 17:09 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - but all the OAuth IETF people will be there
+* 17:09 [[tantek]](https://indieweb.org/User:Tantek.com) - IETF people take IETF i-d more seriously than rando domain with proposals
+* 17:09 [[kevinmarks]](http://www.kevinmarks.com/) - IIW is a good place to socialize specs certainly
+* 17:09 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - I wonder how much of this I can write in the next 2 hours
+* 17:09 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - need a name tho
+* 17:10 [[kevinmarks]](http://www.kevinmarks.com/) - OpenAppID
+* 17:10 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - Oh no
+* 17:11 [[kevinmarks]](http://www.kevinmarks.com/) - I was being facetious
+* 17:11 [[tantek]](https://indieweb.org/User:Tantek.com) - [kevinmarks]: based on what evidence of successful specs to come out of IIW socialization?
+* 17:11 [[tantek]](https://indieweb.org/User:Tantek.com) - kevinmarks++
+* 17:11 [[Loqi]](https://indieweb.org/Loqi) - kevinmarks has 7 karma in this channel over the last year (30 in all channels)
+* 17:11 [[tantek]](https://indieweb.org/User:Tantek.com) - OpenAppID++
+* 17:11 [[Loqi]](https://indieweb.org/Loqi) - OpenAppID has 1 karma over the last year
+* 17:11 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - OAuth came out of IIW
+* 17:11 [[kevinmarks]](http://www.kevinmarks.com/) - OAuth 1.0 had a lot of groundwork done at IIW
+* 17:11 [[kevinmarks]](http://www.kevinmarks.com/) - yes
+* 17:12 [[tantek]](https://indieweb.org/User:Tantek.com) - no that's a myth. OAuth came out of a mailing list started by Blaine at Twitter
+* 17:12 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - A lot of it was done at IIW regardless of where it started exactly
+* 17:12 [[tantek]](https://indieweb.org/User:Tantek.com) - the actual work was done by a small set of folks on a limited-write, public-readable mailing list
+* 17:12 [[kevinmarks]](http://www.kevinmarks.com/) - yes, but getting the yahoo and Google people in the room with him at IIW really helped
+* 17:12 [[tantek]](https://indieweb.org/User:Tantek.com) - it was an interesting model of standards development by email
+* 17:13 [[tantek]](https://indieweb.org/User:Tantek.com) - OAuth did not "come out of" IIW
+* 17:13 [[tantek]](https://indieweb.org/User:Tantek.com) - that's the myth
+* 17:13 [[kevinmarks]](http://www.kevinmarks.com/) - that helped get the mutual trust necessary to contribute to the mailing list
+* 17:13 [[tantek]](https://indieweb.org/User:Tantek.com) - it came out of a limited-write, publicly readable mailing list started by Blaine
+* 17:13 [[kevinmarks]](http://www.kevinmarks.com/) - I didn't say that, I said "a good place to socialize specs"
+* 17:13 [[tantek]](https://indieweb.org/User:Tantek.com) - aaronpk said that
+* 17:14 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - What I meant was OAuth would not have succeeded if it had not been discussed at IIW
+* 17:14 [[kevinmarks]](http://www.kevinmarks.com/) - I dragged several google auth people across the street to IIW, then they joined the mailing list
+* 17:15 [[kevinmarks]](http://www.kevinmarks.com/) - the real bonding experience was them hotpatching the spec and mitigating the replay attack at that foo camp
+* 17:16 [[tantek]](https://indieweb.org/User:Tantek.com) - yes the Open Web Foo hotpatching of OAuth 1 to fix the security problems was key
+* 17:16 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - I need a name that gets across that client registration is replaced by DNS
+* 17:16 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - I would use “implicit client registration” if “implicit” didn’t already have existing meaning in OAuth
+* 17:17 [[tantek]](https://indieweb.org/User:Tantek.com) - "URL client registration" ?
+* 17:17 [[kevinmarks]](http://www.kevinmarks.com/) - Zero Registration per ZeroConf
+* 17:18 [[tantek]](https://indieweb.org/User:Tantek.com) - or NoReg per NoSQL
+* 17:19 [[tantek]](https://indieweb.org/User:Tantek.com) - shortened to "NR"
+* 17:19 [[tantek]](https://indieweb.org/User:Tantek.com) - how do you handle client registration? we use NR for that
+* 17:19 [[tantek]](https://indieweb.org/User:Tantek.com) - "ZR" works just as well
+* 17:19 **sknebel** - client lookup?
+* 17:21 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - PKCE is a great name because it’s easily googleable and also pronounceable (pixie)
+* 17:23 [[tantek]](https://indieweb.org/User:Tantek.com) - aaronpk: Zero Registration shortened to: ZoRg
+* 17:23 [[tantek]](https://indieweb.org/User:Tantek.com) - all the Fifth Element fans will love it
+* 17:23 [[aaronpk]](https://indieweb.org/User:Aaronparecki.com) - zorg omg
+* 17:24 [[tantek]](https://indieweb.org/User:Tantek.com) - YES

_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

@@ -0,0 +1,46 @@
+---
+date: 2020-11-10
+title: Veres One
+description: "The Veres One Blockchain is a fit-for-purpose blockchain optimized for identity on the Web."
+excerpt: "Our vision is to enable all people and organizations in the world to create and own their online identifiers, control their identity data and with whom they share that data."
+header: 
+  image: /images/veres-one-header.webp
+  teaser: /images/veres_one-teaser.webp
+layout: single
+permalink: /blockchain/veres-one/
+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/)**
+
+
+* [Veres One - Summary](https://veres.one/summary/)
+  > The Veres One Project envisions a world where people and organizations control their identifiers and their identity data. The Veres One Blockchain is a fit-for-purpose blockchain optimized for identity on the Web. The network ecosystem is designed to be self-sufficient through the use of an innovative operational and funding model. The operational model ensures openness, prevents attacks against the network, and financially rewards individuals and organizations that choose to run software to ensure the security of the network. Human dignity demands that every individual be able to participate equally in our increasingly digital society. That means everyone deserves the ability create and administer unique, globally resolvable identifiers. For that reason, the network is global and open to the public; anyone may participate.
+
+> The Veres One Community Group, housed at the W3C, directs the development and management of the Veres One Network.
+> 
+> Community Group decisions are made by consensus and sent to the Board of Governors for review and voting. The Board of Governors vote to accept or reject Community Group decisions based on their compliance with the Veres One Mission. Meetings are open to the public and minutes are made available in a public github repository. - [About](https://veres.one/about/)
+
+* [Veres One Community Group](https://www.w3.org/community/veres-one/)
+  > The mission of the Veres One Project is to facilitate the creation of open standards, software, and provide the governance to enable anyone in the world to create and manage their own decentralized identifiers.
+
+* [Nodes](https://veres.one/)
+  > A Node on the Veres One Network contains a record of every event that has has made its way into the Veres One Blockchain over time. It is connected to many of the other Nodes in the Network and can "gossip" events to other Nodes in the Network. When a Node receives an event, if the Node is an Elector, it may suggest that an event is included in the blockchain. If 2/3rds of the Network sees the event, and it is valid, then the event will be included in the blockchain.
+
+* [Creating a DID on Veres One](https://veres.one/download/)
+  > Requirements: Node v8.6+\
+  > Install did-client\
+  > Install the Decentralized Identifier client:\
+  > `mkdir did-client`\
+  > `cd did-client`\
+  > `npm install did-client`\
+  > Generate a Decentralized Identifier:
+  > `./node_modules/did-client/did generate --register`\
+  > Information related to your Decentralized Identifier will be stored in the following directory:\
+  > `ls $HOME/.testdid/`
+
+

_drafts/2020-11-11-tykn.md

@@ -0,0 +1,22 @@
+---
+date: 2020-11-11
+name: Tykn
+title: Tykn Tech
+description: We envision a world where identities are portable, private and secure, so that no one has to lose access to their identity ever again. Creating a future of opportunity.
+excerpt: >
+    Why is SSI better?
+
+    - A secure and digital peer-to-peer channel is established between ID Issuer, ID Owner and ID Verifier. When credentials are exchanged not even the Self-Sovereign Identity system provider knows what is being exchanged. Credential issuing becomes simpler and faster.
+    - SSI Credentials are tamper-proof through the use of cryptography.
+    - They are private and under your control. SSI uses Selective Identity disclosure technology.
+layout: companies
+permalink: companies/tykn-tech/
+canonical_url: 'https://decentralized-id.com/companies/tykn-tech/'
+categories: ["Companies"]
+tags: ["Sovrin Foundation","Trust over IP","DIACC","Founding Sovrin Steward","Indy","Trust Framework"]
+header:
+  image: /images/tykn_header.webp
+  teaser: /images/tykn_teaser.webp
+last_modified_at: 2023-02-20
+toc: true
+---

_drafts/2020-11-17-dragonchain.md

@@ -0,0 +1,108 @@
+---
+date: 2020-11-17
+title: Dragonchain & Factor
+description: "Blockchain technology for decentralized identity management - Guest Post"
+excerpt: >
+    On Factor/MyFii DID, the identity factors are decentralized to the individual owners. Individual users hold their own identity information in granular form as “factors”. Factors can be any data attributed to an individual and can be based on verifications by one or more external 3rd parties, or they can be self-declared/self-certified. These factors can then be provided to other parties needing identity verification. These factors can also be held within smart contracts with controlled and metered access.
+layout: single
+permalink: blockchain/dragonchain-factor/
+canonical_url: 'https://decentralized-id.com/blockchain/dragonchain-factor/'
+tags: ["Dragonchain","Blockchain"]
+header:
+  image: /images/dragonchain-factor-header.webp
+  teaser: /images/dragon-teaser.webp
+  og_image: /images/dragon_factor_og.webp
+last_modified_at: 2020-11-17
+toc: true
+authors:
+  - "<a href='https://twitter.com/hodldrgn'>Holly Jolly Jeffrey</a>"
+  - "<a href='https://www.linkedin.com/in/j0j0r0/'>Joe Roets</a>"
+---
+
+Guest post by [Holly Jolly Jeffrey](https://twitter.com/hodldrgn) ([Linkedin](https://www.linkedin.com/in/jeffrey-neijenhuis/)) and Dragonchain Founder\CEO [Joe Roets](https://www.linkedin.com/in/j0j0r0/).
+{: .notice--info}
+
+## Technology Overview 
+
+As enterprises continuously digitize their businesses, there is an increasing need for security and trust built around digital identities. Current identification systems are siloed and enterprises are having major challenges to manage Personal Identifiable Information (PII) in an increasingly regulated environment (eg. GDPR). On top of that, privacy and control of their data is becoming a greater concern for users as well. Factor is using blockchain technology that allows users to authenticate to a website or other service with a secure cryptographic signing mechanism. No username or password will be necessary or required for the sign in process. 
+
+Dragonchain itself provides for “protection of business data” which can also be used to protect PII/privacy data for users. We do this by stripping the business payload of every transaction before the business’ block goes to the network for verification. In Dragon Net (see Dragonchain architecture), the  proof is decentralized, not the data. This means that all transaction data may be proven in the future to explicit parties without unnecessary exposure.
+
+### Structural approach to privacy and data protection
+
+This separation is a structural approach to the privacy and data protection issue which does not rely on guesses of safety against unknown attack vectors in cryptographic functions. This model allows the business to use best practices devops and existing staff to protect their data.
+
+On Dragonchain, the proof is decentralized, not the data. All transactions are verified in blocks from 5 different contexts in Context Based Verification on Dragon Net. This allows the business to decentralize or share the data as necessary for their particular business model, yet have a proofing system scaled for Enterprise.
+
+On Factor/MyFii DID, the identity factors are decentralized to the individual owners. Individual users hold their own identity information in granular form as “factors”. Factors can be any data attributed to an individual and can be based on verifications by one or more external 3rd parties, or they can be self-declared/self-certified. These factors can then be provided to other parties needing identity verification. These factors can also be held within smart contracts with controlled and metered access.
+
+{% include video id="_6Mzv1CPMXQ" provider="youtube" %}
+
+### Compatibility with W3C standards?
+
+Factor was developed prior to W3C standardization, but we expect to provide mappings and support for W3C standards via our MyFii integration. Dragonchain and Factor are designed to be interoperable with traditional and blockchain systems. Dragonchain holds multiple interoperability and scalability patents that are employed in the Factor/DID system. The systems are literally interoperable with any other system via standard RESTful service API integration.
+
+![Factor decentralized identity logo]({{ site.baseurl }}/images/factor-dragonchain.webp "Factor decentralized identity")
+
+### Features & Specifications 
+
+Factor is a blockchain based identity and access solution that allows users to take control of their identity and eliminates the risk for enterprises to store PII (e.g. risk of data breaches, and GDPR compliance). Delivered as a service, built on top of the Dragonchain platform, Factor Identity authenticates users to applications using public key encryption. Third party Factor Identity Providers confirm claims or factors about a user without sharing the actual data, it de-risks the storage of PIIs associated with users and data breaches. 
+
+This identity solution does not store personal identifiable information, instead, the hashes of the actions are recorded into our decentralized system. This makes it virtually impossible to hack all of the business data because it’s not stored in one location. It also provides better access control and management to the data. Individuals or companies can control who has the ability to view and edit data, reducing unauthorized access. 
+
+Factor provides a better solution than what federated identity provides: businesses can manage and update a person’s consumable identity components or factors into one place. The verification process of Factor relies on third party Factor Identity Providers who are able to verify sensitive data for businesses. Factor has logic built into its system that can update their data once a Factor Identity Provider verifies the data. This can create ease and reduce costs for businesses and end users, for example in handling KYC between multiple banks for the same customer. 
+
+### Protection against quantum attacks?
+
+When it comes to legitimate concerns in regards to future quantum attacks, “The answer is in the architecture of the software itself. Considerations of possible Quantum compute attack are very focused on the cryptographic side of the equation. Yet, if you segregate the actual data from exposure on a public chain, the data will be structurally secure. I would never, ever, put sensitive information like customer’s personal information or military and Space Force information anywhere near an actual public blockchain, encrypted or not, as this data will be subject to all manner of attacks. The data should be segmented and separated away from exposure on a public blockchain. The proof could be affected by quantum, but if any of the many other quantum-resistant algorithms work, you can also apply those at any level.
+
+It’s like some of the things that happened during the Cold War. Both sides would attack each other's data or systems and the other side would not know for years that this had happened. When it comes to blockchain based proof, just knowing that something was stolen or tampered with would be remarkably valuable. At the very least you would be able to measure the level of security. As an example, would my enemy spend three billion dollars to attack this particular part that I'm about to 3D print on a ship?
+
+You can also look back and see direct evidence for simultaneous forks on Bitcoin, Ethereum, Ethereum Classic, (and every other Interchain) overlapping the block time for the transaction in question'', - Joe Roets, Dragonchain Founder & Architect explains.
+
+## Factor benefits:
+
+* Determine where data will be stored, including the geographic region, and allow for tighter control over jurisdictions where nodes are operated. 
+* Keep data private and ensure it never leaves the private blockchain unless explicitly granted, or by including references to the underlying data (stored elsewhere) in the form of a hash value in the payload. 
+* Comply with requests to be forgotten. This is accomplished by removing the underlying data (“off-chain”) reference via a hash value. 
+* Filter access control to applications, providing selective exposure of specific factors. 
+* Eliminate liabilities, such as the retention of PII or other sensitive data. 
+
+### With Factor an individual user can:
+
+* Prove you are over 21 without exposing your full Drivers License or Passport.
+* Prove you reside in a particular region without exposing your address.
+* Prove you have a valid email, without exposing the address.
+* Replace identifiers such as a phone number or email address which were never designed to be safely used for logins
+
+## Case Studies
+
+### Case Study 1 - SafePass and Covid-19
+
+In the first quarter of 2020, Dragonchain was able to partner with Medek Health Systems. The city of Apopka was looking for an application to help enable employees get back to work, as safely as possible. Medek Health Systems leveraged Dragonchain to ensure privacy and personal medical data of individuals is respected.
+
+In the application, a medical assessment provides directions on next steps to take. Should an individual go into quarantine? Or perhaps consider getting tested or seeking medical help for having Covid-19 symptoms? After completing a questionnaire, a medical risk score is assigned to a user. Users of the application are even able to use telemedicine for Covid-19, and have access to medical professionals directly through the app. 
+
+Every step along the way is recorded and validated on Dragonchain’s hybrid blockchain protocol. A combination of ledgering and smart contracts is used to trace the workflow, and provide proof of the pre-described workflow. The system takes into consideration new methods and tests to become available over time, making it a flexible solution. Individuals are able to proof their employee or other authority that the prescribed process has been followed. Within a matter of weeks the application was launched in the Google Play Store and the Apple App store. Medek Health Systems continues to integrate more blockchain based solutions into the application, including our decentralized identity solution Factor.
+
+* [Learn more about SafePass](https://www.bizjournals.com/orlando/news/2020/05/15/heres-how-this-app-lets-customers-know.html)
+
+### Case Study 2 - Decentralized Identity in Social Media
+
+[Den](https://den.social) (social media platform) will integrate with Factor, Dragonchain’s privacy focused decentralized identity technology. Doing this allows for the verification of the identity of Denizens with controlled exposure to Den and the world. The identity system will provide protection against impersonation with cryptographically signed messages and actions. 
+
+Lairs will be able to limit use based upon identity Factors, and will allow a community to decide whether their Lair will be made up of users that are identified, anonymous, or a mix of both. This also allows the creation of a model for an anonymous account economy.
+
+* [Read the Den whitepaper](https://drive.google.com/file/d/1LRe0Cv7bBaSeuDO7knxDst4IQVeTfjJu/view)
+
+## Resources
+
+* [Learn more about Factor](https://dragonchain.com/business/factor/) 
+* [Self Sovereign Identity and Decentralized Identity](https://dragonchain.com/blog/decentralized-identity-self-sovereign-identity-explained)
+* [Quick Take on Decentralized Identity](https://dragonchain.com/blog/quick-take-decentralized-identity)
+* [Dragonchain Spins-off Decentralized Identity Solutions and Services](https://dragonchain.com/blog/factor-spin-off-myfii)
+* [Interchain™ Between Blockchains and Traditional Systems](https://dragonchain.com/blog/interchain)
+* [Remain Sovereign with Blockchain Interoperability](https://dragonchain.com/blog/blockchain-interoperability)
+* [Quantum computing and data protection with blockchain.](https://dragonchain.com/blog/quantum-computing-data-protection-blockchain)
+* [Dragonchain architecture and whitepaper](https://dragonchain.com/Dragonchain-Architecture.pdf)
+

_drafts/2020-11-20-eSSIF.md

@@ -0,0 +1,15 @@
+---
+date: 2020-11-20
+title: ESSIF - European Self Sovereign Identity Framework
+layout: single
+permalink: 
+tags: ["Europe","ESSIFlab","TNO","eIDAS","Accenture","APG","Brightlands","De Volksbank","Rabobank","EBSI"]
+header:
+  image: /images/eSSIF.webp
+  caption: "[image source](https://ssimeetup.org/understanding-european-self-sovereign-identity-framework-essif-daniel-du-seuil-carlos-pastor-webinar-32/)"
+  teaser: /images/european-commission.webp
+last_modified_at: 2020-11-20
+toc: false
+published: false
+---
+

_drafts/2020-11-28-enterprise-ethereum-alliance.md

@@ -0,0 +1,34 @@
+---
+date: 2020-11-30
+title: Enterprise Ethereum Alliance
+description: The EEA is a member-led industry organization whose objective is to drive the use of Ethereum blockchain technology as an open-standard to empower ALL enterprises. 
+excerpt: > 
+    The EEA enables organizations to adopt and use Ethereum technology in their daily business operations. We empower the Ethereum ecosystem to develop new business opportunities, drive industry adoption, and learn and collaborate with one another.
+categories: ["Organizations","Blockchain Based"]
+tags: [Ethereum","Enterprise Ethereum Alliance","Blockchain for Social Impact Coalition","Blockchain Research Institute","SAE ITC", "DIF","Accenture","Consensys","Dragonchain","Ethereum Foundation","Enigma","Ernst & Young","Hyperledger Foundation","IntelJP MorganMicrosoftPerkins Cole]
+
+permalink: blockchain/ethereum/enterprise-alliance/
+canonical_url: https://decentralized-id.com/blockchain/ethereum/enterprise-alliance/
+last_modified_at: 2020-11-30
+header:
+  image: /images/
+  teaser: /images/
+published: false
+---
+
+**[Website](https://entethalliance.org/) • [GitHub](https://github.com/EntEthAlliance) • [Twitter](https://twitter.com/EntEthAlliance) • [Youtube](https://www.youtube.com/channel/UClC49LtcE4Wuo4POqa4J0bA) • [Blog](https://entethalliance.org/blog/)**
+
+* [EntEthVision](https://github.com/EntEthAlliance/EntEthVision)
+  > This Vision Paper describes technologies and standards that are relevant to members of Enterprise Ethereum Alliance. The Vision Paper evolves based on feedback and details highlighted by EEA members, such as short term and long term goals.
+
+* [Enterprise Ethereum Alliance Permissioned Blockchains Specification v3](https://entethalliance.github.io/client-spec/chainspec.html#dfn-identity-proof) EEA Editor's Draft 29 November 2020
+  > In enterprise settings, identifying organizational ownership of signing accounts is critical in many use cases. In the off-chain world, organizations, private businesses, governments and academic institutions all have defined identities. It is critical to have a robust binding between the organization's off-chain identity and their on-chain signing accounts.
+  > 
+  > One example of where this binding can be useful is permissioning. A permissioning contract can use this registry to assign roles to an organization then look up the organization that owns an account to make permissioning decisions.
+  > 
+  > The binding is established with identity proofs. An identity proof is a cryptographical data structure that can be independently verified, either on-chain in the smart contract, or off-chain by client applications, describing the relationship between defined entities such as an account, node, or another participating organization (by defining the root signing account as a member of a participating organization).
+  > 
+  > The registry does not act as the source of truth for network membership. The membership of the blockchain network is maintained by the permissioning contracts.
+
+## [Digital Identity Task Force](https://entethalliance.org/working-group-leadership/)
+* Rouven Heck (Chair) ConsenSys • rouven.heck@consensys.net

_drafts/2020-12-01-xri-technical-committee.md

@@ -0,0 +1,82 @@
+---
+date: 2020-12-01
+title: XRI Technical Committee
+description: Defining a syntax for abstract structured identifiers to share semantics across different URI schemes, domains, and applications (XRI); plus defining a simple XML format for uniform metadata discovery for all URIs (XRD)
+excerpt: > 
+    The purpose of this TC is to define a syntax for abstract structured identifiers -- identifiers that can be used within other URI schemes (such as http: and https: URIs) to share semantics across any number of domains and applications. The TC is also defining a simple XML descriptor format and HTTP(S) protocol for uniform resource metadata discovery.
+category: ["History"]
+tags: ["OASIS","XRI","XDI","Dataweb"]
+last_modified_at: 2020-12-01
+permalink: web-standards/oasis-open/xdi/xdi-tc/
+canonical_url: https://decentralized-id.com/web-standards/oasis-open/xdi/xdi-tc/
+toc: false
+header: 
+  image: /images/xri-tc-header.webp
+  teaser: /images/xri-tc-teaser.webp
+
+---
+
+**[OASIS Extensible Resource Identifier (XRI) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xri)**
+
+* [An Introduction to XRIs](https://docs.oasis-open.org/xri/xri/V2.0/xri-intro-V2.0.pdf)
+  > - XRIs provide a uniform syntax and resolution protocol for both persistent and reassignable abstract identifiers. 
+  > - XRIs provide a uniform syntax for delegating abstract identifiers between authorities at any level or context.
+  > - XRIs provide a uniform syntax (called “cross-references”) for sharing abstract identifiers across all contexts.
+  > - XRIs provide both a generic and a trusted protocol for resolving a single abstract identifier into any number of concrete identifiers.
+  > - XRIs provide a simple, standard means of discovering URIs that may be associated with a resource, including those needed for additional metadata discovery.
+  > - XRIs provide a standard means of protecting privacy by revealing the least possible information in an identifier and allowing an authority to control further access.
+  > - XRIs provide a standard means of extension without sacrificing interoperability.   
+* [XDI FAQ](https://www.oasis-open.org/committees/xdi/faq.php)
+  > **_What features do XRIs have that URIs don't?_**
+  > - **XRIs are "location-independent"** - the content of an XRI is decoupled from the network location of any data or services associated with the XRI. This means, among other things, that accessing a resource associated with an XRI isn't limited to a particular network location or protocol. (Most URI schemes in wide use today use identifiers that imply a close association to a network location or protocol.)
+  > - **XRIs can assert persistence of all or parts of an identifier**. XRIs allow two types of separators (persistent and reassignable) between segments of an XRI, so the XRI can suggest that certain parts of the identifier are intended to be long-lived "primary keys" (a concept borrowed from database technology) and others are subject to change. Most URI schemes, on the other hand, are all-or-nothing. With URNs, for example, the entire identifier is persistent. With HTTP URIs, the entire identifier is potentially transient. The XRI scheme allows both characteristics to be combined in one federated identifier.
+  > - **XRIs provide the ability to "contain" other URIs or XRIs in the form of cross-references**. Conceptually this is similar to using quote marks in English to talk about someone else's text. Cross references allow a well-defined URI or XRI to identify not only a concept or resource, but also to identify that concept or resource relative to another concept or resource. For example, a URI could identify a book, and an XRI could then identify a particular library's copies of the book by using that URI in a cross-reference appended to the library's XRI. So if " urn:isbn:0-131-10362-8" represents The C Programming Language by Kernighan and Ritchie, and "xri:@SeattlePublicLibrary" represents the Seattle Public Library, then "xri:@SeattlePublicLibrary/(urn:isbn:0-131-10362-8) " represents The C Programming Language in the context of the Seattle Public Library.
+  > - **XRIs also support self-references**, a special form of cross-reference that indicates that an XRI is not intended to be resolved on the network but is intended solely as a unique identifier. For example, "xri:(@SeattlePublicLibrary/(urn:isbn:0-131-10362-8))" is a self-reference because it is entirely enclosed by parentheses, and as such represents the identifier itself.
+  > - **XRIs allow unlimited delegation of namespaces**. While many URI schemes rely on DNS delegation, XRIs also have the ability to use abstract (non-DNS) names or identifiers that can contain a wider set of characters and strings. The XRI specification includes several global context symbols for this purpose (e.g., the "@" in "xri:@example/foo" represents a standard global namespace for organizations). In addition, a cross-reference can also serve as a namespace root, thus creating a private or community-based identifier space whose management is entirely community defined (for example, "xri:(http://www.example.com)/foo").
+  > - **XRIs are fully internationalized**. XRI syntax builds on the W3C IRI (Internationalized Resource Identifier) specifications that adapt URIs to the Unicode character set.
+* [Extensible Resource Identifier (XRI) Syntax V2.0](http://www.oasis-open.org/committees/download.php/5109/xri-syntax-resolution-1.0-cd.pdf) - Committee Specification, 14 November 2005 
+  > Extensible Resource Identifiers (XRIs) provide a standard means of abstractly identifying a resource independent of any particular concrete representation of that resource—or, in the case of a completely abstract resource, of any representation at all.
+  >
+  > As shown in Figure 1, XRIs build on the foundation established by URIs (Uniform Resource Identifiers) and IRIs (Internationalized Resource Identifiers) as defined by [URI] and [IRI], respectively.\
+  > ![](https://i.imgur.com/mq9znfO.png)\
+  > The IRI specification created a new identifier by extending the unreserved character set to include characters beyond those allowed in generic URIs. It also defined rules for transforming this identifier into a syntactically legal URI. Similarly, this specification creates a new identifier, an XRI, that extends the syntactic elements (but not the character set) allowed in IRIs. To accommodate applications that expect IRIs or URIs, this specification also defines rules for transforming an XRI reference into a valid IRI or URI reference. 
+* [Extensible Resource Identifier (XRI) Metadata V2.0](https://www.oasis-open.org/committees/download.php/11854/xri-metadata-V2.0-cd-01.pdf)
+  > [XRISyntax] establishes five global context symbol (GCS) characters that may be used to begin an XRI authority segment for the purpose of expressing the abstract global context of an identifier. One of these GCS characters, "$", is reserved for identifiers for which the authority is a standards specification.
+  > 
+  > A second key XRI feature, cross-references (see section 2.2.2 of [XRISyntax]), allows XRIs to be embedded within other XRIs in order to share identifiers across contexts. This syntactic feature allows XRIs in the $ namespace to be used as metadata to describe an XRI itself. For example, the following XRI includes a cross-reference with version metadata.
+  > ```
+  > xri://@example*resource*($v/3)
+  >                         \----/ cross-reference with XRI metadata
+  > ```
+  > The purpose of this specification is to define a set of XRIs in the $ namespace that function as identifier metadata—attributes that may be used describe an identifier itself, as opposed to attributes of the resource it identifies. This specification defines four such types of identifier metadata:
+  > - Language metadata that specifies the human language in which an identifier is intended to be interpreted.
+  > - Date/time metadata that specifies the point in time an identifier was established.
+  > - Version metadata that specifies the identifier’s position in a sequence of identifiers for the same logical resource.
+  > - Annotation metadata that allows XRI producers to add annotations to XRIs or XRI segments.
+  > The definition of each metadata type also specifies comparison rules, significance in resolution, and any other special processing rules specific to that type. 
+* [Extensible Resource Identifier (XRI) Resolution Version 2.0](https://docs.oasis-open.org/xri/xri-resolution/2.0/specs/cs01/xri-resolution-V2.0-cs-01.pdf)
+  > Extensible Resource Identifier (XRI) provides a uniform syntax for abstract structured identifiers as defined in [XRISyntax]. Because XRIs may be used across a wide variety of communities and applications (as Web addresses, database keys, filenames, object IDs, XML IDs, tags, etc.), no single resolution mechanism may prove appropriate for all XRIs. However, in the interest of promoting interoperability, this specification defines a simple generic resource description format called XRDS (Extensible Resource Descriptor Sequence), a standard protocol for requesting XRDS documents using HTTP(S) URIs, and standard protocol for resolving XRIs using XRDS documents and HTTP(S) URIs. Both generic and trusted versions of the XRI resolution protocol are defined (the latter using HTTPS [RFC2818] and/or signed SAML assertions [SAML]). In addition, an HTTP(S) proxy resolution service is specified both to provide network-based resolution services and for backwards compatibility with existing HTTP(S) infrastructure. 
+  > 
+  > | Resolution Component | DNS Architecture | XRI Architecture |
+  > | --- | --- | --- |
+  > | Identifier | domain name |  XRI (authority + path + query) | 
+  > | Resource record format | text (resource record) |  XML (XRDS document) |
+  > | Attribute identifier | string | anyURI |
+  > | Network endpoint identifier | IP address | URI | 
+  > | Synonyms | CNAME | LocalID, EquivID, CanonicalID, CanonicalEquivID | 
+  > | Primary resolution protocol | UDP | HTTP(S) | 
+  > | Trusted resolution options | DNSSEC | HTTPS and/or SAML | 
+  > | Resolution client | resolver | resolver | 
+  > | Resolution server | authoritative nameserver | authority server | 
+  > | Recursing resolution | recursing nameserver | recursing authority server or proxy resolver | 
+
+<div style="width:800px"> <strong style="display:block;margin:12px 0 4px"><a href="https://slideplayer.com/slide/4808597/" title="What do OpenID, Higgins, I-Names, and XDI Have in Common? An OASIS Webinar on XRI and XRDS May 6, 2008 Gabe Wachob, XRI TC Co-Chair Paul Trevithick, The." target="_blank">What do OpenID, Higgins, I-Names, and XDI Have in Common? An OASIS Webinar on XRI and XRDS May 6, 2008 Gabe Wachob, XRI TC Co-Chair Paul Trevithick, The.</a></strong><iframe src="https://player.slideplayer.com/15/4808597/" width="800" height="649" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC;border-width:1px 1px 0" allowfullscreen></iframe><div style="padding:5px 0 12px"></div></div>
+
+## i-names
+
+* [inames](https://web.archive.org/web/20150801134550/http://inames.net/)
+  > URLs are for connecting web pages. Now get the address for connecting people and businesses in rich, long-lasting digital relationships: i-names.
+* [http://dev.inames.net/wiki/Main_Page](https://web.archive.org/web/20111001110114/http://dev.inames.net/wiki/Main_Page)
+  > The goal of this wiki is to be a portal for everything XRI and i-names developers need to know to integrate i-names and XRI infrastructure into their identity-enabled sites, services, and applications. Please let us know via the About Us page if you don't find what you are looking for, or just add a request directly to the wiki.
+* [I Names](https://en.wikipedia.org/wiki/I-name)
+  > I-names are one form of an XRI — an OASIS open standard for digital identifiers designed for sharing resources and data across domains and applications.[1] I-names are human readable XRIs intended to be as easy as possible for people to remember and use. For example, a personal i-name could be =Mary or =Mary.Jones. An organizational i-name could be @Acme or @Acme.Corporation.

_drafts/2020-12-03-karyl-fowler-interview.md

@@ -0,0 +1,205 @@
+---
+title: Karyl Fowler, Transmute, and the DHS Silicon Valley Innovation Program 
+description: Inspired by a conversation with Karyl Fowler. History and background of Transmute and their work with DHS SVIP.
+excerpt: > 
+    For all the sexy tech stuff happening, it's the business challenges that are causing hesitation to adoption. This is one area where my team has an advantage, Orie and I have no overlapping skill sets, which has allowed us to divide & conquer the business and technology components, at the same time.
+tags: [TransmuteDHSTranscript]
+categories: ["Companies"]
+published: false
+---
+
+> For all the sexy tech stuff happening, it's the business challenges that are causing hesitation to adoption. This is one area where my team has an advantage, Orie and I have no overlapping skill sets, which has allowed us to divide & conquer the business and technology components, at the same time. - Karyl Fowler
+
+**A few months ago, I was contacted about an _upcoming company announcement_ from Transmute Industries.** 
+
+> Transmute has been gaining momentum following [their work with in US Department Homeland Security](https://www.dhs.gov/science-and-technology/news/2019/11/08/news-release-dhs-awards-198k-raw-material-import-tracking) (DHS) Science and Technology Directorate's Silicon Valley Innovation Program. 
+
+*The message also relayed* that if I was interested, I could speak with one of Transmute's founders (Karyl Fowler and Orie Steel).
+
+The announcement came on [OCTOBER 21, 2020](https://www.prweb.com/releases/transmute_closes_2m_seed_round_from_moonshots_capital_tmv_kerr_tech_investments/prweb17487962.htm), with the news of Transmute closing a 2 million dollar seed round from Moonshots Capital, TMV, and Kerr Tech Investments.
+
+> With a clear opportunity to grow rapidly in the enterprise market, Transmute plans to deploy the new capital to expand its Austin, Texas-based team to service increasing customer demand. The company secures critical supplier, product, and shipment data to give customers a competitive edge in an increasingly dynamic, global marketplace.
+
+These are clearly exciting times for Transmute and the industry as a whole.
+
+## Transmute's Story
+
+Soon after the announcement, we arranged a call, and I had an excellent interview with Karyl, which I intended to transcribe and share here.
+
+However, there were some technical difficulties and my recording didn't come out. This was extra incentive for me to learn more about Transmute, so I could attempt to reconstruct our discussion. Gratefully, Jess Melton was also on the call, and took excellent notes.
+
+Before I relate that discussion to the best of my ability, I'll share a bit of Transmute's story I've gathered along the way.
+
+### Education and Background
+
+Karyl earned a Masters of Science, Technology Commercialization, graduating from University of Texas at Austin, Red McCombs School of Business, in 2015. While completing that degree she also served as the Economic Development Coordinator for Greater Austin Chamber of Commerce.
+
+From 2015-17 Karyl worked for Novati as their Marketing Director, and managed medical electronics business development. There, she leveraged data-driven strategies to achieve sustainable development partnerships and expand Novati's life sciences portfolio to become a more integral component of their overall market strategy. 
+
+It was in that role when Karyl first became interested data privacy, discovering business models that were being created around DNA sequencing, and seeing how little agency an individual had over their own genetic data, once sequenced.
+
+### Early Hackathon Success
+
+Since her time in Business school, Karyl had been participating in hackathons with (Transmute co-founders) Orie Steele and Eric Olzewski. Incidentally, most hackathon participants don't arrive with a business-person. 
+
+This is where Karyl gave the team an edge, enabling them to show up with something just a little more polished than engineer-only teams. Hackathon winnings also helped her pay off a good portion of her business degree.
+
+They entered Austin's first blockchain hackathon in early 2016, held at the [Capital Factory](https://www.capitalfactory.com), where they built a user-centric and traceable identity management application for refugees who were pouring into Europe, at the time.
+
+> Understanding concerns about business models, built on your most intimate data, I wanted to see something where I had more control over who could access that, and I would actually own it. - [*Giant Robots #324*](https://www.giantrobots.fm/324)
+
+### Early Days of Transmute
+
+Over the following year, co-founders Karyl, Orie and Eric iterated off of that early success, consulting and building proofs of concept. It was during thie time that they realized that fully decentralized applications weren't adoptable by the enterprise without an interface to the centralized services these businesses are already hooked up to. The team had to step back and re-appraise their business strategy with a focus on their commitment to open-source and privacy for users. It was during this time Transmute transitioned from a service model to a product model. 
+
+At the start of 2017 they left their jobs, and founded Transmute. Based on consulting work and proofs-of-concept developed in that time, they arrived at a vision of creating a hybrid app platform that made it easy to deploy blockchain applications using both centralized and decentralized components.
+
+Throughout this period they also became deeply involved in the Ethereum community. In July 2018, Transmute published [a whitepaper](https://www.transmute.industries/whitepaper.pdf) describing their vision, a token model and distribution schedule. Since 2018, Karyl has also served as an advisor for Austin's South by Southwest (SXSW) - Blockchain & Crypto, Tech in Enterprise tracks.
+
+In the aftermath of the following token crash, it was vital to re-asses this vision, and determine the best path forward with the same data-driven acumen Karyl brought to earlier phases in the process. While they did find a viable (and compliant) token model, they didn't find any enterprise demand for the token driven dApp platform. 
+
+What they did find was [*an enormous demand for the resulting efficiency gains and untapped revenue potential of implementing a decentralized identity solution*](https://medium.com/transmute-techtalk/back-to-the-basics-9158f47f4eb6) that doesn't require an Ethereum token.
+
+It wasn't long after shifting focus from their token driven dApp platform, to the high-demand use-case applying their work in decentralized identity to cross-border supply-chain and compliance documents.
+
+## Our Discussion
+
+One thing we discussed, early in the conversation, is the dissonance between the more anarchistic views prevalent in the early years of blockchain to now working with DHS. Personally, I still feel a little bemused at the fact of how my values have come to align, in some significant way, with the values promoted in the [DHS SVIP]({{ site.baseurl }}/government/usa/dhs/).
+
+### Being blockchain agnostic
+
+After discussing Karyl's background and the story of Transmute, the subject came up about  Transmute being largely blockchain agonostic. I was curious to know exactly what that means. 
+
+Karyl shares that Transmute has always felt strongly about interoperability, and just like cloud technologies, this would not be a winner take all scenario. They took a lot of flack for that position in earlier days, and for a while were feeling *too blockchain for the enterprise* and *too enterprise for the blockchain*, but ultimately their thesis is playing out. 
+
+She also shared that they are building in a time where the "winners" are still shaking out, but are working with people in the enterprise space that are cornering themselves into a particular solution, that could easily become obsolete.
+
+To solve for this challenge Transmute uses a single smart-contract and then builds adapters depending upon the needs of where it's being applied. An important component of interoperability involves building on open standards. [Learn about Transmute's standards for interoperability here](https://github.com/transmute-industries/interoperability).
+
+### DHS Silicon Valley Innovation Program
+
+> There are very few use cases that come into play when it comes to the usage of blockchain. Primarily, when there are multiple independent parties in play and no one party wants to own either the infrastructure or the data - *Anil John, [Federal Blockchain News](https://www.federalblockchainnews.com/podcast/episode/7975a493/dhs-melissa-oh-and-anil-john-of-silicon-valley-innovation-program)*
+
+Anil John and Melissa Oh, of the SVIP, were recently interviewed on the Federal Blockchain News Podcast, which sheds light into exactly what values the program operates under.
+
+The DHS is focused on creating increased transparency in the cross-border supply-chain, which can lead to greater efficiencies in trade and unlock massive economic value. The DHS a was in the focus on open-source, open-standards, and interoperability.
+
+> There was a significant push by large platform players and others, to set up a platform model [...] sit in the middle and extract value from that platform. As government, we are rather familiar with being walked into a corner and told that there is only one product that you will buy because it will solve the problem. - *Anil John, [Federal Blockchain News](https://www.federalblockchainnews.com/podcast/episode/7975a493/dhs-melissa-oh-and-anil-john-of-silicon-valley-innovation-program)
+
+In order to stave-off such vendor\platform lock-in scenarios, the DHS S&T SVIP funds the development of international standards, and supports interoperability amongst the platforms and services implementing those standards. 
+
+> We believe there is a fundamental layer of security privacy and interoperability that should be common across all platforms. Then you build value-added services on top of it. - *Anil John, [Federal Blockchain News](https://www.federalblockchainnews.com/podcast/episode/7975a493/dhs-melissa-oh-and-anil-john-of-silicon-valley-innovation-program)
+
+### Multitracking and Diversity
+
+The DHS also uses a technique called multi-tracking, inspired by the Heath Brothers book, [Decisive](https://heathbrothers.com/books/decisive/), where funds multiple companies to solve the same problems, highlighting approaches stemming from the varied backgrounds of the teams working on them. 
+
+This philosophy goes hand in hand with their commitment to diversity. The DHS achieves diversity in founders, not through quotas, but by actively promoting its program in the communities that it wants represented, and insuring all are judged on the same level playing field. 
+
+Instead of the common case where outreach is focused on large mainstream tech conferences, SVIP promotes its program at conferences lead by women, catering to female founders and others that lead in black and brown communities, while seeking also a geographic diversity in the companies it works with.
+
+> At the end of the day our results is what speaks to that. We actually do have a very diverse portfolio of international companies east and west coast middle us as well female founders. - *Melissa Oh, Federal Blockchain News*
+
+### SVIP Phases
+
+Neither the companies or the DHS are stuck in this arrangement, either party can walk away at each stage of the process. The DHS is not contracting companies as service providers, but funding the development of promising technical solutions and moving them through project phases to the extent that companies are able to deliver on intended use-cases. 
+
+Each phase is designed to increase the chance of a successful product, and decrease the risks.
+
+* [Program Phases](https://www.dhs.gov/science-and-technology/svip#expandAll)
+  > * Phase 1	$50-$200K	3-6 months	Proof-of-Concept Demo
+  > * Phase 2	$50-$200K	3-6 months	Demo Pilot-ready Prototype
+  > * Phase 3	$50-$200K	3-6 months	Pilot-test Prototype in Operation
+  > * Phase 4	$50-$200K	3-6 months	Test in Various Operational Scenarios
+  > * Phase 5	As required - Additional Use Cases and Operational Scenarios as DHS Determines
+
+#### Phase 1 - Walk the Talk
+
+In Phase 1, each company demonstrates their capacity to deliver upon the DHS use-case, showing they can deliver a minimum viable product that shows solution to the problem articulated in the call. 
+
+As mentioned at the beginning of this article, transmute entered its [first phase in the SVIP, November 2019](https://www.dhs.gov/science-and-technology/news/2019/11/08/news-release-dhs-awards-198k-raw-material-import-tracking).
+
+> to secure individual agency identities and verifiable credentials to ensure that CBP has visibility into the provenance, traceability and regulatory compliance of raw material imports.
+
+In [May 2020](https://www.dhs.gov/science-and-technology/news/2020/10/08/feature-article-st-svip-leverages-blockchain-interoperability-support-dhs), the SVIP hosted an interoperability plug-fest, as part of a Phase 1 deliverable, to demonstrate the progress its participants made towards multi-platform interoperability. 
+
+Transmute successfully demonstrated those capabilities, securely sharing certificates and licenses related to commodities tracking, between their application, the U.S. Customs and Border Protection, along with fellow Phase 1 participants: Mavennet Systems, and Factom. 
+
+#### Phase II - Prepare for Production
+
+Phase II, involves building out the complete capability that DHS is looking for, so it is production ready, and can be adopted in the marketplace at the end of this phase. 
+
+If a company is not advanced to Phase II, this is usually a result of not completing the challenge in enough time, rather than lack of capacity.
+
+Transmute is currently participating in phase II, working to prevent counterfeit steel imports. This phase will last until the Spring of 2021, and will involve talking to steel importers to see how they can get involved, along with lots of interoperability work.
+
+#### Phase III - Trust but Verify
+
+In this phase a DHS Red Team examines the products from every angle, from penetration testing, security, and privacy assurances, to ensuring documentation is sufficient for independent deployment of the technology offered, and verifying that all the DHS use-cases and necessary features are implemented.
+
+Before the red-team goes in, the DHS Science and Technology Privacy Office helps to highlight what the DHS is looking for from privacy, data protection and retention perspectives. 
+
+This red-team evaluation is shared only with the company evaluated and the DHS itself, who helps the team figure out how to address any concerns highlighted, and afterwards the red-team examines the project again to ensure all issues were addressed.
+
+#### Phase IV
+
+Once a company makes it to this point, they've undergone a battery of tests, interoperability demos, battle testing and refinement in production, and can be informed of any additional factors that the DHS is thinking about provided as operational components for a Phase IV Operational Pilot.
+
+### Design Challenge
+
+Announced in September 2020, DHS recently held a [Digital Wallets Challenge Community Engagement](https://www.dhs.gov/science-and-technology/news/2020/09/08/news-release-st-new-prize-competition-user-interface-digital).
+
+> From an implementation perspective, it is important for those UIs to support best practices for ease of use and visual consistency, while supporting interoperability, security, and privacy. We think there are graphical designers that can help with designing UIs for digital wallets that are part of these systems, that could be used not just by DHS, but anyone in the community working on standards-based verifiable credentials.
+
+In November, the design challenge's [part 1 finalists were announced](https://www.dhs.gov/science-and-technology/news/2020/11/02/news-release-finalists-announced-digital-wallets-prize-challenge): 
+
+* Dignari, LLC - Alexandria, Virginia
+* Indicio, Inc. - Washington, DC
+* Trinsic, Inc. - Provo, Utah
+
+> At the event, finalists received feedback from the community to prepare for stage 2 of the challenge. Federal government experts and the World Wide Web Consortium (W3C), a standards group, provided insights and examples of how they are using and developing standards for digital wallets. 
+
+Part 2 of this challenge will involve finalists showing their work based on feedback gained during the first part of the challenge.
+
+### Tap the Market
+
+* [**324: Tap the Market (Karyl Fowler)**](https://www.giantrobots.fm/324)
+  > Karyl Fowler, CEO & Co-founder of Transmute, discusses utilizing block chain for decentralized identity-management, exploring finding the right customer profile fits, education around data-security, her time at Techstars, and the startup community in Austin.
+
+
+---
+
+
+## Karyll Fowler
+
+### Karyl's Education and Background
+
+While working in Economic Development for the Greater Austin Chamber of Commerce, Karyl earned a Masters of Science in Technology Commercialization from the University of Texas at Austin, Red McCombs School of Business. 
+
+Her work during this time focused mainly on recruiting tech and manufacturing companies to Austin, TX as well as supporting management of the city’s Foreign Trade Zone initiatives.
+
+Karyl then worked for a semiconductor company, Novati Technologies, whose core business was in the defense sector. There, she leveraged data-driven strategies to achieve sustainable development partnerships and expand Novati’s bioelectronics portfolio to become a more integral component of their overall market strategy.
+
+It was in that role when Karyl first became interested in data privacy, discovering business models that were being created around DNA sequencing, and seeing how little agency an individual had over their own genetic data. 
+
+This experience also gave her a front seat view of global supply chains - both the inherent complexity and even intentional opacity involved in moving highly regulated products across borders.
+
+### Early Hackathon Success
+
+Upon graduation, Karyl began participating in hackathons with her co-founder, Orie Steele. Incidentally, most hackathon participants don’t arrive with a business-person.
+
+This is where Karyl gave the team an edge, enabling them to show up with something just a little more polished than engineer-only teams.
+
+They entered Austin’s first blockchain hackathon in early 2016, held at the [Capital Factory](https://www.capitalfactory.com/), where they built a user-centric and traceable identity management application for refugees who were pouring into Europe at the time.
+
+> Understanding concerns about business models, built on your most intimate data, I wanted to see something where I had more control over who could access that, and I would actually own it. - Karyl Fowler, [Giant Robots #324](https://www.giantrobots.fm/324)
+
+### Being blockchain agnostic
+
+After discussing Karyl’s background and the story of Transmute, the subject came up about Transmute being largely blockchain agnostic. I was curious to know exactly what that means.
+
+Karyl shared that Transmute has always felt strongly about interoperability, and just like cloud technologies, this would not be a winner-take-all scenario. They took a lot of flack for that position in earlier days, and for a while were feeling “too blockchain for the enterprise and too enterprise for the blockchain,” but ultimately their thesis is playing out.
+
+She also shared that they are building in a time where the “winners” are still shaking out, and warned that some folks in the enterprise space are cornering themselves into a particular solution stack that could easily become obsolete.
+
+To solve for this challenge, Transmute uses a flexible, ledger-agnostic architecture with  adapters for a variety of ledger options depending upon the needs of where it’s being applied. An important component of [interoperability involves building on open standards](https://github.com/transmute-industries/interoperability).

_drafts/2020-12-10-xdi-technical-committee.md

@@ -0,0 +1,118 @@
+---
+date: 2020-12-01
+title: XDI Technical Committee
+description: XDI is a format and protocol for semantic data interchange -- a way different systems, applications, and databases can describe, map, exchange, link, synchronize, and protect data using a shared semantic graph model.
+excerpt: > 
+   The purpose of the OASIS XDI TC is to define a generalized, extensible, location-, application-, and transport-independent service for sharing, linking, and synchronizing data over the Internet and other data networks using XML documents and XRIs (Extensible Resource Identifiers), a URI-compatible abstract identifier scheme defined by the OASIS XRI Technical Committee. With XDI, data from any data source can be identified, described, linked, and synchronized into an active, machine-readable "dataweb" just as content from any content source can be identified and linked into the human-readable Web today.
+category: ["History"]
+tags: ["OASIS","XRI","XDI","RDF","Dataweb"]
+permalink: web-standards/oasis-open/xdi/xri-tc/
+canonical_url: https://decentralized-id.com/web-standards/oasis-open/xdi/xri-tc/
+last_modified_at: 2020-12-01
+header: 
+  image: /images/xdi-tc-header.webp
+  teaser: /images/xdi-teaser.webp
+toc: false
+---
+
+**[GitHub](https://github.com/OASIS-XDI-Technical-Committee/) • [OASIS XRI Data Interchange (XDI) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xdi)**
+
+> The Technical Committee was closed by OASIS TC Administration on 05 October 2020 and is no longer active. Archives of its work remain publicly accessible and are linked from this page. OASIS appreciates the efforts of all those who participated in this TC.
+
+* [OASIS Members Form XRI Data Interchange (XDI) Technical Committee](http://xml.coverpages.org/ni2004-01-21-b.html)
+> A particular purpose of XDI is to allow the controls needed to mediate access and usage of shared data to be expressed as XDI links. These data sharing controls can govern authority, authentication, authorization, access control, usage control, transmission, synchronization, and rights management. The integration of such controls into a common, generalized data-oriented service can provide a new platform for trusted data sharing networks and applications."
+* [OASIS TC Call For Participation: OASIS XDI TC](https://lists.oasis-open.org/archives/tc-announce/200401/msg00002.html) - Wed, *21 Jan 2004*
+> The purpose of the OASIS XDI TC is to define a generalized, extensible, location-, application-, and transport-independent service for sharing, linking, and synchronizing data over the Internet and other data networks using XML documents and XRIs (Extensible Resource Identifiers), a URI-compatible abstract identifier scheme defined by the OASIS XRI Technical Committee. With XDI, data from any data source can be identified, described, linked, and synchronized into an active, machine-readable "dataweb" just as content from any content source can be identified and linked into the human-readable Web today.
+* [OASIS XRI Data Interchange (XDI) TC - Charter](https://www.oasis-open.org/committees/xdi/charter.php)
+> As a data sharing service, XDI is intended to be very simple and generalized, so it can be bound to any transport protocol offering basic primitives like HTTP or SMTP. Similarly, the XDI graph model is intended to be very simple and generalized, so it can carry data directly (serialized in XML, JSON, or other formats) or reference it externally (much as XML or HTML documents can carry content directly or reference it externally). Such a "lingua franca" for data interchange can solve many problems related to mapping and sharing of data and metadata across domains, directories, schemas, ontologies, applications, and languages (both human and machine).
+>
+> Though the potential uses of XDI are very broad, the scope of the OASIS XDI TC work is limited to defining the specifications required for it to interoperate successfully. This includes:
+> 
+> - Defining the XDI graph model for describing and linking XRI-identified resources and data.
+> - Defining concrete serialization formats for this graph model.
+> - Defining rules for XRI addressing of XDI documents and the graphs they contain independent of serialization format.
+> - Defining an abstract XDI API consisting of logical operations on the XDI graph.
+> - Defining bindings of this abstract API to concrete transport protocols such as HTTP, SMTP, SIP, and XMPP, and to invocation protocols such as SOAP, REST, and RMI.
+> - Defining the semantics of XDI dictionaries — self-describing ontologies for use in XDI data sharing.
+> - Defining the semantics of XDI link contracts — XDI documents used to govern the terms of XDI data sharing relationships.
+> - Defining the semantics of other types of XDI graphs that fulfill general interoperability requirements of XDI infrastructure, e.g., context discovery, versioning, queries, etc.
+> - Maintaining additional versions of these specifications as they evolve over time.
+* [OASIS XRI Data Interchange (XDI) TC - FAQ](https://www.oasis-open.org/committees/xdi/faq.php)
+> 1. **_What is XDI?_**\
+> Specifically, XDI consists of three parts:
+> - The **XDI Meta-Schema-a** very simple XML schema that uses XRIs (Extensible Resource Identifiers) developed by the OASIS XRI TC to describe and link data that may be in many other native formats, including other XML schemas.
+> - **XDI Service**: a WSDL-defined protocol for exchanging data and metadata using XDI documents, together with bindings to different transport protocols (HTTP, SOAP, SMTP/MIME, etc.)
+> - The **XDI Service Dictionary**: a set of pre-defined XDI resources for describing other XDI resources and controlling XDI data interchange using XDI link contracts (see below).
+> 2. **_Is XDI a Web service?_**\
+> XDI over SOAP is a Web service. However XDI can also be bound to HTTP for use in "RESTful" architectures, as well as to other transport protocols like SMTP/MIME. So strictly speaking XDI is a generalized service based on XML document exchange that can be implemented as a Web service.
+> 3. **_What are the primary problems XDI is intended to solve?_**\
+> The general problem XDI is designed to address is interoperable, automated data interchange across distributed applications and trust domains. There are many specific examples of this problem:
+> - Exchange, linking, and lifetime synchronization of electronic business cards, public keys, and other common identity attributes across distributed directories (commonly known as dynamic address books).*
+> - Internet calendar sharing.*
+> - Trusted search (searches that need to cross multiple private websites).*
+> - Auto-configuration and intelligent data synchronization across multiple user devices (desktop, laptop, PDA, land phone, cell phone, etc.)
+> - Automated website registration, form-fill, and e-commerce transactions.
+        Cross-domain security and privacy management.
+> 4. **What is the Dataweb?**\
+> The inspiration for XDI was the application of the architectural principles of the Web and XML to the problem of distributed data sharing. The result is called the Dataweb, as summarized in the table below:
+> 
+> | Principle | World Wide Web | Dataweb |
+> |---|---|---|
+> | 100% addressable resources | URIs |  XRIs |
+> | Common representation and linking language | HTML | XDI Meta-Schema & XDI Service Dictionary | 
+> | Common interchange protocol | HTTP | XDI/HTTP, XDI/SOAP |
+> | Logical organization and navigation of resources | Website | Dataweb site |
+> 
+> In essence, the XDI meta-schema and protocol is to sharing and linking machine-readable data what HTML and HTTP are to sharing and linking human-readable content. In particular, Dataweb links are can define and control two-ways data sharing "pipes" between dataweb sites that can actively synchronize shared data when it changes, as illustrated below.
+> 5. **Why is existing URI syntax not sufficient for cross-domain data sharing?**
+> 
+> While URIs in general, and HTTP URIs (commonly called URLs) in particular, have been spectacularly successful for building the Web, they are missing several features that are vital for cross-domain data sharing:
+> 
+> - HTTP URIs do not provide absolute addressability of data instances down to any level of containment or nesting-they work only to the page or page fragment level. While XPath provides additional addressing features for XML documents, it operates only relative to XML document roots and is not integrated with HTTP URI syntax.
+> - HTTP URIs do not provide support for persistent addresses (the Dataweb equivalent of global foreign keys in databases). Other persistent URI schemes have been created, most notably the URN scheme, however they are not integrated with HTTP URI syntax and have not gained widespread adoption.
+> - HTTP URIs do not provide addressability of resources across contexts, i.e., the ability to share identifiers across multiple websites in order to identify the same logical resource in multiple domains or physical locations. This is extremely useful for cross-domain data sharing.
+* [The Dataweb: An Introduction to XDI](https://www.oasis-open.org/committees/download.php/6434/wd-xdi-intro-white-paper-2004-04-12.pdf) - A White Paper for the OASIS XDI Technical Committee v2, *April 12, 2004* 
+> XDI (XRI Data Interchange) is a new service for generalized distributed data sharing and mediation usingXRIs (Extensible Resource Identifiers), a URI-compatible abstract identifier scheme developed by the OASIS XRI Technical Committee. The goal of XDI is to enable data from any data source to be identified, exchanged, linked, and synchronized into a machine-readable dataweb using XML documents just as content from any content source can linked into the human-readable Web using HTML documents today. Because the controls needed to mediate access and usage of shared data can be built right into every XDI link, the emergence of a global Dataweb has the potential to do for trusted data interchange what the Web did for open content exchange.
+>
+> This white paper presents several examples of classic cross-domain data sharing problems, explains how the Dataweb model can provide a generalized solution, and describes the key objectives of the newlyformed OASIS XDI Technical Committee ([http://www.oasis-open.org/committees/xdi](http://www.oasis-open.org/committees/xdi)). 
+* [The Cover Pages topic on Data Sharing, Mediation, and Synchronization](http://xml.coverpages.org/dataSharing.html) Robin Cover's overview of the context in which XDI is being developed.
+> sample references are being collected for a broad range of topics relating to Web architecture, including notions of resource/object identity, resource identification schemes, persistence, namespaces, naming authorities, registration authorities, name resolution, network protocols, content negotiation, bindings, resource description, metadata, addressing and linking, automated data synchronization, access control, trust management, etc.
+
+## [OASIS XDI TC Technical Committee Wiki](https://wiki.oasis-open.org/xdi/)
+
+> - [The XDI Graph Model](https://wiki.oasis-open.org/xdi/XdiGraphModel) - contains links to introductory materials explaining XDI and the XDI graph model
+> - [XDI Design Goals](https://wiki.oasis-open.org/xdi/XdiDesignGoals) - The ten major design goals for the XDI graph model and semantic data interchange protocol
+> - [XDI ABNF](https://wiki.oasis-open.org/xdi/XdiAbnf) - formal ABNF rules defining the XDI graph model
+> - [XDI Serialization Formats](https://wiki.oasis-open.org/xdi/SerializationFormats) - the JSON serialization formats (and 2 text display formats) for XDI
+> - [XDI Messages](https://wiki.oasis-open.org/xdi/XdiMessagePatterns) - the basic patterns for XDI messaging
+> - [XDI Dictionaries](https://wiki.oasis-open.org/xdi/XdiDictionaryPatterns) - the basic patterns for XDI dictionary definitions
+> - [XDI Signatures](https://wiki.oasis-open.org/xdi/XdiSignature) - the pattern for digitally signing or encrypting an XDI graph, including an XDI message
+> - [XDI Link Contracts](https://wiki.oasis-open.org/xdi/LinkContractPattern) - how XDI does portable semantic authorization
+> - [XDI Policy Expression](https://wiki.oasis-open.org/xdi/XdiPolicyExpression) - how XDI does semantic policy expression
+> - [XDI Discovery](https://wiki.oasis-open.org/xdi/XdiDiscovery) - how XDI does P2P discovery of XDI endpoint URIs
+> - [Glossary](https://wiki.oasis-open.org/xdi/Glossary) - terminology used throughout the XDI 1.0 specifications
+> - [XDI Symbol Table](https://wiki.oasis-open.org/xdi/XdiSymbolTable) - summary of the symbols used in XDI syntax
+> - [XdiDollarDictionary](https://wiki.oasis-open.org/xdi/XdiDollarDictionary) - a list of all proposed entries for the XDI $ dictionary
+Informative Pages
+> - [Informative](https://wiki.oasis-open.org/xdi/CategoryInformative) (NOT part of XDI 1.0 specs)
+
+## [XDI 1.0 Specs List](https://wiki.oasis-open.org/xdi/XdiOneSpecs) - a list of the proposed XDI 1.0 specifications
+
+[**OASIS-XDI-Technical-Committee/xdi-spec-docbook/xdi**](https://github.com/OASIS-XDI-Technical-Committee/xdi-spec-docbook/tree/master/xdi)
+
+* [XDI Core V1.0](https://docs.oasis-open.org/xdi/xdi-core/v1.0/xdi-core-v1.0.html) Editors: Joseph Boyle; Markus Sabadello; Drummond Reed
+  > The foundational spec on which all other specs depend. It defines the ABNF for the normative graph model, serialization formats, and addressing syntax.
+* [XDI Messaging V1.0](https://raw.githubusercontent.com/OASIS-XDI-Technical-Committee/xdi-spec-docbook/master/xdi/xdi-messaging-1.0/xdi-messaging-1.0-wd05.xml) Editors: Joseph Boyle; Markus Sabadello; Drummond Reed
+* [XDI Bindings V1.0](https://raw.githubusercontent.com/OASIS-XDI-Technical-Committee/xdi-spec-docbook/master/xdi/xdi-bindings-1.0/xdi-bindings-1.0-wd05.xml) Editors: Markus Sabadello; Drummond Reed; Joseph Boyle;
+  > Defines the concrete binding of XDI messaging to specific transport protocols, beginning with the http/https protocol.
+* [XDI Link Contracts V1.0](https://raw.githubusercontent.com/OASIS-XDI-Technical-Committee/xdi-spec-docbook/master/xdi/xdi-link-contracts-1.0/xdi-link-contracts-1.0-wd03.xml) Editors: Dan Blum • Drummond Reed • Markus Sabadello 
+  > Defines the standard structure and vocabulary of XDI authorization statements, including XDI link contracts and policy expressions, so they are portable across all XDI endpoints.
+* [XDI Cryptography V1.0](https://github.com/OASIS-XDI-Technical-Committee/xdi-spec-docbook/blob/master/xdi/xdi-cryptography-1.0/xdi-cryptography-1.0-wd02.xml) Editors: Markus Sabadello
+  > Defines the semantics of using digital signatures and encryption with XDI graphs and XDI messages.
+* [XDI Discovery V1.0](https://github.com/OASIS-XDI-Technical-Committee/xdi-spec-docbook/blob/master/xdi/xdi-discovery-1.0/xdi-discovery-1.0-wd01.xml) Editors: Joseph Boyle • Les Chasen • Markus Sabadello • Drummond Reed
+  > Defines P2P discovery of XDI endpoint URI(s) given an XDI address (or a discoverable identifier that can be transformed into an XDI address).
+* [XDI Security Mechanisms V1.0](https://htmlpreview.github.io/?https://raw.githubusercontent.com/OASIS-XDI-Technical-Committee/xdi-spec-docbook/master/xdi/xdi-security-mechanisms-1.0/xdi-security-mechanisms-1.0-wd01.html) Editors: Joseph Boyle • Peter Davis • Dan Blum
+  > Describes the mechanisms for implementing security in XDI, including transport-level security, message-level security, encryption, token formats, etc.
+* [XDI Privacy Mechanisms V1.0](https://github.com/OASIS-XDI-Technical-Committee/xdi-spec-docbook/blob/master/xdi/xdi-privacy-mechanisms-1.0/xdi-privacy-mechanisms-1.0-wd01.xml) Editors: Dan Blum • Peter Davis • Drummond Reed
+  > This working draft describes an environment for writing and publishing an OASIS specification using DocBook XML. It is an internal OASIS support document and not the basis of an OASIS specification in and of itself.
+

_drafts/2020-12-30-ixo-foundation.md

@@ -0,0 +1,7 @@
+---
+published: false
+---
+ethereum ocean ipld
+
+http://www.truevaluemetrics.org/DBpdfs/BlockChain/The-IXO-Protocol-Draft-White-Paper-3.0-for-technical-review-12_8_2017.pdf
+

_drafts/2024-12-19-cosmos.md

@@ -0,0 +1,27 @@
+---
+date: 2020-11-19
+title: Cosmos Network - Internet of Blockchains
+description: Cosmos is a decentralized network of independent parallel blockchains, each powered by consensus algorithms like Tendermint consensus.
+excerpt: >
+  In other words, Cosmos is an ecosystem of that can scale and interoperate with each other. Before Cosmos, blockchains were siloed and unable to communicate with each other. They were hard to build and could only handle a small amount of per second. Cosmos solves these problems with a new technical vision. In order to understand this vision we need to go back to the fundamentals of blockchain technology.
+layout: single
+toc: false
+permalink: blockchain/cosmos/
+canonical_url: 'https://decentralized-id.com/blockchain/cosmos/'
+categories: ["Blockchain"]
+tags: ["Cosmos","oCap","Commercio"]
+last_modified_at: 2020-11-19
+header:
+  image: /images/
+  teaser: /images/
+published: false
+---
+
+
+
+## Building with Cosmos
+
+* [Commercio Network](https://commercio.network/) - Commercio.network is “The Documents Blockchain” that ALLOWS  companies to create identities, sign and exchange business documents among its participants.
+* [Ockam](https://www.ockam.io/) (built w Tendermint \ Cosmos compatible)
+* [NYM](https://nymtech.net/)
+  > Nym uses anonymous authentication credentials based on the [Coconut](https://arxiv.org/abs/1802.07344) signature scheme to enable privacy-enhanced data transfer and decentralized identity. Nym credentials can embed the data needed for a given service (including zero-knowledge proofs of private data), and these credentials are validated in a decentralized and public manner without linking a user to the service they want to access.

_drafts/People.md

@@ -0,0 +1,265 @@
+---
+title: People
+layout: single
+published: false
+---
+
+
+- [Mike Jones’ Blog](https://self-issued.info/)
+- [Nat Sakimura’s Blog](https://nat.sakimura.org/)
+- [John Bradley’s Blog](https://www.thread-safe.com/)
+
+* [IWD2021: Shining the spotlight on women in technology and digital identity](https://securekey.com/iwd2021-shining-the-spotlight-on-women-in-technology-and-digital-identity/)
+  > This International Women’s Day, we celebrate these role models and promote inclusivity to better recognize achievements in technology and digital identity from leading women. We are so lucky to have allies and strong relationships with various organizations led by strong female experts. It is a true honour to work alongside female leaders who heavily impact the industry with their thought leadership and innovative sights.
+* [Women in Identity](https://www.kuppingercole.com/blog//women-in-identity) Dr. Angelika Steinacker
+  > Silvia is a WID member since 2018 and started her career as an Identity engineer. Her topic will be the misbehavior of your digital twin and what you can do if your digital twin misbehaves.
+  > 
+  > Originating from a virtual model reflecting a physical object, the term “digital twin” also has its application in the cyber security industry. Social media giants and the advertisement industry have a huge interest in modeling your behavior, feelings, and thoughts to tailor advertising to you.
+* [Member interview with Jacoba Sieders](https://womeninidentity.org/2020/10/20/www-womeninidentity-org-interview-jacoba-sieders/) Women in Identity
+  > Jacoba Sieders is an independent, digital identity expert [and advisory board member of the EU ESSIF Lab]. She has held executive positions leading IAM and KYC functions for more than 20 years at major banks in the Netherlands and then in Luxembourg at the European Investment Bank. She also lived and worked in New Delhi, India for ING Group.
+
+
+* [Michael Becker Interviewed Kaliya re:SSI](https://identitypraxis.com/2020/11/16/an-interview-on-self-sovereign-identity-with-kaliya-young-the-identity-women/)  
+  > Kaliya’s purpose is to answer this profound question: “How do we own, control, manage, and represent ourselves in the digital world, independently of the BigTech companies (Facebook, Google, etc.)?”
+* [Tim Bouma is interviewed](https://medium.com/@trbouma/self-sovereign-identity-interview-with-tim-bouma-ca193f66f2bb) by SSI Ambassador - Adrian Doerk
+  > Every technology is a two-edged sword, gunpowder, guns, you know anything? There’s an upside and there’s the downside. I think that’s something that we have to be very cognizant of.
+* [The Domains of Identity and SSI with “Identity Woman”](https://www.ubisecure.com/podcast/domains-of-identity-ssi-identity-woman-kaliya-young/), Kaliya Young
+  > Kaliya and Oscar discuss the long-running Internet Identity Workshop (IIW) that she co-founded, the effects of moving to virtual identity conferences in 2020, insights from Kaliya’s books – ‘The Domains of Identity’, newly published in 2020, and ‘A Comprehensive Guide to Self Sovereign Identity’ – plus some great tips for all business leaders on how to view the role of identity in their organisation.
+* [Self-Sovereign Identity Authors Alex Preukschat & Shannon Appelcline](https://securetalkpodcast.com/podcast/self-sovereign-identity-alex-preukschat-shannon-appelcline/) Discussing
+  > Decentralized digital identity and verifiable credentials explain what Self-Sovereign Identity (SSI) is, why it’s important, and provide examples of practical applications for individuals and organizations.
+
+An academic nerdy podcast, out of [RMIT](https://www.rmit.edu.au/), Australia
+
+* [Episode 6: 'Digital Identity & Blockchain' with Kaliya Young, Prof. Jason Potts, & Prof. Ellie Rennie](https://open.spotify.com/episode/4kO6VVT9PmRPrie6e5plPj)
+
+
+![](https://i.imgur.com/jN2CaDz.png)
+
+
+
+Eventually there will be a section with individual pages for the various influential and\or prominent members of the DID\SSI community. But I wasn't sure where to start... 
+
+I decided to start by featuring Women in Identity first, and expand from there.
+
+* [**T**](https://womeninidentity.org/" />WomenInIdentity.org</a> [<a href="https://twitter.com/WomeninID)]
+
+* [stories.jolocom.com - 40 women in identity you should be following on Twitter](https://stories.jolocom.com/40-women-in-identity-you-should-be-following-on-twitter-e07b7e7c088b)
+
+## Kaliya Identity Woman
+
+[<img src="https://i.imgur.com/WB3wTWm.png"/>](https://twitter.com/IdentityWoman)
+
+
+* [identitywoman.net/about-kaliya/bio/](https://identitywoman.net/about-kaliya/bio/)
+> Kaliya Young (formerly Hamlin) is an expert in self-sovereign identity and identity on the blockchain. She is the co-author of a Comprehensive guide to Self-Sovereign Identity and is widely known as Identity Woman (its also the name of her blog and her twitter handle). She is committed her life to the development of an open standards based layer of the internet that empowers people.
+* [twitter.com/IdentityWoman](https://twitter.com/IdentityWoman)
+   * Co-Founder [Internet Identity Workshop](http://www.internetidentityworkshop.com/)(IIW)[[**T**](https://twitter.com/idworkshop)] to discuss "architectural and governance proposals for Internet-wide identity services and their underlying philosophies." -[Announcing IIW 2005](https://identitywoman.net/announcing-the-internet-identity-workshop-iiw2005/)
+* [identitywoman.net](https://identitywoman.net/) - Independent Advocate for the Rights and Dignity of our Digital Selves.
+  * [Exciting SSI announcement was not well received by some](https://identitywoman.net/exciting-ssi-announcement-was-not-well-received-by-some/)
+    > The Microsoft-Mastercard SSI alliance is great news, but some thought it was a bad thing.\
+  * [The Domains of Identity & Self-Sovereign Identity -- Presentation from Kaliya Young](https://youtu.be/U8bZ4GYFwKY)
+  [<img src="https://i.imgur.com/5v814Kl.png"/>](https://youtu.be/U8bZ4GYFwKY)
+    >The Future of Property Rights a program at New America just published a new report [The Nail Finds a Hammer: Self-Sovereign Identity, Design Principles and Property Rights in the Developing World.](https://www.newamerica.org/future-property-rights/reports/nail-finds-hammer/) I commented extensively on the paper before publication and they included the Domains of Identity within the report. It turns out that many of the Domains of Identity include registries. This whole perspective that registries as the root of many of our systems is very eye opening. Just like when one finds identity one sees it everywhere, it turns our registries are everywhere too.
+  * [ssiscoop.com - Your Guide to Self Sovereign Identity](https://ssiscoop.com/) 
+    >A comprehensive analysis of the technology, standards, projects, and companies that use blockchain for identity.
+
+## Kimberly Hamilton Duffey
+
+  * []()
+  * []()
+
+## Natalie Smolenski
+
+* [Natalie Smolenski - Author, Speaker](https://www.nataliesmolenski.com/)
+  > Natalie Smolenski is an anthropologist leading business development for blockchain technology firm Learning Machine. She writes and speaks about identity, tech, and government.
+
+* [Natalie Smolenski - University of Michigan - Academia.edu](http://umich.academia.edu/NatalieSmolenski)
+  > Natalie Smolenski, University of Michigan, Anthropology and History Department, Graduate Student. Studies Phenomenological Psychology, Self psychology, and Anthropology of Religion. Natalie Smolenski is a psychological anthropologist and historian
+
+
+## Ann Cavoukian, Ph.D.
+
+<a href="https://twitter.com/AnnCavoukian"><img src="https://i.imgur.com/r461NzU.png"/></a>
+* <a href="https://twitter.com/AnnCavoukian">twitter.com/AnnCavoukian</a>
+* [Global Privacy and Security By Design](https://gpsbydesign.org/)
+  > Myth: We need to give up our personal privacy for public safety.\
+  > Reality: We can have both. We don't need to choose.\
+  > SECURITY + PRIVACY = FREEDOM, INNOVATION AND PROSPERITY
+* <a href="https://www.linkedin.com/in/ann-cavoukian-ph-d-3a78809/">linkedin:</a>
+  >Distinguished Expert-in-Residence - Privacy by Design Centre of Excellence at Ryerson University
+  * [www.ipc.on.ca](https://www.ipc.on.ca/)
+    >The role of the Information and Privacy Commissioner is set out in three privacy and access laws: the Freedom of Information and Protection of Privacy Act (FIPPA), the Municipal Freedom of Information and Protection of Privacy Act (MFIPPA) and the Personal Health Information Protection Act (PHIPA). The IPC acts independently of government to uphold and promote open government and the protection of personal privacy.a
+  * <a href="https://www.itbusiness.ca/author/ann-cavoukian">itbusiness.ca/author/ann-cavoukian</a>
+    * [Operationalizing Privacy by Design -From Rhetoric to Reality](https://www.itbusiness.ca/blog/operationalizing-privacy-by-design-from-rhetoric-to-reality/20860)
+
+
+Notes:
+
+* Pamela Dingle (now head of ID standards at MSFT) 
+* Mary Ruddy
+* Elizabeth Reneirus
+* Kimberly Little (Sutherland)
+* Marta, formerly blockstream, now with Hyperledger 
+* Katryna Dow - Meeco 
+
+
+...
+
+## kim-cameron
+
+* [Kaliya-Identity Woman (@IdentityWoman)](https://twitter.com/identitywoman/status/1135367999903473664?s=12)
+  > Hanging with @kim_cameron in Toronto before @IdentityNorth
+![](https://pbs.twimg.com/media/D8GjKszX4AAg36e?format=jpg&name=small)
+
+* [Kim Cameron - Identity Laws](https://channel9.msdn.com/Blogs/scobleizer/Kim-Cameron-Identity-Laws) -  video
+  > Kim Cameron has caused quite a stir with his Identity Blog. He came out with a whitepaper called "the Laws of Identity" which has caused quite a bit of conversation.
+
+* [https://identityblog.com/](https://identityblog.com/)
+
+## doc-searls
+
+* [Doc Searls (@dsearls)](https://twitter.com/dsearls)
+  > Free-range journalist; wrote [The Intention Economy](https://www.amazon.com/Intention-Economy-When-Customers-Charge/dp/1422158527), co-wrote @Cluetrain; blogs at [doc.searls.com](http://doc.searls.com/), [doc.blog](http://doc.blog/); runs @VRM; fellow, @ucsbcits
+* [The Intention Economy: When Customers Take Charge](https://cyber.harvard.edu/events/2012/05/searls)
+  > Whether your interest is in preserving Internet freedom and opportunity, changing the economic power structure, new challenges for cyberlaw, or just turning the tables on privacy-violating business models and practices, there will be plenty to hear and discuss at Doc Searls' ...
+
+## mary-ruddy
+
+* [maryruddy (@maryruddy)](https://twitter.com/maryruddy/status/8000292905?s=20)
+  > Re @identiywoman to @davemcclure, I'm @maryruddy working on the adoption and implementation of open identity standards.
+
+* [Mary Ruddy - Gartner](https://www.gartner.com/analyst/44158/Mary-Ruddy)
+
+View Mary Ruddy's Gartner analyst profile. Gartner is the world's leading information technology research and advisory company.
+
+* [Mary Ruddy Archives - Identity Woman](https://identitywoman.net/tag/mary-ruddy/)
+
+## phil-windley
+
+* [Phil Windley's Technometria](http://windley.com/)
+Building the Internet of My Things
+
+* [The Live Web](http://web.archive.org/web/20130120050943/http:/theliveweb.org/) - web.archive.org
+  > Putting Cloud Computing to Work for People | A Book by Phillip J. Windley
+
+* [http://www.windley.com/tags/identity.shtml](http://www.windley.com/tags/identity.shtml)
+
+## kaliya-identitywoman-young
+
+* [TEDxConstitutionDrive 2012 - Kaliya Hamlin - "The Need for Limited Liability Personas"](https://www.youtube.com/watch?v=Lazg31TN8FE)
+  > Our 2012 theme was "Identity" This year we explored Identity in a way that went beyond the standard gender/race/age lines. We see Identity as the non-genetic...
+
+* [The Domains of Identity & Self-Sovereign Identity](https://www.youtube.com/watch?v=U8bZ4GYFwKY) - 2018
+Kaliya Young (“The Identity Woman”) explains 16 domains of identity --variously related to government, civil society, commerce, employment, and the data brok...
+
+![https://cdn.discordapp.com/attachments/619682299134345229/622965172843184128/unknown.png](https://cdn.discordapp.com/attachments/619682299134345229/622965172843184128/unknown.png)
+
+* [Tykn.tech (@Tykn_tech)](https://twitter.com/tykn_tech/status/1187387536185942016?s=12)
+  > "Right now the questions need to be about what do the customers who will be early adopters of this technology really need. How do we really make this stuff interoperable?" - @IdentityWoman 
+* [Interview with Kaliya Young (co-founder of the Internet Identity Workshop and author of the Domains of Identity)](https://tykn.tech/interview-with-kaliya-young/)
+
+## natalie-smolenski
+
+* [Natalie Smolenski - Author, Speaker](https://www.nataliesmolenski.com/)
+  > Natalie Smolenski is an anthropologist leading business development for blockchain technology firm Learning Machine. She writes and speaks about identity, tech, and government.
+
+* [Natalie Smolenski - University of Michigan - Academia.edu](http://umich.academia.edu/NatalieSmolenski)
+  > Natalie Smolenski, University of Michigan, Anthropology and History Department, Graduate Student. Studies Phenomenological Psychology, Self psychology, and Anthropology of Religion. Natalie Smolenski is a psychological anthropologist and historian
+
+* [Truth of Your Life - About](https://www.truthofyourlife.com/about.html)
+  > I am a counselor specializing in individual adult psychoanalysis. My practice is currently conducted only through online correspondence. In other words, my patients and I write to each other. This...
+
+* [Identity and Digital Self-Sovereignty](https://medium.com/learning-machine-blog/identity-and-digital-self-sovereignty-1f3faab7d9e3)
+
+A New Paradigm for Sovereignty on the High Seas
+
+
+## elizabeth-renieris
+
+* [https://hackylawyer.com/about](https://hackylawyer.com/about)
+  > Elizabeth M. Renieris (@hackylawyER) is the founder of the hackylawyER consultancy focused on law and policy engineering. She is also an incoming fellow at the Berkman Klein Center for Internet & Society at Harvard. An entrepreneurial attorney, policy advisor, and strategic consultant who is passionate about the impact of emerging technologies on privacy, identity, civil society, and collective consciousness, Elizabeth frequently advises on the same. Her core areas of expertise include cross-border data protection and privacy (CIPP/E, CIPP/US), digital and self-sovereign identity, blockchain and distributed ledger technologies, and artificial intelligence and machine learning systems.
+
+* [MIT Legal Forum Elizabeth Renieris Preview of Data Protection Session](https://www.youtube.com/watch?v=6UDZR_V6_vE)
+
+## marta-piekarska
+
+* [Meet Hyperledger’s New Director of Ecosystem Development – Hyp...](https://www.hyperledger.org/blog/2017/05/18/meet-hyperledgers-new-director-of-ecosystems)
+  > We’re thrilled to announce that we’ve recently hired Marta Piekarska as our Director of Ecosystems. Please join us in welcoming her to the team. Previously, Marta worked for Blockstream as...
+
+* [Blockchain Workshop Position Statement - Marta Piekarska](https://www.w3.org/2016/04/blockchain-workshop/interest/geater-piekarska.html)
+  > I am a Bachelor of Electrical and Computer Engineering from Warsaw University of Technology and a double Master from Computer Science and Informatics at Technical University of Berlin and Warsaw University of Technology. I did my thesis on Voice Encryption on Android Platform and GPU-aided Payload Delivery on Linux Kernel. Currently finishing my PhD thesis on User-Centric Privacy on Mobile Devices, while working for one of the hottest Silicon Valley startups, Blockstream as their Security Architect. Previously, I was the Lead Architect at Deutsche Telekom on the Future of Mobile Privacy, a collaboration with Mozilla and Deutsche Telekom improving Firefox OS.
+
+* [Marta Piekarska (@mpiekarska8)](https://twitter.com/mpiekarska8)
+Blockchain enthusiasts, Hyperledger evangelist, Security and Privacy gal.
+
+* [marta piekarska - YouTube](https://www.youtube.com/results?search_query=marta+piekarska)
+
+## manu-sporny
+
+
+* [https://www.sbir.gov/sbirsearch/detail/1241085](https://www.sbir.gov/sbirsearch/detail/1241085)
+
+* [http://manu.sporny.org/](http://manu.sporny.org/)
+
+* [https://digitalbazaar.com](https://digitalbazaar.com/)
+
+* [Manu Sporny (@manusporny)](https://twitter.com/manusporny)
+  > Founder/CEO Digital Bazaar; payments, identity & blockchain. Kickstarted Web Payments, Verifiable Credentials, Decentralized Identifiers, and JSON-LD at W3C.
+
+## katryna-dow
+
+* [Katryna Dow - About](https://katrynadow.me/about/)
+  > Katryna Dow is the CEO and founder of Meeco, the global tech company that launched a world leading data independence platform for people. Meeco guarantees individuals choice and data sovereignty ri…
+
+* [Katryna Dow  (@katrynadow)](https://twitter.com/katrynadow)
+  > Founder+CEO @meeco_me #APIofMe #Data #Privacy #SharedValue #Distributed #Blockchain #DigitalRights #Identity #SSID #HODL #Coffee What's next?
+
+* [http://www.linkedin.com/in/katrynadow](http://www.linkedin.com/in/katrynadow)
+
+
+## pamela-dingle
+
+* [Pamela Dingle (@pamelarosiedee)](https://twitter.com/pamelarosiedee)
+  > All your $5 wrenches are belong to me. Director of Identity Standards @ MSFT. Paranoid Optimist. (she/)Her opinions. See #ViewFromtheWindowSeat
+
+* [Eternally Optimistic](http://eternallyoptimistic.com/)
+Adventures of an Eternal Optimist
+
+* [Pamela Dingle - Identiverse 2019](https://identiverse.com/speaker/pamela-dingle/)
+
+* [Pamela Dingle](https://www.kuppingercole.com/speakers/587) - Kuppinger Cole
+  > Pamela Dingle has 15 years of experience in implementation and architecture of identity standards for web access management, provisioning, and federation. As Director of Identity Standards at Microsoft, Pamela leads a team of experts dedicated to collaboration within the indu...
+
+## Katryna Dow
+
+* [FinTech Insider on Tour @ Money20/20 Europe 2018: Katryna Dow, CEO Meeco](https://www.youtube.com/watch?v=q3yzXgesKJY)
+  > Sam sits down with Katryna Dow from Meeco to discuss data and taking control.
+
+* [Katryna Dow - FemTech Leaders](http://web.archive.org/web/20151122105350/http:/www.femtechleaders.com/oceania/katryna-dow-2/) - 2015
+
+The Voices & View from FemTech Leaders
+
+## Drummond Reed
+
+* [XRD Begins](http://www.equalsdrummond.name/?p=172) - Drummond Reed
+  > For most people, watching the evolution of technical specifications is like watching a glacier move. To those of us living the process, though, there can be a great deal of drama to it — in f…
+
+* [Drummond Reed (@drummondreed)](https://twitter.com/drummondreed)
+
+
+## Christopher Allen
+
+![](https://cdn.discordapp.com/attachments/620045023496503299/620045043255869451/unknown.png)
+
+* [The Four Kinds of Privacy](http://www.lifewithalacrity.com/2015/04/the-four-kinds-of-privacy.html) - April 20 2015
+
+* [The Path to Self Sovereign Identity](http://www.lifewithalacrity.com/2016/04/the-path-to-self-soverereign-identity.html)
+
+* [ChristopherA/info](https://christophera.info/)
+  > Simple Identity Website for Christopher Allen. 
+
+## Heather Dahl
+
+[Ep. 74 – Self Sovereign Identity – insights from Sovrin](https://www.insureblocks.com/ep-74-self-sovereign-identity-insights-from-sovrin/)
+
+[Heather Dahl](https://www.linkedin.com/in/heathercdahl/) is the CEO of Sovrin, one of the leading self-sovereign identity solutions. In this podcast we discuss how identity has evolved from the offline world, to the limitations of it being online in the internet and finally to the opportunities it brings in a blockchain world.

_drafts/twitter.md

@@ -0,0 +1,38 @@
+---
+layout: single
+title: Twitter Query - Decentralized ID
+description: "Curated feed from twitter hashtags #decentralizedid #iiw #selfsovereignid"
+excerpt: "Stay up to date on decentralizing digital identity topics on Twitter"
+permalink: /twitter/
+toc: false
+header:
+  image: /images/DecentralizeID_Twitter.webp
+  caption: "[@DecentralizeID](https://twitter.com/DecentralizeID)"
+published: false
+
+---
+
+{% for row in site.data.ssitw103120 %}
+  <h3><a href="https://twitter.com/{{ row.User }}">@{{ row.User }}</a> wrote at: <a href="{{ row.Link }}">{{ row.Time }}</a></h3>
+  <p><sup>Likes: <a href="{{ row.Link }}/likes">{{ row.Favorites }}</a> Following: <a href="https://twitter.com/{{ row.User }}/following/">{{ row.Following }}</a> Followed: <a href="https://twitter.com/{{ row.User }}/followers/">{{ row.Followers }}</a> {% if row.Retweets != "0" %}Retweets: <a href="{{ row.Link }}/retweets">{{ row.Retweets }}</a>{% endif %} {% if row.ReplyURL != "[]" and row.ReplyURL != blank %} - <a href="{{ row.ReplyURL }}">Reply to</a>{% endif %}</sup></p>
+  <blockquote>{{ row.Text }}</blockquote>
+  {% if row.Urls != "[]" %}
+    {% assign lnks = row.Urls | split: "," %}
+    {% assign urlt = row.UrlTitle | split: "," %}
+    {% assign urld = row.UrlDesc | split: "," %}
+    {% assign urli = row.UrlImg | split: "," %}
+    {% assign foo = 0 %}
+    {% for lnk in lnks %}{% assign ln = lnk | remove: "[" | remove: "]" | remove: "'" | remove: '"' %}{% assign urt = urlt[foo] | remove: "[" | remove: "]" | remove: "'" | remove: '"' | remove: 'None'  %}{% assign urd = urld[foo] | remove: "[" | remove: "]" | remove: "'" | remove: '"' | remove: 'None' %}{% assign uri = urli[foo] | remove: "[" | remove: "]" | remove: "'" | remove: '"' | remove: 'None' %}
+<a href="{{ ln }}">{% if urt != blank %}{{ urt }}{% else %}{{ ln }}{% endif %}</a>
+{% if urd != blank and urd != "Weve detected that JavaScript is disabled in your browser. Would you like to proceed to legacy Twitter?" %}<blockquote>{{ urd | remove: "[" | remove: "]" | remove: "'" | remove: '"' }}</blockquote>{% endif%} 
+{% if uri != blank %}<img src="{{ uri }}"/>{% endif%}{% assign foo = foo | plus: 1 %}
+    {% endfor %}
+  {% endif %}
+  {% assign htags = row.Hashtags | split: "', '" %}
+  {% for h in htags %}<a href="https://twitter.com/hashtag/{{ h | remove: "['" | remove: "']" }}">#{{ h | remove: "['" | remove: "']" }}</a> {% endfor %}
+  {% if row.ImageUrls != "[]" %}
+  {% assign imgs = row.ImageUrls | split: "', '" %}
+  {% for img in imgs %}<img src="{{ img | remove: "['" | remove: "']" }}">{% endfor %}
+  {% endif %}
+{% endfor %}
+

_includes/analytics-providers/custom.html

@@ -0,0 +1,6 @@
+<!-- start custom analytics snippet -->
+
+
+
+
+<!-- end custom analytics snippet -->

_includes/analytics-providers/google-gtag.html

@@ -0,0 +1,9 @@
+<!-- Global site tag (gtag.js) - Google Analytics -->
+<script async src="https://www.googletagmanager.com/gtag/js?id={{ site.analytics.google.tracking_id }}"></script>
+<script>
+  window.dataLayer = window.dataLayer || [];
+  function gtag(){dataLayer.push(arguments);}
+  gtag('js', new Date());
+
+  gtag('config', '{{ site.analytics.google.tracking_id }}', { 'anonymize_ip': {{ site.analytics.google.anonymize_ip | default: false }}});
+</script>

_includes/analytics-providers/google-universal.html

@@ -0,0 +1,7 @@
+<script>
+  window.ga=function(){ga.q.push(arguments)};ga.q=[];ga.l=+new Date;
+  ga('create','{{ site.analytics.google.tracking_id }}','auto');
+  ga('set', 'anonymizeIp', {{ site.analytics.google.anonymize_ip | default: false }});
+  ga('send','pageview')
+</script>
+<script src="https://www.google-analytics.com/analytics.js" async></script>

_includes/analytics-providers/google.html

@@ -0,0 +1,14 @@
+<script>
+  var _gaq = _gaq || [];
+  _gaq.push(['_setAccount', '{{ site.analytics.google.tracking_id }}']);
+  {% if site.analytics.google.anonymize_ip == true %}
+    _gaq.push(['_gat._anonymizeIp']);
+  {% endif %}
+  _gaq.push(['_trackPageview']);
+
+  (function() {
+    var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+    ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+  })();
+</script>

_includes/analytics.html

@@ -1,9 +1,14 @@
-<!-- Global site tag (gtag.js) - Google Analytics -->
-<script async src="https://www.googletagmanager.com/gtag/js?id=UA-132558656-1"></script>
-<script>
-  window.dataLayer = window.dataLayer || [];
-  function gtag(){dataLayer.push(arguments);}
-  gtag('js', new Date());
+{% if jekyll.environment == 'production' and site.analytics.provider and page.analytics != false %}
 
-  gtag('config', 'UA-132558656-1');
-</script>
+{% case site.analytics.provider %}
+{% when "google" %}
+  {% include /analytics-providers/google.html %}
+{% when "google-universal" %}
+  {% include /analytics-providers/google-universal.html %}
+{% when "google-gtag" %}
+  {% include /analytics-providers/google-gtag.html %}
+{% when "custom" %}
+  {% include /analytics-providers/custom.html %}
+{% endcase %}
+
+{% endif %}

_includes/archive-single.html

@@ -0,0 +1,52 @@
+{% if post.header.teaser %}
+  {% capture teaser %}{{ post.header.teaser }}{% endcapture %}
+{% else %}
+  {% assign teaser = site.teaser %}
+{% endif %}
+
+{% if post.id %}
+  {% assign title = post.title | markdownify | remove: "<p>" | remove: "</p>" %}
+{% else %}
+  {% assign title = post.title %}
+{% endif %}
+
+<div class="{{ include.type | default: 'list' }}__item">
+  <article class="archive__item" itemscope itemtype="https://schema.org/CreativeWork">
+    {% if include.type == "grid" and teaser %}
+      <div class="archive__item-teaser">
+        <img src="{{ teaser | relative_url }}" alt="">
+      </div>
+    {% endif %}
+    <br><strong><a href="{{ post.url | relative_url }}" rel="permalink">{{ title }}</a></strong>
+    {% if post.excerpt %}<p class="archive__item-excerpt" itemprop="description">{{ post.excerpt | markdownify | strip_html | truncate: 300 }}</p>{% endif %}
+    <p class="page__meta"><strong>Updated:</strong> {{ post.last_modified_at }} <i class="far fa-clock" aria-hidden="true"></i> {% include read-time.html %}</p>
+	{% if post.name and post.categories contains 'Companies' %}
+   	  {% assign tags = Nil%}
+      {% assign sorted_tags = Nil%}
+      {% for company in site.data.companys %}
+        {% if post.name == company.name %}
+    	  {% if company.parent %}{% assign tags = company.parent | push: post.name %}{% endif %}
+    	  {% if company.related != Nil %}
+    	    {% if company.related contains ';'%}
+    		  {% assign tgs = company.related |split: '; ' | push: post.name %}
+    		  {% assign tags = tags | concat: tgs %}
+    	    {% else %}
+    		  {% assign tags = tags | push: company.related | push: post.name %}
+    	    {% endif%}   
+    	  {% endif %}
+    	  {% if tags != Nil %}
+    	    {% assign sorted_tags = tags | concat: post.tags | uniq | compact | sort_natural %}
+    	  {% elsif post.tags !=Nil %}
+    	    {% assign sorted_tags = post.tags | uniq | compact | sort_natural %} 
+    	  {% endif%}
+        {% endif %}
+      {% endfor %}
+	{% else %}
+	  {% assign sorted_tags = post.tags | uniq | compact | sort %}
+	{% endif %}
+    <small><strong>Tags:</strong></small>
+	{% for tag in sorted_tags %}
+      <div class="tags">{{ tag }}</div> 
+    {% endfor %}
+  </article> 
+</div>

_includes/author-profile-custom-links.html

@@ -0,0 +1,7 @@
+<!--
+  <li>
+    <a href="http://link-to-whatever-social-network.com/user/" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+      <i class="fas fa-fw" aria-hidden="true"></i> Custom Social Profile Link
+    </a>
+  </li>
+-->

_includes/author-profile.html

@@ -0,0 +1,246 @@
+{% assign author = page.author | default: page.authors[0] | default: site.author %}
+{% assign author = site.data.authors[author] | default: author %}
+
+<div itemscope itemtype="https://schema.org/Person" class="h-card">
+
+  {% if author.avatar %}
+    <div class="author__avatar">
+      <a href="{{ author.home | default: '/' | absolute_url }}">
+        <img src="{{ author.avatar | relative_url }}" alt="{{ author.name }}" itemprop="image" class="u-photo">
+      </a>
+    </div>
+  {% endif %}
+
+  <div class="author__content">
+    <h3 class="author__name p-name" itemprop="name">
+      <a class="u-url" rel="me" href="{{ author.home | default: '/' | absolute_url }}" itemprop="url">{{ author.name }}</a>
+    </h3>
+    {% if author.bio %}
+      <div class="author__bio p-note" itemprop="description">
+        {{ author.bio | markdownify }}
+      </div>
+    {% endif %}
+  </div>
+
+  <div class="author__urls-wrapper">
+    <button class="btn btn--inverse">{{ site.data.ui-text[site.locale].follow_label | remove: ":" | default: "Follow" }}</button>
+    <ul class="author__urls social-icons">
+      {% if author.location %}
+        <li itemprop="homeLocation" itemscope itemtype="https://schema.org/Place">
+          <i class="fas fa-fw fa-map-marker-alt" aria-hidden="true"></i> <span itemprop="name" class="p-locality">{{ author.location }}</span>
+        </li>
+      {% endif %}
+
+      {% if author.links %}
+        {% for link in author.links %}
+          {% if link.label and link.url %}
+            <li><a href="{{ link.url }}" rel="nofollow noopener noreferrer me"{% if link.url contains 'http' %} itemprop="sameAs"{% endif %}><i class="{{ link.icon | default: 'fas fa-link' }}" aria-hidden="true"></i><span class="label">{{ link.label }}</span></a></li>
+          {% endif %}
+        {% endfor %}
+      {% endif %}
+
+      {% if author.uri %}
+        <li>
+          <a href="{{ author.uri }}" itemprop="url" rel="me">
+            <i class="fas fa-fw fa-link" aria-hidden="true"></i><span class="label">{{ site.data.ui-text[site.locale].website_label | default: "Website" }}</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.email %}
+        <li>
+          <a href="mailto:{{ author.email }}" rel="me" class="u-email">
+            <meta itemprop="email" content="{{ author.email }}" />
+            <i class="fas fa-fw fa-envelope-square" aria-hidden="true"></i><span class="label">{{ site.data.ui-text[site.locale].email_label | default: "Email" }}</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.keybase %}
+        <li>
+          <a href="https://keybase.io/{{ author.keybase }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-keybase" aria-hidden="true"></i><span class="label">Keybase</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.twitter %}
+        <li>
+          <a href="https://twitter.com/{{ author.twitter }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-twitter-square" aria-hidden="true"></i><span class="label">Twitter</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.facebook %}
+        <li>
+          <a href="https://www.facebook.com/{{ author.facebook }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-facebook-square" aria-hidden="true"></i><span class="label">Facebook</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.linkedin %}
+        <li>
+          <a href="https://www.linkedin.com/in/{{ author.linkedin }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-linkedin" aria-hidden="true"></i><span class="label">LinkedIn</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.xing %}
+        <li>
+          <a href="https://www.xing.com/profile/{{ author.xing }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-xing-square" aria-hidden="true"></i><span class="label">XING</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.instagram %}
+        <li>
+          <a href="https://instagram.com/{{ author.instagram }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-instagram" aria-hidden="true"></i><span class="label">Instagram</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.tumblr %}
+        <li>
+          <a href="https://{{ author.tumblr }}.tumblr.com" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-tumblr-square" aria-hidden="true"></i><span class="label">Tumblr</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.bitbucket %}
+        <li>
+          <a href="https://bitbucket.org/{{ author.bitbucket }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-bitbucket" aria-hidden="true"></i><span class="label">Bitbucket</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.github %}
+        <li>
+          <a href="https://github.com/{{ author.github }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-github" aria-hidden="true"></i><span class="label">GitHub</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.gitlab %}
+        <li>
+          <a href="https://gitlab.com/{{ author.gitlab }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-gitlab" aria-hidden="true"></i><span class="label">GitLab</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.stackoverflow %}
+        <li>
+          <a href="https://stackoverflow.com/users/{{ author.stackoverflow }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-stack-overflow" aria-hidden="true"></i><span class="label">Stack Overflow</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.lastfm %}
+        <li>
+          <a href="https://last.fm/user/{{ author.lastfm }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-lastfm-square" aria-hidden="true"></i><span class="label">Last.fm</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.dribbble %}
+        <li>
+          <a href="https://dribbble.com/{{ author.dribbble }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-dribbble" aria-hidden="true"></i><span class="label">Dribbble</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.pinterest %}
+        <li>
+          <a href="https://www.pinterest.com/{{ author.pinterest }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-pinterest" aria-hidden="true"></i><span class="label">Pinterest</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.foursquare %}
+        <li>
+          <a href="https://foursquare.com/{{ author.foursquare }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-foursquare" aria-hidden="true"></i><span class="label">Foursquare</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.steam %}
+        <li>
+          <a href="https://steamcommunity.com/id/{{ author.steam }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-steam" aria-hidden="true"></i><span class="label">Steam</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.youtube %}
+        {% if author.youtube contains "://" %}
+          <li>
+            <a href="{{ author.youtube }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+              <i class="fab fa-fw fa-youtube" aria-hidden="true"></i><span class="label">YouTube</span>
+            </a>
+          </li>
+        {% elsif author.youtube %}
+          <li>
+            <a href="https://www.youtube.com/user/{{ author.youtube }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+              <i class="fab fa-fw fa-youtube" aria-hidden="true"></i><span class="label">YouTube</span>
+            </a>
+          </li>
+        {% endif %}
+      {% endif %}
+
+      {% if author.soundcloud %}
+        <li>
+          <a href="https://soundcloud.com/{{ author.soundcloud }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-soundcloud" aria-hidden="true"></i><span class="label">SoundCloud</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.weibo %}
+        <li>
+          <a href="https://www.weibo.com/{{ author.weibo }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-weibo" aria-hidden="true"></i><span class="label">Weibo</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.flickr %}
+        <li>
+          <a href="https://www.flickr.com/{{ author.flickr }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-flickr" aria-hidden="true"></i><span class="label">Flickr</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.codepen %}
+        <li>
+          <a href="https://codepen.io/{{ author.codepen }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-codepen" aria-hidden="true"></i><span class="label">CodePen</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% if author.vine %}
+        <li>
+          <a href="https://vine.co/u/{{ author.vine }}" itemprop="sameAs" rel="nofollow noopener noreferrer me">
+            <i class="fab fa-fw fa-vine" aria-hidden="true"></i><span class="label">{{ site.data.ui-text[site.locale].email_label | default: "Email" }}</span>
+          </a>
+        </li>
+      {% endif %}
+
+      {% include author-profile-custom-links.html %}
+    </ul>
+  </div>
+</div>

_includes/authors-list.html

@@ -0,0 +1,19 @@
+<p class="page__taxonomy">
+    <strong><i class="fas fa-fw fa-users" aria-hidden="true"></i> Authors:</strong>
+    {% assign authorCount = page.authors | size %}
+    {% if authorCount == 0 %}
+        No author
+    {% elsif authorCount == 1 %}
+        {{ page.authors | first }}
+    {% else %}
+        {% for author in page.authors %}
+            {% if forloop.first %}
+            <a href="{{ author.url }}" rel="author">{{ author }}</a>
+            {% elsif forloop.last %}
+                and <a href="{{ author.url }}" rel="author">{{ author }}</a>
+            {% else %}
+                , <a href="{{ author.url }}" rel="author">{{ author }}</a>
+            {% endif %}
+        {% endfor %}
+    {% endif %}
+</p>

_includes/breadcrumbs.html

@@ -0,0 +1,40 @@
+{% case site.category_archive.type %}
+  {% when "liquid" %}
+    {% assign path_type = "#" %}
+  {% when "jekyll-archives" %}
+    {% assign path_type = nil %}
+{% endcase %}
+
+{% if page.collection != 'posts' %}
+  {% assign path_type = nil %}
+  {% assign crumb_path = '/' %}
+{% else %}
+  {% assign crumb_path = site.category_archive.path %}
+{% endif %}
+
+<nav class="breadcrumbs">
+  <ol itemscope itemtype="https://schema.org/BreadcrumbList">
+    {% assign crumbs = page.url | split: '/' %}
+    {% assign i = 1 %}
+    {% for crumb in crumbs offset: 1 %}
+      {% if forloop.first %}
+        <li itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
+          <a href="{{ '/' | relative_url }}" itemprop="item"><span itemprop="name">{{ site.data.ui-text[site.locale].breadcrumb_home_label | default: "Home" }}</span></a>
+
+          <meta itemprop="position" content="{{ i }}" />
+        </li>
+        <span class="sep">{{ site.data.ui-text[site.locale].breadcrumb_separator | default: "/" }}</span>
+      {% endif %}
+      {% if forloop.last %}
+        <li class="current">{{ page.title }}</li>
+      {% else %}
+        {% assign i = i | plus: 1 %}
+        <li itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
+          <a href="{{ crumb | downcase | replace: '%20', '-' | prepend: path_type | prepend: crumb_path | relative_url }}" itemprop="item"><span itemprop="name">{{ crumb | replace: '-', ' ' | replace: '%20', ' ' | capitalize }}</span></a>
+          <meta itemprop="position" content="{{ i }}" />
+        </li>
+        <span class="sep">{{ site.data.ui-text[site.locale].breadcrumb_separator | default: "/" }}</span>
+      {% endif %}
+    {% endfor %}
+  </ol>
+</nav>

_includes/category-list.html

@@ -0,0 +1,19 @@
+{% case site.category_archive.type %}
+  {% when "liquid" %}
+    {% assign path_type = "#" %}
+  {% when "jekyll-archives" %}
+    {% assign path_type = nil %}
+{% endcase %}
+
+{% if site.category_archive.path %}
+  {% assign categories_sorted = page.categories | sort_natural %}
+
+  <p class="page__taxonomy">
+    <strong><i class="fas fa-fw fa-folder-open" aria-hidden="true"></i> {{ site.data.ui-text[site.locale].categories_label | default: "Categories:" }} </strong>
+    <span itemprop="keywords">
+    {% for category_word in categories_sorted %}
+      <a href="{{ category_word | slugify | prepend: path_type | prepend: site.category_archive.path | relative_url }}" class="page__taxonomy-item p-category" rel="tag">{{ category_word }}</a>{% unless forloop.last %}<span class="sep">, </span>{% endunless %}
+    {% endfor %}
+    </span>
+  </p>
+{% endif %}

_includes/comment.html

@@ -0,0 +1,22 @@
+<article id="comment{{ include.index }}" class="js-comment comment" itemprop="comment" itemscope itemtype="https://schema.org/Comment">
+  <div class="comment__avatar-wrapper">
+    <img class="comment__avatar" src="https://www.gravatar.com/avatar/{{ include.email }}?d=mm&s=80" alt="{{ include.name }}">
+  </div>
+  <div class="comment__content-wrapper">
+    <h3 class="comment__author" itemprop="author" itemscope itemtype="https://schema.org/Person">
+      {% unless include.url == blank %}
+        <span itemprop="name"><a rel="external nofollow" itemprop="url" href="{{ include.url }}">{{ include.name }}</a></span>
+      {% else %}
+        <span itemprop="name">{{ include.name }}</span>
+      {% endunless %}
+    </h3>
+    <p class="comment__date">
+      {% if include.date %}
+        {% if include.index %}<a href="#comment{{ include.index }}" itemprop="url">{% endif %}
+        <time datetime="{{ include.date | date_to_xmlschema }}" itemprop="datePublished">{{ include.date | date: "%B %-d, %Y at %I:%M %p" }}</time>
+        {% if include.index %}</a>{% endif %}
+      {% endif %}
+    </p>
+    <div itemprop="text">{{ include.message | markdownify }}</div>
+  </div>
+</article>

_includes/comments-providers/custom.html

@@ -0,0 +1,3 @@
+<!-- start custom comments snippet -->
+
+<!-- end custom comments snippet -->

_includes/comments-providers/custom_scripts.html

@@ -0,0 +1,3 @@
+<!-- start custom comments scripts -->
+
+<!-- end custom comments scripts -->

_includes/comments-providers/discourse.html

@@ -0,0 +1,13 @@
+{% if site.comments.discourse.server %}
+{% capture canonical %}{% if site.permalink contains '.html' %}{{ page.url | absolute_url }}{% else %}{{ page.url | absolute_url | remove:'index.html' | strip_slash }}{% endif %}{% endcapture %}
+<script type="text/javascript">
+    DiscourseEmbed = { discourseUrl: '//{{ site.comments.discourse.server }}/',
+                       discourseEmbedUrl: '{{ canonical }}' };
+   (function () {
+     var d = document.createElement('script'); d.type = 'text/javascript'; d.async = true;
+     d.src = DiscourseEmbed.discourseUrl + 'javascripts/embed.js';
+     (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(d);
+   })();
+</script>
+<noscript>Please enable JavaScript to view the comments powered by <a href="https://www.discourse.org/">Discourse.</a></noscript>
+{% endif %}

_includes/comments-providers/disqus.html

@@ -0,0 +1,15 @@
+{% if site.comments.disqus.shortname %}
+  <script>
+    var disqus_config = function () {
+      this.page.url = "{{ page.url | absolute_url }}";  /* Replace PAGE_URL with your page's canonical URL variable */
+      this.page.identifier = "{{ page.id }}"; /* Replace PAGE_IDENTIFIER with your page's unique identifier variable */
+    };
+    (function() { /* DON'T EDIT BELOW THIS LINE */
+      var d = document, s = d.createElement('script');
+      s.src = 'https://{{ site.comments.disqus.shortname }}.disqus.com/embed.js';
+      s.setAttribute('data-timestamp', +new Date());
+      (d.head || d.body).appendChild(s);
+    })();
+  </script>
+<noscript>Please enable JavaScript to view the <a href="https://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>
+{% endif %}

_includes/comments-providers/facebook.html

@@ -0,0 +1,8 @@
+<div id="fb-root"></div>
+<script>(function(d, s, id) {
+  var js, fjs = d.getElementsByTagName(s)[0];
+  if (d.getElementById(id)) return;
+  js = d.createElement(s); js.id = id;
+  js.src = "//connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.5{% if site.comments.facebook.appid %}&appId={{ site.comments.facebook.appid }}{% endif %}";
+  fjs.parentNode.insertBefore(js, fjs);
+}(document, 'script', 'facebook-jssdk'));</script>

_includes/comments-providers/giscus.html

@@ -0,0 +1,24 @@
+<script>
+  'use strict';
+
+  (function () {
+    var commentContainer = document.querySelector('#giscus-comments');
+
+    if (!commentContainer) {
+      return;
+    }
+
+    var script = document.createElement('script');
+    script.setAttribute('src', 'https://giscus.app/client.js');
+    script.setAttribute('data-repo', '{{ site.repository | downcase }}');
+    script.setAttribute('data-repo-id', '{{ site.comments.giscus.repo_id }}');
+    script.setAttribute('data-category', '{{ site.comments.giscus.category_name }}');
+    script.setAttribute('data-category-id', '{{ site.comments.giscus.category_id }}');
+    script.setAttribute('data-mapping', '{{ site.comments.giscus.discussion_term | default: "pathname" }}');
+    script.setAttribute('data-reactions-enabled', '{{ site.comments.giscus.reactions_enabled | default: 1 }}');
+    script.setAttribute('data-theme', '{{ site.comments.giscus.theme | default: "light" }}');
+    script.setAttribute('crossorigin', 'anonymous');
+
+    commentContainer.appendChild(script);
+  })();
+</script>

_includes/comments-providers/scripts.html

@@ -0,0 +1,20 @@
+{% if site.comments.provider and page.comments %}
+{% case site.comments.provider %}
+  {% when "disqus" %}
+    {% include /comments-providers/disqus.html %}
+  {% when "discourse" %}
+    {% include /comments-providers/discourse.html %}
+  {% when "facebook" %}
+    {% include /comments-providers/facebook.html %}
+  {% when "staticman" %}
+    {% include /comments-providers/staticman.html %}
+  {% when "staticman_v2" %}
+    {% include /comments-providers/staticman_v2.html %}
+  {% when "utterances" %}
+    {% include /comments-providers/utterances.html %}
+  {% when "giscus" %}
+    {% include /comments-providers/giscus.html %}
+  {% when "custom" %}
+    {% include /comments-providers/custom_scripts.html %}
+{% endcase %}
+{% endif %}

_includes/comments-providers/staticman.html

@@ -0,0 +1,40 @@
+{% if site.repository and site.staticman.branch %}
+  <script>
+    (function ($) {
+    $('#new_comment').submit(function () {
+      var form = this;
+
+      $(form).addClass('disabled');
+      $('#comment-form-submit').html('<i class="fas fa-spinner fa-spin fa-fw"></i> {{ site.data.ui-text[site.locale].loading_label | default: "Loading..." }}');
+
+      $.ajax({
+        type: $(this).attr('method'),
+        url: $(this).attr('action'),
+        data: $(this).serialize(),
+        contentType: 'application/x-www-form-urlencoded',
+        success: function (data) {
+          $('#comment-form-submit').html('{{ site.data.ui-text[site.locale].comment_btn_submitted | default: "Submitted" }}');
+          $('.page__comments-form .js-notice').removeClass('notice--danger');
+          $('.page__comments-form .js-notice').addClass('notice--success');
+          showAlert('{{ site.data.ui-text[site.locale].comment_success_msg | default: "Thanks for your comment! It will show on the site once it has been approved." }}');
+        },
+        error: function (err) {
+          console.log(err);
+          $('#comment-form-submit').html('{{ site.data.ui-text[site.locale].comment_btn_submit  | default: "Submit Comment" }}');
+          $('.page__comments-form .js-notice').removeClass('notice--success');
+          $('.page__comments-form .js-notice').addClass('notice--danger');
+          showAlert('{{ site.data.ui-text[site.locale].comment_error_msg | default: "Sorry, there was an error with your submission. Please make sure all required fields have been completed and try again." }}');
+          $(form).removeClass('disabled');
+        }
+      });
+
+      return false;
+    });
+
+    function showAlert(message) {
+      $('.page__comments-form .js-notice').removeClass('hidden');
+      $('.page__comments-form .js-notice-text').html(message);
+    }
+  })(jQuery);
+  </script>
+{% endif %}

_includes/comments-providers/staticman_v2.html

@@ -0,0 +1,40 @@
+{% if site.repository and site.comments.staticman.branch %}
+  <script>
+    (function ($) {
+    $('#new_comment').submit(function () {
+      var form = this;
+
+      $(form).addClass('disabled');
+      $('#comment-form-submit').html('<i class="fas fa-spinner fa-spin fa-fw"></i> {{ site.data.ui-text[site.locale].loading_label | default: "Loading..." }}');
+
+      $.ajax({
+        type: $(this).attr('method'),
+        url: $(this).attr('action'),
+        data: $(this).serialize(),
+        contentType: 'application/x-www-form-urlencoded',
+        success: function (data) {
+          $('#comment-form-submit').html('{{ site.data.ui-text[site.locale].comment_btn_submitted | default: "Submitted" }}');
+          $('.page__comments-form .js-notice').removeClass('notice--danger');
+          $('.page__comments-form .js-notice').addClass('notice--success');
+          showAlert('{{ site.data.ui-text[site.locale].comment_success_msg | default: "Thanks for your comment! It will show on the site once it has been approved." }}');
+        },
+        error: function (err) {
+          console.log(err);
+          $('#comment-form-submit').html('{{ site.data.ui-text[site.locale].comment_btn_submit  | default: "Submit Comment" }}');
+          $('.page__comments-form .js-notice').removeClass('notice--success');
+          $('.page__comments-form .js-notice').addClass('notice--danger');
+          showAlert('{{ site.data.ui-text[site.locale].comment_error_msg | default: "Sorry, there was an error with your submission. Please make sure all required fields have been completed and try again." }}');
+          $(form).removeClass('disabled');
+        }
+      });
+
+      return false;
+    });
+
+    function showAlert(message) {
+      $('.page__comments-form .js-notice').removeClass('hidden');
+      $('.page__comments-form .js-notice-text').html(message);
+    }
+  })(jQuery);
+  </script>
+{% endif %}

_includes/comments-providers/utterances.html

@@ -0,0 +1,21 @@
+<script>
+  'use strict';
+
+  (function() {
+    var commentContainer = document.querySelector('#utterances-comments');
+
+    if (!commentContainer) {
+      return;
+    }
+
+    var script = document.createElement('script');
+    script.setAttribute('src', 'https://utteranc.es/client.js');
+    script.setAttribute('repo', '{{ site.repository }}');
+    script.setAttribute('issue-term', '{{ site.comments.utterances.issue_term | default: "pathname" }}');
+    {% if site.comments.utterances.label %}script.setAttribute('label', '{{ site.comments.utterances.label }}');{% endif %}
+    script.setAttribute('theme', '{{ site.comments.utterances.theme | default: "github-light" }}');
+    script.setAttribute('crossorigin', 'anonymous');
+
+    commentContainer.appendChild(script);
+  })();
+</script>

_includes/comments.html

@@ -0,0 +1,180 @@
+<div class="page__comments">
+  {% capture comments_label %}{{ site.data.ui-text[site.locale].comments_label | default: "Comments" }}{% endcapture %}
+  {% case site.comments.provider %}
+    {% when "discourse" %}
+      <h4 class="page__comments-title">{{ comments_label }}</h4>
+      <section id="discourse-comments"></section>
+    {% when "disqus" %}
+      <h4 class="page__comments-title">{{ comments_label }}</h4>
+      <section id="disqus_thread"></section>
+    {% when "facebook" %}
+      <h4 class="page__comments-title">{{ comments_label }}</h4>
+      <section class="fb-comments" data-href="{{ page.url | absolute_url }}" data-mobile="true" data-num-posts="{{ site.comments.facebook.num_posts | default: 5 }}" data-width="100%" data-colorscheme="{{ site.comments.facebook.colorscheme | default: 'light' }}"></section>
+    {% when "staticman_v2" %}
+      <section id="static-comments">
+        {% if site.repository and site.comments.staticman.branch %}
+          <!-- Start static comments -->
+          <div class="js-comments">
+            {% if site.data.comments[page.slug] %}
+              <h4 class="page__comments-title">{{ site.data.ui-text[site.locale].comments_title | default: "Comments" }}</h4>
+              {% assign comments = site.data.comments[page.slug] %}
+
+              <!-- In order to sort by date we must have an array of objects, not an array of arrays, so
+                    create a new array of plain comment objects and then sort by the comment date. -->
+              {% assign commentObjects = '' | split: '' %}
+              {% for comment in comments %}
+                {% assign commentObject = comment[1] %}
+                {% assign commentObjects = commentObjects | push: commentObject %}
+              {% endfor %}
+              {% assign comments = commentObjects | sort: "date" %}
+
+              {% for comment in comments %}
+                {% assign email = comment.email %}
+                {% assign name = comment.name %}
+                {% assign url = comment.url %}
+                {% assign date = comment.date %}
+                {% assign message = comment.message %}
+                {% include comment.html index=forloop.index email=email name=name url=url date=date message=message %}
+              {% endfor %}
+            {% endif %}
+          </div>
+          <!-- End static comments -->
+
+          <!-- Start new comment form -->
+          <div class="page__comments-form">
+            <h4 class="page__comments-title">{{ site.data.ui-text[site.locale].comments_label | default: "Leave a Comment" }}</h4>
+            <p class="small">{{ site.data.ui-text[site.locale].comment_form_info | default: "Your email address will not be published. Required fields are marked" }} <span class="required">*</span></p>
+            <form id="new_comment" class="page__comments-form js-form form" method="post" action="{{ site.comments.staticman.endpoint }}{{ site.repository }}/{{ site.comments.staticman.branch }}/comments">
+              <div class="form__spinner">
+                <i class="fas fa-spinner fa-spin fa-3x fa-fw"></i>
+                <span class="sr-only">{{ site.data.ui-text[site.locale].loading_label | default: "Loading..." }}</span>
+              </div>
+
+              <div class="form-group">
+                <label for="comment-form-message">{{ site.data.ui-text[site.locale].comment_form_comment_label | default: "Comment" }} <small class="required">*</small></label>
+                <textarea type="text" rows="3" id="comment-form-message" name="fields[message]" tabindex="1"></textarea>
+                <div class="small help-block"><a href="https://daringfireball.net/projects/markdown/">{{ site.data.ui-text[site.locale].comment_form_md_info | default: "Markdown is supported." }}</a></div>
+              </div>
+              <div class="form-group">
+                <label for="comment-form-name">{{ site.data.ui-text[site.locale].comment_form_name_label | default: "Name" }} <small class="required">*</small></label>
+                <input type="text" id="comment-form-name" name="fields[name]" tabindex="2" />
+              </div>
+              <div class="form-group">
+                <label for="comment-form-email">{{ site.data.ui-text[site.locale].comment_form_email_label | default: "Email address" }} <small class="required">*</small></label>
+                <input type="email" id="comment-form-email" name="fields[email]" tabindex="3" />
+              </div>
+              <div class="form-group">
+                <label for="comment-form-url">{{ site.data.ui-text[site.locale].comment_form_website_label | default: "Website (optional)" }}</label>
+                <input type="url" id="comment-form-url" name="fields[url]" tabindex="4"/>
+              </div>
+              <div class="form-group hidden" style="display: none;">
+                <input type="hidden" name="options[slug]" value="{{ page.slug }}">
+                <label for="comment-form-location">Not used. Leave blank if you are a human.</label>
+                <input type="text" id="comment-form-location" name="fields[hidden]" autocomplete="off"/>
+                {% if site.reCaptcha.siteKey %}<input type="hidden" name="options[reCaptcha][siteKey]" value="{{ site.reCaptcha.siteKey }}">{% endif %}
+                {% if site.reCaptcha.secret %}<input type="hidden" name="options[reCaptcha][secret]" value="{{ site.reCaptcha.secret }}">{% endif %}
+              </div>
+              <!-- Start comment form alert messaging -->
+              <p class="hidden js-notice">
+                <strong class="js-notice-text"></strong>
+              </p>
+              <!-- End comment form alert messaging -->
+              {% if site.reCaptcha.siteKey %}
+                <div class="form-group">
+                  <div class="g-recaptcha" data-sitekey="{{ site.reCaptcha.siteKey }}"></div>
+                </div>
+              {% endif %}
+              <div class="form-group">
+                <button type="submit" id="comment-form-submit" tabindex="5" class="btn btn--primary btn--large">{{ site.data.ui-text[site.locale].comment_btn_submit | default: "Submit Comment" }}</button>
+              </div>
+            </form>
+          </div>
+          <!-- End new comment form -->
+          {% if site.reCaptcha.siteKey %}<script async src="https://www.google.com/recaptcha/api.js"></script>{% endif %}
+        {% endif %}
+      </section>
+    {% when "staticman" %}
+      <section id="static-comments">
+        {% if site.repository and site.staticman.branch %}
+          <!-- Start static comments -->
+          <div class="js-comments">
+            {% if site.data.comments[page.slug] %}
+              <h4 class="page__comments-title">{{ site.data.ui-text[site.locale].comments_title | default: "Comments" }}</h4>
+              {% assign comments = site.data.comments[page.slug] %}
+
+              <!-- In order to sort by date we must have an array of objects, not an array of arrays, so
+                    create a new array of plain comment objects and then sort by the comment date. -->
+              {% assign commentObjects = '' | split: '' %}
+              {% for comment in comments %}
+                {% assign commentObject = comment[1] %}
+                {% assign commentObjects = commentObjects | push: commentObject %}
+              {% endfor %}
+              {% assign comments = commentObjects | sort: "date" %}
+
+              {% for comment in comments %}
+                {% assign email = comment.email %}
+                {% assign name = comment.name %}
+                {% assign url = comment.url %}
+                {% assign date = comment.date %}
+                {% assign message = comment.message %}
+                {% include comment.html index=forloop.index email=email name=name url=url date=date message=message %}
+              {% endfor %}
+            {% endif %}
+          </div>
+          <!-- End static comments -->
+
+          <!-- Start new comment form -->
+          <div class="page__comments-form">
+            <h4 class="page__comments-title">{{ site.data.ui-text[site.locale].comments_label | default: "Leave a Comment" }}</h4>
+            <p class="small">{{ site.data.ui-text[site.locale].comment_form_info | default: "Your email address will not be published. Required fields are marked" }} <span class="required">*</span></p>
+            <form id="new_comment" class="page__comments-form js-form form" method="post" action="https://api.staticman.net/v1/entry/{{ site.repository }}/{{ site.staticman.branch }}">
+              <div class="form__spinner">
+                <i class="fas fa-spinner fa-spin fa-3x fa-fw"></i>
+                <span class="sr-only">{{ site.data.ui-text[site.locale].loading_label | default: "Loading..." }}</span>
+              </div>
+
+              <div class="form-group">
+                <label for="comment-form-message">{{ site.data.ui-text[site.locale].comment_form_comment_label | default: "Comment" }} <small class="required">*</small></label>
+                <textarea type="text" rows="3" id="comment-form-message" name="fields[message]" tabindex="1"></textarea>
+                <div class="small help-block"><a href="https://daringfireball.net/projects/markdown/">{{ site.data.ui-text[site.locale].comment_form_md_info | default: "Markdown is supported." }}</a></div>
+              </div>
+              <div class="form-group">
+                <label for="comment-form-name">{{ site.data.ui-text[site.locale].comment_form_name_label | default: "Name" }} <small class="required">*</small></label>
+                <input type="text" id="comment-form-name" name="fields[name]" tabindex="2" />
+              </div>
+              <div class="form-group">
+                <label for="comment-form-email">{{ site.data.ui-text[site.locale].comment_form_email_label | default: "Email address" }} <small class="required">*</small></label>
+                <input type="email" id="comment-form-email" name="fields[email]" tabindex="3" />
+              </div>
+              <div class="form-group">
+                <label for="comment-form-url">{{ site.data.ui-text[site.locale].comment_form_website_label | default: "Website (optional)" }}</label>
+                <input type="url" id="comment-form-url" name="fields[url]" tabindex="4"/>
+              </div>
+              <div class="form-group hidden" style="display: none;">
+                <input type="hidden" name="options[slug]" value="{{ page.slug }}">
+                <label for="comment-form-location">Not used. Leave blank if you are a human.</label>
+                <input type="text" id="comment-form-location" name="fields[hidden]" autocomplete="off"/>
+              </div>
+              <!-- Start comment form alert messaging -->
+              <p class="hidden js-notice">
+                <strong class="js-notice-text"></strong>
+              </p>
+              <!-- End comment form alert messaging -->
+              <div class="form-group">
+                <button type="submit" id="comment-form-submit" tabindex="5" class="btn btn--primary btn--large">{{ site.data.ui-text[site.locale].comment_btn_submit | default: "Submit Comment" }}</button>
+              </div>
+            </form>
+          </div>
+          <!-- End new comment form -->
+        {% endif %}
+      </section>
+    {% when "utterances" %}
+      <h4 class="page__comments-title">{{ comments_label }}</h4>
+      <section id="utterances-comments"></section>
+    {% when "giscus" %}
+      <h4 class="page__comments-title">{{ comments_label }}</h4>
+      <section id="giscus-comments"></section>
+    {% when "custom" %}
+      {% include /comments-providers/custom.html %}
+  {% endcase %}
+</div>

_includes/documents-collection.html

@@ -0,0 +1,15 @@
+{% assign entries = site[include.collection] %}
+
+{% if include.sort_by %}
+  {% assign entries = entries | sort: include.sort_by %}
+{% endif %}
+
+{% if include.sort_order == 'reverse' %}
+  {% assign entries = entries | reverse %}
+{% endif %}
+
+{%- for post in entries -%}
+  {%- unless post.hidden -%}
+    {% include archive-single.html %}
+  {%- endunless -%}
+{%- endfor -%}

_includes/entry_single.html

@@ -0,0 +1,47 @@
+{%assign attributes = "location,region,policy,event,sector,industry,market,focus,projects,tech,standard" | split: "," %}
+{% if page.name == "Decentralized Identifiers" and row.name !=nil and row.name != lastname %}
+  <h3 id="{{row.name}}">{{row.name}}</h3> 
+  {% assign lastname = page.name %} 
+{% endif %}
+<li><a href="{{ row.link }}">{{ row.title }}</a>
+{%if row.parent !=nil and row.parent != "Personal" %}<strong>From</strong>: {{row.parent}}{%endif%}
+  {% if row.authors !=nil%}<strong>By</strong>: 
+    {% if row.authors contains ';' %}{{ row.authors | replace: ";",", "}}
+    {% else %}{{ row.authors}}
+    {%endif%}
+  {%endif%}
+  {% if row.related contains ';' %}
+    <strong>Related</strong>:{%assign related = row.related|split:';'%}
+    {%assign trekker = 0%}
+    {%for item in related%}
+      {%assign trekker = trekker | plus: 1%}
+    {%endfor%}
+    {%for item in related%}
+      {%if item != nil%} {{item|strip}}{%if trekker > 1%},{%assign trekker = trekker | minus: 1%}{%endif%}{%endif%}
+    {%endfor%}
+  {%elsif row.related == nil%}
+  {%else%} 
+    <strong>Related</strong>: {{row.related}}
+  {%endif%}
+  <strong>Type: </strong>{{row.type|strip|capitalize}}
+  {%if row.date != nil%} <strong>{% if row.type == "Working Group" %}Established:{%else%}Date:{% endif %}</strong> {{row.date}}{%endif%}
+  {%for item in row%}
+    {%if attributes contains item.first and item.last != nil %}
+      {% if item.last contains ';' %}
+        <strong>{{item.first|capitalize}}:</strong> 
+        {% assign ray = item.last | split: ';'%}
+        {%for item in ray %}{%if item != " "%} {{item|strip}}{% if forloop.last %}{% else %}, {% endif %}{%endif%}{%endfor%}
+      {% elsif item.last contains ',' %}
+        <strong>{{item.first|capitalize}}:</strong> 
+        {% assign ray = item.last | split: ','%}
+        {%for item in ray %}{%if item != " "%} {{item|strip}}{% if forloop.last %}{% else %}, {% endif %}{%endif%}{%endfor%}
+      {%else%} 
+        <strong>{{item.first|capitalize}}:</strong> {{item.last}}
+      {%endif%}
+    {%endif%}
+  {%endfor%}
+</li>
+{% if row.text %}<blockquote>{{row.text | markdownify}}</blockquote>{%endif%}
+{%if row.image != Nil%}
+  <ul><li><img src="{{row.image}}"/></li></ul>
+{%endif%}

_includes/feature_row

@@ -0,0 +1,41 @@
+{% if include.id %}
+  {% assign feature_row = page[include.id] %}
+{% else %}
+  {% assign feature_row = page.feature_row %}
+{% endif %}
+
+<div class="feature__wrapper">
+
+  {% for f in feature_row %}
+    <div class="feature__item{% if include.type %}--{{ include.type }}{% endif %}">
+      <div class="archive__item">
+        {% if f.image_path %}
+          <div class="archive__item-teaser">
+            <img src="{{ f.image_path | relative_url }}"
+                 alt="{% if f.alt %}{{ f.alt }}{% endif %}">
+            {% if f.image_caption %}
+              <span class="archive__item-caption">{{ f.image_caption | markdownify | remove: "<p>" | remove: "</p>" }}</span>
+            {% endif %}
+          </div>
+        {% endif %}
+
+        <div class="archive__item-body">
+          {% if f.title %}
+            <h2 class="archive__item-title">{{ f.title }}</h2>
+          {% endif %}
+
+          {% if f.excerpt %}
+            <div class="archive__item-excerpt">
+              {{ f.excerpt | markdownify }}
+            </div>
+          {% endif %}
+
+          {% if f.url %}
+            <p><a href="{{ f.url | relative_url }}" class="btn {{ f.btn_class }}">{{ f.btn_label | default: site.data.ui-text[site.locale].more_label | default: "Learn More" }}</a></p>
+          {% endif %}
+        </div>
+      </div>
+    </div>
+  {% endfor %}
+
+</div>

_includes/figure

@@ -0,0 +1,9 @@
+<figure class="{{ include.class }}">
+  <img src="{{ include.image_path | relative_url }}"
+       alt="{% if include.alt %}{{ include.alt }}{% endif %}">
+  {%- if include.caption -%}
+    <figcaption>
+      {{ include.caption | markdownify | remove: "<p>" | remove: "</p>" }}
+    </figcaption>
+  {%- endif -%}
+</figure>

_includes/footer.html

@@ -0,0 +1,24 @@
+<div class="page__footer-follow">
+  <ul class="social-icons">
+    {% if site.data.ui-text[site.locale].follow_label %}
+      <li><strong>{{ site.data.ui-text[site.locale].follow_label }}</strong></li>
+    {% endif %}
+
+    {% if site.footer.links %}
+      {% for link in site.footer.links %}
+        {% if link.label and link.url %}
+          <li><a href="{{ link.url }}" rel="nofollow noopener noreferrer"><i class="{{ link.icon | default: 'fas fa-link' }}" aria-hidden="true"></i> {{ link.label }}</a></li>
+        {% endif %}
+      {% endfor %}
+    {% endif %}
+
+    {% unless site.atom_feed.hide %}
+      <li><a href="{% if site.atom_feed.path %}{{ site.atom_feed.path }}{% else %}{{ '/feed.xml' | relative_url }}{% endif %}"><i class="fas fa-fw fa-rss-square" aria-hidden="true"></i> {{ site.data.ui-text[site.locale].feed_label | default: "Feed" }}</a></li>
+    {% endunless %}
+  </ul>
+</div>
+
+<script data-goatcounter="https://didecentral.goatcounter.com/count" async src="//gc.zgo.at/count.js"></script>
+
+
+<div class="page__footer-copyright">⧉ <a href="https://infominer.xyz">infominer</a> • <a href="https://creativecommons.org/publicdomain/zero/1.0/">Creative Commons (CC0 1.0) Public Domain</a> • Powered by <a href="https://mademistakes.com/work/minimal-mistakes-jekyll-theme/" rel="nofollow">Minimal Mistakes</a> via <a href="https://web-work.tools/jamstack/github-pages-starter-pack/">Github Pages</a>. ⧉</div>

_includes/footer/custom.html

@@ -0,0 +1,3 @@
+<!-- start custom footer snippets -->
+
+<!-- end custom footer snippets -->

_includes/gallery

@@ -0,0 +1,35 @@
+{% if include.id %}
+  {% assign gallery = page[include.id] %}
+{% else %}
+  {% assign gallery = page.gallery %}
+{% endif %}
+
+{% if include.layout %}
+  {% assign gallery_layout = include.layout %}
+{% else %}
+  {% if gallery.size == 2 %}
+    {% assign gallery_layout = 'half' %}
+  {% elsif gallery.size >= 3 %}
+    {% assign gallery_layout = 'third' %}
+  {% else %}
+    {% assign gallery_layout = '' %}
+  {% endif %}
+{% endif %}
+
+<figure class="{{ gallery_layout }} {{ include.class }}">
+  {% for img in gallery %}
+    {% if img.url %}
+      <a href="{{ img.url | relative_url }}"
+        {% if img.title %}title="{{ img.title }}"{% endif %}>
+          <img src="{{ img.image_path | relative_url }}"
+               alt="{% if img.alt %}{{ img.alt }}{% endif %}">
+      </a>
+    {% else %}
+      <img src="{{ img.image_path | relative_url }}"
+           alt="{% if img.alt %}{{ img.alt }}{% endif %}">
+    {% endif %}
+  {% endfor %}
+  {% if include.caption %}
+    <figcaption>{{ include.caption | markdownify | remove: "<p>" | remove: "</p>" }}</figcaption>
+  {% endif %}
+</figure>

_includes/group-by-array

@@ -0,0 +1,47 @@
+<!--
+# Jekyll Group-By-Array 0.1.0
+# https://github.com/mushishi78/jekyll-group-by-array
+# © 2015 Max White <mushishi78@gmail.com>
+# MIT License
+-->
+
+<!-- Initialize -->
+{% assign __empty_array = '' | split: ',' %}
+{% assign group_names = __empty_array %}
+{% assign group_items = __empty_array %}
+
+<!-- Map -->
+{% assign __names =  include.collection | map: include.field %}
+
+<!-- Flatten -->
+{% assign __names =  __names | join: ',' | join: ',' | split: ',' %}
+
+<!-- Uniq -->
+{% assign __names =  __names | sort %}
+{% for name in __names %}
+
+<!-- If not equal to previous then it must be unique as sorted -->
+{% unless name == previous %}
+
+<!-- Push to group_names -->
+{% assign group_names = group_names | push: name %}
+{% endunless %}
+
+{% assign previous = name %}
+{% endfor %}
+
+
+<!-- group_items -->
+{% for name in group_names %}
+
+<!-- Collect if contains -->
+{% assign __item = __empty_array %}
+{% for __element in include.collection %}
+{% if __element[include.field] contains name %}
+{% assign __item = __item | push: __element %}
+{% endif %}
+{% endfor %}
+
+<!-- Push to group_items -->
+{% assign group_items = group_items | push: __item %}
+{% endfor %}

_includes/head.html

@@ -0,0 +1,38 @@
+<meta charset="utf-8">
+
+{% include seo.html %}
+
+{% unless site.atom_feed.hide %}
+  <link href="{% if site.atom_feed.path %}{{ site.atom_feed.path }}{% else %}{{ '/feed.xml' | relative_url }}{% endif %}" type="application/atom+xml" rel="alternate" title="{{ site.title }} Feed">
+{% endunless %}
+
+<!-- https://t.co/dKP3o1e -->
+<meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+<script>
+  document.documentElement.className = document.documentElement.className.replace(/\bno-js\b/g, '') + ' js ';
+</script>
+
+<!-- For all browsers -->
+<link rel="stylesheet" href="{{ '/assets/css/main.css' | relative_url }}">
+<link rel="preload" href="https://cdn.jsdelivr.net/npm/@fortawesome/fontawesome-free@5/css/all.min.css" as="style" onload="this.onload=null;this.rel='stylesheet'">
+<noscript><link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@fortawesome/fontawesome-free@5/css/all.min.css"></noscript>
+
+{% if site.head_scripts %}
+  {% for script in site.head_scripts %}
+    <script src="{{ script | relative_url }}"></script>
+  {% endfor %}
+{% endif %}
+
+
+<meta name="yandex-verification" content="876ea269be433d62" />
+<!-- Favicons -->
+<link rel="apple-touch-icon" sizes="180x180" href="https://decentralized-id.com/assets/icons/apple-touch-icon.png">
+<link rel="icon" type="image/png" sizes="32x32" href="https://decentralized-id.com/assets/icons/favicon-32x32.png">
+<link rel="icon" type="image/png" sizes="16x16" href="https://decentralized-id.com/assets/icons/favicon-16x16.png">
+<link rel="manifest" href="https://decentralized-id.com/assets/icons/site.webmanifest">
+<link rel="mask-icon" href="https://decentralized-id.com/assets/icons/safari-pinned-tab.svg" color="#eeeeef">
+<link rel="shortcut icon" href="https://decentralized-id.com/assets/icons/favicon.ico">
+<meta name="msapplication-TileColor" content="#eeeeef">
+<meta name="msapplication-config" content="https://decentralized-id.com/assets/icons/browserconfig.xml">
+<meta name="theme-color" content="#eeeeef">

_includes/head/custom.html

@@ -0,0 +1,5 @@
+<!-- start custom head snippets -->
+
+<!-- insert favicons. use https://realfavicongenerator.net/ -->
+
+<!-- end custom head snippets -->

_includes/masthead.html

@@ -0,0 +1,35 @@
+{% capture logo_path %}{{ site.logo }}{% endcapture %}
+
+<div class="masthead">
+  <div class="masthead__inner-wrap">
+    <div class="masthead__menu">
+      <nav id="site-nav" class="greedy-nav">
+        {% unless logo_path == empty %}
+          <a class="site-logo" href="{{ '/' | relative_url }}"><img src="{{ logo_path | relative_url }}" alt="{{ site.masthead_title | default: site.title }}"></a>
+        {% endunless %}
+        <a class="site-title" href="{{ '/' | relative_url }}">
+          {{ site.masthead_title | default: site.title }}
+          {% if site.subtitle %}<span class="site-subtitle">{{ site.subtitle }}</span>{% endif %}
+        </a>
+        <ul class="visible-links">
+          {%- for link in site.data.navigation.main -%}
+            <li class="masthead__menu-item">
+              <a href="{{ link.url | relative_url }}"{% if link.description %} title="{{ link.description }}"{% endif %}>{{ link.title }}</a>
+            </li>
+          {%- endfor -%}
+        </ul>
+        {% if site.search == true %}
+        <button class="search__toggle" type="button">
+          <span class="visually-hidden">{{ site.data.ui-text[site.locale].search_label | default: "Toggle search" }}</span>
+          <i class="fas fa-search"></i>
+        </button>
+        {% endif %}
+        <button class="greedy-nav__toggle hidden" type="button">
+          <span class="visually-hidden">{{ site.data.ui-text[site.locale].menu_label | default: "Toggle menu" }}</span>
+          <div class="navicon"></div>
+        </button>
+        <ul class="hidden-links hidden"></ul>
+      </nav>
+    </div>
+  </div>
+</div>

_includes/nav_list

@@ -0,0 +1,26 @@
+{% assign navigation = site.data.navigation[include.nav] %}
+
+<nav class="nav__list">
+  {% if page.sidebar.title %}<h3 class="nav__title" style="padding-left: 0;">{{ page.sidebar.title }}</h3>{% endif %}
+  <input id="ac-toc" name="accordion-toc" type="checkbox" />
+  <label for="ac-toc">{{ site.data.ui-text[site.locale].menu_label | default: "Toggle Menu" }}</label>
+  <ul class="nav__items">
+    {% for nav in navigation %}
+      <li>
+        {% if nav.url %}
+          <a href="{{ nav.url | relative_url }}"><span class="nav__sub-title">{{ nav.title }}</span></a>
+        {% else %}
+          <span class="nav__sub-title">{{ nav.title }}</span>
+        {% endif %}
+
+        {% if nav.children != null %}
+        <ul>
+          {% for child in nav.children %}
+            <li><a href="{{ child.url | relative_url }}"{% if child.url == page.url %} class="active"{% endif %}>{{ child.title }}</a></li>
+          {% endfor %}
+        </ul>
+        {% endif %}
+      </li>
+    {% endfor %}
+  </ul>
+</nav>

_includes/page__date.html

@@ -0,0 +1,6 @@
+{% assign date_format = site.date_format | default: "%B %-d, %Y" %}
+{% if page.last_modified_at %}
+  <p class="page__date"><strong><i class="fas fa-fw fa-calendar-alt" aria-hidden="true"></i> {{ site.data.ui-text[site.locale].date_label | default: "Updated:" }}</strong> <time class="dt-published" datetime="{{ page.last_modified_at | date: "%Y-%m-%d" }}">{{ page.last_modified_at | date: date_format }}</time></p>
+{% elsif page.date %}
+  <p class="page__date"><strong><i class="fas fa-fw fa-calendar-alt" aria-hidden="true"></i> {{ site.data.ui-text[site.locale].date_label | default: "Updated:" }}</strong> <time class="dt-published" datetime="{{ page.date | date_to_xmlschema }}">{{ page.date | date: date_format }}</time></p>
+{% endif %}

_includes/page__hero.html

@@ -0,0 +1,55 @@
+{% capture overlay_img_path %}{{ page.header.overlay_image | relative_url }}{% endcapture %}
+
+{% if page.header.overlay_filter contains "gradient" %}
+  {% capture overlay_filter %}{{ page.header.overlay_filter }}{% endcapture %}
+{% elsif page.header.overlay_filter contains "rgba" %}
+  {% capture overlay_filter %}{{ page.header.overlay_filter }}{% endcapture %}
+  {% capture overlay_filter %}linear-gradient({{ overlay_filter }}, {{ overlay_filter }}){% endcapture %}
+{% elsif page.header.overlay_filter %}
+  {% capture overlay_filter %}rgba(0, 0, 0, {{ page.header.overlay_filter }}){% endcapture %}
+  {% capture overlay_filter %}linear-gradient({{ overlay_filter }}, {{ overlay_filter }}){% endcapture %}
+{% endif %}
+
+{% if page.header.image_description %}
+  {% assign image_description = page.header.image_description %}
+{% else %}
+  {% assign image_description = page.title %}
+{% endif %}
+
+{% assign image_description = image_description | markdownify | strip_html | strip_newlines | escape_once %}
+
+<div class="page__hero{% if page.header.overlay_color or page.header.overlay_image %}--overlay{% endif %}"
+  style="{% if page.header.overlay_color %}background-color: {{ page.header.overlay_color | default: 'transparent' }};{% endif %} {% if overlay_img_path %}background-image: {% if overlay_filter %}{{ overlay_filter }}, {% endif %}url('{{ overlay_img_path }}');{% endif %}"
+>
+  {% if page.header.overlay_color or page.header.overlay_image %}
+    <div class="wrapper">
+      <h1 id="page-title" class="page__title" itemprop="headline">
+        {% if paginator and site.paginate_show_page_num %}
+          {{ site.title }}{% unless paginator.page == 1 %} {{ site.data.ui-text[site.locale].page | default: "Page" }} {{ paginator.page }}{% endunless %}
+        {% else %}
+          {{ page.title | default: site.title | markdownify | remove: "<p>" | remove: "</p>" }}
+        {% endif %}
+      </h1>
+      {% if page.tagline %}
+        <p class="page__lead">{{ page.tagline | markdownify | remove: "<p>" | remove: "</p>" }}</p>
+      {% elsif page.header.show_overlay_excerpt != false and page.excerpt %}
+        <p class="page__lead">{{ page.excerpt | markdownify | remove: "<p>" | remove: "</p>" }}</p>
+      {% endif %}
+      {% include page__meta.html %}
+      {% if page.header.cta_url %}
+        <p><a href="{{ page.header.cta_url | relative_url }}" class="btn btn--light-outline btn--large">{{ page.header.cta_label | default: site.data.ui-text[site.locale].more_label | default: "Learn More" }}</a></p>
+      {% endif %}
+      {% if page.header.actions %}
+        <p>
+        {% for action in page.header.actions %}
+          <a href="{{ action.url | relative_url }}" class="btn btn--light-outline btn--large">{{ action.label | default: site.data.ui-text[site.locale].more_label | default: "Learn More" }}</a>
+        {% endfor %}
+      {% endif %}
+    </div>
+  {% else %}
+    <img src="{{ page.header.image | relative_url }}" alt="{{ image_description }}" class="page__hero-image">
+  {% endif %}
+  {% if page.header.caption %}
+    <span class="page__hero-caption">{{ page.header.caption | markdownify | remove: "<p>" | remove: "</p>" }}</span>
+  {% endif %}
+</div>

_includes/page__hero_video.html

@@ -0,0 +1,2 @@
+{% assign video = page.header.video %}
+{% include video id=video.id provider=video.provider danmaku=video.danmaku %}

_includes/page__meta.html

@@ -0,0 +1,31 @@
+{% assign document = post | default: page %}
+{% if document.read_time or document.show_date %}
+  <p class="page__meta">
+    {% if document.show_date and document.date %}
+      {% assign date = document.date %}
+      <span class="page__meta-date">
+        <i class="far {% if include.type == 'grid' and document.read_time and document.show_date %}fa-fw {% endif %}fa-calendar-alt" aria-hidden="true"></i>
+        {% assign date_format = site.date_format | default: "%B %-d, %Y" %}
+        <time datetime="{{ date | date_to_xmlschema }}">{{ date | date: date_format }}</time>
+      </span>
+    {% endif %}
+
+    {% if document.read_time and document.show_date %}<span class="page__meta-sep"></span>{% endif %}
+
+    {% if document.read_time %}
+      {% assign words_per_minute = document.words_per_minute | default: site.words_per_minute | default: 200 %}
+      {% assign words = document.content | strip_html | number_of_words %}
+
+      <span class="page__meta-readtime">
+        <i class="far {% if include.type == 'grid' and document.read_time and document.show_date %}fa-fw {% endif %}fa-clock" aria-hidden="true"></i>
+        {% if words < words_per_minute %}
+          {{ site.data.ui-text[site.locale].less_than | default: "less than" }} 1 {{ site.data.ui-text[site.locale].minute_read | default: "minute read" }}
+        {% elsif words == words_per_minute %}
+          1 {{ site.data.ui-text[site.locale].minute_read | default: "minute read" }}
+        {% else %}
+          {{ words | divided_by: words_per_minute }} {{ site.data.ui-text[site.locale].minute_read | default: "minute read" }}
+        {% endif %}
+      </span>
+    {% endif %}
+  </p>
+{% endif %}

_includes/page__taxonomy.html

@@ -0,0 +1,11 @@
+{% if page.authors %}
+  {% include authors-list.html %}
+{% endif %}
+
+{% if site.tag_archive.type and page.tags[0] %}
+  {% include tag-list.html %}
+{% endif %}
+
+{% if site.category_archive.type and page.categories[0] %}
+  {% include category-list.html %}
+{% endif %}

_includes/paginator.html

@@ -0,0 +1,69 @@
+{% if paginator.total_pages > 1 %}
+<nav class="pagination">
+  {% assign first_page_path = paginator.first_page_path | default: site.paginate_path | replace: 'page:num', '' | replace: '//', '/' | relative_url %}
+  <ul>
+    {% comment %} Link for previous page {% endcomment %}
+    {% if paginator.previous_page %}
+      {% if paginator.previous_page == 1 %}
+        <li><a href="{{ first_page_path }}">{{ site.data.ui-text[site.locale].pagination_previous | default: "Previous" }}</a></li>
+      {% else %}
+        <li><a href="{{ site.paginate_path | replace: ':num', paginator.previous_page | replace: '//', '/' | relative_url }}">{{ site.data.ui-text[site.locale].pagination_previous | default: "Previous" }}</a></li>
+      {% endif %}
+    {% else %}
+    <li><a href="#" class="disabled"><span aria-hidden="true">{{ site.data.ui-text[site.locale].pagination_previous | default: "Previous" }}</span></a></li>
+    {% endif %}
+
+    {% comment %} First page {% endcomment %}
+    {% if paginator.page == 1 %}
+      <li><a href="#" class="disabled current">1</a></li>
+    {% else %}
+      <li><a href="{{ first_page_path }}">1</a></li>
+    {% endif %}
+
+    {% assign page_start = 2 %}
+    {% if paginator.page > 4 %}
+      {% assign page_start = paginator.page | minus: 2 %}
+      {% comment %} Ellipsis for truncated links {% endcomment %}
+      <li><a href="#" class="disabled">&hellip;</a></li>
+    {% endif %}
+
+    {% assign page_end = paginator.total_pages | minus: 1 %}
+    {% assign pages_to_end = paginator.total_pages | minus: paginator.page %}
+    {% if pages_to_end > 4 %}
+      {% assign page_end = paginator.page | plus: 2 %}
+    {% endif %}
+
+    {% for index in (page_start..page_end) %}
+      {% if index == paginator.page %}
+        <li><a href="{{ site.paginate_path | replace: ':num', index | replace: '//', '/' | relative_url }}" class="disabled current">{{ index }}</a></li>
+      {% else %}
+        {% comment %} Distance from current page and this link {% endcomment %}
+        {% assign dist = paginator.page | minus: index %}
+        {% if dist < 0 %}
+          {% comment %} Distance must be a positive value {% endcomment %}
+          {% assign dist = 0 | minus: dist %}
+        {% endif %}
+        <li><a href="{{ site.paginate_path | replace: ':num', index | relative_url }}">{{ index }}</a></li>
+      {% endif %}
+    {% endfor %}
+
+    {% comment %} Ellipsis for truncated links {% endcomment %}
+    {% if pages_to_end > 3 %}
+      <li><a href="#" class="disabled">&hellip;</a></li>
+    {% endif %}
+
+    {% if paginator.page == paginator.total_pages %}
+      <li><a href="#" class="disabled current">{{ paginator.page }}</a></li>
+    {% else %}
+      <li><a href="{{ site.paginate_path | replace: ':num', paginator.total_pages | replace: '//', '/' | relative_url }}">{{ paginator.total_pages }}</a></li>
+    {% endif %}
+
+    {% comment %} Link next page {% endcomment %}
+    {% if paginator.next_page %}
+      <li><a href="{{ site.paginate_path | replace: ':num', paginator.next_page | replace: '//', '/' | relative_url }}">{{ site.data.ui-text[site.locale].pagination_next | default: "Next" }}</a></li>
+    {% else %}
+      <li><a href="#" class="disabled"><span aria-hidden="true">{{ site.data.ui-text[site.locale].pagination_next | default: "Next" }}</span></a></li>
+    {% endif %}
+  </ul>
+</nav>
+{% endif %}

_includes/post_pagination.html

@@ -0,0 +1,14 @@
+{% if page.previous or page.next %}
+  <nav class="pagination">
+    {% if page.previous %}
+      <a href="{{ page.previous.url | relative_url }}" class="pagination--pager" title="{{ page.previous.title | markdownify | strip_html }}">{{ site.data.ui-text[site.locale].pagination_previous | default: "Previous" }}</a>
+    {% else %}
+      <a href="#" class="pagination--pager disabled">{{ site.data.ui-text[site.locale].pagination_previous | default: "Previous" }}</a>
+    {% endif %}
+    {% if page.next %}
+      <a href="{{ page.next.url | relative_url }}" class="pagination--pager" title="{{ page.next.title | markdownify | strip_html }}">{{ site.data.ui-text[site.locale].pagination_next | default: "Next" }}</a>
+    {% else %}
+      <a href="#" class="pagination--pager disabled">{{ site.data.ui-text[site.locale].pagination_next | default: "Next" }}</a>
+    {% endif %}
+  </nav>
+{% endif %}

_includes/posts-category.html

@@ -0,0 +1,5 @@
+{%- for post in site.categories[include.taxonomy] -%}
+  {%- unless post.hidden -%}
+    {% include archive-single.html %}
+  {%- endunless -%}
+{%- endfor -%}

_includes/posts-tag.html

@@ -0,0 +1,5 @@
+{%- for post in site.tags[include.taxonomy] -%}
+  {%- unless post.hidden -%}
+    {% include archive-single.html %}
+  {%- endunless -%}
+{%- endfor -%}

_includes/read-time.html

@@ -0,0 +1,15 @@
+{% assign words_per_minute = site.words_per_minute | default: 200 %}
+
+{% if post.read_time %}
+  {% assign words = post.content | strip_html | number_of_words %}
+{% elsif page.read_time %}
+  {% assign words = page.content | strip_html | number_of_words %}
+{% endif %}
+
+{% if words < words_per_minute %}
+  {{ site.data.ui-text[site.locale].less_than | default: "less than" }} 1 {{ site.data.ui-text[site.locale].minute_read | default: "minute read" }}
+{% elsif words == words_per_minute %}
+  1 {{ site.data.ui-text[site.locale].minute_read | default: "minute read" }}
+{% else %}
+  {{ words | divided_by:words_per_minute }} {{ site.data.ui-text[site.locale].minute_read | default: "minute read" }}
+{% endif %}

_includes/scripts.html

@@ -0,0 +1,29 @@
+{% if site.footer_scripts %}
+  {% for script in site.footer_scripts %}
+    <script src="{{ script | relative_url }}"></script>
+  {% endfor %}
+{% else %}
+  <script src="{{ '/assets/js/main.min.js' | relative_url }}"></script>
+  <script src="https://kit.fontawesome.com/4eee35f757.js"></script>
+{% endif %}
+
+{% if site.search == true or page.layout == "search" %}
+  {%- assign search_provider = site.search_provider | default: "lunr" -%}
+  {%- case search_provider -%}
+    {%- when "lunr" -%}
+      {% include_cached search/lunr-search-scripts.html %}
+    {%- when "google" -%}
+      {% include_cached search/google-search-scripts.html %}
+    {%- when "algolia" -%}
+      {% include_cached search/algolia-search-scripts.html %}
+  {%- endcase -%}
+{% endif %}
+
+{% include analytics.html %}
+{% include /comments-providers/scripts.html %}
+
+{% if site.after_footer_scripts %}
+  {% for script in site.after_footer_scripts %}
+    <script src="{{ script | relative_url }}"></script>
+  {% endfor %}
+{% endif %}

_includes/search/algolia-search-scripts.html

@@ -0,0 +1,62 @@
+<!-- Including InstantSearch.js library and styling -->
+<script src="https://cdn.jsdelivr.net/npm/instantsearch.js@2.3.3/dist/instantsearch.min.js"></script>
+<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/instantsearch.js@2.3.3/dist/instantsearch.min.css">
+<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/instantsearch.js@2.3.3/dist/instantsearch-theme-algolia.min.css">
+
+<script>
+// Instanciating InstantSearch.js with Algolia credentials
+const search = instantsearch({
+  appId: '{{ site.algolia.application_id }}',
+  apiKey: '{{ site.algolia.search_only_api_key }}',
+  indexName: '{{ site.algolia.index_name }}',
+  searchParameters: {
+    restrictSearchableAttributes: [
+      'title',
+      'content'
+    ]
+  }
+});
+
+const hitTemplate = function(hit) {
+  const url = hit.url;
+  const hightlight = hit._highlightResult;
+  const title = hightlight.title && hightlight.title.value  || "";
+  const content = hightlight.html && hightlight.html.value  || "";
+
+  return `
+    <div class="list__item">
+      <article class="archive__item" itemscope itemtype="https://schema.org/CreativeWork">
+        <h2 class="archive__item-title" itemprop="headline"><a href="{{ site.baseurl }}${url}">${title}</a></h2>
+        <div class="archive__item-excerpt" itemprop="description">${content}</div>
+      </article>
+    </div>
+  `;
+}
+
+// Adding searchbar and results widgets
+search.addWidget(
+  instantsearch.widgets.searchBox({
+    container: '.search-searchbar',
+    {% unless site.algolia.powered_by == false %}poweredBy: true,{% endunless %}
+    placeholder: '{{ site.data.ui-text[site.locale].search_placeholder_text | default: "Enter your search term..." }}'
+  })
+);
+search.addWidget(
+  instantsearch.widgets.hits({
+    container: '.search-hits',
+    templates: {
+      item: hitTemplate,
+      empty: '{{ site.data.ui-text[site.locale].search_algolia_no_results | default: "No results" }}',
+    }
+  })
+);
+
+// Starting the search only when toggle is clicked
+$(document).ready(function () {
+  $(".search__toggle").on("click", function() {
+    if(!search.started) {
+      search.start();
+    }
+  });
+});
+</script>

_includes/search/google-search-scripts.html

@@ -0,0 +1,30 @@
+<script>
+  (function () {
+    var cx = '{{ site.google.search_engine_id }}';
+    var gcse = document.createElement('script');
+    gcse.type = 'text/javascript';
+    gcse.async = true;
+    gcse.src = 'https://cse.google.com/cse.js?cx=' + cx;
+    var s = document.getElementsByTagName('script')[0];
+    s.parentNode.insertBefore(gcse, s);
+  })();
+
+  function googleCustomSearchExecute() {
+    var input = document.getElementById('cse-search-input-box-id');
+    var element = google.search.cse.element.getElement('searchresults-only0');
+    if (input.value == '') {
+      element.clearAllResults();
+    } else {
+      element.execute(input.value);
+    }
+    return false;
+  }
+
+  {% if site.google.instant_search %}
+    $(document).ready(function () {
+      $('input#cse-search-input-box-id').on('keyup', function () {
+        googleCustomSearchExecute();
+      });
+    });
+  {% endif %}
+</script>

_includes/search/lunr-search-scripts.html

@@ -0,0 +1,10 @@
+{% assign lang = site.locale | slice: 0,2 | default: "en" %}
+{% case lang %}
+{% when "gr" %}
+  {% assign lang = "gr" %}
+{% else %}
+  {% assign lang = "en" %}
+{% endcase %}
+<script src="{{ '/assets/js/lunr/lunr.min.js' | relative_url }}"></script>
+<script src="{{ '/assets/js/lunr/lunr-store.js' | relative_url }}"></script>
+<script src="{{ '/assets/js/lunr/lunr-' | append: lang | append: '.js' | relative_url }}"></script>

_includes/search/search_form.html

@@ -0,0 +1,26 @@
+<div class="search-content__inner-wrap">
+  {%- assign search_provider = site.search_provider | default: "lunr" -%}
+  {%- case search_provider -%}
+  {%- when "lunr" -%}
+  <form class="search-content__form" onkeydown="return event.key != 'Enter';" role="search">
+    <label class="sr-only" for="search">
+      {{ site.data.ui-text[site.locale].search_label_text | default: 'Enter your search term...' }}
+    </label>
+    <input type="search" id="search" class="search-input" tabindex="-1" placeholder="{{ site.data.ui-text[site.locale].search_placeholder_text | default: 'Enter your search term...' }}" />
+  </form>
+  <div id="results" class="results"></div>
+  {%- when "google" -%}
+  <form onsubmit="return googleCustomSearchExecute();" id="cse-search-box-form-id" role="search">
+    <label class="sr-only" for="cse-search-input-box-id">
+      {{ site.data.ui-text[site.locale].search_label_text | default: 'Enter your search term...' }}
+    </label>
+    <input type="search" id="cse-search-input-box-id" class="search-input" tabindex="-1" placeholder="{{ site.data.ui-text[site.locale].search_placeholder_text | default: 'Enter your search term...' }}" />
+  </form>
+  <div id="results" class="results">
+    <gcse:searchresults-only></gcse:searchresults-only>
+  </div>
+  {%- when "algolia" -%}
+  <div class="search-searchbar"></div>
+  <div class="search-hits"></div>
+  {%- endcase -%}
+</div>

_includes/seo.html

@@ -1,114 +1,158 @@
-<!-- Begin Jekyll SEO tag v{{ seo_tag.version }} -->
+<!-- begin _includes/seo.html -->
+{%- if site.url -%}
+  {%- assign seo_url = site.url | append: site.baseurl -%}
+{%- endif -%}
+{%- assign seo_url = seo_url | default: site.github.url -%}
 
+{% assign title_separator = site.title_separator | default: '-' | replace: '|', '&#124;' %}
 
-{% if seo_tag.title? %}
-  <title>{{ seo_tag.title }}</title>
+{%- if page.title -%}
+  {%- assign seo_title = page.title | append: " " | append: title_separator | append: " " | append: site.title -%}
+{%- endif -%}
+
+{%- if seo_title -%}
+  {%- assign seo_title = seo_title | markdownify | strip_html | strip_newlines | escape_once -%}
+{%- endif -%}
+
+{% if page.canonical_url %}
+  {%- assign canonical_url = page.canonical_url %}
+{% else %}
+  {%- assign canonical_url = page.url | replace: "index.html", "" | absolute_url %}
 {% endif %}
 
-<meta name="generator" content="Jekyll v{{ jekyll.version }}" />
+{%- assign seo_description = page.description | default: page.excerpt | default: site.description -%}
+{%- if seo_description -%}
+  {%- assign seo_description = seo_description | markdownify | strip_html | newline_to_br | strip_newlines | replace: '<br />', ' ' | escape_once | strip -%}
+{%- endif -%}
 
-{% if seo_tag.page_title %}
-  <meta property="og:title" content="{{ seo_tag.page_title }}" />
-{% endif %}
+{%- assign author = page.author | default: page.authors[0] | default: site.author -%}
+{%- assign author = site.data.authors[author] | default: author -%}
 
-{% if seo_tag.author.name %}
-  <meta name="author" content="{{ seo_tag.author.name }}" />
-{% endif %}
+{%- if author.twitter -%}
+  {%- assign author_twitter = author.twitter | replace: "@", "" -%}
+{%- endif -%}
 
-<meta property="og:locale" content="{{ seo_tag.page_lang | replace:'-','_' }}" />
+{%- assign page_large_image = page.header.og_image | default: page.header.overlay_image | default: page.header.image | absolute_url -%}
+{%- assign page_large_image = page_large_image | escape -%}
 
-{% if seo_tag.description %}
-  <meta name="description" content="{{ seo_tag.description }}" />
-  <meta property="og:description" content="{{ seo_tag.description }}" />
-{% endif %}
+{%- assign page_teaser_image = page.header.teaser | default: site.og_image | absolute_url -%}
+{%- assign page_teaser_image = page_teaser_image | escape -%}
 
-{% if site.url %}
-  <link rel="canonical" href="{{ seo_tag.canonical_url }}" />
-  <meta property="og:url" content="{{ seo_tag.canonical_url }}" />
-{% endif %}
+{%- assign site_og_image = site.og_image | absolute_url -%}
+{%- assign site_og_image = site_og_image | escape -%}
 
-{% if seo_tag.site_title %}
-  <meta property="og:site_name" content="{{ seo_tag.site_title }}" />
-{% endif %}
+{%- if page.date -%}
+  {%- assign og_type = "article" -%}
+{%- else -%}
+  {%- assign og_type = "website" -%}
+{%- endif -%}
 
-{% if seo_tag.image %}
-  <meta property="og:image" content="{{ seo_tag.image.path }}" />
-  {% if seo_tag.image.height %}
-    <meta property="og:image:height" content="{{ seo_tag.image.height }}" />
+<title>{{ seo_title | default: site.title }}{% if paginator %}{% unless paginator.page == 1 %} {{ title_separator }} {{ site.data.ui-text[site.locale].page | default: "Page" }} {{ paginator.page }}{% endunless %}{% endif %}</title>
+<meta name="description" content="{{ seo_description }}">
+
+{% if author.name %}
+  <meta name="author" content="{{ author.name | default: author }}">
+  {% if og_type == "article" %}
+  <meta property="article:author" content="{{ author.name | default: author }}">
   {% endif %}
-  {% if seo_tag.image.width %}
-    <meta property="og:image:width" content="{{ seo_tag.image.width }}" />
+{% endif %}
+
+<meta property="og:type" content="{{ og_type }}">
+<meta property="og:locale" content="{{ site.locale | replace: "-", "_" | default: "en_US" }}">
+<meta property="og:site_name" content="{{ site.title }}">
+<meta property="og:title" content="{{ page.title | default: site.title | markdownify | strip_html | strip_newlines | escape_once }}">
+<meta property="og:url" content="{{ canonical_url }}">
+
+{% if seo_description %}
+  <meta property="og:description" content="{{ seo_description }}">
+{% endif %}
+
+{% if page_large_image %}
+  <meta property="og:image" content="{{ page_large_image }}">
+{% elsif page_teaser_image %}
+  <meta property="og:image" content="{{ page_teaser_image }}">
+{% endif %}
+
+{% if site.twitter.username %}
+  <meta name="twitter:site" content="@{{ site.twitter.username | replace: "@", "" }}">
+  <meta name="twitter:title" content="{{ page.title | default: site.title | markdownify | strip_html | strip_newlines | escape_once }}">
+  <meta name="twitter:description" content="{{ seo_description }}">
+  <meta name="twitter:url" content="{{ canonical_url }}">
+
+  {% if page_large_image %}
+    <meta name="twitter:card" content="summary_large_image">
+    <meta name="twitter:image" content="{{ page_large_image }}">
+  {% else %}
+    <meta name="twitter:card" content="summary">
+    {% if page_teaser_image %}
+      <meta name="twitter:image" content="{{ page_teaser_image }}">
+    {% endif %}
+  {% endif %}
+
+  {% if author_twitter %}
+    <meta name="twitter:creator" content="@{{ author_twitter }}">
   {% endif %}
 {% endif %}
 
 {% if page.date %}
-  <meta property="og:type" content="article" />
-  <meta property="article:published_time" content="{{ page.date | date_to_xmlschema }}" />
+  <meta property="article:published_time" content="{{ page.date | date_to_xmlschema }}">
 {% endif %}
 
-{% if paginator.previous_page %}
-  <link rel="prev" href="{{ paginator.previous_page_path | absolute_url }}" />
-{% endif %}
-{% if paginator.next_page %}
-  <link rel="next" href="{{ paginator.next_page_path | absolute_url }}" />
-{% endif %}
-
-{% if site.twitter %}
-  {% if seo_tag.image %}
-    <meta name="twitter:card" content="{{ page.twitter.card | default: site.twitter.card | default: "summary_large_image" }}" />
-    <meta property="twitter:image" content="{{ seo_tag.image.path }}" />
-  {% else %}
-    <meta name="twitter:card" content="summary" />
-  {% endif %}
-
-  <meta property="twitter:title" content="{{ seo_tag.page_title }}" />
-  <meta name="twitter:site" content="@{{ site.twitter.username | replace:"@","" }}" />
-
-  {% if seo_tag.author.twitter %}
-    <meta name="twitter:creator" content="@{{ seo_tag.author.twitter }}" />
-  {% endif %}
+{% if og_type == "article" and page.last_modified_at %}
+  <meta property="article:modified_time" content="{{ page.last_modified_at | date_to_xmlschema }}">
 {% endif %}
 
 {% if site.facebook %}
-  {% if site.facebook.admins %}
-    <meta property="fb:admins" content="{{ site.facebook.admins }}" />
-  {% endif %}
-
   {% if site.facebook.publisher %}
-    <meta property="article:publisher" content="{{ site.facebook.publisher }}" />
+    <meta property="article:publisher" content="{{ site.facebook.publisher }}">
   {% endif %}
 
   {% if site.facebook.app_id %}
-    <meta property="fb:app_id" content="{{ site.facebook.app_id }}" />
+    <meta property="fb:app_id" content="{{ site.facebook.app_id }}">
   {% endif %}
 {% endif %}
 
-{% if site.webmaster_verifications %}
-  {% if site.webmaster_verifications.google %}
-    <meta name="google-site-verification" content="{{ site.webmaster_verifications.google }}" />
-  {% endif %}
+<link rel="canonical" href="{{ canonical_url }}">
 
-  {% if site.webmaster_verifications.bing %}
-    <meta name="msvalidate.01" content="{{ site.webmaster_verifications.bing }}" />
-  {% endif %}
-
-  {% if site.webmaster_verifications.alexa %}
-    <meta name="alexaVerifyID" content="{{ site.webmaster_verifications.alexa }}" />
-  {% endif %}
-
-  {% if site.webmaster_verifications.yandex %}
-    <meta name="yandex-verification" content="{{ site.webmaster_verifications.yandex }}" />
-  {% endif %}
-
-  {% if site.webmaster_verifications.baidu %}
-    <meta name="baidu-site-verification" content="{{ site.webmaster_verifications.baidu }}" />
-  {% endif %}
-{% elsif site.google_site_verification %}
-  <meta name="google-site-verification" content="{{ site.google_site_verification }}" />
+{% if paginator.previous_page %}
+  <link rel="prev" href="{{ paginator.previous_page_path | absolute_url }}">
+{% endif %}
+{% if paginator.next_page %}
+  <link rel="next" href="{{ paginator.next_page_path | absolute_url }}">
 {% endif %}
 
 <script type="application/ld+json">
-  {{ seo_tag.json_ld | jsonify }}
+  {
+    "@context": "https://schema.org",
+    {% if site.social.type == "Organization" %}
+      "@type": "Organization",
+      "url": {{ '/' | absolute_url | jsonify }}{% if site.og_image %},
+      "logo": {{ site_og_image | jsonify }}{% endif %}
+    {% else %}
+      "@type": "Person",
+      "name": {{ site.social.name | default: site.name | jsonify }},
+      "url": {{ '/' | absolute_url |jsonify }}{% if site.social.links %},
+      "sameAs": {{ site.social.links | jsonify }}{% endif %}
+    {% endif %}
+  }
 </script>
 
-<!-- End Jekyll SEO tag -->
+{% if site.google_site_verification %}
+  <meta name="google-site-verification" content="{{ site.google_site_verification }}" />
+{% endif %}
+{% if site.bing_site_verification %}
+  <meta name="msvalidate.01" content="{{ site.bing_site_verification }}">
+{% endif %}
+{% if site.alexa_site_verification %}
+  <meta name="alexaVerifyID" content="{{ site.alexa_site_verification }}">
+{% endif %}
+{% if site.yandex_site_verification %}
+  <meta name="yandex-verification" content="{{ site.yandex_site_verification }}">
+{% endif %}
+{% if site.naver_site_verification %}
+  <meta name="naver-site-verification" content="{{ site.naver_site_verification }}">
+{% endif %}
+{% if site.baidu_site_verification %}
+  <meta name="baidu-site-verification" content="{{ site.baidu_site_verification }}">
+{% endif %}
+<!-- end _includes/seo.html -->

_includes/share-bar.html

@@ -1,55 +0,0 @@
-<div id="share-bar">
-
-    <h4>Share this:</h4>
-
-    <div class="share-buttons">
-        <a  href="https://www.facebook.com/sharer/sharer.php?u={{ site.url }}{{ site.baseurl }}{{ page.url }}"
-            onclick="window.open(this.href, 'pop-up', 'left=20,top=20,width=500,height=500,toolbar=1,resizable=0'); return false;"
-            title="Share on Facebook" >
-            <i class="fa fa-facebook-official share-button"> facebook</i>
-        </a>
-
-        <a  href="https://twitter.com/intent/tweet?text={{ page.title }}&url={{ site.url }}{{ site.baseurl }}{{ page.url }}"
-            onclick="window.open(this.href, 'pop-up', 'left=20,top=20,width=500,height=500,toolbar=1,resizable=0'); return false;"
-            title="Share on Twitter" >
-            <i class="fa fa-twitter share-button"> twitter</i>
-        </a>
-
-        <a  href="https://plus.google.com/share?url={{ site.url }}{{ site.baseurl }}{{ page.url }}"
-            onclick="window.open(this.href, 'pop-up', 'left=20,top=20,width=500,height=500,toolbar=1,resizable=0'); return false;"
-            title="Share on Google+" >
-            <i class="fa fa-google-plus share-button"> google</i>
-        </a>
-
-        <a  href="https://www.pinterest.com/pin/create/button/?url={{ site.url }}{{ site.baseurl }}{{ page.url }}"
-            onclick="window.open(this.href, 'pop-up', 'left=20,top=20,width=900,height=500,toolbar=1,resizable=0'); return false;"
-            title="Share on Pinterest" >
-            <i class="fa fa-pinterest-p share-button"> pinterest</i>
-        </a>
-
-        <a  href="https://www.tumblr.com/share/link?url={{ site.url }}{{ site.baseurl }}{{ page.url }}"
-            onclick="window.open(this.href, 'pop-up', 'left=20,top=20,width=900,height=500,toolbar=1,resizable=0'); return false;"
-            title="Share on Tumblr" >
-            <i class="fa fa-tumblr share-button"> tumblr</i>
-        </a>
-
-        <a  href="http://www.reddit.com/submit?url={{ site.url }}{{ site.baseurl }}{{ page.url }}"
-            onclick="window.open(this.href, 'pop-up', 'left=20,top=20,width=900,height=500,toolbar=1,resizable=0'); return false;"
-            title="Share on Reddit" >
-            <i class="fa fa-reddit-alien share-button"> reddit</i>
-        </a>
-
-        <a  href="https://www.linkedin.com/shareArticle?mini=true&url={{ site.url }}{{ site.baseurl }}{{ page.url }}&title={{ page.title }}&summary={{ page.description }}&source={{ site.title }}"
-            onclick="window.open(this.href, 'pop-up', 'left=20,top=20,width=500,height=500,toolbar=1,resizable=0'); return false;"
-            title="Share on LinkedIn" >
-            <i class="fa fa-linkedin share-button"> linkedin</i>
-        </a>
-
-        <a  href="mailto:?subject={{ page.title }}&amp;body=Check out this site {{ site.url }}{{ site.baseurl }}{{ page.url }}"
-            title="Share via Email" >
-            <i class="fa fa-envelope share-button"> email</i>
-        </a>
-    </div>
-
-</div>
-

_includes/sidebar.html

@@ -0,0 +1,19 @@
+{% if page.author_profile or layout.author_profile or page.sidebar %}
+  <div class="sidebar sticky">
+  {% if page.author_profile or layout.author_profile %}{% include author-profile.html %}{% endif %}
+  {% if page.sidebar %}
+    {% for s in page.sidebar %}
+      {% if s.image %}
+        <img src="{{ s.image | relative_url }}"
+             alt="{% if s.image_alt %}{{ s.image_alt }}{% endif %}">
+      {% endif %}
+      {% if s.title %}<h3>{{ s.title }}</h3>{% endif %}
+      {% if s.text %}{{ s.text | markdownify }}{% endif %}
+      {% if s.nav %}{% include nav_list nav=s.nav %}{% endif %}
+    {% endfor %}
+    {% if page.sidebar.nav %}
+      {% include nav_list nav=page.sidebar.nav %}
+    {% endif %}
+  {% endif %}
+  </div>
+{% endif %}

_includes/skip-links.html

@@ -0,0 +1,7 @@
+<nav class="skip-links">
+  <ul>
+    <li><a href="#site-nav" class="screen-reader-shortcut">{{ site.data.ui-text[site.locale].skip_primary_nav | default: 'Skip to primary navigation' }}</a></li>
+    <li><a href="#main" class="screen-reader-shortcut">{{ site.data.ui-text[site.locale].skip_content | default: 'Skip to content' }}</a></li>
+    <li><a href="#footer" class="screen-reader-shortcut">{{ site.data.ui-text[site.locale].skip_footer | default: 'Skip to footer' }}</a></li>
+  </ul>
+</nav>

_includes/social-share.html

@@ -0,0 +1,10 @@
+<section class="page__share">
+  {% if site.data.ui-text[site.locale].share_on_label %}
+    <h3 class="page__share-title">{{ site.data.ui-text[site.locale].share_on_label | default: "Share on" }}</h3>
+  {% endif %}
+
+  <a href="https://twitter.com/intent/tweet?{% if site.twitter.username %}via={{ site.twitter.username | url_encode }}&{% endif %}text={{ page.title | url_encode }}%20{{ page.url | absolute_url | url_encode }}" class="btn btn--twitter" onclick="window.open(this.href, 'window', 'left=20,top=20,width=500,height=500,toolbar=1,resizable=0'); return false;" title="Share on Twitter"><i class="fab fa-fw fa-twitter" aria-hidden="true"></i><span> Twitter</span></a>
+  <a href="https://www.facebook.com/sharer/sharer.php?u={{ page.url | absolute_url | url_encode }}" class="btn btn--facebook" onclick="window.open(this.href, 'window', 'left=20,top=20,width=500,height=500,toolbar=1,resizable=0'); return false;" title="Share on Facebook"><i class="fab fa-fw fa-facebook" aria-hidden="true"></i><span> Facebook</span></a>
+  <a href="https://www.linkedin.com/shareArticle?mini=true&url={{ page.url | absolute_url | url_encode }}" class="btn btn--linkedin" onclick="window.open(this.href, 'window', 'left=20,top=20,width=500,height=500,toolbar=1,resizable=0'); return false;" title="Share on LinkedIn"><i class="fab fa-fw fa-linkedin" aria-hidden="true"></i><span> LinkedIn</span></a>
+  <a href="https://www.reddit.com/submit?url={{ page.url | absolute_url | url_encode }}&title={{ page.title | url_encode }}" class="btn btn--reddit" title="Share on Reddit"><i class="fab fa-fw fa-reddit" aria-hidden="true"></i><span> Reddit</span></a>
+  </section>

_includes/tag-list.html

@@ -0,0 +1,19 @@
+{% case site.tag_archive.type %}
+  {% when "liquid" %}
+    {% assign path_type = "#" %}
+  {% when "jekyll-archives" %}
+    {% assign path_type = nil %}
+{% endcase %}
+
+{% if site.tag_archive.path %}
+  {% assign tags_sorted = page.tags | sort_natural %}
+
+  <p class="page__taxonomy">
+    <strong><i class="fas fa-fw fa-tags" aria-hidden="true"></i> {{ site.data.ui-text[site.locale].tags_label | default: "Tags:" }} </strong>
+    <span itemprop="keywords">
+    {% for tag_word in tags_sorted %}
+      <a href="{{ tag_word | slugify | prepend: path_type | prepend: site.tag_archive.path | relative_url }}" class="page__taxonomy-item p-category" rel="tag">{{ tag_word }}</a>{% unless forloop.last %}<span class="sep">, </span>{% endunless %}
+    {% endfor %}
+    </span>
+  </p>
+{% endif %}

_includes/toc

@@ -0,0 +1,7 @@
+<aside class="sidebar__right">
+<nav class="toc" markdown="1">
+<header><h4 class="nav__title"><i class="fas fa-{{ include.icon | default: 'file-alt' }}"></i> {{ include.title | default: site.data.ui-text[site.locale].toc_label }}</h4></header>
+*  Auto generated table of contents
+{:toc .toc__menu}
+</nav>
+</aside>

_includes/toc.html

@@ -0,0 +1,182 @@
+{% capture tocWorkspace %}
+    {% comment %}
+        Copyright (c) 2017 Vladimir "allejo" Jimenez
+
+        Permission is hereby granted, free of charge, to any person
+        obtaining a copy of this software and associated documentation
+        files (the "Software"), to deal in the Software without
+        restriction, including without limitation the rights to use,
+        copy, modify, merge, publish, distribute, sublicense, and/or sell
+        copies of the Software, and to permit persons to whom the
+        Software is furnished to do so, subject to the following
+        conditions:
+
+        The above copyright notice and this permission notice shall be
+        included in all copies or substantial portions of the Software.
+
+        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+        EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+        OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+        NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
+        HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+        WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+        FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+        OTHER DEALINGS IN THE SOFTWARE.
+    {% endcomment %}
+    {% comment %}
+        Version 1.1.0
+          https://github.com/allejo/jekyll-toc
+
+        "...like all things liquid - where there's a will, and ~36 hours to spare, there's usually a/some way" ~jaybe
+
+        Usage:
+            {% include toc.html html=content sanitize=true class="inline_toc" id="my_toc" h_min=2 h_max=3 %}
+
+        Parameters:
+            * html         (string) - the HTML of compiled markdown generated by kramdown in Jekyll
+
+        Optional Parameters:
+            * sanitize      (bool)   : false  - when set to true, the headers will be stripped of any HTML in the TOC
+            * class         (string) :   ''   - a CSS class assigned to the TOC
+            * id            (string) :   ''   - an ID to assigned to the TOC
+            * h_min         (int)    :   1    - the minimum TOC header level to use; any header lower than this value will be ignored
+            * h_max         (int)    :   6    - the maximum TOC header level to use; any header greater than this value will be ignored
+            * ordered       (bool)   : false  - when set to true, an ordered list will be outputted instead of an unordered list
+            * item_class    (string) :   ''   - add custom class(es) for each list item; has support for '%level%' placeholder, which is the current heading level
+            * submenu_class (string) :   ''   - add custom class(es) for each child group of headings; has support for '%level%' placeholder which is the current "submenu" heading level
+            * base_url      (string) :   ''   - add a base url to the TOC links for when your TOC is on another page than the actual content
+            * anchor_class  (string) :   ''   - add custom class(es) for each anchor element
+            * skip_no_ids   (bool)   : false  - skip headers that do not have an `id` attribute
+
+        Output:
+            An ordered or unordered list representing the table of contents of a markdown block. This snippet will only
+            generate the table of contents and will NOT output the markdown given to it
+    {% endcomment %}
+
+    {% capture newline %}
+    {% endcapture %}
+    {% assign newline = newline | rstrip %} <!-- Remove the extra spacing but preserve the newline -->
+
+    {% capture deprecation_warnings %}{% endcapture %}
+
+    {% if include.baseurl %}
+        {% capture deprecation_warnings %}{{ deprecation_warnings }}<!-- jekyll-toc :: "baseurl" has been deprecated, use "base_url" instead -->{{ newline }}{% endcapture %}
+    {% endif %}
+
+    {% if include.skipNoIDs %}
+        {% capture deprecation_warnings %}{{ deprecation_warnings }}<!-- jekyll-toc :: "skipNoIDs" has been deprecated, use "skip_no_ids" instead -->{{ newline }}{% endcapture %}
+    {% endif %}
+
+    {% capture jekyll_toc %}{% endcapture %}
+    {% assign orderedList = include.ordered | default: false %}
+    {% assign baseURL = include.base_url | default: include.baseurl | default: '' %}
+    {% assign skipNoIDs = include.skip_no_ids | default: include.skipNoIDs | default: false %}
+    {% assign minHeader = include.h_min | default: 1 %}
+    {% assign maxHeader = include.h_max | default: 6 %}
+    {% assign nodes = include.html | strip | split: '<h' %}
+
+    {% assign firstHeader = true %}
+    {% assign currLevel = 0 %}
+    {% assign lastLevel = 0 %}
+
+    {% capture listModifier %}{% if orderedList %}ol{% else %}ul{% endif %}{% endcapture %}
+
+    {% for node in nodes %}
+        {% if node == "" %}
+            {% continue %}
+        {% endif %}
+
+        {% assign currLevel = node | replace: '"', '' | slice: 0, 1 | times: 1 %}
+
+        {% if currLevel < minHeader or currLevel > maxHeader %}
+            {% continue %}
+        {% endif %}
+
+        {% assign _workspace = node | split: '</h' %}
+
+        {% assign _idWorkspace = _workspace[0] | split: 'id="' %}
+        {% assign _idWorkspace = _idWorkspace[1] | split: '"' %}
+        {% assign htmlID = _idWorkspace[0] %}
+
+        {% assign _classWorkspace = _workspace[0] | split: 'class="' %}
+        {% assign _classWorkspace = _classWorkspace[1] | split: '"' %}
+        {% assign htmlClass = _classWorkspace[0] %}
+
+        {% if htmlClass contains "no_toc" %}
+            {% continue %}
+        {% endif %}
+
+        {% if firstHeader %}
+            {% assign minHeader = currLevel %}
+        {% endif %}
+
+        {% capture _hAttrToStrip %}{{ _workspace[0] | split: '>' | first }}>{% endcapture %}
+        {% assign header = _workspace[0] | replace: _hAttrToStrip, '' %}
+
+        {% if include.item_class and include.item_class != blank %}
+            {% capture listItemClass %} class="{{ include.item_class | replace: '%level%', currLevel | split: '.' | join: ' ' }}"{% endcapture %}
+        {% endif %}
+
+        {% if include.submenu_class and include.submenu_class != blank %}
+            {% assign subMenuLevel = currLevel | minus: 1 %}
+            {% capture subMenuClass %} class="{{ include.submenu_class | replace: '%level%', subMenuLevel | split: '.' | join: ' ' }}"{% endcapture %}
+        {% endif %}
+
+        {% capture anchorBody %}{% if include.sanitize %}{{ header | strip_html }}{% else %}{{ header }}{% endif %}{% endcapture %}
+
+        {% if htmlID %}
+            {% capture anchorAttributes %} href="{% if baseURL %}{{ baseURL }}{% endif %}#{{ htmlID }}"{% endcapture %}
+
+            {% if include.anchor_class %}
+                {% capture anchorAttributes %}{{ anchorAttributes }} class="{{ include.anchor_class | split: '.' | join: ' ' }}"{% endcapture %}
+            {% endif %}
+
+            {% capture listItem %}<a{{ anchorAttributes }}>{{ anchorBody }}</a>{% endcapture %}
+        {% elsif skipNoIDs == true %}
+            {% continue %}
+        {% else %}
+            {% capture listItem %}{{ anchorBody }}{% endcapture %}
+        {% endif %}
+
+        {% if currLevel > lastLevel %}
+            {% capture jekyll_toc %}{{ jekyll_toc }}<{{ listModifier }}{{ subMenuClass }}>{% endcapture %}
+        {% elsif currLevel < lastLevel %}
+            {% assign repeatCount = lastLevel | minus: currLevel %}
+
+            {% for i in (1..repeatCount) %}
+                {% capture jekyll_toc %}{{ jekyll_toc }}</li></{{ listModifier }}>{% endcapture %}
+            {% endfor %}
+
+            {% capture jekyll_toc %}{{ jekyll_toc }}</li>{% endcapture %}
+        {% else %}
+            {% capture jekyll_toc %}{{ jekyll_toc }}</li>{% endcapture %}
+        {% endif %}
+
+        {% capture jekyll_toc %}{{ jekyll_toc }}<li{{ listItemClass }}>{{ listItem }}{% endcapture %}
+
+        {% assign lastLevel = currLevel %}
+        {% assign firstHeader = false %}
+    {% endfor %}
+
+    {% assign repeatCount = minHeader | minus: 1 %}
+    {% assign repeatCount = lastLevel | minus: repeatCount %}
+    {% for i in (1..repeatCount) %}
+        {% capture jekyll_toc %}{{ jekyll_toc }}</li></{{ listModifier }}>{% endcapture %}
+    {% endfor %}
+
+    {% if jekyll_toc != '' %}
+        {% assign rootAttributes = '' %}
+        {% if include.class and include.class != blank %}
+            {% capture rootAttributes %} class="{{ include.class | split: '.' | join: ' ' }}"{% endcapture %}
+        {% endif %}
+
+        {% if include.id and include.id != blank %}
+            {% capture rootAttributes %}{{ rootAttributes }} id="{{ include.id }}"{% endcapture %}
+        {% endif %}
+
+        {% if rootAttributes %}
+            {% assign nodes = jekyll_toc | split: '>' %}
+            {% capture jekyll_toc %}<{{ listModifier }}{{ rootAttributes }}>{{ nodes | shift | join: '>' }}>{% endcapture %}
+        {% endif %}
+    {% endif %}
+{% endcapture %}{% assign tocWorkspace = '' %}{{ deprecation_warnings }}{{ jekyll_toc }}

_includes/video

@@ -0,0 +1,24 @@
+{% capture video_id %}{{ include.id }}{% endcapture %}
+{% capture video_provider %}{{ include.provider }}{% endcapture %}
+{% capture video_danmaku %}{{ include.danmaku | default: 0 }}{% endcapture %}
+
+{% capture video_src %}
+  {% case video_provider %}
+  {% when "vimeo" %}
+    https://player.vimeo.com/video/{{ video_id }}?dnt=true
+  {% when "youtube" %}
+    https://www.youtube-nocookie.com/embed/{{ video_id }}
+  {% when "google-drive" %}
+    https://drive.google.com/file/d/{{ video_id }}/preview
+  {% when "bilibili" %}
+    https://player.bilibili.com/player.html?bvid={{ video_id }}&page=1&as_wide=1&high_quality=1&danmaku={{ video_danmaku }}
+  {% endcase %}
+{% endcapture %}
+{% assign video_src = video_src | strip %}
+
+<!-- Courtesy of embedresponsively.com -->
+{% unless video_src == "" %}
+  <div class="responsive-video-container">
+    <iframe src="{{ video_src }}" frameborder="0" webkitAllowFullScreen mozallowfullscreen allowfullscreen></iframe>
+  </div>
+{% endunless %}

_layouts/archive-taxonomy.html

@@ -0,0 +1,29 @@
+---
+layout: default
+author_profile: false
+---
+
+{% if page.header.overlay_color or page.header.overlay_image or page.header.image %}
+  {% include page__hero.html %}
+{% elsif page.header.video.id and page.header.video.provider %}
+  {% include page__hero_video.html %}
+{% endif %}
+
+{% if page.url != "/" and site.breadcrumbs %}
+  {% unless paginator %}
+    {% include breadcrumbs.html %}
+  {% endunless %}
+{% endif %}
+
+<div id="main" role="main">
+  {% include sidebar.html %}
+
+  <div class="archive">
+    {% unless page.header.overlay_color or page.header.overlay_image %}
+      <h1 id="page-title" class="page__title">{{ page.title }}</h1>
+    {% endunless %}
+    {% for post in page.posts %}
+      {% include archive-single.html %}
+    {% endfor %}
+  </div>
+</div>