Orie Steele
Orie Steele
Originally: https://github.com/w3c-ccg/vc-http-api/issues/184 This is ready for PR against the spec, in some informative section of testing.
Can we remove the optionality from the "challenge" / "domain" part of requesting a presentation... and make a requirement. I suggest we do whatever https://github.com/decentralized-identity/waci-presentation-exchange/ does, and use a JWT.
https://github.com/w3c-ccg/vc-http-api/blob/main/docs/holder.yml#L59 in particular, apis that are meant to only be exposed with authorization vs apis that are meant to be exposed without authorization.
When `POST /credentials/issue` with `{ credential: { issuer: did:example:123, ... }` => 200 IF AND ONLY IF `did:example:123` is the default issuer for the issuer implied by the configuration.
What is it supposed to be? I assume the updated revocation list credential. probably the request payload should take a number instead of as string as well: POST https://vc.example/credentials/status ```...
Yet the current API definitions do not define this behavior.
Related: https://github.com/w3c/vc-data-model/issues/881 `proof` is not a property of "Credentials" it is a property of "Verifiable Credentials" that are secured by Data Integrity. The context defining the data integrity suite that...
See the long discussion on this PR https://github.com/w3c/vc-data-model/pull/795 This issue opened to track discussion, and work towards a proposed set of changes or closed issue.
Developers copy spec examples, we should plan to have better boilerplates in v2, here is an example: ```jsonc { "@context": [ // "https://www.w3.org/2018/credentials/v1", "https://www.w3.org/ns/credentials/v2", // "https://www.w3.org/2018/credentials/examples/v1" { "@vocab": "https://www.w3.org/ns/credentials#" }...
In general guidance on presentations is poor. My understanding of them is that they are meant to be extremely short lived, and bound to a challenge provided by a verifier....