Wikidata September 2014

wikidata@lists.wikimedia.org

56 participants
37 discussions

[Wikidata-l] Lighthouse
by Markus Bärlocher 26 Sep '14

26 Sep '14

Liebe WD-Spezialisten, OpenSeaMap möchte die Leuchtfeuer-Daten in WD verbessern :-) Test: https://www.wikidata.org/w/index.php?title=Q1821432&uselang=de _Quelle_ Habe eine neue Quelle für die Koordinate eingefügt. Da steht jetzt die neue Koordinate, und als Quelle "OSM". Wie kann ich die Quelle genau angeben: https://www.openstreetmap.org/node/330119702 _neue Aussage_ Mit Name und Koordinate und "Bauwerk" ist das Objekt unzureichend beschrieben ;-) - Wie kann ich weitere "Aussagen" hinzufügen? - Wie definiere ich die "Struktur" einer Aussage? (z.B. "range=<Tragweite in Seemeilen>") - Wie kann ich dafür sorgen, dass diese Aussagen /allen/ Objekten in der Kategorie "Lighthouse" zur Auswahl angeboten werden? - Wie erzeuge ich eine Kategorie "Lighthouse" bzw. "Nautical light"? - Wie erzeuge ich Unterkategorien? Vielleicht kann das hier jemand nachvollziehbar erklären (deutsch) und am Beispiel "Kiel" exemplarisch umsetzen? Wäre super! _Verlinkung_ Wie kann man automatisch einfügen: - WD-Link in das korrespondierende OSM-Objekt - WD-Link in WP (ist vermutlich über WD automatisch verlinkt?) - OSM-Link in WD - OSM-Link in WP (ist vermutlich über WD automatisch verlinkt?) - WP-Links in WD (ist vermutlich über WD automatisch verlinkt?) - WP-Link in OSM (ist vermutlich über WD automatisch verlinkt?) Wie findet WD alle relevanten WP-Versionen? Wie findet WD die relevante Commons-Kategorie? Mit herzlichem Gruss, Markus

3 3

[Wikidata-l] Why? Modeling causes on Wikidata
by Emw 24 Sep '14

24 Sep '14

Hi all, Talk about causes is ubiquitous in everyday life and many other domains of knowledge. Until recently, we've had a few properties to make statements about cause in certain narrow areas, but lacked a way to structure data about causes across a broad range of subjects. For example, you might want to know: - What caused World War II? - What causes evolution? - What causes malaria? - What causes bread to rise? - What causes rust? - What causes gravity? - What causes rainbows? Wikidata now has some new properties that provide structure for basic answers to such questions. - *has cause* (alias: *has underlying cause*): thing that ultimately resulted in the effect [1] - *has immediate cause*: thing that proximately resulted in the effect [2] - *has contributing factor*: thing that significantly influenced the effect, but did not directly cause it [3] This approach to modeling causation attempts to balance expressiveness with simplicity. It borrows from the idea of causation as a "chain of events", which also has background conditions or events that set the stage for some outcome. These properties are not perfect, but they do allow us to capture much richness in how various sources talk about causes -- and to do so in a way that humans can easily understand. https://www.wikidata.org/wiki/Help:Modeling_causes explains these properties, their background, examples, things to avoid, issues and context. Please comment on the 'Help:Modeling causes' talk page, or here, with any feedback. Hopefully we'll be able to build some cool stuff with this. Cheers, Eric https://www.wikidata.org/wiki/User:Emw 1. *has cause*. https://www.wikidata.org/wiki/Property:P828 2. *has immediate cause. *https://www.wikidata.org/wiki/Property:P1478 3. *has contributing factor.* https://www.wikidata.org/wiki/Property:P1479

2 1

[Wikidata-l] Welcome Jan!
by Lydia Pintscher 18 Sep '14

18 Sep '14

Hey folks :) I'm happy to let you know that Jan Zerebecki has joined the Wikidata dev team. Some of you surely met him at previous hackathons and Wikimania. He will be supporting the dev team on the backend-side. Previously Jan has already been helping out as a volunteer around Wikimedia in many areas - most notably ops. Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher Product Manager for Wikidata Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 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.

3 2

[Wikidata-l] Commons Wikibase
by Derric Atzrott 17 Sep '14

17 Sep '14

Hey, So I heard on another mailing list that Commons is getting its own installation of Wikibase along with using Wikidata? Is this true, and if so, where might I find more information about it? Thank you, Derric Atzrott Computer Specialist Alizee Pathology

16 67

[Wikidata-l] Wikidata / Wikipedia integration : redlinks and items
by Thomas Douillard 15 Sep '14

15 Sep '14

Hi all, I'm wondering about one usage Wikidata could be useful to Wikipedias : Redlinks subject identification. Wikidata is good to identify subjects. Redlinks are used in Wikipedias to identify subjects with currently no article. I post here because I think there is something to integrate this further, but I don't know exactly what. A quick review about the current mechanisms we have to link items and/or articles and subjects together : * Wikidata interwikis. This works well. Links an item to articles and articles titles * articles redirect. This also works well, now we have a mechanism to link article redirects with items, which is cool. * There is currently templates like https://www.wikidata.org/wiki/Q6519884 or https://www.wikidata.org/wiki/Q15977575 Interesting mechanisms actually * Wikidata items aliases : links a set of lexemes to an item * Special:ItemByTitle and Special:GoToLinkedPage which are great, I don't know how much they are used in practice though A little bit different but close * items redirects This seems this covers a lot of the user usecases. Yet there is a lot of red links in Wikipedia with actually no links to a Wikidata item. My feeling is that what actually lacks in this picture is that the templates are a bit hackish and that a deeper integration of item numbers with redlinks would allow to go further and encourage users to make the links at an earlier stage. What about a Wikisyntax to put an item number into a Wikilink or a visual editor integration to suggest an entity every time a user wants to enter a redlink ? This seems a low hanging fruit for WIkidata development and could make Wikidata more real to Wikipedia communities. Especially compared to doing this at the community level where this would require a big maintenance effort and community knowledge about the templates to make the link beetween the red label and the corresponding item concrete, especially if visual editor make the information come to eveyone. One other solution could be to allow to associate items to yet non existing articles to "reserve" them, allow redlinks into the Wikidata interwiki list ?

10 11

[Wikidata-l] breaking changes for gadgets
by Lydia Pintscher 15 Sep '14

15 Sep '14

Hey folks, We are working on re-vamping a lot of the underlying code for the user interface at the moment. These changes are the first major steps for the new user interface. They are necessary to allow editing all sitelinks or label/description/alsiases at once for example. Unfortunately some gadgets will need to be adapted to these changes. Specifically it is the introduction of sitelinkview and aliasview. We are aware of the following gadgets that will need to be adapted but those might not be all: MediaWiki:Gadget-DraggableSitelinks.js MediaWiki:Gadget-KeyShortcuts.js MediaWiki:Gadget-MainLangFirst.js MediaWiki:Gadget-Move.js MediaWiki:Gadget-Preview.js MediaWiki:Gadget-SimpleTransliterate.js The new code is live on test.wikidata.org for you to test your gadgets against. The changes will go live on wikidata.org on Tuesday. Sorry for the breaking change. I hope the new UI will be worth it for you though :) Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher Product Manager for Wikidata Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 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 2

[Wikidata-l] integration of VisualEditor and Wikidata
by Amir E. Aharoni 14 Sep '14

14 Sep '14

Hi, There are plenty of ways in which Wikidata and VisualEditor could be integrated. Let me ask about the following one: Given: Let's imagine that the venerable {{Infobox settlement}} template is fully adapted for pulling the data from Wikidata. All the relevant data about the city of Bratislava is entered into its item page on wikidata.org, and in the source of the article [[Bratislava]] you only need to say {{Infobox settlement}} without any parameters. The people of Bratislava elect a new mayor, and I want to write it in the article. I come to the article [[Bratislava]] and press edit. I click the infobox. What happens? As far as I know, no work has been done in this area; PLEASE CORRECT ME if I'm wrong. My Super-Dream scenario is to be able to edit the Mayor's name write there in the infobox, but I realize that it might be complicated. My Dream scenario is that the VE understands that the data is pulled from Wikidata and shows a dialog that is similar to the current template parameters. I see the old mayor's name in that dialog, I write the new mayor's name, and the new value is stored in Wikidata. Of course, it must be taken into account that the name is likely not just a string, but a label of the Wikidata item. My acceptable-but-suboptimal scenario is taking the user to https://www.wikidata.org/wiki/Q6850543 . This is probably a useful workflow for the tech-savvy editors, but it's suboptimal for a casual editor. I'll go as far as saying that for a casual editor it may be (relatively) more comfortable to edit parameters in a MediaWiki template ("|mayor =[[Milan Ftáčnik]]") than to go to https://www.wikidata.org/wiki/Q6850543 and find the value. Does anybody have any more ideas about it? Am I late to the party and this has already been discussed and designed and I missed it? Please enlighten me :) Thanks! -- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com ‪“We're living in pieces, I want to live in peace.” – T. Moore‬

10 21

[Wikidata-l] Weekly Summary #125
by John Lewis 14 Sep '14

14 Sep '14

Hello everyone, Here is the latest weekly summary covering all the Wikidata things over the past two weeks! https://www.wikidata.org/wiki/Wikidata:Status_updates/2014_09_13 Apologies from Lydia and myself about not producing one last week :) John Lewis

1 0

[Wikidata-l] Making a Wikipedia article link to two wikidata items
by Edward Betts 14 Sep '14

14 Sep '14

The Wikipedia article about Wangerooge describes an island and municipality. https://en.wikipedia.org/wiki/Wangerooge These two concepts, island and municipality, have discrete items. Municipality: https://www.wikidata.org/wiki/Q25135 Island: https://www.wikidata.org/wiki/Q17081143 I would like Q17081143 to point to the Wangerooge Wikipedia article, but adding the link gives this error: > The link enwiki:Wangerooge is already used by item Q25135. You may remove it > from Q25135 if it does not belong there or merge the items if they are about > the exact same topic. How can we fix this? -- Edward.

12 16

Re: [Wikidata-l] policy toward using non-CC0 licensed external databases a
by Denny Vrandečić 13 Sep '14

13 Sep '14

On Sep 13, 2014 3:20 PM, "P. Blissenbach" <publi(a)web.de> wrote: > > Regarding purely factual data comprising a less than significant portion of a > database - which is certainly true for all ISBNs in Googles databas > Btw. if a statement about an ISBN is sourced, among ohers, with "Source: Google", > that does not imply having it from Google. It only states the fact: "Google has > it, too." > > Purodha That's also why it is actually called "reference" and not "source".

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Wikidata September 2014