Rules for diagrams in FPSOT repositories: diagrams as PlantUML code, C4 views for architecture, UML 2.5.1 for structure and behavior, BPMN 2.0.2 for business processes, data model diagrams generated from LinkML, text alternatives, color, SVG output, file names, and diagrams in English and French. Accessibility rules and values come from the FPSOT accessibility specification. Version 0.1 is a draft.
Read the normative text in spec/en/ or spec/fr/.
Start with index.adoc, then read the five parts.
Each requirement has an ID from DIA-001 to DIA-044.
Check each diagram of your repository against every MUST rule.
The shared diagrams workflow of fpsot-org/GitHub-Actions renders the sources and checks the committed SVG files.
Read the guide in docs/modules/en/pages/index.adoc or docs/modules/fr/pages/index.adoc.
It shows one small PlantUML example per notation, and how to embed a diagram with its text alternatives.
The comparison pages show how the practice of Canada and Québec relates to each requirement.
To require the spec from a supplier, ask that every delivered diagram conforms to it.
| Folder | Content |
|---|---|
|
Normative text, in English and French. |
|
Guides, in the Antora folder layout. |
|
The agent skill: a short summary that cites requirement IDs. |
|
Machine-checkable rules. None yet. |
|
PlantUML sources and their rendered SVG files: the example context diagram of the guide, in English and French. |
|
Comparison data: the international baseline, Canada and Québec. |