The MessageTaxonomyURL should link to a versioned canonical specification of the taxonomy for the message. For example, something like https://some-open-standards.org/foo_spec/v1.3.432/
That document should unambiguously define the semantics of a number of numeric codes (uint values). The document should be immutable and permanent. New versions of the document should be created using an open and transparent specification system such as COSS.
This is a less-is-more approach, by removing the hardcoded ack enumerations, we actually make the component much more versatile.
I'm not sure how much should go to the blockchain; is it the whole structure (etherium style) or a single hash (bitcoin style). More analysis required.
/api/ack/codes
is the wrong approach.We should have two values:
The MessageTaxonomyURL should link to a versioned canonical specification of the taxonomy for the message. For example, something like
https://some-open-standards.org/foo_spec/v1.3.432/
That document should unambiguously define the semantics of a number of numeric codes (uint values). The document should be immutable and permanent. New versions of the document should be created using an open and transparent specification system such as COSS.
This is a less-is-more approach, by removing the hardcoded ack enumerations, we actually make the component much more versatile.