DIDs: alsoKnownAs property

[nikolockenvitz]

The alsoKnownAs property has been added to the DID spec recently.
It's basically a string array of some identifiers (URIs) by which the DID subject can also be identified. (see the corresponding section in w3c did-core)

I was wondering whether it is planned to include that in daf-ethr-did too?

Possible implementation
Could be done building upon the setAttribute method of the ethr-did-registry, e.g. did/aka + hex encoded string.
Similar to the other methods in daf-ethr-dids identity-provider (beta-branch) it would just be something like async addAlsoKnownAs({ identity, service, options }: { identity: IIdentity; alsoKnownAs: string; options?: any }, context: IContext): Promise<any>

What's your opinion on that?
(Should I also mention that in ethr-did-resolver somehow?)

Do you have an estimation when the beta-branch will be merged? (Thinking about whether it makes sense to include that in the current version or just go for beta-branch).

EDIT: maybe someone could remove the bug label and add something like feature or feature-request...

[mirceanis]

Thanks for flagging this.
That sounds like a good proposal and it would be fairly easy to add to daf-ethr-did.
However, the resolver would also need to be updated to support this new attribute type.
Let's agree on a format for the did/aka entries in ethr-did spec first and then it would need to be implemented in daf and ethr-did resolver simultaneously for it to work.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[nikolockenvitz]

Still an open issue that should be worked on IMO

[mirceanis]

Still an open issue that should be worked on IMO

Yes, it is. We're waiting for the DID spec to become a bit more stable before committing to this.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.