bds:Incident
typeRisk and compliancecoreSomething that did go wrong: an outage, a breach, an injury, a failed delivery. Record its severity, what it affects, the rootCause and the postmortem. Start and end use schema:startDate and schema:endDate.
Subclass of schema:Event · inherits 69 schema.org properties from Event and above
Properties
Declared by BDS on this type. Everything else is inherited from schema.org.
| Property | Expected type | Description |
|---|---|---|
| bds:affects | schema:Organization, schema:Product, schema:Service, bds:Process, bds:Tool | What the incident or risk touches: a tool, a process, a unit, a product or a customer. |
| 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:postmortem | schema:CreativeWork, bds:Decision | The write-up of what happened and what will change, as a document or a decision. |
| bds:priority | bds:PriorityLevel | How urgent or important the item is. |
| bds:rootCause | schema:Text | The underlying reason the incident happened, once known. |
| bds:severity | bds:Level | How serious the incident is. |
Widened onto it
schema.org properties declared usable on this type. Reuse these before proposing a new one.
References
Where this term shows up elsewhere in the vocabulary.
- Referenced as expected type by
- Nothing points here yet.
- Properties declared on it
- bds:affects, bds:lifecycleStatus, bds:postmortem, bds:priority, bds:rootCause, bds:severity