From 7bec660eb0daa5257dcfe265c47712a87f3a1752 Mon Sep 17 00:00:00 2001 From: Manos Date: Sun, 8 Nov 2015 02:25:43 +0200 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a8ca470..8089934 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@ EasyHarvest aims to simplify the deployment and controlled execution of large-sc Data recorded by Sensing Tasks (STs), processed by Privacy Mechanisms (PMs) and sent to the EasyHarvestServer (EHS) by the EasyHarvestClients (EHCs) should follow a specific structure shown in the table below to achieve proper communication and function of the framework entities. This way, we patronize the data collected without limiting application capabilities and Sensing Task developer freedom. For instance, the values field from an application that monitors location would typically contain [0] longitude, [1] latitude and optionally [2] altitude and [3] speed. | Type | Name | Description | -| ------------- | ------------- | ------------- | +| :-----------: | :-----------: | ------------- | | int | device | The device id assigned by the server during the client registration. | | int | task | The identifier of the sensing task that produced this data. | | int | sensor | The identifier of the sensor that generated this event. |