You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As brought up in the 2020 proposal Add Associated Cost to TimeSeries Option 2, we can more concisely model time series data by grouping reading types within a single auc:TimeSeries element.
This issue is a suggestion to revisit this design when creating version 3 of the schema.
I think Audit Template's method for representing multiple time series data for a resource use could benefit from this change. E.g. here's a row representing meter data in AT which maps well:
We'd have to update the proposal to handle units for each reading type
@markborkum thoughts in the feasibility of this change for audit template?
As brought up in the 2020 proposal Add Associated Cost to TimeSeries Option 2, we can more concisely model time series data by grouping reading types within a single
auc:TimeSeries
element.This issue is a suggestion to revisit this design when creating version 3 of the schema.
For example (taken from the proposal)
The text was updated successfully, but these errors were encountered: