search

universAAL / ontology

Collection of "official" ontologies of universAAL, which play the role of data model
13 stars 11 forks source link

Specialize hasValue properties in ont.device #478

Closed Alfiva closed 7 years ago

Alfiva commented 7 years ago

Originally Opened: @Alfiva (2015-09-28 00:00:00) Originally Closed: 2015-10-05 00:00:00

Right now when the automatic OWL of ont.device gets dumped into the CHE, when its information is recovered back from it, all device types are rdf:type of all other device classes. I believe it has to do with how I implemented the hasValue property restrictions in the ontology class.

This should be avoided by having specialized subProperties of hasValue, depending on the type of value - which in turn would require having some more abstracted types of devices. It should look like this:

-Light,Curtain,Blind,Dimmer Sensor/Actuator/Controller should inherit from IntSensor or IntActuator.

-IntSensor and IntActuator should have a property hasIntValue, that inherits from hasValue, and is restricted to Integer.

-Switch,WaterFlow,...,Fall,Contact Sensor/Actuator/Controller should inherit from StatusSensor or StatusActuator.

-StatusSensor and StatusActuator should have a property hasStatusValue, that inherits from hasValue, and is restricted to StatusValue.

-StatusSensor/Act and IntSensor/Act should inherit from Sensor and Actuator respectively.

Humidity,Temperature,...,Exit Sensor should still inherit directly from Sensor. But each one should have its own property hasXXXValue, that inherits from hasValue, and is restricted to each specific value type.

If I got it right, this should still be backwards-compatible with apps that used the ont.device so far.

--

From: this issue has been automatically imported from our old issue tracker

Alfiva commented 7 years ago

issue cloed on 2015-10-05 00:00:00