• operating system and cloud computing services [in the one case ...] and
• online shop and cloud computing services [in the other case ...]."

We also made a short review in relation to the following keywords and main fields:

• Layer 4: Transport layer
• Layer 3: Network layer
• Layer 2: Data link layer

• "CAS provider is a Distributed Hash Table" (DHT),
• Content Addressable Storage Performance Enhancement by Recipe (CASPER) based on Coda,
• Content Addressable Parallel File System (CAPFS),
• Cooperative File System (CFS) read-only DHT based on Chord layer for lookup, DHash layer for block storage, and Self-certifying FileSystem (SFS),
• Ceph Distributed File System (DFS) based on Controlled Replication Under Scalable Hashing (CRUSH) object-based store,
• etc.,

• Content-Centric Networking (CCN) (2007)/Named Data Neworking (NDN) (2010),
  superset of Node-to-Node (N2N),
• Named Function Networking (NFN) or Named Service Access Point Networking (NSAPN) ("extends the CCN/NDN" respectively classic ICN),
  "A gradual spectrum - complementary [] stupid networks [(e.g. Internet)] - CCN - "domesticated NFN" - lambda calculus"
  "Braden/Faber/Handly, "Role-based architecture", Hotnets 2002): provides header space for more than one "network function"
  • [graphic: NFN started on top of NDN and both might change positions] Once you make these "namable", NFN becomes the core
  • ICN as assembly of several "engines":
    - name space/expr [expression] engine (CCN style, pub/sub [publish-subscribe], [Network] Datalog [(NDlog)], lambda expr)
    - forwarder engine, policy engine, charging engine"
• Publish-Subscribe Internet Routing Paradigm (PSIRP) and PUblish-SUbscribe Internet Technologies (PURSUIT),
• Service-Centric Networking (SCN)

As we said in the related notes and messages in February and March 2019, most of Centric/Named and Semantic networking is an OntoClone. For example,

Eventually, we have essential parts of our Ontologic System Architecture (OSA) and Ontologic System Components (OSC), which goes beyond OO 1, Grid Computing (GC or GridC), Peer-to-Peer Computing (P2PC), and so on. But we did not stop at this point.

AM, BB, CAM, Centric/Named, Semantic, etc. are not sufficient, but are already in our OS, and missing is an overall system architecture, which is also already in our Ontologic System (OS) with its integrating Ontologic System Architecture (OSA), obviously (see also the Ontologic Net Further steps #1 of the 18th of February 2019 once again).

We also have

• Problem Solving Environment (PSE),
• Virtual Environment (VE)
  • Distributed Virtual Environment (DVE) or Networked Virtual Environment (NVE)
    • Massively Multiuser Virtual Environment (MMVE)
      • Multiplayer Online Game (MOG) (see also Voronoi Overlay Network (VON)-based Application-layer Spatial Publish Subscribe (SPS) with Topology-awareness (VAST) and self-organization in Adaptive Scalable Cooperative Environment for Networked Virtual Environment (NVE) Developments (ASCEND) in the OntoLix and OntoLinux Website update of the 12th of March 2019) and
      • Massively Multiplayer Online Role Playing Game (MMORPG),
    • Collaborative Virtual Environment (CVE), and
    • 3-Dimensional Virtual Environment (3DVE),

  and also

• other types of environment,

In the course of the review ... in the Further steps of the 29th of October 2022 ...

Problems or detail questions, focuses, fine tunes
homogeneous, which means holonic and liquid overall architecture, which is true to our OSA
requirements for different OAOS, including informations and communications, environments, real-time systems (e.g. traffic, robotics), ...
requirements for different

• Problem Solving Environment (PSE),
• Virtual Environment (VE)
  • Distributed Virtual Environment (DVE) or Networked Virtual Environment (NVE),
    • Massively Multiuser Virtual Environment (MMVE)
      • Multiplayer Online Game (MOG) and
      • Massively Multiplayer Online Role Playing Game (MMORPG),
  • Collaborative Virtual Environment (CVE), and
  • 3-Dimensional Virtual Environment (3DVE),
• (information) spaces, environments, worlds, and universes respectively realities
  • Virtual Reality Environment (VRE),
  • Augmented Reality Environment (ARE), and
  • Mixed Reality Environment (MRE),

  and also

• other types of environment,

The seamless integration with the legacy Interconnected network (Internet), World Wide Web (WWW), and Virtual Environment (VE) and the migration from them to our ON, OW, and OV, including our

are easily possible.

Talk to the Matter
Talk to the Machine
Talk to the Net
Talk to the Web
Talk to the Universe
Talk to us

By the way:

08.November.2022

06:44 UTC+2
Ontonics Further steps

We are also considering to demand the same like in the case of modules in the fields of Network System (NetS) and Geographic Information System (GIS) (see the message Ontonics Further steps of the 1st of August 2022 for more information) for more parts of the production of mobile goods (e.g. devices (hand-held, wrist-worn, and head-mounted Ontoscopes, intelliTablets, laptops and notebooks), automobiles, drones, robots, etc.) based on our Ontoscope (Os).

01:33 and 14:22 UTC+1
Further steps, Ontologic Net Further steps, and SOPR

*** Work in progress ***
So, we are back into the hotspot after looking at what we did since the year 1998 and described and explained in more detail throughout the following years, specifically since the end of October 2006 and since the year 2019.

Actually, we are looking in some more detail at the mess, or better said next frauds and serious crimes, related to the field of Information-Centric Networking (ICN), including the subfields of

also wrongly called Future Internet, New Generation Network (NGN), and so on by others, and plagiarisms and OntoClones by us. Too many actors are convinced that democracy is just only another manifestation of anarchy. In this sense, we do agree to disagree.
We are also looking at some more detail at DVE or NVE architectures to iron out the last wrinkles, cure minor deficits, and improve where possible respectively to conduct usual evolutionary system development after our revolutionary creations around 1998 to 2005.

Howsoever, we feel that we have reached the point where our OS truly begins to materialize and that only some very few decisions or determinations regarding a common base or standard, or even only the realization respectively implementation of it are missing.
In more technical details, it is about

In this relation, we already said that our approach regarding creation, development, implementation, deployment, operation, maintenance, and migration is seamless. In fact, by having the Society for Ontological Performance and Reproduction (SOPR) data centers on-premise of Ontologic Services Providers (OAOSPs), we can experiment with the prototype and subsequent versions, and improve the soft parts, but also can do so with the hard parts (e.g. processors and routers) without disturbing the daily operation of the existing Internet and World Wide Web (WWW), and the already existing parts of our Ontologic System, also wrongly called Web Services (WS), Grid Computing (GC or GridC), and Cloud, Edge, and Fog Computing and Networking (CEFCN).
Please keep in mind that we have a handle on the modules in the fields of Network System (NetS) and Geographic Information System (GIS) (see the message Ontonics Further of the 1st of August 2022 for more information) and therefore we will not tolerate any oversmart hardware manufacturers in the U.S.America, P.R.China, European Union, or elsewhere.
Also keep in mind that this new network hardware is installed in the facilities of the infrastructures of our SOPR and that we announced to award contracts to Main Contractors (MCs) through public tenders.
In short, no circumventions and infringements of the rights and properties of C.S. and our corporation here, too.

Most potentially, we already provided a related Teaching, Suggestion, Motivation (TSM).
When looking at the partial OntoClones, called Content-Centric Networking (CCN), Information-Centric Networking (ICN), Service-Centric Networking (SCN), Named Data Networking (NDN), Named Function Networking (NFN), and so on, then we always note that the locations of things or objects, including raw signals and data, informations, knowledge, and other contents, functions, applications, services, devices, actors, agents, and users sooner or later play an important role. But we already

On this basis, we simply exploit this highly valuable and freely available facts respectively informations about the space and time just by design of our Ontologic System (OS). See also for example the field of (decentralized or distributed) Network Coordinate System (NCS).
And because we are talking about existence and ontology all the time, we also have the unambiguous and unforgeable IDentity of items in this observable Universe, as explained elsewhere on this website of OntomaX and on the websites of OntoLinux and OntoLix in more detail.

The successor of the Internet Protocol (IP) address or number is the four-dimensional (4D) designation in space and time:

of a

and all the other things

accordingly.

The successor of the World Wide Web (WWW) domain is a real name:

There is no need for

But for sure, a domain respectively name and address can include such designators, prefixes, and slashes, if they are useful.

Space-driven is based on

partitionings, disjoint sets, non-overlapping regions, grids, tilings, tessellations, spatial indices, etc. (e.g. hexagonal (e.g. Geodesic Grid (ISEA3H)), square, triangle, quadtree, Voronoi, Delanauy, Universal Transverse Mercator (UTM), ISO 6709, Military Grid Reference System (MGRS), Global Area Reference System (GARS), etc.) of sets, structures, surfaces, spaces, etc., as required by individual Ontologic Applications and Ontologic Services (OAOS).
"Uniformity of shape and regularity of metrics provide better [partition or] grid-indexing algorithms."
If we remember correctly, we already mentioned that these additional informations are advantageously, because they do not have to be established by probing, gathering informations in the background, and so on, and provide many possibilies and applications (e.g. traffic management, self-driving cars, virtual personal guard in real environments, and so on).

Data-driven is based on

networking.

Messaging, lookup, discovery, routing and forwarding, caching, replication, consistency, synchronization, orchestration, composition, and so on work accordingly.

Content-Addressable and Centric/Named and Semantic, and so on networking can be done in addition to the real and virtual IDentity.
{potentially better or even corrected explanation partially required} The reason for this order is that BlackBoard (BB) (e.g. Tuple Space (TS)) systems are examples for data-driven coordination models, and provide the most advantages with a central entity or master. This also holds in case of hardware networking devices (e.g. network router and network switch) with Content-Addressable Memory (CAM), which is an Associative Memory (AM) or Associatively-Addressable Memory (AAM), and is frequently used for the optimization and acceleration of Forwarding Information Base (FIB) and Routing Table (RT) operations, and also used in cache memory, as well as Content-Centric/Named Data Networking and Named Function Networking.

Indeed, one could implement a kernel-less network, but it is more expensive (e.g. latency) without providing a practical benefit (see also for example the quote of the document titled "Co-ordination in software agent systems" in the Clarification of the 13th of April 2022 (look for the first bold letters)). Client-Server (C-S), Master-Worker (M-W), and Point-to-Point (Po2Po) are more efficient than Peer-to-Peer (P2P), so that trade-offs have to be made to get the best of both, the centralized and decentralized approaches. Exactly the same holds for the fields of Object Request Broker (ORB), Distributed Virtual Environment (DVE) or Networked Virtual Environment (NVE), and all the other fields and their implementations and applications, including Java Jini and JavaSpaces, as shown by others in particular and us in general.
For example, Jini has to broker proxies for services, but not the services themselves to increase the efficiency of such a Tuple Space (TS) system, specifically by decreasing latency between resource or service providers or servers and related requesters or clients, actors, agents, and so on. The proxies are then used by them for direct or Po2Po communication. See also the note about the document "Using JavaSpaces to create adaptive distributed systems" in the OntoLix and OntoLinux Website update of the 10th of March 2019.
See also the second section and other related sections of the Further steps of the 6th of November 2022.

Speech, gesture, and emotion acts as multimodal input and output.
We also mentioned several times that we have ontologies and ontologics for everything, and the real and virtual machines and spirits do the rest for us.

Needless to say, other problems arise, such as privacy, security, and integrity of data. But our OS already has much more new features and functionalities to handle this. Governments, that do mass surveillance can do so and are doing so anyway with or without our OS and our allowance, though this is a different topic for debate.

Now, we have to do a lot of legal and organizational work at first.

09.November.2022

04:20 UTC+1
16 years of official start of OS

04:20, 06:00, and 28:20 UTC+1
Clarification

It is estimated by calculation that the observable Universe contains between 10^78 to 10^82 real atoms. That is not a big number, specifically for mathematicians, who work with prime numbers, informaticians, who work with cryptographic technologies, and computer scientists, who work with massive parallel computing systems.
C.S. has created and designed the Caliber/Calibre, the Ontologic System Architecture (OSA), and the topology of our Ontologic Net (ON) of our Ontologic System (OS) in such a way that every atom can be addressed and looked up with O(1) space or run time requirement or just around 82 to 86 steps and spatially and temporally simulated and handled as an Ontologic holon or Onton, also wrongly called digital twin, in our Ontologic Web (OW) and Ontologic Universe (OV), also wrongly called mirror world, in O(logk n) like an item or object in a Problem Solving Environment (PSE) or a Virtual Environment (VE), such as Distributed Virtual Environment (DVE) or Networked Virtual Environment (NVE), including Massively Multiuser Virtual Environment (MMVE), and Collaborative Virtual Environment (CVE).

Add (the limits of) the Planck units and the latest descriptions about black holes and wormholes, as well as a holographic cosmos based on our OS with our Caliber/Calibre, Theory of Everything (ToE), Twin Ion Engine Royal (TIE R) / LightSwift, and other creations, and not on the alleged recent findings of some scientists, and the whole world looks different.

But at this point the matter only begins to become complex with the fields of Physics, Chemistry, Biology, and Astronomy, and planets, stars, blackholes, molecules, proteins, cells, plants, living beings, etc., and their behaviour and interaction, and so on.

From cybernetical systems over mirror worlds and digital twins to Ontologic holons or Ontons.
From Physical Reality (PR) over Mixed Reality (MX) and eXtended Reality (XR) to New Reality (NR).

Welcome to the Ontoverse (Ov).

11.November.2022

10:55 UTC+1
Ontologic Net Further steps

We are looking at some details in the field of of Distributed System (DS) or Distributed Computing (DC), specifically the integration and scalability of

Actually, C.S. is simulating it in the head once again, but with some more technical details regarding routing and forwarding, to see how it swings and reasonates.

Potentially, we also have developed an improvement of the Luleå algorithm or even a new one, which is used for finding the longest prefix match, emulate the function of Content-Addressable Memory (CAM), which is utilized in networking devices to speed up Forwarding Information Base (IB) and Routing Table (RT) operations, and realizing more cost effective routers and switches without CAM.
We are also looking at new designs for CAM chips.

See also the OntoLix and OntoLinux Website update of the 20th of February 2019 for the work titled "SNAMP: Secure Namespace Mapping to Scale NDN Forwarding" and the Ontologic Net Further steps of the 23rd of February 2019, both in relation to the map-and-encap approach, which are used to keep the size of the FIB and RT under control.

14.November.2022

01:29, 09:25, and 13:45 UTC+1
Further steps, Ontologic Net Further steps

*** Work in progress ***
This is a continuation of the work mentioned in the

We concluded that we had some problems with the ICN respectively Centric/Named networking approach, but at first we have not noted it at all and recently we did not understand why. Maybe, we did not understand how they wanted to steal this part of our Ontologic System (OS) as well.

The point is that 2 different aspects have been mixed 2 times with

Indeed, the operation of a network is a business process of the Communication Service Provider (CSP), specifically in the field of as a Service capability and operational models (aaSx).
But to integrate all in one does not have to be realized in this way, because separation and integration are 2 options.

2 different aspects

This can be nicely observed with the comparison of the fields of

• "letting the network compose a data path that satisfies the needs of a high level user program", and
• transforming the Internet to what is wrongly called Grid, Cloud, Edge, and Fog Computing (GCEFC).

assignment to layers of a system stack
Application and Service-Oriented technologies (SOx)
Centric/Named networking, specifically NFN and SCN 2
AN, SDN, SDWAN

We had already attempts in the 1990s and 2000s with various paradigms, approaches, data-driven and process-oriented coordination models or mechanisms, and programming languages and frameworks with distributed scope, , and so on, such as

For example, JXTA already provides different P2P protocols defined as messages in eXtensible Markup Language (XML) and the work titled "Using JavaSpaces to create adaptive distributed systems" and based on Jini already provides a Protocol Agent for network protocols (see Figure 1).

In addition, hybrids of name resolution and name-based routing:
Arbitrary types of network and deployment paradigms are viewed as nodes connected to a Directed Acyclic Graph (DAG) and executed according to an overall routing and forwarding protocol.
"The best current practice to manage this growth in terms of data volume and devices is to employ application-layer overlays such as [content distribution networks (]CDNs[)], P2P applications, and M2M application platforms that cache content, provide location-independent access to data, and optimize its delivery. In principle, such platforms provide a service model of accessing named data objects (NDOs) (replicated web resources, M2M data in data centers) instead of a host-to-host packet delivery service model.
However, since this functionality resides in overlays only, the full potential of content distribution and M2M application platforms cannot be leveraged as the network is not aware of data requests and data transmissions, leading to: [several problems]."
SCN 2 tries to change this with an SAL between network layer and transport layer.

"There is a growing consensus in the recent literature that the central role of the IP address poorly fits the actual form of Internet usage. [...] users actually exploit the Internet in a content-centric way; indeed, they are not interested in knowing from "where" contents are provided, they are only interested in the fact that they can get "what" they want. Conversely, the underlying IP communication model is still address-centric (or host-centric); [...] Therefore, there is a mismatch between the content-centric usage model of the Internet and the address-centric service model offered by the IP layer."

"factoring out location dependence from the interaction of the user with information" does not mean factoring out location dependence from the interaction of the underlying network with information

But naming, discovering, and routing and forwarding are always required, besides the requirements to be as fast as possible and KISS.

To use the IP address respectively name resolution is not a bad idea as is the case to use data, information, or content address respectively name-based routing.
Staying true to our original and unique Ontologic System Architecture (OSA) means in general that "[t]he demand for not imposing static dependencies, or dependencies that arise in the design phase, among factors, captures the fact that natural selection will imply deprecating and dropping factors" and in particular

and also

as well as

by design.
For sure, this was also copied without referencing.
Howsoever, we have a functional prototype and a lot of improvements for our Wide Area Network (WAN) (parallel computing) cluster with Distributed Shared Memory (DSM) respectively virtual shared memory, shared knowledge, and communal knowledge in addition to message-based communication.

subsystems and platforms for the fabrics, and also other subsystems and platforms of the infrastructures of our SOPR (see the issue SOPR #327 of the 7th of June 2021)

Eventually, we are talking about the related vision and expression of idea, and also parts and components of our Ontologic System (OS).
The next step would be more Cluster Computing (CC or ClusterC) and a so-called Global Brain, or being more precise, our

anyway, if we would not already be there since many years.

This is the next serious copyright warning: We have not seen in true prior art and plagiarism such an architecture, topology, etc. in relation to our ON, also wrongly called Future Internet, New Generation Network (NGN) (e.g. Centric/Named networking), and so on, and even not in the field of Distributed Virtual Environment (DVE) or Networked Virtual Environment (NVE), and so on.
By the way: We will not accept that entities take our OS as source of inspiration and blueprint, copy our expression of idea, and even claim that our original and unique ArtWorks (AWs) and further Intellectual Properties (IPs) would be their vision, idea, creation, innovation, research and development, work, achievement, and so on. There is absolutely no legal certainty in everything related to networking, Distributed Computing (DC), etc., etc., etc., that is related to respectively based on our OS.

As is very well known, we came to the conclusion that the WAN supercomputer is the foundation to provide and integrate the other paradigms with it, like for example Grid Computing (GC or GridC), and Peer-to-Peer Computing (P2PC), Centric/Named networking, Reality Environment (RE), Problem Solving Environment, etc..

Ontologic Applications and Ontologic Services Providers (OAOSPs) have 2 options:

Main Contractors (MCs) should interconnect in accordance to the contractual terms.

"First, a naming scheme for services must be investigated. One potential solution is to structure and classify services hierarchically, as proposed in [10 [An Ontology-based Hierarchical Peer-to-Peer Global Service Discovery System]]. This hierarchy could be adopted as the naming scheme for services."
This is one of the many ontology-based solutions we have integrated in our OS.
By the way: Bingo!!! Do not ask us how many times we were allowed to call it in relation to Centric/Named networking, because of the many substantial and significant evidences, which show that our original and unique OS was taken as source of inspiration and blueprint without creating an own expression and hence a causal link to it.

In relation to DVE or NVE we have a similar situation regarding

• stateless and stateful services,
• events, and
• updates.

The common denominator of data, information, and content, and also interest is the messaging and the publish/subscribe paradigm, specifically Spatial Publish/Subscribe (SPS), if adding the aspect of location respectively the location to an actual ontology.
multicast

For example
Voronoi-based Overlay Network (VON)
"VAST: A Spatial Publish Subscribe Overlay for Massively Multiuser Virtual Environments"
"[... VON-based Application-layer SPS with Topology-awareness (]VAST[)], a generic P2P overlay that provides spatial publish/subscribe (SPS) services with layers to support different VE requirements."
"With SPS as a primitive, VE state management can be supported with two layers of SPS, one for event and another for updates dissemination (i.e., an event layer and an update layer)."
But we note at this point that spatial can also be used and mixed in different ways and in wrong ways.

Eventually, we have different types of Area of Interest (AoI) of all natural and artificil objects involved, which suggest individual layers, protocols, and managements.

In addition, location and mobility of code, device, and user, security, and communication.
here, data-centric, information-centric, and content-centric networking also show problems by design
"factoring out location dependence from the interaction of the user with information"

This leads back to communication, messaging, multicasting, etc.
At this point we begin to run in circles.

For sure, Centric/Named networking, including NFN and SCN, is already a copyright infringement, as is its integration into an operating system kernel and its integration with

• Datalog, specifically
  • Network Datalog (NDlog),

and based on our expression of idea of a liquid all-in-one OSA viewed as multiparadigmatic architecture, meta-architecture, and expressive architecture, which is based on trust, identity, and ontology, including the Zero Ontology, hypergraph, including Directed Acyclic Graph (DAG), architecture, modeling, and components, wrongly called expressive identity, principle, principle type, factor, and empty set by plagiarisms, for an evolvable and trustworthy (successor of the) Internet (see above once again) were also all copied without referencing.

By the way:

16.November.2022

12:23, 13:39, and 19:53 UTC+1
Further steps

While analyzing a document about the field of Service-Centric Networking (SCN) with Service Access Layer (SAL) between Layer 3 network layer and Layer 4 transport layer (SCN 2), we noted a reference to another plagiarism, which focuses on the Inter-Process Communication (IPC) and the basic properties of our OS of

as basis for the Internet and for what is wrongly called Future Internet, New Generation Network (NGN), and so on, and is the one of the relative aggressive and criminal attempts of computer science researchers at a university at the east coast of the U.S.America to steal this part of our Ontologic System (OS).
Unsurprisingly, the authors of the SCN 2 have not discussed this direction further, but simply pushed it away by merely mentioning that the position paper understandably does not present a detailed solution.
Howsoever, our original and unique expressions of ideas do not require a specific presentation to be protected by the copyright.

Obviously, that document about the IPC approach is a plagiarism as well, because IPC is operating system or kernel layer, and has been discussed in relation to our foundations of the fields of microService-Oriented Archticture (mSOA) and Resource-Oriented Computing (ROC) created, presented, performed, and discussed with our original and unique work of art also titled Evolutionary operating system (Evoos), and in case of a Distributed System (DS) we are directly in the field of Distributed operating system (Dos) anyway, like for example TUNES OS and Aperion (Apertos (Muse)), and at least another document in relation to our successor of the Internet, which we have called Ontologic Net (ON) for better understanding, is also a plagiarism written and publicated as part of an overall fraudulent or even serious criminal activity to mislead the public about the true origin of our OS with its ON (see also the related statements in the Further steps of the 14th of November 2022).

Indeed, the view that networking is IPC dates back to the year 1972 or even longer, but this statement was meant more generally and particularly not in relation to the

It is also nothing new in the field of High-Performance Computing (HPC), specifically parallel computing and cluster computing. The latter also points to the field of SCN based on the Object-Oriented (OO 1) paradigm (SCN 1), which again is also applied in the field of HPC since decades and related to our OS with its ON in the context discussed herein.
In this context, we would like to recall that we listed Problem Solving Environment (PSE) in the section Basic Properties of the webpage Overview of our OS OntoLinux and a PSE is based on the field of SuperComputing (SC or SupC), including

• Grid Computing (GC or GridC), and
• Wide Area Network (WAN) SuperComputing (WANSC) or Interconnected SuperComputing (ISC),

(see for example the feature of "'Cluster functionality" listed in the Feature-List #1 and note that our OS has these features by design besides Grid Computing (GC) and Peer-to-Peer Computing (P2PC) functionalities at least since its start in October 2006, though Evoos has some features since December 1999).

We even handle our ON, which is the successor of the Internet, also as a PSE besides as a DVE or NVE, and so on.

A plagiarism copied our related expression of idea and edited our presentation of the foundation and reflective, fractal, holonic, and liquid Ontologic System Architecture (OSA) based on graph, and ontology, as well as operating system by saying and claiming the following: "This position paper outlines a new network architecture, i.e., a style of construction that identifies the objects and how they relate. We do not specify particular protocol implementations or specific interfaces and policies."
This was not the first time that we were able to convict the same faculty of Computer Science at that university and other universities.

The whole matter becomes even more interesting and nasty somehow with the existence and support of a programming language by an institute of technology in the same town at the east coast and also several federal agencies of the U.S.America, because this programming language reflects some of the basic properties of our OS.

We quote an online encyclopedia about this specific subject: "[The programming language] is a high-level, dynamic programming language. Its features are well suited for numerical analysis and computational science.[25][26][27][28]
Distinctive aspects of [the programming language]'s design include a type system with parametric polymorphism in a dynamic programming language; with multiple dispatch as its core programming paradigm. [The programming language] supports concurrent, (composable) parallel and distributed computing (with or without using [Message Passing Interface (MPI[)][29] or the built-in corresponding[clarification needed][30] to "OpenMP-style" threads[31]), and direct calling of C and Fortran libraries without glue code. [The programming language] uses a just-in-time (JIT) compiler [...].
[The programming language] is garbage-collected,[34] uses eager evaluation, and includes efficient libraries for floating-point calculations, linear algebra, random number generation, and regular expression matching. [...]
[...]
[The programming language] works with other languages, calling C has special support [...].

History
[...]
[...] in December 2019 the company got $1.1 million funding from the US government to "develop a neural component machine learning tool to reduce the total energy consumption of heating, ventilation, and air conditioning (HVAC) systems in buildings".[84] In July 2021, [the programming language] Computing announced they raised a $24 million Series A round led by [an investor],[85] which also owns [a] Formula 1 team [...], that partnered with [the programming language company]. [The Formula 1 team's] Commercial Director said: "Investing in companies building best-in-class cloud technology is a strategic focus for [an investor] and [the programming language]'s versatile platform, with revolutionary capabilities in simulation and modelling, is hugely relevant to our business. We look forward to embedding [the programming language company] in the world's most technologically advanced sport".[86]

Language features
[The programming language] is a general-purpose programming language,[87] while also originally designed for numerical/technical computing. It is also useful for low-level systems programming,[88] as a specification language,[89] High-level Synthesis (HLS) tool (for hardware, e.g. FPGAs),[90] and for web programming[91] at both server[92][93] and client[94][16] side.
The main features of the language are:

Multiple dispatch (also termed multimethods in Lisp) is a generalization of single dispatch - the polymorphic mechanism used in common object-oriented programming (OOP) languages, [...] that uses inheritance. [...] Concrete types can not themselves be subtyped the way they can in other languages; composition is used instead (see also inheritance vs subtyping).
[...]
[The programming language] draws inspiration from various dialects of Lisp, including Scheme and Common Lisp, and it shares many features with Dylan, also a multiple-dispatch-oriented dynamic language (which features an ALGOL-like free-form infix syntax rather than a Lisp-like prefix syntax, while in [the programming language] "everything"[99] is an expression), and with Fortress, another numerical programming language (which features multiple dispatch and a sophisticated parametric type system).

[...]

Implementation
[...]
Since [the programming language] uses JIT, [the programming language] generates native machine code directly, before a function is first run (i.e. a different approach than compiling to bytecode, that you distribute by default, to be run on a virtual machine (VM), as with e.g. Java/JVM; then translated from the bytecode while running, as done by Dalvik on older versions of [the partial OS variant] Android).
[...]"

Comment
Our fans and readers might take some time to compare this programming language with the programming language Java and with our Ontologic Programming (OP) paradigm to be able to give the obvious answer where the ""everything is an expression" and other properties truly come from.
Honestly, we always wonder since 2006 why they are still creating (new and rudimentary) programming languages for other reasons than education.

Sadly to say, that programming language is based on the old general approach and is more or less just only syntactic sugar, which is hyped by marketing, as usual.

In relation to the legal and commercial matters we simply refer to the

which by the way do apply for this programming language and for all entities in the U.S.America and elsewhere as well.

Now, we are coming back to the truly original and interesting thing, which is our OS, including our Evoos. But let us mention at first the following:
Success story continues and no end in sight

In fact, one can already see now where that circus is going to after fiddling around with for example what is wrongly called

or better said how it continues with following us. We already pointed at this in relation to SCN 1 in 2019 and SCN 2 recently, as well as other works related to our Ontologic Web (OW) or Universal Brain Space or Global Brain 2.0, and formerly Global Brain Grid.

As we always say, two of the foundational ideas behind our OS are to

In this way, our Ontologic System Architecture (OSA) integrates all in one and can be viewed as a layered system, which depends on the applied ontology respectively point of view of the user respectively observer (see also the Arrow System (AS) of the TUNES OS once again).
We explained this general property many years ago by taking an atom model and the location of an electron at a specific time as an example.

We also have

We also know that no single solution fits all demands regarding the successors of the Internet, the World Wide Web (WWW), and the Mixed Reality (MR).
But everything existing and being proposed is based on these old and new structures and technologies respectively solutions, and we can map all concepts and data structures of Client-Server, Master-Worker, Cluster, P2P, what is wrongly called GCEFC, Centric/Named networking, and so on in a standardized and efficient way.

What we are doing right in the last days is to use our general foundation for the final definition or configuration of the technical details of the special use case of interconnected networking, which is including supercomputing, and so on and is based on supercomputing itself. The concept is already known since 1999 and 2006, and how this looks like should be obvious for true experts after all of our publications.

We also said to begin with a name service and a Name Resolution Server (NRS), or better said Name Resolution Cluster (NRC), based on for example the physical locations of the hardware, which can be static or fixed, or dynamic or mobile. This is even needed with a flat or single layer architecture.
At this point, we also have the OntoBase and OntoBot components available, including Prolog, Datalog, and Network Datalog (NDlog), and every other kind of abstract machine, programming language, datastorage, database, logic engine, and so on (see the feature of "'Full Scripting' of the operating system functions (see e.g. Open Source Poplog and OntoBot)" listed in the Feature-List #1 and note that our OS has these features by design at least since its start in October 2006, though Evoos has some features since December 1999).
This allows for example to specify and verify policies declaratively with or without executive models or specifications in general and to do declarative networking in particular even with Autonomic Computing (AC) and Resource-Oriented Computing (ROC) through our OntoBot.

The next requirement after naming and routing/forwarding is binding. SCN 2 with SAL supports late binding as is the case with some few other approaches in the field of Centric/Named networking, including plagiarisms of the related part of our OS.

But it must also be as fast as possible and KISS. What we have seen so far is not faster than TCP/IP, which is an argument for keeping name resolution and related network protocols as long as no alternative is available everywhere.

We are also bothered by the approach that suddenly everything related to what is wrongly called GCEFC, Future Internet, New Generation Network (NGN) (e.g. Centric/Named networking), and so on should be a service of an application, which is not the case.

Obviously, many experts and even non-experts have understood at least this part of our OS.

We are still working through SCN 2 and also reading the plagiarisms discussed in the last days.

The rest is puzzling the pieces together in the best way. But as we said before, it is clear how our OS works and it is time for the legal matter.

Welcome to the Ontoverse (Ov).

17.November.2022

Ontonics Further steps

We have continued with the adjustment of our overall business plan, specifically the investment and development plans and the sequence of steps, to adapt to the latest decisions of governments and industries (see also the Ontonics Further steps of the 9th of June 2022).

We also extended the special investment program for the Amazon region, which now includes for example a truly working reforestation and a truly sustainable forestry and wood working industry besides other activities as part of our environmental reconstruction and climate change reversal.

18.November.2022

14:10, 19:25, and 29:12 UTC+1
Further steps

*** Work in progress ***
Names are the objects and the nodes in a network. For supporting to this approach, we already have a scalable Name Resolution System (NRS), which allows topological addressing physically and virtually.
But a network has also edges between the nodes. Therefore, we also need a scalable routing system and the TCP/IP and the Border Gateway Protocol (BGP) routing are considered since over 15 years as not being adequat for what we are realizing worldwide and keeping them is only meant for backward compatibility (in the phase of transition to our Ontoverse (Ov)).

We have

in addition to all the many other technologies.

"The fundamental problem in scaling the current routing architecture is that the architecture still treats every [Autonomous System (]AS[) introduced with EGP (the predecessor of BGP)] equally (i.e., the routing at the Inter-domain level is flat), even though customer networks (e.g., university campuses) and provider networks (e.g., [a large Communication Service Provider (CSP)]) have different business models, different growth trends, and different goals in network operations. At the same time, the Internet depends [on] topologically aggregatable address assignments to scale its routing system."
"Two different dimensions of approaches/trade­offs [(related to only name resolution, not name-based routing)]:

{better explanation, because of our more general solution, but it remains some kind of another Area of Interest (AoI)} Required for scalable routing/forwarding is the separation of Globally Routable Addresses (GRA) and Globally Deliverable Addresses (GDA), {not quite correct, because our approach based on graph and DVE is more general} specifically our GRA/GDA Separation Protocol (GGSP), which is not necessarily the same as the session layer IDentifier (ID) (endpoint "name", "who respectively what")/routing and forwarding locator (LOC) (source and destination "address", "where") (ID/LOC) split, specifically the Locator/ID Separation Protocol (LISP) for IPv6 addresses (November 2007).
But our ON provides both and we even have the generalized approach and much more with high performance and efficiency, and get late binding for free in this way once again.
For example, it allows to do so in a GDA 1 again be separating it into GDA 1 GRA or or GRA 2, and GDA 1 GDA or GDA 2 or using a graph-based topology, which is different to a hierarchy respectively tree.
Interestingly, our {approach, Universal SP} GGSP also matches all the other computing and networking paradigms, approaches, and implementations mentioned above, as we have shown with DVE or NVE in the past. It is the same pattern, structure, graph, and so on.
For example, a host and a router of our Ontologic Net (ON) have also an Area of Interest (AoI), or better said Location of Interest (LoI) or Domain of Interest (DoI), and ds not (need to) know what is going on in all locations, sites, areas, domains, etc., and related ON hosts, routers, switches, etc. worldwide.

We already have the very clear vision of the final result and are now putting the elements together to an overall formation and already have the edge or frame of the puzzle and some chains of puzzle pieces across the inner area, so to say, besides the plans for deployment, migration, transformation, evalutation, experimentation, optimization, and evolution.

Other experts should also be able to see now, if they have not seen before, that it will be quick and scalable. In fact, our SuperCluster{s} works on the basis of a Distributed operating system (Dos) with Inter-Process Communication (IPC) and has Distributed Shared Memory (DSM), which means no mapping of network protocol addresses, locators, identifiers, or whatsoever, and our SuperPeers enable one- or two-hop lookup performance in many cases, O(1) (constant) hop lookup performance in most of the cases, and up to O(logk n) (logarithmic to the base of k, polylogarithmic time) hop lookup performance in the worst cases, which are the cases of hotspot regions with churn-intensive workloads, in the related P2P networks.
{(some or all(?)) SuperPeers are / can be parts / nodes of a SuperCluster and the related IPC facility} Moreover, the SuperCluster and the SuperPeers {on one level} are working together as fast as a cluster located at one site, while the SuperCluster even works as a parallel supercomputer.
As a simple consequence, the other sites / nodes can also be SuperClusters and cluster nodes, SuperPeers and peers for SuperComputing (SC or SupC), including High-Throughput Computing (HTC), High Performance Computing (HPC or HPerC), Cluster Computing (CC or ClusterC), Grid Computing (GC or GridC), and so on.
In fact, the hierarchy or distance of network nodes and facilities must be quite deep or long to have an effect and there exist a lot of optimizing features depending on the use cases to improve joint computing and networking, including communication and collaboration.
But the Ontologic Applications and Ontologic Services (OAOS) will also be able to communicate, even multicast, in O (logk n)(!?) with a proper network topology and management, which depends on the site owner and operator, and OAOS Provider (OAOSP).

Furthermore, by the foundations and separations of addresses, locators, and identities external unauthorized entities do not get access to the naming and routing/forwarding systems, and authorized entities, who have access for very convincing reasons, will be few in numbers and known in person, on site, and at any time.
We will see when and where who is what disturbing, hacking, stealing, and destroying, while all others and their rights and properties are protected.

The overall result, our ON, OW, and OV, is far beyond everything others were imagining, researching, and developing in relation to the successors of the old Internet, the old World Wide Web (WWW), the old Semantic (World Wide) Web (SWWW), the old Internet of Things (IoT), the old Semantic Web of Things (SWoT), our old Industry 4.0 (I 4.0), and so on.

So it works reliably and securely all the time and even in real-time, at least where and when required, which is a new world, or better said our New Reality (NR).

23.November.2022

20:14 UTC+1
Further steps, Ontologic Net Further steps

*** Work in progress ***
This is a continuation of the work mentioned in the Further steps of the

and the matter referenced therein, which is related to what is wrongly called

• Information-Centric Networking (ICN), including
  • Content-Centric Networking (CCN) 2007/Named Data Neworking (NDN) 2010,
  • Named Function Networking (NFN) ("extends the CCN/NDN" respectively classic ICN),
  • Publish-Subscribe Internet Routing Paradigm (PSIRP) and PUblish-SUbscribe Internet Technologies (PURSUIT),
  • Service-Centric Networking (SCN),
  • etc.,

by others, and plagiarisms and OntoClones by us.

The main idea differs from resolving the "schizophrenic nature of addresses", because they serve as

by separating them (LOC/ID split) and the fields of

• SuperComputing (SC or SupC), including
  • High-Throughput Computing (HTC),
  • High Performance Computing (HPC or HPerC),
  • Cluster Computing (CC or ClusterC),
  • Grid Computing (GC or GridC),
  • and so on,
• Peer-to-Peer Computing (P2PC),
• (Object-Oriented (OO 1)) technologies (OOx),
• Service-Oriented technologies (SOx),

in so far that the creative and innovative step is to put features and functions of these fields into the network layer and transport layer of the Interconnected network (Internet) or to take them as basis for a substitution of these layers.
The problem with related works is that we have already expressed this idea with our OS and its OS Architecture (OSA) and basic properties, specifically our eXtended Mixed Reality (XMR), including Distributed Virtual Environment (DVE) or Networked Virtual Environment (NVE), and Collaborative Virtual Environment (NVE), and Problem Solving Environment (PSE), specifically with the transformation of the Interconnected network (Internet) into a Wide Area Network (WAN) SuperComputer (SC) (WANSC) or Interconnected supercomputer (Intersup) as part of our Ontologic Net (ON), and that the prior art referenced in those works is merely about the fields listed above.
Furthermore, some works

• holding on to a flat address space,
• holding on to a flat routing architecture, but "prefix aggregation runs into direct conflict with supporting end-site multihoming in the current routing system architecture",
• holding on to the Border Gateway Protocol (BGP), or
• moving the issue to other parts of their new approaches, for example by employing a "flat namespace for [Named data objects (]NDO[)] names, i.e., there is neither topology- nor organization-related hierarchy in names" and "pure name-based routing (in the sense of "routing on flat names")" (see also Routing On Flat Labels (ROFL)),

• location in the control plane, the data plane, and the forwarding plane,
• concatenation, or
• integration,

or

We are also working only on some last details of implementation, specifically in relation to performance and efficiency. For example, some approaches include functionalities of

or handle them in different ways.

One central element is the mapping function or mapping service for network address spaces, protocols, locators, and identities.
Neither concatenation nor integration does solve all problems. In addition, the various general problems are moved to the mapping.
Our original and unique approach with our Ontologic System Architechture (OSA), which integrates all in one, including

schemes, which

For this we have an ontology for the general properties and configurations, and what we propose is a related reflective or plug-in approach.

We have already some improvements of our ON related to the fields of Distributed Hash Table (DHT) and Tuple Space (TS), and also the technologies and functionalities of transaction, communication, and collaboration, etc..
We are not sure if the latency for routing/forwarding, messaging, multihoming, traffic engineering, and so on in our ON will be as fast as in the Internet or even faster through all the new and advanced, required and desired features and functionalities, specifically if and how we add the Network Datalog (NDlog).

We have to note that all these publications referenced above are not finalized and therefore some contents might be confusing, deficient, or even wrong, which will be cured or removed, and potentially summarized in an appropriated way.

26.November.2022

14:50 UTC+1
Further steps, Ontologic Net Further steps

*** Work in progress ***
We have ended the review of the performances and efficiences of our ON with the conclusion that it will be state of the art in practice and precise numbers can only given by measures in operation.
As we already noted, the infrastructures of our SOPR allow a seamless migration and further experimentation, development and research, and improvement.

Because certain features and functionalities are part of the networking (layer), we are also reviewing and adapting some details in relation to the fields of

in accordance with our Ontologic System Architecture (OSA). But this activity does not affect the implementation of the first fabrics with their subsystems and platforms of the infrastructures of our SOPR and our other Societies and adaption of existing technologies, goods, and services.

27.November.2022

17:10 UTC+1
Ontonics Further steps

Another social, legal, and technical problem is developing since around 15 years and reaching a point, where measures are required.
Therefore, we have researched and developed 4 measures regarding the hardware, the software, and the processes, and also the environment by exploiting basic properties of our Ontologic System (OS) with its Ontologic System Architecture (OSA), Ontoverse (Ov), Ontoscope (Os), and other original and unique elements.
But as in the case with our Ontologic Financial System (OFinS) with its Ontologic Bank (OntoBank), Ontologic Exchange (OEx or OntoEx), and other elements, we will directly communicate with the governments and their responsible ministries of the interior and other authorities.

28.November.2022

20:07 UTC+1
Ontologic Net Further steps

We have continued the work on the initial configuration of our Ontologic Net (ON), which we also called puzzling together the various parts and details.
Especially, we configured the structured Peer-to-Peer (sP2P) part, specially in relation to the

• item by item, data by data, or point by point, and
• range query,

which are required, because our ON

Further aspects are related to the fields of

and also the custom configuration and operation.
But these are no-brainers respectively a finger exercise with a good system architecture, because everything can be integrated, configured, and handled seamlessly.

One interesting problem is the replication, because we have replication at the

One interesting aspect is the combination and integration of spatial matter.

One interesting improvement is the integration of mapping functions for the

We have the impression that in many cases, if not in all cases, only one mapping is required or two mappings can be merged into one mapping, which decreases latency and round-trip delay, and increases performance, efficiency, and security, obviously.

One interesting fact is that all foundational features and functionalities of our ON have a performance of up to O(log n) and wherever and whenever possible we use parallel computing, data structures, algorithms, and solutions with a performance of O(c) with c = 1 or 2 in many cases, O(1) (constant) in most of the cases, and up to O(logk n) (logarithmic to the base of k, polylogarithmic time) in worst cases.

We also concluded that we are at the point where we can begin with the preparation, implementation, and deployment worldwide, and also the consideration if we should call it ON 2.0.