Skip to content

Instantly share code, notes, and snippets.

View msporny's full-sized avatar

Manu Sporny msporny

364 followers · 0 following
View GitHub Profile
@msporny
msporny / REC-did-core-20220630.html
Created June 28, 2022 23:32
<!DOCTYPE html><html lang="en" dir="ltr"><head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<meta name="generator" content="ReSpec 32.1.10">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<style>
span.example-title{text-transform:none}
:is(aside,div).example,div.illegal-example{padding:.5em;margin:1em 0;position:relative;clear:both}
div.illegal-example{color:red}
div.illegal-example p{color:#000}
:is(aside,div).example{border-left-width:.5em;border-left-style:solid;border-color:#e0cb52;background:#fcfaee}
@msporny
msporny / gist:ab415042ffd9c06ea3ad1ebd1df1da0a
Last active January 6, 2022 14:57
Verifiable Driver's License with Multiple Data Integrity proofs
{
"@context": [
"https://www.w3.org/2018/credentials/v1",
"https://w3id.org/vdl/v1",
"https://w3id.org/security/suites/ed25519-2020/v1",
"https://w3id.org/security/bbs/v1"
],
"issuer": "did:web:multisig.example",
"issuanceDate": "2022-01-02T00:16:42.195Z",
"type": [
@msporny
msporny / vdl-with-mso.json
Last active December 9, 2021 17:34
{
"@context": [
"https://www.w3.org/2018/credentials/v1",
"https://w3id.org/vdl/v1",
"https://w3id.org/security/iso18013-5/v1"
],
"type": [
"VerifiableCredential",
"Iso18013DriversLicenseCredential"
],
@msporny
msporny / index.html
Last active June 12, 2021 15:25
<!DOCTYPE html><html lang="en" dir="ltr"><head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<meta name="generator" content="ReSpec 26.8.12">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<style>
span.example-title{text-transform:none}
aside.example,div.example,div.illegal-example{padding:.5em;margin:1em 0;position:relative;clear:both}
div.illegal-example{color:red}
div.illegal-example p{color:#000}
aside.example,div.example{padding:.5em;border-left-width:.5em;border-left-style:solid;border-color:#e0cb52;background:#fcfaee}
@msporny
msporny / gist:831e768665a1257f426680b8b51b0009
Last active January 21, 2021 14:06
2021 - W3C CCG Charter Changes
W3C Credentials Community Group Charter (2020)
This charter was ratified by group consensus on [Date]. The previous revision of the Credentials Community Group Charter is also available for archival and auditing purposes.
The mission of the W3C 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.
Scope of Work
In general, topics that are “in scope” include anything related to enabling interoperable credentials on the Web. These topics include the following:
* S
@msporny
msporny / gist:2fac3957e84add230ea401259f84e6cd
Created August 4, 2020 21:51
PROPOSAL: Existing documentation in the DID Core specification should be refined to point out that Verification Relationships are arcs in a graph of information and Verification Methods are nodes in a graph of information. That is, they provide different types of information. The first (Verification Relationship) is the expression of a relationship between a DID Subject and cryptographic information used for the purposes of verifying a proof. The second (Verification Method) is the expression of cryptographic material. An image should be provided depicting the explanation.
PROPOSAL: Mark all verification methods with a warning stating that there is an ongoing discussion around the naming of verification methods that may impact the final names used in the specification.
PROPOSAL: The DID WG urges the W3C CCG to write documentation in the Linked Data Security specifications that clarifies how public / private key terminology has been used in the past, why it is vague and leads to security issues (like key reu
@msporny
msporny / w3c-ccg-spec-template.html
Created May 23, 2018 19:03
A ReSpec Template for W3C CCG Specifications
<!DOCTYPE html>
<html>
<head>
<title>A Template for W3C Credentials Community Group Specifications</title>
<meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
<!--
=== NOTA BENE ===
For the three scripts below, if your spec resides on dev.w3 you can check them
out in the same tree and use relative links so that they'll work offline,
-->
@msporny
msporny / credential-transmission.jsonld
Last active May 4, 2016 02:58
Example of credential transmission with proof of posession
{
"@context":"https://w3id.org/identity/v1",
"id":"did:90096afc-c232-4b96-b48c-dcdba19b7ead",
"type":"Identity",
"credential":[
{
"@graph":{
"@context":"https://w3id.org/identity/v1",
"id":"https://travel.state.gov/credentials/6fc0f6d2c68a",
"type":[
@msporny
msporny / ldsig-vs-jwt.md
Last active April 26, 2016 20:07
Example of similar JSON data being signed using Linked Data Signatures and JSON Web Tokens

Assume that we want to sign this bit of JSON-LD:

{
  "@context": "https://w3id.org/identity/v1",
  "title": "Hello World!"
}

This is what the Linked Data Signature looks like:




  


  




    


          
    

      

        
        

          

              @msporny
          

          

            
                msporny
                / shell.sh
            
            

              Created
              November 26, 2015 01:20
            

              
                Script to install nodejs 0.10.40
              
          

        

      

        

  

    
    


        



  


  

        

          
          curl -sL https://deb.nodesource.com/setup_0.10 | bash -
        

        

          
          apt-get install -y nodejs=0.10.40-*