26.03.2015 Views

19SafQB

19SafQB

19SafQB

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

332 Semantic as an Interoperability Enabler in Internet of Things<br />

can work with one or more agents (Multi agent). It must be published in the<br />

ontology repository in order to be consulted by final applications.<br />

The class Agent has two subclasses:<br />

• AgentName represents the name of the agent.<br />

• Services are the services given by the Agent. At the same time the<br />

class Services has three parts: ServiceName indicates the name of<br />

the service, Input is the input information that user, process or other<br />

provides to the service in order to execute the function properly,<br />

and Output which represents the output information generates by<br />

the service.<br />

All in all, following a service registry annotation example of a temperature<br />

sensor. The annotation has been described using JSON and complies with the<br />

ontology above mentioned:<br />

{<br />

"Entity":{<br />

"Device/Actuator": {<br />

"DeviceName": "Temperature Sensor 1",<br />

"Id": "0014.4F01.0000.B45B",<br />

"Description": "Measures the environmental temperature",<br />

"Manufacturer": "SunSpot Oracle",<br />

"Location": {<br />

"PlaceId": "Living room",<br />

"Latitude": "40.6",<br />

"Longitude": "-3.1"<br />

},<br />

"TechnologyRF": "Zigbee",<br />

"BatteryLevel": "70%"<br />

},<br />

"Resources":{<br />

"Agent":[<br />

{"AgentName": "fullAgent",<br />

"Services": [<br />

{"ServiceName": "temperatureService",<br />

"Input": "void",<br />

"Output": "integer"<br />

},<br />

{"ServiceName": "batteryLevelService",<br />

"Input": "void",<br />

"Output": "integer"<br />

}<br />

]<br />

},

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!