![[photo-1526374965328-7f61d4dc18c5.jpg]] Photo by [Markus Spiske](https://unsplash.com/@markusspiske?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) on [Unsplash](https://unsplash.com/photos/a-motorcycle-parked-on-the-side-of-the-road-mHL3k93BhXQ?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 InfoCode is a data element of information, encoding the information into selected code. Let's examine this statement and explain how we can benefit from encoding information into InfoCode. Fundamentally, #InfoCode is used as a unique semantic ID at the time of design/definition of entity representing ecosystem element or abstract. You can find semantic ID in #MetaNotation used by [MetaX](https://publish.obsidian.md/the-spheres-movement/Blog/MetaX+-+The+Definition) identifying ecosystem MetaStructures with associated MetaData attributes. Semantic ID might be programmatically generated or simply assigned in dependency of mapping keys within associated ontology. The important part is the ability to distribute and associate semantically identified data with full recognition supported by external ontologies. These ontologies are represented at pictures below as a "**Semantic Catalog**", a core functionality needed for translation of each #InfoParticle. Semantic Catalogs are referenced at Wikipedia as Semantic Networks. [1] --- Probably you are asking the questions "How is InfoCode structured" or "What can I do with InfoCode". All good questions, so we will shift focus and answer first question in the next couple of lines; then we can focus on InfoCode usage in the next articles. --- Generally, InfoCode is (as you probably already suspect) a code utilized to compress an association (link) to semantics (meaning). InfoCode could be as long as we want (assuming you have unlimited storage and processing power), but for practical reasons let's assume we have just 4 Bytes which gives us 36 on 4 selections (all English characters + numbers). So that's our range for associations - you can imagine you have a vertical slider for each position (just like on some luggage locks) and you can select (slide) each separately to create code combination. Take a look at the picture below. ![[Pasted image 20230709102737.png|Figure 1: InfoCode vertical sliders and current selection]] What does selected code **8H1Q** represents? It represents a specific **semantic association** in selected ontology (semantic catalog). Three of these InfoCodes combined together are exposing an Information stored inside structured #InfoElement. Diagram below shows our example extended with 2 more InfoCodes and their interpretation (by the semantic catalog) as information (after decoding). ![[Pasted image 20230709102805.png|Figure 2: InfoCodes connected together]] Why three InfoCodes? They represent the minimal information needed to create InfoElement. We call those three "**InfoParticles**". Sequence of three InfoParticles can fully identify InfoElement with following structure (below) with associated example and syntax explanation. ![[Pasted image 20230709102824.png|Figure 3: InfoParticle]] 1. Identified Semantic Catalog (distributed) 2. Element (ecosystem entity) 3. Action / Value (attribute) Summary picture with InfoCode selector is below. ![[Pasted image 20230709102847.png|Figure 4: InfoCode summary]] You probably have more questions related to #InfoTrance, so please take a look at the additional posts [here](https://publish.obsidian.md/the-spheres-movement/Blog/Ecosystem+Communication+-+The+Infotrance+Theory). ## References [1] Wikipedia; Definitions ## Related to [[MetaX Semantic Model]] [[How is MetaNotation connected to Semantic WEB]] [[MetaNotation to help you design and build Ecosystems]]