Specification reference

Process

View this specification's source

Core transformation in the process graph. A Process connects an optional input to an optional output and can reference the Recipe that was executed.

#Properties

PropertyTypeCardinalityRequiredDescription
idText0..1MAYOptional identifier within an application-defined scope. Implementations that require an internal identifier SHOULD use this field. The domain model does not automatically assign identifiers.
typeText1MUSTProcess
additionalTypesText0..*MAYDiscriminator for decoration types.
nameText1MUSTHuman-readable name of the process
inputSample, Data0..1SHOULDSample or data object used as the input of this process
outputSample, Data0..1SHOULDSample or data object produced as the output of this process
executesRecipeRecipe0..1SHOULDRecipe executed by this process
parameterValuesAnnotation0..*SHOULDParameter annotations describing values used in this process

#Relationships

Diagram source
flowchart TD

    additionalTypes@{ shape: stadium, label: "string" }

    na@{ shape: stadium, label: "string" }
    i["Sample or Data (input)"]
    o["Sample or Data (output)"]

    Dataset --processes--> Process
    Process --input--> i
    Process --additionalTypes--> additionalTypes
    Process --"output"--> o
    Process --executesRecipe--> Recipe
    Process --parameterValues--> Annotation
    Process --name--> na

#Inputs and Outputs

Each Process represents one directed graph edge with at most one input and at most one output. Either endpoint MAY be absent. Fan-in, fan-out, and parallel lanes are represented by multiple Process instances.