This new field would specify the preferred variable name by which the entities are referred in other tools, like pybids. One example is the ce entity. The full name for the entity is "Contrast enhancing agent", the entity itself is ce, and the pybids variable is ceagent. To specify the preferred variable name (or shortened name) would make tools that use the schema more useable to outsiders.
The exact variable names could be taken directly from pybids at this point. I don't know if any other elements to the specification need this field, so please let me know if I'm missing something.
This came up in today's NIDM-Terms call. Tagging @jbpoline, @satra, and @yarikoptic.
EDIT: Perhaps a top-level YAML file should be added that describes the other YAML files/folders, in which case we have the YAML file/folder name (e.g., datatypes), the actual name ("Data type"), and some preferred variable name, as used in tools like pybids (datatype).
This new field would specify the preferred variable name by which the entities are referred in other tools, like
pybids. One example is theceentity. The full name for the entity is "Contrast enhancing agent", the entity itself isce, and the pybids variable isceagent. To specify the preferred variable name (or shortened name) would make tools that use the schema more useable to outsiders.The exact variable names could be taken directly from pybids at this point. I don't know if any other elements to the specification need this field, so please let me know if I'm missing something.
This came up in today's NIDM-Terms call. Tagging @jbpoline, @satra, and @yarikoptic.
EDIT: Perhaps a top-level YAML file should be added that describes the other YAML files/folders, in which case we have the YAML file/folder name (e.g.,
datatypes), the actual name ("Data type"), and some preferred variable name, as used in tools like pybids (datatype).