json_of_jsonm is designed to provide a thin layer on top of jsonm that allows conversion to and from a reasonably standard json type. In addition, where appropriate, the API attempts to follow standard conventions (the string module defines a type t and {of,to}_string functions for example) and provide exception and result based eror reporting
Finally, additional I/O mechanisms can easily be defined with an example Async module shown in the examples section of the README.md
ezjsom in comparison provides a number of useful functions that extend the jsonm library as weill as adding Lwt support. However, it follows jsonm typing and does not support I/O methods other than those already provided by the library
Which you use will depend on your needs, for me json_of_jsonm is used to handle thinks like RESTful APIs using Async libraries but others may find ezsjonm’s access functions more useful.