Web of Things (WoT), Architecture, Thing Description, Scripting API | W3C

Documents

Web of Things (WoT) Architecture, 2017-09-14.

Summary
  1. WoT Thing Description
  2. WoT Scripting API
  3. WoT Binding Templates.

Web of Things (WoT) Thing Description, 2017-09-14.

Summary

Describes the metadata and interfaces of Things.

Web of Things (WoT) Scripting API, 2017-09-14.

Summary

Operates on Things characterized by Properties, Actions and Events.

Abstracts

Web of Things (WoT) Architecture

Abstract

The W3C Web of Things (WoT) is intended to enable interoperability across IoT Platforms and application domains. Primarily, it provides mechanisms to formally describe IoT interfaces to allow IoT devices and services to communicate with each other, independent of their underlying implementation, and across multiple networking protocols. Secondarily, it provides a standardized way to define and program IoT behavior.

This document describes the abstract architecture for the W3C Web of Things. It is derived from a set of use cases and can be mapped onto a variety of concrete deployment scenarios, several examples of which are given. This document is focused on the standardization scope of W3C WoT, which consists of three initial building blocks that are briefly introduced and their interplay explained.

The WoT Thing Description (TD) provides a formal mechanism to describe the network interface provided by IoT devices and services, independent of their implementation. Provision of a TD is the primary requirement for a device to participate in the Web of Things. In fact, defining a Thing Description for an existing device allows that device to participate in the Web of Things without having to make any modifications to the device itself. WoT Binding Templates define how a WoT device communicates using a concrete protocol. The WoT Scripting API—whose use is not mandatory—provides a convenient mechanism to discover, consume, and expose Things based on the WoT Thing Description.

Other non-normative architectural blocks and conditions underlying the Web of Things are also described in the context of deployment scenarios. In particular, recommendations for security and privacy are included, while the goal is to preserve and support existing device mechanisms and properties. In general, W3C WoT is designed to describe what exists rather than to prescribe what to implement.

Web of Things (WoT) Thing Description

Abstract

This document describes a formal model and common representation for a Web of Things (WoT) Thing Description. A Thing Description describes the metadata and interfaces of Things, where a Thing is an abstraction of a physical entity that provides interactions to and participates in the Web of Things. Thing Descriptions provide a narrow-waist set of interactions based on a small vocabulary that makes it possible both to integrate diverse devices and to allow diverse applications to interoperate. Thing Descriptions, by default, are encoded in JSON-LD. JSON-LD provides both a powerful foundation to represent knowledge about Things and simplicity, since it allows processing as a JSON document. In addition to physical entities, Things can also represent virtual entities. A Thing Description instance can be hosted by the Thing itself or hosted externally due to Thing’s resource restrictions (e.g. limited memory space) or when a Web of Things-compatible legacy device is retrofitted with a Thing Description.

Web of Things (WoT) Scripting API

Abstract

The Web of Things (WoT) provides layered interoperability between Things by using the WoT Interfaces.

This specification describes a programming interface representing the WoT Interface that allows scripts run on a Thing to discover and consume (retrieve) other Things and to expose Things characterized by properties, Actions and Events.

Scripting is an optional “convenience” building block in WoT and it is typically used in gateways that are able to run a WoT Runtime and script management, providing a convenient way to extend WoT support to new types of endpoints and implement WoT applications like Thing Directory.

Mentions

  • JSON-LD

Argot

The Suitcase Words
  • W3C Web of Things (WoT)
  • IoT Platforms
  • interfaces
  • devices
  • services
  • implementation
  • multiple networking protocols
  • standardized
  • behavior
  • abstract architecture
  • use cases
  • mapped
  • scenarios,
    deployment scenarios,
    concrete deployment scenarios
  • standardization scope
  • WoT Thing Description (TD),
    Thing Description (TD)
  • formal mechanism
  • network interface
  • independent of implementation
  • participate
  • WoT Binding Templates,
    Binding Templates. [no acronym]
  • WoT Scripting API,
    Scripting API.
  • blocks,
    blocks and conditions,
    architectural blocks and conditions,
    non-normative architectural blocks and conditions.
  • scenarios,
    deployment scenarios,
    the context of deployment scenarios,
    in the context of deployment scenarios.
  • Web of Things (WoT)
  • Thing Description
  • narrow-waist
    a narrow-waist set,
    a narrow-waist set of interactions,
    a narrow-waist set of interactions based on a small vocabulary,
    a narrow-waist set of interactions based on a small vocabulary that makes it possible both,
    a narrow-waist set of interactions based on a small vocabulary that makes it possible both to integrate diverse devices and to allow diverse applications to interoperate.
  • JSON-LD
  • foundation … knowledge
  • a Web of Things-compatible legacy device
  • layered interoperability
  • Things
  • WoT Interface
  • Actions
  • Events
  • gateways
  • WoT Runtime
  • script management
  • endpoints
  • Thing Directory

Previously filled.

Comments are closed.