You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add processing:name to complement processing:version #39
processing:version describes the version of the primary processing software or chain, but there is no corresponding field for its name. processing:software can list multiple tools without identifying the primary one, while processing:lineage is free text.
I propose that we add an optional processing:name string identifying the primary software or processing chain. When both fields are present, processing:name and processing:version would describe the same software or chain.
Maybe name is not the right term but something to identify the thing that processing:version describes could be helpful.
As a second thought: Why is it important to know what then primary software name is? The software + version can be listed, just not be set as primary and I'm wondering what the usecase behind it is.
Activity
gadomski commentedon Sep 10, 2026
👍🏼 From the
processing:versiondescription:This implies that there could be other processing softwares or chains, so a
namefield to specify which software or chain makes sense.m-mohr commentedon Oct 6, 2026
Seems reasonable, but don't like the name too much. And I assume the schema should verify that if the "name" is provided also a version is provided?!
m-mohr commentedon Oct 11, 2026
As a second thought: Why is it important to know what then primary software name is? The software + version can be listed, just not be set as primary and I'm wondering what the usecase behind it is.