{"action":"opened","issue":{"url":"https://api.github.com/repos/iot-benchmark/iot-benchmark.github.io/issues/8","repository_url":"https://api.github.com/repos/iot-benchmark/iot-benchmark.github.io","labels_url":"https://api.github.com/repos/iot-benchmark/iot-benchmark.github.io/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/iot-benchmark/iot-benchmark.github.io/issues/8/comments","events_url":"https://api.github.com/repos/iot-benchmark/iot-benchmark.github.io/issues/8/events","html_url":"https://github.com/iot-benchmark/iot-benchmark.github.io/issues/8","id":328133250,"node_id":"MDU6SXNzdWUzMjgxMzMyNTA=","number":8,"title":"Components of an experimental setup","user":{"login":"simonduq","id":1425999,"node_id":"MDQ6VXNlcjE0MjU5OTk=","avatar_url":"https://avatars1.githubusercontent.com/u/1425999?v=4","gravatar_id":"","url":"https://api.github.com/users/simonduq","html_url":"https://github.com/simonduq","followers_url":"https://api.github.com/users/simonduq/followers","following_url":"https://api.github.com/users/simonduq/following{/other_user}","gists_url":"https://api.github.com/users/simonduq/gists{/gist_id}","starred_url":"https://api.github.com/users/simonduq/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/simonduq/subscriptions","organizations_url":"https://api.github.com/users/simonduq/orgs","repos_url":"https://api.github.com/users/simonduq/repos","events_url":"https://api.github.com/users/simonduq/events{/privacy}","received_events_url":"https://api.github.com/users/simonduq/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-31T13:13:35Z","updated_at":"2018-05-31T13:13:35Z","closed_at":null,"author_association":"MEMBER","body":"The current proposal (https://github.com/iot-benchmark/iot-benchmark.github.io/wiki/Data-Schema#experimental-setup---base-components) defines *radio*, *platform* and *environment* as distinct entities. While this might feel neat, I'm not sure it is worth the added complexity (of adding and maintaining a radio, platform and env every time a new testbed/simulation is added/modified).\r\n\r\nIsn't it sufficient to just have environment (e.g. \"Flocklab\") and then as part of the *result*, where we already provide a list of nodes, also specify the platform&radio?"}}
{"actor":{"display_login":"simonduq"}}