Skip to content
Source on GitHubVisitors

17. Today's diagram definitions

Contents of FBL 0.17

The 25 diagram definitions in definitions/diagrams/ were written before FBL; 24 of them name a persistence plugin as their format and the timeline names DISL's yaml. Under FBL:

Outcome Definitions
A declared binding (15 plus the timeline) timeline (timeline.fbl), dependency graph, functional decomposition graph, hype cycle graph, Databricks bundle, job and pipeline ((FBL 0.10) databricks.fbl, the one binding the three readings of a bundle file share; databricks-job.fbl and databricks-pipeline.fbl are the per-reading bindings of 0.1), causal loop diagram (causal-loop-diagram.fbl), Wardley map ((FBL 0.12) wardley-map.fbl (grammar), the .owm read by the grammar family with wardley-map.lark), mind map (mindmap.fbl), the six C4 types (structurizr.fbl (grammar), (FBL 0.11) the Structurizr DSL read by the grammar family with structurizr.lark)
A declared binding, with a plugin for part of its reading Azure DevOps pipeline (template expansion)
A plugin reader under the contract (8) the four W3C types (w3c-turtle.fbl), SPARQL query, .NET dependency graph (dotnet-dependency-graph.fbl), Ansible structure (ansible-structure.fbl), Helm chart (helm-chart.fbl)

The timeline's specification would then say:

{
  "persistence": {
    "format": "fbl",
    "binding": "https://etalii.net/adp/fbl/examples/0.1/timeline.fbl#timeline",
    "ids": { "strategy": "uuid-v4", "encoding": "base36" },
    "view": { "store": [] }
  }
}

Rewriting the definitions to use FBL is follow-up work, as is implementing FBL in the hosts. The per-definition record is in the feature that introduced FBL, specs/005-format-binding/inventory.md.