Re: [Wikidata-tech] how is the datetime value with precision of one year stored

2015-09-01 Thread Richard Light
On 01/09/2015 09:26, Markus Krötzsch wrote: On 01.09.2015 05:17, Stas Malyshev wrote: Hi! I would have thought that the correct approach would be to encode these values as gYear, and just record the four-digit year. While we do have a ticket for that

Re: [Wikidata-tech] how is the datetime value with precision of one year stored

2015-09-01 Thread Markus Krötzsch
On 01.09.2015 05:17, Stas Malyshev wrote: Hi! I would have thought that the correct approach would be to encode these values as gYear, and just record the four-digit year. While we do have a ticket for that (https://phabricator.wikimedia.org/T92009) it's not that simple since many triple

Re: [Wikidata-tech] API JSON format for warnings

2015-09-01 Thread Markus Krötzsch
On 01.09.2015 16:57, Thiemo Mättig wrote: Hi, > I now identified another format for API warnings [...] from action "watch" I'm not absolutely sure, but I think this is not really an other format. The "warnings" field contains a list of modules. For each module you can either have a list of

Re: [Wikidata-tech] API JSON format for warnings

2015-09-01 Thread Tom Morris
On Tue, Sep 1, 2015 at 7:45 AM, Markus Krötzsch < mar...@semantic-mediawiki.org> wrote: > I now identified another format for API warnings. Obviously such variability in error reporting is going to cause consumers of the API aggravation. Perhaps a single, consistent reporting style could be

Re: [Wikidata-tech] API JSON format for warnings

2015-09-01 Thread Markus Krötzsch
I now identified another format for API warnings. For example, I got the following from action "watch": "warnings": { "watch": { "*": "The title parameter has been deprecated." } } For comparison, here is again what I got from wbeditentity: "warnings" :