-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add "at risk" marker noting bitstring format might change in CR. #119
Conversation
@@ -662,6 +662,19 @@ <h2>Algorithms</h2> | |||
and validate status lists as described by this document. | |||
</p> | |||
|
|||
<p class="issue atrisk" | |||
title="Attempting alignment with IETF Token Status List specification"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Attempting alignment with IETF OAuth Status List specification"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like they're going to change the name to "Token Status List" based on their issue tracker oauth-wg/draft-ietf-oauth-status-list#77 (comment)
The issue was discussed in a meeting on 2024-01-10
View the transcript3.5. Add "at risk" marker noting bitstring format might change in CR. (pr vc-bitstring-status-list#119)See github pull request vc-bitstring-status-list#119. Manu Sporny: adds an at risk marker to the bitstring format.
|
Co-authored-by: Ted Thibodeau Jr <[email protected]>
f2c0bc4
to
078db10
Compare
Editorial, multiple reviews, changes requested and made, no objections, merging. |
This PR is an attempt to address issue #93 by adding an at risk issue marker to note that the bitstring format might change during the Candidate Recommendation phase if there is implementer interest to align more closely with the IETF Token Status List specification.
Preview | Diff