-
Notifications
You must be signed in to change notification settings - Fork 2
Description
initial comments from @ColeDCrawford on slack:
Some way to capture whether a date is fuzzy / uncertain / estimated (clearly need to settle on the language too!). This should probably be a range - the default could just be
range(2)
for certain / uncertain, but allow users to override it with their own custom range as needed. We should also have reasonable but overrideable defaults for the impact of the fuzziness on comparators. The Pythonedtf
implementation pads by 100% of the uncertainty (e.g.2022-11~
matches the range for2022-10-1/2022-12-31
forlower_fuzzy()
toupper_fuzzy()
) or2022-11-01/2022-11-30
(lower_strict()
toupper_strict()
). This makes sense to me, but we should let users choose the amount of padding. A percentage would be easiest to start, with the “known” date in the middle. In the future could allow more control (the possible range might be skewed).