From 307adf18f3e73c08a8f588b128c1e080c8d9b5b2 Mon Sep 17 00:00:00 2001 From: Ben Francis Date: Fri, 23 Apr 2021 19:17:47 +0100 Subject: [PATCH] Add event log operations - fixes #892 --- index.html | 827 +++++++++++++++++++++++++++-------------------------- 1 file changed, 417 insertions(+), 410 deletions(-) diff --git a/index.html b/index.html index 8b410e2a6..3895e34e3 100644 --- a/index.html +++ b/index.html @@ -341,30 +341,30 @@ - +

- This document describes a formal model and a common representation - for a Web of Things (WoT) Thing Description 1.1. + This document describes a formal model and a common representation + for a Web of Things (WoT) Thing Description 1.1. A Thing Description describes the metadata and interfaces of Things, where a Thing is an abstraction of a physical or virtual entity that - provides interactions to and participates in the Web of Things. - Thing Descriptions provide a set of interactions based on a small vocabulary - that makes it possible both to integrate diverse devices and - to allow diverse applications to interoperate. + provides interactions to and participates in the Web of Things. + Thing Descriptions provide a 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 a JSON format that also allows JSON-LD processing. The latter provides a powerful foundation to represent knowledge about Things in a machine-understandable way. A Thing Description instance can be hosted by the Thing itself or hosted externally when a Thing has resource restrictions (e.g., limited memory space) - or when a Web of Things-compatible legacy device is retrofitted + or when a Web of Things-compatible legacy device is retrofitted with a Thing Description.

- This specification describes a superset of the features defined in Thing Description 1.0 [[WOT-THING-DESCRIPTION]]. - Unless otherwise specified, documents created with version 1.0 of this specification remain + This specification describes a superset of the features defined in Thing Description 1.0 [[WOT-THING-DESCRIPTION]]. + Unless otherwise specified, documents created with version 1.0 of this specification remain compatible with Thing Description 1.1.

@@ -405,17 +405,17 @@

Introduction

that indicate how the Thing can be used, schemas for the data exchanged with the Thing for machine-understandability, - and, finally, Web links to + and, finally, Web links to express any formal or informal relation to other Things or documents on the Web.

The Interaction Model of W3C WoT defines three types of Interaction Affordances: Properties (PropertyAffordance class) - can be used for sensing and controlling parameters, such as getting the current value or + can be used for sensing and controlling parameters, such as getting the current value or setting an operation state. Actions (ActionAffordance class) model - invocation of physical (and hence time-consuming) processes, but can also be used to - abstract RPC-like calls of existing platforms. + invocation of physical (and hence time-consuming) processes, but can also be used to + abstract RPC-like calls of existing platforms. Events (EventAffordance class) are used for the push model of communication where notifications, discrete events, or streams of values are sent asynchronously to the receiver. @@ -470,14 +470,14 @@

Introduction

- From this TD example, + From this TD example, we know there exists one Property affordance - with the title status. - In addition, - information is provided to indicate that this Property is accessible via - (the secure form of) the HTTP protocol with a GET method - at the URI https://mylamp.example.com/status - (announced within the forms structure by the + with the title status. + In addition, + information is provided to indicate that this Property is accessible via + (the secure form of) the HTTP protocol with a GET method + at the URI https://mylamp.example.com/status + (announced within the forms structure by the href member), and will return a string-based status value. The use of the GET method is not stated explicitly, but is one of the default assumptions defined by this document. @@ -491,15 +491,15 @@

Introduction

The Event affordance enables a mechanism for asynchronous messages to be sent by a Thing. - Here, a subscription to be notified upon a possible overheating event + Here, a subscription to be notified upon a possible overheating event of the lamp can be obtained by using HTTP with its long polling subprotocol on https://mylamp.example.com/oh.

- +

- This example also specifies the basic security scheme, + This example also specifies the basic security scheme, requiring a username and password for access. - Note that a security scheme is first given a name in + Note that a security scheme is first given a name in securityDefinitions and then activated by specifying that name in a security section. In combination with the use of the HTTP protocol this example @@ -519,7 +519,7 @@

Introduction

in some namespace. This mechanism can be used to integrate additional semantics to the content of the Thing Description instance, provided that formal knowledge, e.g., logic rules for a specific domain of application, can be found under the - given namespace. Contextual information can also help specify some configurations and + given namespace. Contextual information can also help specify some configurations and behavior of the underlying communication protocols declared in the forms field. Example 2 extends the TD sample from Example 1 by introducing a second definition in the @context to declare the @@ -534,7 +534,7 @@

Introduction

- +