https://datatracker.ietf.org/doc/draft-devault-bare/
BARE RFC draft 02 has been published
@sir
Yeah, trivial to add means that everybody will do it differently and the only way to know will be comments in the schema file (like in the example). This will make communicating this fundamental physical and human concept incompatible and only agreeable on with documentation. Anyway, this is good for what it is. Thanks for the link.
@brombek there are many data types for which this argument could be made
@sir
True. Thanks.
@brombek it's more concise than COBR, both the encoded messages and the complexity of the spec. It has a grammar, the COBR grammar is not finalized.
There is a Rust impl here:
https://git.sr.ht/~tdeo/serde_bare
NACK to native time encoding, but it's trivial to add your own with a user-defined type