Page History

...

• There is a pilot ongoing to review triple stores
  • selected 3 triple stores (StarDog, Allegrograph (http://allegrograph.com/), Viritouso) and have been working for the past 6 months
  • evaluations covering restricting operations, loading data, performance testing, examine security (secured and anonymous access via proxies)
  • nature of queries haven't been as representative of what is needed for production.
  • more focus on real use queries.  
  • operations - hosting model not supported by CBIIT - so no support.  (ie, patching support not provided)
  • all can be queried with standard SPARQL
  • will still want REST services available to the end users.  
• Transition to SPAQRL gives raw access to the data (unlike API)
  • However, you need to understand the data - and this could differ from endpoint to endpoint.
• What do TripleStores provide - that differ (better than) LexEVS
  • Representation of Hierarchy
  • Level of expressivity
• 3 use cases for triplestore evaluation:
  • Expressivity (reasoning support)
  • Linked open data
    • use vocabulary as a "glue" between different data repositories.  Ability to "join" distributed repositories.
  • Closer integration of vocabulary and meta data (part of the MDR).
• Report writer now uses the triple store 
  • Loading of Value sets take much less time
  • Access of Value Sets is better, but not hugely different.
    
    
• Need to determine where Triple Store is better and where LexEVS is better.  

Decision Points:

• Investigate where Triple Store usage may augment LexEVS. 

...