|
Hi all, Could you please guide me why we use AllegroGraph or Sesame What are all the steps to be required to use these technology |
|
Not enough reputation to post this as a comment above... so I'll say it here. While the AllegroGraph server is written in Lisp, the most common clients are Java and Python. Yes, there is a Common Lisp client, but all three clients are first-class citizens in the AllegroGraph world, and they all use the same REST protocol to communicate with the server. |
|
Hi there are many triplestores, the most popular are:
for example several rdf navigator uses internally jena components (pubby, elda, d2r, ...), and the majority of these stores (including jena) expose also the SAIL implementation, so in other words: you could use sesame libraries and webapps in order to access a repository SAIL-compliant, such as bigowlim, virtuoso, allegro or any other. An interesting addition for me in the SAIL implementations family is the tinkerpop/blueprints stack for graphdb: by these components you could use graph dbs (neo4j, orientdb,...) as backend for a sparql endpoint, so you could also use the workbench webapp from sesame over a neo4j instance, which could be interesting for some purposes. (If you could be interested in this direction please take a look at thi interesting example: http://blog.acaro.org/entry/dbpedia4neo as a starting point) The short version: start from sesame! :-) forgot ask, how these are different from Joseki joseki is jena-based, the semantic navigators cited above are all based on joseki essentially... it works great for acquiring a model from triples, so the majority of the projects i see used triples for the config file, as for the Linked Data Api definition. I found joseki useful for projects that needs to expose a sparql endpoint in a simple way: it's java, it's jena based, it has a pluggability to sail based stores (via jena/sesame bridge), it has some lucene full-text possibility via the arq component... i found it limited when you instead need to construct a sparql endpoint service for a lot of data, and want maybe the possibility to have some plus in terms on scalability of specific services. It's my point of view of course: no doubt it's a good product, but i rather prefer joseki as engine for browsers/navigators etc and some other project (like virtuoso o the tinkerpop family) for more big data access. In that direction the possibility to use the sesame workbench via the SAIL interface in the development phase is really handly |
