Sylvain Bellemare

see https://github.com/bigchaindb/cryptoconditions/pull/67#discussion_r123182031

See https://github.com/bigchaindb/cryptoconditions/pull/67#discussion_r123178351

This method seems to be more of an application-specific utility which could be found elsewhere. At least, for now, that would simplify the implementation and reduce the amount of things...

e.g.: ```python class CryptoConditionsError(Exception): """bla bla bla""" ```

Some questions: * Should the implementation silently ignore extra unsupported subtypes? If not, then when should the implementation complain about it? * At parsing time? * When `.validate()` is explicitly...

At least for now now, whenever it makes sense, we mirror the JS reference implementation. That is, for language-independent things.

Simply to make it more convenient to deal with registered types. Example: ```python RegisteredType = namedtuple('RegisteredType', 'type_id name class_') registered_type = RegisteredType(type_id=0, name='n', class_='c') registered_type.name ```

The new link is https://github.com/rfcs/crypto-conditions/

At https://github.com/interledger/python-crypto-conditions