Also cleans up the schema a bit.
Note that there's still a test that isnt passing

Distinguishes between uints/ints/floats for restricting
types of choices in choices list

The schema now limits the range entries according to the
specific numerical type (uint/int/float).
Also refactors out all the nose.tools.assert_true/false calls.

Any "choice" type parameter needs >=3 choices to be valid
(otherwise it could be a boolean or a constant)

Fixes failed plotter tests as well

Uses the json schema draft 6/7 keywords to better specify
the restrictions on choice-type parameters, and adds tests

Also adds tests & new objects to check validation rules.
Uses new json schema draft 7 keywords

Algorithm range parameters were previously able to be strings,
booleans, numbers, or a mix of those three.

"parameter_value" is the same as the "value" definition
defined in the commons schema

See #74

Complex numbers as parameter types are only supported in
dataformats

See #74

Add a plotterparameter schema file

Closes #66

See merge request !55

Adds schema file, beat.core integration, test files & tests

Closes #66

Fix simple/2 database code

See merge request !68

The migration script didn't properly copy the code.

Protocol template

See merge request !67

Version of beat.env.system.python to 1.3.0r5
Version of beat.env.db.example to 1.4.0r5

It was useless since the file path was store in an unrelated
variable.

This scripts creates the needed protocol templates unless a protocol
template with the same name already exists.

Add BEAT framework classifier

Closes #75

See merge request !66

Factorize simplejson

See merge request !64