![[photo-1501740326664-5571ff5e30a6.jpg]] Photo by [Karim Ghantous](https://unsplash.com/@kdghantous?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) on [Unsplash](https://unsplash.com/photos/MeyssdI7XYQ?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) MetaNotation is the last missing piece of [[MetaX - The Definition|MetaX]] (dynamic, semantically based framework to design and architecture Ecosystems), closing the circle from MetaSystems and MetaData. The real purpose of #MetaNotation is to describe MetaData in structural form and allow technology agnostic translation of MetaData itself. MetaX's MetaNotation supports **Internal** (within CIEL repository) and **External** (distributable) MetaData description of MetaSystems in written form (Non Graphical), generated and stored in 3 different (and distinctive) structures: - Analytical - Native XML, JSON etc. - OWL / RDF ![[Pasted image 20230709113213.png|Figure 1: MetaNotation]] Internal MetaNotation is considered as [[What is CIEL and why do we need Ecosystem Language today|CIEL]] native notation and can be distributed only by replication of repository or by generation to External Notations. One of the major differentiators between MetaData in Internal and External Notations are MetaSystem ownership, versioning and support of external references. Each MetaNotation structure is dedicated to different purpose and is used in different stage of MetaSystem architecture design / distribution / integration (represented at diagram below). ![[Pasted image 20230709113230.png|Figure 2: MetaSystem architecture design stages]] ## Related to [[How is MetaNotation connected to Semantic WEB]]