Hi Thiemo,
Thanks for the background information. I agree with these default
choices -- seems useful. Just two comments:
There may be an option to enter the precision as a number, if requested,
but I don't think this is necessary at this point.
I think the point is simply that it is not
Hi Markus,
(1a) Wikibase will continue to support arbitrary precision values for
coordinates, and the UI will be extended so people can actually enter them.
(1b) Wikibase will restrict the set of supported precision values for
coordinates to those already supported in the UI. Other values are
On 12.01.2015 15:59, Daniel Kinzler wrote:
Am 12.01.2015 14:48, schrieb Markus Krötzsch:
Anybody? If the answer is we not thought about this yet then it would be good
to know this, too. Any considerations that have led to the current
implementation are of interest.
The range is limited (no
Am 12.01.2015 15:09, schrieb Markus Krötzsch:
Great, this clarifies a lot for me. The other question was what to make of
null
values for precision. Do they mean no precision known or something else?
IIRC, null is a bug here. Not sure how to handle that - we don't have the
original string, and
Hi!
Which of the following statements are most accurate given the technical
roadmap of Wikibase?
(1a) Wikibase will continue to support arbitrary precision values for
coordinates, and the UI will be extended so people can actually enter them.
(1b) Wikibase will restrict the set of
