this was missing from the release checklist... awaiting for comments / replies in respect to the ASN.1 grammar extracted (does it suit common tools / ASN.1 parser+unparser generators?) Since I lack knowledge what tools are out there and useful / used, I find the printed grammar at least human-readable (and as you can see in my comments there are already some suggestions how to improve (+how to migrate with backward compatibility -- I would like to preserve (a) read any data ever written to disk and (b) be able to communicate with not updated client versions -- though (a) can be relaxed with a migration script and a albatross release ;)
Together with git+https://github.com/hannesm/ocaml-asn1-combinators.git#wip-print-grammar this produces a human (and maybe machine-readable) grammar: https://gist.github.com/hannesm/5fd65c3a2ed50a7792ec1afcf86d2a1a To use the custom asn1-combinators branch, only the my_explicit needs to be changed (to pass the ?label argument to Asn.S.explicit).
this was missing from the release checklist... awaiting for comments / replies in respect to the ASN.1 grammar extracted (does it suit common tools / ASN.1 parser+unparser generators?) Since I lack knowledge what tools are out there and useful / used, I find the printed grammar at least human-readable (and as you can see in my comments there are already some suggestions how to improve (+how to migrate with backward compatibility -- I would like to preserve (a) read any data ever written to disk and (b) be able to communicate with not updated client versions -- though (a) can be relaxed with a migration script and a albatross release ;)