Change working group to DCP #307
Merged
Conversation
This file contains 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
As per adoption call on mailing list: https://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/Week-of-Mon-20240415/000259.html Also update README to link to somewhere other versions (like implementer's drafts) of the specification can be found. (I chose to link to this page rather than linking directly to the latest implementer's draft etc so that we have fewer places listing the same info so that we have fewer places to try and keep up to date.)
selfissued
approved these changes
Apr 30, 2024
paulbastian
approved these changes
May 1, 2024
pmhsfelix
approved these changes
May 2, 2024
Sakurann
reviewed
May 2, 2024
| @@ -5,6 +5,8 @@ Specification to allow holders to request issuance of credentials and issuers to | |||
|
|
|||
| The current WG-Draft version is built automatically from the master branch and can be accessed at: https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-wg-draft.html | |||
|
|
|||
| Other versions of the spec can be accessed at: https://openid.net/sg/openid4vc/specifications/ | |||
There was a problem hiding this comment.
Do we want to clarify this is a WG's draft vs editors' draft?
There was a problem hiding this comment.
Not entirely sure what you're suggesting we change? line 6 does say that it's a working group draft.
c2bo
approved these changes
May 7, 2024
paulbastian
pushed a commit
that referenced
this pull request
May 14, 2024
4 approvals, open for a week. needed change for administrative reasons As per adoption call on mailing list: https://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/Week-of-Mon-20240415/000259.html Also update README to link to somewhere other versions (like implementer's drafts) of the specification can be found. (I chose to link to this page rather than linking directly to the latest implementer's draft etc so that we have fewer places listing the same info so that we have fewer places to try and keep up to date.)
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.
As per adoption call on mailing list:
https://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/Week-of-Mon-20240415/000259.html
Also update README to link to somewhere other versions (like implementer's drafts) of the specification can be found. (I chose to link to this page rather than linking directly to the latest implementer's draft etc so that we have fewer places listing the same info so that we have fewer places to try and keep up to date.)