It has always been an early goal of this protocol to avoid user lock-in on specific applications or providers. The protocol intentionally gives the profile key precedence over the URI (see 1.3) to bind a profile to the cryptographic key rather than the URI. This degrades the profile provider to a mere publishing service which can be swapped for a different provider.
However, the current version 0.3 of SPXP does not provide a guided migration process or give enough hints for implementors how to discover the new profile URI of a relocated profile.
The original Change Request CR-001_ProfileRelocation can be found here.
Profile Relocation
It has always been an early goal of this protocol to avoid user lock-in on specific applications or providers. The protocol intentionally gives the profile key precedence over the URI (see 1.3) to bind a profile to the cryptographic key rather than the URI. This degrades the profile provider to a mere publishing service which can be swapped for a different provider.
However, the current version 0.3 of SPXP does not provide a guided migration process or give enough hints for implementors how to discover the new profile URI of a relocated profile.
The original Change Request CR-001_ProfileRelocation can be found here.