<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
2017-11-30 17:36 GMT+03:00 Lydia Pintscher <lydia.pintsc...@wikimedia.de>:
> Hey Vladimir,
>
> On Wed, Nov 29, 2017 at 10:54
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
Vladimir Ryabtsev <greatvo...@gmail.com>:
> 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 l
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
I find the order of claims on web site useful, but when requesting entity
data through API (action=wbgetentities) it got lost.
How the claims are ordered on an entity web page and how to restore the
order in API response?
--
Vlad
