On 3/30/15 3:39 PM, Vladimir Alexiev wrote:
Dimitris Kontokostas> we made some different design choices and map wikidata data directly into the DBpedia ontology.I’m very interested in this.A simple example: bgwiki started keeping Place Hierarchy in Wikidata because it’s much less efficient to keep it in deeply nested subtemplates. This made it very hard for bgdbpedia to extract this info, because how do you mix e.g. dbo:partOf and wd:Pnnn? So this is a logical continuation of the first step, which was for DBpedia to source inter-language links (owl:sameAs) from WD. (I haven’t tracked the list in a while, could someone give me a link to such dump? Sorry)Tom Morris> abandoned critical thinking and assumed DBpedia was dead now that we had WikiDataThat’s quite false. Both have their strengths and weaknesses.- DBpedia has much more info than Wikidata. For Chrissake, Wikidata doesn’t even have category>article assignments!- Wikidata has more entities (true, "stubs"), a lot of them created for coreferencing (authority control) purposes. IMHO there’s a bit of a revolution in this domain, check out https://www.wikidata.org/wiki/Wikidata:WikiProject_Authority_control https://twitter.com/hashtag/coreferencing https://tools.wmflabs.org/mix-n-match/VIAF is moving to Wikidata coreferencing, which will get them double the name forms, 300k orgs and 700k persons.This is Big Deal to any library of museum hack.- Wikidata has easier access to labels. In DBpedia you have to do a wikiPageRedirects dance, and if you’re naïve you’ll assume “God Does Not Play Dice” is another name for Einstein- Right now IMHO Wikidata has better direct types for persons. This is a shame and we need to fix it in DBpediawithout thinking about how the two could evolve / compete / cooperate / thrive.We exactly have to think about this.Last few months I've been worrying that the two communities don't much talk to each other.
Hmm..We just have to keep on working towards common ground. These two projects are ridiculously complimentary! The only challenge is making that claim utterly obvious so that we reduce "mutual exclusivity" oriented distractions.
We as humanity should leverage the strengths of both, to gain maximum benefits.
Amen! Anything less is an utter shame.
I've become active in both communities, and I feel no shame in such split loyalies.
I don't look a split loyalties. I see a fundamental obligation to put as much effort into getting everyone to see "mutual inclusion" where they currently see "mutual exclusion" . I could have a good old rant about what's been happening here, but it would be misconstrued (on a good day) and only serve to add more distraction to the goals that many of have in mind re. collaboration across all of these structured data projects.
I went to DBpedia Dublin, now'll go to GlamWiki Hague... It's structured data each way!
Yes!
Some little incoherencies:- The DBpedia Extraction framework is a very ingenious thing, and the devs working on it are very smart. But can they compete with a thousand Wikidata bot writers? (plus Magnus who in my mind holds semi-God status)
Yes, but we don't need to look at it that way Be a reluctant warrior.
- Meanwhile, DBpedia can't muster a willing Wikipedia hack to service mappings.dbpedia.org, which is stuck in the stone age. - Wikidatians move around tons of data every day, but their understanding of RDF *as a community* is still a bit naïve.
Yes, so we MUST teach teach teach, at every opportunity. But in a constructive rather than condescending way.
- DBpedia holds tons of structured data, but Wikidata seems to plan to source it by individual bot contributions... maybe in full in 5 years time? - DBpedia has grokked the black magic of dealing with hand-written *multilingual* units and conversions. Of a gazillion units http://mappings.dbpedia.org/index.php/DBpedia_Datatypes Last I looked, Wikidata folks shrugged this off with "too different from our data types" - https://tools.wmflabs.org/mix-n-match/ is a crowdsourcing Wonder upon God's Earth, but nary a DBpedian has heard of it IMHOA Little Cooperation Goes a Long Way.
Amen, one more time ! Kingsley
Cheers! _______________________________________________ Wikidata-l mailing list wikidat...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
-- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog 1: http://kidehen.blogspot.com Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen Twitter Profile: https://twitter.com/kidehen Google+ Profile: https://plus.google.com/+KingsleyIdehen/about LinkedIn Profile: http://www.linkedin.com/in/kidehen Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ Dbpedia-discussion mailing list Dbpedia-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
