Such general term, independent from a specific approach, is necessary to contrast the content-oriented modelling principle with traditional activity-oriented workflow models (like Petri nets or BPMN) where a workflow is driven by a control flow and where the content production perspective is neglected or even missing.
The "artifact-centric" group itself (i.e. IBM Research) has generalized the characteristics of their approach and has used "information-centric" as an umbrella term in.
[2] Yet, the term information is too unspecific in the context of computer science, thus, "content-orientated workflows" is considered as good compromise.
The data-driven process structures provides a sophisticated workflow model being specialized on hierarchical write-and-review-processes.
The distribution of the enterprise application landscape with its business services is considered, yet, the workflow engine itself seems to be centralized.
The process enactment seems to be tightly coupled with a technically pre-integrated database management system infrastructure.
The form completion flow is controlled by transitions between object configurations each describing a progressing set of mandatory attributes.
The workflow engine embeds a functional fusion of 1) group-based instant messaging 2) with a shared work list editor 3) with version control.
The complete distributed case handling application is provided in form of a single active Document ("α-Doc").
The α-Doc is a case file (as information carrier) with an embedded workflow engine (in form of active properties).
The extensive conceptual claim of CSWC must be put into perspective by its actual solution scope, that is available as the CSCW Matrix.