specs
specs copied to clipboard
reconciliation-api
Specifications of the reconciliation API
It would be helpful to add a Reconciliation Candidates response example in JSON, as in the other sections. *Example below copied from OpenRefine Wiki* The response is a JSON literal...
At the moment, the names and descriptions represented in the reconciliation queries and responses do not come with any language information. For natively multilingual data sources (such as Wikidata) it...
Now that the suggest services return descriptions (which was not the case a few years ago), we could consider removing the flyout service which is redundant with these descriptions. Flyout...
The current specification requires the view template to only have an `{{id}}` placeholder. However, for services that support multiple types, the view template could be substantially different for each type....
Add a section that describes rate limiting, referencing https://tools.ietf.org/id/draft-polli-ratelimit-headers-00.html and other similar specifications.
If a service changes its endpoint URL, but clients have already fetched its manifest at the old URL, they might keep sending queries via POST to the endpoint. Since there...
Citing @osma at https://github.com/NatLibFi/Annif/issues/338 > it would make the implementation easier if there was an OpenAPI (Swagger) spec for the API available I am not familiar with OpenAPI but it...
It is more natural in a REST API to submit a JSON payload as a POST query with `Content-Type: application/json` rather than to URL-encode it in a `queries=` parameter as...
Use case: suppose I reconcile a column to a particular type, and then I use the entity suggest API to manually select matches for some cells. At the moment the...
In the [lobid-gnd reconciliation service](https://lobid.org/gnd/reconcile) we have an `extends.property_settings` item to `select` if a property should be added as an ID or a label. This only makes sense for non-reconciled...
Metadata
Owner
Metadata
Specifications of the reconciliation API