Re: User contributed data to DBpedia, was: [ANN] Add your links to DBpedia workflow version

On 1/25/13 9:39 AM, Barry Norton wrote:
> Sounds like, if you want to upload a whole bunch of data, this should 
> be a WikiData API request first and DBpedia via (one hopes) inclusion 
> of WikiData in Wikipedia.
>
> I know this is still speculative but worth mentioning, I hope.

That's how the virtuous cycle will/should work. Otherwise, emulate YAGO, 
UMBEL etc.. by making linksets that can be added to the dumps on the 
DBpedia download page and also uploaded to the SPARQL endpoint.

Re. SPARQL endpoint, you can even have datasets hot-staged in their own 
named graphs. You can even have groups of folks that can even edit data 
in these graphs via SPARQL 1.1 Update protocol since graph level ACLs 
are an integral part of Virtuoso. Editors can leverage protocols such as 
WebID, OpenID, OAuth etc.. The Read-Write dimension of this entire 
effort simply needs folks to participate :-)

Kingsley
>
> Barry
>
>
>
> On 25.01.2013, at 13:57, Sebastian Hellmann 
> <hellmann@informatik.uni-leipzig.de 
> <mailto:hellmann@informatik.uni-leipzig.de>> 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 
>> <http://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 <Soren.Roug@eea.europa.eu>
>> An:  public-lod@w3.org <public-lod@w3.org>, 
>> hellmann@informatik.uni-leipzig.de <hellmann@informatik.uni-leipzig.de>
>>
>>
>>
>> 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:soren.roug@eea.europa.eu]
>> || Sent: 25 January 2013 14:14
>> || To:public-lod@w3.org;Dbpedia-developers@lists.sourceforge.net;
>> ||hellmann@informatik.uni-leipzig.de
>> || 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
>> ||soren.roug@eea.europa.eu
>> ||
>> || 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 tohttp://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
>> || -----------------------------------------
>>
>>
>>
>>


-- 

Regards,

Kingsley Idehen 
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen