[Wikidata] (Ab)use of "deprecated"

Dear all, As you may know, statements in Wikidata can be marked as "preferred" or "deprecated" to distinguish them from the "normal" ones. I found that many items have perfectly valid historical statements marked as "deprecated". For example, our showcase item "Kleinmachnow" https://www.wik

Re: [Wikidata] Breaking change in JSON serialization?

Dear all, There have been some interesting discussions about breaking changes here, but before we continue in this direction, let me repeat that I did not start this thread to define what is a "breaking change" in JSON. There are JSON libraries that define this in a strict way (siding with Pe

Re: [Wikidata] Breaking change in JSON serialization?

On 08/11/2016 01:35 PM, Stas Malyshev wrote: > Hi! > >> My view is that this tool should be extremely cautious when it sees new data >> structures or fields. The tool should certainly not continue to output >> facts without some indication that something is suspect, and preferably >> should refus

Re: [Wikidata] (Ab)use of "deprecated"

Hi! > I would argue that this is better done by using qualifiers (e.g. start > data, end data). If a statement on the population size would be set to > preferred, but isn't monitored for quite some time, it can be difficult > to see if the "preferred" statement is still accurate, whereas a > qual

Re: [Wikidata] Breaking change in JSON serialization?

Hi! > My view is that this tool should be extremely cautious when it sees new data > structures or fields. The tool should certainly not continue to output > facts without some indication that something is suspect, and preferably > should refuse to produce output under these circumstances. I don

Re: [Wikidata] (Ab)use of "deprecated"

On 11.08.2016 18:45, Andra Waagmeester wrote: On Thu, Aug 11, 2016 at 4:15 PM, Markus Kroetzsch mailto:markus.kroetz...@tu-dresden.de>> wrote: has a statement "population: 20,086 (point in time: 2011)" that is confirmed by a reference. Nevertheless, the statement is marked as "depre

Re: [Wikidata] ArticlePlaceholder is now live on Welsh and Kannada Wikipedia

Great, Lydia, Lucie and All, Thanks for these important ArticlePlaceholder developments. What are further steps ahead for Content Translation in these regards? For example, how best to chart out a possible path to an Universal Translator in Wikipedia's 358 languages from where we are now? What's n

Re: [Wikidata] (Ab)use of "deprecated"

On Thu, Aug 11, 2016 at 4:15 PM, Markus Kroetzsch < markus.kroetz...@tu-dresden.de> wrote: > > has a statement "population: 20,086 (point in time: 2011)" that is > confirmed by a reference. Nevertheless, the statement is marked as > "deprecated". This would mean that the statement "the popluation

[Wikidata] Job Vacancy Textmining, Hannover

Dear all, we have a vacancy in our group on text mining in Open Access publications. The results of the text mining process will be stored using Wikidata infrastructure. The position is for three years with a possibility of extension. The Job is part of a new project "NOA - The replication of

Re: [Wikidata] (Ab)use of "deprecated"

On Thu, Aug 11, 2016 at 4:15 PM, Markus Kroetzsch wrote: > Dear all, > > As you may know, statements in Wikidata can be marked as "preferred" or > "deprecated" to distinguish them from the "normal" ones. > > I found that many items have perfectly valid historical statements marked as > "deprecated

Re: [Wikidata] Controversy around Wikimania talks

On 11 August 2016 at 12:57, David Cuenca Tudela wrote: >> what is the function of all the policies when they so obviously are hardly >> worth the bits they consist of. > > Policies are not commands that have to be blindly obeyed. They are a general > framework for the admins and users to approach

Re: [Wikidata] Controversy around Wikimania talks

I kindly ask to stop this discussion here, and to discuss the relevant topics in the relevant places - on Wikidata, on Meta, or wherever you feel like it, just not here. Thank you. L. ___ Wikidata mailing list Wikidata@lists.wikimedia.org https://lists

Re: [Wikidata] Controversy around Wikimania talks

Hoi, I do not care for "policies" that are only there for some and not for others. I do not care to be told that I am wrong because of the policy and at the same time to notice that policies are arbitrarily enforced. This is not one such situation. One person who has the power deleted many items an

Re: [Wikidata] Breaking change in JSON serialization?

On 08/05/2016 08:57 AM, Daniel Kinzler wrote: > Am 05.08.2016 um 17:34 schrieb Peter F. Patel-Schneider: >> So some additions are breaking changes then. What is a system that consumes >> this information supposed to do? If the system doesn't monitor announcements >> then it has to assume that an

Re: [Wikidata] Breaking change in JSON serialization?

My view is that any tool that imports external data has to be very cautious about additions to the format of that data absent strong guarantees about the effects of these additions. Consider a tool that imports the Wikidata JSON dump, extracts base facts from the dump, and outputs these facts in s

Re: [Wikidata] Render sparql queries using the Histropedia timeline engine

On 11.08.2016 13:40, Daniel Kinzler wrote: Hi Navino! Thank you for your awesome work! Since this has caused some confusion again recently, I want to caution you about a major gotcha regarding dates in RDF and JSON: they use different conventions to represent years BCE. I just updated our JSON

Re: [Wikidata] Render sparql queries using the Histropedia timeline engine

Yay, fun indeed! I can see all of the BCE dates are out by one on the timeline, will get that fixed. Thanks a lot for updating the JSON spec and filling me in on the details, that's cleared a few things up :-) On 11 Aug 2016 12:40, "Daniel Kinzler" wrote: > Hi Navino! > > Thank you for your awe

Re: [Wikidata] Controversy around Wikimania talks

> what is the function of all the policies when they so obviously are hardly worth the bits they consist of. Policies are not commands that have to be blindly obeyed. They are a general framework for the admins and users to approach the blurry or defined limits, but of course some autonomy is need

Re: [Wikidata] Render sparql queries using the Histropedia timeline engine

Hi Navino! Thank you for your awesome work! Since this has caused some confusion again recently, I want to caution you about a major gotcha regarding dates in RDF and JSON: they use different conventions to represent years BCE. I just updated our JSON spec to reflect that reality, see

Re: [Wikidata] Controversy around Wikimania talks

Hoi, What is trivial. I find that the disappointment in what our policies bring us amounts to a lot. Effectively it is only who you are that determines what you get away with. The quality of arguments are easily dismissed with "I have a different opinion" (that is NOT an argument. When you look at

Re: [Wikidata] ArticlePlaceholder is now live on Welsh and Kannada Wikipedia

Hoi, As to search, Magnus already did that over a year ago. Thanks, GerardM On 10 August 2016 at 18:56, Lydia Pintscher wrote: > Hey folks :) > > Just a quick note that we have now rolled out the ArticlePlaceholder > on Welsh and Kannada Wikipedia as well. Both project had requested it. >