Actions

Ontolog Forum

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.


Synthesis: Track A: Ontology Integration in IoT

Co-Champions: LeoObrst and RamSriram

Goal: To discuss the various approaches being taken to address the integration and interoperability issues

Terminology: From Internet of Things to Smart Networked Systems and Societies

  • Internet of Things. The Internet of Things (IoT) is a term that is being used to denote a network – typically the Internet -- of devices that constantly monitor the environment and can result in “intelligent actions.” These devices can range from simple sensors to complex systems such as automobiles and buildings. There are several views of IoT in vogue. For example, ITU (International Telecommunication Union) and IERC (IoT-European Research Cluster) define IoT as “a global network infrastructure with self-configuring capabilities based on standard and interoperable communication protocols where physical and virtual things have identities, physical attributes and virtual personalities, use intelligent interfaces and are seamlessly integrated into the information network.” (See Internet of Things – From Research and Innovation to Market Deployment, Vermesan, O. and Friess, P. (editors), 2014, River Publishers, Aalborg, Denmark).
  • Cyber-Physical Systems. Cyber-physical systems (CPSs) extend IoT and will play an increasingly important role in the next generation industrial systems. These systems extend IoT by adding a control and decision making layer. Again, several views of CPSs exist. One commonly used definition is provided in http://varma.ece.cmu.edu/summit/index.html, which places an emphasis on embedded systems and the tight coupling between hardware and software.
  • Cyber-Physical Human Systems. When humans take an active role in CPSs we have Cyber-physical Human Systems (CPHSs). These systems can be viewed as socio-technical systems, with a symbiotic relationship between the human and the physical device.
  • Cyber-physical Social Systems or Smart Networked Systems and Societies. Social networks, such as Facebook and Twitter, primarily connect people to one another. These networks are playing very important roles in people's lives today, from how some of them behave and interact with one another, to change in human resources processes, how companies market and sell products and services, developments in healthcare and smart (electrical) grid systems, and even roles in politics and democratic uprisings. Social networks have been used both to curtail and to propagate freedom of speech. When these networks are combined with CPSs, we have Smart Networked Systems and Societies (SNSS), which are also known as Cyber-physical Social Systems (CPSS) or Internet of Everything (IoE).

The Technical Challenge: The development of a trusted, secure, reliable, and interoperable net-centric computing environment will need technologies that can assure a flexible and scalable system allowing the application of diverse and robust privacy requirements, thus enabling the trusted and meaningful growth of net-centric infrastructures for the benefit of all societies. One such technical challenge is that the network consists of things (both devices and humans) which are heterogeneous, yet need to have seamless interoperability. This requires the development of standard terminologies which capture objects and events. Creating and testing such terminologies will aid in effective recognition and reaction in a network-centric situation awareness environment.

Strategy for addressing the technical challenge in Track A:

  • Present case studies of IoT/IoE
  • Discuss current approaches in integration and interoperability
  • Discuss gaps in current approaches
  • Propose methods for achieving integration and interoperability through ontologies
  • Propose a unified framework for integration and interoperability for multimodal (audio, text, video, etc.) interfaces

Track A Speakers

  • Dr. SteveRay (Carnegie Mellon University, USA): An Ontology-Driven Integration Framework for Smart Communities
    • Describes a neutral, abstract ontology and framework that supports the vision and diverse contexts of a smart community, supporting IoT and ontology mapping
  • Dr. PayamBarnaghi (University of Surrey, UK): Dynamic Semantics for the Internet of Things
    • Provides an overview of the use-case and requirements for semantic interoperability in the IoT with a focus on annotation, processing and information extraction and dynamicity in the IoT environment
  • Dr. JackHodges (Web of Things (WOT) Research Group, Siemens Berkeley Laboratory, USA): Semantic Integration Prototype for Wearable Devices in Health Care
    • Describes a prototype using curated biomedical ontologies to assist health care professionals in selecting appropriate wearable devices to monitor diagnosed disorders
  • Dr. RamSriram (NIST): Toward Internet of Everything: IoT, CPS, and SNSS
    • Provides definitions of IoT, CPS, and SNSS. Discusses challenges for making a netcentric society a reality. Emphasis the need to develop event ontologies. Discusses an example in the health care domain.
  • Drs. SpencerBreiner (NIST) and EswaranSubrahmanian (CMU): Category Theory for Modular Design: An IoT Example
    • Discuses Category theory (CT) is the mathematical study of structure and, as such, provides a rich formal language for the specification and analysis of ontologies, broadly construed as structured representations of information.
  • Dr. KrzystofJanowicz (University of California, Santa Barbara): Ontology Virtualization for Smart Environments
    • Discusses ontology design patterns. Introduces notion of ontology virtualization, which provides a flexible plug and play-style reconfiguration of patterns with purpose-driven “semantic views.”

Case Studes of IoT/IoE

Current Approaches to Integration and Interoperability

  • The Hyper/CAT approach (see http://www.hypercat.io/standard.html): This a simple approach, where servers provide catalogues – an array of URIs -- of resources, annotated with metadata -- to clients [Barnaghi]
  • Simple Mapping: Manually map JSON entities to target ontologies [Ray]
  • Inference-based Mapping: Mappings between ontologies can be achieved using an inference engine (or AI theorem provers) [Ray]. This may involve making data smart [Janowicz]
  • Combine existing ontologies: There are well defined ontologies in various domains. Use these ontologies to integrate systems [e.g., Quantities, Units, Dimensions; Semantic Sensor Networks; Foundation Model of Anatomy; Symptom Ontology; Human Disease Ontology]

Gaps

  • Most systems in prototype stage
  • Lack of semantic annotation tools
  • Lack of tools for validation of ontologies
  • Need more work on representing events
  • IoT ontologies need to deal with dynamic time varying data vs. the often static Semantic Web
  • Privacy and security issues
  • Mostly manual methods for integration
  • For some promising approaches the mathematics may be solid but there is lack of implementaions.

Methods for Integration and Interoperability

  • Encode dynamic semantics, which includes incorporating time semantics [Barnaghi]
  • Develop event ontologies with above dynamic semantics [Barnaghi, Sriram]
  • Explore category theory, which reveals deep connections between formal logic, computer science and theoretical physics. Approach would involve the following: 1) Begin with two or more models; 2) Identify the overlap between these; 3) Map the overlap into each piece; 4) Define aggregates semantically (using category theory); and 5) Push out, [Breiner and Subrahmanian]
  • Use design patterns toward ontology virtualization: Given a set of ontology design patterns and their combination into micro-ontologies, one can abstract the underlying axiomatization by: dynamically reconfiguring patterns in a plug and play style; bridging between different patters as micro-theories; providing ontological views and semantic shortcuts that suit particular provide, user, and use case needs by highlighting or hiding certain aspects of the underlying ontological model; and mapping between major modeling styles [Janowicz]
  • Expand on techniques presented by Ray and Hodges.

Verification and Validation (abstracted from various talks)

  • Interconnect algorithms and hardware for two existing networks (example: a medical network and a transportation network that provides traffic data) with respect to algorithms and hardware
  • Select an existing ontology to bridge the networks
  • Create evaluation metrics based on strengths and weaknesses of the ontology bridge
  • Test evaluation metrics by interconnecting two other networks and run the same questions/metrics. Expand metrics as needed

Some Process Insights [Barnaghi]

  • Design for large-scale and provide tools and APIs.
  • Think of who will use the semantics and how when you design your models.
  • Provide means to update and change the semantic annotations.
  • Create tools for validation and interoperability testing.
  • Create taxonomies and vocabularies.
  • Try to re-use existing ones as much as you can.
  • Link your data and descriptions to other existing resources.
  • Define rules and/or best practices for providing the values for each attribute.
  • Remember the widely used semantic descriptions on the Web are simple ones like FOAF.
  • Semantics are only one part of the solution and often not the end-product so the focus of the design should be on creating effective methods, tools and APIs to handle and process the semantics. Query methods, machine learning, reasoning and data analysis techniques and methods should be able to effectively use these semantics.