Page History

...

Attendees:  Tin, Cory, Craig, Scott, Yeon, Jason, Kim, Larry, Cuong, Jacob, Sara

Discussion: Triple Store/Graph Database

• Mayo has looked at the report from the SI group from CBIIT.  
• Larry indicated that SPARQL query is the most focus for the NCIT.  Also ability to federate queries across SPARQL end points.  Would like have consistent results across LexEVS, SPARQL.
• Jason and Kim have been working on a project 
• Gilberto - there are no use cases prepared.  However, there are things that a terminology server cannot provide.  Would like to have more integrated services.
  
  • For example, if researching Cancer and looking for gene data (how do I glue this information together). If both are in RDF, then can query using all with SPARQL.
  • Another example, is data elements - are there other data that exist that might be appropriate for my research.  Users can start to explore ontologies for this data discovery.
  • Federation of data from other SPARQL endpoints is the primary interest.  
• Larry suggested that Instead of LexEVS - Hierarchy and traversals might be better implemented in SPARQL.
• Gilberto - 
  • Federated queries - yes.
  • SPARQL doesn't need to support reasoning - however, some minimal reasoning 
  • Performance isn't priority, but it can't be a bottleneck.  (graph DB isn't in the consideration)
  • LexEVS/CTS2 doesn't need to tie to the triple-store (all shouldn't be exposed through the triple store)

{scrollbar:icons=false}

...