Hi,
On 01/11/14 13:14, Fabian Cretton wrote:
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.
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
No no, I'm not saying that. Let me try to explain it:
If we take the Linked Data principles [1], ee could say that LDClient
extends the 3rd point ("when someone looks up a URI, provide useful
information") beyond just "using the standards (RDF*, SPARQL)" by
providing new methods to get RDF data out of other formats.
But LDClient does not modify the 1st principle ("use URIs as names for
things"). And that's what I referred to because the sentence "They are
just like the "linked data" code, except I don't check if the subject of
the triple correspond to the URI".
Maybe I got it wrong, and what you actually do is extend the 4th
principle ("Include links to other URIs. so that they can discover more
things"), which is of course interesting. Just needed to be explained.
BTW, hope you have in mind that if OverLOD produces new LDClient data
providers that can be useful for a broader community, please propose
them to be included in the main project.
Cheers,
[1] http://www.w3.org/DesignIssues/LinkedData.html
P.S.: please, configure you client to use the "Re:" prefix when replying
to public English mailing lists
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 660 2747 925
e: [email protected]
w: http://redlink.co
