"@schedule{...}" activity primitive

The "@schedule{...}" and "@concurrency{...}" primitives are syntactic sugar to describe the scheduling of a machine’s executable components.

The "@schedule{...}" primitive may contain the evaluation politics of some (or all) the subcomponents of the parent machine.

The link between policies described with the "@schedule{...}" and "@concurrency{...}" primitives is the weak sequence "|;;|"

Example

For example, suppose we have a machine M containing four executable components A, B, C and D, with primitives :

Its implicit scheduling policy, triggered by primitive "@run{...}", will be :

Which is equivalent, by transitivity of operator "|;;|", to :