Sergio, Thank you very much for the precisions. And very nice to hear that Marmotta is based on Sesame, that is a good new for us.
As I said, we are not really working on that until mid-august. However, what document would you recommand me to read until then, in order to really understand Marmotta ? Thank you for any pointer Fabian >>> Sergio Fernández<[email protected]> 22/05/14 14:37 >>> Hi Fabian, On 19/05/14 10:57, Fabian Cretton wrote: > Thank you very much for your answer. As we will finally start the > developpment only at the end of the summer, we still have time to > discuss the options. Great. > In a few weeks, I might come back with more precise questions about how > could the overLOD features be implemented effectively. > Do I understand correctly that you say, according to our first thoughts > about "html5/node.js+sesame-owlim" we could implement > "html5/node.js+marmotta-kiwi". With that configuration, would be the > goal of node.js just to "hide" marmotta from the clients ? and thus also > bring an abstraction layer: with that configuration, having node.js > interacting with an LDP platform over HTTP, on the server, it would make > the architecture pretty flexible if there is any need to move from one > LDP to another, that could be interesting. Well, first you have to decide what backend you need to use for your frontend. If JavaEE is enough, you can reuse the same than Marmotta, which will be more efficient than have it running on a different runtime (node.js or whatever). Marmotta admin interface is extensible, so you can easily plug-in new modules. But you can have any other HTML UI on top. Check the Fusepool P3's platform early implementation to have a simple example how: https://github.com/fusepoolP3/platform > But about efficiency and response time, would it be better to simply > have "html5/marmotta", I think that so far Marmotta is implemented like > this with its client interfaces, no ? Exactly, the Marmotta admin interface works in that way. > is Marmotta/Kiwi comparable to the couple Sesame/OWLIM ? Well, not really, but I'll try to explain some things: * Marmotta is based on Sesame * Marmotta allows to use different backends (triplestores) based on the Sesame Sail API: http://marmotta.apache.org/platform/backends * KiWi is the default backend * There are some other backend available out there (Sesame Native, BigData, Virtuoso, Titan, etc) * More can be easily added since it's a matter of implementing a Java interface and a compatible Maven module * Therefore you could easily add a OWLIM backend for Marmotta Hope with these things you have now a clearer picture. > Also, do you have any information about Kiwi performances ? Not really... MARMOTTA-177 is one of our long-time unresolved tasks. The project would benefit a lot if you have resources in overLOD for such kind on performance evaluations. Cheers, -- Sergio Fernández Senior Researcher Knowledge and Media Technologies Salzburg Research Forschungsgesellschaft mbH Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria T: +43 662 2288 318 | M: +43 660 2747 925 [email protected] http://www.salzburgresearch.at
