In this continued effort to get a presence on the web where a discussion could be held on the issues of instantiating code from a UML protocol-state-machine ...we have arrived at this place. These ramblings are/aren't put here to establish an aspect of UML's present limitations (as they have been illustrated to me) in generating code, and to see a place in the community where the average man tries to discuss the intergrations of LISP(CLIM), UML(protocol-state-machine), and an SDN(controller-GUI) .... these are the objects I am using to start a construct ... the job is to generate code from these concepts ....
UML has not been presented here with the aspect of its limitations as that concept has been presented in various other places on the interweb. The things I have seen out there talking about the way a state-protocol-(machine) can be described in the UML way, mention the " The UML allows to define so-called Protocol State Machines (PSM) to define the correct usage of the operations defined by a classifier" ,which of course arises from the OOPs metaphor going around now-a-days of classes containing operations, which of course some Lisps dismiss on the grounds of operations not needing to be contained in classes. Does this mean that my Lisp based transistor-laser LED spreadsheet lookup cells ordering, not need everyone of their locational-lookup lambda functional operations described and contained into discrete object-oriented class based cell structures. This classless society using the Lisp displaced-array structure is among one of the reasons Lisp is considered optimal.
... Put the whole ... lookup structure into the Lisp-array along with its ... use-cases ...
testing ... ... ... 123 ... ... ...
hmmm ... lisp array ... There may be other ways of expressing the idea of 3D data-structures in the world today, but lisp's mention of a 3D structure as the first and simplest view that I saw, and as a means of displaying and constructing ///-defstruct-ing-possibly/// such a 3D model, gave me the contention that I may be able to build this construct with what I had on hand and what lisp already comes with. In my mind's view of the 3D structure access was enabled by just looking at the structure with my minds eye and pointing out any wanted or given location at any time or place it was needed.
Do not feel obliged in any to give these words in any way the stature of law. The ONF(Open Networking Foundation) itself does not have in place a NBI standard. Just allow me to add to the flora being spread about in this current space called NBI. Some day, some way, some how, it may come to pass that what I've envisioned may be dismissed as it is conceived right now, but if I can get the code-ings and all of the concepts I've prepared, into a presentation that this site can render, it may give some future CADT a glimpse of what it means.
So much This[_everyone of their locational-lookup lambda functional operations described and contained into discrete object-oriented class based cell structures_], grepping a mind-map as in an AI expecting the word scape to express some concrete idea.
Tenting things with expectations of comprehension while writings appear as -discrete object-oriented class based cell structures-, there always the wished for simplified extents on conses consing up some splined up lines in scope spaces.