Sergio, 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.
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. 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 ? is Marmotta/Kiwi comparable to the couple Sesame/OWLIM ? Also, do you have any information about Kiwi performances ? Thank you Fabian >>> Sergio Fernández<[email protected]> 11/05/14 18:31 >>> Hi Fabian, first of all thanks for the interest in the project. On 02/05/14 08:54, Fabian Cretton wrote: > So I did prepare a document that can be found here: > https://dl.dropboxusercontent.com/u/852552/Marmotta_OverLOD%20Surfer%20presentation_0.2.pdf > > I hope it will help you to see if, as you say, our project's features > fit in your roadmap. Well, I'm not saying it does not fit, but also take into account that does not require to: you can build your project using Marmotta as platform with your own agenda. But let's see For the document, I'd like to quote a sentence: "Before initiating this discussion with the Marmotta team, our intention was to develop our own tool based on node.js/Sesame-OWLIM for the back-end, and HTML 5 for the front-end." Such plan would be still possible: you just replace OWLIM by Marmotta, and in case you would like to reuse the same runtime, node.js by JavaEE. The rest pieces can remain the same. Actually looking to the idea, technologically talking it does not look so different to what the Fusepool P3 FP7 project tries to do. So, although still in a very early stage, you could take that platform [1] as example of usage/extension of Marmotta. Going deeper into the components of the project: * Many components are UI one. Since it's one of the weakness of the project, I'd say that the results would be relevant for the project for sure. * For me the "OverLOD Referencer" has a big potential of reusing the infrastructure provided by LDClient [2] and LDCache [3]. * For sure you may benefit of some of the other infrastructure (LDP, SPARQL and so on) which does not make sense you implement from scratch. * The analytics part is something interesting to see. * And for sure, all Linked Data apps built of top will be always well received. So, from my personal point of view, I'd welcome OverLOD to be built on top of Marmotta and start to join the community with relevant contributions. I can't promise so much effort besides my support when possible, but we'll manage somehow. Cheers, [1] https://github.com/fusepoolP3/platform [2] http://marmotta.apache.org/ldclient [3] http://marmotta.apache.org/ldcache -- 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
