![[photo-1560961911-dd5c0bdd004a.jpg]] Photo by [Ryan Quintal](https://unsplash.com/@ryanquintal?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) on [Unsplash](https://unsplash.com/photos/OMCZDB5Okbk?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) In the "[Ecosystem Communication: InfoStructure](https://publish.obsidian.md/the-spheres-movement/Blog/Ecosystem+Communication+-+InfoStructure)" article we briefly described InfoStructure and its composition, stating that InfoElements are correlations of InfoParticles for semantic interpretations and InfoBlocks forms InfoElements in sequence to transport and distribute information. Let's examine this statements and explain why these InfoStructure components are crucial for Information distributions. First, each InfoElement is constructed from three InfoParticles containing InfoCodes as we discovered in "[Ecosystem Communication: InfoCode](https://publish.obsidian.md/the-spheres-movement/Blog/Ecosystem+Communication+-+InfoCode)" post (picture below). ![[Pasted image 20230709102409.png|Figure 1: InfoElement contains three InfoParticles]] The purpose of each InfoElement is to uniquely define ecosystem entity in reference-able form and connect it with any action to enable relation with another entity or subject. Example is a "Buy"+"Business"+"Service" - [Action]+[Classified as]+[Element]; a command / order for a transaction. This is a stand-alone element applicable multiple times, however it doesn't specify what we are buying and from who. Logically, we need more information - we have to connect more InfoElements to specify the rest of the order. ![[Pasted image 20230709102447.png|Figure 2: InfoBlock]] The InfoBlock is a collection of 3+ InfoElements to enable transportable information so we can finish our example above. Why 3+ InfoElements? Well, three InfoElements is the bare minimum to specify 2 ecosystem entities and their connection. Let's take a look at the #InfoBlock composition to understand the statement above. ![[Pasted image 20230709102518.png|Figure 3: InfiElements inside InfoBlock]] The InfoBlock itself is the elemental transportable block of information (with 3+ InfoElements); think about network packets - it's like a one packet. Packets (InfoBlocks) can be lost, repeated, received, combined - we will talk about their status in the next article "Ecosystem Communication: #InfoState or Information Processing". InfoBlocks are not sequential in nature, but they can belong to specific #InfoStream channels. Here is the full example (below) extending initial InfoElement we started with. ![[Pasted image 20230709102536.png|Figure 4: InfoBlock example]] By combination of 3 InfoElements (our example) we know that we have following order: **[what] -> "Buy"+"Business"+"Service"** **[from/who] -> "IT"+"Industry"+"Storage Provider"** **[what] -> "Technology"+"Storage"+"10PB"** Example above is not exhaustive, but shows the magnitude of options for business transactions with fully recognized information (semantically based). Now, imagine to automatically provision this storage based on the (let's say) AI generated need for machine learning purposes for a specific business ecosystem... We all know about CI/CD and Infrastructure as a code, but what about dynamic ecosystem generated requests, monitoring itself and behaving dynamically in dependency of consumer behaviors? Questions like this will always start appearing as soon as we connect multiple systems together and complexity reached the capacity of our management capabilities. You probably have more questions related to InfoTrance, so please take a look at the additional posts [[Ecosystem Communication - The Infotrance Theory|here]]. ## References [1] Wikipedia; Definitions ## Related to [[Ecosystem Communication - InfoStructure]]