©: Luftschiffbau Zeppelin→Zeppelin Luftschifftechnik and Style of Speed

The first model of the second generation is shorter, narrower, and most potentially lower, which makes it comparable and competitive in practice with helicopters and other VTOL aircrafts and has the following specification:

In addition, a smaller model with a capacity of 2 passengers and some other models are also designed already.

05.March.2019

03:47, 18:05, and 34:43 UTC+1
More evidences e.Go Mobile mimicking C.S. and C.S. GmbH

*** Work in progress - better epilog ***

Sooner or later we catch every entity, even the teachers in the field of automotive engineering at the university of Aachen, B.R.D..
From an interview of a leading automotive media company specialized on the publication of fabricated news and fake news we got the following informations: "[Reporter:] What are the special features in the production?
[Interview] The most [manufacturers] focus on the automation of the assembly process. This looks nice and robotized, but virtually does never pay off - in no case in quantities under 100,000 vehicles each year. [...] Our plant is in the assembly quasi completely manual - not only in the pre-series production. But the information and data flow is automated to 95 percent - from the early specification. I can make out of this car a convertible and also different wheelbase versions in less than twelve months - as development of pure derivates. The special is that we have an own data base as extract over all these systems - the digital shadow. This is our core element of the Industry 4.0 infrastructure.

[Reporter:] How do you manage to stay cost-effective?
Today, you normally cannot simply access the configurator. Customer configuration and product configuration do not run in one system. Accordingly, an order is effected by means of a complete system change. Alone the incorrect orders through transcription errors are a real loss of value. With us you can configure the car on the [mobile phone] and make a proper purchase order. This goes direclty into the production. In a classic assembly plant much time is lost with each change request by searching and waiting - I would like to raise this loss of time. Thus, at our [company] the information flow is automated, not the assembly process."

First of all, the digital shadow has to be viewed as the digital twin of the related business and production processes, that both belong to our core elements of the fields of

• Industrial Internet of Things (IIoT) and
• Industry 4.0,

that again are all based on our Caliber/Calibre and therefore are elements of our Ontologic System (OS).

For sure, others had presented before the concepts of a

• an adjustable chassis or platform, or
• exchangeable and customizable exterior elements

even in relation to the Lego construction kit, and

but we have not seen the same with

• chassis and the exterior elements,
• interior elements, or
• both,

which are our revolutionary creations that make the significant and decisive difference or simply said our true revolution.

Eventually, we have here our a

• modular hardware and software platform called Integrated Wheeled Intelligence (IWI),
• modular application and service platform with ecosystem, including a Mobility as a Service (MaaS) respectively Transport as a Service (TaaS) platform, and
• overall ecosystem,

The company e.Go Mobile is utilizing components of the company Robert Bosch and also has collaborated with the manufacturer Porsche→Volkswagen for utilizing its so-called Modular Electrification Construction Kit (MECK)==Modularer Elektrifizierungsbaukasten (MEB).
This has to be handled with some attention, because if

then we have a value-added process that is classified as Ontologic Applications and Ontologic Services (OAOS), and a share of the overall revenue generated in this way is due in accordance with the License Model (LM) of our Society for Ontological Performance and Reproduction (SOPR). We gave the rational for this handling in the issues SOPR #121 of the 29th of May 2018 (section Update of the License Model (LM)) and SOPR #123 of the 29th of June 2018 (section Issue #3).

03:47, 18:05, and 29:28 UTC+1
More evidences Volkswagen mimicking C.S. and C.S. GmbH

*** Work in progress - better explanation ***

Around 6 hours ago, the manufacturer Porsche→ Volkswagen has opened its so-called Modular Electrification Construction Kit (MECK)==Modularer Elektrifizierungsbaukasten (MEB) to other companies, which is based on our

• modular hardware and software platform called Integrated Wheeled Intelligence (IWI),
• modular application and service platform with ecosystem, including a Mobility as a Service (MaaS) respectively Transport as a Service (TaaS) platform, and
• overall ecosystem,

and partially resembles the cases of the joint ventures led by a Swiss company and the manufacturer Toyota, and also the case of the company Schaeffler with their plagiarisms called Snap, e-Palette, and Schaeffler Mover.

A related report of a public-law broadcaster many times convicted by our investigations for the publication of fabricated news and fake news gave us the following informations: "Is that how revolution looks like? For decades, Volkswagen was sitting on one's high horse. The own technique was the measure of all things, that one did not give away. Under company patriarch Ferdinand Piech would be unthinkable, what Group's Chief Executive Officer Herbert Diess has declared in Geneva: Competitors are allowed to utilize the before holy VW-technique.
Volkswagen wants to provide quasi an electro-automotive operating system.

In another report of a daily paper we got the following statement of H. Diess in addition: "The MECK should be established as standard of the e-mobility."

Obviously, Volkswagen is not providing its holy technique but our original and unique works of arts titled Ontologic System and Ontoscope, and other related and integrated works, specifically the ones listed above, which

Because we have started one more revolution and set one more worldwide standard in the fields of transportation and mobility as well as other fields with these original and unique, iconic works of us, proper licensing of any reproduction and performance of them in accordance with the License Model (LM) of our Society for Ontological Performance and Reproduction (SOPR) is required for various reasons.
In general, we have six (reduced from eight) categories of activities or roles and also (meta-)levels (see the issues SOPR #121 of the 29th of May 2018 (section Update of the License Model (LM)) and SOPR #123 of the 29th of June 2018 (section Issue #3), and also SOPR #157 of the 23rd of December 2018 and SOPR #159 of the 31st of December 2018):

Accordingly, the share of the overall revenue generated with the MECK is as follows:

We changed the License Model (LM) exactly for companies in the fields of for example cloud computing and automotive engineering for

That said, this specific regulation is not about making more money.

Volkswagen

and e.Go Mobile

so we imply that also the MECK for e.Go is part of the Industry 4.0, but we can already assume from our knowledge about the marque Volkswagen→Audi that the MECK is part of the Industry 4.0.

06.March.2019

02:49, 10:43, and 22:19 UTC+1
More evidences Fiat Chrysler Automobiles mimicking C.S. and C.S. GmbH

*** Work in progress - epilog ***

The company Fiat Chrysler Automobiles thought that it has to present once again a solution based on our original and unique, iconic works created by C.S.. From a report of a leading automotive media company specialized on the publication of fabricated news and fake news we got the following informations: "Electro-study debuts in Geneva [] Fiat Concept [car]
With its modular coachwork inside, outside and with the batteries the [concept car] pursues a completely new concept. Fiat's calculus: Additional money could be made with uncountable possibilities in the matter of individualization.
[...] This is about a small electric car, whose - by far not the only - clou is the modular range.
[...]
[...] The one who wishes for a larger cruising radius can buy or rent up to three additional batteries [...]. They are installed under the vehicle floor, that should work particularly quick and easy thanks to a sliding rail. Another battery is added, which can simply be pushed under the seat and taken out again [...]. [...]

One color shade, but many colorful attachment parts
The theme modularity runs through the Concept [car] in several places. Example bodywork: It is only produced in one color shade, in the case of the Geneva-study it is a matt grey. But the bodywork can be customized with four roofs, bumpers, wheel covers and adhesive foils each. If one has other color shades in mind after a certain time span, the parts can be exchange at any time.
Example roofs: Basically, the [concept car] is opened upwards, but a two-tone polycarbonate top, a soft top, an integrated cargo box or a true roof along with solar module, which is able to generate up to 50 watt of electric energy, can close this opening. The boot lid features a display, on which messages can be communicated with the outside world. While driving the Fiat-Logo is visible here. But while standing the display can change into the "messenger" mode and send advertising messages out for example.

A dashboard like Lego toy
Inside it continues in this style. The dashboard has many small holes, in which different components of any form and function can be built-in - Lego says hello. The door panels can be customized as well and have mounting points, at which storage compartments, bottle holders und loudspeakers can be attached. At the four seats cushions, headrests, color shades and materials can be exchanged. But here can be converted as well: The front passenger seat gives way to a child seat or a storage box if needed. The rear bench seat is retractable and the rear backrests can be turned in such a way that the trunk is enlarged.
Fiat configures the dashboard in two variants. The first one combines a ten inch main display with the smartphone of the driver; this deals then with navigation, entertainment or information. There is a second integrated display as alternative, which enlarges the main monitor to 20 inch. It provides information about driving assistance and safety functions like direction indicators, blind spot assist, brake system and also battery status.

Aftermarket as additional business model
Fiat does not only see in the Concept [car] a car for the individual utilization. It should also be simply integrable in corporate and carsharing fleets. Furthermore, the manufacturer envisions sees in the concept a new business model, which is less the car itself, but is more about the trappings. The whole should be operated through the company-owned accessories division Mopar, which distributes accessoires like sound system, dashboard and door stacking units or seat cushions online; then the customer builds in the parts herself/himself. What is more, some accessoires like for example cup or document holders can be printed on a 3D printer at home, in the dealership or in a special printing plant.
It is not yet entirely clear if and when the Concept [car] will be built in series. But many formulations in the official press release indicate that it might come about. As soon as it is ready, the [concept car] should be "the cheapest BEV on the market". And in addition the easiest one to clean, to repair, and to maintain."

As we summarized in a related case, others had presented before the concepts of a

• an adjustable chassis or platform, or
• exchangeable and customizable exterior elements

even in relation to the Lego construction kit, and

but we have not seen the same with

• chassis and the exterior elements,
• interior elements, or
• both,

which are our revolutionary creations that make the significant and decisive difference or simply said our true revolution.

In this way, Fiat Chrysler Automobiles is the next entity that proved the originality and uniqueness, iconicity of our transportation and mobility revolution based on our Ontologic System and System Automobile. See the notes of the 5th of March 2019 for more details and royalties.

08.March.2019

07:57 and 20:50 UTC+1
Website update

*** Work in progress - some informations missing, update not done ***
Plagiarisms and other issues were confirmed by us another time.

The NetKernel is a plagiarism, as proven once again by a comparison of the histories of the manipulated webpages of an online encyclopedia with our publications and results of investigation. We also got the three fraudsters, who have substantially manipulated the webpage about the NetKernel, and even the real name of one of them, who has also created the webpage about the Resource-Oriented Computing (ROC) paradigm and connected both.
Accordingly, the Investigations::Multimedia of the 28th of October 2018 was slightly updated.

Named Function Networking (NFN) is a plagiarism. For example, in relation to the plagiarism NetKernel we found the following funny fact: "The active URI scheme was proposed by Hewlett-Packard as a means to encode a functional program within a URI. [...] Because the argument values may be URI addresses themselves, a tree-structured set of function calls can be encoded in a single URI."
Now, we do know why it was so familiar all the time.
The complete investigation was already announced and will be publicated after the publication of the Investigations::Multimedia, AI and KM Semantic Sensor Web (SSW) special and related matter.

Istio is a plagiarism, because of its integration of the fields of

• based on our integration of for example the Chemical Abstract Machine (CHAM) and
• utilized for transforming monolithic systems like Linux into Ontologic Systems for example,

From a related webpage of an online encyclopedia about the Linux Foundation we got the following informations: "Linkerd is a [Cloud Native Computing Foundation (]CNCF[)] member project, providing resilient service mesh for cloud native applications. The tool is based on the JVM (Java Virtual Machine) "for developers to help improve communications among microservices."[47 [Buoyant's Linkerd Offers RPC-based Microservices Communications - The New Stack. [...] 2016-05-06]]"
"Originally built at Lyft to move their architecture away from a monolith, Envoy is a high-performance open source edge and service proxy that makes the network transparent to applications. Lyft contributed Envoy to Cloud Native Computing Foundation in September 2017."

From a report about service meshing we also got the following related informations: "Perhaps the oldest effort in this field - one which, through its development, revealed the need for a service mesh in the first place - is an open source project called Linkerd (pronounced "linker - dee"), now maintained by the Cloud-Native Computing Foundation [of the Linux Foundation]. Born as an offshoot of a Twitter project, Linkerd popularized the notion of devising a proxy for each service capable of communicating with similar proxies, over a purpose-built network. [...]
Meanwhile at car-sharing service Lyft, an engineer [...] devised a method for building a network that represented existing code - even when it was bound to a legacy "monolith" - as microservices with APIs. This became Envoy, which is now one of the components of a project that includes the work of IBM and Google, to produce a framework called Istio." And Envoy also provides an evidence that shows a causal link with our OS. Compare with the statement "We at OntoLinux, transform operating systems based on Linux into Ontologic Systems." made on the webpage Profile of OL and the related list point above as well as the notes related to microservices below.
Also note that the

Singularity OS is becoming a plagiarism. Containers with Message Passing Interface (MPI) inside and outside is what? Exactly, nonsense, which shows once again that the whole containerization thingy is at the dead end. Hint: There exists something that is called operating system.

Kubernetes looks like a plagiarism.
From an online encyclopedia we got the following description: "Kubernetes is loosely coupled and extensible to meet different workloads. This extensibility is provided in large part by the Kubernetes API, which is used by internal components as well as extensions and containers that run on Kubernetes.[...]. The platform exerts its control over compute and storage resources by defining resources as Objects, which can then be managed as such. The key objects are:
Pods [...] Services [...] Volumes [...] Namespaces
[...]
Kubernetes is commonly used as a way to host a microservice based implementation, because it and its associated ecosystem of tools provide all the capabilities needed to address key concerns of any microservice architecture."

Comment
So the overall issue also hangs on the microservices issue or said in other words if microservices or the field of microService-Oriented Architecture (mSOA) is a fraud, then Kubernetes is a fraud.

Microservices might be a plagiarism. Somehow, there seem to be two versions and much more fraud and confusion:

Somehow, both groups and their different members describe microservices from different point of views but after our publication like elements of our Ontologic System, such as for example the active object model, actor model, Service-Oriented technologies (SOx), virtualization, and their integration (see also Istio once again. That cannot be correct or legal that a whole industry sector is mimicking us.

Edge computing as well as Network Functions Virtualization (NFV), Deep Packet Inspection (DPI), Software-Defined Networking (SDN), etc. (utilized by telecommunications service providers and other providers) have issues with the basic properties of our OS including Distributed Virtual Environments (DVEs), Master-Worker (MW), Client-Server (CS), Peer-to-Peer (P2P), grid, cloud, and mobile computing, Dedicated Communications (DediCom) system (not to confuse with the Dedicated Short-Range Communications (DSRC) system), Vehicle-to-everything (V2X), etc., and therefore with our Society for Ontological Performance and Reproduction (SOPR), specifically in relation to its infrastructure and its credo "All or nothing at all".
In fact, we explained our convergence and integration of stationary and mobile networking already in the past and once again recently in relation to our Dedicom and V2X (see the {?}Clarification of the 7th of January 2013 and 11th of January 2018, and the More evidences Volkswagen and Siemens mimicking C.S. and C.S. GmbH of the 5th of January 2019 and More evidences Qualcomm and Ford mimicking C.S. and C.S. GmbH of the 7th of January 2019) and the field of Distributed Virtual Environment (DVE) or Networked Virtual Environment (NVE), including the field of Massively Multiuser Virtual Environment (MMVE), including the field of Massively Multiplayer Online Games (MMOG) (see the OntoScope component and the Investigations::Multimedia of the 18th of July 2008, the OntoLinux Further steps of the 14th of November 2012, and the related Ontologic Net Further steps of the 18th, 20th, and 23rd of February 2019).

In fact, only some areas of networking, SOx, and Semantic (World Wide) Web (SWWW) are left uncovered by our OS, but not the rest of the whole.

Style of Speed Further steps
Despite we are not very interested in automobiles anymore, we planned initially to take a chassis of a first manufacturer and a system of a second manufacturer for a specific car model. But the so-called Modular Electrification Construction Kit (MECK)==Modularer Elektrifizierungsbaukasten (MEB) of the manufacturer Porsche→Volkswagen is worth of thorough considerations, though we may ask for

09.March.2019

21:40 and 23:47 UTC+1
Website update

*** Work in progress - update not done ***
Eventually, we could solve the mystery of the microservices. Indeed, there exist two versions, as we already noted yesterday:

Features added and integrated with our OS include the

• computing (operating system, virtualization (hypervisor, Virtual Machine (VM), containerization, etc.), data base, etc.),
• networking (Peer-to-Peer (P2P), grid, cloud, and edge computing, mobile computing, etc.), and
• distributed computing (distributed operating system, etc.),

The projects

• operating system-level virtualization or containerization, active object model, and actor model, or related properties of a Distributed Operating System (DOS) or a Multi-Agent System (MAS), specifically the
  • reflective, fault-tolerant, reliable, and distributed operating system Apertos (Muse) and the Cognac system based on Apertos, and
  • Java Agent Development Environment (JADE) intrinsically based on Peer-to-Peer (P2P) computing and loosely-coupled active entities and featuring container run-time,

  and

• cloud computing and hybrids thereof,

and

• more features of Apertos (Muse),
• middleware,
• features of space-based architectures (e.g. tuple space)

for service meshing, which shows that both are based on mise 2.0 and eventually on our OS.

This also explains the

Eventually, we note that there

In this relation, we would like to recall once again one of the credos of our Society for Ontological Performance and Reproduction (SOPR): "All or nothing at all". This means that the old strategy of avoiding a causal link is not accepted anymore even in those cases where it seems to be working legally.

We will move new matter to the Clarification of the 1st of December 2018, as announced.

10.March.2019

00:07, 07:30, and 38:09 UTC+1
Clarification

*** Work in progress - formulation, better explanation ***
We would like to discuss in (some) more detail the new situation for telecommunications service providers and broadcasters, that we created with our Ontologic System (OS) as well.

Our Ontologic System comprises not only virtual or digital software but also real or physical hardware as it is well known by the Ontoscope and intelligent Tablet (iTablet devices, Sp@ce and Synthetic Reality (SR or SynR) environments, Retina Projection/Fovea Projection, Kineticle, and Wireless Supercomputing (WiSer) technologies, System Automobile comprising our Integrated Wheeled Intelligence (IWI), autonomous vehicles, and so much more.
In addition, it is basically tier-less (see also the Further steps of the 23rd of February 2019).

One feature of our OS, that we always emphasize in relation to mobile computing, is our integration of Wireless Local Area Network (WLAN) and mobile communication.

Ontologic Networking also comprises

as utilized for our Compute Node Cell (CNC) or Compute Cell (ccell) paradigm (see the OntoLix and OntoLinux Further steps of the 13th and 19th of July 2015),

(see the OntoLix and OntoLinux Further steps of the 10th of November 2017 and 20th of February 2019)
as utilized for the (micro)Service-Oriented technologies (mSOx) in the field of telecommunications.
This implies that even the common services of telecommunications service providers (telcos), like for example the operation and management of the

are also part of the infrastructure for our Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV).
Telcos in return can participate with additional performances of Ontologic Applications and Ontologic Services (OAOS), such as for example OAOS in the fields of

• IIoT and
• Industy 4.0,

• Artificial Intelligence (AI),
• Machine Learning (ML), and
• Computer Vision (CV),

• Augmented Reality (AR) and
• Virtual Reality (VR),

as can be seen with their activities in cloud computing and edge computing (see also the issue
For example, "as a peering site where customers may cross-connect directly into a wireless provider's network packet core [...]. This way, the network hand-off between the content provider and the network provider could happen instantaneously [...] instantaneous access, in place of the [Content Delivery Network (]CDN[)] arrangements [...]."

For example, it is not Internet telephony or Voice over IP (VoIP) and Internet Protocol TeleVision (IPTV) anymore.

00:11 and 07:30 UTC+1
OntoLix and OntoLinux Website update

*** Work in progress - summary of common features and our improvements ***
We added to the section Network Technology of the webpage Links to Software the links:

"The purpose of the research has been to develop a multiple tuplespace model that would scale as much as the Internet. A tuplespace is like a shared cache, in which tuples are accessed associatively.
[...]
The Cache-Only Memory Architecture (COMA) [DT99] is a Distributed Shared Memory (DSM) model, which is analogous in some ways to the tuplespace systems. These systems support a logical shared address space in a loosely-coupled environment by replicating and migrating virtual memory pages, in response to memory accesses by application processes.
[...]
Thereby, COMA promises a better average access time to data than traditional Non-Uniform Memory Architecture (NUMA) multiprocessors.
[...]
This thesis studied tuple location and replication issues in a multiple tuplespace environment. The purpose of tuplespace distribution is to provide low access latencies for parallel applications executing on different nodes, spread over the Internet.
This thesis proposed a directory based tuplespace model that allows various space servers to coordinate exchange of tuples and templates. This thesis also described protocols that allow replication of tuples and at the same time allow synchronous operations to execute with global atomicity.
[...]
The most important contribution of this thesis is that the directory based model separates protocols that allow tuple and template matches over multiple spaces from the protocols that are used for tuple replication.
[...]
So the current JavaSpaces applications can be easily ported, to be used on this multiple tuplespace platform. The application interacts with its associated space through the client proxy of the space server. The proxy has been modified to interact with the directory and remote spaces, and the distributed space accesses are transparent to the application process.
[...]
Following this would be an optimization to dynamically register spaces and space servers with a lookup server, which would control the scope of the global tuplespace."
In addition, formal modeling is applied for the development of Scalable Distributed Tuplespaces (SDT) on the basis of the Unified Modeling Language (UML) as well.

We quote some interesting features of the described system: "JavaSpaces' support for asynchronous and loosely coupled communication can be used to simplify creation of advanced services in dynamic network-centric environments. In such environments clients and services come and go all the time and system-components may dynamically be added and removed.
This paper describes how JavaSpaces can be utilized to create adaptive distributed systems. We present a space-based architecture where agents adapt to changing demands placed on the system by dynamically requesting their behavior from a JavaSpace.
We argue that using JavaSpaces technology is a simple way to create adaptive systems, due to JavaSpaces' ability to support messaging in dynamic environments as well as distribution of agent behavior.
[...] A space-based agent system is said to be robust [or resilient respectively fault-tolerant and reliable] because one agent failing will not bring the whole system down. Replication and mirroring of persistent spaces permits communication regardless of partial network and system failure. Scalability is achieved by adding new spaces and agents. Achieving adaptivity is simplified because agents may communicate without knowing each other's addresses. Agents may also communicate even if they are not executing at the same time. Since communication is anonymous and associative, a variable number of distributed agents can work together to solve a task."
[...]
In our space-based architecture, all communication is based on asynchronous associatively addressed messaging through a JavaSpace. Only agents are allowed to interact with a space. Three specialized agents are introduced, namely ActorAgents, ProtocolAgents and Role&RoutingAgents.
[...]
The ActorAgent "containers" provide Jini and JavaSpaces middleware to the role "components" hosted. Some ActorAgents represent specific entities in the real world, like SMS gateways, WAP servers or Service Capability Servers (typically OSA/Parlay gateways, location servers etc.) and therefore play specific roles.
[...]
[...] Scalable Infrastructure (SI) [8 [Cisco Uses Jini Network Technology for Scalable Communication Framework]] project by Cisco Systems is currently working on a highly scalable and robust [or resilient respectively fault-tolerant and reliable] architecture based on JavaSpaces. According to [8], SI started out as "...a project that would potentially allow an infinite number of devices/users to attach to a communications architecture and fulfill its mission under severe time restrictions in an almost real-time environment".
[...]
A possible solution to this problem could be to use a "local" space implementation that is not dependent of [the Remote Method Invocation (]RMI[) request-response protocol, which is the object-oriented programming analog of the Remote Procedure Call (RPC) protocol,] and may allow for optimized communication between locally deployed ActorAgents. Doing this would combine the benefits of associatively addressed messaging with fast messaging within one [Java Virutal Machine (]JVM[)].
[...]
ServiceFrame [[9] Service-Centered Approach to Telecom Service Development] is a service execution framework that contains specific functionality for advanced telecommunication and Internet services. By specializing an already existing set of domain objects new services can be created rapidly. As shown in Figure 5, ServiceFrame is layered on top of the more general ActorFrame and JavaFrame frameworks.
[...]
JavaFrame [10] is a Modeling Development Kit (MDK) which targets large, complex real-time systems written in the Java programming language. These systems are modeled as active objects (state machines and composites) that interact asynchronously."
See the reflective and distributed operating system Apertos (Muse) and the Cognac system based on Apertos, and the related sections of the webpage Overview of the website of OntoLinux.
This document even shows that

• Jini and JavaSpaces (also called a lightweight SOA),
• Space-Based Architecture (SBA) in general, following many of the principles of
  • REpresentational State Transfer (REST),
  • Service-Oriented Architecture (SOA), and
  • Event-Driven Architecture (EDA),

  as well as elements of

  • Grid Computing (GC), including
    • messaging grid,
    • data grid, and
    • processing grid, which is a parallel processing component based on the Master-Worker (MW) pattern (also known as a BlackBoard (BB) pattern (e.g. system of loosely-coupled applications and services, Tuple Space (TS), and Linda like system)) that enables parallel processing of events among different services and where the commands are written as tasks to a shared resource and executed by many threads in parallel,

  and

• our OS in particular,

and

as well (see also the Clarification of the 11th and 23rd of February 2019, the Website update of the 20th of February 2019, and the Website update of the 8th and 9th of March 2019 respectively the Clarification of the 1st of December 2018).

Like the Virtual Service Grid (VSG) approach, the approaches of the Scalable Distributed Tuplespaces (SDT) and the Space-Based Agent System (SBAS) correspond and fit together perfectly with

Also note the still existing importance of a lookup service even in the cases of SDT and SBASs (see also the Clarification of the 1st of December 2018 and once again the Further steps of the 20th of February 2019).
Like the document about the Agent-Based Operating System (ABOS), the descriptions of the SDT and the SBAS also have many matches with the description of our OS and therefore give critics virtually no room to question the related properties of our OS and the related integrations with our OSA.

In addition to KLOS, SPACE, and CHAM, Apertos (Muse), TUNES OS, ABOS, Multi-Agent Systems (MASs), SimAgent Toolkit, Maude, basic properties of (mostly) being self-adaptive and self-organizing, and so on, we also integrated more fields of SoftBionics (SB), specifically

• semantic agent (e.g. Nuin), and
• semantic grid,

• cognitive grid.

We added to the section Collaborative Virtual Environment of the same webpage the projects:

From the first document about Solipsis titled "Toward a Peer-to-Peer Shared Virtual Reality" we got the following introduction: "Shared virtual reality is very popular among science fiction fans and it has been pictured out in many books and movies in which is known as cyberspace [1 [Neuromancer]], metaverse [2 [Snow Crash]] or "the matrix" [3].
[...]
The system we are designing and building, Solipsis¹, intends to be scalable to an unlimited number (millions, billions or more) of users and objects. Since we aim to make Solipsis accessible to low end computers connected at 56Kbs and to mobile wireless devices and not only to full featured broadband connected engines the not so well deployed IP multicast was discarded. And as we mainly focus on solving the scalability issue, the idea arises of getting rid of servers and building up a solution solely based on a network of peers.
[...]
¹ The Solipsis name comes from a philosophical doctrine that claims that reality only exists in one's mind."

While the authors explain in the beginning "[a] point that might be an issue for Solipsis scalability and usability is that each movement (teleportation as well as local movements) generates flows of messages and induces local (in time and space) inconsistencies [...] since Solipsis intends to be a "place" to meet and communicate [...]", they later explain that "[s]imulations have shown that local awareness and global connectivity are well maintained and that traffic remains low and local despite variations in number of participants and huge mobility [15 [A survey of mobility models for ad-hoc network research]]. In particular, teleportation algorithms allow entering the world without disturbing the system."
In a related document titled "Distributed Dynamic Delaunay Triangulation in d-Dimensional Spaces" (to be added in the next website update) the authors suggest to utilize Voronoi diagrams and their dual, Delaunay triangulations.
Here and now, one can see nicely the basic property of our OS of (mostly) being geometric and the reason why we also utilize the techniques of Voronoi diagram or Voronoi tesselation, and Delaunay triangulation or Delaunay tesselation once again, specifically

(see the OntoLix and OntoLinux Website update of the 21st of August 2017, and the OntoLix and OntoLinux Further steps of the 23rd of September 2017 and 16th of August 2018), in combination with VSG, SDT, and other approaches.

"So typically a MMOG "server" is a group of machines with dedicated responsibilities [...] Each machine has a different responsibility to the game. The whole "cluster" of machines operates using grid computing [...] methods to dynamically share resources and ensure consistency across the cluster.
[...]
We have also incorporated the concepts of agent cloning, host replication, and agent groups within our framework.
To support multiagent organization, communication, and coordination as a P2P infrastructure, we also incorporate the concept of agent groups. Any agent within the agent group may perform a multicast or a subcast. A multicast communication allows an agent in the group to send a message to all other agents in the group, no matter where the agents are in the system. A subcast allows an agent to send a message to a subset of the group. Agent groups are identified by name, thus an agent may join a group by merely specifying its name.
The overall system behavior can be seen as an emergent property of the concurrent execution of all agents in the system. Our framework enables the understanding of P2P based MMOG design using mobile agents by specifying and simulating behavior on various levels.
[...]
We have designed our topology with the ability to organize itself efficiently, to reduce the inherent scalability problems. Most basic to this organization is the creation of supernodes. The network can identify which nodes would make good supernodes, based on how much bandwidth a node has and how often and for how long it is usually a part of the network. Supernodes connect to one another and have a collection of normal nodes connected to them. In larger networks, a collection of supernodes could even set up a super-supernode, connected to other super-supernodes, and so on. These scaling techniques have been applied to our MMOG to improve efficiency."

Their emergent and self-organizing Peer-to-Peer (P2P) computing topology for MMOGs based on Multi-Agent Systems (MASs) also corresponds and fits together perfectly with the approaches of the Virtual Service Grid (VSG), the Scalable Distributed Tuplespaces (SDT), the Space-Based Agent System (SBAS), and our parallized Chord# with structured superpeers. See once again the Ontologic Net Further steps of the 18th, 20th, and 23rd of February 2019.
See also the basic properties of our Ontologic System (OS) and the Voronoi Self-organizing Overlay (VSO) of the Voronoi-based Overlay Network (VON)-based Application-layer Spatial Publish Subscribe (SPS) with Topology-awareness (VAST).

zoning or zoned federation
The authors discuss the utilization of structured Peer-to-Peer (P2P) approaches based on the approaches of the Distributed Hash Table (DHT) overlay and unstructured Peer-to-Peer (P2P) computing based on

• Voronoi diagrams in Solipsis and
• Voronoi-based Overlay Network (VON)-based Application-layer Spatial Publish Subscribe (SPS) with Topology-awareness (VAST) in Adaptive Scalable Cooperative Environment for Networked Virtual Environment (NVE) Developments (ASCEND) (to be referenced in the next website update),

but prefer a hybrid infrastructure based on a DHT overlay and an unstructured P2P scheme with hexagonal zoning.

"Colyseus enables low-latency game-play via three important design choices: (1) decoupling object discovery and replica synchronization, (2) proactive replication for short-lived objects, and (3) pre-fetching of relevant objects using interest prediction. Our investigation showed that a range-queriable DHT achieves better scalability and load balance than a traditional DHT when used as a object location substrate, with a small consistency penalty."
Colyseus is utilized for First Person Shooter (FPS) and Real-Time Strategy (RTS) games, which demand real-time performance.
We refer to VSG, SDT, parallized Chord#, and so on once again, and note the overall synergies set free by our integrating OSA.
We improved this even more, as can be seen our OS has everything (e.g. SoftBionics (SB)) for adapting improvements, as in the case of our parallelized Chord# range-queriable lookup algorithm is exactly in correspondence with the requirements of VEs as well.
reduce the bandwidth requirements for both game servers and clients, address consistency, hotspot, congestion and server failure problems, and allow seamless interaction between objects residing on areas handled by different servers

We have not referenced the project and the related document "Hydra: A Massively-Multiplayer Peer-to-Peer Architecture for the Game Developer" (at this time), because Hydra shows how the single parts, which were already overworked, extended, and optimized by us, can be integrated by our Ontologic System Architecture (OSA), which integrates all in one, including all of the prior art.
"We present the design and implementation of Hydra, a peer-to-peer architecture for massively-multiplayer online games [(MMOG)]."

"In addition to peer-to-peer approaches, there are a number of other distributed architectures for peer-to-peer games. Cronin et al. proposed a mirrored architecture, which is a hybrid peer-to-peer and server-client architecture [8]. Rhalibi et al. proposed a similar architecture implemented on [Juxtapose (]JXTA[) (P2P protocols defined as messages in eXtensible Markup Language (XML))] where a DHT is used as the underlying communication substrate and validated it by implementing a game called "Time Prisoners" [20]. Assiotis et al. also proposed an architecture with multiple servers each responsible for one region of the virtual game world [1].The focus on their work however is in achieving efficient event delivery, replication consistency and liveness, and not on fault tolerance. Our work differs from these works because our focus is on developing a programming interface that can be supported transparently at the network layer, instead of designing a network architecture for efficiency or reliability. Optimal Grid [17 [OptimalGrid - autonomic computing on the grid]], is a project that attempts to achieve a similar goal, but in a Grid environment."
Hydra references

• Mercury: Supporting scalable multi-attribute range queries, which we do with the lookup service Chord#, which again was parallized, extended, and optimized by us,
• Colyseus, which is referenced with this website update,
• runtime verification for cheat detection, which is one of the basic properties of our Ontologic System (OS),
• Dive, which is already referenced in this section Collaborative Virtual Environment of the webpage Links to Software,
• Zoned federation of game servers: a peer-to-peer approach to scalable multi-player online games, which is referenced with this website update,
• Agents-based modeling for a peer-to-peer MMOG architecture, which is referenced with this website update, and
• MOPAR, which is referenced with this website update,

Interestingly, one of the authors of Hydra also is an author of the work titled "EpiChord: Parallelizing the Chord Lookup Algorithm with Reactive Routing State Management" and parallelization, which we already adapted for our (soft)bionic (self-organizing, Machine Learning (ML), Soft Computing (SC), Autonomic Computing (AC), etc.) parallized, extended, and optimized lookup service Chord# with structured superpeers (see also the Voronoi-based Overlay Network (VON)-based Application-layer Spatial Publish Subscribe (SPS) with Topology-awareness (VAST)), and one- or two-hop lookup, constant-hop, and logarithmic-hop performance.
Our parallized Chord# allows a completely new management of computing and networking in general, so that the question is not anymore how billions or trillions objects or messages can be processed at all, but how many objects can be

• processed in real-time, or
• kept in a state of
  • synchronicity,
  • consistency,
  • validity, or
  • verifiability

(see once again the Ontologic Net Further steps of the 18th, 20th, and 23rd of February 2019). :D
Also note that the foundation of the field of Autonomic Computing (AC) was created with our Evolutionary operating system (Evoos) described in The Proposal and AC is included in our field of SoftBionics (SB), while SB is a foundation and Evoos is the previous generation of our Ontologic System (OS).

For Addressing Cheating in Distributed MMOGs and make much more possible we have the basic properties of our OS, including

• capability-based security, specifically capability-based operating system,
• smart contract transaction protocol,
• blockchain technique,
• Byzantine resilience protocols, including
  • Byzantine Fault Tolerance (BFT) protocols, and
  • Byzantine-Resilient Replication (BRR) method,
• etc.,

We also have adapted the stationary and mobile CVEs, and DVEs or NVEs, including MMVEs, and integrated them with

• wireline and wireless communications,
• High Performance and High Productivity Computing Systems (HP²CSs), and
• Fault-Tolerant, Reliable, and Trustworthy Distributed Systems (FTRTDSs)

by our Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV).

Note how everything always repeats, corresponds, and fits together perfectly, which also proves that the minimalistic description of our OS is not a happenstance or a cheap trick, but in fact a very well thought out work of art that goes far beyond a common scientific work.

12.March.2019

02:56 and 16:32 UTC+1
OntoLix and OntoLinux Website update

*** Work in progress - better wording ***
In the Website update of the 21st of August 2017 we already mentioned that we utilize Voronoi diagrams for our OntoGlobe and related systems, applications, and services, and also other utilizations, including the field of

• Real Reality Environment (RRE) or simply Real Environment (RE),
• Augmented Reality Environment (ARE) and
• Augmented Virtual Environment (AVE),
• Virtual Reality Environment (VRE) or simply Virtual Environment (VE), including
  • Collaborative Virtual Environment (CVE), and
  • Distributed Virtual Environment (DVE) or Networked Virtual Environment (NVE), including
    • Massively Multiuser Virtual Environment (MMVE), including
      • Massively Multiplayer Online Games (MMOG),

as well as their fusion to our New Reality Environment (NRE) of our OntoVerse (OV) component as part of the manifestation of our New Reality (NR) as the Ontoverse (Ov).
In the Website update of the 10th of March 2019 we already mentioned in relation to zoning in DVEs or NVEs that we utilize Voronoi diagrams for the fields of Voronoi-based Overlay Network (VON) and state management as well besides the utilizations of Voronoi diagram and Delaunay triangulation described in the given links and in combination with Virtual Service Grid (VSG), Scalable Distributed Tuplespaces (SDT), and so on.
We continue with the update of the website at this point today.

We added to the section Network Technology of the webpage Links to Software the link:

"Voronoi diagrams and [their dual,] Delaunay triangulations[,] have proved to be efficient solutions to numerous theoretical problems. They appear as an appealing structure for distributed overlay networks when entities are characterized by a position in a d dimensional space. In this paper, we present some algorithms aiming to maintain an overlay network matching the Delaunay triangulation of the participating entities. We consider that entities are dynamic, that is, they can appear and disappear at any time.
[...]
One of the main drawbacks of these algorithms is the greedy walk needed to detect the entity closest to the queried position. Some recent studies [8 [Could Any Graph Be Turned Into a Small World]] show how to construct small-world networks by adding only one edge between two entities in the overlay. In these small-world networks, a basic walk is guaranteed to succeed in polylogarithmic time. We will try to transform the Delaunay triangulation to a small-world network, such that the detection of the closest entity could be substantially more efficient.
[...]
We intend to use the protocol in 3-dimensions for shared virtual worlds. Especially, we may apply it in the Solipsis [16] platform."
The document also references the document titled "Scalable Peer-to-Peer Networked Virtual Environment" (see below for its updated version).
Here we can see nicely once again the basic property of our OS of (mostly) being geometric and also n-dimensional, as well as how our Ontologic System Architecture (OSA) integrates all in one.
In addtion, our (hyper)graph-based and improved networking is even more efficient and literally spoken the original and unique Game Changer.

A short quote of the homepage of the programming library VAST is given in the Website update of the 21st of August 2017.

"[The authors describe] Voronoi Self-organizing Overlay (VSO), which extends a Voronoi-based Overlay Network (VON) to support SPS operations in constant time and performs automatic load balancing."

"By dynamically partitioning the VE with Voronoi diagrams and aggregating game states of overloaded nodes onto superpeers, VSM supports existing consistency control to enable scalable, load balanced, and fault tolerant VE state management. As both client and server-side resources are utilized collaboratively, VSM also integrates both client-server and peer-to-peer VE designs in a unified approach."
"Few work exists on state management for P2P VEs. SimMud [10 [Peer-to-peer support for massively multiplayer games; based on Scribe: A large-scale and decentralized application-level multicast infrastructure; both based on Pastry]] supports basic state management via superpeers within fixed-size regions. VSM has gone further to allow dynamic region partitioning. Colyseus [12] supports first person shooter (FPS) games based on [Distributed Hash Tables (]DHTs[)], but the log(n) query in DHT may create unacceptable object discovery latency for large node size. By using VON [4], VSM discovers objects within bounded query hops. Time Prisoner [13 [Agents-Based Modeling for a Peer-to-Peer MMOG Architecture]] has basic state management in superpeer-managed zones, but does not consider inter-zone interactions or load balancing. HYMS [11] and Hydra [14] consider fault tolerance issues, but still rely heavily on server resources. Naor and Wieder [36] propose Voronoi partitioning for DHT overlays, but only fixed node locations are considered. Chen and Lee first suggest the use of Voronoi to partition VEs [37], but details are not given. Ohnishi et al. [8] describe a Delaunay (dual of Voronoi diagrams) overlay for VEs, but without considering state management. Our concept of aggregators is similar in spirit to the node clustering scheme recently proposed by Varvello et al. [9] for Delaunay overlays."
VAST also shows how a self-organizing network can adapt dynamically to a change in systems and environments. However, they do not deal with superpeer overloads when the node density increases, while other state management aspects such as consistency control are also not considered.
Also note the aspect of fault tolerance and other aspects, which shows how our Ontologic System also inspired further activities in the field of Virtual Environment (VE).

We added to the section Collaborative Virtual Environment of the same webpage the project:

• Chien-Hao Chien, Shun-Yun Hu, and Jehn-Ruey Jiang: Delaunay State Management [(DSM)] for Large-scale Networked Virtual Environments
• Chang-Hua Wu, Shun-Yun Hu, and Li-Ming Tseng: Discovery of Physical Neighbors for P2P 3D Streaming

"ASCEND is a collective effort to construct programming libraries that will faciliate the creations of scalable, affordable, and accessible peer-to-peer (P2P)-based 3D networked virtual environments (NVEs) where participants may share data (e.g. files, photos, blogs) and interact with one another in real-time. ASCEND is based on the scalable Voronoi-based overlay network (VON) [programming library VON-based Application-layer Spatial Publish Subscribe (SPS) with Topology-awareness (VAST)] and a number of important P2P-based NVE (P2P-NVE) issues will be investigated, including: 3D streaming for P2P-NVEs, state management in P2P-NVEs, persistent storage designed for P2P-NVEs, and suitable P2P-NVE overlays."

"[The authors] present DSM, a p2P-NVE state management system with strong consistency an anti-cheating support. Our system is good at managing objects with strict consistency requirements, at the expense of additional latency. DSM thus is suitable for managing important objects or events with strict consistency requirements, such as trading. Considering more dynamic objects, other state management schemes such as Colyseus [2] or VSM [7 [Voronoi state management for peer-to-peer massively multiplayer online games]] [of VAST] may complement DSM in managing those objects. The mutual checking mechanism in DSM is general, so application to other types of triangulations [4] may also be possible."

In the Ontologic Net Further steps of the 23rd of February 2019 we already mentioned the similarity between the field of DVE or NVE, and MMVE on the one side and the field of Information-Centric Networking (ICN) on the other side (e.g. publish-read, publish-subscribe, producer-consumer, ...) as we also noted in relation to ontology-based middleware.
When taking this direction, then temporal and spatial, and also topical or thematic publish-subscribe is done according to the Caliber/Calibre and Ontologic uniVerse (OntoVerse or OV).
The temporal and spatial, and also topical or thematic dimensions also provide the foundation for the seamless integration of Geographic Information Systems (GISs), like our OntoGlobe and OntoEarth, as well our Semantic Sensor Net (SSN) and Semantic Sensor Web (SSW), and even Channel Computing by design.

We have integrated Voronoi and Delaunay with each other and our parallized Chord# range-queriable lookup, routing, forwarding, caching, and other services, VSG, SDT, VOS, and so on as part of our Ontologic Networking (ON), that solves all issues with P2P VEs and hybrids as well.
This is just another revolution realized with our original and unique, iconic work of art titled Ontologic System and created by C.S. in 2006 already.
This shows how significant, original and unique this next improvement or creation of C.S. truly is and that we solved this specific issue as well, indeed.
Also keep in mind that we integrated KLOS, SPACE, and CHAM, Apertos (Muse), TUNES OS, SimAgent Toolkit, Maude, etc. and also all of the advantageous features of such DVEs.
The overall result is something totally new, that provides totally new possibilities. See our Caliber/Calibre and your favorite works of cyberspace science fiction once again. :D

At the end, we would like to make clear once again that

(see also the end of the Website update of the 10th of March 2019).

It's not a trick - It's Ontologics

13.March.2019
Ontonics Further steps
For sure, we are continuing the work on our own hardware such as routers utilzed for our Ontologic Networking, with which we unified all kinds of networks including networks for wireline and wireless communication and data transfer.
For providing superior performances and accomplishing our goals we utilize the expertises of at least two research institutes with related hardware, as well as our own knowledge gained with our processors and Wireless Supercomputer (WiSer).

Governing authorities can express their desires which hardware manufacturers are allowed to collaborate with us for implementing our routers and other hardware as well as related software.

Btw.: We observed that some companies are still trying to outpace or ignore us. But there is no gold rush in this field, too, due to the reason that eventually our hardware and software is required.

14.March.2019
Style of Speed Further steps
It is doodle time at Style of Speed and today we would like to present with the model CSR, also known as the Yellow Dragon, another Classic model of our 9x9 series.

©

Please do not confuse our original and unique model CSR with a plagiarism called CTR or so.

16.March.2019

09:40 and 27:00 UTC+1
Investigations::Multimedia

*** Work in progress - some kind of an epilog ***

We also know that Kubernetes is the successor of the cluster management system Borg utilized for High-Throughput Computing (HTC) (see also Maui and HTCondor). From the related document titled "Large-scale cluster management at Google with Borg" and publicated by the company Google in April 2015 we got the following informations:
"[...] a set of qualitative observations we have made from operating Borg in production for more than a decade. [This implies that Borg is used since April 2005 at least. But the statement is relatively vague and correspondingly no reference or citation is given.]",
"A Borg job's properties include its name, owner, and the number of tasks it has. [...] Each task maps to a set of Linux processes running in a container on a machine [62 [Linux control groups [...], 2007-2014]]. The vast majority of the Borg workload does not run inside virtual machines (VMs), because we don't want to pay the cost of virtualization. Also, the system was designed at a time when we had a considerable investment in processors with no virtualization support in hardware. [Somehow, we have contradictory statements because between April 2005 and September 2006 neither process containers nor control groups (cgroups) did exist in the Linux kernel. Also, the term workload is connected with one or more jobs, units of work, or unit of execution, which again are terms used in the field of job scheduler and cluster batch system. In the fields of High-Performance Computing (HPC) and Cluster Computing (CC or ClusterC) the fields of batch scheduling and parallel computing are two different subfields.]",
"Users operate on jobs by issuing remote procedure calls (RPCs) to Borg [...].",
"It's not enough to create and place tasks: a service's clients and other systems need to be able to find them, even after they are relocated to a new machine. To enable this, Borg creates a stable "Borg name service" (BNS) name for each task that includes the cell name, job name, and task number. Borg writes the task's hostname and port into a consistent, highly-available file in Chubby [14 [The Chubby lock service for loosely-coupled distributed systems [...] 2006]] with this name, which is used by our RPC system to find the task endpoint. The BNS name also forms the basis of the task's DNS name [...]. Borg also writes job size and task health information into Chubby whenever it changes, so load balancers can see where to route requests to. [We note that Borg is based on the Remote Procedure Call (RPC) mechanism, which again is a request-response protocol for Inter-Process Communication (IPC). See for example the Common Object Request Broker Architecture (CORBA) and other middleware based on the RPC protocol and the Remote Method Invocation (RMI) protocol, which is the object-oriented programming analog of RPC.]",
"A Borg cell consists of a set of machines, a logically centralized controller called the Borgmaster, and an agent process called the Borglet that runs on each machine in a cell [...]. [Because Borg has a master a Borglet is a worker (node), so that we have a Master-Worker (MW) computing system, which matches with the characterization of a job scheduling system and a High-Throughput Computing (HTC) system.]",
"Each cell's Borgmaster consists of two processes: the main Borgmaster process and a separate scheduler [...]. The main Borgmaster process handles client RPCs that either mutate state (e.g., create job) or provide read-only access to data (e.g., lookup job). It also manages state machines for all of the objects in the system (machines, tasks, allocs, etc.), communicates with the Borglets, and offers a web UI as a backup to Sigma. [Recall that in Event-Driven Architecture (EDA), the program is structured as a state machine that is driven by progress of certain operations, typically involving Input/Output (I/O). Event-driven programs make use of non-blocking or asynchronous primitives, along with event notification systems.]",
"When a job is submitted, the Borgmaster records it persistently in the Paxos store and adds the job's tasks to the pending queue. This is scanned asynchronously by the scheduler, which assigns tasks to machines if there are sufficient available resources that meet the job's constraints. (The scheduler primarily operates on tasks, not jobs.)",
"A single elected master per cell serves both as the Paxos leader and the state mutator, handling all operations that change the cell's state, such as submitting a job or terminating a task on a machine. A master is elected (using Paxos) when the cell is brought up and whenever the elected master fails; it acquires a Chubby lock so other systems can find it. [Somehow, we have the impression that somebody is talking about the reflective, fault-tolerant, reliable, and distributed operating system Apertos (Muse).]",
"A high-fidelity Borgmaster simulator called Fauxmaster can be used to read checkpoint files, and contains a complete copy of the production Borgmaster code, with stubbed-out interfaces to the Borglets. It accepts RPCs to make state machine changes and perform operations [...]. [It is uncleare since when Fauxmaster is existing.]",
"The Borglet is a local Borg agent that is present on every machine in a cell. It starts and stops tasks; restarts them if they fail; manages local resources by manipulating OS kernel settings; rolls over debug logs; and reports the state of the machine to the Borgmaster and other monitoring systems. [We still cannot see when the Borglet got these functionalities, though elsewhere in the document they are related to containers (kernel process address spaces), which were introduced in 2006, but the relevant containers patch V1 for the Linux kernel is not referenced at all, and "Each task maps to a set of Linux processes running in a container on a machine [62 [Linux control groups [...], 2007-2014]]" and "cgroup-based resource container", which were introduced in 2007. See also the quote related to containers below this quoted document. Before this date, Borg was not an Agent-Based System (ABS) but only a Master-Worker (MW) computing system with some Autonomic Computing (AC) functionalities. Somehow, we have the impression that the term agent is used in retrospect to present Borg as a system that is more similar to our Evolutionary operating system (Evoos) and our Ontologic System (OS), specifically as a Multi-Agent System (MAS) and in this way to mislead the public. See also the comments to the quotes about the Google Container Engine respectively Kubernetes Enigne below and the quotes related to Space-Based Architecture (SBA) below these quotes.]",
"Offering a set of fixed-size containers or virtual machines, although common among IaaS (infrastructure-as-a-service) providers [7 [AWS. Amazon Web Services VM Instances [...] 2006], 33 [GCE. Google Compute Engine [...] 2012]], would not be a good match to our needs. [It is not clear what Borg is offering since when, though we imply that the size of containers is unspecified and containers are utilized either since Google's containers V1 patch was implemented in 2006 or cgroups were included in the Linux kernel in 2007, as said above, which means around 6 respectively 7 years after the first presentation of our Evoos with its operating system Virtual Machine (osVM) and os-level virtualization or containerization. Also note that the term container is used as a synonym for the term virtual machine. See also the quotes related to containers, cgroups, and namespace below these quotes.]",
"We use a Linux chroot jail as the primary security isolation mechanism between multiple tasks on the same machine. [...] VMs and security sandboxing techniques are used to run external software by Google's App Engine (GAE) [38 [2008]] and Google Compute Engine (GCE) [[33] [2012]]. We run each hosted VM in a KVM process [54 [2006]] that runs as a Borg task. [The Kernel-based Virtual Machine (KVM) allows the Linux operating system (os) kernel to function as a hypervisor, which is also known as a Virtual Machine Monitor (VMM) and is the supervisor of supervisiors. See also once again the quotes related to containers, cgroups, and namespace below this quote of the document.]",
"Early versions of Borglet had relatively primitive resource isolation enforcement: post-hoc usage checking of memory, disk space and CPU cycles, combined with termination of tasks that used too much memory or disk and aggressive application of Linux's CPU priorities to rein in tasks that used too much CPU. [...] Now, all Borg tasks run inside a Linux cgroup-based resource container [17 [cgroups], 58 [Google LMCTFY project (let me contain that for you) [..., 2013 (container stack, which provides Linux application containers)]], 62 [Linux control groups [...], 2007-2014]] and the Borglet manipulates the container settings, giving much improved control because the OS kernel is in the loop. [What means the temporal statement now here? It is unclear since when Borg tasks or Borglets run inside chroot jails and then in containers or control groups (cgroups), though we do know that the designation cgroups is existing since 2007. See also once again the quotes related to containers, cgroups, and namespace below these quotes. Furthermore, the property of an "OS kernel in the loop" suggests a cybernetic and reflective overall system.]",
"A user-space control loop in the Borglet assigns memory to containers based on predicted future usage (for prod tasks) or on memory pressure (for non-prod ones); [...]",
"[69 [Omega: flexible, scalable schedulers for large compute clusters. 2013]] contains a taxonomy of cluster manager architectures. [...] Apache Mesos [45 [Mesos: a platform for fine-grained resource sharing in the data center [...] 2011]] splits the resource management and placement functions between a central resource manager (somewhat like Borgmaster minus its scheduler) and multiple "frameworks" [...]. YARN [76 [Apache Hadoop YARN: Yet Another Resource Negotiator [...] 2013]] is a Hadoop-centric cluster manager. [...] Facebook's Tupperware [64], is a Borg-like system for scheduling cgroup containers on a cluster; [...]. Twitter has open-sourced Aurora [5], a Borg-like scheduler for long running services that runs on top of Mesos, with a configuration language and state machine similar to Borg's. [And Google wants to tell us that the others needed so long to do the same.]",
"The Omega architecture was designed to support multiple distinct workloads that have their own application-specific RPC interface, state machines, and scheduling policies (e.g., long-running servers, batch jobs from various frameworks, infrastructure services like cluster storage systems, virtual machines from the Google Cloud Platform). On the other hand, Borg offers a "one size fits all" RPC interface, state machine semantics, and scheduler policy [...]. [Omega was presented in the year 2013. Also note how Google tries to fill the gap between Borg with chroot jail and virtual machines, also wrongly called containers (later control groups (cgroups)), and Kubernetes with Docker by discussing other plagiarisms and fakes of our Evoos and our OS.]",
"Google's open-source Kubernetes [Engine (formerly Container Engine)] system [53 [2014]] places applications in Docker containers [28 [2014]] onto multiple host nodes. It runs both on bare metal (like Borg) and on various cloud hosting providers, such as Google Compute Engine. [Because it also runs on bare metal, Kubernetes must have functionalities of an operating system (os) kernel.]",
"In this section we recount some of the qualitative lessons we've learned from operating Borg in production for more than a decade, and describe how these observations have been leveraged in designing Kubernetes [53]. [So let us listen to the Google story.]",
"[...] Kubernetes rejects the job notion and instead organizes its scheduling units (pods) using labels - arbitrary key/value pairs that users can attach to any object in the system. [...] Operations in Kubernetes identify their targets by means of a label query that selects the objects that the operation should apply to. This approach gives more flexibility than the single fixed grouping of a job." [This turns the Master-Worker (MW) pattern into a BlackBoard (BB) pattern, which is the central space of a Multi-Agent System (MAS). See also once again the quotes related to command pattern and Space-Based Architecture (SBA) below these quotes.],
"Thanks to the advent of Linux namespaces, VMs, IPv6, and software-defined networking, Kubernetes can take a more user-friendly approach that eliminates these complications: every pod and service gets its own IP address, allowing developers to choose ports rather than requiring their software to adapt to the ones chosen by the infrastructure, and removes the infrastructure complexity of managing ports. [This is very interesting, because we know now when all these items came together. By the way: We learned before that Virtual Machines (VMs) are not good for this task of workload scheduling.]",
"The Kubernetes equivalent of an alloc is the pod, which is a resource envelope for one or more containers that are always scheduled onto the same machine and can share resources. Kubernetes uses helper containers in the same pod instead of tasks in an alloc, but the idea is the same.",
"Kubernetes supports naming and load balancing using the service abstraction: a service has a name and a dynamic set of pods defined by a label selector. Any container in the cluster can connect to the service using the service name. Under the covers, Kubernetes automatically load-balances connections to the service among the pods that match the label selector, and keeps track of where the pods are running as they get rescheduled over time due to failures.",
"Kubernetes aims to replicate many of Borg's introspection techniques. For example, it ships with tools such as cAdvisor [15] for resource monitoring, and log aggregation based on Elasticsearch/Kibana [30] and Fluentd [32]. The master can be queried for a snapshot of its objects' state. [The cAdvisor is a component on a slave node that provides a limited metric monitoring capability.]",
"The master is the kernel of a distributed system. [] Borgmaster was originally designed as a monolithic system, but over time, it became more of a kernel sitting at the heart of an ecosystem of services that cooperate to manage user jobs. For example, we split off the scheduler and the primary UI (Sigma) into separate processes, and added services for admission control, vertical and horizontal autoscaling, re-packing tasks, periodic job submission (cron), workflow management, and archiving system actions for off-line querying. Together, these have allowed us to scale up the workload and feature set without sacrificing performance or maintainability. [As in the case of the plagiarism NetKernel, we note that on the one hand a system is called a kernel and a monolithic system, which both are terms used in the field of operating systems but on the other hand no kernel can be seen here. When taken together with the description of a Master-Worker (MW) computing system as an Agent-Based System (ABS) and other aspects, then we have to assume that the same attempt is tried to confuse the public in relation to our Ontologic System (OS).]", and
"The Kubernetes architecture goes further: it has an API server at its core that is responsible only for processing requests and manipulating the underlying state objects. The cluster management logic is built as small, composable micro-services that are clients of this API server, such as the replication controller, which maintains the desired number of replicas of a pod in the face of failures, and the node controller, which manages the machine lifecycle. [This Application Programming Interface (API) server is merely a request broker for processing messages sent between objects by utilizing the RPC mechanism.]".

Containers
Google's Rohit Seth's containers V1 patch was released on the 14th of September 2006.
The related email sent to the mailing list of the Linux kernel says the following: "Containers:
Commodity [HardWare (]HW[)] is becoming more powerful. This is giving opportunity to run different workloads on the same platform for better HW resource utilization. To run different workloads efficiently on the same platform, it is critical that we have a notion of limits for each workload in Linux kernel. Current cpuset feature in Linux kernel provides grouping of CPU and memory support to some extent (for [Non-Uniform Memory Access (]NUMA[)] machines).
[...]
The user interface for containers is through configfs.
[...]
This is based on lot of discussions over [the] last month or so.
[...]"

(Process) containers were later renamed to control groups (cgroups) and released with the Linux kernel in 2007.
A related report says on the 29th of May 2007 that "[t]he [containers V10] patch has evolved considerably, to the point that Rohit's name no longer appears within it."
And comments to this report adds the following: "What the container concept seems to be [...] is extending that ability to isolate resources to processes running within the base OS.
ie, if you are putting hooks into the kernel to be able to define and limit system resources for virtual machines, why not extend it to processes and resources at the OS level?"
"Right now all resource management is done globally or per process/thread, but not much else. Process containers make it possible to group a bunch of processes and do resource allocation for them as a group (think ulimit, but more). [...]
This is useful for multi-purpose and multi-user machines. [...]
It seems it can also function as a sort of [chroot] jail, limiting the [file system (]fs[)] and process namespace view/access processes have."

This also shows the fundamental

An online encyclopedia gives the following information about namespaces: "[...]
Namespaces are a fundamental aspect of containers on Linux.
[...]
The cgroup namespace type hides the identity of the control group of which process is a member. A process in such a namespace, checking which control group any process is part of, would see a path that is actually relative to the control group set at creation time, hiding its true control group position and identity. This namespace type has existed since Linux 4.6.[6 [2016-03-18]][7 [2016-03-26]]"

An online encyclopedia gives the following information about the command pattern: "[...]
Parallel Processing
Where the commands are written as tasks to a shared resource and executed by many threads in parallel (possibly on remote machines - this variant is often referred to as the Master/Worker pattern)"]

An online encyclopedia gives the following information about the Space-Based Architecture (SBA): "[...]

Components of space-based architecture
[...]
Processing unit
The unit of scalability and fail-over. Normally, a processing unit is built out of a POJO (Plain Old Java Object) container [...].
Virtual middleware
A common runtime and clustering model, used across the entire middleware stack. The core middleware components in a typical SBA architecture are:

Obviously, the document about the cluster manager Borg was created with respect to our OS, as the wrong explanations about features of our OS show. In addition, Kubernetes is even based on our OS.

As we also noted in the Clarification of the 1st of December 2018, OntoLinux is based on the transformation of the Linux kernel and therefore includes everything of the Linux kernel inclusive containers just right from its start in the end of October 2006 and cgroups since their introduction.
See also for example the Investigations::Multimedia of the 11th of December 2018.
In fact, Kubernetes is not in the grey zone, but already is the predecessor of Borg.
mSOA is not the only issue or the main issue at all.
Furthermore, we can see that there is not only mSOA 1.0 and mSOA 2.0, but in fact Cloud Computing of the first generation (CC 1.0) and Cloud Computing of the second generation (CC 2.0), which even coincide with each other or better said were developed together.

In general, we see in relation to the descriptions and informations given about or in the field of mSOA, such as for example SOCK and Jolie, Borg and Kubernetes, whatsoever and Istio, and so on, is that histories were manipulated and fabricated since around the years 2005 to 2007 and once again since around the years 2012 to 2014, which are not conclusive and persuasive when it becomes most interesting that is around the date of the publication of our OS on the 29th of October 2006. Specifically the attempt to present a seamless technological development respectively an ordinary technological progress that would create a legal loophole, fails in relation to mSOA as well.

Last but not least, we repeat what we always say in relation to containers: There exists something that is called operating system.

18.March.2019

17:41 UTC+1
SOPR #169

*** Work in progress ***
The edge is sharpening and hence we have new members of our Society for Ontological Performance and Reproduction (SOPR) with the South Korean:

The companies are telecommunications service providers (telcos) and have presented their Mobile Edge Computing (MEC) platforms and centers applying their 5G core equipment in the Control and User Plane Separation (CUPS) architecture, and in the network virtualisation technology of the MEC centres.
KT plans to use its 5G MEC centres for the deployment of its own autonomous cars, smart factory, Augmented Reality (AR), and Virtual Reality (VR) services, and also to launch new VR games.
SK Telecom said it is already in talks with cloud gaming companies, AR and VR services companies, and cloud providers on using 5G MEC.

For sure, royalties are only due for those parts that are

though we have more and more problems to find cases where the Articles of Association (AoA) and the Terms of Service (ToS) with the License Model (LM) of our Society for Ontological Performance and Reproduction (SOPR) do not apply.
For example, if an application is executed or a service is accessed with an Ontoscope, then we view it as a performance of our OAOS, that include data and communication services of telcos as well.

We have already listed

as well.

Please keep in mind that we have various ways to convince companies to become members of our SOPR, such as for example

in accordance with the AoA and the ToS of our SOPR, which were drawn up in such a way that no entity needs to shy away from making its fair share.

18:13 UTC+1
Ontonics Superstructure #21

The reactions to our latest actions in relation to our World Wide Hover Association (WWHA) Transcontinental Network respectively Silk Skyway were much more surprising and positive.

First of all, we would like to note that our friends from Turkey were quick with showing their interest for a Silk Skyway hub. Hopefully, a megahub will be sufficient to serve the needs in this region of the world.

Furthermore, we noticed that our friends in the P.R.China have a much larger demand and interest in our newest aerial vehicle with Vertical Take-Off and Landing (VTOL) capability, which is initially based on the semi-rigid airship Zeppelin NT (Neue Technologie==New Technology) and shown in the Style of Speed Further steps of the 4th of March 2019.
We will not disappoint them and can already confirm that one of the three further gigahub locations planned and later mentioned in the issue #20 of the 27th of February 2019 is located in Beijing.
But due to the huge demand and interest we were already thinking about a second gigahub and several superhubs and megahubs.
Chineses love to fly. :)

The second gigahub mentioned in the issue #20 of the 27th of February 2019 is located in Pakistan.

The third gigahub mentioned in the issue #20 of the 27th of February 2019 is located in India.

We also added another gigahub location in Australia in the east coast area.

19.March.2019

07:18 and 22:23 UTC+1
SOPR #170

*** Work in progress - maybe some specific SOPR provisions missing ***
We would like to make some few statements to the following two topics:

Digital gaming
Like

• Massively Multiuser Virtual Environments (MMVEs), such as
  • Massively Multiplayer Online Games (MMOGs),

• Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR) cloud computing platforms (AR clouds, VR clouds, and MR clouds),

we consider applications and services, which are based on the field of digital gaming, our Ontologic System Components (OSC), and our integrating Ontologic System Architecture (OSA), as Ontologic Applications and Ontologic Services (OAOS).
Please keep in mind the general provisions of our SOPR, that are demanding

from everybody participating for establishing the guiding principles of our SOPR, that are guaranteeing

for everybody participating.

Legal matters
We added a new clause to the Articles of Association (AoA) of our Society for Ontological Performance and Reproduction (SOPR).
If a new development, event, or causality is considered as an attempt to disturb the goals or even threaten the integrity of the SOPR, then the SOPR is allowed to amend the Articles of Association (AoA) and the Terms of Service (ToS) with the License Model (LM) instantly, accordingly, and reasonably.

We found out that developments, specifically integrations and hybrid environments, done in the fields of

• operating-system-level virtualization or containerization, and
• server virtualization with Virtual Machines (VMs), hypervisors, etc.,

• cluster computing

are based on our Ontologic System (OS) since at least around the year 2008, and also

are based on our OS since at least around the year 2011.
In this way, the due date 1st of January 2010 for related retroactive royalties has been confirmed once again.

20.March.2019

15:09 UTC+1
SOPR #171

*** Work in progress - maybe some SOPR provisions missing ***
We would like to talk a little about one of the missing topics already announced several days ago that is about communication, collaboration, electronic commerce, etc..

The subject matter is highly complex and much momentum is observable in the fields of

• messaging,
• voice call,
• video chat,
• video call,
• conferencing,
• meeting,
• ...,

• online marketplace (e.g. Amazon, eBay, Alibaba, ...),

as well as their integrations like for example

We cannot regulate anything specific due to our neutrality. But we would like to

• service registration and service interface filing,
• common data sharing, and
• provision of further joint efforts

from everybody participating for establishing the guiding principles of our SOPR, that are guaranteeing

• openess,
• fairness,
• neutrality,
• accountability,
• transparency, and
• interoperability, and also
• our Ontologic Economic System (OES), as well as
• protection against monopolies being created outside the regulative scope of our SOPR

for everybody participating,

• Mediated Reality (MedR) including
  • Augmented Reality (AR),
  • Augmented Virtuality (AV), and
  • Virtual Reality (VR),

• Industrial Internet of Things (IIoT) and
• Industry 4.0,

besides all the many other fields and in this way our OS provides much more possibilities to research and develop, build, provide, make business, and have fun.
Many of the customers, business partners, or members of our SOPRA will have more than enough to do and "will even not know where to begin with all the upcoming works and challenges", as we said in the issue #158 of the 24th of December 2018.

Members of our SOPR should think about their Ontologic Applications and Ontologic Services (OAOS) like HTML tags and webpages (of the Semantic (World Wide) Web (SWWW)).

21.March.2019

10:56 and 18:02 UTC+1
More evidences Microsoft and Renault-Nissan-Mitsubishi mimicking C.S. and C.S. GmbH

*** Work in progress - maybe some better wording and some SOPR provisions missing ***

We gave a little scant attention that the company Microsoft and the joint venture Renault-Nissan have collaborated in relation to the Hyper Connectivity suite and other original and unique solutions of our business unit Style of Speed in September 2016, but gave full attention that the joint venture Renault-Nissan-Mitsubishi has unveiled the production release of its so-called Alliance Intelligent Cloud on the 20th of March 2019 (yesterday). From the press release of Microsoft we got the following informations: "Renault-Nissan-Mitsubishi launches Alliance Intelligent Cloud on Microsoft Azure

[...] Renault-Nissan-Mitsubishi, the world's leading automotive alliance, today announced the production release of the Alliance Intelligent Cloud, a new platform that is enabling Renault, Nissan, and Mitsubishi Motors to deliver connected services in vehicles sold in nearly all 200 markets served by the Alliance member companies. Culminating joint development efforts between the Alliance and Microsoft, the auto industry's first global and most ambitious connected vehicle program will be deployed utilizing cloud, artificial intelligence (AI), and IoT technologies provided by Microsoft Azure. Azure provides the Alliance with a global data platform to securely capture, manage and analyze vehicle data to deliver intelligent services based on the vast volume of data created by connected vehicles.
[...] Global Vice President of Alliance Connected Vehicles at Renault-Nissan-Mitsubishi, said: "Today we are deploying a vehicle connectivity platform that will transform the digital experience for customers of Renault, Nissan, and Mitsubishi. Through our collaboration with Microsoft, we are introducing the most powerful and far-reaching connected vehicle platform. Leveraging the size and scale of the Alliance, we have built an intelligent cloud platform that sets the pace for our industry."
[...]
[...] EVP and president, Microsoft Global Sales, Marketing and Operations at Microsoft Corp. "Today's production release of the Alliance Intelligent Cloud enables a new generation of connected services powered by Microsoft Azure to come to market."
Vehicles utilizing the Alliance Intelligent Cloud will benefit from seamless access to the internet, providing enhanced remote diagnostics, continuous software deployment, firmware updates and access to infotainment services.
The Alliance Intelligent Cloud is a highly-scalable platform and will consolidate multiple legacy connected vehicle solutions with current and future connected car features and business operations that will support mobility services. The data-driven platform will enable advanced AI and analytics scenarios and accelerate time to market for new innovations and business initiatives.
Optimized for speed and efficiency, the Alliance Intelligent Cloud will connect to vehicles and share digital features and future innovations across multiple models and brands for consumers in different regions around the world. Features consolidated onto the connected platform include remote services, proactive monitoring, connected navigation, connected assistance, over-the-air software updates, and other customer-tailored services.
The Alliance is taking a unique approach to addressing the business opportunity provided by connected vehicles by owning, operating, and designing its own intelligent cloud platform on Microsoft Azure.
The Alliance Intelligent Cloud is capable of connecting Alliance vehicles with future smart cities infrastructure as it develops and with potential future partners. With this new initiative, any third-party seeking to connect with all legacy and future connected Alliance vehicles will have a single point of contact to partner with."

From a report we got the following additional informations: "The first cars using Microsoft Connected Vehicle platform at scale are coming
[...]
In September 2016, Renault-Nissan announced it planned to use a number of Microsoft cloud services in its next-gen vehicles. This week, the auto maker is ready to deploy services built on Microsoft's Connect[ed] Vehicle Platform at scale, becoming the first Microsoft Connected Vehicle Platform partner to do so.
Microsoft's Connected Vehicle Platform - formerly known as its Connected Car Platform - is all about getting vehicles to connect to Microsoft cloud services like Azure, Office 365 and more on the back-end. Microsoft's Connect[ed] Vehicle strategy replaced its old "Windows Automotive" plan, via which Microsoft attempted to convince car makers to embed Windows inside their vehicles.
On March 20, Renault-Nissan-Mitsubishi unveiled the production release of what the group calls its "Alliance Intelligent Cloud."
[...]
Microsoft isn't the only tech vendor with connected-vehicle ties to Renault-Nissan-Mitsubishi. Last year, the Alliance signed a multi-year deal with Google to produce vehicles with Android-powered infotainment systems as part of a wider strategy to equip new vehicles with a wider array of connected systems.
The rollout of vehicles running Android infotainment systems is expected to begin in 2021 and will enable drivers and passengers to directly use Google Maps from the vehicle, run automotive apps from the Google Play store and use the voice-controlled audio assistant to answer texts and calls, find information and manage different functions within the vehicle. These services will be integrated with the Alliance Intelligent Cloud."

After the Windows Automotive and Connected Car Platform the company Microsoft followed us once again with its Connected Vehicle Platform.
But somehow, we are wondering why it is not mentioned in its related press release.

Our

have become the standards in the vehicles industry as well, as can also be seen with the collaboration of for example Microsoft and the company Porsche→Volkswagen formed for exactly the same reasons and noted on the 26th of February 2019, which grants us several legal rights besides the copyright.
Because we have started one more revolution and set more worldwide standards in the fields of transportation and mobility as well as other fields with these original and unique, iconic works of us, proper licensing of any reproduction and performance of them in accordance with the License Model (LM) of our Society for Ontological Performance and Reproduction (SOPR) is required for various reasons.

Please keep in mind that the

(see also the note More evidences Volkswagen mimicking C.S. and C.S. GmbH of the 5th of March 2019).
Please keep in mind the general provisions of our SOPR, that are demanding

from everybody participating for establishing the guiding principles of our SOPR, that are guaranteeing

for everybody participating.

24.March.2019
Picture of the Day
Hungarian Parliament Building, Budapest, Hungary

©© BY-SA 4.0 Godot13, cropped by C.S.

We took the Hungarian Parliament Building as a blueprint for the Palazzo Stroeti, which covers around a fifth part of the whole complex area, which again is planned at a location in the Veneto region of Italy and with a museum and areas for entertainment, dining, and related activities.
For sure, the architecture has been reworked by adjusting the Gothic style in a way that is more typical for this region (see for example the Palazzo Ducale in Venezia). Other buildings including the Galleria have architectures in the neo-classic Palladian style also typical for this region as well as C.S.' style.

25.March.2019

21:02 UTC+1
Further steps

We are finalizing the investigation of Kubernetes (see the Investigations::Multimedia of the 16th of March 2019).
Some results were already given in the issue SOPR #170 of the 19th of March 2019.
Another result is that our Castle in the Cloud and Managed Peer-to-Peer (MP2P) projects are also an origin of the system evolution. Very important to note in this respect is the point that we have begun the discussion about data privacy and ownership in relation to cloud computing with them even at a time when there was nothing hybrid in relation to virtualization, public and privat cloud computing platforms, microservices, and so on, which means that these projects are parts of our original and unqiue work of art titled Ontologic System and not merely technical ideas and concepts.
Some more outcomes will be given in the next days.

26.March.2019

11:00, 12:40, and 20:28 UTC+1
Further steps

In relation to the Investigations::Multimedia of the 16th of March 2019 we can already confirm our allegations that Kubernetes is a copyright infringement (see related section of the Website update of the 8th and 9th of March 2019) and therefore everything related, specifically

is a copyright infringement as well and in virtually all cases known to us even an evidence for an illegal agreement and an illegal collaboration, as also proven with the related open standards and foundations realized by the same responsible entities as well.
Only some very few details about the cluster manager Borg are left for explanation, but only if Google's explanations are not all correct, though Borg taken alone is virtually irrelevant, because we have learned that it is fundamentally different in comparison to Kubernetes. We even got the impression that only some tools existed in 2005 and we known that Chubby existed in 2006, which were later also utilized for Borg, while Borg itself was only in development since the mid of the year 2006, if at all, and ready in 2007 because Google did not know in 2006 what to steal from us.
Prior art does not help here either, because some elements did not exist at all when they were publicated or their authors have not described and discussed the relevant aspects.
In addition, many more features of our Ontologic System are still missing.

Therefore, the whole strategy of all data center and cloud providers is imploded. Oh!
A repetition of the Android, iPhone, Artificial Intelligence (AI), Mixed Relatiy (MR), Autonomous Vehicle (AV), and other scandals will not happen, definitely.

27.March.2019

20:00 and 22:10 UTC+1
Further steps

Somehow we have overlooked that we already showed the copyright infringement of the company Google and others with the Kubernetes application, engine, or platform in the case of the Investigations::Multimedia of the 11th of December 2018.
Simply take a look at the

Also recall that Java is based on the Remote Method Invocation (RMI) protocol, which is the object-oriented programming analog of the Remote Procedure Call (RPC) protocol.

Borg was not ready in 2006 and in fact an attempt to steal the part of our works of art titled Ontologic System (OS), that is based on our integration of the basic properties of the

Furthermore, like in the case of the companies Hewlett-Packard and 1060 Research, we have in the case of the company Google also an echo of espionage.

08:33 UTC+1
SOPR #172

*** Proof-reading mode ***
Our latest informations in relation to Ontologic Networking has resulted in continuations or new developments by (designated and already virtual) members of our Society for Ontological Performance and Reproduction (SOPR). Correspondingly, we discuss some of the related topics:

Registries of items
A technology (i.e. system, platform), product (i.e. device, application, vehicle), or service, that

• based on,
• connected with,
• linked into, or
• operated inside

  our Ontologic System (OS) with its

• Ontologic System Architecture (OSA),
• Ontologic System Components (OSC),
• Ontoscope Components (OsC), and
• Ontologic Applications and Ontologic Services (OAOS),

and

is considered as a meta-technology (i.e. meta-system, meta-platform), meta-product (i.e. meta-device, meta-application, meta-vehicle), or meta-service (i.e. service to provide services) respectively.
This option was added for all members of our SOPR, that

In all cases, choosing this option

Once again, the reasons for this and other provisions are that we provide for example

for everybody participating.
Therefore, another superordinate or higher alliance, ecosystem, or whatsoever is not needed.

Hardware royalties
Because we

we decided at first to take only very low fees for the reproduction of our OSC and our OsC for the construction and operation of an independent OS respectively access device or access point, if at all.
But some entities might structure their businesses accordingly, specifically manufacturers of microchips and embedded systems, which members of our SOPR might view as unfair.
One option would be to also ask for a share of 5 to 10% of the overall revenue generated with the hardware of Information and Communication Technology (ICT) utilized for performing OAOS, though we already thought about this more than a year ago as well.

Legal matter
We have extended the Articles of Association (AoA) and the Terms of Service (ToS) with the License Model (LM) to reflect the matter discussed in the sections above.

We also would like to recall that computing and networking are already overlapping and still converging due to our singularity.

12:16, 20:00, and 23:25 UTC+1
More evidences Volkswagen and Amazon mimicking C.S. and C.S. GmbH

*** Work in progress ***
We quote a first report publicated by a public-law broadcaster: "[...] Volkswagen builts an own cloud together with the US digital company Amazon. The carmaker wants to increase the productivity of its manufacturing plants by storing and networking of its data in the Internet. Both companies announced a multi-year cooperation.
[...]
VW wants to aggregate the data of all the machines, plants and systems out of all 122 factories in a "[Volkswagen] Industrial Cloud". This would help to optimize procedures and processes in the assembly. [...]
Everything should be digitalized
With the installation of the cloud VW forms the basis for a consistent digitalization of its manufacturing and logistics.
[...]

Platform should be opened
In the long term, the more than 1500 suppliers and partner companies of VW should also be integrated in the cloud. Until now, their systems differ in parts from site to site. In the future, the new cloud service should also be accessible for other automakers. VW spoke of a "continously growing, worldwide industrial ecosystem". Negotiations with large industrial companies are already going on."

From a second report we got the following additional informations: "IoT and cloud computing: AWS and Volkswagen have a grand plan to connect up factories
Industrial Internet of Things and cloud project will link up 30,000 sites and 1,500 suppliers.
[...]
The aims of the project are to increase plant efficiency and uptime, improve production flexibility, and increase vehicle quality.
[...]
[Volkswagen] will also build a company-wide data lake built on Amazon S3 to analyse the data, so that the car giant can improve forecasting, and streamline operations by identifying gaps in production and waste.
[...]
Volkswagen will also use Amazon [... Problem Solving Environment (PSE)] service which allows data scientists to build, train, and deploy machine-learning models quickly, to optimise the operation of machinery and equipment in all of its plants."

Hopefully, it is obvious that we have here a reproduction of our Ontologic System, as can be easily seen with the Distributed System (DS) consisting of a

• Industrial Internet of Things (IIoT) (2012) and
• Industry 4.0 (2011),

utilized for its new production infrastructure around the world, which is being linked together via

• Artificial Intelligence (AI),
• Machine Learning (ML), and
• Computer Vision (CV),

Depending on how the DS is built, what is manufactured, and how it is manufactured different fees and shares are due as royalties.
Connecting the suppliers and partners of Volkswagen's global supply chain makes it a meta-platform.
Opening the industrial cloud to other entities makes it a meta-platform.
We do not think that the industrial ecosystem of Volkwagen and other large industrial companies is a good idea, because the reasons for this rejection and other provisions are that we provide for example

and also our

for everybody participating.
Therefore, another superordinate or higher alliance, ecosystem, or whatsoever is not needed.

All or nothing at all. Now and not in the future.
We will not make any further concessions.

28.March.2019

14:03 UTC+1
More evidences Nvidia mimicking C.S. and C.S. GmbH

*** Work in progress ***
The company Nvidia is

• SoftBionics (SB),
• High Performance and High Productivity Computing (HP²C),
• high-performance networking,
• video gaming,

and

• online gaming and
• grid computing or cloud computing.

In relation to Nividia's and others infringing activities in the field of SB we got the following informations from a first report: "Dell EMC and Nvidia said a reference design for artificial intelligence workloads is now available and part of a portfolio of converged systems designed for machine learning and scaling next-gen workloads.
[...]
AI is becoming a critical workload for enterprises and storage giants are rolling out building blocks to build out machine learning and AI workloads. The Dell EMC-Nvidia system will be offered through Dell partners [...].
Other storage vendors ranging from NetApp to Pure Storage to IBM and HPE are all targeting AI workloads as well as working with frameworks such as TensorFlow and Pytorch."

From a second report related to the same matter we also got the following informations: "Pure Storage, Nvidia, Cisco launch AI hyperscale systems
[...] systems for artificial intelligence and machine learning workloads.
[...] it has combined its AIRI artificial intelligence platform with Nvidia's DGX-1 and DGX-2 hyperscale systems and rolled out a new FlashStack for AI with Cisco and Nvidia.
The effort highlights how storage players are lining up with Nvidia to create hyperscale systems designed for [Artificial Intelligence (]AI[)] and [M]achine [L]earning [(ML)]. Last week [(see quote before)], Dell EMC said its system in collaboration with Nvidia was available.
[...]
Both systems work with Nvidia's [Nvidia GPU Cloud (]NGC[)] software container registry and various machine learning frameworks as well as Kubernetes. Pure Storage cited Taiwan's Linkou Chang Gung Memorial Hospital, the main branch of the Chang Gung Memorial Healthcare System, and German non-profit UnternehmerTUM [of the Technical University Munich (TUM)], an AI innovation incubator, as customers."

Btw.: We will estimate the royalties that entities like TUM and UnternehmerTUM have to pay.

In relation to its and others infringing activities in the field of SB and Nividia's GeForce Now service we got the following informations from a third report: "Nvidia unwraps [...] hardware and cloud instances
GPU giant unveils new CUDA-X label for its software stack.
Nvidia has taken the wraps off its next iteration of workstations for data scientists and users interested in machine learning, with a reference design featuring a pair of Quadro [...] GPUs.
[...]
Signed up to provide the new, beefier workstations are Dell, HP, and Lenovo.
On the server side, the company unveiled its [...] blade server, which can pack 40 GPUs into an 8U space, and is labelled as a [...] Server Pod when combined with 31 other [...] blade servers. All up, the [...] Server [Pod] has 1,280 GPUs. The storage and networking backbone of the blade servers are provided by [a subsidiary].
Speaking during his keynote, CEO Jensen Huang said Pods would be used to support the company's GeForce Now service, to which [the telecommunications service providers (telcos)] SoftBank and LG Uplus were announced as members of the GeForce Now Alliance, and its upcoming Omniverse collaboration product that Huang described as Google Docs for movie studios.
[...] GPUs are being offered by Cisco, Dell EMC, Fujitsu, HPE, and Lenovo in machines that have been certified as Nvidia GPU Cloud-ready - an award Nvidia launched in November that shows "demonstrated ability to excel in a full range of accelerated workloads", and are able to run containers put together by Nvidia for certain workloads.
"The rapid adoption of [a GPU] on the world's most popular business servers signals the start of a new modern era in enterprise computing - one in which GPU acceleration has become standard," Nvidia vice president and general manager of Accelerated Computing Ian Buck said.
In the cloud, users of Amazon Web Services (AWS) will soon be able to make use of Nvidia [...] GPUs [...]. AWS users will also be able to make use of [GPU]s with Amazon Elastic Container Service for Kubernetes.
[...]
At the same time, Nvidia is repackaging its software stack and libraries to fall under the CUDA-X moniker, including RAPIDS, cuDNN, cuML, and TensorRT.
Finally, Google Cloud ML and Microsoft Azure Machine Learning have integrated RAPIDS [...]."

A fabricated report: "Nvidia looking to surf data science wave into the data center
As enterprises shift to distributed forms of computing, Nvidia hopes to slide into the datacentre.
[...]
The company that started out making graphics chips, and to uninformed observers would have appeared to be making a weird deviation in the world of artificial intelligence, is now bringing it all back together as graphics and AI merge.
[...]
The state of the art is at such a point that the company believes it can claim to create photo-realistic images from sketches, which, besides a few boundary issues with different elements, looked realistic enough.
Inferring by AI is also being used to add ray tracing into Quake II.
"We are doing a lot of work in AI-inferred image generation. It is unquestionably the future," Nvidia CEO Jensen Huang told [...] on Tuesday.
[...]
Nvidia believes that data science and the use of neural networks needs to make use of the massively parallel hardware it offers, and that the days of being able to get away with CPU-run neural networks are fading fast.
[...]
"What we are seeing now is that the networks that people are deploying can no longer run on CPUs."
[...]
"So that's the shift that we are seeing, the [neural] networks are not able to run on the CPUs to get the accuracy or latency requirements."
During the week, the company announced that [...] GPUs are being offered in Nvidia-certified servers from Cisco, Dell EMC, Fujitsu, HPE, and Lenovo [(see the quoted report above)]. But for Buck, the addition of a GPU into a standard enterprise server is merely the first step into the larger world of distributed computing, and to get its potential customers there, the data scientist is key.
[...]
"I think distributed data analytics and data science is the big next chapter for the enterprise, and one technical barrier might be turning the corner on the networking. [...]"
Nvidia's [...] purchase of Mellanox should signal how seriously the company is taking its push into the datacentre. It already had its own compute stack, and should the purchase gain approval, will add networking and interconnects to its bag.
When discussing the purchase, Huang pointed to the increase of east-west traffic in the datacentre due to technologies like containers and neural networks, as well as the size of data being analysed.
"Both of these conditions cause the network to be the bottleneck, both conditions, and during that time when Moore's law is slowing down, the software stack, the networking software stack, has to be moved onto the fabric as much as possible," the Nvidia CEO said.
"The CPU is now too rare a resource, so you have to offload any work that you can, and Mellanox is world class at CPU offloading, they take the entire stack of networking and they run it on the smart [Network Interface Controller(]NIC[)].
"In the future, more and more and more of that will happen, so the network is going to become intelligent."
According to Huang us, the computing fabric will extend beyond the node and into the network.
"The whole thing is going to be one large computer," he we said.
At the same time as it is trying to get enterprises at the bottom end of the market onto GPUs, Nvidia is offering 1,280 GPU RTX Server Pods. The sort of machine that is being pitched at telcos to allow them to offer services like GeForce Now. SoftBank in Japan and Korea's LG Uplus are already signed up for Pods.
From above and below, Nvidia is determined to find a way into the datacentre."]

A fabricated report about our Ontologic System (OS) and its Ontologic System Components (OSC) OntoBot, OntoScope, OntoNet, etc. provides us the following informations: "Video games meet enterprise technology, business: The intersection blurs more
Developments originally intended for the video game industry are now having an impact on the cloud, AI, data science, and autonomous vehicles. It makes you wonder if Epic's Unreal Engine can move beyond games.
The infrastructure behind the video game industry is increasingly leading to new enterprise technology and business use cases to the point where you'll have to pay attention to both to connect the dots for the future.
In a week in which the Game Developers Forum [(GDF) ...] and Nvidia's GPU Technology Conference (GTC) were happening at the same time, the overlap between the enterprise and gaming were hard to ignore. Nvidia and its graphics processors and subsequent ecosystem of developers focused on [A]rtificial [I]ntelligence [(AI)], Machine [L]earning [(ML)] and [H]igh-[P]erformance [C]omputing [(HPC)] were a common thread between the two events.
Nvidia is a big driver behind this intersection of video games and the enterprise. CEO Jensen Huang outlined Nvidia's strategy during the company's analyst meeting. Huang's comments related to how Nvidia got into the data center game - even more so since the company bought [a company]. Let's look at Huang's [C.S.' and our] approach:
"No longer was it sufficient to just accelerate graphics. We had to first simulate the physics and then accelerate the graphics. Because you have to simulate the water. You have to simulate the leaves blowing into wind. You have to simulate things, particle physics, as buildings crumbled. And so it was impossible to have animated all of that. We decided to simulate that. So we expanded the aperture of our accelerator, and we invented this idea, called CUDA, so that we could expand not just accelerating graphics, but the domain of [V]irtual [R]eality [(VR)]. About that time, when we transitioned from a graphics accelerator to a domain accelerator, we became an accelerated computing company. An accelerator accelerates a function. An accelerated computing platform accelerates a domain of applications."
From an approach that worked for graphics and video games, Nvidia is leveraging its software, GPUs, and stack to:

Huang [C.S. and we] said:
"Cities of the future, factories of the future, buildings of the future will have three characteristics. The first characteristic is tons of sensors. The second characteristic? A bunch of computation at the edge - basically, the reflexes of that robotic city. It doesn't have to go to a cognitive brain in the cloud. And then, third: Connected to a cognitive brain in the cloud. Those three characteristics are so that you can make decisions and plan."

Huang [C.S. and we] said:
"And the reason for that is this ... Data science is the only high-performance computing problem we know where there's millions of people. Millions of people in different fields of science, healthcare, financial services - they call them quants, insurance companies, retail, logistics, travel. You name it. Every single industry will benefit from data science."
[...]
Jeffery Fisher, executive vice president Nvidia, told analysts that Nvidia has developed a server that's optimized for cloud gaming. "We'll sell a complete server. And on top of that, we will run our GeForce Now service, license to telcos, share revenue as this scales out. This gives us the opportunity to hit markets that we don't currently address. And it gives telcos the opportunity to bring in more value-added customers into their ecosystem," said Fisher.
While Nvidia is the most upfront about its plans and the intersection of gaming and business, there are signs that other technology vendors are seeing the crossover, too.
At GDC, the other notable news was that Epic is launching its Unreal Engine 4, the top game engine for video games. Epic also happens to be the company behind Fortnite, which runs on Amazon Web Services, and has 250 million users. Fortnite to the Unreal Engine is what Amazon's e-commerce business is to AWS: A scalable business that yields technology that can target other markets.
Epic has 7.5 million licensees for its Unreal Engine and an army of developers. CEO Tim Sweeney said that Epic's success is linked to developer success. What Epic has with its Unreal Engine is a huge platform.
Unreal Engine 4.22 ships with ray tracing, hot reload for live coding, multi-user collaboration in Unreal Editor, support for Microsoft HoloLens streaming, and Google's Stradia game platform.
Sweeney hasn't expanded beyond the gaming market, but you play this out, and it's clear the Unreal Engine could apply to businesses. Epic may want to take Nvidia's approach and look for those big unicorn markets. For Nvidia, data science is the next unicorn market. Epic has a massive video game industry, so it doesn't have to expand yet. But it does make you wonder what Epic could do elsewhere - say, human resources, collaboration or marketing.
[...]
Also on the gaming-meets-business front, Google outlined its Stadia cloud game streaming effort. Google is a bit late to the party, and Nvidia has been on the case for years. Selling RTX servers to telecoms may have cracked the code. But Google's approach is worth noting.
Stadia is designed to run on multiple screens, leverage Google Cloud Platform, and expand the gaming base of folks who don't have the best PC kit. The real win would be more browser-based gaming without the latency.
Google's Stadia is partnered with Nvidia rival AMD and has industry support.
Now, it's unclear whether Stadia is going to get the gaming hits that put it on the map, but that cynicism may miss the point. If Stadia can seamlessly stream video games across multiple screens, perhaps the real play is streaming analytics, collaboration, or something new entirely."

For our fans and readers, who are not experts in the field of computers and computer networks, we would like to give the additional explanations of an online encyclopedia about Nvidia GRID and Nvidia GeForce Now.
"Nvidia GRID is a family of graphic processing units (GPU) made by Nvidia, introduced in 2008, that is targeted specifically towards cloud gaming.[1] The Nvidia GRID includes both graphics processing and video encoding into a single device which is able to decrease the input to display latency of cloud base video game streaming.[2] Nvidia offer their own game streaming service that makes use of the Nvidia Grid that supports full 1080p at 60 frames per second over the Internet.[3]
While GPUs, and Nvidia in particular, are generally considered mainly for video games, there has been a recent growth of business applications that are GPU-accelerated. The Nvidia GRID K1 and K2 are being integrated with [...] server clusters for use with 3D-intensive applications such as graphics and computer aided drafting (CAD).[4] In 2015, Microsoft began including Nvidia GRID as part of its Azure Enterprise cloud platform for businesses, such as engineers and designers, to make use of.[5]"

"GeForce Now is a brand used by three cloud gaming services offered by Nvidia. The Nvidia Shield version of GeForce Now, formerly known as Nvidia GRID, launched in beta in 2013, with Nvidia officially unveiling its name on September 30, 2015. The service is a subscription-based offering that allows users unlimited access to a library of games hosted on Nvidia servers for the life of the subscription, delivered to subscribers through streaming video.
[...]
In January 2017, Nvidia unveiled a separate cloud gaming service for PC and Macintosh computers also branded as GeForce Now. It is a remote desktop provider in which users can rent access to a virtual computer, where they can install their existing PC games from existing digital distribution platforms, and play them remotely. As with the Shield version, the virtual desktop is streamed from Nvidia servers.
[...]
GeForce Now consists of a network of servers based in data centers in North America, and Europe that host and serve the GeForce Now game library to members in those regions.[3] The servers utilize Nvidia Tesla graphics cards [...].
[...]
At Consumer Electronics Show in January 2017, Nvidia announced a version of GeForce Now for PC and Macintosh computers. Unlike the version for Nvidia Shield (which Nvidia promoted as being similar to Netflix),[4] this is a separate offering in which users can rent access to a remote desktop with access to a Windows environment with GeForce GTX graphics. Users can install digital distribution clients such as Steam and Origin onto the remote desktop to download and run purchased or free-to-play games as they would locally. The service is sold per-minute of play time using blocks of service credits; two price tiers are available, with GTX 1060 and GTX 1080-class performance respectively. Nvidia aimed this service towards users who want to play their own purchased games on computers that are not compatible with them, such as laptops and computers with low-end capabilities.[7][8][9]
Nvidia had announced a planned beta of the service in March 2017, but it was silently cancelled. In an earnings report in May 2017, Nvidia CEO Jen-Hsun Huang revealed that a beta would be held "soon", but that the company was "still years away from being able to find the right balance between cost and quality of service and the pervasiveness of virtualizing a gaming PC."[10] In late October 2017, Nvidia launched a free and open beta of the service limited to the Macintosh platform for English users in North America and Europe.[11][12] In January 2018 Nvidia added PCs to the Nvidia GeForce Now service.[13]"

Note that all references given in relation to Nvidia GRID are dated between the years 2013 and 2015, which does not correspond with the alleged introduction date of Nvidia GRID but does correspond with the introduction date of GeForce Now in the Nvidia Shield version, formerly known as Nvidia GRID.

The official introduction of the parallel computing platform based on General-Purpose computing on Graphics Processing Units (GPGPUs) and called CUDA was the 23rd of June 2007. Honestly, we only know CUDA as a parallel computing platform based on GPGPUs, which might be used in the field of VR, but actually we are unable to remember having read something about this specific utilization. That statement of Nvidia's CEO is even not conclusive because VR demands very much amounts of graphics processing and not general purpose computing. The fact seems to be that we expanded VR in this way, as can be seen with for example the related list points of the Feature-List #1 of our OS.
And when the CEO begins to talk in such a way, then we do know how to interpret his statements and Nvidia's latest activities.

We do not think that the GeForce Now Alliance of Nvidia and other large industrial companies is a good idea, because

have already shown that our OS with its Ontologic System Architecture (OSA), Ontologic System Components (OSC), and Ontologic Applications and Ontologic Services (OAOS) is the industry standard in these fields as well and the reasons for this rejection and other provisions are that we provide for example

and also our

for everybody participating.
Therefore, another superordinate or higher alliance, ecosystem, or whatsoever is not needed.

For sure, this matter is very critical and will be handled by us rigorously because it is related to our Caliber/Calibre and Ontologic uniVerse (OV), and also with our Ontologic Net (ON) and Ontologic Web (OW), as well as the infrastructure, platforms, applications, and services of our Society for Ontological Performance and Reproduction (SOPR).

All or nothing at all. Now and not in the future.
We will not make any further concessions.

29.March.2019

11:27 UTC+1
Clarification

*** Work in progress - some better order and wording ***
The Information Technology (IT) circus went a full circle over the fields of

only to arrive at our Evolutionary operating system (Evoos) and our Ontologic System (OS).

In this relation, we made the observations of

• utilizing in practice,
• disturbing others, and
• avoiding causal links,

We discussed that strategy listed in the first point with Google and Amazon in relation to

in the past already, but the same strategy was also applied with

For sure, that strategy was applied in relation to our Evolutionary operating system (Evoos), our Ontologic System (OS), and our Ontoscope (Os) as well, as not expected otherwise by us around 13 years ago.
But eventually, that strategy and the whole house of cards imploded recently, as never expected otherwise.
By the way: This is not the case with our application of that strategy in relation to

In the end, the whole IT circus is back at the start with

But that is all included in our OS since its start, which implies that the whole circus is at our OS or better said in our OS.

This conclusion is reaching far beyond technical issues.
The (pioneering) activities and achievements of other companies in the field of cloud computing were one of the main arguments when we were

But in the last days we had to learn that this argument or lever of external entities did not, does not, and will not exist at all, which also leads to other considerations in relation to legal issues.

Another main argument or consideration was that external entities get the allowance to transfer their businesses to our OS and our Os on the basis of our Ontologic System Components (OSC), Ontoscope Components (OsC), and Ontologic Applications and Ontologic Services (OAOS). But what we observe is that they focus on the growth of their businesses in a way that reflects and hence disturbs the growth of our corporation.

Ontonics Further steps
We are thinking about the production of the first 133,333 autonomous paletts and movers, or 33,333 autonomous drones, or both for the transportation of people and goods in public areas.

Think bigger.