So far, the primary key for crawled responses is the URL that was requested, split into the two fields backend + path (e.g. https://earthengine.openeo.org/v0.4 + /collections).
The primary key for individual backend instances is backend (e.g. https://earthengine.openeo.org/v0.4).
However, backend could be represented by service + version, where service is the URL under which the well-known document resides and version the api_version field of that well-known document (e.g. https://earthengine.openeo.org + v0.4.2).
But again, service could be represented by provider, e.g. Google Earth Engine or GEE.
provider + version + path would be the most abstract form and thus also the most robust -- think URL changes.
Just writing down some thoughts I just had
So far, the primary key for crawled responses is the URL that was requested, split into the two fields
backend+path(e.g.https://earthengine.openeo.org/v0.4+/collections).The primary key for individual backend instances is
backend(e.g.https://earthengine.openeo.org/v0.4).However,
backendcould be represented byservice+version, whereserviceis the URL under which the well-known document resides andversiontheapi_versionfield of that well-known document (e.g.https://earthengine.openeo.org+v0.4.2).But again,
servicecould be represented byprovider, e.g.Google Earth EngineorGEE.provider+version+pathwould be the most abstract form and thus also the most robust -- think URL changes.