-
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
Design a sameas 'lite' api #86
Comments
We still need a source of sameas triples. Let's put how we generate that to one side, as there are many ways to do this. Let us consider the task of getting all the available data on an initiative that exists in the dotcoop and oxford data sets. Can we expose an api which takes a uri of the initiative and uris of the candidate datasets and returns a merged version of all the data available on that initiative from any of those datasets. The sparql query we would need to call should be straight forward, and the json returned would have the same structure of the data sent to sea-map instances when big data sets are requested. In this way if we used this call when we were selecting an initiative to display its data in a dialog, we could use the same code to display it. |
The api call would look something like... https://lod.coop/coops/find?initiative="dotcoop/404939450" &stores="sea-lod/oxford, dotcoop" |
So let's set up a test environment for designing the sparql query |
What options are there for handling clashes in the absense of data time stamps?
https://lod.coop/coops/find?initiative="dotcoop/404939450" & stores="sea-lod/oxford, dotcoop" & mergeOption=ALL_FIELDS|FIRST_FIELD |
For some reason I seem to have got notifications for these posts a bit late. Not sure if I entirely understand the scenario/motivation here, which means I am not sure how to answer. The above look like heuristics which would need to be layered on top of each other. As an aside, I recall finding a paper which suggest that https://link.springer.com/chapter/10.1007/978-3-642-17746-0_20 But I'm not sure of alternatives - perhaps synthesising a new graph from two or more others? |
As you are not assigned to it, you may be using different notification settings. It's not a scheduled ticket, so no hurry. |
I read the abstract, but not the paper. So it seems there are a few ways if interpreting what sameAs can mean. I wonder how ambiguous it would be for how we would use it? I think we want to say that that the two uris referenced in the triple refer to the same real world SSE initiative. How could this be ambiguous? We need to look at how sameAs is being used elsewhere when addressing organisations. Hard to imagine at the moment how it would change how we use it though... |
Anyway, what would the next steps.
|
Might need a chat at some point to clarify motivation and how I imagine implementation. |
To date most uses of sameas we considering using stores of sameas triples when running big sparql queries so that multiple data sets get merged. However, we should explore a lighter version too, which may be more flexible, so only merging data about a single initiative when it is needed, so we would be doing realtime dynamic multi database sparql queries from a sea-map instance say, but retrieving much a smaller set of information.
The text was updated successfully, but these errors were encountered: