equivalentId or canonicalId are DID Document resolution metadata properties used for indicating equivalent forms of a DID and which one is canonical. The network part of a did:tz DID is optional and defaults to mainnet. Should the Tezos DID Method specification support this usage, to say that with or without mainnet is equivalent, and one of the forms is canonical?
Some excerpts from the above linked sections from DID Core and how it relates to DID Methods:
A DID Method can define different forms of a DID that are logically equivalent.
[...] the canonicalId value is defined by the DID Method to be the canonical ID for the DID subject in the scope of the containing DID document.
A conforming DID Method specification MUST guarantee that each equivalentId value is logically equivalent to the id property value.
A conforming DID Method specification MUST guarantee that the canonicalId value is logically equivalent to the id property value.
equivalentId or canonicalId are DID Document resolution metadata properties used for indicating equivalent forms of a DID and which one is canonical. The network part of a
did:tzDID is optional and defaults tomainnet. Should the Tezos DID Method specification support this usage, to say that with or withoutmainnetis equivalent, and one of the forms is canonical?Some excerpts from the above linked sections from DID Core and how it relates to DID Methods: