Fabian Steeg

Quoting myself from https://github.com/metafacture/metafacture-core/issues/464#issuecomment-1295129003: > For proceeding here, I suggest we close this issue and keep using that new module (JsonApiReader) for some more workflows in OERSI, and consider if...

> Supporting URLs for the main schema [...] brings in some additional aspects to consider (like caching to avoid an HTTP request for every document, testing without introducing remote requests...

See https://github.com/metafacture/metafacture-core/issues/443#issuecomment-1413396013 for a summary of the new changes.

> In our case another param would be helpful: the language associated with the query. For instance in our database we have a lot of transliterated names (originally in Tibetan,...

> The server has two person items Q12 `John Philips (en)` and Q23 `Иван Филипов (bg) = John Philips (en)` [...] What's the `Content-Language` of this document? It's neither `bg`...

> The property suggest service already supports a type filtering (such that you can propose properties that are relevant for a given type), but even that is undocumented in our...

Resolved with #166 (PR for #150, which was a duplicate of this), closing.

Is this resolved with the new `conditions`, `match_quantifier`, and `match_qualifier`? See https://reconciliation-api.github.io/specs/draft/#structure-of-a-reconciliation-query

This seem related to (or even a duplicate of) #69.

I think this is addressed with #131: `matchQualifier`, see https://reconciliation-api.github.io/specs/draft/#structure-of-a-reconciliation-query: > [...] like spatial matching with geo data (e.g. containment search with "schema:containsPlace" etc.)