bds:Rule

typeOperationscore

A Policy precise enough to check: if the condition holds, the consequence follows. Rules can be enforced by people or by an Automation.

Subclass of bds:Policy

Properties

Declared by BDS on this type. Everything else is inherited from schema.org.

Property	Expected type	Description
bds:condition	schema:Text	The "if" part of a rule, in words or as an expression.
bds:consequence	schema:Action, schema:Text	The "then" part of a rule: what happens when the condition holds.
bds:appliesTo	schema:Organization, schema:Thing, bds:Position, bds:Process	Who or what the policy covers.
bds:enforcedBy	schema:Person, bds:Position, bds:Process	The person, position, process or automation that makes sure the policy is followed.
bds:lifecycleStatus	bds:LifecycleStatus	Where the item is in its life: draft, active, on hold, completed, cancelled, archived or superseded. For a Task use schema:actionStatus instead; for a Deal use dealStatus.
bds:reviewDate	schema:Date	When the item should next be reviewed to confirm it is still right.
bds:supersedes	bds:Agreement, bds:Decision, bds:Policy, bds:Process	An earlier item of the same kind that this one replaces. The earlier item should carry SupersededStatus or DecisionSuperseded.

Where this term shows up elsewhere in the vocabulary.