http://yuml.me and yuml-diagram used to generate examples of various
high-level diagrams and design patterns. One example is a REST-sequence
diagram.
- Clone repo
$ npm isntall
$ npm run gen ./examples/{INPUT}.yuml ./{OUTPUT}.svg
My main goal with this repo is to enable a yaml2yuml2yed2kingly (like, uh, presentation to docker with yuml embedded to yed to kingly to code) workflow such that textual forms can be crafted in YUML syntax and then used to generate yEd state diagrams to ported to Kingly, ultimately determining normative code matter in a Yeoman-ish like way (but, like, from text files, as a presumed normative format for generating code not weird ass templates).
The progression of the application based on the link relation's relating relation presupposes that a mereological complex may be layered although the categorical heterogeneity of the names in which layering in expressed need be ontologically homogeneous.
What we know today is that it took nearly 4 decades for a public syntax for UML to be published. Why did we allow proprietary licensing and so on to hinder our progress, lending to centralization for the benefit of militarizing companies? Much was out of our hands, if not the world itself.
Here we will also wish to include a unified music language such that sound structures may be used to elaborate the interactions and exchanges between an abstraction thought to indicate underlying substrate dependencies (often computers, of some variety, performing work).