If you have difficulty in submitting comments on draft standards you can use a commenting template and email it to admin.start@bsigroup.com. The commenting template can be found here.
Implementations MAY support requesting presentation of Verifiable Credentials using a set of scope values. A scope is an alias for a well-defined Presentation Definition. The specific scope value and the mapping between it and the respective Presentation Definition are out of the scope of this specification. The array MUST contain at least one value. If the array is empty, the Credential Service MUST return HTTP 4xx. If the array contains scopes that a client is not entitled to, the Credential Service MUST return HTTP 2xx with the PresentationResponseMessage's presentation array holding less entries than requested.A scope is a string value in the form:[alias]:[descriminator]The [alias] value MAY be implementation-specific.The vc.type alias value MUST be supported and is used to specify access to a verifiable credential by type. For example:org.eclipse.dspace.dcp.vc.type:Memberdenotes read-only access to the VC type Member and MAY be used to request a VC or VP.The org.eclipse.dspace.dcp.vc.id alias value MUST be supported and is used to specify access to a verifiable credential by id. For example:org.eclipse.dspace.dcp.vc.id:8247b87d-8d72-47e1-8128-9ce47e3d829ddenotes read-only access to the VC identified by 8247b87d-8d72-47e1-8128-9ce47e3d829d and MAY be used to request a Verifiable Credential. Schema JSON Schema REQUIRED - @context: Specifies a valid Json-Ld context ([json-ld11], sect. 3.1). - type: A string specifying the PresentationResponseMessage type. - presentation: An array of Verifiable Presentations. The Verifiable Presentations MAY be strings, JSON objects, or a combination of both depending on the format. OPTIONAL - presentationSubmission: A valid Presentation Submission according to [presentation-ex].A PresentationResponseMessage SHOULD only include valid (non-expired, non-revoked, non-suspended) credentials. The following are non-normative examples of the JSON response body:Example 4: Presentation Response Message{ "@context": [ "https://w3id.org/dspace-dcp/v1.0/dcp.jsonld" ], "type": "PresentationResponseMessage", "presentation": [ "presentation1", "presentation2" ]}Example 5: Presentation Response Message with Presentation Submission{ "@context": [ "https://w3id.org/dspace-dcp/v1.0/dcp.jsonld" ], "type": "PresentationResponseMessage", "presentation": [ "jwtPresentation" ], "presentationSubmission": { "id": "Presentation example 2", "definition_id": "Example with multiple VPs", "descriptor_map": [ { "id": "id_credential", "format": "jwt_vp", "path": "$.presentation[0]", "path_nested": { "id": "id_nested_credential", "format": "jwt_vc", "path": "$.vp.verifiableCredential[0]" } } ] }}
You are now following this standard. Weekly digest emails will be sent to update you on the following activities:
You can manage your follow preferences from your Account. Please check your mailbox junk folder if you don't receive the weekly email.
You have successfully unsubscribed from weekly updates for this standard.
Comment on proposal
Required form fields are indicated by an asterisk (*) character.