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.
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
STA V2.0 Design Draft #167
Comments
resultTime::Observation, time::PreparationStep needs to be of type TM_Instant. As described in #177 the way OData defines it is DateTimeOffset, this should be elaborated in the OData binding section of the standard and not in the data model. |
I fixed the image. |
Is the Deployment entity to be included in the Core Sensing Part of the document? |
Updated images: |
Changed Sampling -> Thing relation cardinality to 0..1. |
I designed a draft data model that addresses some of the concerns the community has had over the past couple of years and also attempts to align with OMS V3.
ObservationCollection
In TC Singapore, perhaps this was debated as to whether or not is it really a collection of observations or just a Datastream renamed to ObservationCollection.
[1] As per OMS, an ObservationCollection should be homogeneous or summarizing type.
[2] Should ObservationCollection be allowed to contain different types of observations that may potentially violate the OBSC req set out by OMS? Will it help in addressing issues?
[3] resultType is adopted as per SWE Common JSON schema (see #122 )
Deployment
This entity describes the current state of observers (read Sensors) in their association with Host (Thing (?))
[1] position property may be used to describe geographic location of sensors for moving things?
ObservingProcedure
See #160
Do we need it?
FeatureOfInterest
In order to introduce sampling in STA, FoI can be specialized further to pFOI and uFOI as specified in OMS. This also allows to extend pFOI by introducing and linking Sampling entitites with it. pFOI may act as a Sample proxy in the design
Please feel free to critique and put forward your suggestions
The text was updated successfully, but these errors were encountered: