Re: A notation for expressing frequency of data collection

> The range for hasFrequency shouldn't be hard-set. So one could use enums

> (instances of a class are a better design pattern than strings IMO) or
> OWL-TIME or XSD or ints. Same for duration or location or other properties.
I agree, but to make sure we're on the same page, I want to double-check a thing.

The problem has to be seen from 2 perspectives:
[a] machine
[b] person

A computer wants classes and strongly typed entities that it can quantify and compare. But a grandma buying a gadget for her beloved nephew wants to see "every hour" rather than  `Frequency(unit=hour,value=1)`.

My understanding is that you operate at the [a] level, whereas I operate at [b], the user-facing side.


Both aspects are important and must go hand in hand. Otherwise we might end up with many different "human representations" derived from the same formal specification, because different teams interpreted it in their own way.

Can you provide some actual examples of what your proposal might look like, from an end-user's perspective?