Thank you Sergio, >> Another critical aspect about LDCache I'd like (as others I guess) to >> understand: >> How does LDCache handle the 'update' of those information ? How does it >> know that a triple did came from a web resource (and should be updated), >> and how does it know that a triple was added afterwards (and should be >> kept for instance) ? >> Let say I have a bunch of triples with >> <http://www.websemantique.ch/people/fabiancretton> as a subject. Those >> triples are loaded from the web. LDCache will do some updates, thus >> deleting all triples where >> <http://www.websemantique.ch/people/fabiancretton> is subject, and the >> reimporting all triples where >> <http://www.websemantique.ch/people/fabiancretton> is subject, is that >> correct ? >> in the mean while, I did add a new triple with >> <http://www.websemantique.ch/people/fabiancretton> as a subject -> will >> it be deleted by LD Cache ?
> Not sure. That's an inherited problem of the RDF data model and the Open > World assumption. But actually that's a good point; I'll also discuss it > with Jakob on Monday. About this last point, I think I can guess the answer: - LDCache only deals with triples in the 'cache' context (and don't touch the other ones) - in the 'cache' context, all triples with a same subject do come from a same source and thus, LDCache can handle updates easily -> and this is one point very different from our OverLOD use case thanks again Fabian
