I included in PR#20 the figure from the D&TA standard/contribution. A comment has been made in GitHub on the PR (https://github.com/oasis-tcs/dps/pull/20#discussion_r2112648743) that I will repeat here as everyone is not as familiar with GitHub, and I need help from others in resolving.
The comment is:
"Can we include a maintainable source version instead, like mermaid fenced code block or an additional source file for the SVG?"
I would ask the D&TA originators how the SVG was created. Some tools use simpler source code to create the SVG. If so, could we have it? Other tools let you play on the screen and create the detailed SVG output like in this file. The SVG file is in a separate file, and it is SVG, ie ASCII text, that can be interpreted and editied by many tools (I usually use Inkscape). So I would argue it definitely is maintainable as text under source control. But as the comment implies, it would be nicer to a simpler source like plantuml has text like https://github.com/sparrell/openc2-tc-ops/blob/master/sources/pub-cs.plant.txt to create images like https://github.com/sparrell/openc2-tc-ops/blob/master/images/WorkProduct-Github-Process.png. Or draw.io is another image specification language that is more human readable.
Personally I don't think we should hold up the spec based on this (ie "raw" SVG is good enough until someone provides something better). But comments welcome.
------------------------------
Duncan Sparrell
Chief Cyber Curmudgeion
sFractal Consulting LLC
Oakton VA
703-828-8646
------------------------------