google
Add enpoint as a parameter for more generic adapters
In most existing DTP adapters, there is exactly one provider for the underlying API. In contrast, the Mastodon and Solid adapters currently seem to be the only adapters for which an endpoint can be freely chosen. They are currently not supported by the UI and their usage is currently unclear (see https://github.com/google/data-transfer-project/issues/785). They are also lacking an authentication adapter.
Beyond Mastodon and Solid, scenarios in which an API might be supported by a variety of service providers can be considered at least as equally important for Data Portability (and hence DTP?) as the "single-service-provider" adapters. This way a bigger quantity of service providers could be supported without the need of implementing an adapter for each specific provider (or even software). Accordingly, we'd propose the following extensions and modifications to DTP (some of which might need further/deeper discussion):
- allow choosing an endpoint in the UI
- extend some classes of the API with parameters like
path,endpointorport
This could then be used as a basis to implement a generic adapter for a specific standardized API like IMAP, CalDAV or JMAP (independent of the underlying software).
Do you have a general opinion on this?
