Thanks for your review, Roman. My responses are inline below, prefixed by
"Mike>".
The proposed resolutions below are incorporated in
https://github.com/oauth-wg/draft-ietf-oauth-resource-metadata/pull/58. Please
let me know if you'd like to see any changes before we apply them.
-Origina
Thanks for your review, Mike. My replies are inline below, prefixed by "mbj>".
The proposed resolutions below are incorporated in
https://github.com/oauth-wg/draft-ietf-oauth-resource-metadata/pull/57. Please
let me know if you'd like to see any changes before we apply them.
-Original Mes
Roman Danyliw has entered the following ballot position for
draft-ietf-oauth-resource-metadata-10: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please r
I read over the W3C issue but it is not clear to me why using "typ" is an
issue. I do see the issue that there is some possible name collision -- so
perhaps someone does not get their first choice?
A design objective of what became JOSE was to use JSON so that we did not
need to cram a bunch of me
Thanks for the additional explanation Dick,
The explicit typing construct is RECOMMENDED and not a MUST because there
exist perfectly legitimate cases where the construct is neither needed nor
appropriate. See https://github.com/w3c/vc-jose-cose/issues/282 for one
example where, amidst the noise i
