Changes between Version 1 and Version 2 of SesameIntegration


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

--

Legend:

Unmodified
Added
Removed
Modified

  • SesameIntegration

    v1 v2  
    33at the moment, we have two major features and key factors in gnowsis: 
    44 
    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.  
     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.  
    88 
    99At 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. 
    … …  
    1111at the moment we have: 
    1212 
    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  
     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  
    1616 
    1717So, by switching to Sesame2 we hope to have a more durable solution in the future, because: 
    1818 
    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  
     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  
    2323 
    2424Especially 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. 
    … …  
    2929Sesame2 has to be stressed-tested before, reagrding its SPARQL capabilities, etc: 
    3030 
    31     * SPARQL 
    32     * QUADS 
    33     * Fulltext-search ( or with catwiesel ) 
    34     * fast inserting of data  
     31 * SPARQL 
     32 * QUADS 
     33 * Fulltext-search ( or with catwiesel ) 
     34 * fast inserting of data  
    3535 
     36= Steps to do = 
     37 1. learning Sesame2 (get it from Sourceforge-CVS, project: openRDF) 
     38 2. which parts in gnowsis have to be replaced? (which functions are important?) 
     39 3. which parts of gnowsis can be deleted? 
     40 4. do everything from scratch 
     41 4. We need an architecture overview (graphical) 
     42 5. API'S have to be implemented: 
     43   1. Central Repository 
     44   2. Ontology Manager 
     45   3. Gnowsis Search 
     46   4. Central Hub 
     47 
     48 
     49== which parts of gnowsis can be deleted? == 
     50most code inside this package can be removed: 
     51source:trunk/gnowsis/src/org/gnowsis/repository 
     52 
     53= Aperture = 
     54 1. Aperture will be used instead of the package source:trunk/gnowsis/src/org/gnowsis/adapters and 
     55    source:trunk/gnowsis/src/org/gnowsis/data 
     56 
     57= Result = 
     58Everything to Gnowsis Server project 
     59