P1 In this section, we will delve deeper into Layers as Web Apps, the driving force behind the rebirth of hyper layering architecture two point zero. We will explore its underlying philosophy and uncover the new computing paradigm at its core.

P2 This slide illustrates the relationship between the standard svgmapjs framework interface and Layers as Web Apps.

P2-1 The map area is the shared canvas where layers are composited. On the left, you see hyperlinks to groups of layers.

P2-2 When a user selects a layer from this list, the corresponding web app, the Layers as Web App, is launched in the box on the right.

P2-3 This layers as web apps receives service specific data, converts it into the document object model format for the framework, and displays it. Even with Geo industry standards like WMS or WFS, unique UI and application logic are indispensable for services like weather forecasts, for example, setting the forecast time. layers as web apps supports this crucial application logic.

P3 Next, let's compare hyper layering architecture two point zero and layers as web apps with well known modern web service design patterns.

P4 Let's quickly review the behavior of Layers as Web Apps. The client framework loads and plugs in small web apps. These apps run unique logic to fetch layer data from their server and display it on the client. Other layers behave similarly and independently.

P5 This behavior closely resembles the Microservices Architecture. In hyper layering architecture's context, the servers that deliver layer data precisely correspond to these Microservices.

P6 Furthermore, we see similarity to the Micro Frontend design pattern. layers as web apps is the direct equivalent of the Micro Frontend pattern for geospatial data.

P7 Next, let's look at the decisive differences. Do you notice two key differences? First, the summary site contains hyperlinks to the microservices. Second, layers as web apps renders its content onto a shared map canvas integrated by geospatial coordinates. This difference leads to a decisive divergence in philosophy, which we will now explain.

P8 First, let's look at the well known challenges in Micro Frontends. When building a service, individual frontends often impact others, resulting in tight couplings, or N multiplied by N minus 1 divided by 2. Consequently, the pattern is limited to a small number of elements, within a single, specific system.

P9 Now, let's look at Layers as Web Apps. This diagram shows the composition of layers as web apps.

P10 The number of couplings has dramatically decreased, resulting in a Hub and Spoke structure. All elements couple only with the map or shared context. If you add one new element, only a single coupling is added, and the impact on others is minimal.

P11 This simple coupling—just one context and one link per element—enables hyperlink based coordination from the summary page. This is precisely the consistency with the original WWW principles.

P12 As a result, this architecture elevates the system to a level of interoperability between heterogeneous systems, where elements have no direct coupling, through loose coupling.

P13 Let's summarize. Layers as Web Apps goes beyond traditional Microservices and Micro Frontends. We believe layers as web apps represents a philosophical innovation by recapturing the Web's fundamental interoperability on the front end side through loose coupling.

P14 Now, let's advance our exploration. layers as web apps represents hyper layering architecture two point zero as a new paradigm for distributed and edge computing.

P15 You may recall the end of the demo: we displayed clinic locations and seismic intensity, then performed an operation between these layers, an intersection, to list affected clinics. The crucial point is that the "operation performed between the layers" itself was also constructed as a Layers as Web App.

P16 Now, let's look at this geospatial processing function. It is equipped with a user interface for the user to select the two layers and a function to fetch the selected layers from the shared canvas. The key takeaway is that layers as web apps is not introducing data, but the "processing or computing itself" is being introduced ad hoc onto the platform based on the end user's instruction.

P17 This is the final slide. In traditional systems, data integration is possible, but advanced computing is limited: either monolithic front end processing, or centralized server dependence. layers as web apps overturns this by achieving interoperability of the computing itself through user centric, ad hoc computing. This marks a step toward a new computing paradigm: Hyper Computing, which is user initiated computing driven by hyperlinks. This concludes my presentation.