On 18.12.2012 17:08, Sven Manguard wrote:
How about this:
- Values default to a non-range value
- You can click a checkbox that says "range" to turn the input into a range
value instead
- An entry can only be represented by either a non-range or a range number, not both
Please be careful not to mix ranges as actual data values with ranges as accuracies:
There could be an "in-office" property which takes a range. The beginning and end of the range may each have an accuracy (for example, for some medieval king, we may have an exact date of death (and end of office), but only a vague idea of the coronation date.
This is conceptually different from a property that has a specific date/time as a value, which is only known with some given level of accuracy, which may be expressed as a range.
Now, I don't think we need or want ranges as a data type at all (better have separate properties for the beginning and end). But I still think the above distinction is an important one.
-- daniel