![[photo-1642775196125-38a9eb496568.jpg]] Photo by [Leif Christoph Gottwald](https://unsplash.com/@project2204?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) on [Unsplash](https://unsplash.com/photos/7_BXZJmQJGE?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) In this article, we will move a bit from the theory to one of the possible ways to implement MetaX as a semantically based Database. I have to put an emphasis on "one of the possible" keywords, this is certainly very simplified (not optimized or efficient) version and it doesn't try to realistically answer all questions related to functionality and integration with other components. Let's start with a conceptual picture of MetaX deployed inside RDS (relational) database, running on IaaS inside public cloud, accessible via HTML5 based we application interface and MetaX API (picture below). ![[Pasted image 20230708132034.png|Figure 1: Technology stack]] First question (probably) is how do we get ecosystem related data into the ER database and how we can expert it out. Fundamentally, simplified ER model is used to generate SQL scripts and deployment to RDS database with transition logic accommodating ecosystem abstracts as entities associated with their attributes (picture below. From this structure, we can easily execute visualization of ecosystem model (right side of the picture). ![[Pasted image 20230718211437.png|Figure 2: Transition of structures ]] Now let's take a look at the ER logical model of DB (apologize for a small tables with hard to read names). Legend at the bottom right corner helps us to recognize (color coding) major building blocks of ecosystem: - MetaSphere > MetaSystem > MetaSource = Ecosystem design - MetaPattern = Ecosystem patterns - MetaIndex = Taxonomy - CIEL = Integration with symbols and their categories - InfoSymbolism = Integration with symbol sets ![[Pasted image 20230708132059.png|Figure 3: ER Logical Model]] Full description of simplified version of MetaX tables is available below. It is not a full (exhaustive) list of structures needed inside the MetaX, but simplified enough to enable better understanding of minimal requirements of MetaX repository capable to semantically identify ecosystem components and enable interactive visualizations. ![[Pasted image 20230708132125.png|Figure 4: Description of Tables]] Additionally, there is another dimension (inside MetaX) we have to cover by ecosystem repository implementation. It is actual execution / running / operations / simulating designed or existing ecosystems. MetaSystem Architecture is stored in MetaSystem_* tables. These tables contains static Architecture of MetaSystem and are used as source for MetaSystem Deployment and Execution which is stored in E_MetaSystem_* tables. Prior to Execution, all data for Particular MetaSystem are copied to E_MetaSystem_* tables as Initial state for New Instance of MetaSystem. During Execution or Simulation of MetaSystem Live, data in E_MetaSystem_* tables are dynamically changed. ![[Pasted image 20230708132144.png|Figure 5: Architecture and execution structures]] Note: This technique is just one of the possible options to achieve separation of static and dynamic structures. Note: This technique is just on of the possible options to achieve that separation of static and dynamic structures. Example showing differences between static content of MetaSystem_* tables and dynamic (live) content of E_MetaSystem_* tables is depicted below. ![[Pasted image 20230708132208.png|Figure 6: Example of Architecture vs. Execution]] Real implementation of MetaX repository is vastly different (in sense of used technologies and integration methods), but coherent from perspective of MetaX structures used to store and reference ecosystem architecture and associated MetaData. ## Related to [[MetaX - The Definition]]