Sebastian, I am so glad you said that! I already think (as I have said on the list before) that links and stuff should not be part of "dbpedia" - when I access dbpedia I am expecting stuff that came out of wikipedia - no more than that. It therefore comes with all the trust (!) and provenance of that source. Adding even links that are not clearly marked as a different source is very suspect. Adding extra "correcting" information would be a Bad Thing. Correcting the information in wikipedia is the usual way to go. Or, it might be sensible to extend your excellent idea of the github resource to provide information such as dbpediaURI-linked RDF. But I'm not sure why that would be useful, as the data is presumably already somewhere else. So it is more an index of where dpbepdiaURIs are used (and Sindice does a lot of that).
When it comes to hierarchy (and instance/class descriptions, although I don't think they are useful), I think the same thing applies. Can Wikipedia be enhanced to include the information? If not, then any such enhancements over dbpediaURIs should be clearly separated from the main source. Best Hugh On 25 Jan 2013, at 13:57, Sebastian Hellmann <[email protected]> wrote: > Hi Søren, > (I renamed the topic and replaced DBpedia developers list with discussion) > > in general, we would like to improve nothing in DBpedia, whcih should be > fixed in Wikipedia. So population numbers should be fixed there (or WikiData > soon hopefully). We really do not want to become something like Freebase, as > DBpedia should stay a Semantic Web mirror of Wikipedia. By the way, wouldn't > it be sufficient to link to EuroStats? > > On the other hand, it might make sense to create additional structures over > DBpedia identifiers. Yago, umbel and schema.org already does this and > provides their hierarchy for DBpedia to include. This should, however, not > overlap with the DBpedia ontology. There are also plans to extend the > Mappings Wiki, so everybody can customize mappings for personal use cases. > This is not an easy topic however. > > > -- Sebastian > > > -------- Original-Nachricht -------- > Betreff: RE: [ANN] Add your links to DBpedia workflow version 0.1 (this > is also an RFC) > Datum: Fri, 25 Jan 2013 14:30:16 +0100 > Von: Søren Roug <[email protected]> > An: [email protected] <[email protected]>, > [email protected] <[email protected]> > > Another idea: When linking DBPedia administrative regions to NUTS codes I > sometimes see population numbers in the DBPedia resources, but they are of > low quality. I can provide the newest Eurostat numbers for them. And again; > what should the predicate be? > > Best regards, > Søren Roug > > > || -----Original Message----- > || From: Søren Roug [ > mailto:[email protected] > ] > || Sent: 25 January 2013 14:14 > || To: > [email protected]; [email protected] > ; > || > [email protected] > > || Subject: Re: [ANN] Add your links to DBpedia workflow version 0.1 (this is > also > || an RFC) > || > || I'll contribute some links to a vocabulary of NUTS codes. The Nomenclature > of > || Territorial Units for Statistics [1] is a hierarchial organisation of > || administrative regions in Europe. It is heavily used by Eurostat, and LOD2 > has > || converted the Eurostat datasets to RDF. > || > || The word hierarchial lead me to my question. Would it be useful to > contribute > || links to DBPedia that link two DBPedia resources together in a hierarchy, > and > || what should the predicate be? SKOS broader/narrower seems to me to have > || too > || little semantic information about what kind of relationship it is. I.e. > that > || it is a spatial form of broader/narrower. > || > || [1] > || > http://en.wikipedia.org/wiki/Nomenclature_of_Territorial_Units_for_Statistics > > || > || > || -- > || Sincerely yours, > || > || Søren Roug > || European Environment Agency > || > [email protected] > > || > || Onsdag den 16. januar 2013 15:06:13 skrev Sebastian Hellmann: > || > Dear all, > || > > || > we thought that it might be a nice idea to simplify the workflow for > || > creating outgoing links from DBpedia to your data sets. This is why we > || > created the following GitHub repository: > || > > https://github.com/dbpedia/dbpedia-links > > || > > || > Please feel free to add new files and change the links and then send us > || > a *pull request*. This message is an announcement as well as a request > || > for comments. > || > > || > Here is a (non-exhaustive) list of open issue: > || > > || > - it is yet unclear, when the links will be loaded into > || > > http://dbpedia.org/sparql > (maybe with version 3.9? ) > || > - we plan weekly updates to > http://live.dbpedia.org > > || > - yago, freebase and flickrwrappr have been excluded due to their size ( > || > > || > > 0.5GB ) > || > > || > - there will be some quality control; not everybody will be able to > || > include any links he wants to include. We are open to ideas how to > || > manage this. Consider "pull requests" as "application for inclusion" > || > - folder/file structure is still very simple, we will adapt upon uptake > || > > || > All the best, > || > Sebastian > || ----------------------------------------- > > > > >
