Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Historical Data Analysis with learnings from IDTA Submodel #1179

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Historical Data Analysis with learnings from IDTA Submodel #1179

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion planning/ThingDescription/analysis-historical-data-work-item.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,11 @@ Ideally, the feature can exist only after the requirements are identified. Howev
- [Timeseries Data Submodel Specification at IDTA](https://industrialdigitaltwin.org/wp-content/uploads/2023/03/IDTA-02008-1-1_Submodel_TimeSeriesData.pdf)
- Timepoint (A UTC time) and Duration (time after the start and last measurement) are possible. In Duration, start time is necessary
- TAI and UTC are basic formats. Unix Time, Ephemeris Time (ET) or Barycentric Dynamical Time (TBD) are possible
- Sampling Interval or Rate can be provided
- Sampling Interval or Rate can be provided as metadata
- Start and End Time can be provided since it also takes past values into account. Accordingly, you can also provide whether it is an ongoing timeseries or a completed one. (Ege: This is probably not relevant for us)
- Last Update can be provided. This is probably a data and not metadata for WoT. We can give guidelines/defaults on this. Normally, it should be equal to the timestamp of the last value.
- Each data blob is called a record.
- First the metadata is defined and then each data point needs to respect to that. Basically, it is like providing a data schema and then the values.
- [InfluxDB Timeseries Data oriented Database](https://www.influxdata.com/)
- [WebThings.io REST API](https://webthings.io/api/#event-resource)
- ECHONET Lite Web API has an extension of the current TD specification on this direction
Expand Down