From 9d0e3e32286acdedd0a7e804f50e55f3311c449a Mon Sep 17 00:00:00 2001 From: Matteo Francia Date: Tue, 5 Jan 2021 11:17:25 +0100 Subject: [PATCH] Update iot-agent-json.md --- docs/iot-agent-json.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/iot-agent-json.md b/docs/iot-agent-json.md index 51bc8da..cedc050 100644 --- a/docs/iot-agent-json.md +++ b/docs/iot-agent-json.md @@ -383,7 +383,7 @@ The response will look similar to the following: The IoT Agent acts as a middleware between the IoT devices and the context broker. It therefore needs to be able to create context data entities with unique IDs. Once a service has been provisioned and an unknown device makes a measurement the IoT Agent add this to the context using the supplied `` (unless the device is recognized and -can be mapped to a known ID. +can be mapped to a known ID). There is no guarantee that every supplied IoT device `` will always be unique, therefore all provisioning requests to the IoT Agent require two mandatory headers: