[after #1518]"type" of VP when it includes `presentation_submission`

[David W Chadwick]

Verifiable Presentations have a type parameter which is an array so that different types of VP can be differentiated (as is the case for VCs as well). I suggest that we use different types of VP that have different contents. So a basic VP of type VerifiablePresentation would contain the minimum properties (@context, type, id, verifiableCredential, holder). When we add the presentation_submission property to the VP, we can add the second type value PresentationSubmission to the type array. In this way we make the VP “well formed”. If we add additional properties to the VP we can add different type values to indicate this.

[Kristina Yasuda]

I think it makes sense to add a text saying that when presentation_submission is included in a VP and not in the response, VP MUST contain type PresentationSubmission. Does a schema or @context needs to be defined..?

[David W Chadwick]

Yes an @context file needs to be defined that maps the string PresentationSubmission into its globally unique URL.

[David W Chadwick]

Alternatively we could simply put the URL as the type value e.g. https://oidf.org/oidc4vps/contexts?PresentationSubmission

[Kristina Yasuda]

resolution depends on the outcome of issue #1518

[Kristina Yasuda]

Closing since we agreed that presentation_submission must be included as a separate response parameter and not in the VP and PR #278 has been merged