Currently, as part of specification usage data though data subscription service can be controlled by published-min/published-max and updated-min/updated-max. There will be some third party who is interested on Interval Block/Reading data based on usage time. Basically, they need data from date to this data irrespective when last correction happen or when it first published though green button channel (usage time always would be less than published time... could vary one hour to days to several days.)
I see your point. You desire a start:duration (with default duration being start+duration = currentTime). Marty, are these query parameters currently defined?
I am raising this for further discussion on this.
Currently, as part of specification usage data though data subscription service can be controlled by published-min/published-max and updated-min/updated-max. There will be some third party who is interested on Interval Block/Reading data based on usage time. Basically, they need data from date to this data irrespective when last correction happen or when it first published though green button channel (usage time always would be less than published time... could vary one hour to days to several days.)