As part of our work on the reconciliation spec, we should provide a version of our GND reconciliation service that conforms to the current 1.0-draft version of the spec. As discussed in the last meeting of the reconciliation community group, we should use that as an opportunity to set up a migration guide for reconciliation service providers that want to migrate their services to the latest version of the spec.
To implement this, I think it would make sense to adopt the version negotiation approach suggested in reconciliation-api/specs#78 (comment), i.e. if we get reconciliation requests with an Accept: application/reconciliation.v1+json header, we dispatch them to the new service. This new service could be implemented in a separate repo and use the same tech stack as our new UI prototype.
As part of our work on the reconciliation spec, we should provide a version of our GND reconciliation service that conforms to the current 1.0-draft version of the spec. As discussed in the last meeting of the reconciliation community group, we should use that as an opportunity to set up a migration guide for reconciliation service providers that want to migrate their services to the latest version of the spec.
To implement this, I think it would make sense to adopt the version negotiation approach suggested in reconciliation-api/specs#78 (comment), i.e. if we get reconciliation requests with an
Accept: application/reconciliation.v1+jsonheader, we dispatch them to the new service. This new service could be implemented in a separate repo and use the same tech stack as our new UI prototype.