Hi Sergio, >> >> Then, I did implement LDClients that can import RDF files (instead of >> using the import service). They are just like the "linked data" code, >> except I don't check if the subject of the triple correspond to the >> URI. >> My goal is to handle all imports with LDClient, which allows me to do >> other things on the temporary imported data. >> If you want this code, just tell me how to do.
>Well, that moves LDClient way from the Linked Data paradigm. I >understand your use case, but I'd not push it upstream. > >Maybe writing specialized Sesame RDFHandlers could be another approach >for that problem. Of course we don't expect that the code we write for OverLOD will be appreciated by the Marmotta Team, but we will just let people know it is there if needed :-) But actually I don't understand your point here about RDF files moving away from Linked Data paradigm. Do you mean that Youtube, Vimeo, RDFa and SPARQL endpoints, which all have LDClients, follow linked data paradigm more than http://sws.geonames.org/2921044/about.rdf I can see your point if LDClient only handles data published following the linked data principles, as DBPedia. But as LDClient also handles RDFa, do you mean that RDFa is more linked data than rdf files ? Not to say that LDClient seems event to play the role of RDFizer (Youtube and Vimeo) Thank you for your explanation on that. Cheers and thank you for your time Fabian
