Commit 4abdabe6 authored by Giulia Biagioni's avatar Giulia Biagioni
Browse files

insert upflex downflex

insert upflex and downflex individuals of type ic-data:usage
parent 13735187
......@@ -25,21 +25,21 @@
<http://purl.org/dc/elements/1.1/creator> <https://www.linkedin.com/in/lauradaniele> ;
<http://purl.org/dc/elements/1.1/creator> "Cornelis Bouter -TNO"@en ;
<http://purl.org/dc/elements/1.1/creator> "Georg Jung - VITO" ;
rdfs:comment """Datatype and Timeseries ontology.
This ontology extension was created to address the following needs:
- The necessity of expressing time-series of data for various tasks and services in InterConnect
rdfs:comment """Datatype and Timeseries ontology.
This ontology extension was created to address the following needs:
- The necessity of expressing time-series of data for various tasks and services in InterConnect
- A workable and unambiguous characterization of quantities, combining units with measurements. This characterization should be technically complete so that quantities cannot be confused during data exchange between unfamiliar services"""@en ;
owl:imports <http://ontology.tno.nl/interconnect/flexibility> ;
.
ic-data:DataPoint
a owl:Class ;
rdfs:comment """A data point is a quantity that is extended with various pieces of process information, namely
- A creation time (instant). This is the point in time when the data point was created, which is not necessarily the time for which it is valid. In the case of soft-sensors or forecasters, a data point might have been created ahead of time, in the case of a direcet measurement a data point might created at its time of validity (or at the end of its validity time interval) and in the case of an archived value the data point might have been created after the fact.
- A validity time (temporal entity) which will be named \"time stamp\". The validity time is the instant or interval in time in which a specific quantity is in effect. For example a room temperature might be measured at 12:00, which means it is in effect at this very instant. A specific amount of energy might me expended within the time-slot between 12:30 and 12:45, which means that the energy measurement is in effect during this time interval.
rdfs:comment """A data point is a quantity that is extended with various pieces of process information, namely
- A creation time (instant). This is the point in time when the data point was created, which is not necessarily the time for which it is valid. In the case of soft-sensors or forecasters, a data point might have been created ahead of time, in the case of a direcet measurement a data point might created at its time of validity (or at the end of its validity time interval) and in the case of an archived value the data point might have been created after the fact.
- A validity time (temporal entity) which will be named \"time stamp\". The validity time is the instant or interval in time in which a specific quantity is in effect. For example a room temperature might be measured at 12:00, which means it is in effect at this very instant. A specific amount of energy might me expended within the time-slot between 12:30 and 12:45, which means that the energy measurement is in effect during this time interval.
- A location or topological association. For example, a measurement might be taken in a specific room, a power avarage might have been measured by a specific meter, a forecast might be valid for a specific region or grid segment. This association is therefore not always a location."""@en ;
rdfs:label "Data point" ;
rdfs:subClassOf saref:Measurement ;
......@@ -213,10 +213,20 @@ ic-data:consumption
a owl:NamedIndividual ;
rdfs:label "consumption"@en ;
.
ic-data:upflex
a ic-data:Usage ;
a owl:NamedIndividual ;
rdfs:label "upflex"@en ;
.
ic-data:downflex
a ic-data:Usage ;
a owl:NamedIndividual ;
rdfs:label "downflex"@en ;
.
ic-data:hasCreationTime
a owl:ObjectProperty ;
rdfs:comment """The time instant that defines the creation time of a data point or quantity or forecast or similar entities. This is not the same as the time at which the quantity is in effect. For example, if a temperature is forecasted today at 12:30 (creation time of the forecast) for the following day at 14:45 (time when the temperature is expected to be in effect), the this instant should be 12:30 of today.
rdfs:comment """The time instant that defines the creation time of a data point or quantity or forecast or similar entities. This is not the same as the time at which the quantity is in effect. For example, if a temperature is forecasted today at 12:30 (creation time of the forecast) for the following day at 14:45 (time when the temperature is expected to be in effect), the this instant should be 12:30 of today.
A creation time (instant). This is the point in time when the data point was created, which is not necessarily the time for which it is valid. In the case of soft-sensors or forecasters, a data point might have been created ahead of time, in the case of a direcet measurement a data point might created at its time of validity (or at the end of its validity time interval) and in the case of an archived value the data point might have been created after the fact."""@en ;
rdfs:label "has creation time" ;
rdfs:range time:Instant ;
......@@ -230,7 +240,7 @@ ic-data:hasDataPoint
.
ic-data:hasEffectivePeriod
a owl:ObjectProperty ;
rdfs:comment """This connects to the temporal entity which describes when (time interval) the quantity of this data point was, is, or will be in effect. This is the time interval which is covered by the forecast.
rdfs:comment """This connects to the temporal entity which describes when (time interval) the quantity of this data point was, is, or will be in effect. This is the time interval which is covered by the forecast.
This should be equivalent to the time interval covered by the time-series that express the forecast. *A potential application of SHACL?*""" ;
rdfs:label "has effective period" ;
rdfs:range time:TemporalEntity ;
......@@ -244,10 +254,10 @@ ic-data:hasQuantile
.
ic-data:hasStandardDeviation
a owl:ObjectProperty ;
rdfs:comment """Adds a standard deviation to a data point.
It should be used as follows: :
<Datapoint> <:hasStandardDeviation> <om:Quantity>;
<om:Quantity> <om:hasAggregateFunction> <om:Function>;
rdfs:comment """Adds a standard deviation to a data point.
It should be used as follows: :
<Datapoint> <:hasStandardDeviation> <om:Quantity>;
<om:Quantity> <om:hasAggregateFunction> <om:Function>;
<om:Function> value <om:standardDeviation>."""@en ;
rdfs:domain ic-data:GaussianDataPoint ;
rdfs:label "has standard deviation"@en ;
......@@ -267,8 +277,8 @@ ic-data:hasTextValue
.
ic-data:hasUpdateRate
a owl:ObjectProperty ;
rdfs:comment """The rate at which a data point or time-series or forecast or other data entity is being updated.
rdfs:comment """The rate at which a data point or time-series or forecast or other data entity is being updated.
If the time series gets regularly updated, then the time between two updates can be recorded here."""@en ;
rdfs:label "has update rate" ;
rdfs:range time:TemporalDuration ;
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment