Skip to content
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

Media types do not indicate securing mechanism #1065

Closed
msporny opened this issue Mar 15, 2023 · 3 comments · Fixed by #1107
Closed

Media types do not indicate securing mechanism #1065

msporny opened this issue Mar 15, 2023 · 3 comments · Fixed by #1107
Assignees
Labels
ready for PR This issue is ready for a Pull Request to be created to resolve it

Comments

@msporny
Copy link
Member

msporny commented Mar 15, 2023

Originally posted by @Sakurann in #1062 (comment)

media types do not indicate proofing mechanisms

I think we should apply the same philosophy to all media types related to this specification that media types describe a secured 'thing' and media type itself does not imply the proofing mechanism. given the base media type is application/vc+ld+json; all extensions of VCDM core spec should use vc+.

@TallTed
Copy link
Member

TallTed commented Mar 16, 2023

Rather, I would say that media types describe a securable 'thing' or media types describe a possibly secured 'thing'.

That is to say — as with a password-secured ZIP, or a signed and/or encrypted email message — the structure is defined by the media type and allows for signature or encryption, but the content does not necessarily include either signature or encryption.

@Sakurann
Copy link
Contributor

might be more in-scope fo vc-jwt spec. but needs guidance that this media type is to be used as cty not typ JOSE Header.

@msporny msporny self-assigned this Mar 20, 2023
@msporny msporny added the ready for PR This issue is ready for a Pull Request to be created to resolve it label Mar 20, 2023
@brentzundel
Copy link
Member

I've attempted to capture the language and ideas above in PR #1107, please review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready for PR This issue is ready for a Pull Request to be created to resolve it
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants