Skip to content

Commit 370d2f3

Browse files
spec: add network-directed specification (#2864)
## New Specification: `network-directed` Related to #2858 --- ### specification.md # network-directed: Directed Network Graph ## Description A directed network graph visualizes relationships between entities using nodes connected by edges with arrows, indicating the direction of relationships or flow. Unlike undirected graphs, directed graphs reveal asymmetric relationships such as dependencies, hierarchies, or information flow. The arrows clearly communicate which entity points to which, making cause-and-effect relationships and directional dependencies immediately visible. ## Applications - Mapping software module dependencies to understand build order and identify circular dependencies - Visualizing citation networks where arrows show which papers cite which others - Displaying organizational reporting structures or workflow approval chains - Analyzing web page link structures to understand navigation patterns and page authority ## Data - `nodes` (list of dicts) - entities with unique IDs and optional attributes like label or group - `edges` (list of tuples/dicts) - directed connections as (source_id, target_id) pairs where arrows point from source to target - `weight` (numeric, optional) - edge weight that can affect arrow thickness or style - Size: 10-50 nodes for clear static visualization (larger networks require interactive exploration) - Example: Software package dependencies where arrows show import direction ## Notes - Arrows should be clearly visible and appropriately sized relative to node size - Consider curved edges when nodes have bidirectional connections to avoid arrow overlap - Node position can use force-directed layout, hierarchical layout, or circular layout depending on data structure - Arrow style (filled, open, curved) should be consistent throughout the graph --- **Next:** Add `approved` label to the issue to merge this PR. --- :robot: *[spec-create workflow](https://github.com/MarkusNeusinger/pyplots/actions/runs/20608361723)* Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
1 parent 6368e5e commit 370d2f3

2 files changed

Lines changed: 58 additions & 0 deletions

File tree

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# network-directed: Directed Network Graph
2+
3+
## Description
4+
5+
A directed network graph visualizes relationships between entities using nodes connected by edges with arrows, indicating the direction of relationships or flow. Unlike undirected graphs, directed graphs reveal asymmetric relationships such as dependencies, hierarchies, or information flow. The arrows clearly communicate which entity points to which, making cause-and-effect relationships and directional dependencies immediately visible.
6+
7+
## Applications
8+
9+
- Mapping software module dependencies to understand build order and identify circular dependencies
10+
- Visualizing citation networks where arrows show which papers cite which others
11+
- Displaying organizational reporting structures or workflow approval chains
12+
- Analyzing web page link structures to understand navigation patterns and page authority
13+
14+
## Data
15+
16+
- `nodes` (list of dicts) - entities with unique IDs and optional attributes like label or group
17+
- `edges` (list of tuples/dicts) - directed connections as (source_id, target_id) pairs where arrows point from source to target
18+
- `weight` (numeric, optional) - edge weight that can affect arrow thickness or style
19+
- Size: 10-50 nodes for clear static visualization (larger networks require interactive exploration)
20+
- Example: Software package dependencies where arrows show import direction
21+
22+
## Notes
23+
24+
- Arrows should be clearly visible and appropriately sized relative to node size
25+
- Consider curved edges when nodes have bidirectional connections to avoid arrow overlap
26+
- Node position can use force-directed layout, hierarchical layout, or circular layout depending on data structure
27+
- Arrow style (filled, open, curved) should be consistent throughout the graph
Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
# Specification-level metadata for network-directed
2+
# Auto-synced to PostgreSQL on push to main
3+
4+
spec_id: network-directed
5+
title: Directed Network Graph
6+
7+
# Specification tracking
8+
created: 2025-12-30T23:43:28Z
9+
updated: 2025-12-30T23:43:28Z
10+
issue: 2858
11+
suggested: MarkusNeusinger
12+
13+
# Classification tags (applies to all library implementations)
14+
# See docs/concepts/tagging-system.md for detailed guidelines
15+
tags:
16+
plot_type:
17+
- network
18+
- graph
19+
- directed
20+
data_type:
21+
- network
22+
- relational
23+
- categorical
24+
domain:
25+
- general
26+
- technology
27+
- research
28+
features:
29+
- directed
30+
- arrows
31+
- flow-visualization

0 commit comments

Comments
 (0)