Hi all,
I've been working on a small side project using DBPedia, and found that there
are too many broken image links in DBPedia. e.g.
http://dbpedia.org/resource/Thank_You_%28Jamelia_album%29
http://en.wikipedia.org/wiki/Thank_You_%28Jamelia_album%29
http://upload.wikimedia.org/wikipedia/commons/c/c0/Jamelia_-_Thank_You_%28Version_1%29.jpg
http://dbpedia.org/resource/Siege_of_Tuyen_Quang
http://en.wikipedia.org/wiki/Siege_of_Tuyen_Quang
http://upload.wikimedia.org/wikipedia/commons/b/bc/Defense_of_Tuyen_Quan_bf_1923.jpg
http://dbpedia.org/resource/Yolo_County_Arts_Council
http://en.wikipedia.org/wiki/Yolo_County_Arts_Council
http://upload.wikimedia.org/wikipedia/commons/a/a3/Ycac.png
and many more. And there are some that are incorrect (I assume that this is due
to errors in the extraction process) e.g.
http://dbpedia.org/page/Grand_Duchy_of_Tuscany - foaf:depiction ->
http://upload.wikimedia.org/wikipedia/commons/c/c3/Flag_of_France.svg
Perhaps checking for broken links now and then wouldn't be such a bad thing.
Just an idea.
Also a lot of properties that seam to be duplicate properties for things:
http://dbpedia.org/property/birthPlace and
http://dbpedia.org/property/birthplace. Visor (http://visor.psi.enakting.org/)
a tool I created is very good at surfacing such errors.
Sorry if I'm pointing out things that are already known problems but I'm new to
this list so I thought I share my experience from a hacker/user perspective.
Best,
--Igor
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Dbpedia-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
