docs: explain indexAllocator for status updates#625
Draft
PatStLouis wants to merge 4 commits into
Draft
Conversation
Expand OpenAPI description and Update Status prose: why index bookkeeping exists, when multiple allocators apply, linkage to issuance, and that values are implementation-defined. Fix UpdateCredentialStatusRequest example JSON (boolean true). Closes #594. Signed-off-by: Patrick St-Louis <patrick.st-louis@opsecid.ca> Made-with: Cursor
TallTed
reviewed
Apr 14, 2026
msporny
reviewed
Apr 14, 2026
PatStLouis
marked this pull request as draft
April 14, 2026 19:59
PatStLouis
marked this pull request as draft
April 14, 2026 19:59
dlongley
reviewed
Apr 27, 2026
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Manu Sporny <msporny@digitalbazaar.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
TallTed
reviewed
Apr 28, 2026
| the Verifiable Credentials they issue. Issuer software is expected to ensure | ||
| that it does not overallocate or misallocate status metadata (e.g., status | ||
| lists or list indexes), as this overallocated, misallocated, or unused | ||
| information can create privacy harms both to holders and issuers of Verifiable |
Member
There was a problem hiding this comment.
Suggested change
| information can create privacy harms both to holders and issuers of Verifiable | |
| information can create privacy harms to both holders and issuers of Verifiable |
TallTed
reviewed
Apr 28, 2026
| that it does not overallocate or misallocate status metadata (e.g., status | ||
| lists or list indexes), as this overallocated, misallocated, or unused | ||
| information can create privacy harms both to holders and issuers of Verifiable | ||
| Credentials. In architectures that are highly available, horizontally scalable, |
Member
There was a problem hiding this comment.
Suggested change
| Credentials. In architectures that are highly available, horizontally scalable, | |
| Credentials. In architectures that are highly available, horizontally scaled, |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Expand OpenAPI description and Update Status prose: why index bookkeeping exists, when multiple allocators apply, linkage to issuance, and that values are implementation-defined.
Fix UpdateCredentialStatusRequest example JSON (boolean true).
Closes #594.
💥 Error: 500 Internal Server Error 💥
PR Preview failed to build. (Last tried on Apr 28, 2026, 7:32 PM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one:
🚨 Spec Generator - Spec Generator is the web service used to build bikeshed/ReSpec specs
🔗 Related URL
Error output:
This seems to be an issue with the Spec Generator service. PR Preview doesn't manage this service and so has no control over it. If you've identified an issue with it, you can report the issue to the maintainers of Spec Generator directly. Please be courteous. Thank you!
If you don't have enough information above to solve the error by yourself or if the issue doesn't seem related to Spec Generator, you can file an issue with PR Preview.