iotest project: semantic interoperability
DESCRIPTION
IoTest project: Semantic interoperability, presented in the session: "Interoperability ", at the Internet of Things Workshop (27.10.2011), during the Future Internet Week, Poznan, Poland, 24-28 October 2011TRANSCRIPT
Semantic Interoperability for IoT Services and ResourcesKlaus Moessner
Centre for Communication Systems Research
University of Surrey
October 2011
Internet of Things
• Internet of Things (IoT) vision:– large number of physical world objects interacting with each other and the ambient environment
– data/services from these objects to provide ‘real world’ services
• provide information• allow interaction
Requirements
• structured representation of identified IoT concepts
• homogeneous access mechanism to heterogeneous objects with diverse capabilities
• automated machine interpretability of the possible interactions and horizontal integration with existing applications
How to model Things?
• resource model– Gateway, sensors, processing resources
• entity model– Physical world objects
• Features of interest for each entity
• service model– IoT services and interfaces
IoT Services
• services are provided by a plethora of heterogeneous objects that are often directly related to the physical world
• data and/or functionalities offered by such services provide information about the physical world and allow interaction with it
Data and services in IoT ‐ Challenges
• large‐scale networks, huge volumes of data, dynamic and sometimes unreliable data sources
• dynamicity, transient data and subject to quality changes
• scalability of the solutions
• express‐ability and extensibility of semantics and meta‐data
• heterogeneity ‐more devices are contented, more diversity
• more autonomous processes (integration, aggregation, filtering, ...) are required
• management of the resources
Role of metadata
• semantic tagging• machine‐interpretable data annotation and resource descriptions
• re‐usable ontologies• resource description framework(s)• structured data, structured query
In IoT semantic models are useful for:• description of various concepts and attributes in the IoT framework
• providing machine interpretable and structured representation of resources/entities/services and domain knowledge
• supporting automated processing and decision making over various interactions and integration with existing and new applications
Metadata and Semantics
• to describe:– Content– Context– Resources – Entities and features of interest
• to create:– Perception– Context and situation awareness
• to support:– Automated processes for management of resources and decision
making
Semantic interoperability for
• resource description – SENSEI resource description, IoT‐A resource model, W3C SSN Ontology,…
• entity description and domain knowledge– SENSEI entity description, IoT‐A entity model, linked data models and linked open data fro domain knowledge,…
• IoT services– In IoT.est we plan to use semantic web services (extension to OWL‐S) that we have developed in the context of the IoT‐A project.
11
W3C Incubator Group, SSN Ontology
makes observations of this type
where it is
What it measures
units
SSN-XG ontologies
SSN-XG annotations
Service modelEntity Model Ontology
W3C SSN OntologyResource Model Ontology
OWL‐S Service Profile Ontology
P(em:DomainAttribute)
OWL‐S Service Grounding Ontology
Service Model Ontology
hasInput
profile:Profile
iot:ResourceAccessAtomicProcessGrounding
em:DomainAttribute
em:DomainAttribute
P(em:DomainAttribute)
hasEffect
hasPrecondition
hasOutput
Service
presents
supports
rm:AccessInterface
hasAccessInterface
ssn:Property ssn:Property ssn:Condition ssn:Condition
hasInputType hasOutputType
hasPreconditionTypehasEffectType
iot:ObservationArea
iot:ObservationSchedule
hasObservationArea
hasObservationSchedulehasServiceType
ServiceType
OWL‐S USDL
WSML xxx
<<instanceOf>>
Service instance: an example
Entity Model Ontology
W3C SSN Ontology
Resource Model Ontology
OWL‐S Service Profile Ontology
OWL‐S Service Grounding Ontology
Service Model Ontology
U38_TempSensorService_Profile
U38_TempSensorServiceProcessGrounding
RoomU38.hasA (AmbientTempAttribute)hasOutput
U38_TempSensor_Service
pres
ents
supports
AccessInterface_U38_temp_sensor
hasAccessInterface
U38_TempSensorService_Property
hasOutputType
U38_ObservationArea
U38_ObservationSchedule
hasObservationArea hasObservationSchedule
hasServiceType
OWL‐S
SENSEI Observation and Measurement Ontology
TemperaturesubClassOf
What are the challenges?
• the models provide the basic description frameworks, but alignment between different models and frameworks are required.
• semantics are the starting point, reasoning and interpretation of data is required for automated processes.
• real interoperability happens when data/services from different frameworks and providers can be interchanged and used with minimised intervention.
What are the practical steps?
• linked data approach is a promising way for integrating data from different sources and interlinking semantic descriptions
• alignment between different description models for IoT Services/Resources/Entities
• proposing reference and abstract models for semantic descriptions in IoT (e.g. similar to the W3C SSN approach)
References and links
• Suparna De, et al, Service modelling for the Internet of Things– http://www.iot‐a.eu/public/public‐documents/documents‐1/1/2/service‐
modelling‐for‐the‐internet‐of‐things/at_download/file
• W3C SSN – http://www.w3.org/2005/Incubator/ssn/XGR‐ssn‐20110628/
• Claudia Villalonga, A Resource Model for the Real World Internet– http://www.springerlink.com/content/ejxm56331g8w7rk2/fulltext.pdf
Thank you!