The document discusses storing a geopolitical ontology containing about 21,000 triples. It currently stores the ontology in a flat file and uses the JENA API. The document proposes alternative architectures for storage, including using a triple store or relational database, and compares loading times for different options based on benchmark results. It suggests hosting a SPARQL endpoint for querying if using a relational database-based storage.

1. Triple storage for geopolitical ontology

2. Geopolitical ontology Size : about 21,000 triples Storage : flat file Ontology API: JENA (java)

3. Possible Architecture for storage Current Triple store-based RDBS-based APPLICATION APPLICATION APPLICATION JENA JENA JENA Triple store Ontology in Flat file Mysql

4. Loading time http://www4.wiwiss.fu-berlin.de/bizer/BerlinSPARQLBenchmark/results/V5/index.html#comparison Chris Bizer, Andreas Schultz. The Berlin SPARQL Benchmark. Int. J. Semantic Web Inf. Syst. 5(2): 1-24 (2009)

5. Possible Architecture for storage Current Triple store-based RDBS-based APPLICATION APPLICATION APPLICATION JENA JENA JENA Triple store Ontology in Flat file Mysql JENA SDB JENA TDB

6. SPARQL end point RDBS-based SPARQL endpoint (JOSEKI) JENA Mysql JENA SDB