1. Triple Store/Graph Database Overview There have been discussions in the past between Mayo and NCI about using a triple store/graph database. The Semantics Infrastructure (SI) group of CBIIT has also done considerable research and analysis on this topic. We need to understand what NCI’s requirements are surrounding this topic.

2. Triple Store/Graph Database Discussion topics to understand NCI’s requirements: Is there an existing requirement to move to a triple store or graph db? Does the SI group have recommendations? If not, when will they have them? Will the EVS team be following the recommendations of the SI group?

3. Triple Store/Graph Data Base SI Talking Points Are federated queries required? Should these be over SPARQL endpoints? There are potential security issues with this. Does SPARQL need to support reasoning/inference? What priority is performance? Why is performance only focused on for triple stores? How does this tie in to any LexEVS/CTS2 API requirements, if any?

4. Triple Store/Graph Data Base What does a terminology datastore need to do? KVS - Key-Value store DS - Document Store RDBMS - Relation Database GDB - Graph Database Datastore FeatureDatastore Type that Performs Well Store a resource with an IDKVS, DS, RDBMS, GDB Find a resource by IDKVS, DS, RDBMS, GDB Find a resource by a set of propertiesDS, RDBMS, GDB Find all edges of a resourceGDB, RDBMS Traverse a graphGDB Compute subgraphsGDB Perform set operations on subgraphsGDB Calculate pathsGDB

5. Triple Store/Graph Data Base Demo of ArangoDB Next steps/roadmap

6. Triple Store/Graph Data Base Discussion Recap Requirements Decision Points Priority