Enable users to migrate/copy their accounts to another server

Develop an API/workflow recommendation for users to be able to securely migrate or copy their account (and potentially all of its data) to another Solid server or compatible service provider.

Considerations:

• What should the workflow be, for authorizing the copying (via "pull") of the data to another server?
• What should the UI look like, for selecting which data / containers the user wants copied?
• The old server/solid provider should be able to redirect (via HTTP 301, etc) links to the old account's data to the new one. See http://www.w3.org/TR/cooluris/ etc.
  • This policy should be encouraged, but will ultimately be determined by the service provider. Need to discuss how the service provider should signal this in their terms of service.

See also:

• The current process of transferring domains to a new registrar
• https://www.w3.org/Payments/IG/wiki/ProposalsQ42015/VerifiableClaimsTaskForce (mentioned by @mediaprophet)
• WebDAV's COPY verb?

(Discussion of moving/migrating an account extracted from the original solid-spec account export issue).

Start by reviewing the extracted account export issue (#68) and the references to WebDAV COPY, HTTP 301 redirects, and the Cool URIs guidance. Map the proposed authorization, data-selection UI, migration, and redirect considerations into a documented API/workflow recommendation. Done means the specification clearly addresses these considerations and the provider-policy question.