oeg-upm / auroral-adapters-ontology Goto Github PK

There is a typo in Precipitation word of the ontology, the code states 'Percipitation' instead of 'Precipitation'

Actual description of Person Counter Sensor refers to "The person sounter sensor is designed to count the number of person that visit a specific city". Instead of city, this should be about a Building Space, SpatialObject or any similar class.

Hi, I want suggest to include a tag "status" in the reading of energy production that can indicate if the data exposed was read with the right technical condition and can be considered validated from the source. This could help to distinguish for example a value of "0" read from non-correctly-working sensor from a really-read value of "0".
Thank you.

Missing unit: watt-hour

This is my data I am developing a thing description I am missing the type for weather service api.

Response data example:

{
  "airPressureAtSeaLevel": 1015.9,
  "airTemperature": 25.7,
  "cloudAreaFraction": 35.2,
  "relativeHumidity": 84.7,
  "windFromDirection": 168.4,
  "windSpeed": 6.7
}

PM1.0 is missing. PM10 is different than PM1.0

missing property "depth" for soil moisture sensors

Add property dev_position (related to Device position. identifies if device is in normal or tilt position)

I was checking the class https://auroral.iot.linkeddata.es/def/core#Device in the code of the ontology and it seems that is not subClassOf saref:Device. However in the diagram it appears as if it was.

The data properties "has id", "serial number" and "version number" are in https://saref.etsi.org/core#Device, it should be part of https://auroral.iot.linkeddata.es/def/core#Device

Why the dp timestamp is needed in core:Device?

Hello,
I would like to have cloudCover under adapters:ambientProperty

typo on SoilMoistureSEnsor

Add diagram and documentationo about the ontology to the readme.

Do we need to represent this property or is it internal use?

location-<location_id>/flood-/sensor/error: if different from 0, there is an error with the sensor

and

location-<location_id>/flood-/sensor/act_reasons: list of reasons which woke up the device: battery, button, periodic, poweron, sensor, alarm

(from https://cloud.auroral.eu/index.php/f/98609)

Alentejo pilot.

Add rdfs:label to all classes and include María as a creator

https://auroral.iot.linkeddata.es/def/adapters#StatusProperty

StatusProperty missing property "active" (True/False) to indicate if the motion detection is active or not

These properties can be measured in the context of pv and solar radiation, we should add them to the ontology:

• DirectRadiation
• DiffuseRadiation
• DirectNormalIrradiance
• TerrestrialRadiation
• ShortwaveRadiationInstant
• DirectRadiationInstant
• DiffuseRadiationInstant
• DirectNormalIrradianceInstant
• TerrestrialRadiationInstant

Add a new instance for the Ultrasound Sensor. This sensor measures distance. We are currently using the Grove Ultrasonic Ranger sensor https://wiki.seeedstudio.com/Grove-Ultrasonic_Ranger/

Is the prefix "@Prefix adapters: http://www.semanticweb.org/user/ontologies/2022/5/adapters ." a valid domain?

How can we describe the data below in the thing description using json schema?

Thing definition:

{
 "td": {
   "@context": [
     "https://www.w3.org/2019/wot/td/v1",
     "https://auroralh2020.github.io/auroral-ontology-contexts/adapters/context.json"
   ],
   "title": "Auroral Safe Search Weather Reader",
   "description": "Reads data from Auroral Safe Search API",
   "@type": "",
   "properties": {
     "auroral_safe_search_weather_reader": {
       "title": "Auroral Safe Search Weather Reader property",
       "readOnly": true,
       "type": "object",
       "@type": "weather",
       "forms": [
         {
           "op": [
             "readproperty"
           ],
           "href": "http://192.168.178.31:9000/api/weather"
         }
       ]
     }
   }
 }
}

Data response:

{
    "airPressureAtSeaLevel": 1015.9,
    "airTemperature": 25.7,
    "cloudAreaFraction": 35.2,
    "relativeHumidity": 84.7,
    "windFromDirection": 168.4,
    "windSpeed": 6.7
  }

The adapters ontology is using two ontologies for sensors. For instance, if I want to express that I have a temperature sensor that measures the property adpaters:ActsReasons I can only use SOSA, with saref as it is now the ontology it is not possible.

Shall we keep only one of these two ontologies? or in other case, we should ensure that all the things can be expressed with both. But I think it would be better to use just one ontology.

Translating the owl file of the ontology into a different serialization is not possible because some terms have dots in their name which seems to be an error. For instance adapters:PM.25Concentration produces an error, instead adapters:PM25Concentration does not

In order to define a geometry and spatial features. It could be useful to have a SubClass relationship between saref:PhysicalObject and geosparql:Feature.
Then it would be possible add geosparql:hasGeometry property to every sensor device.

Possible missing property "realy_status"

Instead of redefining the saref:makesMeasurement in adapters ontology with core:makesMeasurments, let's use the saref property

Add property "ext_power" to temperature and humidity sensor

Possible duplicated adapters: "Electric Voltage" and "Grid Voltage"