← roadmap:is-blocked-by property

• Superproperty

  ---

  prov:wasInformedBy
  PROV ontology property

• Inverse Property

  ---

  roadmap:blocks
  Indicates blocking relationship in forward direction

• Purpose

  ---

  Indicates that one roadmap item is blocked by another
  Used to express dependencies from the dependent item's perspective

roadmap:is-blocked-by indicates that one roadmap item is blocked by another. It is a subproperty of prov:wasInformedBy, allowing blocking relationships to be integrated with provenance tracking.

Usage

Use is-blocked-by to express dependencies from the perspective of the dependent item:

- $id: _:task-b
  $type: roadmap:Task
  $: Task B
  is-blocked-by:
    - _:task-a

Inverse Relationship

roadmap:is-blocked-by is the inverse of roadmap:blocks. If task A blocks task B, then task B is blocked by task A:

# These are equivalent:
- $id: _:task-a
  $type: roadmap:Task
  $: Task A
  blocks:
    - _:task-b

- $id: _:task-b
  $type: roadmap:Task
  $: Task B
  is-blocked-by:
    - _:task-a

Nesting

Tasks can be nested directly under is-blocked-by: for a more compact structure:

- $type: roadmap:Task
  $: Dependent task
  is-blocked-by:
    - $: Prerequisite 1
      $type: roadmap:Task
    - $: Prerequisite 2
      $type: roadmap:Task