In a time dimension, there are month and day value attributes, which are super helpful for retrieving a date range with an attribute filter etc. However, these are currently strings and therefore may not work with some comparisons and mathematical functions. These values really should be numeric.
I understand, that the problem of numeric attribute values is, that they aggregate and therefore can only be stored on base elements. But this means, there could be something like a numeric attribute, that doesn't aggregate, to solve this issue. Or the time editor automatically creates a numeric attribute, that is populated by a rule and simply returns the numeric value of the string attribute, to overrule any aggregation. Or the time dimension becomes "smarter" and there is logic in the background that would solve this.
