Normative statements checklist: 7. Resolution about did-test-suite

[peacekeeper]

Also assigning @shigeya , since I did section 7.1 (DID Resolution #29) and section 7.2 (DID URL Dereferencing #30), while he did section 7.3 (Metadata Structure #31).

[msporny]

Since I don't have write permissio to this repository, I can't check tem,

I have checked the Metadata tests and did an additional audit. All checked items are implemented, non-checked items are human-only tests.

[msporny]

PR #86 has been merged. Marking as pending close.

[peacekeeper]

Related: #53

[shigeya]

Since I don't have write permissio to this repository, I can't check tem, so... for 7.3 Metadata Structure, all but following two items are done:

All metadata property definitions registered in the DID Specification Registries [DID-SPEC-REGISTRIES] MUST define the value type, including any additional formats or restrictions to that value (for example, a string formatted as a date or as a decimal integer).

Following entry is RECOMMENDED so testing is not mandatory.

It is RECOMMENDED that property definitions use strings for values.

[peacekeeper]

Update: After merging #86, all statements in 7.1 and 7.2 should have tests, except MAY and SHOULD statements, as well as the following three MUST statements that we decided don't need tests:

• A conforming DID Method specification MUST guarantee that each equivalentId value is logically equivalent to the id property value.
• equivalentId is a much stronger form of equivalence than alsoKnownAs because the equivalence MUST be guaranteed by the governing DID method.
• A conforming DID Method specification MUST guarantee that the canonicalId value is logically equivalent to the id property value.