Hi,
I'm working on the Research Software Ecosystem, specifically on tools and workflows metadata. I noticed that in the Codex, the EDAM annotations are EDAM labels, and not EDAM URIs. This can cause issues, as classes' main labels can change over time, while URIs are permanent. Another issue is that in some (rare) cases, a class can switch from a subclass to another one (for example, an operation can become a topic). Finally, in some (rare) cases, several classes will have the same main label. While we try to avoid such cases in EDAM, they do happen exceptionally.
An example: the tool abyss is annotated with the topic "Sequence assembly", which also happens to be an operation and a data type.
Is it at all feasible to switch from labels to URIs? For now I am doing it on my end, but it's not ideal given the cases mentioned above.
Hi,
I'm working on the Research Software Ecosystem, specifically on tools and workflows metadata. I noticed that in the Codex, the EDAM annotations are EDAM labels, and not EDAM URIs. This can cause issues, as classes' main labels can change over time, while URIs are permanent. Another issue is that in some (rare) cases, a class can switch from a subclass to another one (for example, an operation can become a topic). Finally, in some (rare) cases, several classes will have the same main label. While we try to avoid such cases in EDAM, they do happen exceptionally.
An example: the tool
abyssis annotated with the topic "Sequence assembly", which also happens to be an operation and a data type.Is it at all feasible to switch from labels to URIs? For now I am doing it on my end, but it's not ideal given the cases mentioned above.