@xgranade@wandering.shop Where the uncertainty is in the data, I'm honestly not convinced it's actually that complicated - usually the data layer is the most-custom, least-outsourced-to-an-abstraction part of an application.
And when you do need to interact with something that requires certainty (eg. a "sorted by date" item list display), you can convert to the most reasonable estimate for that specific context, from a source data structure that is designed for uncertainty?
@xgranade@wandering.shop (For example, in EXIF data, you might pick the start of a date range for the 'standard' field and then add the whole date range in an additional custom field, for applications which can deal with the uncertainty)
