About this Document
This is a written supplement to the major dapp toolchain component of P2P Modular Organizing Diagram. This document will provide some explanatory description, definitions, and (eventually) a verbal overview of that model.
Objective: To provide a visual model and a mapping system which can effectively describe formal relationships within any intentional ecosystem which supports and sustains a specific dapp.
Specialized Definitions and Descriptions for this model and mapping system:
-
function: Within the context of the DAE model, a function means a digital data transmitting and/or processing function. Such functions can be complexly constructed through hierarchically layered and/or networked relationships.
- Each function may have its own formal ID, Description and Traits.
- Each function may have its own levels of organization.
-
ecosystem: a system of distributed apps and of p2p agents which supports one or more specific social [goals].
-
agent: an agent is p2p participant which plays a functional role within a specific
-
level: this represents a level of organization which contains a set of functions which create a specific parallel process. (That parallel process is the layer's function within the ecosystem.)
-
traits: this represents a set of relational elements which identify the formal "behaviors"-- i.e., a types of interactivity -- which the described element possesses within an organizational context.
- Note: Effectively defined traits often create semantic links which connect a formal element to another formal element. If a trait does not link to another formal element, then the viewer may assume that that element is supposed to possess that behavior "globally" (i.e., in all valid interactions) within its level of organization. However, traits which do create semantic links may describe relationships which connect different levels of organization. (For example, an output from one function may be specified as an input for another level of organization, or even for a different ecosystem.)
-
link: visual links indicate formal relationships between different functions. These are fundamentally important to the DAE model.
- A link may (and should) have its own ID, description and traits-- just as each level and each function may have.
- A link should be formally constrained by identifying each of its types of input and output as a Trait. Furthermore, inputs and outputs may be complexly bundled by mutually required relationship/responsibility to each other.
- It will be very important to clearly display directionality of links, so that the flow from input to output is visible from a high level overview.
- Links should clearly indicate the nature of linkage such as app-to-app, app-to human agent, human agent-to- human agent etc.
- Links can (and ultimately should) be automatically generated by assigning traits properly to each element.