SOSENS - The SOcial SENSor Semantic Web framework

Web Demo: New sensor observation(s)

In this demo, you can use the SOSENS API to create sensor observations, as expressed in the SOSENS environment and in your chosen RDF serialization format.

SOSEN Api workflow

Begin by choosing the level of detail of the demo (Simple/Advanced)
Fill in the forms that appear or choose "fill the form with demo values"
When you're done filling in your data, press the "Create REQUEST" button to get a preview of what the data sent to the API should look like.
Finally, press "SEND to API" to get a real-time response from the '/api/v1/observation' endpoint containing the SOSENS semantic representation of your data

Please choose the level of detail of this demo (and the SOSENS API Usage Mode):

Please fill in the form below manually or fill the form with demo values

GLOBAL OPTIONS

Show Help

Everything listed below is optional.

type	variable	example	comment
optional	outputFormat	n3	The RDF output format (defaults to n3)
optional	namespace	http://example.org/data#	The local namespace that will be used if URIs are not full http

outputFormat

namespace

URI

The local namespace that will be used if URIs are not full http

SENSOR OBSERVATIONS

Show Help

- If all you want to do is to simply create a few observations in SOSENS using the SOSENS defaults, just fill in the “required” type variables
- The SOSENS API will create a URI for the observation in the form of {observedBy}_obs_{property}_{time} and create the necessary RDF

type	variable	example	comment
required	observedBy	Sensor_1	The sensor that created the observation
required	feature	Area_1	The feature of interest that the sensor observes (OWL Instance)
required	property	temperature	The observed property of the sensor (OWL Instance). Not required if defining an observationClass
required	time	2014-05-20T14:30:00	The time of the observation, in XSDDateTime format. Not required if defining a timeInstanceURI
required	valueType	quantity	Choose “quantity” or “quality”. Choosing either will resultin using the SOSENS Generic SSN Value ontology to describe the observationValue. You may override this behaviour by defining your own classes and/or observationValueURI
required	value	50	The observed value of the observation
required	valueDataType	integer	Corresponds to XMLSchema Datatypes (double, integer, etc.)
optional	unitOfMeasurement	Celsius	The unit in which the observation value is measured in (OWL instance)
optional	wasParsedFrom	Facebook_Post_1	(for Social Sensors) The sioc:Post that the information was parsed from (OWL instance)
optional	wasResultOfParsingActivity	Parsing_Activity_1	(for Social Sensors) The sosens:ParsingActivity that transformed the above sioc:Post into a ssn:Observation (OWL instance)
optional	observationClass	TemperatureObservation	The class the observation instance will be a member of (must be a subclass of ssn:Observation). You may skip defining the “observedBy” variable if you declare this
optional	sensorOutputClass	TemperatureSensorOutput	The class the sensor output instance will be a member of (must be a subclass of ssn:SensorOutput)
optional	observationValueClass	CelsiusValue	The class the observation value instance will be a member of (must be a subclass of ssn:ObservationValue)
optional	observationURI	Observation_1	The URI of the observation instance
optional	sensorOutputURI	SensorOutput_1	The URI of the sensor output instance
optional	observationValueURI	ObservationValue_1	The URI of the observation value instance
optional	timeInstanceURI	TimeInstance_1	The URI of the instance that will be defined as the predicate of the ssn:observationResultTime property

To fill in URIs: enter a string for using the local namespace (can be modified in the "global" options) OR a full URI with http:// for external namespace (e.g. Sensor_1 OR http://example.com/sensors#Sensor_1)

Observation

observationURI

observationClass

observedBy*

feature*

property*

Not required if defining an observationClass

Use the TIME ontology?
Yes No

time*

timeInstanceURI

sensorOutput
URI

sensorOutput
Class

Use the SOSENS Generic SSN Value ontology?
Yes No

valueType*

Quantity Quality

value*

unitOf
Measurement

observationValue
URI

observationValue
Class

wasParsedFrom

wasResultOf
ParsingActivity

Add New Observation CREATE REQUEST

SOSENS API Web Demo

Web Demo: New sensor observation(s)

GLOBAL OPTIONS

SENSOR OBSERVATIONS

Modal title