Hi Kingsley,
How about making an RDF document that describes LDF? Producing such a
document would make its value proposition clearer. This approach is also a
nice case of Linked Data dog-fooding e.g., the basis for the most basic LDF
utility example using an RDF document as the data
Hi Pascal
Interesting piece, forwarded to the Linked Open Vocabularies community [1].
Since there is not mention of the LOV project in the article, except only
indirectly by mentioning VOAF which was developed for this project, I
wonder if you were aware of this proposal I made two years ago [2].
** apologies for cross-posting **
LD4KD 2014
1st Workshop on Linked Data for Knowledge Discovery
http://events.kmi.open.ac.uk/ld4kd2014/
co-located with the European Conference on Machine Learning and
Principles and Practice of Knowledge Discovery 2014
Thanks Antoine, Bernard; we looked into several related proposals and
approaches and we are glad for your pointers. Yes, we mention LOV/VOAF
in the editorial.
I just added the links you provided as comments to the original blog
article [1] to help us keep track of them and make them easier
... according to http://dbpedia.org/data/HTTPRange-14.n3
We already knew it was turtles all the way down, but this is *news*.
Thanks to danbri for the pointer discovered in a side discussion about a
raging debate (too serious for a Friday evening) [1]
Have a great week-end.
[1]
On 4/11/14 3:12 PM, Bernard Vatant wrote:
... according to http://dbpedia.org/data/HTTPRange-14.n3
We already knew it was turtles all the way down, but this is *news*.
Thanks to danbri for the pointer discovered in a side discussion about
a raging debate (too serious for a Friday evening) [1]