Hey,
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.
To answer the first part: probably because no one got to that yet. As for
the second part: how so? The internal format also does not have this.
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.
That would better serve the WDTK use case, and those who do a full
deserialization. I strongly suspect most users of the JSON do not fall into
that category.
Cheers
--
Jeroen De Dauw -
http://www.bn2vs.com
Software craftsmanship advocate
Evil software architect at Wikimedia Germany
~=[,,_,,]:3