Changes between Version 9 and Version 10 of SesameIntegration


Ignore:
Timestamp:
01/26/06 15:36:28 (15 years ago)
Author:
grimnes
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SesameIntegration

    v9 v10  
    88We need rdf storage in different parts of gnowsis. Each storage has a reason and different requirements. 
    99 
    10  * configuration store: part of gnowsis-config api. Is used to configure the services (hostname, passwords, services, etc). It has to be stored in an N3-RDF to be able to hack it if something goes wrong. This relates to ticket:107.  
    11  * pimo-store: all things of the user, the pimo ontology itself, the imported domain ontologies, the things of the user, links to occurrences, wiki pages, wiki names, all.... Features: text indexing (using the lucene SAIL, configured to what is indexed). Named graphs are not really used? Reification is used to say when a triple was inserted when its a user triple like pimo:occurrence. Pimo-store replaces the Central-Rpository! 
    12  * resource-store: stores all resources (pimo:ResourceManifestation) of the user. Its filled by Aperture and sometimes by the applications that want to add a few resources before they are annotated (using pimo:occurrence). No other parts of pimo go there, especially no pimo:occurrence links. Needs fulltext indexing using LuceneSail(configured by Aperture ontology and PIMO-ResourceManifestation) OR Catwiesel. Named graphs are used to seperate single resources, each ResourceManifestation gets a named graph. 
    13  * service-data-store: used by services like Thumbnailservice, IconService, ContextService, etc to store the RDF data they need to work. Named graphs are used to seperate the services. No text-indexing needed (no LuceneSail). Interfaces: Sesame2, Jena ModelDatabase..? 
     10 * configuration store: part of gnowsis-config api. Is used to configure the services (hostname, passwords, services, etc). It has to be stored in an N3-RDF to be able to hack it if something goes wrong. This relates to ticket:107. #140 
     11 * pimo-store: all things of the user, the pimo ontology itself, the imported domain ontologies, the things of the user, links to occurrences, wiki pages, wiki names, all.... Features: text indexing (using the lucene SAIL, configured to what is indexed). Named graphs are not really used? Reification is used to say when a triple was inserted when its a user triple like pimo:occurrence. Pimo-store replaces the Central-Rpository! #141 
     12 * resource-store: stores all resources (pimo:ResourceManifestation) of the user. Its filled by Aperture and sometimes by the applications that want to add a few resources before they are annotated (using pimo:occurrence). No other parts of pimo go there, especially no pimo:occurrence links. Needs fulltext indexing using LuceneSail(configured by Aperture ontology and PIMO-ResourceManifestation) OR Catwiesel. Named graphs are used to seperate single resources, each ResourceManifestation gets a named graph. #142 
     13 * service-data-store: used by services like Thumbnailservice, IconService, ContextService, etc to store the RDF data they need to work. Named graphs are used to seperate the services. No text-indexing needed (no LuceneSail). Interfaces: Sesame2, Jena ModelDatabase..? #143 
    1414 
    1515Startup sequence for the stores is: 
     
    2020Common Interfaces we need in different services: 
    2121 
    22  * Named graphs: in Sesame2 they are Repository/Sail, in Jena they are SPARQL-[http://jena.sourceforge.net/ARQ/javadoc/com/hp/hpl/jena/query/DataSource.html DataSource] 
     22 * Named graphs: in Sesame2 they are Repository/Sail, in Jena they are SPARQL-[http://jena.sourceforge.net/ARQ/javadoc/com/hp/hpl/jena/query/DataSource.html DataSource] #134 
    2323 
    2424Logical Services to provide: 
    2525  
    26  * big trick: write a wrapper that wraps Sesame2 as Jena Named graph (NG4J) and as a normal Jena Model. Vice Versa: have a sesame2 repository that wrapper for Jena Models. The native Jena Model is neede for inference perhaps. What might happen is that the pimo-store is stacked with one Jena model in between for the PIMO inference. 
     26 * big trick: write a wrapper that wraps Sesame2 as Jena Named graph (NG4J) and as a normal Jena Model. Vice Versa: have a sesame2 repository that wrapper for Jena Models. The native Jena Model is neede for inference perhaps. What might happen is that the pimo-store is stacked with one Jena model in between for the PIMO inference. #134,#135,#136 
    2727 * Gnowsis CentralHub API: implement the ususal features. SEe the current centralhub. 
    2828