Comments (6)
I have tooling that generates similar graphs for JWT headers, which serve the same purpose...
I can take the action to produce svg diagrams for JWT headers.
from vc-data-model.
Boy, that sounds straightforward...
from vc-data-model.
%%{
init: {
'theme': 'base',
'themeVariables': {
'primaryColor': '#DDDDDD',
'primaryTextColor': '#000000',
'nodeBorder': '#000000',
'edgeLabelBackground': '#DDDDDD',
'clusterBkg': '#DDDDDD',
'clusterBorder': '#000000',
'lineColor': '#000000',
'fontFamily': 'monospace',
'darkmode': true
}
}
}%%
graph
subgraph 0 [  Verifiable Credential   ]
n4("Metadata")
n5("Claim(s)")
n6("Proof(s)")
end
subgraph 1 [  JSON Web Token   ]
n1("Header")
n2("Claimset")
n3("Signature")
end
subgraph 2 [  Claimset   ]
subgraph 3 [  Metadata   ]
n7("AlumniCredential")
n8("Credential 123")
n9("ExampleUniversity")
n10("2023-05-21T19:16:35.495Z")
end
subgraph 4 [  Claims   ]
n11("Pat")
n12("ExampleUniversity")
end
end
subgraph 5 [  Protected Header   ]
n13("iss: did:example:123")
n14("kid: #key-42")
n15("alg: ES384")
n16("typ: vc+ld+jwt")
n17("cty: vc+ld+json")
end
0 --   representation   --> 1
n8 -- type --> n7
n8 -- validFrom --> n10
n8 -- issuer --> n9
n8 -- subject --> n11
n11 -- AlumniOf --> n12
n2 --> 2
n1 --> 5
class n1,n4,n7,n8,n9,n10,n13,n14,n15,n16,n17 RedNode;
class n2,n5,n11,n12 YellowNode;
class n3,n6 GreenNode;
classDef RedNode text-align: center, color:#000, fill:#DDAABB, stroke:#000, stroke-width:1px;
classDef YellowNode color:#000, fill:#FFEE99, stroke:#000, stroke-width:1px;
classDef GreenNode color:#000, fill:#BBDDAA, stroke:#000, stroke-width:1px;
from vc-data-model.
With "proof tunneling"
%%{
init: {
'theme': 'base',
'themeVariables': {
'primaryColor': '#DDDDDD',
'primaryTextColor': '#000000',
'nodeBorder': '#000000',
'edgeLabelBackground': '#DDDDDD',
'clusterBkg': '#DDDDDD',
'clusterBorder': '#000000',
'lineColor': '#000000',
'fontFamily': 'monospace',
'darkmode': true
}
}
}%%
graph
subgraph 1 [  JSON Web Token   ]
n1("Header")
n2("Claimset")
n3("Signature")
end
subgraph 7 [  Verifiable Credential   ]
subgraph 2 [  Credential Graph   ]
subgraph 3 [  Metadata   ]
n7("AlumniCredential")
n8("Credential 123")
n9("ExampleUniversity")
n10("2023-05-21T19:16:35.495Z")
end
subgraph 4 [  Claims   ]
n11("Pat")
n12("ExampleUniversity")
end
end
subgraph 6 [  Proof Graph   ]
n18("Signature 456")
n19("DataIntegrityProof")
n20("2023-05-21T20:09:37.988Z")
n21("zu4oey5q...eV6")
n22("Example University Public Key 7")
end
end
subgraph 5 [  Protected Header   ]
n13("iss: did:example:123")
n14("kid: #key-42")
n15("alg: ES384")
n16("typ: vc+ld+jwt")
n17("cty: vc+ld+json")
end
2 --   proof   --> 6
n8 -- type --> n7
n8 -- validFrom --> n10
n8 -- issuer --> n9
n8 -- subject --> n11
n11 -- AlumniOf --> n12
n2 --> 7
n1 --> 5
n18 -- type --> n19
n18 -- created --> n20
n18 -- proofValue --> n21
n18 -- verificationMethod --> n22
class n1,n4,n7,n8,n9,n10,n13,n14,n15,n16,n17 RedNode;
class n2,n5,n11,n12 YellowNode;
class n3,n6,n18,n19,n20,n21,n22 GreenNode;
classDef RedNode text-align: center, color:#000, fill:#DDAABB, stroke:#000, stroke-width:1px;
classDef YellowNode color:#000, fill:#FFEE99, stroke:#000, stroke-width:1px;
classDef GreenNode color:#000, fill:#BBDDAA, stroke:#000, stroke-width:1px;
from vc-data-model.
Related PR is the digital bazaar tooling which is powering the current examples rendered in the spec... digitalbazaar/respec-vc#8
from vc-data-model.
The issue was discussed in a meeting on 2023-06-28
- no resolutions were taken
View the transcript
2.10. Add VC-JWT diagrams to core specification (issue vc-data-model#1135)
See github issue vc-data-model#1135.
Brent Zundel: #1135 - Add VC JWT diagrams to core specification.
Manu Sporny: yes, this can be a post-CR thing.
Michael Prorock: +1 post cr.
Brent Zundel: as diagrams are non-normative this is a post-CR.
Orie Steele: related to date integrity proofs in the core context and need to be understood by implementers. The pictures are one of the most important information we offer.
Shigeya Suzuki: Is it possible to add "diagram" tag for any issues requests diagrams?
Manu Sporny: +1 for diagrams visualizing both securing mechanisms.
Orie Steele: prefer to see the diagrams upgraded include proof specs that define securing mechanisms.
Manu Sporny: (PRs welcome) :).
Brent Zundel: w3c/vc-data-integrity#107.
Orie Steele: anyone working on JWT want diagrams to show up in the core data model? open a PR.
Brent Zundel: PRs are welcomed! (Manu encouraged that).
Orie Steele: You can always put your text in an issue, and ask an editor to do the PR for it.
Brent Zundel: if anyone has a problem raising a PR ask for help of Brent or anyone to learn how.
Michael Jones: reinforced Orie's comment about stuff that should be in the securing spec.
Orie Steele: +1 selfissued.
Manu Sporny: -1 to not talking about securing in the core spec.
Dave Longley: of course, philosophies around external vs. internal securing mechanisms are at odds there -- we should remember they are different things and that may influence approaches.
from vc-data-model.
Related Issues (20)
- Add Security Consideration to avoid key reuse HOT 5
- Pre-CR review from Jeffrey Yasskin HOT 9
- Update i18n example
- JSON-only processors and VCDM 2.0 conformance HOT 29
- Multiple Credential Status Lists HOT 2
- Prefer Arrays and Objects. HOT 5
- Clarify evidence section to point to OBv3 evidence property usage
- address normative statements in non-normative sections HOT 1
- Clarify what conformance means to the issuers/verifiers HOT 1
- add explicit notes where terminology in the spec diverges from things elsewhere
- Remove the at risk issue marker for `Evidence` HOT 5
- (Editorial) Use a three level deep TOC in the VCDM spec
- Controller Documents HOT 4
- Include credentialSubject examples that use URLs rather than DIDs
- Make Section 4.1 non-normative HOT 1
- Section 3 "Core Data Model" clean up
- clarify relationship to the `proof` property and the specifications defining how to secure VCs HOT 2
- Use a better example for bidirectional text (Editorial) HOT 4
- Default context contains terms outside of the spec HOT 9
- Consider abandoning drafts for non-data-integrity-proof securing formats HOT 13
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vc-data-model.