Hi Rupert, Florent and Antonio
El 27/05/14 08:51, Rupert Westenthaler escribió:
As the result of Enhancement Routes is content + metadata I can not
see what you want to "store" in the Entityhub that is about managing
Entities.
> - entityhub: To query/update the entityhub component
Maybe. If you can come up with a good use case ^^
> - contenthub: To develop a new content-hub using chain/engine components
>and solr/elasticsearch/whatever component (solr and elasticsearch component
>already exist in Camel)
IMO implementing a new Contenthub like component is outside the scope
of this GSoC project. However If there is already Solr/Elasticsearch
component it would be a really useful thing
Regarding this, in my opinion, the use case of an eventual integration
with a Content hub is probably one of the most clear for this project.
I'm not sure if that is what Antonio was trying to explain but, with a
single route using as last endpoint Solr or any other backend system, we
would be almost cloning the same functionality than the previous
ContentHub implementation (Stanbol 0.12). Entities could be dereferenced
using the EntityHub before storing the content along with the metadata,
which is the point of integration of the EntityHub in such use case. And
even most interesting, now with the integration of Marmotta contributed
by Rupert, it would be possible to use a whole graph for dereferencing,
so "simply" routing components like Enhancer->Marmotta->Solr sounds to
me like an interesting use case.
wdyt?
Cheers,
Rafa
