The Workflow Reference Model¶
Coalition, W. M. The Workflow Reference Model.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Orchestration
- Six commitments must hold together: two or more differentiated components, a directing locus carrying system-level state, an execution plan or policy, authority to assign and order, active management of the interfaces between components, and an integrated outcome that is nobody's individual output.
This sourceDocument TC00-1003, Issue 1.1, 1995. Separates build-time process definition from run-time enactment, and specifies an engine holding control data that identifies the state of each process and activity instance, navigating between activities and invoking both applications and human participants.
Supported in partVerified against the work's full text
The Reference Model describes a process definition plus an engine holding run-time state that sequences activities and invokes participants, covering several but not all of the six listed commitments.
“The workflow enactment service maintains internal control data either centralised or distributed across a set of workflow engines; this workflow control data includes the internal state information associated with the various process and activity instances under execution”
- Six commitments must hold together: two or more differentiated components, a directing locus carrying system-level state, an execution plan or policy, authority to assign and order, active management of the interfaces between components, and an integrated outcome that is nobody's individual output.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:23638b1e6b36 · see in the full table