As I am just in the middle of trying to put together a high-quality information base using DBpedia 2016-10, I'll vote strongly for more-frequent extractions at the expense of dropping some of the datasets.
The problem that I have run into is that there are some major errors in at least the Italian, Spanish, and Russian DBpedias. If there were going to be new versions of this information coming along shortly I would be very motivated to spend the extra time required to try to fix these problems and wait for the next extraction run. As things stand now, however, any changes that I make to extraction rules will not show up for months, so what motivation do I have to fix them? I'm going to just ignore the parts of DBpedia where these errors come from, which isn't ideal but at least gets me some useful information. So I would be much happier with a DBpedia that has a single namespace (particularly if it is the Wikidata one). This would allow for jettisoning a lot of the fluff triples. Now there may be some need to keep the different language DBpedias separate, but this can be done by putting them in different documents. One issue is just how to handle identifiers that don't nicely correspond to Wikipedia pages (or Wikidata items) - I'm in favour of using blank nodes (or if blank nodes are still too controversial using fake blank nodes, i.e., something like Skolem names). peter On 09/25/2017 09:31 AM, Sebastian Hellmann wrote: > Hi all, > > we are currently having quite a discussion about a stretch at DBpedia. > > The main point is that we spent a lot of time maintaining the current way > DBpedia is done, i.e. bi-annual releases. Personally, I feel that our time > would be spent better on innovating it, i.e. > > - having links, mappings and ontology maintained at GitHub > > https://github.com/dbpedia/links , > https://github.com/dbpedia/ontology-tracker/ , > https://github.com/dbpedia/mappings-tracker > > - letting the extraction run more frequently (maybe 15 day interval), but then > producing less datasets, i.e. focusing on the ones that are the most used > > - update the endpoint more often > > > Also we would really benefit in terms of data quality and completeness, if we > were to go for a fused version, where we pick the best data from all available > sources (Wikidata+all DBpedia versions for now, later more sources like yago, > VIAF and other datasets). I mean the data is there, why not fuse it into > something consistent and usable. > > This becomes especially obvious, if you look at the > https://meta.wikimedia.org/wiki/Grants:Project/DBpedia/CrossWikiFact proposal > and also at the display of the prototype: > > http://downloads.dbpedia.org/temporary/crosswikifact/results/q64.html > > > The pickle is a bit to decide, whether we should just stop releasing DBpedia > in its current form and put all efforts into a more live version that also > allows more contributions in a timely manner. > > Any opinions on this? I have the feeling that we are only marginally getting > better with the current way of running things. > > > -- > All the best, > Sebastian Hellmann > > Director of Knowledge Integration and Linked Data Technologies (KILT) > Competence Center > at the Institute for Applied Informatics (InfAI) at Leipzig University > Executive Director of the DBpedia Association > Projects: http://dbpedia.org, http://nlp2rdf.org, http://linguistics.okfn.org, > https://www.w3.org/community/ld4lt <http://www.w3.org/community/ld4lt> > Homepage: http://aksw.org/SebastianHellmann > Research Group: http://aksw.org > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > _______________________________________________ > DBpedia-discussion mailing list > DBpedia-discussion@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ DBpedia-discussion mailing list DBpedia-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
