Orie Steele

Example: https://github.com/w3c-ccg/traceability-interop/blob/main/docs/openapi/schemas/SerializedVerifiablePresentation.yml ^ This covers the shape of both JWT and Data Integrity Proof VCs... I am in favor of defining schemas... I like type safe languages. I'm more interested...

if this is really a request for `presentationSchema` I suggest we update the title and description.

This is good, but it's unclear what changes need to be made to accept it.

I suggest making this PR spec text changes only.

I opened https://github.com/w3c/vc-data-model/issues/923. can we close this now?

I am in favor of eliminating "multiple credential subjects" as an option from the spec... I have not observed any real world use cases for this, and it seems that...

@TallTed @msporny please provide actual examples, not hypotheticals, happy to discuss on a call. For example, here are the credential formats we recently updated to avoid interoperability failures with JWT:...

> being an array and keeping it to only object or string (I'd like to see string option removed as well personally). +1 to making `credentialSubject` a non empty object,...

Answering my own question above: The following non normative example exist: https://www.w3.org/TR/vc-data-model/#example-specifying-multiple-subjects-in-a-verifiable-credential Here is that example slightly modified to show a blank node for one of the subjects: https://v.jsld.org/2WkicfpCVYRoHC9GcvevhboR812jL3J8DyCZ4evgRL9eJ3sE17ZkLMJ9Hvze4R9jRYMbiKBXaPCfER4czSmfYTHYqw9287F1VpKvKPEpebTrFYoWTFwSpMKU9ZwouwioyweMwNcBtsRYdajx5jHETMzSVHDVFkCSpWBXEe88KMHSvvgNGwgx4zwvHd4JLcdf4QW6uqeHM3jXCK55EVsYpJRz8PPUy6pQ68zFP11HUsrDDEXKND467Sy2m7sfo1XPdosZHMfdqhYu68CZp6CAZr2VQmzVxwUQEAUgXiZbTVWZEV896uHgMBUQK61aGigc17MQupZgvNjKtz73KFnZwpvcz3p1Q77tCVowUJBwQTgkL4dw8aUy8GHkTGD ```...

We could also just delete the sentence that says: > If sub is present, the value MUST be used to set the value of the id [property](https://www.w3.org/TR/vc-data-model/#dfn-property) of credentialSubject of...