Johan Euphrosine

some pointer from @olofk: - https://edalize.readthedocs.io/en/latest/edam/api.html - https://github.com/olofk/fusesoc/blob/master/fusesoc/edalizer.py#L235

Given the heavy usage of python in the opensource EDA tooling, using https://www.python.org/dev/peps/pep-0484/, https://www.python.org/dev/peps/pep-0526/ and https://www.python.org/dev/peps/pep-0557/ could be an easier way to describe the format while allowing direct integration with...

https://github.com/protocolbuffers/protobuf or https://capnproto.org/ could also be an option if we're looking for x-language interop and possible over-the-wire invocation. the later in particular is also used for https://fpga-interchange-schema.readthedocs.io/ which could bring...

@olofk could you point me to examples of EDAM files that we could test schema validation against?

@olofk, used https://pypi.org/project/genson/ a jsonschema from those: https://gist.github.com/proppy/113ba53a8a339baf7f906f05db0b0883#file-edam-schema-json This of course should be refined with proper `description` property for every field but it gives an idea on how it could...

used https://pypi.org/project/datamodel-code-generator/ to generate a [pydantic](https://pydantic-docs.helpmanual.io/) model from https://github.com/olofk/edalize/issues/288#issuecomment-995862085: https://gist.github.com/proppy/113ba53a8a339baf7f906f05db0b0883#file-edam_model-py to get an idea how it would look like to define the schema using regular python typing annotation.

and https://gist.github.com/proppy/113ba53a8a339baf7f906f05db0b0883#file-edam-cue gives an idea of what it would like in https://cuelang.org/ (I personally have a bias :cupid: for that one)

@umarcor that doesn't seems to be an issue with `dataclass` itself, but rather with the `dataclasses-json` wrapper library, see https://gist.github.com/proppy/073181576ff968ad8abf77f8b7b258ac - dataclasses are capable of modeling both types, but don't...

@olofk maybe we can have it live in a `contrib` directory in the main edalize repo first and get it out as a separate thing if it becauses too invasive....

re: something FuseSoC github org, know that I think more about it would it also make sense to have CUE schema definitions for `.core` files? (maybe we could even express...