Wikidata April 2012

wikidata@lists.wikimedia.org

73 participants
111 discussions

Re: [Wikidata-l] Hello from the YAGO team
by Nadja Kutz 15 Apr '12

15 Apr '12

I meanwhile found a public accessible link to your publication: http://www.mpi-inf.mpg.de/yago-naga/yago/publications/aij.pdf in which you write: "However, in contrast to the original YAGO, the methodology for building YAGO2 (and also maintaining it) is systematically designed top-down with the goal of integrating entity-relationship-oriented facts with the spatial and tempo- ral dimensions. To this end, we have developed an extensible approach to fact extraction from Wikipedia and other sources, and we have tapped on specific inputs that contribute to the goal of enhancing facts with spatio-temporal scope. Moreover, we have developed a new representation model, coined SPOTL tuples (SPO + Time + Location), which can co-exist with SPO triples, but provide a much more convenient way of browsing and querying the YAGO2 knowl- edge base. " etc. page 3 so it seems one special feature is the explicit treatment of space and time, which sounds interesting. So I would like make some of my questions more precise "YAGO has about 100 manually defined relations, such as wasBornOnDate, locatedIn and hasPopulation. Categories and infoboxes can be exploited to deliver instances of these relations. (p.3) " ... "The new YAGO2 architecture is based on declarative rules that are stored in text files." -Is there a wiki or some other public accessible place for those like the mapping wiki of dbpedia? -what do you do if infoboxes change? -How do you treat microformats? "Instead of seeing only SPO triples and thus having to perform an explicit de-reification join for associated meta-facts, the user should see extended 5-tuples where each fact already includes its associated temporal and spatial information. We refer to this view of the data as the SPOTL view: SPO triples augmented by Time and Location. We also discuss a further optional extension into SPOTLX 6-tuples where the last component offers keywords or key phrases from the conteXt of sources where the original SPO fact occurs.(p. 20)" It is not yet fully clear to me how your concept go together with other concepts to include contexts like with named graphs or with the inclusion of context-ontologies within formats like JSON-LD, eventually that would need a longer discussion, are you planning to set up a wiki page on datawiki, like for example there is one for JSON-LD: http://meta.wikimedia.org/wiki/Talk:Wikidata/Data_model/JSON ? Is it possible to extract the Yago queries in some RDF serialization format?

1 0

Re: [Wikidata-l] Hello from the YAGO team
by Nadja Kutz 14 Apr '12

14 Apr '12

Hello Fabian, Is it possible to briefly explain the major differences between DBpedia and the Yago Knowledge graph? what is the www conference ? nad

1 0

Re: [Wikidata-l] weekly summary #1
by Sylvain Boissel 14 Apr '12

14 Apr '12

2012/4/14 JFC Morfin <jefsey(a)jefsey.com> > Lydia, > May be you could create and maintain http://meta.wikimedia.org/** > wiki/Wikidata/Status_updates/<http://meta.wikimedia.org/wiki/Wikidata/Status_updates/>as a menu page for all the monthly reports? This way we could quote and use > it as a single permanent URL for the Status Reports. > Thank you and best JFC, http://meta.wikimedia.org/wiki/Wikidata/Status_updates already exists. Regards, Sylvain. -- Sylvain Boissel Chargé de mission communauté et technologie de Wikimédia France tél 07.62.93.42.02 - email sylvain.boissel(a)wikimedia.fr - twitter @sboissel<https://twitter.com/#!/sboissel> *Imaginez un monde où chaque personne sur la planète aurait librement accès à la totalité du savoir humain. C'est notre engagement. Aidez Wikimedia France à en faire une réalité <https://dons.wikimedia.fr>.* www.wikimedia.fr

1 0

Re: [Wikidata-l] weekly summary #1
by JFC Morfin 14 Apr '12

14 Apr '12

At 13:44 13/04/2012, Lydia Pintscher wrote: >Content-Transfer-Encoding: base64Heya folks :) > >I'll be doing weekly summaries of what's been happening around >Wikidata. This is the first one. The plan is to collect them and then >make a blog post out of them every month. Lydia, May be you could create and maintain http://meta.wikimedia.org/wiki/Wikidata/Status_updates/ as a menu page for all the monthly reports? This way we could quote and use it as a single permanent URL for the Status Reports. Thank you and best jfc PS. As you can see: the way you entered that mail made it readable (with LF between the lines)? >The wiki version of this can be found at >http://meta.wikimedia.org/wiki/Wikidata/Status_updates/2012_04_13 > >= Development = >* drafted http://meta.wikimedia.org/wiki/Wikidata/Data_model >* drafted http://meta.wikimedia.org/wiki/Wikidata/Notes/API >* http://meta.wikimedia.org/wiki/Wikidata/Development has useful infos >for setting up a dev environment (but you probably want to wait a bit >with that still until we've worked out some more quirks) >* finished first scrum cycle: >http://meta.wikimedia.org/wiki/Wikidata/Development/Scrum_cycle_archive >** implemented the data grid view which basically is an overview page >for the data of one Wikidata item >** implemented basic functionality for editing some of the information >in data grid dynamically (item label and description) with a >JavaScript generated user interface >** lots of struggling with git >** created proper base for Wikibase and Wikibase Client extensions, >including things such as i18n files, settings files, and a skeleton >for the API >** created skeleton pages for the extensions on MediaWiki.org: >https://www.mediawiki.org/wiki/Extension:Wikibase and >https://www.mediawiki.org/wiki/Extension:Wikibase_Client >** WikibaseClient extension has its basic functionality implemented. >Whenever a page is rendered, the extension loads the information about >interlanguage links from the repository, sorts the links, and displays >them. >** WikibaseClient extension also defines a new magic word/parser >function {{NOEXTERNALINTERLANG}}. It can disable fetching the links >from the repository completely (when used on its own as >{{NOEXTERNALINTERLANG}} or with asterisk as a parameter as >{{NOEXTERNALINTERLANG:*}}), or just remove the links for certain >languages (for example {{NOEXTERNALINTERLANG:de|fr}} will remove the >links to German and French). It remains possible to add new >interlanguage links just like it is now and the new links will be >sorted together with the external interlanguage links. >* start of second scrum cycle: >http://meta.wikimedia.org/wiki/Wikidata/Development/Current_scrum_cycle > >You can follow commits at >https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/WikidataClient… >and >https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/WikidataRepo.g… >(stuff not merged into master yet isn't included there) > >= Diskussions/Press = >* Kurier: https://de.wikipedia.org/wiki/Wikipedia_Diskussion:Kurier#Wikidata >(This will probably be archived soon. I will summarize and address the >comments there in a blog post in the next days.) >* The Atlantic: >http://www.theatlantic.com/technology/archive/2012/04/the-problem-with-wiki… >(please also read Denny's important comment there) >* Signpost: >http://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2012-04-09/Wikida… > >= Events = >* held first office hours on IRC (logs at >http://meta.wikimedia.org/wiki/Wikidata/Events#IRC_office_hours) >* attended/presented at the Berlin Semantic Web meetup: >http://www.meetup.com/The-Berlin-Semantic-Web-Meetup-Group/events/56299712/ >* upcoming: WWW2012: http://meta.wikimedia.org/wiki/Wikidata/Events > >= other stuff = >* published team intro: >http://blog.wikimedia.de/2012/04/04/meet-the-wikidata-team/ >* published some basic assumptions and requirements: >http://meta.wikimedia.org/wiki/Wikidata/Notes/Requirements >* search for an initial logo: >http://meta.wikimedia.org/wiki/Talk:Wikidata#WikiData_logo_candidate >and http://commons.wikimedia.org/wiki/Category:Wikidata_logo_proposals >(still have to get to promoting this and making this less painful) >* volunteer page started: http://meta.wikimedia.org/wiki/Wikidata/Volunteers >* collecting use-cases: >http://meta.wikimedia.org/wiki/Wikidata/Queries and >http://meta.wikimedia.org/wiki/Wikidata/Infoboxes > >If you have anything to add please share it. > > >Cheers >Lydia > >PS: In case you have not seen it yet I'm posting daily updates on >twitter and identi.ca (@wikidata). > >-- >Lydia Pintscher - http://about.me/lydia.pintscher >Community Communications for Wikidata > >Wikimedia Deutschland e.V. >Obentrautstr. 72 >10963 Berlin >www.wikimedia.de > >Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. > >Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg >unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das >Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985. > >_______________________________________________ >Wikidata-l mailing list >Wikidata-l(a)lists.wikimedia.org >https://lists.wikimedia.org/mailman/listinfo/wikidata-l

1 0

[Wikidata-l] Linked Data Cup - Deadline Extension until April 25th, 2012
by Sebastian Hellmann 13 Apr '12

13 Apr '12

(apologies for multiple posts; please forward; please email i-challenge2012_a_t_easychair.org for questions) ******************** NEWS: - Deadline extension until April 25th, 2012 - The total amount of 2,000 EUR (sponsored by Wolters Kluwer) will be awarded in prizes and split among the most promising applications. - Linked Data Cup Board updated: http://i-challenge.blogs.aksw.org/chairs-committee ******************** Linked Data Cup 2012 http://i-challenge.blogs.aksw.org/ co-located with the I-Semantics 2012 Graz, Austria, 5 - 7 September 2012 http://www.i-semantics.at ******************** The yearly organised Linked Data Cup (formerly Triplification Challenge) awards prizes to the most promising innovation involving linked data. Four different technological topics are addressed: triplification, interlinking, cleansing, and application mash-ups. The Linked Data Cup invites scientists and practitioners to submit novel and innovative (5 star) linked data sets and applications built on linked data technology. Although more and more data is triplified and published as RDF and linked data, the question arises how to evaluate the usefulness of such approaches. The Linked Data Cup therefore requires all submissions to include a concrete use case and problem statement alongside a solution (triplified data set, interlinking/cleansing approach, linked data application) that showcases the usefulness of linked data. Submissions that can provide measurable benefits of employing linked data over traditional methods are preferred. Note that the call is not limited to any domain or target group. We accept submissions ranging from value-added business intelligence use cases to scientific networks to the longest tail [1] of information domains. The only strict requirement is that the employment of linked data is very well motivated and also justified (i.e. we rank approaches higher that provide solutions, which could not have been realised without linked data, even if they lack technical or scientific brilliance). The total amount of 2,000 EUR (sponsored by Wolters Kluwer) will be awarded in prizes and split among the most promising applications. Evaluation Criteria =================== The submissions will be initially evaluated with a well-known five star ranking system [2]. Furthermore, entries will be assessed according to the extent to which they 1. motivate the relevancy of their use case for their respective domain; 2. justify the adequacy of linked data technologies for their solution; 3. demonstrate that all alternatives to linked data would have resulted in an inferior solution; 4. provide an evaluation that can measure the benefits of linked data Topics ====== Ideas for topics include (but are not limited to): * Improving traditional approaches with help of linked data * Linked data use in science and education * Linked data supported multimedia applications * Linked data in the open source context * Web annotation * Generic applications * Internationalization of linked data * Visualization of linked data * Linked government data * Business models based on linked data * Recommender systems supported by linked data * Integrating microposts with linked data * Distributed social web based on linked data * Linked data sensor networks Submission and Reviewing ======================== Submissions to the Linked Data Cup will be reviewed by members of the Linked Data Cup Board and invited experts from the Linked Data community. Submissions should consist of 4 pages and must be original and must not have been submitted for publication elsewhere. Papers should follow the ACM ICPS guidelines for formatting as accepted submissions will be published in the I-SEMANTICS 2012 proceedings in the digital library of the ACM ICP series. Please read the submission page[a] for detailed information on how to submit. Important Dates (Linked Data Cup) 1. Paper Submission Deadline: April 25, 2012 2. Notification of Acceptance: May 21, 2012 3. Camera-Ready Paper: June 11, 2012 Links ===== [1] http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=uleiauersemmedmainz20… [2] http://www.w3.org/DesignIssues/LinkedData.html -- Dipl. Inf. Sebastian Hellmann Department of Computer Science, University of Leipzig Projects: http://nlp2rdf.org , http://dbpedia.org Homepage: http://bis.informatik.uni-leipzig.de/SebastianHellmann Research Group: http://aksw.org

1 0

[Wikidata-l] Hello from the YAGO team
by Fabian M. Suchanek 13 Apr '12

13 Apr '12

Dear Wikidata team, I am writing on behalf of the YAGO team at the Max Planck Institute for Informatics in Saarbruecken [1]. We have heard about the Wikidata project, and we are very excited to learn that you aim to launch a free knowledge base in the spirit of Wikipedia. We would like to get in touch with you -- also to see whether or how we could help on the long run. Let me briefly tell you what we have on our side: As you might know, YAGO is knowledge graph that has been extracted automatically from the infoboxes and categories of Wikipedia. We have evaluated YAGO manually and achieved a precision of 95%, meaning that statistically speaking, only 5 out of 100 statements in the knowledge graph are extracted wrongly. We also have a link of the Wikicategories to the WordNet taxonomy (again with 95% precision), and type checking methods for the extracted statements. Should these things ever be useful to you, we would be happy to help. I will be at the WWW conference next week. In case some of you are there, too, I'd be happy to get in touch to learn more about your current work. Thanks Fabian [1] http://yago-knowledge.org -- Thanks Fabian -- Fabian online: http://suchanek.name

2 1

[Wikidata-l] weekly summary #1
by Lydia Pintscher 13 Apr '12

13 Apr '12

Heya folks :) I'll be doing weekly summaries of what's been happening around Wikidata. This is the first one. The plan is to collect them and then make a blog post out of them every month. The wiki version of this can be found at http://meta.wikimedia.org/wiki/Wikidata/Status_updates/2012_04_13 = Development = * drafted http://meta.wikimedia.org/wiki/Wikidata/Data_model * drafted http://meta.wikimedia.org/wiki/Wikidata/Notes/API * http://meta.wikimedia.org/wiki/Wikidata/Development has useful infos for setting up a dev environment (but you probably want to wait a bit with that still until we've worked out some more quirks) * finished first scrum cycle: http://meta.wikimedia.org/wiki/Wikidata/Development/Scrum_cycle_archive ** implemented the data grid view which basically is an overview page for the data of one Wikidata item ** implemented basic functionality for editing some of the information in data grid dynamically (item label and description) with a JavaScript generated user interface ** lots of struggling with git ** created proper base for Wikibase and Wikibase Client extensions, including things such as i18n files, settings files, and a skeleton for the API ** created skeleton pages for the extensions on MediaWiki.org: https://www.mediawiki.org/wiki/Extension:Wikibase and https://www.mediawiki.org/wiki/Extension:Wikibase_Client ** WikibaseClient extension has its basic functionality implemented. Whenever a page is rendered, the extension loads the information about interlanguage links from the repository, sorts the links, and displays them. ** WikibaseClient extension also defines a new magic word/parser function {{NOEXTERNALINTERLANG}}. It can disable fetching the links from the repository completely (when used on its own as {{NOEXTERNALINTERLANG}} or with asterisk as a parameter as {{NOEXTERNALINTERLANG:*}}), or just remove the links for certain languages (for example {{NOEXTERNALINTERLANG:de|fr}} will remove the links to German and French). It remains possible to add new interlanguage links just like it is now and the new links will be sorted together with the external interlanguage links. * start of second scrum cycle: http://meta.wikimedia.org/wiki/Wikidata/Development/Current_scrum_cycle You can follow commits at https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/WikidataClient… and https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/WikidataRepo.g… (stuff not merged into master yet isn't included there) = Diskussions/Press = * Kurier: https://de.wikipedia.org/wiki/Wikipedia_Diskussion:Kurier#Wikidata (This will probably be archived soon. I will summarize and address the comments there in a blog post in the next days.) * The Atlantic: http://www.theatlantic.com/technology/archive/2012/04/the-problem-with-wiki… (please also read Denny's important comment there) * Signpost: http://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2012-04-09/Wikida… = Events = * held first office hours on IRC (logs at http://meta.wikimedia.org/wiki/Wikidata/Events#IRC_office_hours) * attended/presented at the Berlin Semantic Web meetup: http://www.meetup.com/The-Berlin-Semantic-Web-Meetup-Group/events/56299712/ * upcoming: WWW2012: http://meta.wikimedia.org/wiki/Wikidata/Events = other stuff = * published team intro: http://blog.wikimedia.de/2012/04/04/meet-the-wikidata-team/ * published some basic assumptions and requirements: http://meta.wikimedia.org/wiki/Wikidata/Notes/Requirements * search for an initial logo: http://meta.wikimedia.org/wiki/Talk:Wikidata#WikiData_logo_candidate and http://commons.wikimedia.org/wiki/Category:Wikidata_logo_proposals (still have to get to promoting this and making this less painful) * volunteer page started: http://meta.wikimedia.org/wiki/Wikidata/Volunteers * collecting use-cases: http://meta.wikimedia.org/wiki/Wikidata/Queries and http://meta.wikimedia.org/wiki/Wikidata/Infoboxes If you have anything to add please share it. Cheers Lydia PS: In case you have not seen it yet I'm posting daily updates on twitter and identi.ca (@wikidata). -- Lydia Pintscher - http://about.me/lydia.pintscher Community Communications for Wikidata Wikimedia Deutschland e.V. Obentrautstr. 72 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.

2 1

Re: [Wikidata-l] Fwd: [Wiki-research-l] Wikidata opinion piece in The Atlantic
by JFC Morfin 13 Apr '12

13 Apr '12

At 11:36 13/04/2012, Jeroen De Dauw wrote: >Hey, >I've been following the usage of WikiData on twitter, and for the >last week or so, more then half the tweets have been pointing to >this article. Apparently people like to criticize :) To discuss something fundamental is not criticizing. This article raises a problem we know very well à the different (linguistic, telecom, network) strata below (diversity, orthotypography, normalization, informatics, canonization, globalization, internationalization, etc. ) which now touches the semantical and intellectual strata. Engineering issues, as discussed here, are for the technical processes to work better. The problem is to determine what "better" societaly means in an "antropobotical" society (persons/robots) like ours - broadly influenced by its daily experience of Wikipedia. This leads to fundamental questions on the Freedom of Knowledge. The difficulty is the resulting ethical/technical loop and the impact on engineering orientations. jfc

1 0

[Wikidata-l] (no subject)
by Leonard Wallentin 13 Apr '12

13 Apr '12

http://300.co/114la/html/zhaoshangjiameng/epffs.html?u=uf.aabaa&bmj=ppz.aar…

1 0

[Wikidata-l] JSON-LD Provenance use case
by Gregg Kellogg 12 Apr '12

12 Apr '12

I updated the JSON Talk page [1] with an example of using the JSON-LD named-graph syntax to express provenance information about some facts, based on a discussion of the use case in the W3C RDF Working Group [2] trying to express the following: ParisFact1 expresses "Paris locatedIn France ." ParisFact1 hasReference EncyclopediaBritannica, Wikipedia, Brockhaus. ParisFact2 Paris hasPopulation 7000000^^int ParisFact2 hasReference Wikipedia The JSON-LD looks like the following: { "@context": { "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#", "ex": "http://example.org/", "xsd": "http://www.w3.org/2001/XMLSchema#", "ex:locatedIn": {"@type": "@id"}, "ex:hasPopulaton": {"@type": "xsd:integer"}, "ex:hasReference": {"@type": "@id"} }, "@graph": [ { "@id": "http://example.org/ParisFact1", "@type": "rdf:Graph", "@graph": { "@id": "http://example.org/location/Paris#this", "ex:locatedIn": "http://example.org/location/France#this" }, "ex:hasReference": ["http://www.britannica.com/", "http://www.wikipedia.org/", "http://www.brockhaus.de/"] }, { "@id": "http://example.org/ParisFact2", "@type": "rdf:Graph", "@graph": { "@id": "http://example.org/location/Paris#this", "ex:hasPopulation": 7000000 }, "ex:hasReference": "http://www.wikipedia.org/" } ] } Which could be expressed in TriG as: @prefix ex: <http://example.org/> . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . { ex:ParisFact1 a rdf:Graph; ex:hasReference <http://www.britannica.com/>, <http://www.wikipedia.org/>, <http://www.brockhaus.de/> . ex:ParisFact2 a rdf:Graph; ex:hasReference <http://www.wikipedia.org/> . } ex:ParisFact1 { <http://example.org/location/Paris#this> ex:locatedIn <http://example.org/location/France#this> . } ex:ParisFact2 { <http://example.org/location/Paris#this> ex:hasPopulation 7000000 . } Note that JSON-LD recently added support for named graphs [3]. Gregg [1] http://meta.wikimedia.org/wiki/Talk:Wikidata/Data_model/JSON [2] http://www.w3.org/2011/rdf-wg/wiki/TF-Graphs-UC#.28C_priority.29_Wikidata [3] http://json-ld.org/spec/latest/json-ld-syntax/#named-graphs Gregg

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Wikidata April 2012