Rob Lee schrieb: > Sebastian Hellmann wrote: > >> Yes, >> there are disambiguation pages. >> Formerly data looked like this: >> :Apple a :FloweringPlant >> :Apple :kingdom :Plant >> :Apple :disambiguates :Apple_Inc. >> >> >> There were even worse cases. >> e.g. Braniff_(Disambiguation) was made to Braniff, which was a redirect >> to Braniff_International_Airways >> >> There is no correct algortihmic approach to solve this matter, so the >> reason, why we changed it, is that it reflects the pages on Wikipedia as >> they are, without any transformations, that might lead to a strange >> representation. >> >> If Apple is a FloweringPlant, how can it disambiguate Apple Inc.? >> The concepts have nothing to with each other, except sharing the String >> identifier. >> >> > > I can see the logic and agree with it (I think), but I can't see any > evidence of the change in the changelog for 3.4 (have I just missed it > ?) It's quite a big change to have made (the disambiguation dataset has > nearly doubled in size between 3.3 and 3.4) - was there any discussion > on the mailing list as to the best implementation (for example, it might > be nice to add a reference to the disambiguation page - 'disambiguated > by' or similar) ? Is there any benefit in setting up a > dbpedia-developers list, in order to discuss these changes to the core > data ? > The disambiguation issue was considered a bug and therefore just fixed. Especially, with the upcoming live extraction, DBpedia clearly needs to reflect Wikipedia on a page level. A dbpedia-developers list is something, which is on our todo list, but it should not be another mailing list. Currently, our developers are busy. One thing is the live extraction, the other thing is the complete refactoring of the extraction framework in java/scala. Code fluctuation is so high, that a developers list would be not effective.
However, I understand the concern, you have. There should be more public influence and we are working on that. Part of it comes bundled with the live extraction and also, once we have a steady code base, there should be appropriate places to discuss changes and enhancements properly. Also the vocabulary used should reflect consensus. As a preview, you can have a look here: http://meta.wikimedia.org/wiki/DBpedia Regards, Sebastian > Rob > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Dbpedia-discussion mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion > > -- Dipl. Inf. Sebastian Hellmann Department of Computer Science, University of Leipzig Homepage: http://bis.informatik.uni-leipzig.de/SebastianHellmann Research Group: http://aksw.org ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Dbpedia-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
