Conversation
| "items": { | ||
| "type": "string", | ||
| "format": "uri" | ||
| }, |
There was a problem hiding this comment.
We will want an "AcceptedIssuer" type here as well, to allow an object with various properties.
There was a problem hiding this comment.
@dlongley noted on the call today that we should think about supporting this:
acceptedIssuers: [did, {"recognizedIn": <here>}]
| "type": "array", | ||
| "description": "List of accepted cryptographic suites for credential proofs", | ||
| "items": { | ||
| "$ref": "#/$defs/Cryptosuite" |
There was a problem hiding this comment.
We might want to call this an "AcceptedCryptosuite" type instead.
| "type": "array", | ||
| "description": "List of accepted envelope formats for credentials", | ||
| "items": { | ||
| "$ref": "#/$defs/Envelope" |
There was a problem hiding this comment.
We might want to call this an "AcceptedEnvelope" type instead.
| "credentialSubject": { | ||
| "type": "object", | ||
| "description": "Properties that the credential subject should have", | ||
| "properties": { |
There was a problem hiding this comment.
We might need to explicitly set additionalProperties: true. I don't recall what the JSON schema default value is.
|
The json schema will need to take into account the Schema could also be revisited at some point in the future to support other query types. |
3 participants
This PR is an attempt to address issue #538 by providing a JSON Schema for QueryByExample.