[Wikidata] Re: History of some original Wikidata design decisions?

2021-07-26 Thread Jan Dittrich
ny. They are still a nice read. :) >>> >>> 1/3 >>> https://blog.wikimedia.de/2013/02/22/restricting-the-world/ >>> >>> 2/3 >>> https://newwwblog.wikimedia.de/2013/06/04/on-truths-and-lies/ >>> >>> 3/3 >>> https://blog.w

[Wikidata] Report on Wikidata Use in Cultural Institutions

2019-12-05 Thread Jan Dittrich
LAM institutions who showed and explained to us how they use Wikidata. Kind Regards, Jan -- Jan Dittrich UX Design/ Research Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Tel. (030) 219 158 26-0 https://wikimedia.de Unsere Vision ist eine Welt, in der alle Menschen am Wis

Re: [Wikidata] Imperative programming in Lua, do we really want it?

2017-12-08 Thread Jan Dittrich
want something different? >>> >>> John >>> >>> ___ >>> Wikidata mailing list >>> Wikidata@lists.wikimedia.org >>> https://lists.wikimedia.org/mailman/listinfo/wikidata >>> >>> >> >> _

Re: [Wikidata] Wikimedia takes part in Google Code-in. Which small Wikidata tasks do you plan to mentor?

2016-11-09 Thread Jan Dittrich
tps://lists.wikimedia.org/mailman/listinfo/wikidata >> > >> >> >> -- >> Amit Kumar Jaiswal >> [Mozilla Reps](reps.mozilla.org/u/amitkumarj441) >> [Fedora Contributor](https://fedoraproject.org/wiki/User:Amitkumarjaiswal >> ) >> Kanpur | Uttar Pradesh | India &

Re: [Wikidata] use of wdq and wqd create-a-query interface

2016-10-24 Thread Jan Dittrich
lt;https://www.google.com/+ThadGuidry> > > > ___ > Wikidata mailing list > Wikidata@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikidata > > -- Jan Dittrich UX Design/ User Research Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (

Re: [Wikidata] use of wdq and wqd create-a-query interface

2016-10-21 Thread Jan Dittrich
te baseline demand, in > terms of what complexity is required. > > On Thu, Oct 20, 2016 at 1:27 PM Jan Dittrich <jan.dittr...@wikimedia.de> > wrote: > >> Hi Magnus, >> Hi List, >> >> Thanks for your assessment! >> >> > Since "

Re: [Wikidata] use of wdq and wqd create-a-query interface

2016-10-20 Thread Jan Dittrich
-language-to-SPARQL tool somewhere, but I can't > find the URL... > > This is not to say that we shouldn't have, at some point down the road, a > query-building interface that is tailored to our needs! > > My two Eurocent, > Magnus > > > On Thu, Oct 20, 2016 at 12:30 PM Jan Di

[Wikidata] use of wdq and wqd create-a-query interface

2016-10-20 Thread Jan Dittrich
you, don't hesitate to include them. -- Jan Dittrich UX Design/ User Research Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (0)30 219 158 26-0 http://wikimedia.de Imagine a world, in which every single human being can freely share in the sum of all knowledge. T

Re: [Wikidata] List generation input

2016-09-06 Thread Jan Dittrich
pdates/2016_ 09_03 (see the events section) Hope that helps, Jan -- Jan Dittrich UX Design/ User Research Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (0)30 219 158 26-0 http://wikimedia.de Imagine a world, in which every single human being can freely shar

[Wikidata] Dynamic Lists, Was: Re: List generation input

2016-09-05 Thread Jan Dittrich
Hi Gerard (and everyone interested in list generation) Dynamic lists are an interesting point since currently most (manually generated) Lists of Wikipedia are static. I would love to hear more about the issues and workflows around dynamic lists to understand their use better. Some things that are

Re: [Wikidata] List generation input

2016-09-05 Thread Jan Dittrich
Hello Scott, Thanks for your input! If I understand this right, your concern is that there might be lists like "list of species" which are impossible (with several million entries) to have as single list? There is the splitting lists scenario,

Re: [Wikidata] List generation input

2016-09-02 Thread Jan Dittrich
Hi Scott, Thanks for your suggestion! I'd love to have more good information on using Wikidata. I assume, though, that putting it to the Scenarios for *List generation input *maybe not the best place (although the name suggests input in general, and I am guilty of not choosing a more specific