Skip to content

docs(rwm): trim trade-off prose, align diagram with dj.Diagram, restructure concrete-first#186

Open
dimitri-yatsenko wants to merge 4 commits into
mainfrom
wip/trim-rwm-deliberate-tradeoff
Open

docs(rwm): trim trade-off prose, align diagram with dj.Diagram, restructure concrete-first#186
dimitri-yatsenko wants to merge 4 commits into
mainfrom
wip/trim-rwm-deliberate-tradeoff

Conversation

@dimitri-yatsenko

@dimitri-yatsenko dimitri-yatsenko commented Jun 13, 2026

Copy link
Copy Markdown
Member

Summary

Three cleanups on src/explanation/relational-workflow-model.md:

  1. Trim the "deliberate trade-off" subsection. After Expand Relational Workflow Model concept page #184 (expanded RWM intro) and Add two deeper concept pages: Schema as a Workflow Specification + Comparison to Workflow Languages #185 (new Comparison to Workflow Languages page), the same argument lived in two places. Now: one-paragraph mention on the RWM page that links out to the developed treatment on the Comparison page.

  2. Align the worked-example diagram with dj.Diagram notation. The Mermaid in the page now matches the actual conventions from datajoint-python/src/datajoint/diagram.py:1017-1082:

    • Manual: green rectangle
    • Lookup: plaintext (no border/fill) — was previously a filled rectangle
    • Imported: blue stadium shape (closest Mermaid approximation to Graphviz ellipse)
    • Computed: red stadium shape (same)
    • Inline tier-name and make() annotations on each node removed; tier is conveyed by shape + color, as in real dj.Diagram output.
    • A lead paragraph above the diagram spells out the convention.
  3. Restructure concrete-first and reframe as added interpretation, not shift.

    • New order: tight opening → worked example → Three interpretations (Codd/Chen/RWM) → A semantic interpretation, not a departure → trade-off pointer → Substrate consequences → Beneath the model → Two readings of the same schema → Further reading.
    • Renamed "Four shifts from the classical relational model" → "A semantic interpretation, not a departure"; bullets now read additively ("tables also represent workflow steps") rather than contrastively ("not merely categories of records"). Classical relational concepts apply unchanged; RWM layers a semantic interpretation on top.
    • Renamed "From transactions to transformations" → "Two readings of the same schema"; lead-in clarifies both readings hold simultaneously.

Also removes the .github/follow-ups/trim-rwm-deliberate-tradeoff.md tracker that scheduled the first cleanup.

Test plan

  • mkdocs build --strict succeeds (no new broken links/anchors)
  • Page reads cleanly: opening → worked example → historical lineage → semantic interpretation
  • Diagram renders in MkDocs Mermaid preview with correct shapes and colors
  • Link from RWM → Comparison resolves
  • Reviewed locally via mkdocs serve

Placeholder for follow-up work after #184 (expand RWM) and #185 (deeper
concept pages) merge. Tracker file outlines what to trim, why, and how to
pick the work up once both upstream PRs land.

No content changes to docs source in this PR. The tracker file is to be
deleted in the same commit that applies the trim.
The developed argument lives on the Comparison to Workflow Languages
page (added in #185). The RWM page now mentions the trade-off in one
paragraph and links out, preventing drift between two homes for the
same argument.

Removes the .github/follow-ups/ tracker that scheduled this work.
@dimitri-yatsenko dimitri-yatsenko force-pushed the wip/trim-rwm-deliberate-tradeoff branch from c60ffe6 to cbb578f Compare June 14, 2026 16:01
@dimitri-yatsenko dimitri-yatsenko changed the title WIP: trim deliberate-trade-off prose from RWM page (depends on #184 + #185) docs(rwm): trim deliberate-trade-off prose; link to Comparison page Jun 14, 2026
@dimitri-yatsenko dimitri-yatsenko marked this pull request as ready for review June 14, 2026 16:01
Match the conventions from datajoint-python's dj.Diagram
(diagram.py:1017-1082):

- Manual: green rectangle (unchanged)
- Lookup: plaintext — no border/fill (was a filled rectangle)
- Imported: blue stadium-shaped node — closest Mermaid approximation
  to dj.Diagram's ellipse
- Computed: red stadium-shaped node — same

Drop the inline tier-name and make() annotations on each node; tier
is now conveyed by shape and color alone, as in the real diagrams.
A new lead paragraph spells out the convention so the reader can
decode the diagram without a separate legend.
@dimitri-yatsenko dimitri-yatsenko changed the title docs(rwm): trim deliberate-trade-off prose; link to Comparison page docs(rwm): trim deliberate-trade-off prose + align diagram with dj.Diagram notation Jun 14, 2026
Two structural cleanups on relational-workflow-model.md:

Concrete-first ordering. Open with a tight paragraph naming the
model, then lead with the worked example (diagram + walkthrough).
The historical lineage (Codd/Chen/RWM three interpretations) now
follows the example, placing DataJoint's contribution in context
once the reader has a concrete pipeline to anchor on. The closing
side-by-side reading table moves to the end of the page.

Reframe as interpretation, not departure. Classical relational
concepts (tables, rows, foreign keys, normalization, the query
algebra) apply unchanged; RWM adds a semantic interpretation on
top. Renamed and rewrote two sections to reflect this:

- "Four shifts from the classical relational model"
  → "A semantic interpretation, not a departure"
  Bullets now read additively ("tables also represent workflow
  steps") rather than contrastively ("not merely categories").

- "From transactions to transformations"
  → "Two readings of the same schema"
  Lead-in clarifies both readings hold simultaneously. Column
  header changes from "Traditional view" to "Classical reading."
@dimitri-yatsenko dimitri-yatsenko changed the title docs(rwm): trim deliberate-trade-off prose + align diagram with dj.Diagram notation docs(rwm): trim trade-off prose, align diagram with dj.Diagram, restructure concrete-first Jun 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant