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

Add at risk issue marker regarding multibit status entries. #123

Merged
merged 2 commits into from
Jan 13, 2024

Conversation

msporny
Copy link
Member

@msporny msporny commented Dec 30, 2023

This PR is an attempt at addressing some comments in issue #73 by marking the multibit status entry feature as at risk. The PR makes it such that implementers don't have to implement the feature to have a conforming processor, but allows implementations that need the feature to implement it in an interoperable fashion.


Preview | Diff

CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
@iherman
Copy link
Member

iherman commented Jan 10, 2024

The issue was discussed in a meeting on 2024-01-10

  • no resolutions were taken
View the transcript

3.7. Add at risk issue marker regarding multibit status entries. (pr vc-bitstring-status-list#123)

See github pull request vc-bitstring-status-list#123.

Manu Sporny: adding an at risk marker to the multiple status list feature.
… if there are insufficient implementors of this feature it will be removed.
… we will need a test suite for it as well as implementations.

Chris Abernethy: I believe we intend to implement it.

Base automatically changed from msporny-conformance to main January 13, 2024 15:55
@msporny msporny force-pushed the msporny-statusMessage branch from 2d24d4a to 53b0466 Compare January 13, 2024 21:21
@msporny
Copy link
Member Author

msporny commented Jan 13, 2024

Normative, multiple reviews, changes requested and made, no objections, merging.

@msporny msporny merged commit f812b4b into main Jan 13, 2024
1 of 2 checks passed
@msporny msporny deleted the msporny-statusMessage branch January 13, 2024 21:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants