Add multibase datatype definition

[msporny]

This PR addresses #162 (comment) by defining the multibase datatype as we recently did for cryptosuiteString. It then updates proofValue's range to be multibase.

@iherman, we'll need to define the datatype in the vocabulary.yml file as well, but I didn't see how that was done for cryptosuiteString yet -- perhaps that still needs to be merged?

---

Preview | Diff

[TallTed]

small language tweaks

[iherman]

@iherman, we'll need to define the datatype in the vocabulary.yml file as well, but I didn't see how that was done for cryptosuiteString yet -- perhaps that still needs to be merged?

Yes, that is part of #171 .

(would be good to merge that one, to avoid unnecessary issues...)

[iherman]

This PR addresses #162 (comment) by defining the multibase datatype as we recently did for cryptosuiteString. It then updates proofValue's range to be multibase.

Forgive me if my question reveals my missing knowledge, but shouldn't this be the range of secretKeyMultibase and publicKeyMultibase, too? At this moment, those two properties have simply xsd:string as their range.

[msporny]

Forgive me if my question reveals my missing knowledge, but shouldn't this be the range of secretKeyMultibase and publicKeyMultibase, too? At this moment, those two properties have simply xsd:string as their range.

Yes, good catch, I'll make that change in a future revision to this PR.

[msporny]

@iherman wrote:

Forgive me if my question reveals my missing knowledge, but shouldn't this be the range of secretKeyMultibase and publicKeyMultibase, too? At this moment, those two properties have simply xsd:string as their range.

Done in 78c30c0.

[msporny]

Normative, multiple reviews, changes requested and made, no objections, merging.