Virtual Sensor RDF Schema Editor Use
All you need to run the Schema Editor is Java 7.0 (Java SDK 1.7), JBoss AS 7.1.X and a deployed version of OpenIoT LSM-Light and Security modules
LSM-Light (client and server) OpenIoT CAS (Security Modules)
JBoss AS 7.1.X
Deploy: To deploy the Schema Editor on JBoss AS 7.X, copy the ui.schemaeditor.war to the server's standalone/deployments directory. Undeploy: To undeploy the application, you need to remove the .deployed marker file that is generated upon successful deployment of the Schema Editor module.
You can find more detailed directions on deploying application on JBoss AS7 here.
Please open the following link in your favourite web browser. http://localhost:8080/ui.schemaeditor/
This will re-direct to the OpenIoT security module. If you are using the VDK, you can trial the Schema Editor using the credentials openiot/openiot.
For more help w.r.t OpenIoT CAS, please refer to Security Module
The landing page is a navigator page for
- Sensor Type Editor
- Sensor Instance Editor
The sensor type editor is used to create new sensor classes which will be automatically stored as an extension to the OpenIoT ontology in LSM server. Below is a screenshot of the sensor type editor with a sample sensor description
-
Sensor Type Name: The name of the new sensor class the user wishes to create (E.g. WeatherStation, SoilMoistureSensor)
-
Add Observed Property: This will allow a observed property to be attached to the sensor. On click the icon, a add new property window will appear.
- Property Name: Name of the observed property (e.g. http://services.openiot.eu/AirTemperature) Note: The Property Name must be a URL
- Accuracy: The accuracy is a string value. The application is responsible to convert the accuracy value to corresponding domain specific knowledge
- Frequency: The frequency is a string value. The application is responsible to convert the frequency value to corresponding domain specific knowledge
