daniel added a comment. The reason 350±150 is shown as 400±200 is that rounding is applied based on the uncertainty, and the same rounding is applied to the uncertainty itself (basically, you cannot be more precise about the uncertainty than about the value itself). The reason we apply rounding here is for consistency: if unit conversion is applied, we have to apply rounding to avoid false precision. So for consistency, we always apply rounding.
But this is not set in stone. I'm coming around to the opinion to apply rounding only when needed, and to show values as-is otherwise. Regarding the "data loss" aspect of the HTML rendering I disagree: we have never guaranteed or even tried to make the HTML representation lossless. That would be rather hard to do, and would contradict the wish to have "nice" readable values in HTML. This is particularly true for values that are references to other entities - we show them using labels, not IDs, so when you copy&paste them, you lose information. TASK DETAIL https://phabricator.wikimedia.org/T95425 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: daniel Cc: Thryduulf, Addshore, Lydia_Pintscher, Jc3s5h, Snipre, mgrabovsky, daniel, thiemowmde, Aklapper, Wikidata-bugs, aude _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
