Closed lastmeta closed 3 years ago
we want to be able to model the namespace of the network in terms of nested structures, like nested business processes. nested namespacing seems like the most intuitive way to structure a dag, but its not the only way and we may want to cut the structure in any number of ways because the structure may not even be a dag. it may be a dag when looking at it from a particular angle, ignoring some parts of it, but it may not be a dag, taken as a whole. so we need a general solution and part of me wonders if the hypergraph concept would be helpful here... still researching...
minimal viable solution created: nested directory structure to mirror dag hierarchy. not enforced. closing for now.
right now you every function name in the network must be unique. we need to implement a namespacing solution so nodes can be organized into regions or groups of any kind.