Closed AdrianValentinCiu closed 2 months ago
The use of servicemeta is experimental for us (EBRAINS Curation team), so we might get back to you with change requests once this is deployed, but as far as I can see this looks good.
It is a bit odd, to have these JSON files in the code with the hard-coded version number and details, and the need to have 2 of them (one for the Software and one for the WebService)
Depending on your build process, perhaps you could reduce duplication by generating the servicemeta from the codemeta with some kind of diff?
Considered: