-
Notifications
You must be signed in to change notification settings - Fork 6
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
Updating ABNF for DIDs #57
Labels
Comments
Christopher, I could not agree more. This is my #1 priority as a spec
editor. If we cover nothing else at Rebooting the Web of Trust next month
(March 1-3), I want to nail down the PRs around the ABNF.
I'm happy to discuss on this thread between now and then.
=Drummond
…On Fri, Feb 8, 2019 at 11:00 AM Christopher Allen ***@***.***> wrote:
There are a variety of issues related to the ABNF of DIDs that is becoming
critical path as new people from W3C and IETF communities join our meetings
for DID discussions, and language and resolution and dereferencing. These
issues cause problems for those who already have deep understanding of this
area from other standards.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#57>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADLkTcno6thDCeo8_Xjmvuqj9lCl1pLSks5vLcldgaJpZM4axHAC>
.
|
@dmitrizagidulin Created a PR to move this conversation forward w3c-ccg/did-spec#168 Please comment there. We will also be discussing this on the next CCG call. |
I think this can be closed now that w3c-ccg/did-spec#189 has been merged? |
Closing per CCG call on July 2, 2019. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
There are a variety of issues related to the ABNF of DIDs that is becoming critical path as new people from W3C and IETF communities join our meetings for DID discussions, and language and resolution and dereferencing. These issues cause problems for those who already have deep understanding of this area from other standards.
The text was updated successfully, but these errors were encountered: