→ roadmap:blocks property

• Superproperty

  ---

  prov:wasInformedBy
  PROV ontology property

• Inverse Property

  ---

  roadmap:is-blocked-by
  Indicates blocking relationship in reverse direction

• Purpose

  ---

  Indicates that one roadmap item blocks another
  Used to express dependencies and prerequisites

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

Usage

Use blocks to express that one item must be completed before another can proceed:

- $type: roadmap:Task
  $: Main task
  blocks:
    - $: Dependent task
      $type: roadmap:Task

Inverse Relationship

roadmap:blocks is the inverse of roadmap:is-blocked-by. 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 blocks: for a more compact structure:

- $type: roadmap:Task
  $: Main task
  blocks:
    - $: Subtask 1
      $type: roadmap:Task
    - $: Subtask 2
      $type: roadmap:Task
      blocks:
        - $: Nested subtask
          $type: roadmap:Task