Hi Fabian,
On 22/08/14 09:19, Fabian Cretton wrote:
I hope you are well, and I am coming back to you as I will start these
days to understand better Marmotta and see (hopefully with your help)
how the features we are thinking of in OverLOD could be implemented.
There are quiet a few questions in this email, hope you can answer them
so that I can move on more efficiently. Thank you in advance.
The community will try to help us when possible, sure.
In a former email your were pointing me towards Fusepool, saying
"Actually looking to the idea, technologically talking it does not look
so different to what the Fusepool P3 FP7 project tries to do. "
I thus had a look at Fusepool, but from what I saw, Fusepool is about
"creating" RDF from non-RDF resources, whereas OverLOD is mainly about
consuming existing RDF data and have it at disposal for a specific
platform and use-case.
So one goal of OverLOD is more about the "next steps" of the semantic
web: how to consume efficiently RDF, and then make it easier for non-RDF
developpers to use the data.
I may got it wrong. Sure, the goal looks different. And very important
and careless one. Let's see what progress OverLOD is able to do :-)
About developpment
Apache developpment is a new world for me, but some colleagues here
might help me.
Also I will follow the instruction you gave to QiHong earlier this
year, and so I will start to fork marmotta if I am not mistaken (git and
github are also new to me).
So I will do the same, and thus, in my fork, create a branch from
'develop' -> is there a name you recommand me ? do I need to create
'Issues' about OverLOD features ?
Wekk, forking the repo from github could be also useful. But since you
are not going to modify the core of Marmotta (right|?), just depending
on the Maven level should be more than enough for you.
Please, report as Jira issues all problems and/or needs you may have.
As you pointed out "For me the "OverLOD Referencer" has a big potential
of reusing the infrastructure provided by LDClient [2 (
http://marmotta.apache.org/ldclient/ )] and LDCache [3 (
http://marmotta.apache.org/ldcache/ )]."
LDClient seems the way to import external data into Marmotta. I don't
see LDClient on the "Platform Architecture Overview".
This external data could be RDF, or data that needs to be RDFized,
right ?
The first question is the one already expressed here above: does
LDClient already handle the automatic update of the data once the data
source have been modified ? (I only read about some time-out features
but don't know yet what it means).
Second question is about the RDFizers: there is a nice list of RDFizer
listed, but nothing about Microdata/Microformat, would that be something
to implement if needed ?
Then, LDCache does handle where to store the incoming data from
LDClient. But is this storage different from the main Marmotta storage ?
Are the imported data part of the default graph and queryable
transparently with the other data from the LDP ? I guess so, but from
what I read I did have some doubts.
Shortly:
* LDClient is a library to access resources as Linked Data, not only
directly Linked Data resources, but also allowing the transformation of
non-Linked data resource into Linked Data (RDF). It comes with some data
providers http://marmotta.apache.org/ldclient/dataproviders, but it can
be extended to support new ones, such as for Microdata.
* LDCache is the infrastructure built on top of LDClient to
automatically retrieve (cache) data from different sources. Further
details at: http://marmotta.apache.org/ldcache
These two libraries are use in the Marmotta platform to automatically
cache in the triple store (under an special named graph / context) data,
and keep it updated according the configuration.
Hope that helps.
Cheers,
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 660 2747 925
e: [email protected]
w: http://redlink.co
