w3c / vc-data-model

W3C Verifiable Credentials Working Group — VC Data Model and Representations specification

https://w3c.github.io/vc-data-model/

w3c/vc-data-model Issues

Add issuee definition
Updated 8 days ago18
Add Security Considerations related to advances in Artificial Intelligence
Updated 9 days ago1
Ensure reserved terms are in v2 context
Updated 11 days ago
SD-JWT fields in the v2 context should use `"@type": "@json"`
Updated 12 days ago2
Comments/Suggestions on Privacy Considerations
Updated 12 days ago4
Could not define "name" and "description" as attributes of my type
Updated 12 days ago11
Consider explicitly allowing/recommending language maps for use in internationalisation.
Updated 12 days ago6
Revisit Verifiable Credential media types
Closed 13 days ago21
VC-JWT examples are out-of-date
Closed 14 days ago6
Suggest to make explicit reference to the JADES standard
Closed 14 days ago8
Remove at risk issue markers for property extension points.
Updated 19 days ago3
Unify cryptographic hash expression formats
Closed 23 days ago4
Inconsistency between spec and schema
Closed 24 days ago2
`credential repository` vs `repository`, and definitions in _1.2 Ecosystem Overview_ vs _2. Terminology_
Closed a month ago6
Example of Use of renderMethod
Updated a month ago3
EnvelopedVerifiablePresentation missing in https://www.w3.org/ns/credentials/v2
Closed a month ago3
Should we use `Ed25519Signature2020` in the Examples?
Closed a month ago4
consider merging 3.4 and 5.1 as both sections are about the credential lifecycle.
Closed 2 months ago1
Truth (or falsity) is not part of VCDM ecosystem
Closed 2 months ago4
first example contains an http url identifying a credential
Closed 3 months ago5
Do we need sha3-512 in the vocabulary tables?
Closed 3 months ago6
Unmatched HTML Tag
Closed 3 months ago3
What does the hash values in §B.2 mean?
Closed 4 months ago4
EnvelopedVerifiablePresentation missing in data model
Closed 4 months ago5
Unnecessary direction attribute?
Closed 4 months ago12
Specify what kind of processing is safe on a returned document
Closed 4 months ago23
Does the specification need a normative "Credential Type Specifications" section?
Closed 4 months ago5
Proposal: remove ambiguity and asymmetry as it relates to subject identifiers
Closed 4 months ago7
phrasing and/or punctuation for input "inputBytes or inputDocument and inputMediaType" needs work
Closed 4 months ago4
reconsider `@id` for `mediaType` term
Closed 4 months ago17
`Type-Specific Credential Processing` is better phrasing than `Credential Type-Specific Processing`
Closed 4 months ago2
Support of SHACL Schema in Version 2.0
Closed 4 months ago4
typo in Terms of Use
Closed 5 months ago2
Backtick characters in Internationalization / Language examples
Closed 5 months ago2
"…" as a term name in the context file?
Closed 5 months ago2
Rewrite verification algorithm in a way that does not cause layer violations
Closed 6 months ago9
(editorial) "bitstring" vs "bit string"
Closed 6 months ago1
Clarify embedded proof extension point
Closed 6 months ago3
Ensure `credentialStatus` `id` field is optional
Closed 6 months ago5
Do VCs still need Media Types with Multiple Suffixes?
Closed 6 months ago11
Verifying a VC should return the same credential regardless of the verification method
Closed 6 months ago3
Specify that it is important to validate the `issuer` value
Closed 6 months ago8
Allow extensions to ProblemDetails object
Closed 6 months ago5
Clarify section on verifiable credential graph
Closed 6 months ago13
Update algorithms section to normatively depend on the INFRA specification
Closed 6 months ago6
Separate verification from validation in verification algorithm
Closed 6 months ago5
Remove repetition of normative statements in verification algorithm
Closed 6 months ago4
Specify guarantees that all securing mechanisms must provide.
Closed 6 months ago10
Clarify the domain and range of the `verifiablePresentation.verifiableCredential` property
Closed 7 months ago7
Bug in the context file?
Closed 7 months ago7