Skip to content

Slot: Chain Compatibility Assertions (chain_compatibility_assertions)

Declarations that two chain steps are compatible (e.g. daymet@1.0.0 expects geocoder@>=3.0.0 output column schema). Optional but enables strict-mode validation.

Tier: optional

Why this slot matters

Version bumps in one chain step can silently break the assumptions of the next (e.g. a changed output column schema); explicit compatibility declarations make such mismatches machine-checkable in strict mode instead of surfacing later as wrong values.

In plain terms

These are notes saying "step B was built to accept what step A produces" — like declaring that a plug and a socket follow the same standard, so a checker can catch mismatched pairs automatically.

URI: envar:slot/chain_compatibility_assertions

Applicable Classes

Name Description Modifies Slot
ProvenanceChain The ordered list of all upstream ToolRuns whose outputs were inputs to this... no

Properties

Type and Range

Property Value
Range String
Domain Of ProvenanceChain

Cardinality and Requirements

Property Value
Multivalued Yes

Examples

Value
None

Identifier and Mapping Information

Annotations

property value
tier optional
justification Version bumps in one chain step can silently break the assumptions of the next (e.g. a changed output column schema); explicit compatibility declarations make such mismatches machine-checkable in strict mode instead of surfacing later as wrong values.
explanation These are notes saying "step B was built to accept what step A produces" — like declaring that a plug and a socket follow the same standard, so a checker can catch mismatched pairs automatically.

Schema Source

Mappings

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

LinkML Source

name: chain_compatibility_assertions
annotations:
  tier:
    tag: tier
    value: optional
  justification:
    tag: justification
    value: Version bumps in one chain step can silently break the assumptions of the
      next (e.g. a changed output column schema); explicit compatibility declarations
      make such mismatches machine-checkable in strict mode instead of surfacing later
      as wrong values.
  explanation:
    tag: explanation
    value: These are notes saying "step B was built to accept what step A produces"
      — like declaring that a plug and a socket follow the same standard, so a checker
      can catch mismatched pairs automatically.
description: Declarations that two chain steps are compatible (e.g. `daymet@1.0.0`
  expects `geocoder@>=3.0.0` output column schema). Optional but enables strict-mode
  validation.
title: Chain Compatibility Assertions
examples:
- object: daymet@1.0.0 expects geocoder@>=3.0.0 output column schema
from_schema: https://w3id.org/linkml/microschemas/envar
rank: 1000
domain_of:
- ProvenanceChain
range: string
multivalued: true