-
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 mechanism to retrieve historical status list information. #112
Conversation
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.
Accepting this -- but haven't put much thought into the side effects (privacy considerations, so on) yet.
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.
thanks for adding this. it would be great to have an example query.
index.html
Outdated
a valid URL-encoded [[XMLSCHEMA11-2]] dateTimeStamp string value. The result of | ||
dereferencing such a timestamped URL MUST be a status list credential containing | ||
either the status list as it existed at the given point in time, or a | ||
<a href="#STATUS_RETRIEVAL_ERROR">STATUS_RETRIEVAL_ERROR</a>. |
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.
I would consider adding a sentence that says something like...
"Providing such a mechanism to dereference the status list as of a particular point in time lends itself to allowing for the functionality of determining as precise as possible timestamps of status changes, at the issuers discretion"
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.
Done in 804df0e.
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.
👍
index.html
Outdated
dereferencing such a timestamped URL MUST be a status list credential containing | ||
either the status list as it existed at the given point in time, or a | ||
<a href="#STATUS_RETRIEVAL_ERROR">STATUS_RETRIEVAL_ERROR</a>. |
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.
dereferencing such a timestamped URL MUST be a status list credential containing | |
either the status list as it existed at the given point in time, or a | |
<a href="#STATUS_RETRIEVAL_ERROR">STATUS_RETRIEVAL_ERROR</a>. | |
dereferencing such a timestamp-parameterized URL MUST be a status list credential | |
containing either the status list as it existed at the given point in time, or a | |
<a href="#STATUS_RETRIEVAL_ERROR">STATUS_RETRIEVAL_ERROR</a>. |
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.
or
dereferencing such a timestamped URL MUST be a status list credential containing | |
either the status list as it existed at the given point in time, or a | |
<a href="#STATUS_RETRIEVAL_ERROR">STATUS_RETRIEVAL_ERROR</a>. | |
dereferencing such a timestamp-parameterized URL MUST be either a status list | |
credential containing the status list as it existed at the given point in time, | |
or a <a href="#STATUS_RETRIEVAL_ERROR">STATUS_RETRIEVAL_ERROR</a>. |
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.
Fixed in dfa5e31.
The issue was discussed in a meeting on 2024-01-10
View the transcript3.3. Add mechanism to retrieve historical status list information. (pr vc-bitstring-status-list#112)See github pull request vc-bitstring-status-list#112. Manu Sporny: request to retrieve historical status list. David Chadwick: We would like implementer feedback, but we shouldn't have a spec that has multiple options on the reply - that might be confusing to implementers. Select one option for the reply (when you don't have one, we should say you MUST/SHOULD return an error) vs. "it's up to implementers". Manu Sporny: we can make this change. |
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
19f6160
to
e41c768
Compare
Normative, multiple reviews, changes requested and made, no objections, merging. |
This PR is an attempt to address issue #94 by adding an optional normative mechanism to retrieve historical status list information.
Preview | Diff