mirror of
https://github.com/Decentralized-ID/decentralized-id.github.io.git
synced 2024-10-01 01:05:54 -04:00
consolidate \ clean up link structure
This commit is contained in:
⧉ infominer
parent
71612c9bc7
commit
956cf51860
@ -8,8 +8,9 @@ excerpt: >
|
||||
The Semantic Web isn't just about putting data on the web. It is about making links, so that a person or machine can explore the web of data. With linked data, when you have some of it, you can find other, related, data
|
||||
|
||||
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
|
||||
permalink: web-standards/w3c/wg/json-ld/json-ld/
|
||||
permalink: web-standards/w3c/wg/json-ld/
|
||||
redirect_from:
|
||||
- web-standards/w3c/wg/json-ld/json-ld/
|
||||
- web-standards/w3c/json-ld-wg/json-ld/
|
||||
- web-standards/linked-data/JSON-LD/
|
||||
- specs-standards/JSON-LD/
|
||||
@ -11,10 +11,10 @@ excerpt: >
|
||||
tags: ["W3C","WebAuthN","Microsoft","FIDO"]
|
||||
categories: ["Web Standards"]
|
||||
redirect_from:
|
||||
- web-standards/w3c/webauthn/
|
||||
- web-standards/w3c/webauthn/webauthn/
|
||||
- specs-standards/webauthn/
|
||||
- web-standards/webauthn/
|
||||
- web-standards/w3c/wg/webauthn/
|
||||
permalink: web-standards/w3c/wg/webauthn/webauthn/
|
||||
permalink: web-standards/w3c/webauthn/
|
||||
last_modified_at: 2023-05-19
|
||||
---
|
||||
@ -8,9 +8,10 @@ excerpt: >
|
||||
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.
|
||||
categories: ["Web Standards"]
|
||||
tags: ["51nodes","ABT Network","Aergo","Alastria","ArcBlock","Ardor","Baidu","BCGov","Besu","BIF","BiiLabs","Binance","Bitcoin","BlockchainCommons","Blockcore","Blocko","Blockstack","BOTLabs","bryk","BSC","Teleinfo CAICT","Celo","Ceramic Network","Chainyard","Cloudchain","Commercio","Consensys","Consent","Corda","Cosmos","Credentials Community Group","cryptonics","DID:AERGO","DID:ALA","DID:AVVCYBER","DID:BBA","DID:BID","DID:BNB","DID:BRYK","DID:BTCR","DID:CCP","DID:CELO","DID:COM","DID:CORDA","DID:DID","DID:DOCK","DID:DOGE","DID:ECHO","DID:ELASTOS","DID:ELEM","DID:EMTRUST","DID:EOS","DID:ERC725","DID:ETHO","DID:ETHR","DID:EVAN","DID:FACTOM","DID:GATC","DID:GIT","DID:GITHUB","DID:GRG","DID:HEDERA","DID:HOLO","DID:ICON","DID:INDY","DID:IO","DID:ION","DID:IPID","DID:IS","DID:IWT","DID:JLINC","DID:JNCTN","DID:JOLO","DID:JWK","DID:KEY","DID:KILT","DID:KLAY","DID:LIFE","DID:META","DID:MOAC","DID:MORPHEUS","DID:NEAR","DID:NFT","DID:OBJECT","DID:OCKAM","DID:OMN","DID:ONION","DID:ONT","DID:OP","DID:ORB","DID:PANACEA","DID:PEER","DID:PISTIS","DID:PKH","DID:PTN","DID:SAN","DID:SCHEMA","DID:SELFKEY","DID:SIGNOR","DID:SIRIUS","DID:SOV","DID:STACK","DID:TAG","DID:TANGLE","DID:TRUSTBLOC","DID:TRX","DID:TTM","DID:TWIT","DID:TYRON","DID:TYS","DID:TZ","DID:UNDID","DID:UNISOT","DID:UNS","DID:V1","DID:VAA","DID:VAULTIE","DID:VID","DID:VVO","DID:WEB","DID:WLK","DID:WORK","DID","Digital Bazaar","Dock","Echo","Elastos","Element","Email","EOS","ERC725","Ethereum","Evan Network","Evernym","Fabric","Factom","Gatica","Github","GRGBanking","GrgChain","Halialabs","Hashgraph","Holochain","Hydra","Hyland Credentials","Hyperledger","IBM","ICONLOOP","IIW","Indy","InfoWallet","ION","IOP","IOTA","IoTeX","IPFS","JLinc","Jnctn","Jolocom","JWK","KILT","Klaytn","lifeID","MediBloc","Metadium","Microsoft","MOAC","NEAR","Ocean Protocol","Ockam","OmniOne","Ontology","Panacea","ProximaX","Quorum","Raonsecure","RChain","RWoT","SecureKey","SelfKey Identity","SelfKey","Sovrin Foundation","Sovrin","SpaceElephant","Sphereon","SpruceID","Swisscom","TIFAC-CORE","TMChain","Token.TM","TOR","TranSendX","Transmute","TRON","Twitter","UNISOT","UNS","uPort","Vaultie","VeramoLabs","Veres One","Vivvo","VP","W3C","Weelink","Workday","YLZ Inc","Zilliqa"]
|
||||
permalink: web-standards/w3c/wg/did/decentralized-identifier/
|
||||
permalink: web-standards/w3c/decentralized-identifier/
|
||||
canonical_url: https://decentralized-id.com/web-standards/w3c/wg/did/decentralized-identifier/
|
||||
redirect_from:
|
||||
- web-standards/w3c/wg/did/decentralized-identifier/
|
||||
- web-standards/w3c/did-wg/decentralized-identifier/
|
||||
- specs-standards/decentralized-identifier-did/
|
||||
- web-standards/decentralized-identifier-did/
|
||||
@ -9,12 +9,15 @@ excerpt: >
|
||||
Verifiable credentials (VCs) are the electronic equivalent of the physical credentials that we all possess today, such as: plastic cards, passports, driving licenses, qualifications and awards, etc. The data model for verifiable credentials is a World Wide Web Consortium Recommendation, "Verifiable Credentials Data Model 1.0 - Expressing verifiable information on the Web" published 19 November 2019.
|
||||
tags: ["W3C","Verifiable Credentials","Credentials Community Group","VC-WG","JSON-LD","OAuth","FIDO","Claims and Credentials WG"]
|
||||
categories: ["Web Standards"]
|
||||
permalink: web-standards/w3c/wg/vc/verifiable-credentials/
|
||||
permalink: web-standards/w3c/verifiable-credentials/
|
||||
header:
|
||||
image: /images/verifiable-credentials_head.webp
|
||||
caption: "[Verifiable Credentials Data Model](https://www.w3.org/TR/vc-data-model/)"
|
||||
teaser: /images/verifiable-credentials-teaser.webp
|
||||
redirect_from:
|
||||
- web-standards/w3c/wg/vc/
|
||||
- web-standards/vc-wg/
|
||||
- web-standards/w3c/wg/vc/verifiable-credentials/
|
||||
- web-standards/w3c/wg/vc/verifiable-credentials/adoption/
|
||||
- web-standards/w3c/vc-wg/verifiable-credentials/
|
||||
- specs-standards/verifiable-credentials/
|
||||
@ -1,122 +0,0 @@
|
||||
---
|
||||
date: 2020-11-09
|
||||
title: W3C History
|
||||
description: An international community that develops open standards to ensure the long-term growth of the Web.
|
||||
excerpt: "First started as an IETF application area at the beginning of 1990, the Web standard stack, given its foreseen volume and applicative nature on top of the Internet protocols, quickly spun off its own forum. The W3C then laid the foundations of the Web with the development of HTML 4 and XML at the end of the last century. It still works closely with IETF today, on the HTTP or URL specifications and in other areas of common interest (e.g. crypto, security, video)."
|
||||
layout: single
|
||||
permalink: web-standards/w3c/history/
|
||||
canonical_url: 'https://decentralized-id.com/web-standards/w3c/history/'
|
||||
categories: ["Web Standards","History"]
|
||||
tags: ["W3C","0Auth","Microsoft"]
|
||||
header:
|
||||
image: /images/w3c_banner.webp
|
||||
teaser: /images/w3c_teaser.webp
|
||||
last_modified_at: 2020-11-22
|
||||
---
|
||||
|
||||
**[World Wide Web Consortium(W3C)](https://www.w3.org/) • [Twitter](https://twitter.com/w3c) • [GitHub](https://github.com/w3c) • [LinkedIn](https://www.linkedin.com/company/w3c/)**
|
||||
|
||||
* [ICANN WIki](https://icannwiki.org/W3C)
|
||||
> 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).
|
||||
|
||||
## Consortium
|
||||
|
||||
> 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.
|
||||
|
||||
### [Mission](https://www.w3.org/Consortium/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. Learn more about OpenStand: the modern paradigm for standards.
|
||||
|
||||
### [Facts](https://www.w3.org/Consortium/facts.html)
|
||||
|
||||
> 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.
|
||||
|
||||
### Early Early
|
||||
* [Web Design Issues - Identity](https://www.w3.org/DesignIssues/Identity.html) Tim Berners-Lee 1998
|
||||
> Identifiers - what is identified?\
|
||||
> 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.
|
||||
The Platform for Privacy Preferences 1.1 (P3P1.1) Specification
|
||||
* [Identity Interoperability](https://www.w3.org/2005/Incubator/webid/wiki/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.
|
||||
* [The Platform for Privacy Preferences 1.1 (P3P1.1) Specification](https://www.w3.org/TR/P3P11/)
|
||||
> 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.
|
||||
* [Identity Definitions in the P3P Specification](https://www.w3.org/P3P/2003/09-identifiable.html)
|
||||
* [Identity Rights Agreements and Provider Reputation](https://www.w3.org/2005/Security/usability-ws/papers/26-idcommons/)
|
||||
> IDENTITY COMMONS Position Paper Kaliya Hamlin, Identity Woman & Identity Commons Phillip J. Windley, Brigham Young University Aldo Castaneda, The Story of Digital Identity
|
||||
>
|
||||
> 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.
|
||||
|
||||
### [W3C Workshop on Identity in the Browser](https://www.w3.org/2011/identity-ws/report.html) 24/25th May 2011, Mountain View (USA)
|
||||
> 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.
|
||||
>
|
||||
>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.
|
||||
|
||||
[Position papers](https://www.w3.org/2011/identity-ws/papers.html) • [Download all papers](https://www.w3.org/2011/identity-ws/papers.zip) as a ZIP file.
|
||||
|
||||
* [Identity in the Browser: Easy Wins and Guiding Principles](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_52.pdf) by Naveen Agarwal, Miranda Callahan, Tyler Close, Travis McCoy, Chris Messina, Glen Murphy, Dirk Pranke (Google)
|
||||
* [National Strategy for Trusted Identities in Cyberspace - Requirements and Potential Use Cases](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_21.pdf) by Peter Alterman (NIH)
|
||||
* [A Vision for Browser-Assisted Web Authentication](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_43.pdf) by Siddharth Bajaj, Slawek Ligier (Symantec)
|
||||
* [The Chained Identity Systems of Online Entertainment](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_14.pdf) by Wendell Baker (Yahoo!)
|
||||
* [Identity in the Platform - Thinking Beyond the Browser](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_26.pdf) by Dirk Balfanz (Google)
|
||||
* [Web authentication is deeply flawed, and it is time to fix it](https://www.w3.org/2011/identity-ws/papers/bichsel-raggett-wenning.html) by Patrik Bichsel, Dave Raggett and Rigo Wenning
|
||||
* [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) by Aaron Brauer-Rieke (Center for Democracy & Technology)
|
||||
* [Expression of Interest - Improving Identity Management on the Internet](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_12.pdf) by David W Chadwick, George Inman, Kristy Siu (University of Kent)
|
||||
* [NSTIC, Privacy and Social Login](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_48.pdf) by Francisco Corella, Karen P. Lewison (Pomcor)
|
||||
* [Tailored Signatures with DOSETA](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_1.pdf) by D. Crocker (Brandenburg InternetWorking)
|
||||
* [AuthenTec Online Open Authentication](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_34.pdf) by Vito Fabbrizio, Greg Kerr (AuthenTec)
|
||||
* [Account Management: A Deployment and Usability Problem](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_10.pdf) by Phillip Hallam-Baker (Comodo Group)
|
||||
* [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) by Kaliya Hamlin, Mary Hodder (Personal Data Ecosystem Consortium)
|
||||
* [Federated Browser-Based Identity using Email Addresses](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_25.pdf) by Mike Hanson, Dan Mills, Ben Adida (Mozilla)
|
||||
* [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) by Dick Hardt
|
||||
* [Identity as a Platform Service](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_9.pdf) by Sam Hartman (Painless Security), Josh Howlett (JANET(UK))
|
||||
* [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) by Carl Hewitt
|
||||
* [Identity in the Browser - Avoiding Common Flaws](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_37.pdf) by Brad Hill
|
||||
* [Importance and Impact of Requirements on Technical Solutions for Identity](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_31.html) by Frederick Hirsch (Nokia)
|
||||
* [Mobile Provided Identity Authentication on the Web](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_20.pdf) by Jonas Hogberg(Ericsson)
|
||||
* [The Nexus of Identity](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_35.pdf) by Maryann Hondo, Mary Ellen Zurko, Matthew Flaherty, Paula K. Austel, Sridhar Muppidi (IBM)
|
||||
* [How to Improve the Security around the Mobile User Authentication Process?](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_6.pdf) by John Hwang (Neustar)
|
||||
* [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) by Phil Hunt (Oracle)
|
||||
* [The Emerging JSON-Based Identity Protocol Suite](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_30.pdf) by Michael B. Jones (Microsoft)
|
||||
* [Identity Security within Web Browsers](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_8.pdf) by Kevin Jones, Narm Gradiraju, Jack Matheson (Intel)
|
||||
* [Selected issues with web identity mechanisms and a possible way forward](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_18.pdf) by Vladimir Katardjiev, Goran Eriksson (LM Ericsson AB)
|
||||
* [Identity in the Federal Learning Registry](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_27.pdf) by James Klo, Marie Bienkowski (SRI International)
|
||||
* [Goals, Constraints, and Issues for Identity in the Browser](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_2.pdf) by John Linn (RSA/EMC)
|
||||
* [Browser Personas: Towards a Reasonable Middle Ground](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_40.pdf) by Ben Livshits (Microsoft)
|
||||
* [Backplane Protocol and Identity Scenario](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_49.pdf) by Brian Mcginnis, Johnny Bufu, Vlad Skvortsov (Echo)
|
||||
* [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) by Miguel A. Monjas, Jose M. del Alamo, Juan-Carlos Yelmo, Jonas Hogberg (Ericsson)
|
||||
* [Browser support for identity federation with many identity providers](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_29.pdf) by RL "Bob" Morgan (University of Washington, InCommon)
|
||||
* [Reparing HTTP authentication for Web security](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_36.pdf) by Yutaka Oiwa, Tatsuya Hayashi, Boku Kihara (AIST)
|
||||
* [Bridging the Disconnect Between Web Privacy and User Perception](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_38.pdf) by Mike Perry (The Tor Project)
|
||||
* [Improving password managers and multidevice synchronization](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_47.pdf) by Yngve Pettersen (Opera Software ASA)
|
||||
* [Two-factor Authentication for the Cloud](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_11.pdf) by Anders Rundgren (PrimeKey Solutions AB)
|
||||
* [The WebID Protocol & Browsers](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_22/webid.html) by Jeff Sayre, Henry Story
|
||||
* [Thoughts on Trust Infrastructure, User Interface, and Legal Issues](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_50.pdf) by Stephen Schultze (Princeton University)
|
||||
* [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) by Dan Schutzer (Financial Services Roundtable/BITS)
|
||||
* [Do you know who I am?](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_51.pdf) by David Singer (Apple)
|
||||
* [Building the Legal Framework for Browser-Enabled Identity](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_39.pdf) by Thomas J. Smedinghoff (Wildman Harrold, Allen & Dixon)
|
||||
* [A WebID Implementation in Pure JavaScript and Flash](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_7.pdf) by Manu Sporny, David Longley, David I. Lehn, Mike Johnson (Digital Bazaar)
|
||||
* [Identity in the Browser: Putting the Cart Before the Horse](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_55.pdf) by Andy Steingruebl, Jeff Hodges (PayPal)
|
||||
* [A usable identity management system for the Digital Public Space](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_17.html) by Olivier Thereaux, Mo McRoberts, Richard Northover (British Broadcasting Corporation)
|
||||
* [On OIX and NSTIC](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_53.pdf) by Don Thibeau (OpenID Foundation, OIX)
|
||||
* [Digital Identity in Perspective](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_57.pdf) by John Tolbert (The Boeing Company)
|
||||
* [Identity In The Browser at 5. Lessons Learned](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_41.html) by Paul Trevithick (Azigo)
|
||||
* [Browser Support for the Open Authorization (OAuth) Protocol](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_32.pdf) by Hannes Tschofenig, Barry Leiba, Blaine Cook, Rob van Eijk
|
||||
* [The Need for a Web Security API](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_28.pdf) Sean Turner (IETF Security Area Director), Stephen Farrell (IETF Security Area Director), Peter Saint-Andre (IETF Applications Area Director)
|
||||
* [Server Authentication with DNSSEC](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_3.pdf) by M. Vanderveen
|
||||
* [Browser Assisted Identity Management](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_15.pdf) by Yu Wang, Aanchal Gupta (Yahoo!)
|
||||
* [Position paper from Netflix, Inc.](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_23.pdf) by Mark Watson, Mitch Zollinger, Wesley Miaw (Netflix)
|
||||
* [GSS-REST, a Proposed Method for HTTP Application-Layer Authentication](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_16.pdf) by Nicolas Williams (Cryptonector)
|
||||
* [Consumer Third Party Authentication: Challenges and Potential Solutions](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_42.pdf) by Craig H. Wittenberg (Microsoft)
|
||||
|
||||
### And beyond
|
||||
|
||||
* [A draft charter of Web Identity](https://www.w3.org/community/webcryptoapi/2011/10/05/a-draft-charter-of-web-identity/) Channy Yun - Posted on: October 5, 2011
|
||||
> The W3C has prepared Web Identity working group and make a draft charter. As following is main track for works.
|
||||
* [ISSUE-17: Identity, Agent, Person, Persona, Account etc. need clarifications](https://www.w3.org/Social/track/issues/17)
|
||||
> As for today we don't seem to have clear strategy on how to define and use Online Identity related concepts.
|
||||
* [WebID](https://www.w3.org/wiki/WebID) - W3C Wiki
|
||||
> 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.
|
||||
* [USER IDENTITY ON THE WEB COMMUNITY GROUP](https://www.w3.org/community/w3id/)
|
||||
> 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.
|
||||
* [The Story of Open SSI Standards - Drummond Reed/Evernym - Webinar 1](https://ssimeetup.org/story-open-ssi-standards-drummond-reed-evernym-webinar-1/) • [Youtube](https://www.youtube.com/watch?v=RllH91rcFdE) • [Slideshare](https://www.slideshare.net/SSIMeetup/self-sovereign-identity-ssi-open-standards-with-drummond-reed)
|
||||
> 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.
|
||||
@ -1,9 +1,11 @@
|
||||
---
|
||||
date: 2020-11-09
|
||||
name: W3C
|
||||
layout: standards
|
||||
title: World Wide Web Consortium
|
||||
headings: ["Main","W3C ID History","ID in the Browser 2011"]
|
||||
description: An international community that develops open standards to ensure the long-term growth of the Web.
|
||||
excerpt: "First started as an IETF application area at the beginning of 1990, the Web standard stack, given its foreseen volume and applicative nature on top of the Internet protocols, quickly spun off its own forum. The W3C then laid the foundations of the Web with the development of HTML 4 and XML at the end of the last century. It still works closely with IETF today, on the HTTP or URL specifications and in other areas of common interest (e.g. crypto, security, video)."
|
||||
layout: single
|
||||
permalink: web-standards/w3c/
|
||||
canonical_url: 'https://decentralized-id.com/web-standards/w3c/'
|
||||
categories: ["Web Standards","Organizations"]
|
||||
@ -11,119 +13,7 @@ tags: ["W3C","Credentials Community Group","JSON-LD","WebAuthN","DID","Verifiabl
|
||||
header:
|
||||
image: /images/w3c_banner.webp
|
||||
teaser: /images/w3c_teaser.webp
|
||||
last_modified_at: 2020-11-22
|
||||
last_modified_at: 2023-05-19
|
||||
redirect_from:
|
||||
- web-standards/w3c/history/
|
||||
---
|
||||
|
||||
**[World Wide Web Consortium(W3C)](https://www.w3.org/) • [Twitter](https://twitter.com/w3c) • [GitHub](https://github.com/w3c) • [LinkedIn](https://www.linkedin.com/company/w3c/)**
|
||||
|
||||
* [ICANN WIki](https://icannwiki.org/W3C)
|
||||
> 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).
|
||||
|
||||
## Consortium
|
||||
|
||||
> 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.
|
||||
|
||||
### [Mission](https://www.w3.org/Consortium/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. Learn more about OpenStand: the modern paradigm for standards.
|
||||
|
||||
### [Facts](https://www.w3.org/Consortium/facts.html)
|
||||
|
||||
> 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.
|
||||
|
||||
### [Standards](https://www.w3.org/standards/)
|
||||
|
||||
> 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.
|
||||
|
||||
## Info
|
||||
|
||||
* [W3C Workshop on Strong Authentication & Identity](https://www.w3.org/Security/strong-authentication-and-identity-workshop/report.html)
|
||||
* [A Public Identity](https://www.w3.org/DesignIssues/PublicIdentity.html) - Tim Berners-Lee 2018
|
||||
> 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.
|
||||
* [Call for Participation in Digital Identity Community Group](https://www.w3.org/community/dic/2019/06/20/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.
|
||||
|
||||
## Community and Working Groups on GitHub
|
||||
### Verifiable Claims Working Group (VC-WG)
|
||||
|
||||
[Verifiable Claims WG - Mailing List](https://lists.w3.org/Archives/Public/public-vc-wg/) (and archives)
|
||||
|
||||
* [w3c/verifiable-claims](https://github.com/w3c/verifiable-claims) - W3C Verifiable Claims Working Group.
|
||||
* [w3c/vc-data-model](https://github.com/w3c/vc-data-model) -Verifiable Claims Data Model and Representations specification.
|
||||
* [w3c/vc-use-cases](https://github.com/w3c/vc-use-cases) - Verifiable Claims Use Cases.
|
||||
* [w3c/vc-test-suite](https://github.com/w3c/vc-test-suite) - Verifiable Claims WG Test Suite.
|
||||
* [w3c/vc-imp-guide](https://github.com/w3c/vc-imp-guide) - Verifiable Credentials Implementation Guidelines
|
||||
|
||||
### Credentials Community Group (CCG)
|
||||
|
||||
[Public mailing list for the Credentials Community Group](http://lists.w3.org/Archives/Public/public-credentials/) (and archives) - Anyone may read or write to this list.
|
||||
* [w3c-ccg/meetings](https://github.com/w3c-ccg/meetings) CCG Meeting Transcripts
|
||||
* [w3c-ccg/community](https://github.com/w3c-ccg/community) - CCG Community Repo
|
||||
* [w3c-ccg/announcements](https://github.com/w3c-ccg/announcements) - CCG Announcements
|
||||
* [w3c-ccg/w3c-ccg-process](https://github.com/w3c-ccg/w3c-ccg-process)
|
||||
* [w3c-ccg/registries-process](https://github.com/w3c-ccg/registries-process)
|
||||
|
||||
#### DID
|
||||
|
||||
* [w3c-ccg/did-primer](https://github.com/w3c-ccg/did-primer) - A Primer for Decentralized Identifiers
|
||||
* [w3c-ccg/did-spec](https://github.com/w3c-ccg/did-spec) - Decentralized Identifier (DID) 1.0 Specification - Data Model and Syntax
|
||||
* [w3c-ccg/did-resolution](https://github.com/w3c-ccg/did-resolution) Spec 1.0
|
||||
* [w3c-ccg/did-use-cases](https://github.com/w3c-ccg/did-use-cases)
|
||||
* [w3c-ccg/did-method-registry](https://github.com/w3c-ccg/did-method-registry) - a list of all known DID Methods and their current level of maturity.
|
||||
* [w3c-ccg/didm-btcr](https://github.com/w3c-ccg/didm-btcr) - WORK ITEM: BTCR DID Method Spec
|
||||
* [w3c-ccg/didm-veres-one](https://github.com/w3c-ccg/didm-veres-one) - Veres One Decentralized Identifier Method Specification
|
||||
* [w3c-ccg/did-wg-proposal](https://github.com/w3c-ccg/did-wg-proposal) - Proposal to W3C membership for a DID Working Group.
|
||||
* [w3c-ccg/did-wg-charter](https://github.com/w3c-ccg/did-wg-charter) - EXPERIMENTAL charter for the W3C Decentralized Identifier Working Group
|
||||
* [w3c-ccg/did-hackathon-2018](https://github.com/w3c-ccg/did-hackathon-2018)
|
||||
* [w3c-ccg/data-minimization](https://github.com/w3c-ccg/data-minimization) - Data Minimization, Selective Disclosure, and Progressive Trust
|
||||
* [w3c-ccg/credential-handler-api](https://github.com/w3c-ccg/credential-handler-api)
|
||||
* [w3c-ccg/amira](https://github.com/w3c-ccg/amira) - Amira Engagement Model.
|
||||
* [w3c-ccg/functional-identity](https://github.com/w3c-ccg/functional-identity)
|
||||
|
||||
#### Verifiable Credentials
|
||||
|
||||
* [w3c-ccg/vc-status-registry](https://github.com/w3c-ccg/vc-status-registry) - REGISTRY: The Verifiable Credentials Status Scheme Registry.
|
||||
* [w3c-ccg/edu_occ_verifiable_credentials](https://github.com/w3c-ccg/edu_occ_verifiable_credentials) - WORK ITEM: Drafts and Ideas of Educational and Occupational Verifiable Credentials.
|
||||
* [w3c-ccg/vc-examples](https://github.com/w3c-ccg/vc-examples) - WORK ITEM: Verifiable Credentials Examples
|
||||
|
||||
#### Linked Data
|
||||
* [w3c-ccg/ocap-ld](https://github.com/w3c-ccg/ocap-ld) - WORK ITEM: Linked Data Object Capabilities specification
|
||||
* [w3c-ccg/ld-cryptosuite-registry](https://github.com/w3c-ccg/ld-cryptosuite-registry) - REGISTRY: Linked Data Keys Registry
|
||||
|
||||
### WebAuthN WG
|
||||
|
||||
* [w3c/webauthn](https://github.com/w3c/webauthn) - Web Authentication: An API for accessing Public Key Credentials
|
||||
* [w3c.github.io/webauthn/](https://w3c.github.io/webauthn/) (website)
|
||||
* [w3c/webauthn-pay](https://github.com/w3c/webauthn-pay) - Joint task force of Web Authentication WG and Web Payments WG
|
||||
|
||||
### JSON-LD WG
|
||||
- [w3c/json-ld-wg](https://github.com/w3c/json-ld-wg) • [website](https://www.w3.org/2018/json-ld-wg/)
|
||||
- [w3c/json-ld-framing](https://github.com/w3c/json-ld-framing) - JSON-LD 1.1 Framing Specification
|
||||
- [w3c/json-ld-api](https://github.com/w3c/json-ld-api) - JSON-LD 1.1 Processing Algorithms and API Specification
|
||||
- [w3c/json-ld-syntax](https://github.com/w3c/json-ld-syntax) - JSON-LD 1.1 Specification
|
||||
* [w3c/json-ld-bp](https://github.com/w3c/json-ld-bp) JSON-LD 1.1 Best Practices Note [w3c.github.io/json-ld-bp](https://w3c.github.io/json-ld-bp/)
|
||||
* [w3c/json-ld-rc](https://github.com/w3c/json-ld-rc)
|
||||
|
||||
### W3C DID 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.
|
||||
|
||||
- [w3c/did-wg](https://github.com/w3c/did-wg)
|
||||
- [Website](https://www.w3.org/2019/did-wg/)
|
||||
- [Charter](https://w3c-ccg.github.io/did-wg-charter/)
|
||||
- [did-core](https://github.com/w3c/did-core) - [site](https://w3c.github.io/did-core/)
|
||||
> W3C Decentralized Identifier Specification v1.0
|
||||
- [.well-known](https://github.com/decentralized-identity/.well-known) - [site](https://identity.foundation/.well-known)
|
||||
> Specs and documentation for all DID-related /.well-known resources
|
||||
- [did-spec-registries](https://github.com/w3c/did-spec-registries) - [site](https://w3c.github.io/did-spec-registries/)
|
||||
> DID Spec Registry (Note)
|
||||
- [did-use-cases](https://github.com/w3c/did-use-cases) - [site](https://w3c.github.io/did-use-cases/)
|
||||
> Decentralized Identifier Use Cases and Requirements v1.0
|
||||
- [did-wg](https://github.com/w3c/did-wg) - [site](https://www.w3.org/2019/did-wg/)
|
||||
> Home page of the Decentralized Identifier Working Group
|
||||
- [did-test-suite](https://github.com/w3c/did-test-suite) - [site](https://w3c.github.io/did-test-suite/)
|
||||
> W3C DID Test Suite and Implementation Report
|
||||
- [did-imp-guide](https://github.com/w3c/did-imp-guide) - [site](https://w3c.github.io/did-imp-guide/)
|
||||
> DID Implementation Guide (Note)
|
||||
- [did-rubric](https://github.com/w3c/did-rubric) - [site](https://w3c.github.io/did-rubric/)
|
||||
> W3C Decentralized Characteristics Rubric v1.0
|
||||
|
||||
@ -4,7 +4,9 @@ title: Schema.org Community Group
|
||||
description: The Schema.org Community Group provides a forum for discussing all changes, additions and extensions to schema.org.
|
||||
excerpt: >
|
||||
The Schema.org Community Group provides a forum for discussing all changes, additions and extensions to schema.org. In addition to providing a public setting for the day to day operation of the project, it serves as the mechanism for reviewing extensions and as a liaison point for all parties developing independent extensions to the schema.org core.
|
||||
permalink: web-standards/w3c/cg/schema-org/
|
||||
permalink: web-standards/w3c/schema-org/
|
||||
redirect_from:
|
||||
- web-standards/w3c/cg/schema-org/
|
||||
tags: ["Schema.org","W3C","JSON-LD","RDF","Microsoft"]
|
||||
categories: ["Web Standards"]
|
||||
header:
|
||||
@ -1,5 +0,0 @@
|
||||
---
|
||||
published: false
|
||||
permalink: /web-standards/w3c/did-wg/
|
||||
tags: ["DID-WG","DID","W3C"]
|
||||
---
|
||||
@ -1,40 +0,0 @@
|
||||
---
|
||||
date: 2020-11-23
|
||||
layout: single
|
||||
title: W3C Verifiable Claims Working Group
|
||||
description: The mission of the 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.
|
||||
excerpt: The Working Group will maintain the Verifiable Credentials Data Model specification, which provides a mechanism to express a verifiable credential on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.
|
||||
permalink: web-standards/w3c/wg/vc/
|
||||
redirect_from:
|
||||
- web-standards/vc-wg/
|
||||
toc: false
|
||||
tags: ["W3C","VC-WG","Verifiable Credentials"]
|
||||
categories: ["Web Standards"]
|
||||
last_modified_at: 2020-11-23
|
||||
---
|
||||
|
||||
* [W3C Verifiable Claims Working Group](https://www.w3.org/2017/vc/WG/)
|
||||
* [w3c/verifiable-claims](https://github.com/w3c/verifiable-claims)
|
||||
* [public-vc-wg@w3.org](mailto:public-vc-wg@w3.org?subject="Subscribe"): the group’s primary mailing list.
|
||||
* [Mail Archives](https://lists.w3.org/Archives/Public/public-vc-wg/) - Technical discussion and public announcements for the Verifiable Claims Working Group
|
||||
> The mission of the 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.
|
||||
* [Verifiable Credentials Working Group Charter](https://www.w3.org/2020/01/vc-wg-charter.html)
|
||||
> The Working Group will maintain the Verifiable Credentials Data Model specification, which provides a mechanism to express a verifiable credential on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.
|
||||
|
||||
|
||||
## Outputs
|
||||
* [Verifiable Credentials Data Model 1.0](https://www.w3.org/TR/verifiable-claims-data-model/) and Representations specification.
|
||||
* [Editors Draft](https://w3c.github.io/vc-data-model/) - Expressing verifiable information on the Web
|
||||
* [GitHub w\ Issue Tracker](https://github.com/w3c/vc-data-model)
|
||||
* [Verifiable Credentials Use Cases](https://www.w3.org/TR/vc-use-cases/)
|
||||
* [Editors Draft](https://w3c.github.io/vc-use-cases/)
|
||||
* [GitHub w\ Issue Tracker](https://github.com/w3c/vc-use-cases) - Verifiable Claims Use Cases.
|
||||
* [Verifiable Credentials Implementation Guidelines 1.0](https://www.w3.org/TR/vc-imp-guide/)
|
||||
* [Editors Draft](https://w3c.github.io/vc-imp-guide/)
|
||||
* [GitHub with Issue Tracker](https://github.com/w3c/vc-imp-guide)
|
||||
* [W3C Verifiable Claims Working Group Test Suite](https://w3c.github.io/vc-test-suite/)
|
||||
* [w3c/vc-test-suite](https://github.com/w3c/vc-test-suite) Verifiable Claims WG Test Suite.
|
||||
* [Verifiable Credentials Data Model Implementation Report 1.0](https://w3c.github.io/vc-test-suite/implementations/)
|
||||
* [w3c/vctf](https://github.com/w3c/vctf) **Archived** (precursor to vcwg)
|
||||
> The Web Payments Interest Group's Verifiable Claims Task Force
|
||||
* [Verifiable Claims Task Force Use Cases](https://opencreds.org/specs/source/use-cases/)
|
||||
@ -1,44 +0,0 @@
|
||||
---
|
||||
date: 2020-11-25
|
||||
title: Verifiable Credentials - Adoption
|
||||
description: Companies and organizations adopting verifiable credentials.
|
||||
permalink: web-standards/w3c/wg/vc/verifiable-credentials/adoption/
|
||||
categories: ["Web Standards"]
|
||||
tags: ["Claims and Credentials WG","Verifiable Credentials","Adoption","Credentials Community Group","IBM","VC-WG","W3C","Blockcerts","Blockstack","MATTR","RWoT"]
|
||||
last_updated_at: 2020-11-25
|
||||
---
|
||||
|
||||
* [Substrate Verifiable Credentials Workshop](https://substrate.dev/substrate-verifiable-credentials/#/) - Learn to build blockchains with Parity Substrate
|
||||
* [Verifiable Credential API](https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITALEBSI/Verifiable+Credential+API) CEF Digital Connecting Europe
|
||||
> The Verifiable Credential API provides a Core Service of the EBSI platform providing the capability of creating W3C credentials ready for signing and validating W3C Verifiable Credentials.
|
||||
* [SolidVC : a decentralized framework for Verifiable Credentials on the web](https://dspace.mit.edu/handle/1721.1/121667)
|
||||
> 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.
|
||||
* [Blockcerts V3 Proposal - Verifiable Credentials & Decentralized Identifiers](https://community.blockcerts.org/t/blockcerts-v3-proposal-verifiable-credentials-decentralized-identifiers/2221)
|
||||
> 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.
|
||||
* [mattr.global/Verifiable Credential based Authentication via OpenID Connect](https://mattr.global/verifiable-credential-based-authentication-via-openid-connect/)
|
||||
> At MATTR, we’ve been working hard on an exciting opportunity with the Government of British Columbia (BC Gov) in Canada. In June 2019, the BC Gov Verifiable Organisations Network team put out a “Code With Us” development bounty to integrate KeyCloak, their chosen enterprise Identity and Access Management (IAM) solution, with a new W3C standard called Verifiable Credentials. This work led to a solution that enables the use of Verifiable Credentials (VC) as a means of authentication that is interoperable with OpenID Connect (OIDC). We call this work VC-AuthN-OIDC. The output is an adapter that bridges these standards and enables a whole new set of capabilities through a simple extension of most modern IAM solutions.
|
||||
* [Blockstack and Verifiable Credentials - Paris P2P Festival](https://p2p.paris/gen/attADzQJ92rNIv6B3-Blockstack_and_Verifiable_Credentials_-_Paris_P2P_Festival_.pdf)
|
||||
> • Keep auth and smart contracts on-chain\
|
||||
> • Keep encrypted data off-chain\
|
||||
> • Wrap everything in an easy JavaScript API
|
||||
* [IBM Verify Credentials](https://docs.info.verify-creds.com)
|
||||
> With IBM Verify Credentials and our alpha components, you can begin your journey of exploring the benefits of decentralized identity. We have provided an interactive experience centered around the challenge of proving your identity while opening a financial account. Additionally, we will walk you through the development of your first end-to-end decentralized identity solution.
|
||||
* [Verifiable credentials and libp2p](https://discuss.libp2p.io/t/verifiable-credentials-and-libp2p/206)
|
||||
> 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.
|
||||
* [Open Badges are Verifable Credentials](https://nbviewer.jupyter.org/github/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/open-badges-are-verifiable-credentials.pdf)
|
||||
> 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.
|
||||
* [Workday Credentials & WayTo™ By Workday](https://credentials.workday.com/docs/overview/)
|
||||
> An issuer is any entity that wishes to relinquish and publicly attest to the veracity of data pertaining to a user. Public attestation comes in the form of a digital signature. When an issuer offers a credential to a user, Workday Credentials cryptographically signs the data in each credential with the issuer's private key before offering it to the user. The signing key's corresponding public key is written to a public ledger and is declared as belonging to the issuer, so that anyone can use that public key to verify the signature embedded in a user's digital credentials and establish trust in a credential's authenticity.
|
||||
|
||||
## Code
|
||||
|
||||
* [Identity.com Verifiable Credential Library](https://www.npmjs.com/package/@identity.com/credential-commons)
|
||||
> 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.
|
||||
* [EDCI-Data-Model](https://github.com/european-commission-europass/EDCI-Data-Model)
|
||||
> The European Commission is developing the Europass Digital Credentials Infrastructure (EDCI) – a set of tools, services and software to support the issuance of authentic, tamper-proof digital credentials (such as qualifications and other learning achievements) across Europe. The EDCI is being developed as part of ongoing work to implement the new Europass Framework for supporting transparency of skills and qualifications in Europe.
|
||||
* [gautamdhameja/substrate-verifiable-credentials](https://github.com/gautamdhameja/substrate-verifiable-credentials)
|
||||
> A minimal Substrate runtime for verifiable credentials' issuance and verification.
|
||||
* [bcgov/TheOrgBook](https://github.com/bcgov/TheOrgBook)
|
||||
> A public repository of verifiable claims about organizations. A key component of the Verifiable Organization Network.
|
||||
* [bcgov/vc-authn-oidc](https://github.com/bcgov/vc-authn-oidc)
|
||||
> Verifiable Credential Authentication with OpenID Connect (VC-AuthN OIDC)
|
||||
Loading…
Reference in New Issue
Block a user