Changes between Initial Version and Version 1 of SesameIntegration


Ignore:
Timestamp:
12/21/05 11:33:28 (19 years ago)
Author:
dburkhar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SesameIntegration

    v1 v1  
     1This will be implemented by Daniel Burkhart in ticket:92 
     2 
     3at the moment, we have two major features and key factors in gnowsis: 
     4 
     5   1. fast storage of masses of RDF in a quad-store (context-aware triplestore) and having this with SPARQL available 
     6   2. fulltext search 
     7   3. publishing this RDF store with an API that can be easily programmed.  
     8 
     9At the moment, these three goals are both realised using Jena and home-grown software. The first features is implemented using Jena and SPARQL2SQL. SPARQL2SQL is not maintained anymore and has serious performance problems on insert, especially when we activate our bad hack for mysql. The second solution at the moment is a mysql hack. We also had to implement client and server APIs to support the third feature. 
     10 
     11at the moment we have: 
     12 
     13   1. Jena and SPARQL2SQL 
     14   2. a MYSQL hack that crashes from time to time 
     15   3. an API that is expensive to maintain and to use - the gnowsis Repository and CentralHub? API  
     16 
     17So, by switching to Sesame2 we hope to have a more durable solution in the future, because: 
     18 
     19   1. sesame supports a triple store and quad store in sesame2 
     20   2. sesame supports lucene SAILs (or will support them soon) to enable fulltext search 
     21   3. sesame has a well-known API that can be used from many applications 
     22   4. sesame does not depend on any third party apps like MySQL - their native SAIL is said to be performant and scalable  
     23 
     24Especially the last point will have spare us some trouble. So we will still need something for the CentralHub? API but the repository and ontManager APIs can be replaces or enhanced completely using Sesame2. 
     25 
     26Another reason to switch to Sesame2 is our dedication to Aperture. 
     27BEFORE this we evaluate 
     28 
     29Sesame2 has to be stressed-tested before, reagrding its SPARQL capabilities, etc: 
     30 
     31    * SPARQL 
     32    * QUADS 
     33    * Fulltext-search ( or with catwiesel ) 
     34    * fast inserting of data  
     35