Slot: Tool Version (tool_version)

Semver tool version. Mandatory.

Tier: core

Why this slot matters

Two versions of the same tool can produce different outputs from identical inputs, so "we ran daymet" without a version is not reproducible. It is mandatory because it is the cheapest and most decisive reproducibility anchor after the tool name.

In plain terms

Software changes over time, and a version number labels one specific edition of it — like the edition of a book. Recording it says exactly which edition of the tool did the work.

URI: envar:slot/tool_version

Applicable Classes

Name	Description	Modifies Slot
ToolRun	A single tool invocation that produced an output from one or more inputs: too...	yes

Properties

Type and Range

Property	Value
Range	String
Domain Of	ToolRun

Cardinality and Requirements

Property	Value

Examples

Value
1.0.0

See Also

• https://semver.org/

Identifier and Mapping Information

Annotations

property	value
tier	core
justification	Two versions of the same tool can produce different outputs from identical inputs, so "we ran daymet" without a version is not reproducible. It is mandatory because it is the cheapest and most decisive reproducibility anchor after the tool name.
explanation	Software changes over time, and a version number labels one specific edition of it — like the edition of a book. Recording it says exactly which edition of the tool did the work.
covered_by	None

Schema Source

• from schema: https://w3id.org/linkml/microschemas/envar

Mappings

Mapping Type	Mapped Value
self	envar:tool_version
native	envar:tool_version

LinkML Source

name: tool_version
annotations:
  tier:
    tag: tier
    value: core
  justification:
    tag: justification
    value: Two versions of the same tool can produce different outputs from identical
      inputs, so "we ran daymet" without a version is not reproducible. It is mandatory
      because it is the cheapest and most decisive reproducibility anchor after the
      tool name.
  explanation:
    tag: explanation
    value: Software changes over time, and a version number labels one specific edition
      of it — like the edition of a book. Recording it says exactly which edition
      of the tool did the work.
  covered_by:
    tag: covered_by
    annotations:
      omop_gaia:
        tag: omop_gaia
        annotations:
          extent:
            tag: extent
            value: absent
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: no column
          note:
            tag: note
            value: No gaia table records the gaia-db image version.
      degauss:
        tag: degauss
        annotations:
          extent:
            tag: extent
            value: full
          status:
            tag: status
            value: verified
          where:
            tag: where
            value: output filename container image tag (e.g. daymet_1.0.0) and ghcr.io/degauss-org/...
              reference
          evidence:
            tag: evidence
            value: COMPARISON.md §K — tool version ✅ carried as the container image
              tag in the filename
          note:
            tag: note
            value: Container image tag baked into the filename pins the exact tool
              version.
      amadeus:
        tag: amadeus
        annotations:
          extent:
            tag: extent
            value: absent
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: no column
          note:
            tag: note
            value: Amadeus's R package version lives in the object attributes but
              no native file records it.
      cher:
        tag: cher
        annotations:
          extent:
            tag: extent
            value: partial
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: table_dictionary.version (resource version 001/002...) via §2.6
          note:
            tag: note
            value: C-HER carries a resource version code, but it versions the dataset
              resource, not a per-run producing tool.
      codata:
        tag: codata
        annotations:
          extent:
            tag: extent
            value: out_of_layer
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: no column
          note:
            tag: note
            value: Per-run tool version is instance-layer; out of scope for CODATA
              EV/CDIF conceptual layer.
description: Semver tool version. Mandatory.
title: Tool Version
examples:
- value: 1.0.0
from_schema: https://w3id.org/linkml/microschemas/envar
see_also:
- https://semver.org/
rank: 1000
domain_of:
- ToolRun
range: string