Fabian Steeg

Results 84 comments of Fabian Steeg
trafficstars

Marking as draft, needs URL support for the main schema. See https://github.com/metafacture/metafacture-core/issues/443#issuecomment-1262023148.

We briefly touched this issue in [yesterday's meeting](http://etherpad.lobid.org/p/reconciliation-june-2021), discussing if an HTTP status code like 429 (Too Many Requests) could be a reasonable way for services to communicate to clients...

Trying to summarize our discussion of this in our [May meeting](https://etherpad.lobid.org/p/reconciliation-may-2022): - Communicating limits in an HTML page (as mentioned in https://github.com/reconciliation-api/specs/issues/66#issuecomment-1100794188) has the downside that a client could not...

@agnescameron: I don't think I fully understand your use case yet, but did I mention Cocoda (https://coli-conc.gbv.de/cocoda/) in the meeting? I have not worked with it myself, but it uses...

> we get an pica binary dump and need to transform this to picaxml I would have expected that we will process the dump with a different decoder (`decode-pica`?) instead...

This came up in [our discussion](https://etherpad.lobid.org/p/reconciliation-may-2023#L74) of [SSSOM](https://mapping-commons.github.io/sssom/spec/), a spec for ontology mappings, which in addition to the plain mapping uses a `predicate_id` e.g. `skos:exactMatch` and a `mapping_justification` e.g. `...

> Historically, the goal has been exact matches only. I was thinking about these different match relations not on the entity level, but on a property level. Basically, for the...

If I understand this correctly it seems to be very much like our [data extension](https://reconciliation-api.github.io/specs/draft/#data-extension-service) functionality. I think that clients who want to get more information about candidates (for custom...

Right, I missed that part in your example. Perhaps this could be done using [property proposals](https://reconciliation-api.github.io/specs/draft/#data-extension-property-proposals), so something like this: `GET /extend/propose?type=location` Would return this: ```json { "type": "location", "properties":...

Right, thanks for explaining, now I see how that could be done in a reasonable way. We should keep that in mind for when we have other pagination use cases,...