Re: [Wikidata-tech] Order of claims on entity page

2017-11-29 Thread Vladimir Ryabtsev
The talk is not about JSON, I never mentioned it. JSON is a serialization format and it does not have to be "nice". The talk about the ability to do something. As for use case, I have already described it: representing data in the same (familiar to user) layout as on Wikidata page. If you consider

Re: [Wikidata-tech] Order of claims on entity page

2017-11-29 Thread Thiemo Kreuz
> […] it turns out it lacks PLENTY of properties we usually work with. From 1400+ properties we normally use, there are only 480 on this page This is intended. The list was originally created with the most common properties, and can and should be expanded any time when the need to do so arises. Un

Re: [Wikidata-tech] Order of claims on entity page

2017-11-29 Thread Vladimir Ryabtsev
As a follow-up, I analyzed the properties mentioned in https://www.wikidata .org/wiki/MediaWiki:Wikibase-SortedProperties and it turns out it lacks PLENTY of properties we usually work with. From 1400+ properties we normally use, there are only 480 on this page :( Vlad 2017-11-29 16:13 GMT+03:00

Re: [Wikidata-tech] Order of claims on entity page

2017-11-29 Thread Vladimir Ryabtsev
Thiemo, thanks, I understand that I can use the order from that page as well as invent my own order. My point is that it would be nice to have a way to represent data same way as Wikidata site does. Since I see the same claims layout every time I refresh a page, I assume this order is fixed and sto

Re: [Wikidata-tech] Order of claims on entity page

2017-11-29 Thread Markus Krötzsch
Dear Vlad, Ordering claims on a page as you suggest would not work well, since several other orders must take precedence over the order you suggest. First of all, statements are grouped by property and you don't want to change this. Hence, you cannot use the order across statements of differe

Re: [Wikidata-tech] Order of claims on entity page

2017-11-29 Thread Thiemo Kreuz
> what is the purpose of giving order of qualifiers then? The JSON still contains fields called "qualifiers-order" on each qualifier, as well as "snaks-order" on each reference. These are fragments from a feature the Wikibase software once supported. In 2013 the interface had "move up" and "move d

Re: [Wikidata-tech] Order of claims on entity page

2017-11-29 Thread Владимир Рябцев
OK Lydia, what is the purpose of giving order of qualifiers then? Along with helping to give a user a better representation of data, the order can be useful in automated processing of properties. To my mind, it starts with the most important entity data. Moreover, in case of contradiction, I wou

Re: [Wikidata-tech] Order of claims on entity page

2017-11-29 Thread Lydia Pintscher
On Wed, Nov 29, 2017 at 11:14 AM, Владимир Рябцев wrote: > Thanks for the link with sorted properties. Is this page updated > automatically or maintained manually by someone? In latter case this looks > weird to me, because the order may become not actual at some moment. Yes it is maintained by h

Re: [Wikidata-tech] Order of claims on entity page

2017-11-29 Thread Владимир Рябцев
Thanks for the link with sorted properties. Is this page updated automatically or maintained manually by someone? In latter case this looks weird to me, because the order may become not actual at some moment. It is curious that when properties are used as qualifiers we have a separate field spe

Re: [Wikidata-tech] Order of claims on entity page

2017-11-29 Thread Thiemo Kreuz
The order of properties as presented in the web interface is specified in https://www.wikidata.org/wiki/MediaWiki:Wikibase-SortedProperties . You can use the same list to order the data you get from any API response accordingly. Note that, technically, the order of elements in a JSON object (curly

Re: [Wikidata-tech] Order of claims on entity page

2017-11-29 Thread Lucas Werkmeister
As far as I can tell, this is not possible via the API directly. However, you can get the order of properties from MediaWiki:Wikibase-SortedProperties , and sort the response you get accordingly. If you’re using Lua, there’s also th