-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
entity matching in addition to entity reconciliation? #2
Comments
I am not sure what a web-based protocol would look like for entity matching, it is an interesting question. I am not against discussing that problem in the group, given that it is clearly closely related. |
I am adding this in the document as in scope for now, but it can be changed. |
That is very useful Vladimir, I did not know about EDOAL! If you are familiar with it, do you want to write something about what you think about it in relation to the reconciliation API in https://github.com/reconciliation-api/census/blob/master/_pages/other-protocols.md? |
Reconciliation (as exemplified by OpenRefine) is "one to many": one tabular row is matched against many entities in a dataset or KG. (For efficiency, the protocol sends a batch of rows, but each one is treated separately.)
Entity matching (as a merging step needed in KG building) is "many to many": potentially ALL entities of the source dataset are considered, and entities in either the source or target dataset may be merged.
Is the scope of this group limited to Reconciliation only, or would it also include Matching?
The text was updated successfully, but these errors were encountered: