The following pages and posts are tagged with
| Title | Type | Excerpt |
|---|---|---|
| Acknowledgements / Quality of Service | Page | Acknowledgements are a concept in Ditto used to indicate that a supported signal was successfully received or processed by either an internal Ditto functionality or an external subscriber of that signal. Acknowledgements can be seen as (potentially multiple) responses to a single signal like for example a twin command.... |
| APIs | Page | Ditto provides two ways to interact with: A REST-like HTTP API with a sophisticated resource layout that allows to create, read, update and delete Things and the Thing’s data. A JSON-based WebSocket API implementing the Ditto Protocol. HTTP API or WebSocket? The two ways... |
| Authentication and authorization | Page | You can integrate your solutions with Ditto via the HTTP API or via WebSocket. On all APIs Ditto protects functionality and data by using Authentication to make sure the requester is the one he/she claims to be, Authorization to make sure the requester is allowed to... |
| Change notifications | Page | Signals already described what an Event in Ditto is. Events are emitted after an entity (either a digital twin or an actual device) was changed. At the Ditto API there are different ways for getting notified of such events: Via the WebSocket API a WebSocket client... |
| Errors | Page | Errors are datatypes containing information about occurred failures which were either cause by the user or appeared in the server. Error model specification Status The “status” uses HTTP status codes semantics (see RFC 7231) to indicate whether a specific command has been successfully completed,... |
| Feature | Page | A Feature is used to manage all data and functionality of a Thing that can be clustered in an outlined technical context. For different contexts or aspects of a Thing different Features can be used which are all belonging to the same Thing and do not exist without this Thing.... |
| Messages | Page | Messages do not affect the state of a digital twin or an actual device. Therefore, Ditto does not handle messages like commands: there are no responses which are produced by Ditto and no events which are emitted for messages. Note: Ditto has no... |
| Thing Metadata | Page | A Thing in Ditto is also able to store metadata information, e.g. about single feature properties, complete features and also attributes or other data stored in a digital twin (thing). This metadata can contain additional information which shall not be treated as part of the twin’s value,... |
| Namespaces and Names | Page | Ditto uses namespaces and names for the IDs of important entity types like Things or Policies. Due to the fact that those IDs often need to be set in the path of HTTP requests, we have restricted the set of allowed characters. Namespace The namespace must conform to the... |
| Basic concepts overview | Page | Domain model Eclipse Ditto does not claim to know exactly which structure Things in the IoT have or should have. Its idea is to be as agnostic as possible when it comes to Thing data. Nevertheless, two coarse elements are defined... |
| Policy | Page | A Policy enables developers to configure fine-grained access control for Things and other entities easily. Note: Find the HTTP API reference at Policies resources. Authorization concept A specific policy provides someone (called subject), permission to read and/or write a given resource. <div... |
| Thing | Page | The versatile assets in IoT applications can be managed as Things. Thing Things are very generic entities and are mostly used as a “handle” for multiple features belonging to this Thing. Examples: Physical Device: a lawn mower, a sensor, a vehicle, a lamp. Virtual Device: a room in... |