| Behaviour Modelling [message #1799576] |
Mon, 10 December 2018 12:46  |
 Aditya Bhola
Messages: 1
Registered: December 2018 |
Junior Member |
|
|
I've been going through the project documentation, and found that a 'thing' or asset, can be modelled as a set of features, each of which can internally have a hierarchy of parameters, which can be read or written using APIs.
My question is, does the Ditto project have behaviour modelling too in the future plan? By behaviour modelling, I mean introducing features / parameters which are not directly recorded by sensors on the things, but are deduced from the existing features.
For example, let's say a fridge (the thing) has a sensor for door open / close.
But doesn't have a sensor to know whether the light is on or not. I can currently model this scenario as follows:
{
"attributes": {
"manufacturer": "XYZ",
"VIN": "12345"
},
"features": {
"door": {
"properties": {
"open": true
}
}
"light": {
"properties": {
"on": true
}
}
}
}
But the lights:on parameter would never be set. My question is that is there a way I can model that door:open leads to light:on, and door:close leads to light:off? If not currently possible, is something like this in the plan?
|
|
|
|
Powered by
FUDForum. Page generated in 0.02596 seconds
] 
Search
Help
Register
Login
Home
