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
We need to refactor fixtures for implementers #32
Comments
I am asserting that no PRs will make it in until we have at least one example of an implementer fixture that shows how to do this... and its going to be dangerous to skip over it. |
The issue was discussed in a meeting on 2021-03-30
View the transcript7.3. We need to refactor fixtures for implementersSee github issue did-test-suite#32. Orie Steele: Same point Markus and others have raised. Essentially, the structure of the test suites is not set in stone or finalized or working. Brent Zundel: This one is unassigned Manu Sporny: I will take it
|
I have raised PR #52 to address this issue. Specifically, there is now an |
The issue was discussed in a meeting on 2021-04-06
View the transcript7.7. need clear instructions for implementersSee github issue did-test-suite#33, did-test-suite#32. Markus Sabadello: also related to refactoring Daniel Burnett: pretty straightforward Markus Sabadello: last two are about sections of the spec which are still missing |
This is done once PR #55 is merged. |
PR #55 has been merged, closing. |
We need to clearly show the difference between abstract and concrete representations.
there should be did document data models for both abstract and concrete examples
The text was updated successfully, but these errors were encountered: