Please describe your request. Is your feature request related to a problem?
Problem is that we don't have a consistent way of annotating our algorithms with metadata, and therefore, they aren't machine searchable, e.g. by schema.org. Further, this can provide more complete information to Zenodo (e.g. authors and intent etc) when we archive released versions of a transformer.
Also, there is a lot of hard-coding of information that could be put into a json file and used from there
Describe the solution you'd like
Some options:
Have users put algorithm information into a codemeta.json file, and perhaps have the template populate some fields automatically when a new transformer is created.
Use a common / expected python approach. It appears setup.py can be used for this. Then codemetapy can be used to generate the codemeta.json file
codemeta doesn't support the workflow information (inputs, outputs, etc) (e.g. in the NIST plugin.json) but maybe a single file could contain both the codemeta w/ jsonld and the workflow info
Please describe your request. Is your feature request related to a problem?
Problem is that we don't have a consistent way of annotating our algorithms with metadata, and therefore, they aren't machine searchable, e.g. by schema.org. Further, this can provide more complete information to Zenodo (e.g. authors and intent etc) when we archive released versions of a transformer.
Also, there is a lot of hard-coding of information that could be put into a json file and used from there
Describe the solution you'd like
Some options:
See https://codemeta.github.io/
Can use a validator https://codemeta.github.io/codemetar/reference/codemeta_validate.html
Additional Info
codemeta doesn't support the workflow information (inputs, outputs, etc) (e.g. in the NIST plugin.json) but maybe a single file could contain both the codemeta w/ jsonld and the workflow info