Rethinking API, reimplementing rules

In the first release problems came up, so there was a good chance to capture the requirements. At the same time I thought it was safe to implement the encoding/decoding rules by property-based testing driven development. It is a fun, and it covered many errors I didn't think about.
I also reworked the conversion rules, to get rid of extra tuples, and make place for conversion option as well.