Comments (7)
I'm not opposed to seeing an example in the spec that has been secured using JAdES, but the WG will need to come to consensus on that.
Has it been listed in the VC Specifications Directory as a viable securing mechanism? That should be the first step regardless.
from vc-data-model.
@brentzundel added as w3c/vc-specs-dir#36
from vc-data-model.
@anthonycamilleri wrote:
@brentzundel added as w3c/vc-specs-dir#36
This has been merged and included in the VC Specs Directory.
I'll note that the example linked to above is really big and verbose. Do you think you could add a JADES extension to respec-vc? That is what we use to generate the digitally signed examples. We could include JADES as another tab in some of the examples if you did so.
from vc-data-model.
In any case, we should capitalize JAdES (the "JSON format for AdES Signatures") correctly, painful though it may be...
from vc-data-model.
The issue was discussed in a meeting on 2024-06-05
- no resolutions were taken
View the transcript
6.1. Suggest to make explicit reference to the JADES standard (issue vc-data-model#1481)
See github issue vc-data-model#1481.
Brent Zundel: suggestion to make explicit reference to JADES standard.
… request is to have an example in our spec of how to do this.
Manu Sporny: I prefer not to include a big example, things signed with JADES are like 100KB blobs, adding an example would not demonstrate anything.
Dmitri Zagidulin: can we /link/ to a JADES example?
Manu Sporny: request to normatively say it is totally fine to use JADES, we shouldn't do that either.
… we do in the spec mention a variety of other securing formats, we mention JWT, CWT, mDL, Gordian Envelopes, etc, can add JADES to list.
Brent Zundel: +1 to adding to that list.
Brent Zundel: proposal is to link to JADES as we have linked to other securing mechanisms.
Phillip Long: +1 to that.
Brent Zundel: if you are opposed jump into the issue and tell us, otherwise that is what we will do.
… thanks to all for being here.
Ivan Herman: +1 for me as well.
from vc-data-model.
PR #1501 has been raised to address this issue. This issue will be closed once PR #1501 has been merged.
from vc-data-model.
The issue was discussed in a meeting on 2024-06-12
- no resolutions were taken
View the transcript
2.2. Add reference to JAdES standard in Ecosystem Compatability. (pr vc-data-model#1501)
See github pull request vc-data-model#1501.
See github issue vc-data-model#1481.
Brent Zundel: pull request 1501. the related issue is 1481. 1481 says -- we have a JADES impl of securing a VC, and think the spec should note that. this PR adds a link to JADES for ecosystem compatibility -- already has anoncreds, ACDC, many other 'vc-like' things that should be compatible with this spec.
… want to give folks a chance to look at it if they have not yet. it will be merged.
from vc-data-model.
Related Issues (20)
- first example contains an http url identifying a credential HOT 5
- Remove at risk issue markers for property extension points. HOT 3
- What does the hash values in §B.2 mean? HOT 4
- Proposal: remove ambiguity and asymmetry as it relates to subject identifiers HOT 7
- Do we need sha3-512 in the vocabulary tables? HOT 6
- Should we use `Ed25519Signature2020` in the Examples? HOT 4
- Unmatched HTML Tag HOT 3
- Revisit Verifiable Credential media types HOT 20
- consider merging 3.4 and 5.1 as both sections are about the credential lifecycle. HOT 1
- Add issuee definition HOT 17
- Truth (or falsity) is not part of VCDM ecosystem HOT 4
- `credential repository` vs `repository`, and definitions in _1.2 Ecosystem Overview_ vs _2. Terminology_ HOT 6
- Consider explicitly allowing/recommending language maps for use in internationalisation. HOT 5
- Example of Use of renderMethod HOT 3
- EnvelopedVerifiablePresentation missing in https://www.w3.org/ns/credentials/v2 HOT 3
- VC-JWT examples are out-of-date HOT 5
- Inconsistency between spec and schema HOT 2
- Unify cryptographic hash expression formats HOT 4
- Could not define "name" and "description" as attributes of my type HOT 10
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.