Hi,
Two quick questions about orderings of stuff in JSON. Currently, we have two order-related keys:
snaks-order qualifiers-order
They are used to specify the order of groups of snaks in references (snaks-order) and statements (qualifiers-order). This is needed since the snak groups are stored in JSON maps in both cases (property => snak list), and maps do not have order semantics.
Question 1: Why don't we also have some information about statement/claim order? This seems to be necessary for using the API JSON internally as planned.
Question 2: Wouldn't it be more convenient to store lists of things in all cases, and have the "map" version just as an optional API switch for users who don't care about order (it could remain the default)? This would help to retrieve order information more easily.
Cheers,
Markus