How do we define input paramters?

[simonduq]

Currently, values assigned are just textual, e.g. "traffic-pattern: many-to-many", or "payload: 2B--128B". We probably want something in a strict format, understandable by a machine.

But also at some point, textual description is needed somewhere, to define e.g. what we mean with the various patterns and properties, so that they can be implemented (by the testbed or the firmware).

[romain-jacob]

Agree 100%. Textual description is definitely needed for the profile to be legible.
But we also need a formalized 'input' formatting, so that eventually we can reach the goal of a testbed or simulator directly inputting a profile to setup an experiment.

-> The question becomes: what is a right data format that enables both? I am only familiar with xml-based files, the like Flocklab is using. But I would assume there are many other options. Just need something 'easy to parse'. Maybe YAML is not the best thing here.