aothms
commented
2 years ago There's a quite concrete and elaborate plan to leverage a BIMtester kind of set of natural language gherkin rules for software certification. These kind of constraints may be better suited there. That would make them automatically checkable.
It's also possible to think of some sort of middle ground, to lay out these kind of constraints visually. But these kind of diagrams have a much more informative nature to me. The exact meaning of the diagram in terms of what's allowed and what's not allowed is rather imprecise. We can extend the DOT-grammar based layout code with a convention of clusters https://graphviz.org/Gallery/directed/cluster.html and have them with a red background color or sth to indicate it defines a prohibited subgraph. I'm not against it.
So to me the question is, what to prioritize? Automatic checking or visual informative presentation. I don't see a clear middle ground, besides trying to come up with a mvdXML 3.0 (which has failed in the past).
Taking a random example such as this.
Was wondering if the restrictions mentioned in the text blurbs about the concept could be incorporated in the diagram instead. Example below. Would think this would make it easier to understand.