You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to share my observations based on the testing Steve Apps ([email protected]) has done with a test network using the module.
The context property MUST be @context, not context
The context https://www.w3.org/ns/did/v1 does not provide definitions for the following terms:
a. EcdsaSecp256k1VerificationKey2019
b. publicKeyMultibase
The following properties should either be removed or changed.
a. controller property at the top level should probably be the DID of this document. It certainly is not valid as an empty array. If it is empty, it should not be present. "If present, the value MUST be a string or a set of strings that conform to the rules in § 3.1 DID Syntax." https://www.w3.org/TR/did-core/#did-controller
b. controller property on the verification method maps, through the DID context, to https://w3id.org/security#controller This may or may not be the right definition for EcdsaSecp256k1VerificationKey2019
After JSON-LD processing (after updating "@context" and removing the non-conformant properties), we are left with the following,
Note that because publicKeyMultibase is not in the JSON-LD context, it gets dropped. This is, unfortunately, the most important piece of data in the document.
The text was updated successfully, but these errors were encountered:
I'd like to share my observations based on the testing Steve Apps ([email protected]) has done with a test network using the module.
The
context
property MUST be@context
, notcontext
The context
https://www.w3.org/ns/did/v1
does not provide definitions for the following terms:a.
EcdsaSecp256k1VerificationKey2019
b.
publicKeyMultibase
The following properties should not be present
a.
service
-- "If present, the value of the serviceEndpoint property MUST be a string, a map, or a set composed of one or more strings and/or maps." https://www.w3.org/TR/did-core/#servicesb.
assertionMethod
-- "If present, the associated value MUST be a set of one or more verification methods."https://www.w3.org/TR/did-core/#assertion"c.
keyAgreement
-- "If present, the associated value MUST be a set of one or more verification methods." https://www.w3.org/TR/did-core/#key-agreementd.
capabilityInvocation
-- "If present, the associated value MUST be a set of one or more verification methods." https://www.w3.org/TR/did-core/#capability-invocatione.
capabilityDelegation
-- "If present, the associated value MUST be a set of one or more verification methods." https://www.w3.org/TR/did-core/#capability-delegationThe following properties should either be removed or changed.
a.
controller
property at the top level should probably be the DID of this document. It certainly is not valid as an empty array. If it is empty, it should not be present. "If present, the value MUST be a string or a set of strings that conform to the rules in § 3.1 DID Syntax." https://www.w3.org/TR/did-core/#did-controllerb.
controller
property on the verification method maps, through the DID context, tohttps://w3id.org/security#controller
This may or may not be the right definition forEcdsaSecp256k1VerificationKey2019
After JSON-LD processing (after updating "@context" and removing the non-conformant properties), we are left with the following,
Note that because publicKeyMultibase is not in the JSON-LD context, it gets dropped. This is, unfortunately, the most important piece of data in the document.
The text was updated successfully, but these errors were encountered: