Specification Guide
The normative specification lives in docs/spec. ProcessCore is the small shared model. Decorations specialize or extend it for ISA, Workflow Run, and Datamap use cases without changing the core requirements.
ProcessCore
|
Core entities:
Entity |
Source |
|---|---|
Dataset |
|
LabProcess |
|
LabProtocol |
|
Material |
|
Data |
|
PropertyValue |
|
FormalParameter |
|
DefinedTerm |
Decorations
Decorations add domain-specific meaning through additionalType, specialized properties, and decoration-specific entities.
Decoration |
Purpose |
Source |
|---|---|---|
ISA |
Investigation, Study, Assay, Source, Sample, and ISA property value roles |
|
Workflow Run |
Workflow and Run datasets, workflow protocols, and workflow invocations |
|
Datamap |
Datamap datasets and DataContext annotations for file fragments |
Naming Notes
The current core vocabulary uses LabProcess and LabProtocol, not the older placeholder names Process and Protocol.
For process I/O, the current core and YAML schema names are:
inputsoutputsexecutesProtocolparameterValueadditionalProperty
Some legacy/profile-shaped examples and upstream references use RO-Crate or Bioschemas names such as object, result, and executesLabProtocol. See Examples and schemas for how those files are treated.
Querying
The query use cases are described in Querying. The implementation exposes Path as a returned value object, while traversal and query operations are attached to the model types in src/ProcessCore/Graph.fs.
ProcessCore