simphony-osp
simphony-osp copied to clipboard
simphony
Implement a neosemantics wrapper
Neo4j recently presented neosemantics which is a project to store rdf data in an efficient manner in neo4j. This might be a better way to store CUDS objects compared to SQL databases.
This could improve export and import to rdf needed for #297
@aaronAB1993 @yoavnash anything missing?
Did you find any information concerning its capabilities of exporting to RDF/OWL?
I guess to export everything, one would need to use the export by CIPHER method with a CIPHER query that selects every resource.
Would it be too much work to test the export time of both neosemantics and a triple-store SQL-database?
You mean without a wrapper? Does it make sense to compare SQL and Neosemantics only in terms of rdf-export? I think neo4j will be definitely better when it comes to complex queries, where the sql table would need to do a lot of self-joins.
The export is planned to be done directly on the DB, correct? or are you planning to convert first to CUDS?
Sorry, I misread before. In that case, comparing without a wrapper would make sense I would say, but you asked about other aspects. For queries, are we going to query directly the DB? if so, then wouldn't we be bypassing the semantic layer? if not, then should we even consider querying?
In second thought, for implementing the search methods and get_by_oclass it might make a big difference.
I think the speed of RDF export is one of the least important aspects when it comes to the choice of your database backend
Update: With the new TriplestoreWrapperSession, this should be very simple. We could use the AllegroGraphSession as an example.
We could keep that in mind for a HiWi task. Maybe we should tag as such? (e.g. "Possible HiWI task")