Repository navigation
Replies: 1 comment 3 replies
There isn't much that is planned in the reconciliation API itself for keeping track of such events. In OpenRefine, users learn that reconciled data can get stale, and that they might need to reconcile again if they wait too much before using it. If I had to imagine a way to stay in sync, I'd probably try to do it based on existing LOD standards. I don't know if there are good ways to listen to updates of a collection of RDF URIs, apart from fetching the RDF statements about them, one by one. |
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello everyone,
My name is Nicola, and I'm the founder of ATARAVIA, a company I'm developing to help people with disabilities and other access requirements make informed decisions about travel and participation.
I've been researching the Reconciliation API, OpenRefine, Cocoda, SKOS, and JSKOS to better understand how existing systems identify entities, connect information from different sources, and manage those relationships.
The research has been helpful, but I've reached a point where I think it makes more sense to ask people who have experience working with these systems for direction.
One thing I'm trying to understand is what happens after entities have been matched. If something changes, is merged, or is deleted, how do systems identify what else might be affected? I'm also interested in how people keep track of why a match was originally accepted and what happens when new information calls that decision into question.
I realize some of what I'm exploring may fall outside the scope of the Reconciliation API, and that's perfectly fine. I'm interested in learning what approaches already exist and whether there are other projects, standards, or communities I should be looking at.
I'd appreciate any guidance or suggestions on where to direct my research.
Thank you!
All reactions