Skip to content

Need to clarify the nature of the media type in relationship to "credential" vs "verifiable-credential" #1012

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
OR13 opened this issue Jan 18, 2023 · 6 comments
Labels

Comments

@OR13
Copy link
Contributor

OR13 commented Jan 18, 2023

Related to #1009

Work to be done:

Add extra paragraph around the media type, something to this effect:

application/credential+ld+json

  1. proof MUST NOT be present.
  2. proof MAY be present.
  3. proof MUST be present.
@TallTed
Copy link
Member

TallTed commented Jan 19, 2023

Seems to also need something alongside, like

application/verifiable-credential+ld+json

  1. proof MUST NOT be present.
  2. proof MAY be present.
  3. proof MUST be present.

and similar for any other known/expected simple or compound media types (incorporating jws, jwt, etc.)

@paulfdietrich
Copy link

Manu, after discussions today and the specification language

"This specification registers the application/credential+ld+json MIME Media Type specifically for identifying documents conforming to the Verifiable Credentials format."

This seems clear enough to me that this means a document conforming to the VC format. Not sure why there needs to be any language around whether a proof is required as it clearly is not. The string "credential" does evoke questions, but something like "w3c-vc", or "w3c-vc-2.0" would make it clearer to me that this media type dictates a document that conforms to this specification.

Whether there needs to be additional media types to specify a restricted data model where a proof MUST be present or MUST be absent, I defer to others, but there should be a media type that describes any document compliant with the data model VC specification.

@OR13
Copy link
Contributor Author

OR13 commented Apr 11, 2023

Seems we can close this, I will close based on the resolutions we have taken.

@OR13 OR13 closed this as completed Apr 11, 2023
@Sakurann
Copy link
Contributor

superceded by a resolution to use vc+ld+json for a credential

@iherman iherman reopened this Apr 12, 2023
@iherman
Copy link
Member

iherman commented Apr 12, 2023

The issue was discussed in a meeting on 2023-04-11

  • no resolutions were taken
View the transcript

1.5. Need to clarify the nature of the media type in relationship to "credential" vs "verifiable-credential" (issue vc-data-model#1012)

See github issue vc-data-model#1012.

Kristina Yasuda: Need to clarify the nature of the media type in relationship to "credential" vs "verifiable-credential" - was this resolved?.

Dave Longley: +1 to the idea that this is resolved.

Orie Steele: agrees that this has been resolved.

Joe Andrieu: suggests to move past this.

Kristina Yasuda: cheers on closing issue.

@iherman iherman closed this as completed Apr 12, 2023
@iherman
Copy link
Member

iherman commented Apr 12, 2023

The issue was discussed in a meeting on 2023-04-11

  • no resolutions were taken
View the transcript

1.5. (issue vc-data-model#1012)

See github issue vc-data-model#1012.

Kristina Yasuda: Need to clarify the nature of the media type in relationship to "credential" vs "verifiable-credential" - was this resolved?.

Dave Longley: +1 to the idea that this is resolved.

Orie Steele: agrees that this has been resolved.

Joe Andrieu: suggests to move past this.

Kristina Yasuda: cheers on closing issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants