CausalPathway
A multi-step mechanistic explanation showing how an initial cause leads to a final outcome through intermediate steps. This type captures complex causation that cannot be expressed with simple "A causes B" relationships.
Properties
Properties from CausalPathway (in addition to properties inherited from Thing):
| Property | Expected Type | Description |
|---|---|---|
| name | Text | Descriptive name for the pathway (e.g., "Rising Damp Mechanism") |
| description | Text | Summary of the causal mechanism |
| initialCause | Text or Thing | What starts the causal chain |
| pathwaySteps | CausalStep | Ordered sequence of steps in the causal chain |
| finalOutcome | Thing | Resulting condition or state after the pathway completes |
| timeframe | Duration or Text | Typical duration of the full pathway |
| acceleratingFactors | ContributingFactor | What speeds up the process |
| mitigatingFactors | ContributingFactor | What slows or prevents the process |
Examples
Example 1: Rising Damp Mechanism
A construction example showing how moisture moves through masonry:
JSON-LD
{
"@context": [
"https://schema.org",
{
"cs": "https://causalschema.org/",
"CausalPathway": "cs:CausalPathway",
"CausalStep": "cs:CausalStep"
}
],
"@type": "CausalPathway",
"name": "Rising Damp Mechanism",
"description": "How ground moisture penetrates walls lacking effective damp proof courses",
"initialCause": "Ground moisture in contact with wall base",
"pathwaySteps": [
{
"@type": "CausalStep",
"stepNumber": 1,
"mechanism": "Porous masonry in contact with damp ground",
"result": "Moisture enters wall base through capillary action"
},
{
"@type": "CausalStep",
"stepNumber": 2,
"mechanism": "Capillary action draws moisture upward through brick and mortar",
"result": "Moisture rises through wall, typically to 1-1.5m height"
},
{
"@type": "CausalStep",
"stepNumber": 3,
"mechanism": "Evaporation at wall surface deposits dissolved ground salts",
"result": "Hygroscopic salt accumulation in plaster"
},
{
"@type": "CausalStep",
"stepNumber": 4,
"mechanism": "Hygroscopic salts absorb atmospheric moisture",
"result": "Self-perpetuating damp even after source addressed"
}
],
"finalOutcome": {
"@type": "Thing",
"name": "Rising damp damage",
"description": "Damaged plaster, salt deposits, and potential structural decay"
},
"timeframe": "Months to years depending on conditions"
}Example 2: Generic Causal Pathway
A minimal implementation showing the essential structure:
JSON-LD
{
"@context": "https://causalschema.org/context.jsonld",
"@type": "CausalPathway",
"name": "Cause → Effect Mechanism",
"initialCause": "Initial trigger event",
"pathwaySteps": [
{
"@type": "CausalStep",
"stepNumber": 1,
"mechanism": "First process occurs",
"result": "Intermediate state A"
},
{
"@type": "CausalStep",
"stepNumber": 2,
"mechanism": "Second process follows",
"result": "Intermediate state B"
}
],
"finalOutcome": "End result"
}Usage Notes
When to Use CausalPathway
- Multi-step mechanisms — How something works through multiple transitions or stages
- Complex causation — Relationships that go beyond simple "A causes B"
- Process explanations — How conditions develop through sequential steps
- Mechanism of action — How treatments, failures, or interventions work
When NOT to Use CausalPathway
Use standard schema.org for simple relationships:
- Single-step causation — Use direct properties like
causeorriskFactor - Simple associations — Use standard schema.org relationship properties
Best Practices
- Order steps logically — Use
stepNumberto maintain correct sequence - Include time information — Use
timeDelayin CausalStep to show timing - Cite evidence — Include
evidenceSourcefor credibility - Be specific — Detailed mechanisms are more useful than vague descriptions