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

Ambiguous language about specifying claims #63

Closed
selfissued opened this issue Aug 25, 2024 · 4 comments · Fixed by #80
Closed

Ambiguous language about specifying claims #63

selfissued opened this issue Aug 25, 2024 · 4 comments · Fixed by #80
Assignees
Labels
editorial This item is editorial in nature. pr exists A Pull Request exists to address this issue.

Comments

@selfissued
Copy link
Collaborator

https://www.w3.org/TR/2024/WD-controller-document-20240817/#assertion
In "The assertionMethod verification relationship is used to specify how the controller is expected to express claims, such as for the purposes of issuing a verifiable credential.", it's not clear what it means to "specify how the controller is expected to express claims". A normal reading of the English text in this context might lead one to believe this is saying something about the JWT claims that might be contained in a credential, but I doubt that's what it's about. What is it about?

@msporny
Copy link
Member

msporny commented Aug 26, 2024

The sentence is meant to suggest that the cryptographic method is used to verify whether an entity issued a set of claims/statements or not and is not specific to JWTs. It applies to any securing mechanism used to protect assertions made by an issuer.

Please suggest some language.

@msporny msporny added the editorial This item is editorial in nature. label Aug 26, 2024
@dlongley
Copy link
Contributor

This issue seems to be asking for the inverse of what some other recently filed issues are asking for.

We have two issues that are asking for more text for things that are out of scope for the controller document:

#63 (this one)
#64

And issues that are asking for less because those things are out of scope for the controller document:

#60
#61

We might want some generic language that indicates something like "Verification relationships allow controllers to authorize verification methods for use for specific purposes, but how specific use cases are achieved such as authenticating to a website, accessing a resource using a capability, encrypting data, or expressing assertions or claims is out of scope for this specification."

For this particular issue, we could change this sentence:

"The assertionMethod verification relationship is used to specify how the controller is expected to express claims, such as for the purposes of issuing a verifiable credential."

To:

"The assertionMethod verification relationship is used to specify verification methods that a controller authorizes for use when expressing assertions or claims, such as in verifiable credentials."

I think this would be more accurate.

@selfissued
Copy link
Collaborator Author

@dlongley's suggested wording works for me.

@msporny msporny added the ready for pr This issue is ready to have a pull request created for it. label Aug 26, 2024
@selfissued
Copy link
Collaborator Author

I agree that this is ready for a PR.

@selfissued selfissued self-assigned this Aug 29, 2024
@selfissued selfissued added pr exists A Pull Request exists to address this issue. and removed ready for pr This issue is ready to have a pull request created for it. labels Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editorial This item is editorial in nature. pr exists A Pull Request exists to address this issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants