This repository has been archived by the owner on Oct 29, 2019. It is now read-only.
DID Test Suite and untestable normative statements #228
Assignees
Labels
clarify
There is consensus, but the spec needs clarifying
Comments
|
please note has developed should be is developing. Literally just started this morning! Big questions to solve is how to test individual DiD implementations. We are using a binary that takes command line arguments for the other tests. |
|
Action from 6/11/2019: create an github issue against DID spec. Create spreadsheet, mark ones people want to keep as normative |
|
I imagine #210 partially (but not fully?) addressed this issue? |
|
Closing because we've moved it to the DID WG did-spec repo. https://github.com/w3c/did-spec |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Digital Bazaar has developed a DID Test Suite and identified 83 untestable normative statements. Let's discuss on the call for awareness and figure out if there's any tracking or work we need to do in advance of the DID WG.
https://lists.w3.org/Archives/Public/public-credentials/2019Jun/0008.html
The text was updated successfully, but these errors were encountered: