Hello, fwd...
Thanks, ---------- Forwarded message ---------- From: Adeel Ahmad <aahmad1...@gmail.com> Date: 12 July 2012 01:01 Subject: jena/sesame To: d...@jena.apache.org Hello, I wanted to query about the performance, scalability, and portability issues with jena and sesame. If I am correct both can be utilized with tinkerpop? However, sesame provides a direct sail interface? What I wanted to get your opinion on is it better to load the data using jena but then query it using sesame? Or, should such load and extract steps be implemented from the same api? I find that jena is fast in terms of loading but very slow in terms of quering data where as the sesame works better in the opposite approach. I have noticed the adapter bridge between jena and sesame in some respects provides a solution for that. Is there a roadmap towards merging their functionality or perhaps making them equally compatible with each other atleast in terms of how they work with RDF related data? Also, I noticed that sesame has more of a portability for other languages apart from just java, whereas jena seems to be more focused towards java support. Are there any plans of making the bridge for python and php support such as seen on redland or for making the interfaces more tangible in use across different databases and lucene/hadoop streams? -- Thanks, Adeel Ahmad -- Thanks, Adeel Ahmad
