search

ATTX-project / graph-component

Graph Manager component that handles state of the internal graph/data.
0 stars 0 forks source link

Plan GM linking functionality in the API #19

Closed blankdots closed 7 years ago

blankdots commented 7 years ago

Description

We need to investigate how the linking functionality would be implemented in the short and long run. For this we need to indentify parameters and options by taking into consideration the strategy https://github.com/ATTX-project/project-management/wiki/Linking-graphs

DoD

Update swagger definition and wiki documentation.

Testing

Peer review.

blankdots commented 7 years ago

Wiki: https://github.com/ATTX-project/project-management/wiki/Graph-Manager-API Swagger: https://github.com/ATTX-project/graph-component/blob/feature-LinkingStrategy/gm-API/src/gm_api/swagger/gmAPI-swagger.yml

There are still 3 standing points:

  1. How will the strategy get implemented and could there be multiple types of strategies e.g. SPARQL, RML etc.?
  2. Clustering of IDs is it a hard dependency for the strategy to successfully complete?
  3. Updating provenance - it looks like the provenance might need to get update as a result of this linking, from the GM-API as well - considering that a new dataset will be generated as a result of successfully completing the linking.
blankdots commented 7 years ago

To be implemented:

  1. Link DPU
  2. LinkStrategy endpoint that gets the list of strategies from the graph
  3. loading strategies to Graph Store via config.ttl
  4. First strategy as SPARQL query
blankdots commented 7 years ago

Updated with new specifications: Wiki: https://github.com/ATTX-project/project-management/wiki/Graph-Manager-API Swagger: https://github.com/ATTX-project/graph-component/blob/feature-LinkingStrategy/gm-API/src/gm_api/swagger/gmAPI-swagger.yml