| 1 | | This will be implemented by Daniel Burkhart in ticket:92 |
| | 1 | This will be implemented by Gunnar Grimnes and Daniel Burkhart in ticket:92 |
| | 2 | we make more tickets for subtasks. |
| | 3 | |
| | 4 | = Needed Services = |
| | 5 | |
| | 6 | We need rdf storage in different parts of gnowsis. Each storage has a reason and different requirements. |
| | 7 | |
| | 8 | * 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 |
| | 9 | * 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. |
| | 10 | * 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 OR Catwiesel. Named graphs are used to seperate single resources, each ResourceManifestation gets a named graph. |
| | 11 | |
| | 12 | = Approach = |
