Repository navigation
docs(wallets): refresh walt.id capability entry - #17
Merged
Merged
Conversation
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
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.
Summary
Refresh walt.id's existing capability entry (portal 90) so consortium members can find the current Android/iOS SDKs and understand the scope of proximity and demo attestation support.
What Changed
Caveats and Follow-Ups
The controlled standards vocabulary is unchanged; OpenID4VCI 1.0 and OpenID4VP 1.0 are described in the free-text field. Capability declarations, trusted-list membership, and conformance results remain separate.
The capability wording follows the current mobile SDK and ITB runner documentation.