Bump to next dev release.
Merge remote-tracking branch 'origin/master' into next
Make the protobuf format more clear in README.
Add 'extras' field to JSON messages for custom data.
Expand diagnostic mode field to a full byte's range.

Fixed #10.
Explain when to use JSON vs. binary.
Require an 'action' in diagnostic requests.

It wasn't very clean to try and infer a delete/create/update based on
the value of the frequency field - this will require a little more code,
but as they say in Python, explicit is better than implicit.

Fixed https://github.com/openxc/openxc-message-format/issues/12
Remove 'update' feature of diag request commands.
Add a 'status' field to command responses.
Move action field to ControlCommand in binary format.
Note that 0x prefix on hex strings is optional.
Re-build with nanopb v0.3.1.
Add passthrough command and refactor commands in binary format.

The ControlCommand is now more like a VehicleMessage - it has a 'type'
and many optional fields pointing to the various types. If the type is
diagnostic, the client should look at the diagnostic_request field.
Merge remote-tracking branch 'origin/latest-nanopb' into passthrough-command

Conflicts:
	gen/cpp/openxc.pb.c
	gen/cpp/openxc.pb.h
Simplify passthrough command to just a boolean.
Deprecate "translated" and "raw" verbiage.

Partway towards #16 but need to updated the binary format, too.
Add missing comma in example.
Add a control command to control AF bypass status.

See openxc/vi-firmware#301.
Update compiled files.
Add a command to change message format while running.