Add trait: DID rotation

[jceb]

Functionality:

• DID Rotation
  • Rotating/switching from DID to another DID without losing data
  • "Rotate to", did:ebsi → did:xyz
  • "Rotate from"

More information is required.

[fabianekc]

here a more verbose description of DID Rotation:

Description: DID Rotation refers to the process of transitioning from one DID Method to another while preserving continuity of identity and optionally associated cryptographic proofs.

Motivation: Updating and switching DID methods allows to remain aligned with the latest technological advancements and best practices, guaranteeing optimal performance and compatibility. Additionally, it provides a mechanism to avoid vendor lock-in by enabling entities to seamlessly update or replace their DIDs and associated service endpoints without dependency on a single provider or infrastructure.

Types:

• Rotate from: does a DID method support through the available infrastructure (registrar, trust registry, resolver) to be the source of a DID Rotation, i.e., update this DID so that it resolves to another method; example: resolve did:oyd:123 to did:ebsi:456
• Rotate to: does a DID method support to be the target of a DID rotation, i.e., allow a new DID to have as predecessor/ancestor a DID from another method; example: did:ebsi:456 has a history that points to did:oyd:123

[peacekeeper]

Is this really an independent trait? I thought DID Rotation is possible whenever:

1. old DID is updatable
2. old DID is deactivatable
3. new DID is updatable
4. both DIDs support the alsoKnownAs property

But I guess there's nothing wrong with having a trait that is dependent on or linked to other traits.

[fabianekc]

I see the implementation with the 4 requirements as necessary but not sufficient to provide DID Rotation because it also requires tweaks in the resolution process (at least it does for did:oyd). It might even be possible to also implement DID Rotation in another way, therefore I described it from a result perspective.