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

Bug 27562 - Odd wording of section "2.7. Javascript Object Signing and Encryption (JOSE)" #48

Closed
mwatson2 opened this issue May 23, 2016 · 3 comments
Assignees

Comments

@mwatson2
Copy link
Collaborator

mwatson2 commented May 23, 2016

Bug 27562:

2.7. Javascript Object Signing and Encryption (JOSE) ¶

A web application wishes to make use of the structures and format of messages defined by the IETF Javascript Object Signing and Encryption (JOSE) Working Group. The web application wishes to manipulate public keys encoded in the JSON key format (JWK), messages that have been integrity protected using digital signatures or MACs (JWS), or that have been encrypted (JWE).

The style of this paragraph doesn't fit with the preceding ones, and not entirely sure how to parse it. Whereas the preceding sections describe concrete use cases, this one seems to be talking about the emotional state of a web application...

@mwatson2
Copy link
Collaborator Author

The style is not all that out-of-line with preceding use-cases. They could all do with some improved wording.

@bdhess
Copy link
Contributor

bdhess commented Jun 7, 2016

I took a stab at cleaning this up in #108. I left the "emotional state of the web application" stuff intact, since discussing it in terms of the web application conveniently sidesteps questions about who the decision-making actor is (it's not always the web application developer either).

@hhalpin
Copy link

hhalpin commented Jun 20, 2016

Looks good to me @bdhess

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

No branches or pull requests

3 participants