This particular use case is focused on #MetaNotation (language) for 3D Printers and other machines, used as a “Construction Knowledge Code”. Yes, this use case is not necessarily focused on building ecosystem. However, we will demonstrate simplification of complexity by employing #InfoSymbolism and #CIEL for machines replicating objects becoming part of the ecosystems. This might be applicable for stranded (frontier) communities, outposts, colonization flotilla to Mars (yes we said it) or simply as a process to increase customer experience for on demand goods - we do not need huge warehouses with complex logistics anymore. ## Situation We need a bucket – physical object, vertical cylinder or truncated cone, with an open top and a flat bottom, usually attached to a semicircular carrying handle called the bail. ![[Pasted image 20230708130405.png|Figure 1: Design]] So our definition is **based on functionality**, not a structure necessary. ## Process Flow MetaX phases (activities) and their models are helping us to drive process we introduced at previous article "[[MetaX Models - From vision to execution]]". ![[Pasted image 20230708130141.png|Figure 2: Metax phases]] Okay, we have our Framework and methodology selected , let's focus on each step: 1. **Visualization**: Selection of “bucket” symbol from library of “known” or existing objects. Symbols are referencing Entity structures (#MetaSystem structure) 2. **Identification**: Semantic identification of Entities. This action will link MetaSystem structure (bucket in this case) with semantic id , which is interconnected with generic description of MetaSystem structure in physical world. This action can reference STL [1] file (StereoLithography) used as surface geometry definition for 3D objects. 3. **Translation**: During this phase, low level construction knowledge code is generated for particular 3D printer. 4. **Construction**: 3D Printer execute printing of selected symbol (bucket) and as a result we receive required object without any prior knowledge of construction ![[Pasted image 20230718212015.png|Figure 3: From visualized selection to construction code]] Picture above shows default selection of "Bucket" symbol from taxonomy of known objects (semanticID 32056), user can select (based on the preferences) design and advanced functionality by selection of alternate symbol (InfoSymbolism); selected version will influence generated construction knowledge code (CKC). In this use case CKC (construction code) is a simple STL file as an input for 3D printer. > Stereolithography (SLA or SL; also known as stereolithography apparatus, optical fabrication, photo-solidification, or resin printing) is a form of 3D printing technology used for creating models, prototypes, patterns, and production parts in a layer by layer fashion using photochemical processes by which light causes chemical monomers and oligomers to cross-link together to form polymers.[1] Those polymers then make up the body of a three-dimensional solid. Research in the area had been conducted during the 1970s, but the term was coined by Chuck Hull in 1984 when he applied for a patent on the process, which was granted in 1987 ![[Pasted image 20230708130440.png|Figure 4: How is it connected together]] Process stack is visualized above with solution , selected method and integration components connected together. As an example of STL code for your bucket, y0u might visit portals dedicated for 3D printing such as [cults3d](https://cults3d.com/en/3d-model/gadget/heineken-ice-bucket) . ## Observations There are couple of observations for this generic use case, here is our explanation: - Semantic ID references DEFAULT Construction definition (CKC), however alternate CKCs could be selected in dependency of MetaSystem attributes. Good examples could be different color, shape or size. This is clearly advantage of dynamic MetaSystem definition and alternative symbols from InfoSymbolism (Symbols set for various bucket types, shapes, colors and many more possible attributes). - Symbol sets (InfoSymbolism) are not only providing variations but also enabling business **differentiators for market and vendors** associated with symbols as Construction Knowledge Code owners. So, there are various Knowledge code owners (designers of STL files), which are proposing variations for free or for sale. - Example of Object Alternatives (InfoSymbolism) – You can find 100s of objects from different artist on ETSY website, these are different object versions in InfoSymbolism. Imagine ETSY will start **selling construction codes** signed by artists (NFTs) - Default Object version (CIEL) has VersionID=0 and this is aligned with Default object construction file (CKC). Object version is unique, assigned by and managed in repository. There are unlimited options to customize bucket - therefore we can have construction code based on different versions #### Non-fungible token (NFT) A non-fungible token (NFT) is a non-interchangeable unit of data stored on a blockchain, a form of digital ledger.[1] Types of NFT data units may be associated with digital files such as photos, videos, and audio. Because each token is uniquely identifiable, NFTs differ from blockchain cryptocurrencies, such as Bitcoin. NFT ledgers claim to provide a public certificate of authenticity or proof of ownership, but the legal rights conveyed by an NFT can be uncertain. NFTs do not restrict the sharing or copying of the underlying digital files and do not prevent the creation of NFTs with identical associated files. Example of artistic representation visible at NFT store is below: [  #### The Blue Bucket [Original]  Created by Altered_Data • The Blue Bucket This is the original blue bucket used to support the weight of my car while the thieves carried of their work unnoticed and stole two of its wheels. This simple use case is combining couple of concepts together: Symbols of objects with variations by functionality #InfoSymbolism serving as a catalog for generation of construction code (compare to infrastructure as a code) , consumed by construction machine (i.e. 3D Printer, CAD machine) to produced desired object. Now, imagine this example (we just described) as just one of the components of your **private ecosystem** - connected as IoT (Internet of Things) device. You are inside your home (unit) , you push the bucket symbol on touchscreen , select the bucket type and expect to use printed bucket within the minute for whatever you though you would need it. Sounds intuitive , but to extend this concept to everything around us - it really highlights the need for ecosystem approach (objects and actors connected together) and vastly different perspective on semantically based solutioning. ## References [1] Wikipedia; Definitions ## Related to [[MetaX Models - From vision to execution]]